Various documantation fixes

Change-Id: I122f2384dd50123bdde946fdd052a814dd48701e
This commit is contained in:
Samir Ibradžić 2016-07-01 16:31:34 +09:00
parent a1ca5e802e
commit 196ad915d9
7 changed files with 59 additions and 7 deletions

Binary file not shown.

Binary file not shown.

View File

@ -42,7 +42,7 @@ Known Limitations
* Current version of plugin can only deploy single MidoNet Gareway role node.
MidoNet itself supports any number of gateway nodes, it is only a plugin
limitation, additional nodes needs to be set up manually.
limitation, additional nodes needs to be set up manually.
.. _v2015.06: https://github.com/midonet/midonet/tree/stable/v2015.06.2
.. _MEM: http://docs.midokura.com/docs/latest/manager-guide/content/index.html

View File

@ -289,3 +289,21 @@ messages, they should either be included in MidoNet support claims to help
to help the troubleshooting or an action can be taken by user to prevent issue
from happening on re-deployment.
Note on Fuel upgrades
`````````````````````
Fuel provides special mechanism for upgrading locally hosted (usually on a Fuel
master node itself) Operating System as well as OpenStack repositories. This is
achieved with executing following commands on Fuel master node (assuming
environment number 1 deployed on nodes 2, 3, 4, 5 and 6):
::
# fuel-createmirror -M
# fuel --env 1 node --node-id 2 3 4 5 6 --tasks upload_core_repos
For deployments based on MidoNet this will cause Neutron services to be restarted.
This is an expected behavior, and it will not affect network functionality on VMs,
virtual routers or gateways.

View File

@ -120,13 +120,13 @@ Gateway role
::
name: midonet-gw
meta:
name: midonet-gw
meta:
name: MidoNet HA Gateway
description: MidoNet Gateway
volumes_roles_mapping:
- allocate_size: min
id: os
description: MidoNet Gateway
volumes_roles_mapping:
- allocate_size: min
id: os
#. Create the role for the environment (``Ubuntu 2015.1.0-7.0``) using the
`Fuel CLI <https://docs.mirantis.com/openstack/fuel/fuel-7.0/user-guide.html#using-fuel-cli>`_:
@ -238,3 +238,32 @@ follow these steps:
.. _Experimental Features: https://docs.mirantis.com/openstack/fuel/fuel-7.0/operations.html#enable-experimental-features
.. _Fuel Plugin Catalog: https://www.mirantis.com/products/openstack-drivers-and-plugins/fuel-plugins/
Verifying installation
----------------------
MidoNet MEM Fuel Plugin replaces Neutron default OpenvSwitch networking plugin in a
typical OpenStack deployment based on Neutron. Therefore, the goal of the verifying
the system that has just been deployed is to to ensure that plugin installation was
successful as well to ensure that OpenStack Neutron networking supported by MidoNet
is fully functional. Basic fuel OSTF health check provides a solid base for
verifying basic OpenStack as well as MidoNet functionality, it is highly advised
to make sure that this particular set of OSTF tests are passing correctly:
#. Sanity tests:
- Request list of networks
#. Functional tests:
- Check network connectivity from instance via floating IP (requires functional BGP setup)
- Check network parameters
- Launch instance with file injection (requires functional BGP setup)
|
Although the list is somewhat short, executing these functional tests successfully will
ensure that a larger set of MidoNet functionality is operating correctly. Just to mention
few: MidoNet NSDB, MidoNet REST API, MidoNet Neutron plugin integration, MidoNet
networking agents, MidoNet BGP gateway including Floating IPs.

View File

@ -41,6 +41,11 @@ Revision history
0.3 07.03.2016 Samir Ibradzic Added release notes
and troubleshooting
(samir@midokura.com)
0.3a 29.06.2016 Samir Ibradzic Formating fixes,
added "Verifying
installtion" and "Note
on Fuel Upgrades" sections
(samir@midokura.com)
========= =============== ========================== =========================
.. raw:: pdf