Implement kolla-compose script
Renamed kolla script to kolla-compose Update change in the dev guide also Change-Id: I6cae3d13752ecb4bb3deeb91c5e0f827fde80c2a Implements: blueprint kolla-compose-script
This commit is contained in:
parent
3b394581ab
commit
e245eb2ff5
@ -7,7 +7,7 @@ installation of openstack. Running the 'tools/genenv' script creates an
|
||||
'openrc' to allow access to the installation.
|
||||
|
||||
Once you have run that you can either manually start the containers using the
|
||||
'docker-compose' command or try the 'tools/kolla start' script which tries to
|
||||
'docker-compose' command or try the 'tools/kolla-compose start' script which tries to
|
||||
start them all in a reasonable order, waiting at key points for services to
|
||||
become available. Once stood up you can issue the typical openstack commands
|
||||
to use the installation. If using nova networking use:
|
||||
|
@ -120,7 +120,7 @@ you can edit for a different setup.
|
||||
|
||||
Next, run the start script.
|
||||
|
||||
$ ./tools/kolla start
|
||||
$ ./tools/kolla-compose start
|
||||
|
||||
The `start` script is responsible for starting the containers
|
||||
using `docker-compose -f <osp-service-container> up -d`.
|
||||
|
@ -90,11 +90,11 @@ interface name in `compose/openstack.env`:
|
||||
|
||||
Next, run the start command:
|
||||
|
||||
$ sudo ./tools/kolla start
|
||||
$ sudo ./tools/kolla-compose start
|
||||
|
||||
Finally, run the status command:
|
||||
|
||||
$ sudo ./tools/kolla status
|
||||
$ sudo ./tools/kolla-compose status
|
||||
|
||||
This will display information about all Kolla containers.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user