openstack/openstack-helm
Code Issues Proposed changes

Fix typos in all-in-one code example and add auth info

Browse Source 
This PS simply fixes a few typos in an all-in-one code block
example dedicated to setting up the gateway. It also adds
additional information about how to set up auth information
to use the python-openstackclient.

Change-Id: Ie9cc63d3d435c474c3cbda90964f2eababa81139
This commit is contained in:
Felipe Monteiro 2018-01-13 20:12:11 -05:00 committed by Tin Lam
parent da77f2118b
commit aaff2ce6ba
2 changed files with 23 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/source/install/developer/all-in-one.rst
View File

@ -356,6 +356,26 @@ Alternatively, this step can be performed by running the script directly:
./tools/deployment/developer/19-use-it.sh ./tools/deployment/developer/19-use-it.sh
To run further commands from the CLI manually, execute the following to
set up authentication credentials::
export OS_CLOUD=openstack_helm
Note that this command will only enable you to auth successfully using the
``python-openstackclient`` CLI. To use legacy clients like the
``python-novaclient`` from the CLI, reference the auth values in
``/etc/openstack/clouds.yaml`` and run::
export OS_USERNAME='admin'
export OS_PASSWORD='password'
export OS_PROJECT_NAME='admin'
export OS_PROJECT_DOMAIN_NAME='default'
export OS_USER_DOMAIN_NAME='default'
export OS_AUTH_URL='http://keystone.openstack.svc.cluster.local/v3'
The example above uses the default values used by ``openstack-helm-infra``.
Removing Helm Charts Removing Helm Charts
==================== ====================

6
tools/deployment/developer/16-setup-gateway.sh
View File

@ -21,9 +21,9 @@ OSH_EXT_SUBNET="172.24.4.0/24"
sudo ip addr add ${OSH_BR_EX_ADDR} dev br-ex sudo ip addr add ${OSH_BR_EX_ADDR} dev br-ex
sudo ip link set br-ex up sudo ip link set br-ex up
# NOTE(portdirect): With Docker >= 1.13.1 the default the default FORWARD chain # NOTE(portdirect): With Docker >= 1.13.1 the default FORWARD chain policy is
# policy is configured to DROP, for the l3 agent to function as expected and # configured to DROP, for the l3 agent to function as expected and for
# VMs reach the outside world correctly this needs to be set to ACCEPT. # VMs to reach the outside world correctly this needs to be set to ACCEPT.
sudo iptables -P FORWARD ACCEPT sudo iptables -P FORWARD ACCEPT
# Setup masquerading on default route dev to public subnet # Setup masquerading on default route dev to public subnet