docs: NSX plugin: Virtual Interface creation failed when starting instances without NSX Service node

[Eugene Korekin]

{"ostf_sha": "4dcd99cc4bfa19f52d4b87ed321eb84ff03844da", "auth_required": true, "api": "1.0", "nailgun_sha": "c2820546f9b2c9aadb4716c7b4100e19b23fc42d", "production": "docker", "fuelmain_sha": "e2008a5398f8d1fabc8d4563b412bfd62eff5b54", "astute_sha": "78963a5415935f22e405e355d710fe92cee34331", "feature_groups": ["experimental"], "release": "5.1", "fuellib_sha": "3a06124c93034444576df2a32516ececfdc9b636"}

Instances fail to start on compute node deployed with nsx plugin.

Error messages in /var/log/nova/compute.log:

2014-09-03 15:34:55.950 12484 ERROR nova.compute.manager [req-69c5c658-48e9-477b-9ad4-21227580effa None] [instance: 62984d87-a17a-4e10-877c-776625bb8efe] Instance failed to spawn
2014-09-03 15:34:55.950 12484 TRACE nova.compute.manager [instance: 62984d87-a17a-4e10-877c-776625bb8efe] Traceback (most recent call last):
2014-09-03 15:34:55.950 12484 TRACE nova.compute.manager [instance: 62984d87-a17a-4e10-877c-776625bb8efe] File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1714, in _spawn
2014-09-03 15:34:55.950 12484 TRACE nova.compute.manager [instance: 62984d87-a17a-4e10-877c-776625bb8efe] block_device_info)
2014-09-03 15:34:55.950 12484 TRACE nova.compute.manager [instance: 62984d87-a17a-4e10-877c-776625bb8efe] File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 2266, in spawn
2014-09-03 15:34:55.950 12484 TRACE nova.compute.manager [instance: 62984d87-a17a-4e10-877c-776625bb8efe] block_device_info)
2014-09-03 15:34:55.950 12484 TRACE nova.compute.manager [instance: 62984d87-a17a-4e10-877c-776625bb8efe] File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 3687, in _create_domain_and_network
2014-09-03 15:34:55.950 12484 TRACE nova.compute.manager [instance: 62984d87-a17a-4e10-877c-776625bb8efe] raise exception.VirtualInterfaceCreateException()
2014-09-03 15:34:55.950 12484 TRACE nova.compute.manager [instance: 62984d87-a17a-4e10-877c-776625bb8efe] VirtualInterfaceCreateException: Virtual Interface creation failed

Reason:
NSX Service node wasn't installed but Neutron was configured to use it.

Workaround for 5.1:
The file /etc/neutron/plugins/vmware/nsx.ini on a Controller node has a parameter 'replication_mode'. It should be 'service' if you use NSX Service node, or 'source' if you don't. Fuel 5.1 sets it to 'service'. So, if you don't have NSX Service node just set this parameter to 'source' on all the Controller nodes.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/119331

[Igor Zinovik (izinovik)]

This bug wont be fixed, we need explicitly state in our documentation for 5.1 that integration of
VMware NSX requires cluster that runs with NSX Service node.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/119331
Committed: https://git.openstack.org/cgit/stackforge/fuel-docs/commit/?id=f02094ceb7dc780a94ad41df82f4b0fbde8a4abc
Submitter: Jenkins
Branch: master

commit f02094ceb7dc780a94ad41df82f4b0fbde8a4abc
Author: Igor Zinovik <email address hidden>
Date: Fri Sep 5 13:18:55 2014 +0400

    state the fact that NSX Service node is mandatory for Mirantis OpenStack

    - NSX cluster can successfully operate without Service node, but our
      tests show that creation of virtual interfaces fails, due to incorrect
      configuration of `replication_mode' setting in Neutron NSX plugin
      confguration file (plugin is configured to use Service node)
    - we need more work to be done to implement working Mirantis OpenStack
      with NSX cluster that operates without Service node
    - note that OpenStack itself can be used with NSX cluster that lacks
      Service node
    - while here add missing article

    Change-Id: Ibd88834a525104f4c9e71c355c3e7e0ea833adba
    Closes-bug: #1365043

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/5.1
Review: https://review.openstack.org/123356

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/123356
Committed: https://git.openstack.org/cgit/stackforge/fuel-docs/commit/?id=dd0493da4420f82f4a5aca28aacfc4b50bf8091e
Submitter: Jenkins
Branch: stable/5.1

commit dd0493da4420f82f4a5aca28aacfc4b50bf8091e
Author: Igor Zinovik <email address hidden>
Date: Fri Sep 5 13:18:55 2014 +0400

    state the fact that NSX Service node is mandatory for Mirantis OpenStack

    - NSX cluster can successfully operate without Service node, but our
      tests show that creation of virtual interfaces fails, due to incorrect
      configuration of `replication_mode' setting in Neutron NSX plugin
      confguration file (plugin is configured to use Service node)
    - we need more work to be done to implement working Mirantis OpenStack
      with NSX cluster that operates without Service node
    - note that OpenStack itself can be used with NSX cluster that lacks
      Service node
    - while here add missing article

    Change-Id: Ibd88834a525104f4c9e71c355c3e7e0ea833adba
    Closes-bug: #1365043

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/125961

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/125962

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/125961
Committed: https://git.openstack.org/cgit/stackforge/fuel-web/commit/?id=0ba6bf46f0f8ec598aa6b061ebf843f756b125ba
Submitter: Jenkins
Branch: master

commit 0ba6bf46f0f8ec598aa6b061ebf843f756b125ba
Author: Igor Zinovik <email address hidden>
Date: Fri Oct 3 16:48:29 2014 +0400

    provide UI control for NSX plugin 'replication_mode' setting

    - NSX cluster can operate without NSX Service nodes, but this requires
      configuration of `replication_mode' setting, so lets add an
      opportunity for user to specify that his NSX cluster runs in testing
      mode (without Service nodes).

    Change-Id: Ia545dd90fd7e8b3b2de7280088bd07c689b1adb7
    Partial-bug: #1365043

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/127226

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/125962
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=7c71f946b5de6385b2d5fb32d18821ff69ccec1c
Submitter: Jenkins
Branch: master

commit 7c71f946b5de6385b2d5fb32d18821ff69ccec1c
Author: Igor Zinovik <email address hidden>
Date: Fri Oct 3 16:14:53 2014 +0400

    honour `replication_mode' configuration option in the VMware NSX plugin

    - `replication_mode' stanza determines network traffic replication mode.
      Default value for this setting is `service' which means that NSX
      cluster operates with NSX Service nodes (as any NSX production cluster
      should) and packet replication on router and switches happens on NSX
      Service nodes.
    - setting `replication_mode' to `source' means that traffic replication
      happens localy on nodes, which is the only option if we do not have
      Service nodes.

    DocImpact
    Change-Id: I830dc687dbf25a8fd9e4d375c5e37af2bda83df4
    Partial-bug: #1365043

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/127226
Committed: https://git.openstack.org/cgit/stackforge/fuel-docs/commit/?id=01a7c49c028a8d597d429a3b67a5c4f116a16337
Submitter: Jenkins
Branch: master

commit 01a7c49c028a8d597d429a3b67a5c4f116a16337
Author: Igor Zinovik <email address hidden>
Date: Thu Oct 9 16:53:43 2014 +0400

    MOS can be used with NSX cluster that lacks Service nodes

    - remove warning that says that NSX Service node is mandatory for
      Mirantis OpenStack
    - add note about fact that NSX Service node is mandatory for high volume
      environments
    - update screenshot with NSX settings block that shows new checkbox

    Change-Id: I196f1b6353b8a64ba221d93f0622f6d3859dc9ea
    Partial-bug: #1365043

[Mike Scherbakov (mihgen)]

Do we still expect new changes to docs?

[Dmitry Borodaenko (angdraug)]

No, nothing related to this bug is expected to be changed in 6.0 docs.