Chapter 7. Network Design in OpenStack Operations Guide

[Spyderdyne]

 Multi-NIC Provisioning

OpenStack Compute has the ability to assign multiple NICs to instances on a per-project basis. This is generally an advanced feature and not an everyday request. This can easily be done on a per-request basis, though. However, be aware that a second NIC uses up an entire subnet or VLAN. This decrements your total number of supported projects by one.

I have received word that this is deprecated and this limitation only applied/applies to Nova-Networks, not Neutron.

-----------------------------------
Built: 2014-06-04T07:20:28 00:00
git SHA: 26c6c6dd9a24a9086965cc572badf4bd28410391
URL: http://docs.openstack.org/trunk/openstack-ops/content/network_design.html
source File: file:/home/jenkins/workspace/operations-guide-tox-doc-publishdocs/doc/openstack-ops/ch_arch_network_design.xml
xml:id: network_design

[OpenStack Infra (hudson-openstack)]

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

[Darren Chan (dazzachan)]

So based on the above information, is the content in http://docs.openstack.org/admin-guide-cloud/content/section_use-multi-nics.html outdated?

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/137508
Committed: https://git.openstack.org/cgit/openstack/operations-guide/commit/?id=f310a5264b84e57e04a0cac34d1eb8827201a661
Submitter: Jenkins
Branch: master

commit f310a5264b84e57e04a0cac34d1eb8827201a661
Author: darrenchan <email address hidden>
Date: Thu Nov 27 15:09:01 2014 +1100

    Minor edits to Multiple NICs section in the Operations Guide

    Reworded paragraph to explain multiple NICs are applicable to Neutron

    Change-Id: I4c605d4d8c549e033c5f7dcb4919eecdd7942823
    backport: none
    Closes-Bug: #1330518