opendevreview | kiran pawar proposed openstack/manila master: Add new policy `list_all_projects` for share/share-snapshot https://review.opendev.org/c/openstack/manila/+/932414 | 09:45 |
---|---|---|
opendevreview | Chuan Miao proposed openstack/manila-specs master: Add spec for share group affinity policy https://review.opendev.org/c/openstack/manila-specs/+/933558 | 11:03 |
opendevreview | Chuan Miao proposed openstack/manila-specs master: Add spec for share group affinity policy https://review.opendev.org/c/openstack/manila-specs/+/933558 | 14:39 |
carloss | VolodymyrBoiko[m]: yes, I'll take a look | 15:04 |
carloss | o/ chuanm re: https://review.opendev.org/c/openstack/manila-specs/+/933558/comment/cc7ffb4d_0e73639a/ | 15:05 |
carloss | Yes, I got it. I think I might be missing context or something, so this might only be a question. If I understand this correctly, in the shares creation we will specify a share group, and that share group will have this affinity_policy defined. When the share creation starts, we'd relate the share to the share group and we'd check if it has an affinity/anti-affinity policy. If it is anti-affinity, that would mean the share | 15:05 |
carloss | can't be in the same host as the shares in the group. Is that correct? | 15:05 |
carloss | my concern is based on the answer for this being yes... in that case, the share will be related to the share group but it has an anti-affinity with the share group, and the share will be tied to the share group anyways | 15:11 |
carloss | so on paper, this would be something not very logical to track | 15:11 |
carloss | and for the tracking, maybe I am too attached to the affinity/antiy-affinity for shares concept, where we define which hosts we have affinity/anti-affinity with in the metadata. When I asked about it, it is because I was thinking that at some point we'd like to track which other share groups or hosts a share group has or has not affinity with | 15:13 |
carloss | for example: share group A has an anti-affinity policy with host@backend#netapp1 | 15:14 |
carloss | that is what I meant with the tracking... I was thinking if we should follow the same way we are tracking the affinity/anti-affinity hosts for shares | 15:15 |
opendevreview | Merged openstack/manila master: updated VAST driver documentation https://review.opendev.org/c/openstack/manila/+/935367 | 16:04 |
opendevreview | Chuan Miao proposed openstack/manila master: Improve listing share servers with search option https://review.opendev.org/c/openstack/manila/+/936861 | 17:10 |
-opendevstatus- NOTICE: Gerrit will have a short outage while we update to the latest 3.9 release in preparation for our 3.10 upgrade on Friday | 21:31 | |
opendevreview | Jonathan Koerber proposed openstack/manila master: api: Add Schemas for share export locations https://review.opendev.org/c/openstack/manila/+/926678 | 22:24 |
opendevreview | Youssef baataoui proposed openstack/manila master: Update JSON schema validation to metadata API https://review.opendev.org/c/openstack/manila/+/933625 | 23:20 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!