doc: fix typo and slight wording order for networking
There was a hanging ` but at the same time having two blocks of fixed width text next to each other it led to some user confusion so reflowed it to be a bit more clear. Change-Id: I1f326bf8f6807c8ce1967d954d1b643f31fbaba3 Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
This commit is contained in:
parent
8bbfb60f85
commit
1b2482c83a
@ -171,11 +171,11 @@ After provisioning work has been completed, and prior to the node being
|
||||
moved to the ``ACTIVE`` ``provision_state``, the previously attached ports
|
||||
are unbound.
|
||||
|
||||
In the case of the ``flat`` ``network_interface```, the requested VIF(s)
|
||||
In the case of the ``network_interface`` set to ``flat``, the requested VIF(s)
|
||||
utilized for all binding configurations in all states.
|
||||
|
||||
In the case of the ``neutron`` ``network_interface``, the user requested VIFs
|
||||
are attached to the Ironic node for the first time, as the time spent in
|
||||
In the case of the ``network_interface`` set to ``neutron``, the user requested
|
||||
VIFs are attached to the Ironic node for the first time, as the time spent in
|
||||
the *provisioning network* was utilizing VIFs which Ironic created and then
|
||||
deleted as part of the baremetal node's movement through the state machine.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user