Confirmed users
920
edits
Webdev:DevBoxVMImages: Difference between revisions
Jump to navigation
Jump to search
→Maintaining VM images
LesOrchard (talk | contribs) |
LesOrchard (talk | contribs) |
||
| Line 80: | Line 80: | ||
Jenkins. | Jenkins. | ||
=== Building a plain VM === | |||
Here's the general process for building a plain VM by hand: | |||
* Grab an ISO of your base OS. (eg. MDN is using CentOS) | |||
* Create a VirtualBox VM. | |||
* Install the bare minimum of server packages. | |||
** You might want to export an OVA of this base install for future from-scratch builds. | |||
* Create a [https://raw.github.com/mozilla/kuma/HEAD/scripts/rackspace-bootstrap.sh bootstrap script] that gets Puppet installed and prepares a git clone of the project's source | |||
* As root, run <code>puppet apply /vagrant/puppet/dev-vagrant.pp</code> (or whatever you named it) | |||
* Once Puppet has finished, verify that the project is working. | |||
* Shutdown the VM and export an OVA | |||
* Upload the exported appliance to hosting | |||
With some more thinking, much or most of the above could be automated using libcloud or VBoxManage | |||
=== Building a Vagrant box === | |||
Needs work: | |||
* Use <code>vagrant destroy && vagrant up</code> to spin up a VM in VirtualBox | * Use <code>vagrant destroy && vagrant up</code> to spin up a VM in VirtualBox | ||