Re: [Puppet Users] Re: Installing puppet and using ruby from RVM.
On Friday, September 21, 2012 7:11:18 PM UTC-7, Jakov Sosic wrote: On 09/22/2012 03:21 AM, jdehnert wrote: I'm aware of the issues of installing software through source vs. pkg management systems. I should have mentioned that I've been in IT for over 20 years. Its just puppet and ruby that are new to me, but I'm learning fast. We are in agreement about sticking to one type of package management. It much easier now that it was back when I was installing SunOS 4.1.4 on Sun 3's and Sparc 2's and compiling X11 from source. If you were really aware, then you wouldn't do it... I haven't done anything yet, except appeal to the puppet community at large for some insight I've considered all of these. Does anyone know of a CentOS/RH repo that has the latest versions of Ruby available? I have done some searching, but not exhaustively so, for a repo with the most recent versions of Ruby, but no luck so far. The reason I want to use ruby-1.9.2-p320 on these test VM's is because in the production environment that these are mimicking the engineering folks are running that release, under RVM, and they want to avoid any installs of other versions to eliminate any chance of something getting pointed to an older version of Ruby accidentally. The dev and production environments will both point to Ruby under RVM. This is wrong approach. Try to figure out why is RHEL/CentOS and Suse Enterprise sticking to older version of ruby (or every other piece of software they distribute), and what are the benefits... Considering that the developers have been working on this for over a year, and they have their reasons for selecting RVM and Ruby 1.9.2, it's not my call. I'm here to bring as much consistency and reliability as I can to the systems that have been managed by the whims of the developers for quite some time. I've made a huge amount of progress by basically giving them them some nice, clean, secure production systems that they aren't allowed to manage. I have helped them get to the point where they can use Capistrano to deploy the application, and we have partitioned Neo4j and Mongodb onto their own separate systems. Now I'm working on deploying puppet to keep the systems consistent and allow me to do all that puppet can do to keep things in order. I was hoping someone might know some details about the rpm system that might allow me to tell it that ruby was installed without installing ruby, as with fake sendmail. Perhaps a lesser known tool that allows one to insert entries into the rpm database files. You are mangling with the system in a way it shouldn't be mangled with. Try to persuade your developers to use platform that is already used on production, and not vice versa. Well, I suppose everyone has a different mandate at different companies. My current gig is at yet another start up and the company is engineering driven. Given that I need to make sure that I don't do anything that steps on engineering. I'm not entirely under their thumb. I insisted on certain conditions before I took this job, and that has allowed me to replace token security with real security. Engineering and I have worked together very closely to help get them more compartmentalized to the application is now of a discrete unit, and not so much an electron cloud where they may have reached all over the OS. I give them a reliable server, and they agree to keep the application contained. If that doesn't go quite right, then take src.rpm from RedHat/CentOS, bump version to 1.9.x - or whatever do you want to use, drop in newer sources, fix patches - and rebuild the RPM - or try to backport latest feodra build: http://fedora.aau.at/linux/releases/17/Fedora/source/SRPMS/r/ruby-1.9.3.194-10.1.fc17.src.rpm but that could bring you back to trouble because that version probably won't be 100% identical to the one that your dev team uses (if they stick to sources). So we're back to square one - you *have to* convice your team to use Ruby from RPM package - either fedora backport or standard RHEL 1.8.x. Everything else _*will*_ bit you in the ass in the long run. That’s why I'm here asking questions. Its good to minimize all the future ass biting that one can, which is also why I'm testing on a pair of VM's to get puppet functional and worked out before it gets anywhere near a production system. -- Jakov Sosic www.srce.unizg.hr -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/OEPaTlAP2QIJ. To post to this group, send email to puppet-users@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] Installing puppet and using ruby from RVM.
On 22/09/2012, at 4:23 PM, jdehnert jdehn...@gmail.com wrote: On Friday, September 21, 2012 7:11:18 PM UTC-7, Jakov Sosic wrote: On 09/22/2012 03:21 AM, jdehnert wrote: I'm aware of the issues of installing software through source vs. pkg management systems. I should have mentioned that I've been in IT for over 20 years. Its just puppet and ruby that are new to me, but I'm learning fast. We are in agreement about sticking to one type of package management. It much easier now that it was back when I was installing SunOS 4.1.4 on Sun 3's and Sparc 2's and compiling X11 from source. If you were really aware, then you wouldn't do it... I haven't done anything yet, except appeal to the puppet community at large for some insight I've considered all of these. Does anyone know of a CentOS/RH repo that has the latest versions of Ruby available? I have done some searching, but not exhaustively so, for a repo with the most recent versions of Ruby, but no luck so far. The reason I want to use ruby-1.9.2-p320 on these test VM's is because in the production environment that these are mimicking the engineering folks are running that release, under RVM, and they want to avoid any installs of other versions to eliminate any chance of something getting pointed to an older version of Ruby accidentally. The dev and production environments will both point to Ruby under RVM. This is wrong approach. Try to figure out why is RHEL/CentOS and Suse Enterprise sticking to older version of ruby (or every other piece of software they distribute), and what are the benefits... Considering that the developers have been working on this for over a year, and they have their reasons for selecting RVM and Ruby 1.9.2, it's not my call. I'm here to bring as much consistency and reliability as I can to the systems that have been managed by the whims of the developers for quite some time. I've made a huge amount of progress by basically giving them them some nice, clean, secure production systems that they aren't allowed to manage. I have helped them get to the point where they can use Capistrano to deploy the application, and we have partitioned Neo4j and Mongodb onto their own separate systems. Now I'm working on deploying puppet to keep the systems consistent and allow me to do all that puppet can do to keep things in order. I was hoping someone might know some details about the rpm system that might allow me to tell it that ruby was installed without installing ruby, as with fake sendmail. Perhaps a lesser known tool that allows one to insert entries into the rpm database files. You are mangling with the system in a way it shouldn't be mangled with. Try to persuade your developers to use platform that is already used on production, and not vice versa. Well, I suppose everyone has a different mandate at different companies. My current gig is at yet another start up and the company is engineering driven. Given that I need to make sure that I don't do anything that steps on engineering. I'm not entirely under their thumb. I insisted on certain conditions before I took this job, and that has allowed me to replace token security with real security. Engineering and I have worked together very closely to help get them more compartmentalized to the application is now of a discrete unit, and not so much an electron cloud where they may have reached all over the OS. I give them a reliable server, and they agree to keep the application contained. If that doesn't go quite right, then take src.rpm from RedHat/CentOS, bump version to 1.9.x - or whatever do you want to use, drop in newer sources, fix patches - and rebuild the RPM - or try to backport latest feodra build: http://fedora.aau.at/linux/releases/17/Fedora/source/SRPMS/r/ruby-1.9.3.194-10.1.fc17.src.rpm but that could bring you back to trouble because that version probably won't be 100% identical to the one that your dev team uses (if they stick to sources). So we're back to square one - you *have to* convice your team to use Ruby from RPM package - either fedora backport or standard RHEL 1.8.x. Everything else _*will*_ bit you in the ass in the long run. That’s why I'm here asking questions. Its good to minimize all the future ass biting that one can, which is also why I'm testing on a pair of VM's to get puppet functional and worked out before it gets anywhere near a production system. -- Jakov Sosic www.srce.unizg.hr -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/OEPaTlAP2QIJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com.
Re: [Puppet Users] puppet and std
Le 21 sept. 2012 à 17:05, jcbollinger a écrit : On Friday, September 21, 2012 4:35:41 AM UTC-5, Fabrice Bacchella wrote: I'm starting it by hand. It's the same process (pid 1845) that is nulling stderr that is writing to it, so it's not related to the way it's launched, --debug provides no help. Using strace is not a long term solution. It was used to understand why Puppet keep failing silently. I still not know why it's failling. But I know why it's silent : error message going to /dev/null, instead of syslog. Are you running puppet agent or just puppet? It should be the former. puppet agent. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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 --no-client ignore USR1
Le 21 sept. 2012 à 15:35, jcbollinger a écrit : On Friday, September 21, 2012 6:21:04 AM UTC-5, Fabrice Bacchella wrote: When puppet is launched as a daemon, a kill -USR trigger a catalog run : Sep 21 12:56:01 XXX puppet-agent[15324]: Caught USR1; calling reload Sep 21 12:56:24 XXX puppet-agent[15324]: Finished catalog run in 12.96 seconds But when launched with --listen --no-client, nothing happens any more : Sep 21 13:01:44 XXX puppet-agent[16858]: Caught USR1; calling reload Sep 21 13:02:21 XXX puppet-agent[16858]: Caught USR1; calling reload With only --listen, it still works. Yes, that's exactly what I would expect. With --no-client, the agent only requests a catalog when it is signaled by the master. The response to SIGUSR1 is a function of the client mode. But in the manpage : --no-client Do not create a config client. This will cause the daemon to run without ever checking for its configuration automatically, and only makes sense when puppet agent is being run with listen = true in puppet.conf or was started with the --listenoption. SIGUSR1 Immediately retrieve and apply configurations from the puppet master. runinterval How often puppet agent applies the client configuration; in seconds. Note that a runinterval of 0 means “run continuously” rather than “never run.” If you want puppet agent to never run, you should start it with the --no-client option. Default: 1800 How can I understand that you say from the documentation ? It says checking for its configuration automatically, that's not the same thing as reacting to a signal. Reacting to SIGUSR1 is the same kind of comportment as client : puppet waiting for external signals. The should go together. I want to launch puppet in listen only mode, and schedule it using mcollective, but because a stack of different bugs, what should be a simple task is becoming a nightmare. There is this one. But there is also : http://projects.puppetlabs.com/issues/4411 http://projects.puppetlabs.com/issues/8917 Can someone show me a way out of this maze ? I'm not very familiar with using MCollective to schedule Puppet runs, but bugs notwithstanding, it looks like you are asking for more from Puppet than you need to achieve that. Have you considered not running the agent in daemon mode at all? You should be able to use mco to perform puppet agent --onetime --no-daemonize at need. If you don't *also* need the ability for the master to trigger Puppet runs over the listen interface, or for local processes to trigger runs via SIGUSR1, then that should completely cover your needs. When running using puppet through mco with onetime once, the run is synchrone : each catalog puppet must be finished before going to the next, it's too slow. When puppet is running as a daemon, the run is asynchrone and so much faster. I was thinking about using the schedule type (http://docs.puppetlabs.com/references/latest/type.html#schedule), but I'm loosing hope. I don't expect it to run when runinterval is disabled, even if I think it should be. Even if you are running the agent with --listen --no-client (more on that in a moment), you can still trigger one-off agent runs of the puppet agent as described above. That's safe inasmuch as Puppet uses a lock file to prevent overlapping runs. You can work around the issue of agent options not recognized in the config file via Puppet's sysconfig interface (in some versions of Puppet, at least) or by modifying the actual service management script. With the sysconfig interface, for example, you would install a file /etc/sysconfig/puppet, containing at least: PUPPET_EXTRA_OPTS==--no-client to make the service control script provide that option directly when it launches the agent. If it essential that the agent accept SIGUSR1 to trigger a catalog cycle, then you must run in daemon mode with the client enabled (but --listen is not relevant to this question). In that case you could consider setting the run interval to something very long, so that automated runs are very rare (except that runs will always happen at service startup). very rare and at service startup is not the same thing as never. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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] install vmware tools through puppet
On Fri, Sep 21, 2012 at 6:48 PM, Jakov Sosic jso...@srce.hr wrote: On 09/19/2012 11:55 PM, Hai Tao wrote: There seems to be a few vmware tools installation modules. Has someone used these modules to install VMware tools? Searching http://forge.puppetlabs.com ... NAMEDESCRIPTION AUTHORKEYWORDS vchoi-vmwarePuppet module to handle installation, upgrade and reconfiguration of vmware tools on vmware virtual nodes. @vchoivirtualization vmware vmware-tools vmware_tools vmtools razorsedge-vmwaretools Puppet VMware Tools OSP Module @razorsedge vmware vmware-tools vmware_tools vmtools rhel CentOS SuSE OEL puppetlabs-vcenter VMware vCenter installation and management @puppetlabs windows vmware vcenter vsphere 5UbZ3r0-vmwaretools This module handles the installation the VMware Tools Operating System Specific @5UbZ3r0 debian virtualization rhel CentOS vmware vmware-tools vmwaretools puppetlabs-appdirector # VMware vFabric Application Directorâ ¢ Puppet Service @puppetlabs vmware How well does it work? It seems that nobody tried this already. I'm interested too... -- Jakov Sosic www.srce.unizg.hr -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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. I don't know that I would endorse one over another, but Puppet Labs did a module of the week post about one of them. http://puppetlabs.com/blog/module-of-the-week-razorsedge-vmwaretools/ That might be a good starting point. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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] variable usage in a string, scenario dependent?
Possibly stupid question - how do I know when I have to use a variable
in a string like this - ${apache::params::moddir}/php.conf - or when
it's safe to just do it like this -
$apache::params::moddir/php.conf. It seems like sometimes I need to
do the former, and other times the latter.
I don't really have any prior programming knowledge - I feel like this
would be obvious if I did. :-(
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@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: variable usage in a string, scenario dependent?
It turns out that you do always need the {}, and this just works because
the / in the path breaks the variable-finding regex.
Thanks to rodjek on irc! :-D
On Saturday, September 22, 2012 3:15:07 PM UTC-4, Zachary Alex Stern wrote:
Possibly stupid question - how do I know when I have to use a variable
in a string like this - ${apache::params::moddir}/php.conf - or when
it's safe to just do it like this -
$apache::params::moddir/php.conf. It seems like sometimes I need to
do the former, and other times the latter.
I don't really have any prior programming knowledge - I feel like this
would be obvious if I did. :-(
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/_obS97BTTYsJ.
To post to this group, send email to puppet-users@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] install vmware tools through puppet
It is a useful tool. However, the difficulty is that our ENV has multiple versions of ESX hosts, 3.5, 4.1 and 5.0. The guest OS has no clue what version of ESX it is running on, so how can puppet server push a correct version of vmware tools to a client? On Sat, Sep 22, 2012 at 11:20 AM, Michael Stahnke stah...@puppetlabs.com wrote: On Fri, Sep 21, 2012 at 6:48 PM, Jakov Sosic jso...@srce.hr wrote: On 09/19/2012 11:55 PM, Hai Tao wrote: There seems to be a few vmware tools installation modules. Has someone used these modules to install VMware tools? Searching http://forge.puppetlabs.com ... NAMEDESCRIPTION AUTHORKEYWORDS vchoi-vmwarePuppet module to handle installation, upgrade and reconfiguration of vmware tools on vmware virtual nodes. @vchoivirtualization vmware vmware-tools vmware_tools vmtools razorsedge-vmwaretools Puppet VMware Tools OSP Module @razorsedge vmware vmware-tools vmware_tools vmtools rhel CentOS SuSE OEL puppetlabs-vcenter VMware vCenter installation and management @puppetlabs windows vmware vcenter vsphere 5UbZ3r0-vmwaretools This module handles the installation the VMware Tools Operating System Specific @5UbZ3r0 debian virtualization rhel CentOS vmware vmware-tools vmwaretools puppetlabs-appdirector # VMware vFabric Application Directorâ ¢ Puppet Service @puppetlabs vmware How well does it work? It seems that nobody tried this already. I'm interested too... -- Jakov Sosic www.srce.unizg.hr -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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. I don't know that I would endorse one over another, but Puppet Labs did a module of the week post about one of them. http://puppetlabs.com/blog/module-of-the-week-razorsedge-vmwaretools/ That might be a good starting point. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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. -- Hai Tao -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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] install vmware tools through puppet
I believe the open-vm-tools at http://packages.vmware.com/tools are ESX host version agnostic. We pull the rhel 4-6 repos into RHN satellite and just use puppet ensure the latest is installed. If you do t use satellite you could just clone the repo and configure yum on the clients. Packages are available for RHEL, SuSE and deb at least. -Alan On Sep 22, 2012 3:25 PM, Hai Tao ehai...@gmail.com wrote: It is a useful tool. However, the difficulty is that our ENV has multiple versions of ESX hosts, 3.5, 4.1 and 5.0. The guest OS has no clue what version of ESX it is running on, so how can puppet server push a correct version of vmware tools to a client? On Sat, Sep 22, 2012 at 11:20 AM, Michael Stahnke stah...@puppetlabs.com wrote: On Fri, Sep 21, 2012 at 6:48 PM, Jakov Sosic jso...@srce.hr wrote: On 09/19/2012 11:55 PM, Hai Tao wrote: There seems to be a few vmware tools installation modules. Has someone used these modules to install VMware tools? Searching http://forge.puppetlabs.com ... NAMEDESCRIPTION AUTHORKEYWORDS vchoi-vmwarePuppet module to handle installation, upgrade and reconfiguration of vmware tools on vmware virtual nodes. @vchoivirtualization vmware vmware-tools vmware_tools vmtools razorsedge-vmwaretools Puppet VMware Tools OSP Module @razorsedge vmware vmware-tools vmware_tools vmtools rhel CentOS SuSE OEL puppetlabs-vcenter VMware vCenter installation and management @puppetlabs windows vmware vcenter vsphere 5UbZ3r0-vmwaretools This module handles the installation the VMware Tools Operating System Specific @5UbZ3r0 debian virtualization rhel CentOS vmware vmware-tools vmwaretools puppetlabs-appdirector # VMware vFabric Application Directorâ ¢ Puppet Service @puppetlabs vmware How well does it work? It seems that nobody tried this already. I'm interested too... -- Jakov Sosic www.srce.unizg.hr -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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. I don't know that I would endorse one over another, but Puppet Labs did a module of the week post about one of them. http://puppetlabs.com/blog/module-of-the-week-razorsedge-vmwaretools/ That might be a good starting point. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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. -- Hai Tao -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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-users@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] install vmware tools through puppet
I've done something similar using the open-vm package on debian hosts. On Saturday, September 22, 2012 3:06:10 PM UTC-5, Alan Evans wrote: I believe the open-vm-tools at http://packages.vmware.com/tools are ESX host version agnostic. We pull the rhel 4-6 repos into RHN satellite and just use puppet ensure the latest is installed. If you do t use satellite you could just clone the repo and configure yum on the clients. Packages are available for RHEL, SuSE and deb at least. -Alan On Sep 22, 2012 3:25 PM, Hai Tao eha...@gmail.com javascript: wrote: It is a useful tool. However, the difficulty is that our ENV has multiple versions of ESX hosts, 3.5, 4.1 and 5.0. The guest OS has no clue what version of ESX it is running on, so how can puppet server push a correct version of vmware tools to a client? On Sat, Sep 22, 2012 at 11:20 AM, Michael Stahnke sta...@puppetlabs.com javascript: wrote: On Fri, Sep 21, 2012 at 6:48 PM, Jakov Sosic jso...@srce.hrjavascript: wrote: On 09/19/2012 11:55 PM, Hai Tao wrote: There seems to be a few vmware tools installation modules. Has someone used these modules to install VMware tools? Searching http://forge.puppetlabs.com ... NAMEDESCRIPTION AUTHORKEYWORDS vchoi-vmwarePuppet module to handle installation, upgrade and reconfiguration of vmware tools on vmware virtual nodes. @vchoivirtualization vmware vmware-tools vmware_tools vmtools razorsedge-vmwaretools Puppet VMware Tools OSP Module @razorsedge vmware vmware-tools vmware_tools vmtools rhel CentOS SuSE OEL puppetlabs-vcenter VMware vCenter installation and management @puppetlabs windows vmware vcenter vsphere 5UbZ3r0-vmwaretools This module handles the installation the VMware Tools Operating System Specific @5UbZ3r0 debian virtualization rhel CentOS vmware vmware-tools vmwaretools puppetlabs-appdirector # VMware vFabric Application Directorâ ¢ Puppet Service @puppetlabs vmware How well does it work? It seems that nobody tried this already. I'm interested too... -- Jakov Sosic www.srce.unizg.hr -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet...@googlegroups.comjavascript: . To unsubscribe from this group, send email to puppet-users...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. I don't know that I would endorse one over another, but Puppet Labs did a module of the week post about one of them. http://puppetlabs.com/blog/module-of-the-week-razorsedge-vmwaretools/ That might be a good starting point. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet...@googlegroups.comjavascript: . To unsubscribe from this group, send email to puppet-users...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Hai Tao -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet...@googlegroups.comjavascript: . To unsubscribe from this group, send email to puppet-users...@googlegroups.com javascript:. 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 view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/FTYloCumctkJ. To post to this group, send email to puppet-users@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] duplicated public keys in authorized keys
hi
please delete the common information from the key value ,may be you used
ssh-keygen -t rsa -C XXX.
2012/9/21 Hiu yen...@gmail.com
hi Admin,
How are you?
I have a easy ssh_authorized_key like below
ssh_authorized_key { hiu@$fqdn:
name = hiu@$fqdn,
ensure = present,
type = ssh-rsa,
key = $keys,
user = hiu,
}
I manage to inject my public key onto the puppet clients, but the problem
is whenever the puppet agent refresh itself with -runinterval=XX, then, the
public key re-created again. as the result, I have a lot duplicated public
keys result like below in my authorized_keys. How can i avoid the
duplicated keys?
ssh-rsa XXX
ssh-rsa XXX
ssh-rsa XXX
please advise. thanks!
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/cKNAQRj2WCMJ.
To post to this group, send email to puppet-users@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-users@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] install vmware tools through puppet
I think vmware tools RPMs are categarized by ESX version, am I wrong? On Sat, Sep 22, 2012 at 7:42 PM, Christian McHugh christian.mch...@gmail.com wrote: I've done something similar using the open-vm package on debian hosts. On Saturday, September 22, 2012 3:06:10 PM UTC-5, Alan Evans wrote: I believe the open-vm-tools at http://packages.vmware.com/tools are ESX host version agnostic. We pull the rhel 4-6 repos into RHN satellite and just use puppet ensure the latest is installed. If you do t use satellite you could just clone the repo and configure yum on the clients. Packages are available for RHEL, SuSE and deb at least. -Alan On Sep 22, 2012 3:25 PM, Hai Tao eha...@gmail.com wrote: It is a useful tool. However, the difficulty is that our ENV has multiple versions of ESX hosts, 3.5, 4.1 and 5.0. The guest OS has no clue what version of ESX it is running on, so how can puppet server push a correct version of vmware tools to a client? On Sat, Sep 22, 2012 at 11:20 AM, Michael Stahnke sta...@puppetlabs.com wrote: On Fri, Sep 21, 2012 at 6:48 PM, Jakov Sosic jso...@srce.hr wrote: On 09/19/2012 11:55 PM, Hai Tao wrote: There seems to be a few vmware tools installation modules. Has someone used these modules to install VMware tools? Searching http://forge.puppetlabs.com ... NAMEDESCRIPTION AUTHORKEYWORDS vchoi-vmwarePuppet module to handle installation, upgrade and reconfiguration of vmware tools on vmware virtual nodes. @vchoivirtualization vmware vmware-tools vmware_tools vmtools razorsedge-vmwaretools Puppet VMware Tools OSP Module @razorsedge vmware vmware-tools vmware_tools vmtools rhel CentOS SuSE OEL puppetlabs-vcenter VMware vCenter installation and management @puppetlabs windows vmware vcenter vsphere 5UbZ3r0-vmwaretools This module handles the installation the VMware Tools Operating System Specific @5UbZ3r0 debian virtualization rhel CentOS vmware vmware-tools vmwaretools puppetlabs-appdirector # VMware vFabric Application Directorâ ¢ Puppet Service @puppetlabs vmware How well does it work? It seems that nobody tried this already. I'm interested too... -- Jakov Sosic www.srce.unizg.hr -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet...@googlegroups.com. To unsubscribe from this group, send email to puppet-users...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. I don't know that I would endorse one over another, but Puppet Labs did a module of the week post about one of them. http://puppetlabs.com/blog/module-of-the-week-razorsedge-vmwaretools/ That might be a good starting point. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet...@googlegroups.com. To unsubscribe from this group, send email to puppet-users...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Hai Tao -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet...@googlegroups.com. To unsubscribe from this group, send email to puppet-users...@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 view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/FTYloCumctkJ. To post to this group, send email to puppet-users@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. -- Hai Tao -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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.
