stackforge/packstack-vagrant
Code Issues Proposed changes
Files
42efdf94fd8bb9a05b21eb04b729378baca38ce2
packstack-vagrant/doc/source/initialization.rst
Christian Berendt 42efdf94fd Cleanup files and improve Vagrantfile 
* integrate bootstrap.sh into the Vagrantfile
* remove deprecated patches
* remove unused files
* remove support for local Squid installation
* fix several syntax issues identified by Rubocop

Change-Id: I45d7aada7a9c5d1b7affcc3e3d246bebecd02fc4
2015-02-24 07:46:04 +01:00

753 B
Raw Blame History

Initialization

$ vagrant up

Afterwards run the following command on the controller node as the unprivileged user vagrant (vagrant ssh controller) to deploy OpenStack with Packstack.

$ packstack --answer-file packstack.answers

Run packstack with --debug to enable debug logging.

$ packstack --debug --answer-file packstack.answers
  • The installation log file is available at: /var/tmp/packstack/YYMMDD-HHMMSS-abcdef/openstack-setup.log
  • The generated manifests are available at: /var/tmp/packstack/YYMMDD-HHMMSS-abcdef/manifests

Finally (optional) you can run the setup.sh script after the successful deployment to add cloud images etc. pp.

$ ./scripts/setup.sh