Non-VLAN multitenancy

Registered by Ben Swartzlander

All of the multitenancy work so far has been tested using VLAN-based network segmentation. Since other forms of segmentation are possible, we need to validate which ones manila is compatible with and publish a list. Then we need to work on adding compatibility where there are gaps.

The interesting use case is when neutron is configured to use GRE or VXLAN based network segmentation, but manila is managing a storage controller that ONLY supports VLAN based network segmentation, for example. In that case a swich or router will need to provide plumbing to join the VLAN to the GRE or VXLAN network. We need to determine if that is a manual step done by the admin beforehand or whether manila can/should automate that work.

Blueprint information

Status:
Complete
Approver:
Ben Swartzlander
Priority:
Not
Drafter:
Scott DAngelo
Direction:
Approved
Assignee:
Scott DAngelo
Definition:
Superseded
Series goal:
None
Implementation:
Good progress
Milestone target:
None
Started by
Ben Swartzlander
Completed by
Ben Swartzlander

Related branches

Sprints

Whiteboard

Confirmed that multi-tenant manila works with 2 and 3 node devstack and GRE tunnels.

An issue exist with work item: Create Tempest tests. This requires multi-node Tempest. Neutron DVR has an infra spec for this: https://review.openstack.org/#/c/106495/

(?)

Work Items

Work items:
[scott-dangelo] Confirmed that multi-tenant manila works with 2 and 3 node devstack and GRE tunnels: DONE
[scott-dangelo] Document test process with 2+ node Devstack: DONE
[rushil] test with VLAN-only backend : TODO
[scott-dangelo] Create Tempest tests: TODO
[scott-dangelo] Confirm with VXLAN: DONE

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.