x
/
fuel-plugin-nsxv
Code Issues Proposed changes

Describe settings that must not be changed after cluster deployment 

Mention that Fuel 9.0 can run deployment process on working cluster.
Explicitly state that metadata changes made after successfull cluster
deployment are prohibited.

Fix two minor nits.

Change-Id: Iebd7710104bd83533161904b16a8459905f798d3
This commit is contained in:
Igor Zinovik 2016-07-01 13:27:03 +03:00
parent 88dfc65c7b
commit 14bd126b9c
2 changed files with 17 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/user/source/configuration.rst
View File

@ -8,10 +8,17 @@ settings are shown on the screenshot below:
.. image:: /image/nsxv-settings-filled.png
:scale: 60 %
Several plugins input fields refer to MoRef ID (Managed Object Reference ID),
Several plugin input fields refer to MoRef ID (Managed Object Reference ID),
these object IDs can be obtained via Managed Object Browser which is located on
the vCenter host, e.g. https://<vcenter_host>/mob
Starting from Fuel 9.0 settings on web UI are not disabled and it is possible
to run deployment process with changed settings against working cluster. This
change also impacts plugin settings which means that plugin settings can be
changed and applied to Neutron. From plugin perspective it is not possible to
disable specific input fields, below settings that break Neutron operations are
commented.
Plugin contains the following settings:
#. NSX Manager hostname (or IP) -- if you are going to use hostname in this
@ -50,8 +57,10 @@ Plugin contains the following settings:
deployed.
#. Resource pool MoRef ID -- resource pool for NSX Edge nodes deployment.
Setting change on deployed cluster affects only new Edges.
#. Datastore MoRef ID -- datastore for NSX Edge nodes.
#. Datastore MoRef ID -- datastore for NSX Edge nodes. Change of datastore
setting on deployed cluster affects only new Edges.
#. External portgroup MoRef ID -- portgroup through which NSX Edge nodes get
connectivity with physical network.
@ -102,6 +111,7 @@ Plugin contains the following settings:
#. Enable HA for NSX Edges -- if you enable this option NSX Edges will be
deployed in active/standby pair on different ESXi hosts.
Setting change on deployed cluster affects only new Edges.
#. Which network will be used to access the nova-metadata -- select network
through which nova-api-metadata service will be available for NSX edge
@ -115,6 +125,10 @@ Plugin contains the following settings:
If *Public* network selected, then you need to specify you own IP address, netmask
and gateway. See metadata related settings below.
.. warning::
Do not change metadata settings after cluster is deployed!
To enable Nova metadata service, the following settings must be set:
#. Init metadata infrastructure -- If enabled, instance will attempt to

2
doc/user/source/environment.rst
View File

@ -23,7 +23,7 @@ these steps:
.. image:: /image/wizard-step2.png
:scale: 70 %
#. Once you get environment created add one or more controller node.
#. Once you get environment created add one or more controller nodes.
Pay attention on which interface you assign *Public* network, OpenStack
controllers must have connectivity with NSX Manager host through *Public*