Access Groups

Registered by Ben Swartzlander on 2014-05-22

In Atlanta there was a suggestion from the audience that we support access groups rather than forcing users to allow IP addresses one at a time. There are 2 proposals really:
1) Create an object in manila which can be used to grant bulk access to a share, called can access group
2) While the initial definition of an access group may just be a list of IPs, eventually we may want to allow other implementations, such as mapping to neutron security groups. In that case we would want to suscribe to updates and update the access in manila automatically. That could be a hard thing to do so we would make that a 2.0 kind of feature.

Blueprint information

Status:
Started
Approver:
Ben Swartzlander
Priority:
Medium
Drafter:
Ben Swartzlander
Direction:
Approved
Assignee:
NidhiMittalHada
Definition:
Review
Series goal:
Accepted for newton
Implementation:
Started
Milestone target:
None
Started by
NidhiMittalHada on 2016-02-02

Related branches

Sprints

Whiteboard

(Older Version)
https://etherpad.openstack.org/p/manila-access-groups-api-proposal
dpkshetty: I added few questions in the etherpad above.)

(Created by Nidhi)
https://etherpad.openstack.org/p/access_group_nidhimittalhada

https://wiki.openstack.org/wiki/Manila/design/access_groups

Access rules state mapping should be done with shares and not share instances
This has a database impact and needs a migration
Alter table: ShareInstanceAccessMapping

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.