diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-sysadm/2011-July/003765.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-1be510f9529cb082f802408b472a77d074b394c0.tar archives-1be510f9529cb082f802408b472a77d074b394c0.tar.gz archives-1be510f9529cb082f802408b472a77d074b394c0.tar.bz2 archives-1be510f9529cb082f802408b472a77d074b394c0.tar.xz archives-1be510f9529cb082f802408b472a77d074b394c0.zip | |
Diffstat (limited to 'zarb-ml/mageia-sysadm/2011-July/003765.html')
| -rw-r--r-- | zarb-ml/mageia-sysadm/2011-July/003765.html | 154 |
1 files changed, 154 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2011-July/003765.html b/zarb-ml/mageia-sysadm/2011-July/003765.html new file mode 100644 index 000000000..fc045d696 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2011-July/003765.html @@ -0,0 +1,154 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-sysadm] Questions about puppet config + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Questions%20about%20puppet%20config&In-Reply-To=%3CCAHHMSxiq6WaNdgv8f9%2B3C8p3At-EG%2BVZSmT5-5RTP9sZCxrbww%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="003760.html"> + <LINK REL="Next" HREF="003811.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-sysadm] Questions about puppet config</H1> + <B>Sébastien Kurtzemann</B> + <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Questions%20about%20puppet%20config&In-Reply-To=%3CCAHHMSxiq6WaNdgv8f9%2B3C8p3At-EG%2BVZSmT5-5RTP9sZCxrbww%40mail.gmail.com%3E" + TITLE="[Mageia-sysadm] Questions about puppet config">sebelee at free.fr + </A><BR> + <I>Tue Jul 19 17:38:50 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="003760.html">[Mageia-sysadm] Questions about puppet config +</A></li> + <LI>Next message: <A HREF="003811.html">[Mageia-sysadm] Questions about puppet config +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3765">[ date ]</a> + <a href="thread.html#3765">[ thread ]</a> + <a href="subject.html#3765">[ subject ]</a> + <a href="author.html#3765">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>2011/7/19 Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">misc at zarb.org</A>> +><i> +</I>><i> Le mardi 19 juillet 2011 à 02:54 +0200, <A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">sebelee at free.fr</A> a écrit : +</I>><i> > After regarding a little bit the puppet configuration, I have some questions about the current puppet configuration. +</I>><i> > +</I>><i> > +</I>><i> > 1) Why using both subscribe() and notify() metaparameters ? +</I>><i> +</I>><i> Mainly a question of style. +</I>><i> +</I>><i> You can use the graph feature to see everything : +</I>><i> <A HREF="http://bitfieldconsulting.com/puppet-dependency-graphs">http://bitfieldconsulting.com/puppet-dependency-graphs</A> +</I>><i> ( except that we do not provides them purely by slack ) +</I>><i> +</I>><i> I guess a simple task to learn puppet would be to make them usable by +</I>><i> everybody. But I can also do it quite fast, if you need to look to the +</I>><i> graphs. +</I>><i> +</I>><i> +</I>Okay thanks for this information about viewing graphs dependency ;) + +><i> > 2) In the same idea, after reading the beginning of the book "Pro Puppet", the author +</I>><i> > describes a sort of Best Pratice for managing puppet's module. +</I>><i> +</I>><i> This seems quite overkill for simple module, and I am not sure it will +</I>><i> help to reduce so much the complexity on complex module ( such as sympa +</I>><i> or subversion ). While I would agree that we should have some shared +</I>><i> style to help rereading the code, I also think this is one issue that +</I>><i> can trigger some heated arguments. Despite being annoyed every day by +</I>><i> the mix of space and tabs in subversion or buildsystem, I never pushed +</I>><i> for uniformisation there, but maybe that should be done. +</I>><i> +</I>Ok + +><i> > 3) With this schema, we can also classify specials functionnalites or class by creating one or more extra file(s) +</I>><i> > +</I>><i> > +</I>><i> > I'm just a beginner with puppet and I don't know if this a method can work +</I>><i> > for a production environnement day after day... +</I>><i> +</I>><i> It greatly depend on what you mean by "work" :) +</I>><i> +</I>With "work", I mean not breaking the current architecture :P + +><i> I do not see obvious reasons it would break something, and to me, the +</I>><i> question is just to know if too much division will really improve +</I>><i> comprehension. +</I>><i> +</I>><i> It is like java. I like the java layering and separation of modules, at +</I>><i> least on paper, it is quite clean. In practice, there is this feeling of +</I>><i> awful complexity due to the separation and heavy use of object +</I>><i> hierarchy :/ +</I>><i> +</I>><i> I can understand your frustration of having to read a large corpus of +</I>><i> code/configuration without having this feeling of a clean base ( ie, +</I>><i> different conventions, lack of style, etc ). And we do have some need +</I>><i> for cleaning and consistency for sure. +</I>><i> +</I>><i> But on the other hand, having a too rigid structure of things may have +</I>><i> been too constraining for a small team, to start. +</I>><i> +</I>I'm not afraid to read large corpus ;) +But it's more difficult to start and understand how things works if we +had different conventions and structures all over modules. +And I completely agree with you that a too rigid structure may constraint team. + +So starting to send you some patches for cleaning and uniform modules +structures will be a good thing now ? Or maybe later ? Or Not ? + +><i> > But i think instead of having all the module's classes in a same file, split them +</I>><i> > into specifics items would be more easy for understanding and also give more granularity. +</I>><i> +</I>><i> The granularity is already achieved at class level, and I think we are +</I>><i> quite good at this point. Too much would maybe be over-engineering at +</I>><i> this point, we only have 7 servers :) +</I>><i> +</I>Yep + +><i> -- +</I>><i> Michael Scherer +</I>><i> +</I>><i> _______________________________________________ +</I>><i> Mageia-sysadm mailing list +</I>><i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">Mageia-sysadm at mageia.org</A> +</I>><i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">https://www.mageia.org/mailman/listinfo/mageia-sysadm</A> +</I> +-- +Sébastien Kurtzemann +</PRE> + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="003760.html">[Mageia-sysadm] Questions about puppet config +</A></li> + <LI>Next message: <A HREF="003811.html">[Mageia-sysadm] Questions about puppet config +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3765">[ date ]</a> + <a href="thread.html#3765">[ thread ]</a> + <a href="subject.html#3765">[ subject ]</a> + <a href="author.html#3765">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm +mailing list</a><br> +</body></html> |