[Puppet Users] Re: Managing producton & backup datacenter
> > But for more sophisticated puppet setups - what are your ways to determine > > which environment you are in. > > I wrote a custom fact, location, that embeds all the logic in a tiny bit of > custom Ruby. (In fact, it just grabs the hostname, domain, and IP address, > then uses a tiny bit of logic to select between them.) Same sort of solution here. I made a location fact that maps primary ipaddress subnet to a descriptive location string. >From there I went a different route than the extlookup() + case method. I ended up using exported resources with 'tag => $location' and '<<| tag = $location |>>' on the client side. If a resource doesn't have a native Type I used the same technique with the concat module. -- 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: mcollective scalability
> 2000 nodes certainly is within my goals with the design, that said there has > not been such a big deploy. We've got 500+ nodes on mcollective currently. Nothing special as far as setup, a few of the contrib agents and few more in house agents. Nodes are primarily split between two buildings connected by gigE. 95% response from mc-ping is 300ms, average 200ms. I'm expecting at least 1000 nodes in three geo areas by the end of the year. My todo list for this summer has federating some more activemqs into the setup. > You'd probably want a few activemq instances in a cluster in such a setup, > though I've heard of much larger client counts on activemq. The above all runs off of a single activemq server currently. Quad core xeon w/ 3gb ram sitting at 99% idle. -- 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] node inheritance, variable scope, and pain.
Russ Allbery writes:
> Daniel Pittman writes:
>
>> It was, until yesterday, my naive expectation that this would work:
>
>> node default{ include broken }
>> node "krosp" inherits "default" { $value = "not " }
>> class broken{ notice("This is ${value}broken") }
>
>> Specifically, I expected this would output 'This is not broken', but instead
>> we get the counter-intuitive and *very* annoying 'This is broken'.
[...]
> Our rule of thumb is that any time one is tempted to set variables and use
> those values in included and inherited classes, that's a red flag that you
> actually wanted a define instead. If you had instead written this as:
>
> node default { broken { "message": value => "" } }
> node "krosp" inherits "default" { Broken["message"] { value => "not " } }
> define broken($value) { notice("This is ${value}broken") }
>
> I'm pretty sure you'd get the behavior you expected.
I do, indeed. I don't much like it, as it feels the same sort of work-around
as turning "default" into a class — especially because I don't want a
define, I want a class with a tiny bit of configuration.[1]
Still, it is probably less bad than the alternatives, and I do agree that
using a define (or, next release, a parametrized class) is a better solution
than action-at-a-distance variables.
Daniel
Footnotes:
[1] In this case, one bit worth of configuration, dammit.
--
✣ 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] node inheritance, variable scope, and pain.
Daniel Pittman writes:
> It was, until yesterday, my naive expectation that this would work:
> node default{ include broken }
> node "krosp" inherits "default" { $value = "not " }
> class broken{ notice("This is ${value}broken") }
> Specifically, I expected this would output 'This is not broken', but instead
> we get the counter-intuitive and *very* annoying 'This is broken'.
> As far as I can tell this is because puppet treats $value as out of scope to
> the classes included from default: the order of processing is:
> - node 'default', or any other inherited node.
>- any classes included are processed.
> - node $hostname is processed.
> This means our practice of included universal features into the default
> node, then inheriting that into other nodes, also makes it impossible
> for us to do things like configure features of those universal classes.
> I really do *NOT* want to go down the path of having to repeat the same
> set of classes in every node; that invites disaster, by forcing me to
> repeat myself.
Our rule of thumb is that any time one is tempted to set variables and use
those values in included and inherited classes, that's a red flag that you
actually wanted a define instead. If you had instead written this as:
node default { broken { "message": value => "" } }
node "krosp" inherits "default" { Broken["message"] { value => "not " } }
define broken($value) { notice("This is ${value}broken") }
I'm pretty sure you'd get the behavior you expected.
--
Russ Allbery (r...@stanford.edu)
[Puppet Users] node inheritance, variable scope, and pain.
G'day.
It was, until yesterday, my naive expectation that this would work:
node default{ include broken }
node "krosp" inherits "default" { $value = "not " }
class broken{ notice("This is ${value}broken") }
Specifically, I expected this would output 'This is not broken', but instead
we get the counter-intuitive and *very* annoying 'This is broken'.
As far as I can tell this is because puppet treats $value as out of scope to
the classes included from default: the order of processing is:
- node 'default', or any other inherited node.
- any classes included are processed.
- node $hostname is processed.
This means our practice of included universal features into the default node,
then inheriting that into other nodes, also makes it impossible for us to do
things like configure features of those universal classes.
I really do *NOT* want to go down the path of having to repeat the same set of
classes in every node; that invites disaster, by forcing me to repeat myself.
I suspect we will turn 'node default' into 'class default', then include that
rather than inheriting that, since that does fix the scope issue.
Anyway, my two questions:
Is this actually the correct behaviour as of 0.25.4?
Is this every likely to change to something that doesn't suck?
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] Re: puppet for switches
seph wrote: Geoff Crompton writes: This might be a crazy idea, but it just popped into my head, and I wanted to know if it's possible. Perhaps not possible right now, but possible in a theoretical sense. Is it possible that puppet could be modified to be used to manage switches that have a command line based interface? I think there's a lot of value in configuration management system for network stuff. Though I don't think puppet is a good fit. Puppet has lots of types that don't really make sense in that context. http://www.netomata.com is the most recent thing I've seen in this space. I'm not sure how far along they are. seph I posted a similar question on sage-au just after my puppet post. Someone pointed me to http://www.netomata.com. While it looks like it has a little way to go, it looks so good that it deflated my enthusiasm for using puppet for this. Naturally TMTOWTDI. -- +-Geoff Crompton +--Debian System Administrator +---Trinity College -- 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 Dashboard packages updated for V1.0 release
On 5 May 2010, at 5:26 PM, James Turnbull wrote: I've fixed it now and added some further fixes to the spec file provided by Todd Zullinger. Thanks, both. -- Ian Ward Comfort Systems Team Lead, Academic Computing Services, Stanford University -- 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 Dashboard packages updated for V1.0 release
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/05/10 9:49 AM, Ian Ward Comfort wrote:
> On 3 May 2010, at 3:47 AM, James Turnbull wrote:
>> On 3/05/10 8:19 PM, Kenneth Holter wrote:
>>> I downloaded the "puppet-dashboard-1.0.0-2.noarch.rpm" and
>>> installed it, and found that the init script got placed in the
>>> wrong directory ("/etc/rc.d/init.d}").
>
>> I've fixed the problem and pushed a new package.
>
> Thanks a lot for setting up this repository -- it should really reduce
> the manual effort for keeping up with Dashboard versions to almost
> nothing.
>
> It looks like the latest RPM isn't signed, though. I wonder if you
> could fix that?
>
> $ curl -sLO \
>http://yum.puppetlabs.com/base/puppet-dashboard-1.0.0-3.noarch.rpm
> &&
>rpm -qip puppet-dashboard-1.0.0-3.noarch.rpm | grep Signature
>
Weird. I was prompted for a passphrase. Oh well. I've fixed it now
and added some further fixes to the spec file provided by Todd
Zullinger.
Thanks Todd!
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+IMoCFa/lDkFHAyAQLw1Af/Yi++15s4Mxs6CnsONkqxVHz03hqMBLEU
pVCQ94FIxa5XOn1XayxZQ6CRb0pjZM5Qnk3gAH61hvdDZPtWomsOuDAC+CzzmJVc
yI/cJofv5wnGJn2dieVESElWJ1ZiADyyTB6uyEF0KTlGrrJX8wDTeojZzFdbJS3A
u4mPYEAE/f6MXTTKFZ1PvbxPVdYwQeu423Uv8iufAwjHbK7RdYQ12OHXfzp0KZS5
EnzOexut5yCuz284ZtLSHbvLit6tzc4P/wURy64bYddjKHaD5GvcYuPv9FOPlM63
INQ7Mr+/BGCGPOABTOt7NMTJTlB84akr08C2XTxnf6nrV82+WPSeEg==
=u032
-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 Dashboard packages updated for V1.0 release
On 3 May 2010, at 3:47 AM, James Turnbull wrote:
On 3/05/10 8:19 PM, Kenneth Holter wrote:
I downloaded the "puppet-dashboard-1.0.0-2.noarch.rpm" and
installed it, and found that the init script got placed in the
wrong directory ("/etc/rc.d/init.d}").
I've fixed the problem and pushed a new package.
Thanks a lot for setting up this repository -- it should really reduce
the manual effort for keeping up with Dashboard versions to almost
nothing.
It looks like the latest RPM isn't signed, though. I wonder if you
could fix that?
$ curl -sLO \
http://yum.puppetlabs.com/base/puppet-dashboard-1.0.0-3.noarch.rpm
&&
rpm -qip puppet-dashboard-1.0.0-3.noarch.rpm | grep Signature
--
Ian Ward Comfort
Systems Team Lead, Academic Computing Services, Stanford University
--
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-dev] GSoC - Introducing myself
On Wed, May 5, 2010 at 3:20 PM, William Van Hevelingen wrote: > Hello Everybody, > > I'm William and I am the other Google Summer of Code 2010 student. I will be > working on a Puppet type to manage advanced provisioning and configuration > of network interfaces (initially on various Linux distributions). I'm really > excited to start working on this project and I would like to thank Michael > DeHaan for being a great mentor so far. > > I'm on freenode in #puppet as blkperl if you want to say hello or offer some > tips :) and email works too. Great to see you both! Both projects look really useful. > > Regards > -- > William Van Hevelingen > Computer Science Major > Portland State University > w...@cs.pdx.edu > http://blkperl.blogspot.com/ > > > -- > 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.
[Puppet Users] Re: [Puppet-dev] GSoC - Introducing myself
Hello Everybody, I'm William and I am the other Google Summer of Code 2010 student. I will be working on a Puppet type to manage advanced provisioning and configuration of network interfaces (initially on various Linux distributions). I'm really excited to start working on this project and I would like to thank Michael DeHaan for being a great mentor so far. I'm on freenode in #puppet as blkperl if you want to say hello or offer some tips :) and email works too. Regards -- William Van Hevelingen Computer Science Major Portland State University w...@cs.pdx.edu http://blkperl.blogspot.com/ -- 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] GSoC - Introducing myself
Hello All! My name is Carla, and I am one of Google Summer of Code 2010 students selected to work on Puppet this summer. My proposal is to develop types for management of virtual machines, initially focus on Xen and KVM. You can contact me at freenode as carlasouza or by e-mail. Any suggestions is welcome. :) --Carla -- 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] determine whether host responds to an IP address
Hey folks, I'm looking for a best practice for determining whether a host has a specific IP address configured on it, in order to make puppet configuration decisions. I know there are a list of facts for each interface with an associated IP address, but am trying to determine whether ANY interface matches a corresponding IP. I haven't found a good way to cleanly iterate through multiple facts. Does anyone have a good way for doing this? Should I be using a custom type? Thanks, Casey -- - Casey Feskens System Administrator/Network Svcs. Consultant Willamette Integrated Technology Services Willamette University, Salem, OR - -- 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] List of available variables for use in templates
When writing an ERB template, I know that I can define variables in my
nodes and classes, and that the facter variables for the node are available.
I'd like to know if there are any other predefined puppet variables
available. In specific, I'd like the node's name in the node definition.
node "foobar" {
include this
include that
}
I'd like to get "foobar". In my case, this is probably NOT the facter
variable fqdn or hostname.
I can't find this documented anywhere.
Assistance?
Thanks,
Ed Greenberg
--
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: Puppet with cloud instances
Sounds like using the certname configuration variable is what I need, I expect to have users terminating and launching new instances all the time, with or without notice, so something that doesn't require my attention at each launch is critical. I'll search for how to customize the cert CN, but if you have a suggestion on where to look, that would be appreciated as well. Thank you for the help!!! On May 5, 10:31 am, Jeff McCune wrote: > Hi, > > You could clean the certificate on the puppetmaster CA using puppetca > --clean debian.example.org prior to connecting the rebuilt server > again. > > If you have a short lifecycle and rapid turnover of the same hostname, > you may benefit from using the certname configuration variable and > using some other fact besides the fqdn for the certificate common name > field. Large sites with high turnover often set the cert CN to a uuid > or something similar. > > -- > Jeff McCune > > > > On Wed, May 5, 2010 at 11:51 AM, Murteas wrote: > > Hello all, > > > Recently I was asked to start using Puppet as part of our Eucalyptus > > powered internal cloud. I have been able to set up Puppet and a > > puppet master on various instances, but what I am running into, is > > that several of the instances have the same hostname or no hostname > > when they are first launched, so of course when they try to get a cert > > from puppetmaster I get an error saying that I can't overwrite the > > existing certificate with the new one. > > > My question is: > > > If I have one instance launched in a cloud with a hostname of > > debian.example.org and then that instance is terminated, and then I > > bring up an identical instance but this one has a new ip address, how > > can I get a cert for this new instance? Obviously I can do a clean > > on the puppetmaster, but I need to automate this process somehow, as > > this could happen constantly with our customers launching new > > instances or identical instances. > > > Any thoughts? > > > -- > > 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 > 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] Puppet order
On Wed, May 5, 2010 at 11:50 AM, Roshan Punnoose wrote: [snip > Is there currently a way to ensure that either the directories exist first > in the function file copy, or, better yet, to specify an order to the > function calls? Roshan, This topic is something that separates puppet from many other tools. With puppet, resources and their relationships are declared rather than a procedure of action. This means unless explicitly stated, resources are managed in an arbitrary order. Please take a look at the before, after, require, and notify parameters. These parameters are available with every resource type and create explicit ordering among the resources you manage. The language tutorial covers this, located at: http://docs.puppetlabs.com/guides/language_tutorial.html Hope this helps, -- Jeff McCune -- 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 with cloud instances
Hi, You could clean the certificate on the puppetmaster CA using puppetca --clean debian.example.org prior to connecting the rebuilt server again. If you have a short lifecycle and rapid turnover of the same hostname, you may benefit from using the certname configuration variable and using some other fact besides the fqdn for the certificate common name field. Large sites with high turnover often set the cert CN to a uuid or something similar. -- Jeff McCune On Wed, May 5, 2010 at 11:51 AM, Murteas wrote: > Hello all, > > Recently I was asked to start using Puppet as part of our Eucalyptus > powered internal cloud. I have been able to set up Puppet and a > puppet master on various instances, but what I am running into, is > that several of the instances have the same hostname or no hostname > when they are first launched, so of course when they try to get a cert > from puppetmaster I get an error saying that I can't overwrite the > existing certificate with the new one. > > My question is: > > If I have one instance launched in a cloud with a hostname of > debian.example.org and then that instance is terminated, and then I > bring up an identical instance but this one has a new ip address, how > can I get a cert for this new instance? Obviously I can do a clean > on the puppetmaster, but I need to automate this process somehow, as > this could happen constantly with our customers launching new > instances or identical instances. > > Any thoughts? > > -- > 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] Puppet with cloud instances
Hello all, Recently I was asked to start using Puppet as part of our Eucalyptus powered internal cloud. I have been able to set up Puppet and a puppet master on various instances, but what I am running into, is that several of the instances have the same hostname or no hostname when they are first launched, so of course when they try to get a cert from puppetmaster I get an error saying that I can't overwrite the existing certificate with the new one. My question is: If I have one instance launched in a cloud with a hostname of debian.example.org and then that instance is terminated, and then I bring up an identical instance but this one has a new ip address, how can I get a cert for this new instance? Obviously I can do a clean on the puppetmaster, but I need to automate this process somehow, as this could happen constantly with our customers launching new instances or identical instances. Any thoughts? -- 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 for switches
On 5 May 2010 16:54, Gary Law wrote: > > Before reinventing the wheel in terms of grabbing and storing > switch/router/firewall configs, take a look at this: > > http://www.shrubbery.net/rancid/ And http://trac.nocproject.org/trac/ -- 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: puppet for switches
Geoff Crompton writes: > This might be a crazy idea, but it just popped into my head, and I > wanted to know if it's possible. Perhaps not possible right now, but > possible in a theoretical sense. > > Is it possible that puppet could be modified to be used to manage > switches that have a command line based interface? I think there's a lot of value in configuration management system for network stuff. Though I don't think puppet is a good fit. Puppet has lots of types that don't really make sense in that context. http://www.netomata.com is the most recent thing I've seen in this space. I'm not sure how far along they are. seph -- 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 for switches
- "Geoff Crompton" wrote: > Is it possible that puppet could be modified to be used to manage > switches that have a command line based interface? Before reinventing the wheel in terms of grabbing and storing switch/router/firewall configs, take a look at this: http://www.shrubbery.net/rancid/ HTH Gary -- Gary Law -- 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 order
Hi,
I have a node definition that looks like:
node default {
include mymod
mymod::func1()... // copy a file
mymod::func2()... // copy a file
}
The module ,mymod, defines that a certain set of directories get copied
over, and the functions define files that need to go into those directories.
I have noticed that sometimes the func1 and/or func2 occur before those
directories are copied and fail because the directories don't exist.
Is there currently a way to ensure that either the directories exist first
in the function file copy, or, better yet, to specify an order to the
function calls?
Roshan
--
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 for switches
- "Geoff Crompton" wrote:
> This might be a crazy idea, but it just popped into my head, and I
> wanted to know if it's possible. Perhaps not possible right now, but
> possible in a theoretical sense.
>
> Is it possible that puppet could be modified to be used to manage
> switches that have a command line based interface?
>
> When I manage our Allied Telesis switches (which have a CLI similar
> to
> cisco IOS) I wonder if I could control it via a puppet-like node:
>
> node 'switch-101' {
>vlan { storage:
> id => 1234,
> untagged_ports => "3/e1, 4/e3",
> tagged_ports => "1/e1-2/e48",
>}
>include gvrp
>include stp::rstp
>stp::portfast { "1/e1-e48,2/e1-48",3/e1-48": }
> }
>
>
> Now I know we probably can't get puppet to run on the switch, but we
> can
> get a host to ssh or telnet to the switch, and to download the
> current
> configuration of the switch.
there was a past thread on this, it's not perfect but might give you something
to think about
http://www.mail-archive.com/puppet-...@googlegroups.com/msg05169.html
--
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 for switches
That would be very cool indeed, manifests would get quite big though
in really large environments (think 100k end points). Juniper and
Cisco support would be great.
Sent from my iPhone
On May 5, 2010, at 4:15 AM, Nicolas Szalay wrote:
- "Geoff Crompton" a écrit :
| This might be a crazy idea, but it just popped into my head, and I
| wanted to know if it's possible. Perhaps not possible right now, but
| possible in a theoretical sense.
|
| Is it possible that puppet could be modified to be used to manage
| switches that have a command line based interface?
|
| When I manage our Allied Telesis switches (which have a CLI similar
| to
| cisco IOS) I wonder if I could control it via a puppet-like node:
|
| node 'switch-101' {
|vlan { storage:
| id => 1234,
| untagged_ports => "3/e1, 4/e3",
| tagged_ports => "1/e1-2/e48",
|}
|include gvrp
|include stp::rstp
|stp::portfast { "1/e1-e48,2/e1-48",3/e1-48": }
| }
|
|
| Now I know we probably can't get puppet to run on the switch, but we
| can
| get a host to ssh or telnet to the switch, and to download the
| current
| configuration of the switch.
Funny, Brice and I had talked about this a while ago :) Obviously
you could use a host as "proxy" to get facts and then decide what
hooks to run. I (re)wrote a little ruby lib [1] thinking about this,
still need some work btw
--
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 for switches
- "Geoff Crompton" a écrit :
| This might be a crazy idea, but it just popped into my head, and I
| wanted to know if it's possible. Perhaps not possible right now, but
| possible in a theoretical sense.
|
| Is it possible that puppet could be modified to be used to manage
| switches that have a command line based interface?
|
| When I manage our Allied Telesis switches (which have a CLI similar
| to
| cisco IOS) I wonder if I could control it via a puppet-like node:
|
| node 'switch-101' {
|vlan { storage:
| id => 1234,
| untagged_ports => "3/e1, 4/e3",
| tagged_ports => "1/e1-2/e48",
|}
|include gvrp
|include stp::rstp
|stp::portfast { "1/e1-e48,2/e1-48",3/e1-48": }
| }
|
|
| Now I know we probably can't get puppet to run on the switch, but we
| can
| get a host to ssh or telnet to the switch, and to download the
| current
| configuration of the switch.
Funny, Brice and I had talked about this a while ago :) Obviously you could use
a host as "proxy" to get facts and then decide what hooks to run. I (re)wrote a
little ruby lib [1] thinking about this, still need some work btw
--
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.
