It matters not to me, since i cannot install the new update to Firewalld. I,am still using the one that was installed by default The old fashion system used by Linux to install updates, is only used by the old school linux users, who can unpack it to the proper directory?nobody can, and then install it. Yum never opens tar.gz or tar.bz archives,returns a message and says (YUM nothing to do?) and if you cannot install an app,especially a Firewall daemon, what the hell is the sense of using it.like i said the update sytems are useless, and should be Auto installed,like Windows does it,with there install sheild, it is totally unusable by all Linux newbies, and mid level Linux users,as well. so we do not update, and cannot participate in any sharing of data to help fix any problems.I have said this over and over for years, and the same package update confusion still exists today. you should Standardize the package updating, and build auto installers,which put it in the correct Directory, and if any command line users want to install it themselves to another location, were they want it let them have the option at install, to bypass the auto install. Randy Fitzgerald


On Thu, Jun 26, 2014 at 7:19 AM, Jiri Popelka <jpopelka@redhat.com> wrote:
Hi,

this is just heads-up to let you know early, that I've started working on firewalld module for Puppet recently.
It's in very early stage, because I knew nothing about Puppet a week ago.

It lives here:
https://github.com/jpopelka/puppet-firewalld

Testing it on Fedora is piece of cake, just get a repo file from
https://copr.fedoraproject.org/coprs/jpopelka/puppet-firewalld/
and put it into /etc/yum.repos.d/
There's only rawhide-x86_64 for Fedora, but that should be fine for all Fedoras/archs, because the module is noarch.

Install the module with:
# yum install puppet-firewall

Then try the included example with:
# puppet apply /usr/share/doc/puppet-firewalld/examples/misc-example.pp

What the example does at the moment is:
- install firewalld package
- disable ip[6]table services
- create a zone called "custom" with few opened ports and predefined services
- set it as default zone
- (re)start firewalld

Sample of documentation is here:
http://jpopelka.fedorapeople.org/puppet-firewalld/doc/firewalld/zone.html

I'll be glad for any suggestions as I know very little about what Puppet can and can't do.

--
Jiri
_______________________________________________
firewalld-users mailing list
firewalld-users@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/firewalld-users