diff options
| author |   Tim Rozet <trozet@redhat.com> | 2017-03-30 22:08:05 -0400 |
|---|---|---|
| committer | Tim Rozet <trozet@redhat.com> | 2017-03-30 22:08:05 -0400 |
| commit | 1d655538cfe9a665c5e12dc8b910ddaaae21bae7 (patch) | |
| tree | a218adbac3b93b0b71463a7c2b674850725403f4 /docs/release/installation/baremetal.rst | |
| parent | 28529146f87e5b725616c6574e69697410975f77 (diff) | |
More doc updates for Danube
Change-Id: I125548acde034d8c4c85cce93fb001ba06c8ab33
Signed-off-by: Tim Rozet <trozet@redhat.com>
Diffstat (limited to 'docs/release/installation/baremetal.rst')
| -rw-r--r-- | docs/release/installation/baremetal.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/release/installation/baremetal.rst b/docs/release/installation/baremetal.rst index 83cda326..dcee817a 100644 --- a/docs/release/installation/baremetal.rst +++ b/docs/release/installation/baremetal.rst @@ -50,7 +50,7 @@ images provided by the undercloud. These disk images include all the necessary packages and configuration for an OPNFV deployment to execute. Once the disk images have been written to node's disks the nodes will boot locally and execute cloud-init which will execute the final node configuration. This -configuration is largly completed by executing a puppet apply on each node. +configuration is largely completed by executing a puppet apply on each node. Installation High-Level Overview - VM Deployment ================================================ @@ -62,7 +62,7 @@ VM a collection of VMs (3 control nodes + 2 compute for an HA deployment or 1 control node and 1 or more compute nodes for a Non-HA Deployment) will be defined for the target OPNFV deployment. The part of the toolchain that executes IPMI power instructions calls into libvirt instead of the IPMI -interfaces on baremetal servers to operate the power managment. These VMs are +interfaces on baremetal servers to operate the power management. These VMs are then provisioned with the same disk images and configuration that baremetal would be. @@ -235,7 +235,7 @@ help you customize them. (``/etc/opnfv-apex/``). These files are named with the naming convention os-sdn_controller-enabled_feature-[no]ha.yaml. These files can be used in place of the (``/etc/opnfv-apex/deploy_settings.yaml``) file if one suites - your deployment needs. If a pre-built deploy_settings file is choosen there + your deployment needs. If a pre-built deploy_settings file is chosen there is no need to customize (``/etc/opnfv-apex/deploy_settings.yaml``). The pre-built file can be used in place of the (``/etc/opnfv-apex/deploy_settings.yaml``) file. |