starlingx
/
docs
Code Issues Proposed changes

Merge "Installation: "Mad" Legacy Naming Change"

This commit is contained in:
Zuul 2019-02-06 22:41:57 +00:00 committed by Gerrit Code Review
parent 35484012d9 482f08ade5
commit f98abfae09
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/source/installation_guide/installation_libvirt_qemu.rst
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
****************************************