Change UserGuide and TestPlan for 3.1
Change-Id: I953e5ef0d4f2beb81aba9b1b2b96f3ccd6bc3338
This commit is contained in:
Igor Gajsin
parent
738ad6c396
commit
75df65724f
|
|
@ -63,9 +63,9 @@ copyright = u'2016, Mirantis Inc.' # noqa
|
|||
# built documents.
|
||||
#
|
||||
# The short X.Y.Z version.
|
||||
version = '3.0.0'
|
||||
version = '3.1.0'
|
||||
# The full version, including alpha/beta/rc tags.
|
||||
release = '3.0-3.0.0-1'
|
||||
release = '3.1-3.1.0-1'
|
||||
|
||||
# The language for content autogenerated by Sphinx. Refer to documentation
|
||||
# for a list of supported languages.
|
||||
|
|
|
|||
|
|
@ -1384,7 +1384,7 @@ Steps
|
|||
4. Configure interfaces on nodes.
|
||||
5. Configure network settings.
|
||||
6. Enable and configure DVS plugin with multiple uplinks.
|
||||
In format "luster:VDS:TU1;TU2;TU3".
|
||||
In format "Cluster:VDS:TU1;TU2;TU3".
|
||||
7. Enable VMware vCenter/ESXi datastore for images (Glance).
|
||||
8. Configure VMware vCenter Settings. Add 2 vSphere clusters and configure
|
||||
Nova Compute instances on controllers and compute-vmware.
|
||||
|
|
@ -1521,4 +1521,4 @@ Expected result
|
|||
###############
|
||||
|
||||
After disabling two of three teaming uplinks instances are alive and functioning.
|
||||
All OSTF tests passed.
|
||||
All OSTF tests passed.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
=============================================
|
||||
Test Plan for VMware DVS plugin version 3.0.0
|
||||
Test Plan for VMware DVS plugin version 3.1.0
|
||||
=============================================
|
||||
|
||||
************
|
||||
|
|
@ -69,7 +69,7 @@ Product compatibility matrix
|
|||
- Version
|
||||
- Comment
|
||||
* - MOS
|
||||
- 9.0 with Mitaka
|
||||
- 9.1 with Mitaka
|
||||
-
|
||||
* - Operating System
|
||||
- Ubuntu 14.04
|
||||
|
|
@ -94,7 +94,7 @@ Evaluation Mission and Test Motivation
|
|||
The main goal of the project is to build a MOS plugin that integrates
|
||||
the Neutron ML2 Driver For VMware vCenter DVS. This will allow to use Neutron
|
||||
for networking in VMware-related environments. The plugin must be compatible
|
||||
with the version 9.0 of Mirantis OpenStack and should be tested with the
|
||||
with the version 9.1 of Mirantis OpenStack and should be tested with the
|
||||
software/hardware described in `product compatibility matrix`_.
|
||||
|
||||
See the VMware DVS Plugin specification for more details.
|
||||
|
|
|
|||
Binary file not shown.
|
Before Width: | Height: | Size: 20 KiB After Width: | Height: | Size: 34 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 56 KiB After Width: | Height: | Size: 79 KiB |
|
|
@ -64,9 +64,9 @@ copyright = u'2016, Mirantis Inc.' # noqa
|
|||
# built documents.
|
||||
#
|
||||
# The short X.Y version.
|
||||
version = '3.0.0'
|
||||
version = '3.1.0'
|
||||
# The full version, including alpha/beta/rc tags.
|
||||
release = '3.0-3.0.0-1'
|
||||
release = '3.1-3.1.0-1'
|
||||
|
||||
# The language for content autogenerated by Sphinx. Refer to documentation
|
||||
# for a list of supported languages.
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ creating an environment in Fuel and modifying the environment settings.
|
|||
|
||||
\pagebreak
|
||||
|
||||
3. In the :guilabel:`Networking Setup` menu, select
|
||||
#. In the :guilabel:`Networking Setup` menu, select
|
||||
:guilabel:`Neutron with VMware DVS`:
|
||||
|
||||
.. figure:: _static/net.png
|
||||
|
|
@ -47,15 +47,31 @@ creating an environment in Fuel and modifying the environment settings.
|
|||
|
||||
\pagebreak
|
||||
|
||||
6. In the :guilabel:`Networks` tab, click :guilabel:`Other`:
|
||||
#. In the :guilabel:`Networks` tab, click :guilabel:`Other`:
|
||||
|
||||
#. Select the :guilabel:`Neutron VMware DVS ML2 plugin` checkbox.
|
||||
#. Specify the :guilabel:`Cluster to VDSwitch mapping`.
|
||||
#. Specify the :guilabel:`Cluster to VDSwitch mapping`. Please notice that
|
||||
in the 3.1 release it has new format:
|
||||
|
||||
#. New string is used as a delimiter between clusters.
|
||||
#. There are 2 new columns: list of teaming uplinks and list of fallback
|
||||
uplinks. Both are optional.
|
||||
#. The semicolon is used as a delimiter between uplinks.
|
||||
#. There is no limitation for amount of uplinks.
|
||||
#. Thereby there are next options for a mapping-string:
|
||||
|
||||
#. ClusterName:VDSName:TeamingUplink1;TeamingUplink2:FallBackUplink1;FallBackUplink2
|
||||
#. ClusterName:VDSName:TeamingUplink1;TeamingUplink2;...;TeamingUplinkN
|
||||
#. ClusterName:VDSName
|
||||
|
||||
#. There is no option to set fallback uplinks without teaming uplinks.
|
||||
#. All uplinks should be presented on real VDS.
|
||||
#. If you want to use security groups on your ports, select
|
||||
:guilabel:`Use the VMware DVS firewall driver`.
|
||||
|
||||
.. figure:: _static/settings.png
|
||||
:width: 90%
|
||||
See the `Teaming and Failover Policy <https://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.networking.doc/GUID-4D97C749-1FFD-403D-B2AE-0CD0F1C70E2B.html>`__ for more detail about uplinks usage on VDS.
|
||||
|
||||
.. caution::
|
||||
The VMware DVS ML2 plugin does not support the Distributed Virtual
|
||||
|
|
@ -66,7 +82,7 @@ creating an environment in Fuel and modifying the environment settings.
|
|||
|
||||
\pagebreak
|
||||
|
||||
7. In the :guilabel:`VMware` tab, fill in the VMware configuration fields:
|
||||
#. In the :guilabel:`VMware` tab, fill in the VMware configuration fields:
|
||||
|
||||
.. figure:: _static/vmware.png
|
||||
:width: 90%
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ Before you proceed with the VMware DVS plugin installation, verify that:
|
|||
|
||||
.. code-block:: console
|
||||
|
||||
$ scp fuel-plugin-vmware-dvs-3.0-3.0.0-1.noarch.rpm <Fuel Master node ip>:/tmp
|
||||
$ scp fuel-plugin-vmware-dvs-3.1-3.1.0-1.noarch.rpm <Fuel Master node ip>:/tmp
|
||||
|
||||
#. Log in to the Fuel Master node CLI as root.
|
||||
|
||||
|
|
@ -28,7 +28,7 @@ Before you proceed with the VMware DVS plugin installation, verify that:
|
|||
|
||||
.. code-block:: console
|
||||
|
||||
# fuel plugins --install /tmp/fuel-plugin-vmware-dvs-3.0-3.0.0-1.noarch.rpm
|
||||
# fuel plugins --install /tmp/fuel-plugin-vmware-dvs-3.1-3.1.0-1.noarch.rpm
|
||||
|
||||
#. Verify that the plugin was installed successfully:
|
||||
|
||||
|
|
@ -39,11 +39,11 @@ Before you proceed with the VMware DVS plugin installation, verify that:
|
|||
+------+--------------------------+-----------+--------------------+
|
||||
| id | name | version | package\_version |
|
||||
+------+--------------------------+-----------+--------------------+
|
||||
| 2 | fuel-plugin-vmware-dvs | 3.0.0 | 4.0.0 |
|
||||
| 2 | fuel-plugin-vmware-dvs | 3.1.0 | 4.0.0 |
|
||||
+------+--------------------------+-----------+--------------------+
|
||||
|
||||
#. Proceed to :ref:`configure_env`.
|
||||
|
||||
.. raw:: latex
|
||||
|
||||
\pagebreak
|
||||
\pagebreak
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@ Introduction
|
|||
------------
|
||||
|
||||
The purpose of this document is to describe how to install, configure,
|
||||
and use the VMware DVS plugin 3.0.0 for Fuel 9.0.
|
||||
and use the VMware DVS plugin 3.1.0 for Fuel 9.1.
|
||||
|
||||
Mirantis OpenStack supports using vCenter as a hypervisor on vCenter-only or
|
||||
heterogeneous environments that are mixed with KVM. The vmware_dvs driver for
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
Limitations
|
||||
-----------
|
||||
|
||||
The VMware DVS plugin 3.0.0 for Fuel has the following limitations:
|
||||
The VMware DVS plugin 3.1.0 for Fuel has the following limitations:
|
||||
|
||||
* The plugin is enabled only on environments with Neutron as the
|
||||
networking option.
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ Before you install and start using the VMware DVS plugin on Fuel, complete the
|
|||
following steps:
|
||||
|
||||
#. Install and set up
|
||||
`Fuel 9.0 <http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide.html>`__.
|
||||
`Fuel 9.1 <http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide.html>`__.
|
||||
|
||||
#. Plan the vSphere integration. For details, see
|
||||
`Mirantis OpenStack Planning Guide <https://docs.mirantis.com/openstack/fuel/fuel-9.0/mos-planning-guide.html#plan-the-vsphere-integration>`_.
|
||||
|
|
|
|||
|
|
@ -1,13 +1,6 @@
|
|||
Release notes
|
||||
-------------
|
||||
|
||||
The VMware DVS plugin 3.0.0 contains the following updates:
|
||||
The VMware DVS plugin 3.1.0 contains the following updates:
|
||||
|
||||
* Added a new consistent engine for remote security groups.
|
||||
|
||||
* Enhanced the VMware DVS plugin stability, especially when multiple tasks
|
||||
run simultaneously.
|
||||
|
||||
* Improved the VMware DVS plugin overall performance.
|
||||
|
||||
* Improved the VMware DVS plugin documentation.
|
||||
* Added support of multiple uplinks on VDS.
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ To uninstall VMware DVS plugin, follow the steps below:
|
|||
|
||||
.. code-block:: console
|
||||
|
||||
# fuel plugins --remove fuel-plugin-vmware-dvs==3.0.0
|
||||
# fuel plugins --remove fuel-plugin-vmware-dvs==3.1.0
|
||||
|
||||
#. Verify whether the VMware DVS plugin was uninstalled successfully:
|
||||
|
||||
|
|
@ -27,4 +27,4 @@ To uninstall VMware DVS plugin, follow the steps below:
|
|||
|
||||
.. raw:: latex
|
||||
|
||||
\pagebreak
|
||||
\pagebreak
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
Requirements
|
||||
------------
|
||||
|
||||
The VMware DVS plugin 3.0.0 for Fuel has the following requirements:
|
||||
The VMware DVS plugin 3.1.0 for Fuel has the following requirements:
|
||||
|
||||
* Fuel 9.0 on Mitaka
|
||||
* Fuel 9.1 on Mitaka
|
||||
* vCenter 5.5/6.0
|
||||
|
|
|
|||
Loading…
Reference in New Issue