65dce2a8c2
* force the removal of existing nodes * send generated log message to STDOUT and to a logfile * fix a typo (bringign --> bringing) * add a note to the documentation where to find the log files * add a note to the documentation about the running time * print the status of all VMs at the end Change-Id: I29e9b0cb482188345345527e09b248eb8b0b52d7
38 lines
982 B
ReStructuredText
38 lines
982 B
ReStructuredText
Initialization
|
|
==============
|
|
|
|
First run the ``bootstrap.sh`` script to prepare all required nodes.
|
|
|
|
::
|
|
|
|
$ ./scripts/bootstrap.sh
|
|
|
|
- A logfile for each node will be created in the directory ``log``.
|
|
- It will take a long time (approximately 30 minutes, depends on your
|
|
local environment) to boostrap all required nodes.
|
|
|
|
Afterwards run the following command on the controller node
|
|
(``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``
|
|
|
|
Optionally you can run the ``setup.sh`` script after the successful
|
|
deployment to add cloud images etc. pp.
|
|
|
|
::
|
|
|
|
$ ./scripts/setup.sh
|