diff options
Diffstat (limited to 'zarb-ml/mageia-sysadm/2011-July/003760.html')
| -rw-r--r-- | zarb-ml/mageia-sysadm/2011-July/003760.html | 132 |
1 files changed, 132 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2011-July/003760.html b/zarb-ml/mageia-sysadm/2011-July/003760.html new file mode 100644 index 000000000..46058777a --- /dev/null +++ b/zarb-ml/mageia-sysadm/2011-July/003760.html @@ -0,0 +1,132 @@ +<!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=%3C1311076966.6636.125.camel%40akroma.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="003752.html"> + <LINK REL="Next" HREF="003765.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-sysadm] Questions about puppet config</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Questions%20about%20puppet%20config&In-Reply-To=%3C1311076966.6636.125.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-sysadm] Questions about puppet config">misc at zarb.org + </A><BR> + <I>Tue Jul 19 14:02:45 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="003752.html">[Mageia-sysadm] Questions about puppet config +</A></li> + <LI>Next message: <A HREF="003765.html">[Mageia-sysadm] Questions about puppet config +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3760">[ date ]</a> + <a href="thread.html#3760">[ thread ]</a> + <a href="subject.html#3760">[ subject ]</a> + <a href="author.html#3760">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>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> 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> +Mainly a question of style. + +You can use the graph feature to see everything : +<A HREF="http://bitfieldconsulting.com/puppet-dependency-graphs">http://bitfieldconsulting.com/puppet-dependency-graphs</A> +( except that we do not provides them purely by slack ) + +I guess a simple task to learn puppet would be to make them usable by +everybody. But I can also do it quite fast, if you need to look to the +graphs. + + +><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> +This seems quite overkill for simple module, and I am not sure it will +help to reduce so much the complexity on complex module ( such as sympa +or subversion ). While I would agree that we should have some shared +style to help rereading the code, I also think this is one issue that +can trigger some heated arguments. Despite being annoyed every day by +the mix of space and tabs in subversion or buildsystem, I never pushed +for uniformisation there, but maybe that should be done. + +><i> +</I>><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> +It greatly depend on what you mean by "work" :) + +I do not see obvious reasons it would break something, and to me, the +question is just to know if too much division will really improve +comprehension. + +It is like java. I like the java layering and separation of modules, at +least on paper, it is quite clean. In practice, there is this feeling of +awful complexity due to the separation and heavy use of object +hierarchy :/ + +I can understand your frustration of having to read a large corpus of +code/configuration without having this feeling of a clean base ( ie, +different conventions, lack of style, etc ). And we do have some need +for cleaning and consistency for sure. + +But on the other hand, having a too rigid structure of things may have +been too constraining for a small team, to start. + +><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> +The granularity is already achieved at class level, and I think we are +quite good at this point. Too much would maybe be over-engineering at +this point, we only have 7 servers :) + +-- +Michael Scherer + +</PRE> + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="003752.html">[Mageia-sysadm] Questions about puppet config +</A></li> + <LI>Next message: <A HREF="003765.html">[Mageia-sysadm] Questions about puppet config +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3760">[ date ]</a> + <a href="thread.html#3760">[ thread ]</a> + <a href="subject.html#3760">[ subject ]</a> + <a href="author.html#3760">[ 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> |