From 888bb9cc8c68bf61fddc0ca08a69f764a4012121 Mon Sep 17 00:00:00 2001 From: Martin André Date: Fri, 20 Mar 2015 10:31:02 +0900 Subject: Move genenv.sh and start.sh to tools directory Rename them `genenv` and `start`. Have `genenv` create the openrc file in the top-level directory. Add openrc and compose/openstack.env to gitignore, as well as *.img. Change-Id: I5d8006e97efd77cf364215f55d5e585139ae273e --- docs/developer-env.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) (limited to 'docs') diff --git a/docs/developer-env.md b/docs/developer-env.md index fe1916bb6..3d31aa530 100644 --- a/docs/developer-env.md +++ b/docs/developer-env.md @@ -7,18 +7,18 @@ compose directory. To start, setup your environment variables. $ cd kolla - $ ./tools/genenv.sh + $ ./tools/genenv -The `genenv.sh` script will create an openstack.env file +The `genenv` script will create a compose/openstack.env file and an openrc file in your current directory. The openstack.env file contains all of your initialized environment variables, which you can edit for a different setup. Next, run the start script. - $ ./start.sh + $ ./tools/start -The `start.sh` script is responsible for starting the containers +The `start` script is responsible for starting the containers using `docker-compose -f up -d`. If you want to start a container set by hand use this template @@ -36,7 +36,9 @@ If any of the containers exited you can check the logs by doing $ sudo docker logs $ docker-compose logs -If you want to start a individual service like `glance-api` by hand, then use this template. This is a good method to test and troubleshoot an individual container. +If you want to start a individual service like `glance-api` by hand, then use +this template. This is a good method to test and troubleshoot an individual +container. $ docker run --name glance-api -d \ --net=host -- cgit v1.2.3