Re: [Puppet Users] puppet-module-apache
Paul Lathrop writes:
> On Tue, May 11, 2010 at 7:33 PM, Daniel Pittman wrote:
>> Paul Lathrop writes:
>>
>>> I've open-sources Digg's apache module:
>>> http://github.com/plathrop/puppet-module-apache
>>>
>>> I know this isn't much more advanced than what I've seen a lot of people
>>> using.
>>
>> It looks very much like our internal, not-able-to-release version. The two
>> features we have that you don't are:
>
> Is it "not able to release yet" or "not ever gonna release"?
I would have to ask my boss; it could be the former, but we have not looked at
the plans. Honestly, until relatively recently enough of this stuff was
limited to "what we need and absolutely no more" that it wouldn't be much help
to most people.
Apache is about the exception, because it is used enough that it is reasonably
flexible.
>> * the module enable/disable feature also ships appropriate configuration and
>> installs the appropriate packages for the platform.
>
> Nice, I'd love to add that.
We did it the nasty way:
define apache::module (...) {
case $name {
"fastcgi": {
package { libapache2-mod-fastcgi: ensure => latest }
# ...and if you need config, use apache::conf here.
}
}
}
Obviously that is going to be doing more for other platforms than Debian.
[...]
>> * apache::listen{,::port80,::port443}, which configures the system to listen
>> on a custom port, and then wraps that in a class for the standard ports.
>
> I don't do it quite the same way, but there is a tunable for the
> ports: $apache_listen_ports
*nod* We ended up with various services needing to deploy to different ports,
and that worked out the best way for them to coordinate that without a single
point that set it up.
>>> Here's my proposition, though. Let's get all the disparate "apache" modules
>>> out there merged together into One Awesome Module. What do you think?
>>
>> Sounds like a great idea to me, but it is a heck of a lot of work.
>
> Yeah, but I'm going to try anyway.
Well, while releasing internal config might be hard, contributing back to an
upstream project we use is easy to approve, so I will see how far we would
need to change to use your module as the base for what we do.
If we can get that I (and my staff) can contribute back enhancements to y'all
easily, and I do want to do that — the less code I maintain the cheaper this
is for my boss.[1]
>> The most likely "next" feature for us, incidentally, will be to try and
>> extract the parts of a VirtualHost tag that are custom, and the parts that
>> are
>> standard like the header, auth, logging, etc, so that we don't duplicate
>> those
>> in dozens of different files we install...
>
> I love this idea. Will have to see if I can add something to this module.
*nod* My goal was to get the "80 percent" bit right: make it easy to turn on
features like injecting a configuration fragment for authentication.
My rough thought was to make it dynamic: supply a string name for "auth", and
it includes some boilerplate in the right location, and then interpolates a
template I supplied with the right name, or something...
Not really a finished thought though.
Daniel
Footnotes:
[1] ...and the less it sucks when I got to the next company, since I don't
have to rebuild all that nice infrastructure from scratch.
--
✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet-module-apache
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/05/10 12:33 PM, Daniel Pittman wrote: > > * the module enable/disable feature also ships appropriate configuration and >installs the appropriate packages for the platform. > There's also this that I and Teyo wrote - that manages Apache modules on Debian/Ubuntu. http://github.com/jamtur01/puppet-apache-modules Regards James Turnbull - -- Author of: * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBS+ouISFa/lDkFHAyAQJYkAgAkZW6Do8cnVhcpVrVABfjCnjjm1JJzYnw ISjcx1k0KRfKmPLsjxWftn+al2jH6yRCjdESw1AZunBWIXRBzb25VnBMt7KIpV+e Bc1/wp0sUWcznYUEwlRne4OjYLUd9tQkETH/m+K5AR92WNjmjR0leAW6AF3HZkZP 1z8MeSc0jyxewUgixM7vaV3nWKqud1pkhmDF4bcsBpP8cCZFsYHMiO0dK8QO6g78 IeixquwUCNONva7dDNSLgzuaAjU7ltl83cVta4Kq7vZiTFIhPAZguOZxRPv7uAhQ NIvyR99TgfMHTyMsA4Nnpoaxa1F0anoQhxFaJP885QmRci7NzqqdBQ== =1JJt -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet-module-apache
On Tue, May 11, 2010 at 7:33 PM, Daniel Pittman wrote:
> Paul Lathrop writes:
>
>> I've open-sources Digg's apache module:
>> http://github.com/plathrop/puppet-module-apache
>>
>> I know this isn't much more advanced than what I've seen a lot of people
>> using.
>
> It looks very much like our internal, not-able-to-release version. The two
> features we have that you don't are:
Is it "not able to release yet" or "not ever gonna release"?
> * the module enable/disable feature also ships appropriate configuration and
> installs the appropriate packages for the platform.
Nice, I'd love to add that.
> * apache::conf, which installs a fragment in conf.d/*
Actually, apache::config in my module does exactly that.
> * apache::listen{,::port80,::port443}, which configures the system to listen
> on a custom port, and then wraps that in a class for the standard ports.
I don't do it quite the same way, but there is a tunable for the
ports: $apache_listen_ports
>> Here's my proposition, though. Let's get all the disparate "apache" modules
>> out there merged together into One Awesome Module. What do you think?
>
> Sounds like a great idea to me, but it is a heck of a lot of work.
Yeah, but I'm going to try anyway.
> The most likely "next" feature for us, incidentally, will be to try and
> extract the parts of a VirtualHost tag that are custom, and the parts that are
> standard like the header, auth, logging, etc, so that we don't duplicate those
> in dozens of different files we install...
I love this idea. Will have to see if I can add something to this module.
--Paul
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet-module-apache
Did Isaac just volunteer to be the canary for CentOS/RHEL/Fedora? Seriously, I will integrate these various modules, including bringing in any distribution-specific stuff I can find, but I don't have any experience with the CentOS, etc. family of distributions. Related, though, is the concept that we, as a community, may want to settle on one "right way" to lay out an apache configuration. What I mean is, there ought to be a best practice established by now that we can codify into the module, and lay out the apache configs the same on Linux in general, only different where required to hook into the rest of the system. I think this is one of the few areas where the Debian way is actually really smart. That is probably a different discussion though. --Paul On Tue, May 11, 2010 at 7:13 PM, Isaac Christoffersen wrote: > +1 for this. But let's not forget the CentOS/RHEL/Fedora folks out there. > Minor but key differences in directory structure, permissions, SELinux > policies, etc. > > > On 5/11/10 9:56 PM, James Turnbull wrote: >> >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Paul >> >> These are the ones I know about: >> >> http://github.com/camptocamp/puppet-apache >> http://github.com/wesabe/puppet-apache2 >> http://github.com/puppet-modules/puppet-apache >> http://github.com/simpsonjulian/puppet-apache-ubuntu >> http://github.com/ohlol/puppet-apache >> >> Regards >> >> James Turnbull >> >> - -- Author of: >> * Pro Linux System Administration (http://tinyurl.com/linuxadmin) >> * Pulling Strings with Puppet (http://tinyurl.com/pupbook) >> * Pro Nagios 2.0 (http://tinyurl.com/pronagios) >> * Hardening Linux (http://tinyurl.com/hardeninglinux) >> -BEGIN PGP SIGNATURE- >> Version: GnuPG v1.4.7 (Darwin) >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >> >> iQEVAwUBS+oK2yFa/lDkFHAyAQKQWAf+O8Ga73MCHh357VyjJomeX3D+qXvufrf2 >> Rdn0t7gPcO30eOKzPTluF7VxvifKKaeADQktIcnX+o0+VwEYg3Yb198GQMDx >> e8Vx8MeZs8dq80anVSOko/Zc23U1+R76qQQ0zzRd9S6KzvD5bwlkTaAwtwGM2WE0 >> kS0R/xx2KA4CRQK/Vtu1u7BCrMoONbXS+5rF+6MCgYerwD+wqOPvX7PH77xdLmZz >> sFMIinJUkqcaMnZPIWXCxuwAB+abe3WxUGZ7dE1qTgrbt8BEZYuITTRRcXg+kNLO >> CfMW6sPrCtedfxxW9fyuG/Ko1BVaHlMKpG44cr5LMR0OKm3vFmWgBg== >> =vyFz >> -END PGP SIGNATURE- >> >> > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] File Hierarchy
All,
Does the file hierarchy provided below follow current best practices:
lib/
manifests/
---site.pp
---templates.pp
---nodes.pp
modules/
---{modulename}/
--depends/
--files/
--manifests/
-init.pp
-defaults.pp
--lib/
-puppet/
parser/
---functions/
provider/
type/
-facter/
--templates/
--README
---user/
---services/
---clients/
notes/
tools/
The aforementioned file hierarchy is based on the following links:
http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Best_Practice
http://docs.reductivelabs.com/guides/modules.html#internal_organisation
The only difference is that...
- the "services" and "clients" directories at the root of the hierarchy
have been made subdirectories of "modules"
- the "plugins" directory in the root of the hierarchy has been renamed
"lib"
Is this correct?
Mike
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet-module-apache
Paul Lathrop writes:
> I've open-sources Digg's apache module:
> http://github.com/plathrop/puppet-module-apache
>
> I know this isn't much more advanced than what I've seen a lot of people
> using.
It looks very much like our internal, not-able-to-release version. The two
features we have that you don't are:
* the module enable/disable feature also ships appropriate configuration and
installs the appropriate packages for the platform.
* apache::conf, which installs a fragment in conf.d/*
* apache::listen{,::port80,::port443}, which configures the system to listen
on a custom port, and then wraps that in a class for the standard ports.
> Here's my proposition, though. Let's get all the disparate "apache" modules
> out there merged together into One Awesome Module. What do you think?
Sounds like a great idea to me, but it is a heck of a lot of work.
The most likely "next" feature for us, incidentally, will be to try and
extract the parts of a VirtualHost tag that are custom, and the parts that are
standard like the header, auth, logging, etc, so that we don't duplicate those
in dozens of different files we install...
Daniel
--
✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Have I found a bug with variables in nodes?
Dan Bode writes: > On Tue, May 11, 2010 at 3:27 PM, Nigel Kersten wrote: >> On Tue, May 11, 2010 at 3:19 PM, R.I.Pienaar wrote: > > >> - "Brian Gallew" wrote: > >> in nodes and have them >> propagate to their children, then I submit that >> nodes are so >> fundamentally broken as to make node inheritance >> completely useless, in >> which case node inheritance should be pulled. > > that sums it up well. >> >> ++ I was shocked how useless node inheritance was, once we actually hit the point of doing more than adding a few static classes in it. :/ >> I haven't even told my users that nodes can do inheritance, as I haven't >> yet come across any reason to do so. We have two inherited definitions: default, and standard. default applies to anything that connects to our network, and apples the minimum set of classes required for conformance to our certification standards, etc. standard extends that with the behaviour we expect for most nodes: common authentication setup, some additional monitoring services, and so forth. Then, all nodes inherit one of those. That way we don't have to repeat ourselves: to make something common to a large class of nodes we derive their definition from default, and we can change those. So, we will be replacing that with a define, or parameterized class when they ship, that allows us to do the same thing. Given that node inheritance *looks* designed to achieve that goal, though, and I can't imagine any other use for it, pulling the entire pointless feature seems like the right decision to me. > you guys don't use an external node classifier? Is there a reason you prefer > to declare nodes? If we have to hand-maintain the data then we may as well keep it inside the puppet repository and language. There is *zero* benefit to fragmenting that data when there is one, and only one, consumer of it. We will likely move to an LDAP external node classifier once that actually brings some benefit: when we have other services sharing that directory, and/or a GUI interface to maintain it. Until then, though, declaring nodes by hand is cheaper and quicker. Daniel For a small shop, or someone just starting out, I would encourage the same thing, too. Until you grow to the size an external node classifier is required there isn't much point spending the money to implement one — only to discover you have to deploy version two that meets your actually needs. -- ✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155 707 ♽ made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet-module-apache
+1 for this. But let's not forget the CentOS/RHEL/Fedora folks out there. Minor but key differences in directory structure, permissions, SELinux policies, etc. On 5/11/10 9:56 PM, James Turnbull wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul These are the ones I know about: http://github.com/camptocamp/puppet-apache http://github.com/wesabe/puppet-apache2 http://github.com/puppet-modules/puppet-apache http://github.com/simpsonjulian/puppet-apache-ubuntu http://github.com/ohlol/puppet-apache Regards James Turnbull - -- Author of: * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBS+oK2yFa/lDkFHAyAQKQWAf+O8Ga73MCHh357VyjJomeX3D+qXvufrf2 Rdn0t7gPcO30eOKzPTluF7VxvifKKaeADQktIcnX+o0+VwEYg3Yb198GQMDx e8Vx8MeZs8dq80anVSOko/Zc23U1+R76qQQ0zzRd9S6KzvD5bwlkTaAwtwGM2WE0 kS0R/xx2KA4CRQK/Vtu1u7BCrMoONbXS+5rF+6MCgYerwD+wqOPvX7PH77xdLmZz sFMIinJUkqcaMnZPIWXCxuwAB+abe3WxUGZ7dE1qTgrbt8BEZYuITTRRcXg+kNLO CfMW6sPrCtedfxxW9fyuG/Ko1BVaHlMKpG44cr5LMR0OKm3vFmWgBg== =vyFz -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet-module-apache
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul These are the ones I know about: http://github.com/camptocamp/puppet-apache http://github.com/wesabe/puppet-apache2 http://github.com/puppet-modules/puppet-apache http://github.com/simpsonjulian/puppet-apache-ubuntu http://github.com/ohlol/puppet-apache Regards James Turnbull - -- Author of: * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBS+oK2yFa/lDkFHAyAQKQWAf+O8Ga73MCHh357VyjJomeX3D+qXvufrf2 Rdn0t7gPcO30eOKzPTluF7VxvifKKaeADQktIcnX+o0+VwEYg3Yb198GQMDx e8Vx8MeZs8dq80anVSOko/Zc23U1+R76qQQ0zzRd9S6KzvD5bwlkTaAwtwGM2WE0 kS0R/xx2KA4CRQK/Vtu1u7BCrMoONbXS+5rF+6MCgYerwD+wqOPvX7PH77xdLmZz sFMIinJUkqcaMnZPIWXCxuwAB+abe3WxUGZ7dE1qTgrbt8BEZYuITTRRcXg+kNLO CfMW6sPrCtedfxxW9fyuG/Ko1BVaHlMKpG44cr5LMR0OKm3vFmWgBg== =vyFz -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet-module-apache
+1 Here is another apache module that I wrote: http://github.com/ohadlevy/puppet-foreman/tree/master/apache2/ Thanks, Ohad On Wed, May 12, 2010 at 8:27 AM, Paul Lathrop wrote: > I'll even do the integration work, just link me to your module and > I'll try to integrate its feature set into mine. > > On Tue, May 11, 2010 at 5:17 PM, Nigel Kersten wrote: > > On Tue, May 11, 2010 at 5:15 PM, Paul Lathrop > wrote: > >> Hey all, > >> > >> I've open-sources Digg's apache module: > >> http://github.com/plathrop/puppet-module-apache > >> > >> I know this isn't much more advanced than what I've seen a lot of > >> people using. Here's my proposition, though. Let's get all the > >> disparate "apache" modules out there merged together into One Awesome > >> Module. What do you think? > >> > >> One module to rule them all > >> One module to find them > >> One module to bring them all > >> And via Puppet bind them. > >> > > > > +1 > > > > > > -- > > nigel > > > > -- > > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > > To post to this group, send email to puppet-us...@googlegroups.com. > > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com > . > > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet-module-apache
I'll even do the integration work, just link me to your module and I'll try to integrate its feature set into mine. On Tue, May 11, 2010 at 5:17 PM, Nigel Kersten wrote: > On Tue, May 11, 2010 at 5:15 PM, Paul Lathrop wrote: >> Hey all, >> >> I've open-sources Digg's apache module: >> http://github.com/plathrop/puppet-module-apache >> >> I know this isn't much more advanced than what I've seen a lot of >> people using. Here's my proposition, though. Let's get all the >> disparate "apache" modules out there merged together into One Awesome >> Module. What do you think? >> >> One module to rule them all >> One module to find them >> One module to bring them all >> And via Puppet bind them. >> > > +1 > > > -- > nigel > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet-module-apache
On Tue, May 11, 2010 at 5:15 PM, Paul Lathrop wrote: > Hey all, > > I've open-sources Digg's apache module: > http://github.com/plathrop/puppet-module-apache > > I know this isn't much more advanced than what I've seen a lot of > people using. Here's my proposition, though. Let's get all the > disparate "apache" modules out there merged together into One Awesome > Module. What do you think? > > One module to rule them all > One module to find them > One module to bring them all > And via Puppet bind them. > +1 -- nigel -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] puppet-module-apache
Hey all, I've open-sources Digg's apache module: http://github.com/plathrop/puppet-module-apache I know this isn't much more advanced than what I've seen a lot of people using. Here's my proposition, though. Let's get all the disparate "apache" modules out there merged together into One Awesome Module. What do you think? One module to rule them all One module to find them One module to bring them all And via Puppet bind them. --Paul -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Have I found a bug with variables in nodes?
On Tue, May 11, 2010 at 3:31 PM, Dan Bode wrote: > On Tue, May 11, 2010 at 3:27 PM, Nigel Kersten wrote: >> >> On Tue, May 11, 2010 at 3:19 PM, R.I.Pienaar wrote: >> > >> > - "Brian Gallew" wrote: >> > >> >> in nodes and have them propagate to their children, then I submit that >> >> nodes are so fundamentally broken as to make node inheritance >> >> completely useless, in which case node inheritance should be pulled. >> > >> > that sums it up well. >> >> ++ >> >> I haven't even told my users that nodes can do inheritance, as I >> haven't yet come across any reason to do so. > > you guys don't use an external node classifier? Is there a reason you prefer > to declare nodes? I do use one now, but spent a while looking into node inheritance trying to understand it, even given the caveats in the (quite good) documentation. > >> >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "Puppet Users" group. >> > To post to this group, send email to puppet-us...@googlegroups.com. >> > To unsubscribe from this group, send email to >> > puppet-users+unsubscr...@googlegroups.com. >> > For more options, visit this group at >> > http://groups.google.com/group/puppet-users?hl=en. >> > >> > >> >> >> >> -- >> nigel >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To post to this group, send email to puppet-us...@googlegroups.com. >> To unsubscribe from this group, send email to >> puppet-users+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- nigel -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Have I found a bug with variables in nodes?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/05/10 5:05 AM, Brian Gallew wrote: > Actually, the case I'm demonstrating is NOT covered in that FAQ. The > nodes *only* set variables. No includes happen until the final, > selective node (in this case "pslave1").If you cannot set variables > in nodes and have them propagate to their children, then I submit that > nodes are so fundamentally broken as to make node inheritance completely > useless, in which case node inheritance should be pulled. > Actually it is explained in the FAQ. Variables do not inherit between nodes, hence this the statement: "This is because the inherited test_class remains in the scope of base_node, where $testname is undefined." And: "Node inheritance is currently only really useful for inheriting static or self-contained classes, and is as a result of quite limited value." I don't think anyone has claimed that inheritance is good for anything else - I don't think this merits it being pulled but I would suggest that it merits a feature request saying "this should be fixed". Additionally, when variable scoping is revised and changed a lot of these problems will go away. I believe that's planned for the release after Rowlf. Regards James Turnbull - -- Author of: * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBS+njPSFa/lDkFHAyAQJ5Mwf/XqOM688m8ZvnYRvEZ/LehWWOYOiqwDvF 2rSbHSplR0l7CoFNRyza5mxQcBglx/iey7/4B/nHFqFyUEtSt2v2QO9WKn5EWZRH yBbufcBrhB70bsgmyYzEKoYY9AiFKkfH2PR5qJYuWEW5ViUrKZXOMVAaG6vHaIvS +WDaK8WQPFB9tccNbhCL5DYDSQ1Dl4Y0hi59CzkWR2G1t9X4TWF5v1mFoxe4mX6k 86AwEgkxWfE3lmJQnrUVZz4Kra53T6jmKcVeyvaVXeRq/HEP/BlHC4V7XijM5FCb oCt7OdpuikHrlFgjaxYNeQruw+wwjsOq2dRLDeWOpvlqUkaTB+XISg== =H1i9 -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Have I found a bug with variables in nodes?
"Haven't gotten there yet". In my case, I'm specifically choosing to use a node-based classifier for building the puppetmasters from the master-master. 8/ The puppetmasters, in turn, will use a database. But I've still got to build a half-dozen puppetmasters (network separation), so to get there I need, you know, "basic functionality". On Tue, May 11, 2010 at 3:31 PM, Dan Bode wrote: > On Tue, May 11, 2010 at 3:27 PM, Nigel Kersten wrote: > >> On Tue, May 11, 2010 at 3:19 PM, R.I.Pienaar wrote: >> > >> > - "Brian Gallew" wrote: >> > >> >> in nodes and have them propagate to their children, then I submit that >> >> nodes are so fundamentally broken as to make node inheritance >> >> completely useless, in which case node inheritance should be pulled. >> > >> > that sums it up well. >> >> ++ >> >> I haven't even told my users that nodes can do inheritance, as I >> haven't yet come across any reason to do so. >> > > you guys don't use an external node classifier? Is there a reason you > prefer to declare nodes? > > >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups "Puppet Users" group. >> > To post to this group, send email to puppet-us...@googlegroups.com. >> > To unsubscribe from this group, send email to >> puppet-users+unsubscr...@googlegroups.com >> . >> > For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> > >> > >> >> >> >> -- >> nigel >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To post to this group, send email to puppet-us...@googlegroups.com. >> To unsubscribe from this group, send email to >> puppet-users+unsubscr...@googlegroups.com >> . >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Have I found a bug with variables in nodes?
On Tue, May 11, 2010 at 3:27 PM, Nigel Kersten wrote: > On Tue, May 11, 2010 at 3:19 PM, R.I.Pienaar wrote: > > > > - "Brian Gallew" wrote: > > > >> in nodes and have them propagate to their children, then I submit that > >> nodes are so fundamentally broken as to make node inheritance > >> completely useless, in which case node inheritance should be pulled. > > > > that sums it up well. > > ++ > > I haven't even told my users that nodes can do inheritance, as I > haven't yet come across any reason to do so. > you guys don't use an external node classifier? Is there a reason you prefer to declare nodes? > > > > -- > > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > > To post to this group, send email to puppet-us...@googlegroups.com. > > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com > . > > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > > > > > > > -- > nigel > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Have I found a bug with variables in nodes?
On Tue, May 11, 2010 at 3:19 PM, R.I.Pienaar wrote: > > - "Brian Gallew" wrote: > >> in nodes and have them propagate to their children, then I submit that >> nodes are so fundamentally broken as to make node inheritance >> completely useless, in which case node inheritance should be pulled. > > that sums it up well. ++ I haven't even told my users that nodes can do inheritance, as I haven't yet come across any reason to do so. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- nigel -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Have I found a bug with variables in nodes?
- "Brian Gallew" wrote: > in nodes and have them propagate to their children, then I submit that > nodes are so fundamentally broken as to make node inheritance > completely useless, in which case node inheritance should be pulled. that sums it up well. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] master on Debian client on SLES 10.2 question....
0.24 puppetmaster don't work with 0.25 puppet client. Upgrade your puppetmaster to 0.25.4 (and facter to 1.5.7). You can use ubuntu "lucid" packages. Benoit Le 11/05/2010 22:40, FAZANG a écrit : On my puppet master i have installed ruby1.8 1.8.7.72-3lenny1 puppetmaster0.24.5-3 facter 1.5.1-0.1 On my SLES10.2 client i have installed ruby-1.8.4-17.16 from the SDK DVD i got off novell site puppet-0.25.4-4.1 RPM facter-1.5.7-1.1 RPM Background: I already had puppetmaster and puppet going on 2 debian servers now i am trying to get a Debian master and SLES client to work. The first problem i had was on SLES running command puppetd --server puppetmaster.uits.uconn.edu --test Apparently it does not send the .pem file it creates to the puppetmaster server. I sftp'd the .pem file into "/var/lib/puppet/ssl/ca/requests" on the master, then "puppetca -l" and "puppetca -s hostname" worked I also had to change the first line in /usr/sbin/puppetd first line to be "#!/usr/bin/ruby" was "/usr/bin/env ruby" NOW rcpuppet actually WORKS !!! Reason I'm posting is i am trying the simple example with SUDO and nothing happens so i was wondering if my "hacked" install could be part of the problem ? BTW the SuSe firewall is off I am allowing ALL traffic to and from master and client in network firewall tcpdump show packets going accross the wire from both machines any suggestions on how to turn up logging to test the SUDO example would be great too...? -ALF -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] master on Debian client on SLES 10.2 question....
0.24 puppetmaster don't work with 0.25 puppet client. Upgrade your puppetmaster to 0.25.4 (and facter to 1.5.7). You can use ubuntu "lucid" packages. Benoit Le 11/05/2010 22:40, FAZANG a écrit : On my puppet master i have installed ruby1.8 1.8.7.72-3lenny1 puppetmaster0.24.5-3 facter 1.5.1-0.1 On my SLES10.2 client i have installed ruby-1.8.4-17.16 from the SDK DVD i got off novell site puppet-0.25.4-4.1 RPM facter-1.5.7-1.1 RPM Background: I already had puppetmaster and puppet going on 2 debian servers now i am trying to get a Debian master and SLES client to work. The first problem i had was on SLES running command puppetd --server puppetmaster.uits.uconn.edu --test Apparently it does not send the .pem file it creates to the puppetmaster server. I sftp'd the .pem file into "/var/lib/puppet/ssl/ca/requests" on the master, then "puppetca -l" and "puppetca -s hostname" worked I also had to change the first line in /usr/sbin/puppetd first line to be "#!/usr/bin/ruby" was "/usr/bin/env ruby" NOW rcpuppet actually WORKS !!! Reason I'm posting is i am trying the simple example with SUDO and nothing happens so i was wondering if my "hacked" install could be part of the problem ? BTW the SuSe firewall is off I am allowing ALL traffic to and from master and client in network firewall tcpdump show packets going accross the wire from both machines any suggestions on how to turn up logging to test the SUDO example would be great too...? -ALF -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] master on Debian client on SLES 10.2 question....
On my puppet master i have installed ruby1.8 1.8.7.72-3lenny1 puppetmaster0.24.5-3 facter 1.5.1-0.1 On my SLES10.2 client i have installed ruby-1.8.4-17.16 from the SDK DVD i got off novell site puppet-0.25.4-4.1 RPM facter-1.5.7-1.1 RPM Background: I already had puppetmaster and puppet going on 2 debian servers now i am trying to get a Debian master and SLES client to work. The first problem i had was on SLES running command puppetd --server puppetmaster.uits.uconn.edu --test Apparently it does not send the .pem file it creates to the puppetmaster server. I sftp'd the .pem file into "/var/lib/puppet/ssl/ca/requests" on the master, then "puppetca -l" and "puppetca -s hostname" worked I also had to change the first line in /usr/sbin/puppetd first line to be "#!/usr/bin/ruby" was "/usr/bin/env ruby" NOW rcpuppet actually WORKS !!! Reason I'm posting is i am trying the simple example with SUDO and nothing happens so i was wondering if my "hacked" install could be part of the problem ? BTW the SuSe firewall is off I am allowing ALL traffic to and from master and client in network firewall tcpdump show packets going accross the wire from both machines any suggestions on how to turn up logging to test the SUDO example would be great too...? -ALF -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Provisioning VM in Xen via Puppet - Howto??
Dear All, I've finally managed to get xen installed on a remote system via puppet http://puppetnewbie.blogspot.com/2010/05/installing-xen-instance.html I was about to create my test machines manually, when it occurred to me, that I should be doing this via puppet. Hence my question in the subject. I was given some advice on the irc channel, but it didn't really sink in very much. If anyone has any ideas, please feel free to send me a note, I'll be working on this privately, and post my findings and ideas, back to the list. The way I have installed xen is noted in my blog if you would like to reference it. Thank you The Puppet Apprentice :- http://puppetnewbie.blogspot.com/ Follow me on twitter:- http://twitter.com/mritguru Puppet #tag on twitter :- #puppet IRC :- itguru ON irc.freenode.org (feel free to say hi!) -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Have I found a bug with variables in nodes?
Actually, the case I'm demonstrating is NOT covered in that FAQ. The nodes
*only* set variables. No includes happen until the final, selective node
(in this case "pslave1").If you cannot set variables in nodes and have
them propagate to their children, then I submit that nodes are so
fundamentally broken as to make node inheritance completely useless, in
which case node inheritance should be pulled.
On Tue, May 11, 2010 at 7:58 AM, Joe McDonagh
wrote:
> On 05/11/2010 02:11 AM, Brian Gallew wrote:
>
> (vastly trimmed code)
> *manifests/site.pp:*
> import "base"
>
> *module/base/manifests/init.pp*:
> import "baselines/*.pp"
> import "infrastructures/*.pp"
> import "nodes.pp"
>
> *nodes.pp:
> *node 'pslave1' inherits rnc {
> notice($my_puppet_master)
> }
>
>
> *infrastructures/geographical.pp:*
> node rnc inherits basenode {
> $my_puppet_server = "puppetmaster"
> }
>
>
> And after all the, the notice emitted is empty. My understanding is that
> node inheritance should bring "$my_puppet_master" into the scope of node
> pslave1, so the notice should ahve the right value. I'm reasonably sure
> this worked correctly under Puppet 0.24.mumble, but the new 0.25.4 instance
> I'm working is seems to behave differently. Should I file a bug report on
> this?
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
> This never worked, check out
> http://projects.puppetlabs.com/projects/puppet/wiki/Frequently_Asked_Questionsin
> the Common Misconceptions area.
>
> --
> Joe McDonagh
> AIM: YoosingYoonickz
> IRC: joe-mac on freenode
> "When the going gets weird, the weird turn pro."
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Disabling exec type output
All,
How can I stop the "returns successfully" messages from the exec {}
type unless their is a failure? Don't really want to see it. Using
logoutput => on_failure with exec doesn't seem to work (as this person
says here
http://unimpressed.org/post/93835992/disabling-puppets-executed-successfully-emails).
I also tried that however, with:
exec {
"dummy-passwd-${name}":
command => "cat /etc/passwd | grep \"^${name}\" >
/var/sftp/chroot/${name}/etc/passwd",
onlyif => "test /var/sftp/chroot/${name}/etc",
logoutput => on_failure,
tag => bitbucket;
}
Not knowing what tagmail.conf is all about since I can't find it
documented anywhere, I tried putting a tagmail.conf in /etc/puppet on
the client with:
all, !bitbucket: myem...@somewhere
and no effect still.
Doug
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] RE: Setting up a Xen instance - SOLVED
I decided to simplify every that I was doing. I noticed that I had begun
to overthink things, and I decided that KISS, is still the best way to
go.
This has turned out to be something like this;
***
File xenmaster.testdomain.com.pp
node xenmaster.testdomain.com {
include xen
}
Where xen has been defined as a class in
File testdomain.classes.pp
class xen {
package { xen: ensure => installed }
service { "xen":
ensure => running,
require => Package["xen"],
}
***
I am pretty pleased with the outcome, even though it looks so basic, I
can now roll out xen to any box under my command, with this entry,
"include xen" -- Seeing as I use virt-manager, to manage my VM's under
xen, I have no need to do automated provisioning, yet. I have the class
I can include/inherit in another class to do automatic provisioning.
More info about what I'm doing realating to this post is available on my
blog, and those of your on twitter, join the movement! Info in
signature.
The Puppet Apprentice :- http://puppetnewbie.blogspot.com/
Follow me on twitter:- http://twitter.com/mritguru
Puppet #tag on twitter :- #puppet
IRC :- itguru ON irc.freenode.org (feel free
to say hi!)
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Have I found a bug with variables in nodes?
On 05/11/2010 02:11 AM, Brian Gallew wrote:
(vastly trimmed code)
/manifests/site.pp:/
import "base"
/module/base/manifests/init.pp/:
import "baselines/*.pp"
import "infrastructures/*.pp"
import "nodes.pp"
/nodes.pp:
/node 'pslave1' inherits rnc {
notice($my_puppet_master)
}
/infrastructures/geographical.pp:/
node rnc inherits basenode {
$my_puppet_server = "puppetmaster"
}
And after all the, the notice emitted is empty. My understanding is
that node inheritance should bring "$my_puppet_master" into the scope
of node pslave1, so the notice should ahve the right value. I'm
reasonably sure this worked correctly under Puppet 0.24.mumble, but
the new 0.25.4 instance I'm working is seems to behave differently.
Should I file a bug report on this?
--
You received this message because you are subscribed to the Google
Groups "Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
This never worked, check out
http://projects.puppetlabs.com/projects/puppet/wiki/Frequently_Asked_Questions
in the Common Misconceptions area.
--
Joe McDonagh
AIM: YoosingYoonickz
IRC: joe-mac on freenode
"When the going gets weird, the weird turn pro."
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Breaking down variables (and setting new ones) from within a manifest using regular expressions
I use this to create two variables that I can use in a cron type: # The variable boot_time is set on the client in the /etc/init.d/ puppet-at-boot script # as a FACTER environmental variable i.e. export FACTER_BOOT_TIME=`date '+%H:%M'` $boot_hour = regsubst($boot_time,'^([0-9]+)[:]([0-9]+)','\1') $boot_minute = regsubst($boot_time,'^([0-9]+)[:]([0-9]+)','\2') I think you would have to create the variables first, then use the variables in the if/else statements. Ed On May 7, 9:05 am, Ryan wrote: > Hello all! > > I'm hoping for your help on what I admit is a weird and uncommon > problem. > > I'm working on a module that (among other things) creates a series of > home folders. The format of the home folders looks something like > this /filesys/home/#/letter/userid where # is a number between 0-15, > letter is the first letter of the userid. > > Anyhow, I'm inserting a variable into the manifest something like > this: $folders = ["/filesys/", "/filesys/home", "/filesys/home/0", "/ > filesys/home/0/x/xyz123", /filesys/home/1/a/abc123"] and etc > > My problem is, I want to take that master variable and break it down > so puppet can do different things to different pieces. For example, I > was looking at making an if/else statement to take a regular > expression that would strip out a userid and make that the variable > puppet uses for the owner/group on each of the userid directories. > Else, the owner/group would be sys or whatever else. > > I'm thinking of other stuff too, but my basic question is, does puppet > support using regular expressions in if/else statements like this or > am I really trying to get too crazy? > > Thanks in advance for bearing with me! > > --Ryan > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] multiple OS support conventions?
On 05/11/2010 05:45 AM, Dick Davies wrote: I've been using Puppet very happily for the last 6 months or so to manage our CentOS and RHEL servers. Over the summer I want to knock things up a notch, and part of that is going to be supporting a wider range of OSes. First on the hit list are likely to be Solaris 10 and Suse (SLES). I know a lot of people do support multiple OSes, just wondered what sort of approach you've found works best? Of course at the end of the day it's a question of 'case $operatingsystem' statements, but I wondered whether you create a dedicated 'os' module, or whether you structure each module in a standard way, or something else. Thanks for any pointers. I forgot to add- the splitting inside init.pp allows for generic includes- like you just say include common, and it gets the os-specific class such as common::solaris through black magic. -- Joe McDonagh AIM: YoosingYoonickz IRC: joe-mac on freenode "When the going gets weird, the weird turn pro." -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] multiple OS support conventions?
On 05/11/2010 05:45 AM, Dick Davies wrote:
I've been using Puppet very happily for the last 6 months
or so to manage our CentOS and RHEL servers.
Over the summer I want to knock things up a notch,
and part of that is going to be supporting a wider range of OSes.
First on the hit list are likely to be Solaris 10 and Suse (SLES).
I know a lot of people do support multiple OSes, just wondered
what sort of approach you've found works best?
Of course at the end of the day it's a question of 'case $operatingsystem'
statements, but I wondered whether you create a dedicated 'os' module,
or whether you structure each module in a standard way, or something
else.
Thanks for any pointers.
Generally if the changes are really profound, I will split a module into
os-specific classes inside init.pp using an operatingsystem case
statement. If the changes are small I will use selectors in the
resources. I also set a bunch of resource defaults in site.pp to make
multi-os modules more readable. An example is OpenBSD; there is no root
group, so I do this:
File {
backup => "main",
ensure => "present",
group => $kernel ? {
Linux => "root",
OpenBSD => "wheel"
},
owner => "root"
}
--
Joe McDonagh
AIM: YoosingYoonickz
IRC: joe-mac on freenode
"When the going gets weird, the weird turn pro."
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: puppet for switches
I have a dozen use cases for some sort of Puppet 'proxy' client that could supply facts and act as a provider for (e.g. load balancers, rackspace cloud, web services, embedded devices) where running Puppet locally was not practical. Does anyone know of such a thing? On Thu, May 6, 2010 at 4:35 PM, Michael DeHaan wrote: > Just to add a similar 'this would be neat' comment to it, I know > several of the Cobbler guys have talked about wanting to see a > "libswitch" kind of similar to a libvirt. > > If we had such a thing, making a Puppet type for it seems quite logical. > > This sounds like it would be along similar lines. > > Next steps: X-10 home automation hooks :) > > --Michael > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] multiple OS support conventions?
I've been using Puppet very happily for the last 6 months or so to manage our CentOS and RHEL servers. Over the summer I want to knock things up a notch , and part of that is going to be supporting a wider range of OSes. First on the hit list are likely to be Solaris 10 and Suse (SLES). I know a lot of people do support multiple OSes, just wondered what sort of approach you've found works best? Of course at the end of the day it's a question of 'case $operatingsystem' statements, but I wondered whether you create a dedicated 'os' module, or whether you structure each module in a standard way, or something else. Thanks for any pointers. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
