diff options
| -rw-r--r-- | docs/release/installation/baremetal.rst | 4 | ||||
| -rw-r--r-- | docs/release/installation/virtual.rst | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/docs/release/installation/baremetal.rst b/docs/release/installation/baremetal.rst index 49997f89..17223df0 100644 --- a/docs/release/installation/baremetal.rst +++ b/docs/release/installation/baremetal.rst @@ -88,7 +88,7 @@ Install Bare Metal Jump Host ``sudo yum install https://repos.fedorapeople.org/repos/openstack/openstack-pike/rdo-release-pike-1.noarch.rpm`` ``sudo yum install epel-release`` - ``sudo curl -o /etc/yum/repos.d/opnfv-apex.repo http://artifacts.opnfv.org/apex/euphrates/opnfv-apex.repo`` + ``sudo curl -o /etc/yum.repos.d/opnfv-apex.repo http://artifacts.opnfv.org/apex/euphrates/opnfv-apex.repo`` The RDO Project release repository is needed to install OpenVSwitch, which is a dependency of opnfv-apex. If you do not have external connectivity to @@ -224,7 +224,7 @@ Follow the steps below to execute: network_settings.yaml allows you to customize your networking topology. Note it can also be useful to run the command with the ``--debug`` argument which will enable a root login on the overcloud nodes with - password: 'opnfv-apex'. It is also useful in some cases to surround the + password: 'opnfvapex'. It is also useful in some cases to surround the deploy command with ``nohup``. For example: ``nohup <deploy command> &``, will allow a deployment to continue even if ssh access to the Jump Host is lost during deployment. diff --git a/docs/release/installation/virtual.rst b/docs/release/installation/virtual.rst index 9336b8e7..2da8ccf6 100644 --- a/docs/release/installation/virtual.rst +++ b/docs/release/installation/virtual.rst @@ -80,7 +80,7 @@ Follow the steps below to execute: -n network_settings.yaml -d deploy_settings.yaml`` Note it can also be useful to run the command with the ``--debug`` argument which will enable a root login on the overcloud nodes with - password: 'opnfv-apex'. It is also useful in some cases to surround the + password: 'opnfvapex'. It is also useful in some cases to surround the deploy command with ``nohup``. For example: ``nohup <deploy command> &``, will allow a deployment to continue even if ssh access to the Jump Host is lost during deployment. |