x
/
fuel-plugin-nsxv
Code Issues Proposed changes

Document certificate and nova-api-metadata network settings for 3.0 

- document NSX Manager CA certificate file and drop description of old
  "Bypass NSX Manager certificate verification"
- describe nova-api-metadata network selection drop old "Use management
  network to access the nova-api-metadata" setting
- update screenshot

Change-Id: I529b113434ba2e7100f340ccb9c1334ce4180ba0
This commit is contained in:
Igor Zinovik 2016-05-12 14:06:48 +03:00
parent 6872aa1927
commit cb7f8d5c9c
2 changed files with 16 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
doc/user/image/nsxv-settings-filled.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 93 KiB

After

Width:  |  Height:  |  Size: 121 KiB

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

@ -1,8 +1,9 @@
Configuration
=============
Switch to Networks tab of the Fuel web UI and click on *Settings*/*Other* section,
the plugin checkbox enabled by default.
Switch to Networks tab of the Fuel web UI and click on *Settings*/*Other*
section, the plugin checkbox enabled by default. For reasons of clarity not all
settings are shown on the screenshot below:
.. image:: /image/nsxv-settings-filled.png
:scale: 60 %
@ -30,6 +31,10 @@ Plugin contains the following settings:
#. NSX Manager password.
#. CA certificate file -- file in PEM format that contains bundle of CA
certificates which will be used by Neutron during HTTPS connection to NSX
Manager. If no file is present, then HTTPS connection will not be verified.
#. Datacenter MoRef ID -- ID of Datacenter where NSX Edge nodes will be
deployed.
@ -87,10 +92,15 @@ 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.
#. Bypass NSX Manager certificate verification -- disable this option if you
want Neutron NSX plugin to verify NSX Manager security certificate. *CA
certificate file* setting will appear providing an option to upload
CA certificate which emitted NSX Manager certificate.
#. Which network will be used to access the nova-metadata -- select network
through which nova-api-metadata service will be available for NSX edge
nodes. Currently two options are available *Public* and *Management*
networks.
Subitem "Allocate IP address in management network for NSX metadata proxy"
allows automatically allocate free IP address from management network range
for nova-api-metadata, if you want to specify you own IP address, netmask
and gateway see metadata related settings below.
To enable Nova metadata service, the following settings must be set:
@ -98,14 +108,6 @@ Plugin contains the following settings:
initialize the metadata infrastructure to access to metadata proxy service,
otherwise metadata proxy will not be deployed.
#. Use management network to access the nova-api-metadata -- configure
nova-api-metadata service to listen on OpenStack management network. If
disabled nova-api-metadata will listen on Public network.
#. Allocate IP address in management network for NSX metadata proxy --
automatic IP address allocation, if disabled then user have to manually
specify IP address, netmask and gateway to avoid possible collisions.
#. Certificate for metadata proxy -- certificate in PEM format that will be
used to secure connection between metadata proxy and metadata agent (NSX
Edge).