2aa4faca0f
Add two changes from the main Vagrantfile also to the Vagrantfiles in ds-build and split. * Id3aeaa16e062f764412bd6c5fd9460b5867333a9 (vagrant-cachier) * Ie615cf81be40b8395d8e7672e59407cc4925b410 (vagrant-berkshelf) Change-Id: I2309db433c547736732217ffcd1e1f440d1684ab |
||
|---|---|---|
| .. | ||
| roles | ||
| README.md | ||
| Vagrantfile | ||
The ds-build Vagrant profile installs the latest DevStack onto an Ubuntu Trusty virtual machine, activating extra services and setting it up to run out of Upstart rather than screen sessions.
Default admin credentials are username admin and password admin.
Services Enabled
The following services are enabled:
- Ceilometer
- Cinder
- Glance
- Heat
- Horizon
- Keystone
- Neutron
- Nova
- Swift
Note that with Neutron, Q_PLUGIN is set to linuxbridge rather than
openvswitch.
Upstart instead of screen
The cookbook includes a script which creates Upstart init scripts for each of
the services. It also sets up log files in the /var/log/ directory. When
the VM is booted, all DevStack processes will start automatically.
Usage
Initial build
From within this directory, run this command to build the server:
vagrant up
The DevStack installation will take a long time, and you can follow its
progress from another terminal by running vagrant ssh and then
tail -f /opt/stack/logs/stack.sh.log
Packaging for VagrantCloud
From within the ds-build directory, run this command to build a new
VagrantCloud box image after vagrant up completed successfully:
box='devstack.box'; [ -e ../$box ] && rm -v ../$box ; vagrant package devstack --output $box