Confirmed users
1,136
edits
Webdev:DevBoxVMImages: Difference between revisions
Adding CI use case and sasl-browserid to page
LesOrchard (talk | contribs) |
(Adding CI use case and sasl-browserid to page) |
||
| Line 4: | Line 4: | ||
of our websites. That way, a new contributor can focus on contributing, | of our websites. That way, a new contributor can focus on contributing, | ||
rather than learning how to install and configure a website first. | rather than learning how to install and configure a website first. | ||
A second use case is continuous integration against a VM hosted environment. As | |||
a first stab, we're using a vagrant based VM. We'll refer to this as CI use case below. | |||
== Open questions == | == Open questions == | ||
| Line 20: | Line 23: | ||
** Shared folder from Host to VM | ** Shared folder from Host to VM | ||
** Custom box format rather than straight VM appliance or image | ** Custom box format rather than straight VM appliance or image | ||
** For CI case, we want vanilla Vagrant behaviors, but libcloud thingie would work too | |||
* [http://libcloud.apache.org/getting-started.html libcloud]+Puppet better than Vagrant+Puppet? | * [http://libcloud.apache.org/getting-started.html libcloud]+Puppet better than Vagrant+Puppet? | ||
** libcloud could [https://bitbucket.org/ianb/libcloud-vbox target VirtualBox] locally and Rackspace / Amazon EC2 remotely | ** libcloud could [https://bitbucket.org/ianb/libcloud-vbox target VirtualBox] locally and Rackspace / Amazon EC2 remotely | ||
| Line 44: | Line 48: | ||
*** eg. <code>~/.gitconfig</code> with contributor's name and email, etc | *** eg. <code>~/.gitconfig</code> with contributor's name and email, etc | ||
** Need instructions advising a <code>git pull</code> after initial boot-up | ** Need instructions advising a <code>git pull</code> after initial boot-up | ||
** Vagrant defaults are probably fine for CI use case | |||
=== Blank slate content === | === Blank slate content === | ||
| Line 53: | Line 58: | ||
* Synthetic test data | * Synthetic test data | ||
** Need to hand-maintain | ** Need to hand-maintain | ||
** CI use case provides test data | |||
=== Local hardware vs Rackspace VM? === | === Local hardware vs Rackspace VM? === | ||
| Line 59: | Line 65: | ||
* Running a VM on Rackspace costs $$$ | * Running a VM on Rackspace costs $$$ | ||
** How to get an image loaded into a Rackspace VM? | ** How to get an image loaded into a Rackspace VM? | ||
* CI use case requires Jenkins server to be able to run Vagrant | |||
** Finding the right mix of CentOS / Ruby / vagrant gem / VirtualBox is challanging | |||
== Participating sites == | == Participating sites == | ||
| Line 65: | Line 73: | ||
* SUMO? | * SUMO? | ||
* Socorro | * Socorro | ||
* Mozillians | * Mozillians | ||
* MDN? | * MDN? | ||
** Need proper hosting | ** Need proper hosting | ||
| Line 73: | Line 81: | ||
* AUS | * AUS | ||
* Graphserver | * Graphserver | ||
* sasl-browserid | |||
== Maintaining VM images == | == Maintaining VM images == | ||