MOS can be used with NSX cluster that lacks Service nodes
- remove warning that says that NSX Service node is mandatory for Mirantis OpenStack - add note about fact that NSX Service node is mandatory for high volume environments - update screenshot with NSX settings block that shows new checkbox Change-Id: I196f1b6353b8a64ba221d93f0622f6d3859dc9ea Partial-bug: #1365043
This commit is contained in:
Binary file not shown.
|
Before Width: | Height: | Size: 50 KiB After Width: | Height: | Size: 51 KiB |
@@ -34,26 +34,23 @@ VMware NSX Installation
|
||||
Before installing Fuel and using it
|
||||
to create a Mirantis OpenStack environment
|
||||
that is integrated with VMware NSX,
|
||||
the VMware NSX installation must be up and running.
|
||||
the VMware NSX installation must be installed and running.
|
||||
Please check that you completed the following steps:
|
||||
|
||||
|
||||
* Install NSX Controller node
|
||||
* Install NSX Gateway node
|
||||
* Install NSX Manager node
|
||||
* Install NSX Service node
|
||||
|
||||
.. note:: According to VMware documentation, an NSX cluster can operate
|
||||
successfully without an NSX Service node, but its presence is
|
||||
mandatory for deploying Mirantis OpenStack. Support of NSX clusters
|
||||
without a Service node might appear in future versions of Fuel.
|
||||
* Install NSX Service node (you may skip this step if you are going to test
|
||||
NSX cluster; Service nodes are mandatory for high volume traffic
|
||||
environments)
|
||||
|
||||
VMware NSX cluster configuration
|
||||
--------------------------------
|
||||
|
||||
* Configure NSX Controller
|
||||
|
||||
* Assign IP address to NSX controller. If the controller is going
|
||||
* Assign an IP address to the NSX controller. If the controller is going
|
||||
to be placed in any of the OpenStack :ref:`logical
|
||||
networks<logical-networks-arch>` (Public, Management, Storage),
|
||||
you must assign an IP address that does not overlap
|
||||
|
||||
Reference in New Issue
Block a user