Comment 7 for bug 1730845

I would agree with Miguel here, and I am not sure I appreciate the strength of the proposed model. The command you propose maps exactly to a trunk one:

openstack nested-port create --child port2 --parent port1 --type vlan --segmentation-id 7

maps to:

openstack trunk create --parent-port port1 --subport port=port2,segmentation-type=vlan,segmentation-id=7

There's a reason why the segmentation type/ID is per subport (and that is to potentially open up to L2GW-type of scenarios), which seems to be the only difference with your proposal.

As for new segmentation types, the API today is not prescriptive to what types are allowed, and it should not be hard to add extra stuff to the sub-port resource (beyond today's segmentation type and ID). That said, I'd be wary to bloat the API without justifying with a solid use case.

Back to you Omer, ball is in your court :)