From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-sysadm/2010-November/000528.html | 97 +++++++++++++++++++++++++ 1 file changed, 97 insertions(+) create mode 100644 zarb-ml/mageia-sysadm/2010-November/000528.html (limited to 'zarb-ml/mageia-sysadm/2010-November/000528.html') diff --git a/zarb-ml/mageia-sysadm/2010-November/000528.html b/zarb-ml/mageia-sysadm/2010-November/000528.html new file mode 100644 index 000000000..2b8a0e260 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-November/000528.html @@ -0,0 +1,97 @@ + + + + [Mageia-sysadm] Installing firewall + + + + + + + + + +

[Mageia-sysadm] Installing firewall

+ Michael Scherer + misc at zarb.org +
+ Mon Nov 15 01:47:23 CET 2010 +

+
+ +
Le vendredi 12 novembre 2010 à 18:30 +0100, nicolas vigier a écrit :
+> Hello,
+> 
+> The Mageia packages repository will be stored on valstar. As the
+> repository will be needed on build nodes, it will have to be either
+> mirrored or mounted via nfs (readonly). If we use nfs, I think we should
+> first setup a firewall before installing the nfs server. A firewall
+> would also be useful to filter connections to the pgsql/mysql servers,
+> to the build nodes, etc ...
+> 
+> I suggest using shorewall to manage the firewall configuration. Any
+> comment about this ?
+
+I would rather prefer something a little bit higher level, but that's ok
+for a start. Having a good abstraction ( like some puppet class ) would
+be nice. We could also take a look at exported ressources too
+( http://projects.puppetlabs.com/projects/1/wiki/Exported_Resources ),
+so we could say "allow postgresql connexion from server running this
+class"
+
+> I plan to write a shorewall module in puppet, test it on jonund first,
+> without installing shorewall (only writting the config files), then
+> install shorewall on jonund, and if we didn't lose access to jonund
+> install it on other nodes.
+
+Technically, using puppet allow us to test on VM without much problem.
+
+And in fact, I would strongly suggest using VMs rather than our servers
+because this allow us to catch some stupid errors in the manifest that
+could help us in case of disaster recovery, or computer duplication. Not
+to mention than testing on production servers is not a good idea ( even
+if I suppose we all do this ).
+
+-- 
+Michael Scherer
+
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ -- cgit v1.2.1