Fixed typos.

Change-Id: Ib144270038077ef66d9491a1738c0dad8cbab271
This commit is contained in:
Svetlana Karslioglu 2016-10-27 10:08:45 -07:00
parent 3389596f74
commit 5dbe5d939e
5 changed files with 11 additions and 10 deletions

View File

@ -11,14 +11,15 @@ you can create your own. We strongly recommend that you use the
build your own network template.
.. note::
When you configure a network using network templates, you cannot apply
When you configure a network using a network template, you cannot apply
changes to the nodes network configuration using the Fuel web UI. For
example, if you configure an OpenStack environment using network
templates, deploy the OpenStack environment, and later decide to add
new nodes, you must update network configuration of these nodes using
network templates and do not use the Fuel web-UI. However, templates do
not describe the level 2 and level 3 network settings. Therefore, you
must set them using Fuel web UI, CLI, or API.
new nodes to that environment, you must update network configuration
of these nodes using a network template and do not use the Fuel web UI.
However, templates do not describe the level 2 and level 3 network
settings. Therefore, you must set them using Fuel web UI, CLI, or API.
After uploading a network template, you must create and/or
delete networks and node groups using the Fuel CLI to reflect the uploaded

View File

@ -8,7 +8,7 @@ You can delete a network template that you have previously uploaded.
.. warning::
Do not delete network templates that are used in your OpenStack
environment as it may result in failure of the whole network
environment as it may result in a failure of the whole network
configuration.
**To delete a network template:**

View File

@ -11,7 +11,7 @@ When using network templates, consider the following limitations:
cannot be removed.
* When you use network templates, do not download and modify Fuel
deployment configurations using the ``fuel download`` and
``fuel upload`` commands as it may result in system malfunction.
``fuel upload`` commands as it may result in a system malfunction.
* Mapping of network roles to networks, as well as network topology cannot
be configured for individual nodes. They can only be set for a node role
or/and node group.

View File

@ -7,7 +7,7 @@ A network template is a ``.yaml`` file that contains network configuration
for an OpenStack environment. To apply custom network
configurations, create and configure
the template according to your environment requirements. For your convenience,
use the following :ref:` Network template examples`.
use the following :ref:`network-templates-examples`.
The name of the network template
must follow this convention: ``network_template_<ENV_ID>.yaml``. Verify the

View File

@ -5,10 +5,10 @@ nic_mapping
**Description**
Specifies aliases to network interface names mapping,
Specifies aliases to the network interface names mapping,
for example, ``adm: eth0``. If a node is not listed in this section,
default mapping applies. You can configure custom mapping for
any node by the node name. The number of NICs depends on the
any node using the node name. The number of NICs depends on the
network topology and may vary. Aliases are optional and if
all nodes have the same number of NICs connected in a similar
manner, you can use NIC names instead.