Re: [Puppet Users] Renaming puppet binary to use with two puppet agent instances
This isn't about two masters, but two agents. The reason being is permissions.. sudo, ldap, nfs, ntp, etc is managed by a separate group. Everything else is up to us. We do not have access to that master and they are using 2.7, while we would like to use the 3.x version. It's not the best situation. Because our modules are written in 3.x syntax, we cannot share modules because we use the newer features in 3.x vs 2.7. The installation/run works fine and coexist with absolute path, as recommended by R.I, just not with the renamed short command. I'm just curious about the shortcut, because normally I would symlink to the binary and it would be fine, but in this scenario when I symlink it ends up using the command as an ARGV 0 value. -John. On Tuesday, July 9, 2013 5:26:56 PM UTC-7, Pete wrote: I think the general consensus on multiple masters managing a node is don't do it. I personally can't see a reason why this sort of thing is even necessary. Why do you need two separate masters managing the same node? What specific reason do you need to split the resource management between two masters? Can't you achieve the same effect with modules? On 10 July 2013 03:33, John V. jvil...@gmail.com javascript: wrote: 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 for two separate teams for 2.7 and 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 Error: Unknown Puppet subcommand 'puppet3' See 'puppet help' for help on available puppet subcommands 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? Thank you. -John -- 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 javascript:. To post to this group, send email to puppet...@googlegroups.comjavascript:. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Renaming puppet binary to use with two puppet agent instances
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 for two separate teams for 2.7 and 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 Error: Unknown Puppet subcommand 'puppet3' See 'puppet help' for help on available puppet subcommands 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? Thank you. -John -- 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+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Multiple Puppet agents on one node?
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. On Thursday, February 21, 2013 2:00:24 AM UTC-8, R.I. Pienaar wrote: - Original Message - From: Michael Hüttermann mic...@huettermann.net javascript: To: puppet...@googlegroups.com javascript: 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 -- 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+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
