[RFE] support trunk's subport range

[Yan Songming]

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.

[Kevin Benton (kevinbenton)]

How would you expect this to work with a range? How would it know which sub-ports to use?

[Yan Songming (songmingyan)]

We hope to add a api like this:
openstack network trunk create \
--parent-port 73fb9d54-43a7-4bb1-a8dc-569e0e0a0a38 \
--subport port=auto, \
segmentation-type=vlan,segmentation-id=100,200

That means we we will create 100 net,it's net's type is vlan ,segmentid is 100 to 200.
Each net will create one port to use as a subport, subport's segmentation-type=vlan , segmentation-id=100~200

[Armando Migliaccio (armando-migliaccio)]

This was proposed and rejected at the time of the spec discussion, as it's quite a deal of orchestration forced on neutron server, for something that is usually and typically scripted. There's greater implication on how to coordinate the creation of ports, handling failure modes etc and for this reason I am soft reject. That said, I'd be open to other people's opinions.

[Armando Migliaccio (armando-migliaccio)]

BTW: a similar request [1] that did not yield success. If we go down the path of approving both the server side logic can really bloat.

[1] https://review.openstack.org/#/c/421880/

[Armando Migliaccio (armando-migliaccio)]

Furthermore: your proposal of introducing a CLI call like the following:

openstack network trunk create \
--parent-port 73fb9d54-43a7-4bb1-a8dc-569e0e0a0a38 \
--subport port=auto, \
segmentation-type=vlan,segmentation-id=100,200

is unclear which networks subports must plug into.

[Armando Migliaccio (armando-migliaccio)]

Marking incomplete until use case is clarified.

[Yan Songming (songmingyan)]

Yes, we can do this by using script. But i think this will increase the API calls，which is bad for performance.
As for network:
"openstack network trunk create \
--parent-port 73fb9d54-43a7-4bb1-a8dc-569e0e0a0a38 \
--subport port=auto, \
segmentation-type=vlan,segmentation-id=100,200 "
This means neutron will create 100 networks, the segmentation is vlan,the segment id is 100~200 automatically.
Each net will create a port for subport.

[Armando Migliaccio (armando-migliaccio)]

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.