1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-sysadm] [138] use a cname for puppet
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20%5B138%5D%20use%20a%20cname%20for%20puppet&In-Reply-To=%3C1288969075.25457.36.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="000261.html">
<LINK REL="Next" HREF="000253.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-sysadm] [138] use a cname for puppet</H1>
<B>Michael Scherer</B>
<A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20%5B138%5D%20use%20a%20cname%20for%20puppet&In-Reply-To=%3C1288969075.25457.36.camel%40akroma.ephaone.org%3E"
TITLE="[Mageia-sysadm] [138] use a cname for puppet">misc at zarb.org
</A><BR>
<I>Fri Nov 5 15:57:55 CET 2010</I>
<P><UL>
<LI>Previous message: <A HREF="000261.html">[Mageia-sysadm] [138] use a cname for puppet
</A></li>
<LI>Next message: <A HREF="000253.html">[Mageia-sysadm] [139] Add a few more dependencies
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#266">[ date ]</a>
<a href="thread.html#266">[ thread ]</a>
<a href="subject.html#266">[ subject ]</a>
<a href="author.html#266">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le vendredi 05 novembre 2010 à 14:59 +0100, nicolas vigier a écrit :
><i> On Fri, 05 Nov 2010, Michael Scherer wrote:
</I>><i>
</I>><i> >
</I>><i> > I see 2 solutions :
</I>><i> > - keep in sync puppet.conf with modules/puppet/templates/puppet.conf
</I>><i> > - (re)move puppet.conf so it doesn't conflict, and be sure that puppet
</I>><i> > deploy the proper one even on the master
</I>><i>
</I>><i> I don't understand 2nd solution. But 1st solution seems ok.
</I>
cd $CHECKOUT_OF_PUPPET
svn rm puppet.conf
svn commit
then, on next cron update on puppetmaster :
svn up will remove puppet.conf
then puppet agent will kick in, recreate the config file and all is
well.
Then later, updates are handled like all others file managed by puppet.
( we should just be sure that we do not ask puppet to reload when the
file change and while it is updating itself )
Or I hope so.
We may have to add the puppet file by hand for the migration however.
><i> But maybe new changes to puppet.conf on clients are going to be very
</I>><i> rare, so it can be ok if managed managed manually ?
</I>
I was planning on enabling some features after more tests :
- reporting, so we get mail when there is a error ( once I have tested
the feature, doing mistakes is not so easy :p )
- filebucket, so file are saved if the were manually edited on the
server ( useful to prevent errors ), didn't play with it
- there is also a system of plugin, that could be used if we start to
manage urpmi with it ( I have such a plugin, except it is not finished
and do not work and not public ), and this requires "pluginsync = true"
in agent
- puppet config file may change ( they changed it for 2.6 ) and so may
requires cluster wide update to remove warning
I also think we could use storedconfig in the futur ( puppet node send
their configuration to the master ), but this doesn't requires config on
client, afaik.
--
Michael Scherer
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000261.html">[Mageia-sysadm] [138] use a cname for puppet
</A></li>
<LI>Next message: <A HREF="000253.html">[Mageia-sysadm] [139] Add a few more dependencies
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#266">[ date ]</a>
<a href="thread.html#266">[ thread ]</a>
<a href="subject.html#266">[ subject ]</a>
<a href="author.html#266">[ 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>
|
