Tip for single interface runs that are started remotely
Change-Id: I6e2870b5c409dd81a34cd9934f540d9558642f91
This commit is contained in:
parent
6fff3cc035
commit
6b1f49910e
@ -19,6 +19,18 @@ physical interface can be used to transmit tenant network traffic,
|
|||||||
the OpenStack API traffic, and management traffic.
|
the OpenStack API traffic, and management traffic.
|
||||||
|
|
||||||
|
|
||||||
|
.. warning::
|
||||||
|
|
||||||
|
When using a single interface networking setup, there will be a
|
||||||
|
temporary network outage as your IP address is moved from the
|
||||||
|
physical NIC of your machine, to the OVS bridge. If you are SSH'd
|
||||||
|
into the machine from another computer, there is a risk of being
|
||||||
|
disconnected from your ssh session (due to arp cache
|
||||||
|
invalidation), which would stop the stack.sh or leave it in an
|
||||||
|
unfinished state. In these cases, start stack.sh inside its own
|
||||||
|
screen session so it can continue to run.
|
||||||
|
|
||||||
|
|
||||||
Physical Network Setup
|
Physical Network Setup
|
||||||
----------------------
|
----------------------
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user