Update standalone documentation

Since the merging of I6713469bfbd4fe9fc47d3cb2d3571fe10871f34e and
I0496f4dd2026ab6c705683126c8f50302a0861b9, the default role includes a
basic full cloud deployment and creates a clouds.yaml for the root user.
Update the documentation to include this information and how to leverage
the clouds.yaml.

Change-Id: I2c31e80000e55e70db26c24147e349d8ccd4d273
Related-Blueprint: all-in-one
This commit is contained in:
Alex Schultz 2018-07-10 20:47:47 -06:00
parent dd98f0dbff
commit 1f053673ef

View File

@ -167,50 +167,13 @@ Deploying a Standalone Keystone node
--output-dir $HOME \
--standalone
#. Validate Keystone services
#. Check the deployed OpenStack Services
You can validate the Keystone is running by fetching a token::
At the end of the deployment, a clouds.yaml configuration file is placed in
the /root/.config/openstack folder. This can be used with the openstack
client to query the OpenStack services.
# validate keystone
export ADMIN_PASS=$(egrep "^[[:space:]]+AdminPassword:" $HOME/tripleo-undercloud-passwords.yaml | awk '{print $2}')
.. code-block:: bash
KEYSTONE_PAYLOAD=$(cat <<EOF
{ "auth": {
"identity": {
"methods": ["password"],
"password": {
"user": {
"name": "admin",
"domain": { "id": "default" },
"password": "$ADMIN_PASS"
}
}
}
}
}
EOF
)
curl -i \
-H "Content-Type: application/json" \
-d "$KEYSTONE_PAYLOAD" \
"http://$IP:5000/v3/auth/tokens" ; echo
#. Create clouds.yaml for use with openstackclient
You can create a clouds.yaml which allows you to use the openstackclient::
mkdir -p ~/.config/openstack
cat <<EOF >~/.config/openstack/clouds.yaml
clouds:
standalone:
auth:
auth_url: http://$IP:5000/
project_name: admin
username: admin
password: $ADMIN_PASS
region_name: regionOne
identity_api_version: 3
EOF
export OS_CLOUD=standalone
openstack endpoint list
export OS_CLOUD=standalone
openstack endpoint list