Installation: "Mad" Legacy Naming Change

"Mad" is a legacy name used for StarlingX deployments, let's change
to "Stx".

Story: 2004794
Task: 29033

Depends-On: https://review.openstack.org/#/c/612826
Change-Id: I6aa98d86c6929d453f351ad9ccc5bf0bf83385fe
Co-authored-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Abraham Arce <abraham.arce.moreno@intel.com>
This commit is contained in:
Abraham Arce 2019-01-22 03:55:12 -06:00
parent 76eb2822ee
commit 482f08ade5
1 changed files with 8 additions and 8 deletions

View File

@ -47,14 +47,14 @@ These scripts are configured using environment variables that all have
built-in defaults. On shared systems you probably do not want to use the
defaults. The simplest way to handle this is to keep an rc file that can
be sourced into an interactive shell that configures everything. Here's
an example called madcloud.rc:
an example called stxcloud.rc:
::
export CONTROLLER=madcloud
export COMPUTE=madnode
export STORAGE=madstorage
export BRIDGE_INTERFACE=madbr
export CONTROLLER=stxcloud
export COMPUTE=stxnode
export STORAGE=stxstorage
export BRIDGE_INTERFACE=stxbr
export INTERNAL_NETWORK=172.30.20.0/24
export INTERNAL_IP=172.30.20.1/24
export EXTERNAL_NETWORK=192.168.20.0/24
@ -86,7 +86,7 @@ Clone the stx-tools project into a working directory.
git clone git://git.openstack.org/openstack/stx-tools.git
It will be convenient to set up a shortcut to the deployment script
It is convenient to set up a shortcut to the deployment script
directory:
::
@ -94,11 +94,11 @@ directory:
SCRIPTS=$(pwd)/stx-tools/deployment/libvirt
Load the configuration (if you created one) from madcloud.rc:
If you created a configuration, load it from stxcloud.rc:
::
source madcloud.rc
source stxcloud.rc
****************************************