Public bug reported: We use Chef (solo) for our infrastructure automation in both production, staging and local development environments .
We're using Ubuntu Cloud Image AMIs on AWS for production (and staging). Currently using the Ubuntu Cloud Images for Vagrant to closely match the production AMIs. We prefer not to maintain our own Vagrant boxes and AMIs so the Ubuntu Cloud Images are fantastic. It's preferable for these, for us, to be as vanilla as possible. We boostrap Chef (at a fixed version) onto both the AMIs (https://github.com/matschaffer/knife-solo) and Vagrant boxes (https://github.com/schisamo/vagrant-omnibus) This provides greater control than reliance on a bundled version. Our team is distributed throughout the globe and fluctuates between 20-30 developers. The stability and quality of the Ubuntu Cloud Images as well as the parity between the images for multiple targets is key to reducing friction in a distributed development environment. Currently limitation is the availability of only VirtualBox provider Vagrant boxes. Vagrant now supports VMWare Fusion and Workstation as virtualization providers and for many users in our environment vmware fusion is vastly preferable. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1178451 Title: ubuntu cloud images and vagrant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1178451/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
