| opendevreview | Eunkyung Kim proposed openstack/python-manilaclient master: Add mount_point_name option for manage shares https://review.opendev.org/c/openstack/python-manilaclient/+/970787 | 06:04 |
|---|---|---|
| opendevreview | Merged openstack/manila stable/2025.2: NetApp - Implemented volume autosize reset support for REST https://review.opendev.org/c/openstack/manila/+/975114 | 09:31 |
| opendevreview | Ivan Anfimov proposed openstack/manila master: ox: Drop basepython https://review.opendev.org/c/openstack/manila/+/975605 | 10:02 |
| opendevreview | Ivan Anfimov proposed openstack/manila master: tox: Drop basepython https://review.opendev.org/c/openstack/manila/+/975605 | 10:02 |
| opendevreview | Ivan Anfimov proposed openstack/manila master: tox: Drop basepython https://review.opendev.org/c/openstack/manila/+/975605 | 10:04 |
| opendevreview | Medha Choudhary proposed openstack/manila stable/2025.1: NetApp - Implemented volume autosize reset support for REST https://review.opendev.org/c/openstack/manila/+/975606 | 10:09 |
| opendevreview | Sylvan Le Deunff proposed openstack/manila master: update share server list endpoint to perform all filtering using ORM https://review.opendev.org/c/openstack/manila/+/975530 | 10:48 |
| opendevreview | Sylvan Le Deunff proposed openstack/manila master: update share server list endpoint to perform all filtering using ORM https://review.opendev.org/c/openstack/manila/+/975530 | 11:05 |
| opendevreview | kiran pawar proposed openstack/manila master: Add support for QoS type and specs https://review.opendev.org/c/openstack/manila/+/967822 | 12:57 |
| opendevreview | kiran pawar proposed openstack/manila master: Netapp: Add support for QoS type specs for dhss=true https://review.opendev.org/c/openstack/manila/+/973962 | 12:57 |
| Sai | Hi carloss gouthamr | 13:04 |
| carloss | o/ | 13:04 |
| Sai | Today we have replica create/promote tests here https://github.com/openstack/manila-tempest-plugin/blob/master/manila_tempest_tests/tests/api/test_replication.py | 13:05 |
| Sai | And we would like to add replica create/promote with metadata | 13:05 |
| Sai | As we are working on share replica create with metadata feature | 13:06 |
| Sai | We have our own metadata, which is {"replication_policy:" : "<MirrorAllSnapshots/Sync/StrictSync>"} | 13:06 |
| Sai | This is NetApp specific | 13:07 |
| Sai | Need a suggestion here on how to add these tests as adding replication_policy is not valid for all vendors | 13:07 |
| carloss | Sai: thanks for bringing this up | 13:08 |
| carloss | so yes, that is a good concern. indeed we should not implement tests in the core that would be targeting only a vendor | 13:08 |
| carloss | so my suggestion here would be: maybe you can try adding a new configuration option that allows you to set metadata? | 13:08 |
| carloss | that would be added to manila-tempest-plugin | 13:09 |
| carloss | something like: share_replica_backend_metadata | 13:09 |
| carloss | and have tests targeting it. that could be a list for a ddt iteration for example, so you guys would be able to define something like: | 13:10 |
| carloss | [{"replication_policy:" : "MirrorAllSnapshots"}, {"replication_policy:" : "Sync"}, {"replication_policy:" : "StrictSync"}] | 13:10 |
| carloss | the netapp CI job would be setting these in the tempest config and it would be picked up by manila-tempest-plugin | 13:11 |
| carloss | so you can add tests like create_replica_with_metadata that would pick it up. each vendor that implements it can set the metadata that makes sense to them and test it. that would produce iterations with the different kinds of metadata that can be set | 13:12 |
| carloss | this can be set as an empty value | 13:12 |
| carloss | and only if there's a metadata that will be honored by the backend, the job would configure it, as you're also introducing tests for the metadata CRUD in share replicas | 13:13 |
| carloss | Sai: does that make sense? | 13:13 |
| carloss | not sure if gouthamr has some bright ideas on this, but that would be the thing that made the most sense in my mind right now | 13:14 |
| Sai | > and only if there's a metadata that will be honored by the backend, the job would configure it, as you're also introducing tests for the metadata CRUD in share replicas | 13:15 |
| Sai | For now, NetApp only supports create. | 13:16 |
| Sai | > Sai: does that make sense? | 13:16 |
| Sai | I kind of get it and makes sense. | 13:16 |
| carloss | > For now, NetApp only supports create. | 13:17 |
| carloss | yep, but for the CRUD of metadata, any backend that supports replication will be able to test it. The concern you brought up is where things happen differently though | 13:17 |
| Sai | Okay | 13:17 |
| carloss | like how to set storage-specific extra specs | 13:17 |
| Sai | got it | 13:17 |
| Sai | INFO: I have anyway added tempests tests to verify create/set/unset metadata operations. | 13:18 |
| carloss | Sai: that's great, thanks for working on those :) | 13:18 |
| dviroel | in the past, those netapp specific tests lived in the netapp's internal plugin. Does that still exists and run? | 13:20 |
| Sai | Thank you carloss, appreciate your suggestions. | 13:20 |
| Sai | > in the past, those netapp specific tests lived in the netapp's internal plugin. Does that still exists and run? | 13:22 |
| Sai | They exists but not running I guess ;( | 13:23 |
| Sai | Need to check | 13:23 |
| dviroel | yeah, there was specific tests running there, that were important | 13:26 |
| Sai | > yeah, there was specific tests running there, that were important | 15:03 |
| Sai | Ahh, I think we need to check and use them efficiently. | 15:03 |
| Sai | Thank you dviroel | 15:03 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!