| Thread Previous • Date Previous • Date Next • Thread Next |
Having a single command deal with the amount of orchestration you're
proposing is not good either, as it may lead to inconsistencies etc.
Our design philosophy is to provide users with smaller building blocks
that can be assembled to achieve more complex use cases.
** Changed in: neutron
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1698500
Title:
[RFE] support trunk's subport range
Status in neutron:
Won't Fix
Bug description:
When we use one trunk port，the following step should be done.
1 openstack port create --network project-net-A trunk
2 openstack port create --network trunked-net subport1
3 openstack network trunk create \
--parent-port 73fb9d54-43a7-4bb1-a8dc-569e0e0a0a38 \
--subport port=91f9dde8-80a4-4506-b5da-c287feb8f5d8, \
segmentation-type=vlan,segmentation-id=100
But when we need to use a trunk port for vlan 1000~2000. That need tremendous work to do.
Suggesting add API for subport range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1698500/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
