Hi all, I am a developer and have no experience at all with Puppet. In the future, we will probably offer an increasing number of services to our customers via HTTP, and the reliability and maintainability of our infrastructure will correspondingly become more and more critical. We have invested heavily in virtualization infrastructure, in particular VMWare ESX. How well does Puppet work with VMWare ESX? I have found some material, but not as much as I hoped for. I am wondering if this is perhaps a combination we should better avoid. What are your recommendations? Jens -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Jun 13, 11:39 am, Jens Meydam <jmey...@gmail.com> wrote:> We have invested heavily in virtualization infrastructure, in > particular VMWare ESX. How well does Puppet work with VMWare ESX? I > have found some material, but not as much as I hoped for. I am > wondering if this is perhaps a combination we should better avoid.Not at all, Puppet with vmware guest platforms is fantastic. We have a procedure in place that uses kickstart with CentOS and puppet for post-install configuration that can bring a system up and on the net and with all packages installed in under 10 minutes. We deploy hosts constantly using this method, and each new host comes up already puppet-managed, with vmware tools installed, and ready for final configuration.> What are your recommendations?Do it! :) -d -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
> > Not at all, Puppet with vmware guest platforms is fantastic. >+1 More to the point, puppet seems best at allowing rapid scale out of applications via virtualization. Our policy is to deploy all linux virtual machines via puppet. It is the physical machines serving as hypervisors or as critical cluster management/infrastructure that we don''t let puppet currently touch.> We have a procedure in place that uses kickstart with CentOS and > puppet for post-install configuration that can bring a system up and > on the net and with all packages installed in under 10 minutes. We > deploy hosts constantly using this method, and each new host comes up > already puppet-managed, with vmware tools installed, and ready for > final configuration. >We currently do cloning of a template VM for new rhel nodes. We''ve avoided kickstart because a) we already have to go into vcenter to create/configure new vms properly and b) there isn''t much that kickstart would give us we don''t already get from cloning and running scripts after clone. When/if we can get to a point that puppet dashboard can tell vcenter to spawn a new vm, provision appropriate virtual hardware and vm settings, start kickstart, and then start puppet, then we''ll switch to that :) -Matt -- Matthew Marlowe - http://www.deploylinux.net/ CEO @ DeployLinux Consulting, Inc matt@deploylinux.net, 858-400-7430 http://www.twitter.com/deploylinux -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi "dbs", Hi Matthew, Thanks a lot for your detailed answers! Jens On Jun 14, 3:39 pm, Matthew Marlowe <m...@deploylinux.net> wrote:> > Not at all, Puppet with vmware guest platforms is fantastic. > > +1 > > More to the point, puppet seems best at allowing rapid scale out of applications via virtualization. Our policy is to deploy all linux virtual machines via puppet. > > It is the physical machines serving as hypervisors or as critical cluster management/infrastructure that we don''t let puppet currently touch. > > > We have a procedure in place that uses kickstart with CentOS and > > puppet for post-install configuration that can bring a system up and > > on the net and with all packages installed in under 10 minutes. We > > deploy hosts constantly using this method, and each new host comes up > > already puppet-managed, with vmware tools installed, and ready for > > final configuration. > > We currently do cloning of a template VM for new rhel nodes. We''ve avoided kickstart because a) we already have to go into vcenter to create/configure new vms properly and b) there isn''t much that kickstart would give us we don''t already get from cloning and running scripts after clone. When/if we can get to a point that puppet dashboard can tell vcenter to spawn a new vm, provision appropriate virtual hardware and vm settings, start kickstart, and then start puppet, then we''ll switch to that :) > > -Matt > -- > Matthew Marlowe -http://www.deploylinux.net/ > CEO @ DeployLinux Consulting, Inc > m...@deploylinux.net, 858-400-7430http://www.twitter.com/deploylinux-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.