Lots of information covered very quickly. I think I got it all.
A couple of questions that I had from the talk:
1) Should Chef and/or Puppet be used in production? Was clear that Vagrant should not.
2) Is SSH through Vagrant preferred way of interacting with box (read log files, clear cache, etc)
Would be great to have this talk early in the week and a deep dive (or hands-on) later. Could also be one of the Thursday sessions for the same purpose.
Information packed. I've been playing with vagrant for a few weeks, and have been using puppet in prod for almost 3 years, and I learned many new things here. Lots of cues for audience participation which got everyone involved. Excellent presentation all around. A live demo was the only thing missing, but that didn't detract from the talk one bit.
@Chad: Puppet or Chef are definitely tools that can be used to provision production servers. These same provisioning scripts can be re-used to make sure your vagrant boxes represent a copy of your production environment.
The "vagrant ssh" is by far the preferred way to interact with the machines. Please have a look at the slides for more information: https://speakerdeck.com/thijsferyn/vagrant-puppet-and-chef-number-ftw-sunshinephp-2014
Very effective delivery of information without any BS and straight to the point! I really liked how you walked through two implementations of the same problem and allowed us to make a side by side comparison. Good job and I hope you submit a talk for next year's conference.
Would have loved a little more information on 'why' we need this. With all the complicated setup involved, it's hard to justify this when you have one production server and can pass around ready-made VM's to developers.
I definitely learned quite a bit about vagrant, puppet, and chef in this talk. Thank you Thijs!
I would have liked to you touch on puPHPet a little, even by reference, as it have reminded me to ask a question about how to persist post deploy changes...or maybe how to add those changes to the deploy process.
((When I use puPHPet to generate the base box, I still have to go through and do a few environment tweaks or change the default settings on some of the installed apps, but every time I run vagrant up, those changes get overriden back to defaults.))
Comments
Comments are closed.
Good talk, thank you. Too bad about the sound system :(
You are very enthusiastic about the topic and you had lots of examples. Looking forward to see the slides so I can review the samples.
Thanks!
Lots of information covered very quickly. I think I got it all.
A couple of questions that I had from the talk:
1) Should Chef and/or Puppet be used in production? Was clear that Vagrant should not.
2) Is SSH through Vagrant preferred way of interacting with box (read log files, clear cache, etc)
Would be great to have this talk early in the week and a deep dive (or hands-on) later. Could also be one of the Thursday sessions for the same purpose.
Information packed. I've been playing with vagrant for a few weeks, and have been using puppet in prod for almost 3 years, and I learned many new things here. Lots of cues for audience participation which got everyone involved. Excellent presentation all around. A live demo was the only thing missing, but that didn't detract from the talk one bit.
Great talk, highly informative and well presented.
Great talk Thijs. Very informative.
@Chad: Puppet or Chef are definitely tools that can be used to provision production servers. These same provisioning scripts can be re-used to make sure your vagrant boxes represent a copy of your production environment.
The "vagrant ssh" is by far the preferred way to interact with the machines. Please have a look at the slides for more information: https://speakerdeck.com/thijsferyn/vagrant-puppet-and-chef-number-ftw-sunshinephp-2014
Very effective delivery of information without any BS and straight to the point! I really liked how you walked through two implementations of the same problem and allowed us to make a side by side comparison. Good job and I hope you submit a talk for next year's conference.
Would have loved a little more information on 'why' we need this. With all the complicated setup involved, it's hard to justify this when you have one production server and can pass around ready-made VM's to developers.
I definitely learned quite a bit about vagrant, puppet, and chef in this talk. Thank you Thijs!
I would have liked to you touch on puPHPet a little, even by reference, as it have reminded me to ask a question about how to persist post deploy changes...or maybe how to add those changes to the deploy process.
((When I use puPHPet to generate the base box, I still have to go through and do a few environment tweaks or change the default settings on some of the installed apps, but every time I run vagrant up, those changes get overriden back to defaults.))