* Bump plugin version to 3.0.1
* Update documentation and mention in release notes that plugin version
3.0.1 is compatible with Fuel 9.1
Change-Id: Ibba9cb5297774d9e4c7cf3767e000f68998a1bb7
* Add nsxv_hot: test plan
* Add nsxv_insecure_false: test plan and automation
* Add known issue about ceilometer OSTF fails
Change-Id: I1655570a1f76cf0d772767a10f0cca399e917176
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
* add nsxv_config_ok_metadata_custom_certificate
* add nsxv_config_ok_metadata_self_signed_certificate
* update test plan with new test
nsxv_config_ok_metadata_self_signed_certificate
* update test plan: rename nsxv_config_ok to
nsxv_config_ok_metadata_custom_certificate
* fix step numeration
Change-Id: Id448e9cf9142e0693a2c03dbb246a653c23c649d
Remove nova-api-metadata key and certificate, because these options do
not work without key being encrypted.
Related-bug: #1590407
Change-Id: I9c01af1ed4020f37a9c6bd172e319b673ae339ba
Plugin cannot change port state. Command "neutron port-update" will
return success code, but port still remains in active state.
Change-Id: I40dc1f294ef51838c382af2e3c002c816a75a729
* Update test plan nsxv_disable_hosts, nsxv_smoke_add_compute
* Add test nsxv_ha_edges
* Switch test plan to version '3'
* Fixes in tests: add_delete_nodes
Change-Id: I64b0cbc499814ec7926029d24ff91a9b81ab67e4
* add test nsxv_disabled_roles
* add missed test nsxv_specified_router_type
* add step to nsxv_add_delete_controller
* add test nsxv_config_ok_metadata
Change-Id: Ic6a829c60beb74a34c12d26a405b924dd20e202b
Deleted 'Allocate IP address in management network for NSX metadata
proxy' parameter. Now this is the default behavior when choosing a
management network for "nova metadata api".
If "nsxv metadata proxy" address will be different from openstack
management network - between "nova metadat api" and "nsxv metadata
proxy" will not l3 connectedness.
Change-Id: I7484fbe0fa749e2d2c7a6a8d8ce53d5e55e68ece
- 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
Document known issue when puppet run fails when user specified huge
amount of nodes in backup pool. Puppet waits for neutron-server while it
starts and neutron-server in turn waits for NSX Manager to report that
all backup nodes are in 'ready' status. Failure depends on amount of
nodes and computing powers of vSphere infrastructure (how quickly it can
provision edges). The only possible workaround is to rerun deployment
process after all edges are provisioned.
Hook up known-issues.rst to table of content.
Related-bug: #1576556
Change-Id: I1942be746d558f661e708b7f85138fdcbef61fae
Document following new knobs:
- certificate key pair that can be used to secure traffice between
metadata agent (NSX Edge) and metadata proxy
- opportunity to allow metadata proxy listen additional ports
- opportunity to specify name servers for instances
- specify instance name servers that will be used when DHCP is turned
off
- switch to init metadata service
Change-Id: I39fe45411ad2f11ad2ac41ac43557f5ce6aa74ac
When NSX Manager get registered in vCenter it expands user role list
with four additional roles: auditor, security administrator, NSX
administrator and enterprise administrator (combination of security &
NSX administrators). If operator wants to use SSO user instead of local
NSX administrator account this user must have enterprise administrator
role in order to be able create router, network (NSX administrator
rights) and create/modify/assign security groups (security
administrator).
Change-Id: I820905f1a8b8feffa03381ce34398a2a21a754cd
Traffic from management network is always sent via vrouter network
namespace no matter what network nova-api-metadata is listening, but
mentioning it on configuration page, may lead to questions why this
behaviour is written here.
Change-Id: I51f88d475705e75ff64d4fdb3a027951cf6990fb
Document two options related to nova-api-metadata network configuration.
Edit labels and descriptions in environment_config.yaml. Fix typos.
Change-Id: I0089c7b5ae8ff9fc29bca80829b1c600fb845163
- explicitly specify vCenter version
- specify limitation that only clusters on 1st level of hierarchy are
supported
- group plugins limitations into separate section
- correct spelling of fuel-plugin-builder and turn it into hyperlink
- explain how to check that plugin works as expected
- add output into test plan for install/uninstall plugin
- add step for distributed/exclusive router tests to attach networks
- edit tests accordingly to new requirements
Change-Id: I201d712a1b2e8bdefe813ff394ab8dd6d88d6b26
(cherry picked from commit c64aa2ebc8)
Explicitly enumerate components that cannot be enabled with NSXv plugin.
Otherwise they are marked with tooltip that says "This component was not
tested with the following components: ..."
NSXv plugin is not compatible with:
* Ceph as block and ephemeral storage is not compatible, because it
cannot be connected to ESXi hosts via vCenter
* Sahara and Murano are incompatible due to deployment errors
* Ironic is not compatible, because it requires Neutron with VLAN
segmentation support
List qemu as compatible hypervisor, because otherwise message "This
component was not tested... with Neutron NSX plugin" appears may confuse
end user.
List incompatible component in "Limitations" section of user guide.
Cherry-picked from e0ceda1b
Closes-bug: 1550169
Change-Id: I48e388615a68fbc593e912d265523da780243a92
- attach separate section in documentation contents
- describe possible problems of plugin and NSX platform
- remove sentence about pre-built plugin package from last page
Change-Id: I26ab3c774206916c62c88fafd31f444af6f633a8
Cherry-picked from 5474fac
- add screenshots of plugin item in wizard
- add description for shared, exlusive and distributed router types
- add URL for Fuel plugin catalog
- small text improvments
Change-Id: Id71d5029bf2a0ab29cb0ceff696c567acc2acfac
- Specify upstream modules that plugin use in Puppetfile; right now
this file is taken from fuel-library/ repository on 05 Feb 2016
- upstream modules that plugin use are:
puppet-neutron
puppet-nova
puppetlabs-stdlib
puppetlabs-inifile
puppet-openstacklib
puppet-keystone
- for modules update we utilize modified update_modules.sh script
from fuel-library/
- add remove_modules.sh script that will clean repository
- hook update_modules.sh and remove_modules.sh into pre_build_hook
- add note about puppet-librarian in plugin build guidelines
Change-Id: Ib38037c77a981d74c4da0e8d74652b51947e2203
* Added get vcenter cluster name from "Vmware" tab
* Added convert cluster name to morefid
* Added public/private key to controller/compute nodes
* Added script, what check and configure neutron, if need
* Added task for connect to controller from compute-vmware via ssh and
execute neutron reconfigure script
* Update documentation
Change-Id: I0dbd6b15fc2cb1efd0de009ee79a27222fe4bab3
Andreas Jaeger