Hi everyone, I noticed puppet 3 has made it to rc3 and they have made it available in the devel repositories. I am getting tempted to switch now and avoid the rush. I have tried to find out what is new or different with puppet 3 but haven''t been able to find anything. I am currently running 2.7.17 with puppetdb for config storing which works great by the way. I only have 10 nodes right now but that will be growing shortly. Has anything been deprecated in 3 and is there anything I need to change with my current code to make it work under version 3? Thanks Pete -- 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.
I would hope you have a development environment to test this on before you make the switch? I wouldn''t actually recommend switching a production environment to a release candidate. It''s okay to start testing puppet 3 in a staging environment to see if you are going to have majore issues, but I personally won''t be switching until the first two or three minor releases after 3.0. I prefer others to run into problems instead of me :) As for the changes, reading through the release notes will give you a good idea. There are some major changes and a lot of minor changes, so test, rinse, repeat would be my suggestion. http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes have fun! Walter On Fri, Jul 6, 2012 at 9:24 AM, Peter Brown <rendhalver@gmail.com> wrote:> Hi everyone, > > I noticed puppet 3 has made it to rc3 and they have made it available > in the devel repositories. > I am getting tempted to switch now and avoid the rush. > I have tried to find out what is new or different with puppet 3 but > haven''t been able to find anything. > I am currently running 2.7.17 with puppetdb for config storing which > works great by the way. > I only have 10 nodes right now but that will be growing shortly. > > Has anything been deprecated in 3 and is there anything I need to > change with my current code to make it work under version 3? > Thanks > > Pete > > -- > 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. >-- Walter Heck -- Check out my startup: Puppet training and consulting @ http://www.olindata.com Follow @olindata on Twitter and/or ''Like'' our Facebook page at http://www.facebook.com/olindata -- 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 6 July 2012 12:59, Walter Heck <walterheck@gmail.com> wrote:> I would hope you have a development environment to test this on before > you make the switch? I wouldn''t actually recommend switching a > production environment to a release candidate. It''s okay to start > testing puppet 3 in a staging environment to see if you are going to > have majore issues, but I personally won''t be switching until the > first two or three minor releases after 3.0. I prefer others to run > into problems instead of me :)I guess it''s time to build myself a vm on the laptop (probably with puppet :) )and see how it goes. If my code works I may switch the production env over and see how that goes.> As for the changes, reading through the release notes will give you a > good idea. There are some major changes and a lot of minor changes, so > test, rinse, repeat would be my suggestion. > http://projects.puppetlabs.com/projects/puppet/wiki/Release_NotesCool. thanks for that.> have fun!I always do preferably learning something while having fun.> > Walter > > On Fri, Jul 6, 2012 at 9:24 AM, Peter Brown <rendhalver@gmail.com> wrote: >> Hi everyone, >> >> I noticed puppet 3 has made it to rc3 and they have made it available >> in the devel repositories. >> I am getting tempted to switch now and avoid the rush. >> I have tried to find out what is new or different with puppet 3 but >> haven''t been able to find anything. >> I am currently running 2.7.17 with puppetdb for config storing which >> works great by the way. >> I only have 10 nodes right now but that will be growing shortly. >> >> Has anything been deprecated in 3 and is there anything I need to >> change with my current code to make it work under version 3? >> Thanks >> >> Pete >> >> -- >> 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. >> > > > > -- > Walter Heck > > -- > Check out my startup: Puppet training and consulting @ http://www.olindata.com > Follow @olindata on Twitter and/or ''Like'' our Facebook page at > http://www.facebook.com/olindata > > -- > 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. >-- 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 Fri, Jul 6, 2012 at 11:46 AM, Peter Brown <rendhalver@gmail.com> wrote:> I guess it''s time to build myself a vm on the laptop (probably with > puppet :) )and see how it goes. > If my code works I may switch the production env over and see how that goes.Look into virtualbox, vagrant and veewee, the three combined make an extremely flexible, powerful and cool solution that can automatically build a vm with your repository applied to it. Pure magic :) -- Walter Heck -- Check out my startup: Puppet training and consulting @ http://www.olindata.com Follow @olindata on Twitter and/or ''Like'' our Facebook page at http://www.facebook.com/olindata -- 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 6 July 2012 13:57, Walter Heck <walterheck@gmail.com> wrote:> On Fri, Jul 6, 2012 at 11:46 AM, Peter Brown <rendhalver@gmail.com> wrote: >> I guess it''s time to build myself a vm on the laptop (probably with >> puppet :) )and see how it goes. >> If my code works I may switch the production env over and see how that goes. > Look into virtualbox, vagrant and veewee, the three combined make an > extremely flexible, powerful and cool solution that can automatically > build a vm with your repository applied to it. Pure magic :)I tried getting puppet to manage virtualbox nodes but gave up when it looked like I needed to deploy a dhcp setup with tftp and pxe to make it work. Those three look like a pretty handy trio though. I was using xen for vm''s in my last job and manageing them with puppet but no one likes xen anymore (especially major linux distros) so my current environment is setup with kvm, cobbler and koan all managed by puppet. I have linux on my laptop so i will just use my current config and build me a new test environment :)> > > -- > Walter Heck > > -- > Check out my startup: Puppet training and consulting @ http://www.olindata.com > Follow @olindata on Twitter and/or ''Like'' our Facebook page at > http://www.facebook.com/olindata > > -- > 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. >-- 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 07/06/2012 12:57 AM, Peter Brown wrote:> On 6 July 2012 13:57, Walter Heck <walterheck@gmail.com> wrote: >> On Fri, Jul 6, 2012 at 11:46 AM, Peter Brown <rendhalver@gmail.com> wrote: >>> I guess it''s time to build myself a vm on the laptop (probably with >>> puppet :) )and see how it goes. >>> If my code works I may switch the production env over and see how that goes. >> Look into virtualbox, vagrant and veewee, the three combined make an >> extremely flexible, powerful and cool solution that can automatically >> build a vm with your repository applied to it. Pure magic :) > I tried getting puppet to manage virtualbox nodes but gave up when it > looked like I needed to deploy a dhcp setup with tftp and pxe to make > it work. > Those three look like a pretty handy trio though. > > I was using xen for vm''s in my last job and manageing them with puppet > but no one likes xen anymore (especially major linux distros) so my > current environment is setup with kvm, cobbler and koan all managed by > puppet. > > I have linux on my laptop so i will just use my current config and > build me a new test environment :) > > >VirtualBox will host PXE and TFTP services for your VM''s when using the NAT interface: https://www.virtualbox.org/manual/ch06.html#nat-tftp I got this working before I found out how awesome vagrant and veewee are. You''ll need VM''s with NAT and host-only NIC''s. vagrant can set the IP''s for the host-only network. If you''re using a puppet server, instead of serverless puppet, then it will have to go over the host-only network. Jason -- 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.