overcloudrc should not be managed by the CLI
Bug #1615720 reported by
Tomas Sedovic
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Dougal Matthews |
Bug Description
The `openstack overcloud deploy` command generates the overcloudrc file which contains the environment variables necessary to interact with the deployed OpenStack.
Right now, that code lives in python-
Generating overcloudrc would be a useful thing for the GUI as well and moving this logic outside of tripleoclient will help reduce the disparity between the command line and web interfaces.
Changed in tripleo: | |
importance: | Undecided → Medium |
tags: | added: tripleoclient |
Changed in tripleo: | |
assignee: | nobody → Dougal Matthews (d0ugal) |
milestone: | ongoing → ocata-1 |
Changed in tripleo: | |
milestone: | ocata-2 → ocata-3 |
To post a comment you must log in.
At the moment tripleoclient creates two different overcloudrc files. overcloudrc and overcloudrc.v3. The second is for KeyStone v3. The two files look like this:
[stack@instack ~]$ cat overcloudrc overcloud 192.0.2. 11:5000/ v2.0 API_VERSION= 1.1 9EgEvRtzKfEVhA7 48mcJcXc8B ,192.0. 2.11,192. 0.2.11 NAME=admin "ignore: Certificate has no, ignore:A true SSLContext object is not available"
# Clear any old environment that may conflict.
for key in $( set | awk '{FS="="} /^OS_/ {print $1}' );do unset $key ; done
export OS_NO_CACHE=True
export OS_CLOUDNAME=
export OS_AUTH_URL=http://
export NOVA_VERSION=1.1
export COMPUTE_
export OS_USERNAME=admin
export OS_PASSWORD=
export no_proxy=
export OS_PROJECT_
export PYTHONWARNINGS=
[stack@instack ~]$ cat overcloudrc.v3 API_VERSION= 1.1 ,192.0. 2.11,192. 0.2.11 DOMAIN_ NAME=Default DOMAIN_ NAME=Default overcloud 192.0.2. 11:5000/ v3 NAME=admin API_VERSION= 3 9EgEvRtzKfEVhA7 48mcJcXc8B "ignore: Certificate has no, ignore:A true SSLContext object is not available"
# Clear any old environment that may conflict.
for key in $( set | awk '{FS="="} /^OS_/ {print $1}' );do unset $key ; done
export OS_NO_CACHE=True
export COMPUTE_
export OS_USERNAME=admin
export no_proxy=
export OS_USER_
export OS_PROJECT_
export OS_CLOUDNAME=
export OS_AUTH_URL=http://
export NOVA_VERSION=1.1
export OS_PROJECT_
export OS_IDENTITY_
export OS_PASSWORD=
export PYTHONWARNINGS=
so they are similar, but contain a few obvious differences. How should this be handled from Mistral? Should be action return JSON with both? Something like this?
{"overcloudrc": "....", "overcloudrc.v3": "...."}