yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #59868
[Bug 1649531] Re: No supported trunking drivers currently display the "default" behavior.
Reviewed: https://review.openstack.org/410919
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=849baa89815e44a0727bce1d99d9a1c1bb1e0320
Submitter: Jenkins
Branch: master
commit 849baa89815e44a0727bce1d99d9a1c1bb1e0320
Author: John Davidge <john.davidge@xxxxxxxxxxxxx>
Date: Wed Dec 14 18:49:47 2016 +0000
[network] Clarify current trunk driver limitations
All currently supported trunk drivers require both the
``segmentation-type`` and ``segmentation-id`` to be provided
when creating a trunk. This is contrary to these parameters
being optional in the neutron API.
This patch adds a note to clarify the situation until a
future driver removes this requirement.
Change-Id: I18c5577ab04058dc46eaa4ef8b5742e75d3baab7
Closes-Bug: #1649531
** Changed in: openstack-manuals
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1649531
Title:
No supported trunking drivers currently display the "default"
behavior.
Status in neutron:
Invalid
Status in openstack-manuals:
Fix Released
Bug description:
According to Neutron trunk specification [0] segmentation_id and
segmentation_type are optional fields. But when we adding subport to
trunk requests without segmentation_id/segmentation_type are failing.
Example:
$ openstack network trunk set --subport port=port2 trunk10
Failed to add subports to trunk 'trunk10': Invalid input for operation: Invalid subport details '{u'port_id': u'f9922f99-f0e4-4420-be73-dbb9ea7904c6'}': missing segmentation information. Must specify both segmentation_id and segmentation_type.
Neutron server returns request_ids: ['req-7601d1a4-afdf-40e6-9273-1fdab1fc8040']
[0] https://specs.openstack.org/openstack/neutron-specs/specs/mitaka
/vlan-aware-vms.html#proposed-change
UPDATE:
Though these parameters are not required at the API level, all
currently supported drivers make them a requirement. This should be
documented to avoid confusion until a driver that behaves in the
"default" way is added.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1649531/+subscriptions
References