| opendevreview | kiran pawar proposed openstack/manila stable/2026.1: netapp: skip pcuser config for DP read-only volumes https://review.opendev.org/c/openstack/manila/+/988582 | 08:21 |
|---|---|---|
| opendevreview | kiran pawar proposed openstack/manila master: Deferred delete share server and share network https://review.opendev.org/c/openstack/manila/+/981706 | 10:53 |
| opendevreview | kiran pawar proposed openstack/manila master: NetApp: Support force delete volume https://review.opendev.org/c/openstack/manila/+/978780 | 11:08 |
| opendevreview | Takashi Kajinami proposed openstack/manila-tempest-plugin master: Replace deprecated openstackdocstheme options https://review.opendev.org/c/openstack/manila-tempest-plugin/+/988618 | 12:45 |
| opendevreview | Inyong Hong proposed openstack/manila-specs master: Add availability_zone filter to share list spec https://review.opendev.org/c/openstack/manila-specs/+/988650 | 15:59 |
| opendevreview | Inyong Hong proposed openstack/manila-specs master: Add availability_zone filter to share list spec https://review.opendev.org/c/openstack/manila-specs/+/988650 | 16:02 |
| srinesh[m] | Hi gouthamr carloss, thanks for the suggestion. Using matrix client now | 16:04 |
| srinesh[m] | We want to support mountable snapshot for HPE Alletra driver, but our array snapshot behavior is that it inherits the same access rules from the base share and it cannot be modified independently from the base share. | 16:05 |
| srinesh[m] | I understood from goutham's reply in the ptg etherpad that it would require changes in manila api itself if we need to support this behavior. | 16:05 |
| srinesh[m] | I wanted to know if we can use some workaround like erroring out in case someone tries to modify snapshot access rules we can do to support it. Or it is not possible to support it in current state without manila api changes. | 16:05 |
| opendevreview | Ivan Anfimov proposed openstack/manila-ui master: Update packaging configuration https://review.opendev.org/c/openstack/manila-ui/+/987136 | 19:10 |
| carloss | srinesh[m]: hey, so considering manila's current behavior, that deviates from the security we expect | 19:45 |
| carloss | > I understood from goutham's reply in the ptg etherpad that it would require changes in manila api itself if we need to support this behavior. | 19:45 |
| carloss | yes | 19:45 |
| carloss | > I wanted to know if we can use some workaround like erroring out in case someone tries to modify snapshot access rules we can do to support it. Or it is not possible to support it in current state without manila api changes. | 19:46 |
| carloss | it is possible, and at the end, it depends on how the API will be designed for it | 19:46 |
| carloss | it is a storage back end limitation, so maybe we should let the driver error out and signal it through user messages without leaking what are the current access rules, of course | 19:47 |
| opendevreview | Jan Jasek proposed openstack/manila-ui master: pytest-based selenium tests extend share_groups coverage and test docs https://review.opendev.org/c/openstack/manila-ui/+/988693 | 20:19 |
| opendevreview | Jan Jasek proposed openstack/manila-ui master: Extend share_groups selenium tests, README, and horizon.conf template https://review.opendev.org/c/openstack/manila-ui/+/988693 | 20:23 |
| gouthamr | srinesh[m]: carloss: on the PTG etherpad's note/suggestion, i wanted the snapshot's allow/deny access rules to error out. My thought was to create a backend capability in addition to "mount_snapshot_support" that will indicate whether the snapshot's access rules will inherit from the share, or can be exclusively granted. When we have that info, manila can save it in the share and check against it in the API to provide an | 20:28 |
| gouthamr | immediate feedback | 20:28 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!