Multiple Puppet agents on one node?

[Michael Hüttermann]

Hello,

can I run two different Puppet agents on one node listening to two different Masters?

Thank you for your help.

Best regards

Michael

[Dan White]

I will ask the obvious:

Why do you want to do this ?

“Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin & Hobbes)

---

From: "Michael Hüttermann" <mic...@huettermann.net>
To: puppet...@googlegroups.com
Sent: Wednesday, February 20, 2013 12:22:55 PM
Subject: [Puppet Users] Multiple Puppet agents on one node?

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To post to this group, send email to puppet...@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Michael Hüttermann]

I'm just curious if this is possible, technically.
Is it?

[Peter Brown]

On 21 February 2013 06:34, Michael Hüttermann <mic...@huettermann.net> wrote:

I'm just curious if this is possible, technically.
Is it?

It is theoretically possible but like I said last time it isn't a good idea at all.

[Michael Hüttermann]

thank you for your opinion.
I've somehow lost the last post, sorry for bothering you again with the same strange question.

[R.I.Pienaar]

----- Original Message -----
> From: "Michael Hüttermann" <mic...@huettermann.net>
> To: puppet...@googlegroups.com
> Sent: Thursday, February 21, 2013 9:37:35 AM
> Subject: Re: [Puppet Users] Multiple Puppet agents on one node?
>
> thank you for your opinion.
> I've somehow lost the last post, sorry for bothering you again with the
> same strange question.

It's easily done by just giving each agent their own libdir and config file.

In fact if you just ran puppet agent as non root it would use ~/.puppet as
its work dirs and it will just work.

of course you're pretty limited in what you can do then - only stuff non root
can do

[Peter Brown]

If you explain why you need to do this we may be able to provide a better solution that would work better than running two agents talking to two masters.

There are a lot of people here with a great deal of experience with this sort of thing.

Pete.

[Peter Brown]

Actually scratch the why and replace it with what you are trying to achieve.

[Jeffrey Watts]

Michael, I'll try and help.  I had a set of servers at my last employer where I had to run two separate agents from cron.  That particular team had been using Puppet to manage an application which was no longer being actively developed and was on life support.

Therefore, when I deployed Puppet across the entire company I set up those machines to have two separate agent runs with different Puppetmasters.  I ran two separate crons with separate names so the two Puppets wouldn't conflict.  I manually set the --server, --logdest, --vardir, and --ssldir directives (--ssldir may be extraneous if your local config is $vardir/ssl) on the cronjob's command line.  I had no issues running them separately, keep in mind though that it might get hairier if you try and run two different Puppet versions.  I never tried doing that.

Good luck, and I hope this helps.

Jeffrey.

Michael

--

[damian....@gmail.com]

I have recently half thought about whether this was possible (but haven't done it), and i'd be interested in some best practice for the following.

We have a sysadmins department who manage ~1500 nodes across a large organisation using PE. They are responsible for the OS build and management for the whole lot.  We also have a development department who are looking at Puppet to manage the bespoke apps and system app software.  However this department only have approx 200 nodes that covers the usual dev, test, and live environments for their area of responsibility.

The dev department like to have timely control of at least the dev and test environments (i.e. we cannot wait for the sysadmins dept to add new modules etc), but we are still reliant upon the sysadmins department to manage the OS.  Whilst the situation is not ideal, any changes to the status quo are firmly NOT going to happen.

We would also like to make use of MCollective to orchestrate some app deployments (stopping services in correct order, making puppet runs, actioning some custom stuff, then starting up the system in the correct order etc etc).

So far I haven't seen an easy way to allow devs to only be in control of their own stuff. I'm trying to convince the sysadmins team to allow us our own puppet master that they jointly administer so that the OS gets managed as well as the app stuff.  Currently it doesn't look like they are going to allow us to do that.

I am looking at doing something with module paths but are limited by $environment being used by the sysadmins for their purposes (i.e. the devs will have their own modulepath in which that can upload their modules at will but it will be limited to just one that covers all of dev, test, and live.  Ideally we'd like to be able to publish modules to our dev, then test, then live).

I'm also worried that with MCollective the devs could affect the whole estate rather than their area as i've not yet seen a way of restricting execution.

Anybody with any thoughts?

 

[John V.]

Hi, 

Sorry to revive this old thread, but I'm trying to do the same thing and running into two minor problems.. I would like to rename the puppet command to something like puppet3. We're running two versions while we're migrating from 2.7 to 3.x However, when I try to do a symlink I get the following error.

Error: Unknown Puppet subcommand 'puppet3'

See 'puppet help' for help on available puppet subcommands

ie 

puppet agent -t -> everything is normal

puppet3 agent -t -> calls puppet3 /opt/puppet3.2/bin/puppet

I do not have any problems with puppet colliding with puppet 2 but I'd like to use a shortcut vs using the /path/to/puppet3/bin/.puppet. Is there a way to do this? I looked at the command_line.rb but I hope it doesn't require too much hacking to get something like this to work. 

I would also want to run a daemon for the puppet3 version. 

Please advise. 

Thank you.