I've just started using Vagrant, but am not quite sure how it relates to production.
Can I use Vagrant to build out my production server too? Or would I just use Chef/Puppet/Ansible with the same playbook/recipe on both my Vagrant powered VM and non-vagrant powered production machine?
I use Salt (used to use Puppet) to build out my Vagrant box(es) in development.
When I'm good to go, I use Packer with the same Salt configuration to build an image and push it to AWS/DO/RackSpace as needed. Makes it super easy to develop and deploy on exactly the same machine, and the Vagrant/Packer configurations are typically fairly minimal so there's very little set-up time once you've written out your Salt/Puppet/etc configurations.
Comments
I've just started using Vagrant, but am not quite sure how it relates to production.
Can I use Vagrant to build out my production server too? Or would I just use Chef/Puppet/Ansible with the same playbook/recipe on both my Vagrant powered VM and non-vagrant powered production machine?
I use Salt (used to use Puppet) to build out my Vagrant box(es) in development.
When I'm good to go, I use Packer with the same Salt configuration to build an image and push it to AWS/DO/RackSpace as needed. Makes it super easy to develop and deploy on exactly the same machine, and the Vagrant/Packer configurations are typically fairly minimal so there's very little set-up time once you've written out your Salt/Puppet/etc configurations.
I believe Vagrant is for quickly and repeatably building development environments - I don't think it's meant for production.
Look into packer for building out Production images, and Chef/Puppet/Ansible for additional configuration ontop those images.