| *** bauzas_ is now known as bauzas | 00:32 | |
| *** bauzas_ is now known as bauzas | 01:42 | |
| *** bauzas_ is now known as bauzas | 03:45 | |
| *** bauzas_ is now known as bauzas | 04:01 | |
| *** bauzas- is now known as bauzas | 04:34 | |
| *** bauzas_ is now known as bauzas | 05:34 | |
| *** bauzas_ is now known as bauzas | 05:59 | |
| *** bauzas_ is now known as bauzas | 06:15 | |
| *** bauzas_ is now known as bauzas | 06:31 | |
| *** bauzas_ is now known as bauzas | 07:00 | |
| *** bauzas_ is now known as bauzas | 07:41 | |
| *** bauzas_ is now known as bauzas | 08:24 | |
| *** bauzas_ is now known as bauzas | 08:55 | |
| *** bauzas_ is now known as bauzas | 09:23 | |
| *** tosky_ is now known as tosky | 12:28 | |
| carloss | #startmeeting manila | 15:00 |
|---|---|---|
| opendevmeet | Meeting started Thu Jun 13 15:00:18 2024 UTC and is due to finish in 60 minutes. The chair is carloss. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| opendevmeet | The meeting name has been set to 'manila' | 15:00 |
| carloss | courtesy ping: dviroel vhari gouthamr carthaca msaravan pulluri ashrodri | 15:00 |
| dviroel | o/ | 15:00 |
| kpdev | hi | 15:01 |
| ashrodri | o/ | 15:01 |
| carthaca | hi | 15:01 |
| gouthamr | o/ | 15:01 |
| vhari | hi | 15:02 |
| haixin | o/ | 15:02 |
| jayaanand | hi | 15:02 |
| ccokeke[m] | Hello | 15:02 |
| gireesh | hi | 15:02 |
| msaravan | Hi | 15:03 |
| carloss | hello everyone! | 15:04 |
| carloss | good quorum, let's get started | 15:04 |
| carloss | our meeting agenda for today: | 15:04 |
| carloss | #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting | 15:04 |
| carloss | #topic Announcements | 15:05 |
| carloss | Schedule and Deadlines | 15:05 |
| carloss | #link https://releases.openstack.org/dalmatian/schedule.html | 15:05 |
| carloss | we're 2 weeks away from spec freeze and 4 weeks away from our bugsquash | 15:06 |
| carloss | for spec freeze, I think we are in the right path and some details of the two specs being proposed are being hashed out | 15:08 |
| carloss | thank you everyone that managed to share their thoughts on the specs | 15:09 |
| kpdev | i would like to have more thoughts on spec | 15:09 |
| kpdev | earlier reviewers mentioned that metadata update should be considered as superset of share properties. And should be applicable for all possible share operations e.g. shrink, extend etc. | 15:10 |
| kpdev | so if set property x in share type extra spec and then similar property in share metadata, the share metadata value would overwrite property x from share type (which is applicale for all shares of that type) | 15:11 |
| kpdev | how best can we achieve this ? | 15:11 |
| gouthamr | ( have to read this through; I haven’t looked at these comments yet) | 15:13 |
| kpdev | that would be helpful | 15:13 |
| carloss | I think that we need to think of something in the lines of: do we want the share type capability to be modified for a specific share? | 15:14 |
| gouthamr | it could get very confusing to users if share type extra specs and metadata are both visible and are both mutable | 15:14 |
| ashrodri | is overriding share type spec with share metadata a user capbility, or admin? | 15:15 |
| kpdev | few are admin only and rest for all users. | 15:16 |
| gouthamr | not all share type extra specs are tenant visible - and those that are visible, and mutable are copied over to the share currently - for example: create_share_from_snapshot_support - the idea is that if the share type is modified, and the value of such a spec is changed, it doesn’t affect existing shares | 15:16 |
| gouthamr | users know the behavior within an existing share because there’s a corresponding “property” (not in the metadata table, but an immutable metadata of sorts) on the share itself | 15:17 |
| gouthamr | so id think we need a similar mechanism if we’re starting to throw in more such concepts through (user modifiable) metadata | 15:18 |
| gouthamr | I wonder, kpdev - is your use case entirely around modifying what’s in share type extra specs today ? have you considered a “retype” sort of workflow instead of this approach? | 15:19 |
| kpdev | my spec was just forward metadata update to backend driver and perform action if possible | 15:19 |
| gouthamr | we don’t have retype - but, cinder does and there were requests to add that feature in the pst | 15:20 |
| kpdev | but recent reviews are inclined to use metadata not only in update but also for all possible share operations. | 15:20 |
| gouthamr | I see; thanks for the call out… I will take a look and comment | 15:21 |
| kpdev | and also use that metadata as properties uniqeu to that share, which means it will override the properties of share that comes from share_type of that share | 15:21 |
| carloss | gouthamr: thanks :) | 15:23 |
| carloss | let's continue the discussion in the spec | 15:23 |
| gouthamr | ^ i can't think of the overlapping properties... | 15:23 |
| gouthamr | > let's continue the discussion in the spec | 15:26 |
| gouthamr | +1 | 15:26 |
| carloss | #topic Review focus | 15:26 |
| carloss | #link https://etherpad.opendev.org/p/manila-dalmatian-review-focus | 15:26 |
| carloss | I have cleared up some things in our review focus etherpad | 15:26 |
| carloss | and I need to populate it with some more fixes | 15:28 |
| carloss | this for example: | 15:28 |
| carloss | #link https://review.opendev.org/c/openstack/manila/+/912777 (Fix for our pylint job) | 15:28 |
| carloss | our pylint job has been broken for a while and I'm trying to fix it | 15:28 |
| carloss | haixin kpdev ashrodri: can I have your eyes on this change? | 15:29 |
| ashrodri | yes | 15:29 |
| carloss | thank you! | 15:29 |
| haixin | sure | 15:29 |
| carloss | thanks | 15:30 |
| carloss | just added two other fixes from kpdev to the list | 15:31 |
| carloss | msaravan gireesh jayaanand: can we have your eyes on | 15:32 |
| carloss | #link https://review.opendev.org/c/openstack/manila/+/920382 (NetApp - Fix share revert to snapshot) | 15:32 |
| carloss | ? | 15:32 |
| gireesh | sure | 15:32 |
| msaravan | Yes, kpdev pinged us.. we'll work on it today/tomorrow. | 15:32 |
| carloss | thank you! :) | 15:33 |
| msaravan | Was occupied with lot of customer queries/solution.. last week.. good thing is, they all wanted Manila..and they love our tenancy model - DHSS=True for datacenter. | 15:33 |
| carloss | msaravan: good stuff, DHSS=True is indeed very nice :D | 15:35 |
| carloss | is there another change you would like to bring up during this meeting? | 15:36 |
| carloss | going once.. | 15:37 |
| carloss | going twice.. | 15:37 |
| carloss | #topic Bug Triage | 15:38 |
| carloss | vhari: o/ floor is yours | 15:38 |
| vhari | hi | 15:38 |
| carloss | #link https://etherpad.opendev.org/p/manila-bug-triage-pad-new (Bug triage etherpad) | 15:38 |
| vhari | lets dive in | 15:38 |
| vhari | #link https://bugs.launchpad.net/manila/+bug/2069230 | 15:38 |
| vhari | global id will help API tracing b'n manila and other services | 15:40 |
| vhari | so this is an ask, long pending | 15:40 |
| gouthamr | +1 | 15:40 |
| vhari | seems easy to implement? | 15:40 |
| gouthamr | medium prio i think | 15:40 |
| carloss | #link https://etherpad.opendev.org/p/dalmatian-ptg-manila-sap#L72 (Discussion of the topic at the PTG) | 15:41 |
| vhari | ack | 15:41 |
| vhari | plenty of examples ^^ | 15:41 |
| carloss | yeah, we are starting to get more attention to this | 15:41 |
| carloss | ++ on medium prio | 15:41 |
| vhari | lhf? | 15:42 |
| gireesh | can we add https://bugs.launchpad.net/tempest/+bug/2069125 bug also in list | 15:42 |
| gireesh | one of the customer is hitting this issue | 15:42 |
| gireesh | we need to correct few field for this bug | 15:42 |
| gireesh | I am working on this | 15:42 |
| carloss | vhari: yes, sounds like lhf | 15:44 |
| gouthamr | the global request id thing? | 15:45 |
| gouthamr | probably not a LHF in our terms | 15:45 |
| vhari | gouthamr, ack | 15:45 |
| vhari | is anyone interested in taking this? :) | 15:47 |
| carloss | gireesh: yep, we can add it to the list :D | 15:47 |
| gireesh | sure | 15:48 |
| vhari | if no other thoughts .. next up | 15:48 |
| vhari | #link https://bugs.launchpad.net/manila/+bug/2069270 | 15:48 |
| vhari | gireesh++ I added the bug to the list | 15:49 |
| carloss | vhari: sorry, previous bug might be a good challenge for someone looking for some fun... ashrodri would you be willing to take a look at it? | 15:49 |
| gireesh | thanks vhari | 15:50 |
| vhari | np, carloss I updated bug notes | 15:50 |
| carloss | thanks | 15:50 |
| ashrodri | ill take a look, thanks vhari | 15:50 |
| vhari | ashrodri++ awesome | 15:50 |
| carloss | ashrodri ++ :D | 15:50 |
| vhari | have a few minutes to char about ^^ 2069270 | 15:51 |
| vhari | looking for minro triage atm | 15:51 |
| carloss | might be a bit of an ignorance of mine, but would 2069270 apply to manila as well? | 15:52 |
| vhari | or NetApp only? | 15:53 |
| carloss | I was thinking likely cinder-only | 15:54 |
| carloss | I remember at least when we were managing volumes, we checked if they had luns | 15:54 |
| carloss | and if there were, we'd block the operation | 15:55 |
| carloss | #link https://opendev.org/openstack/manila/src/commit/d773353502cd8932c31581cfbc3b80846067fe68/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L2094 | 15:55 |
| carloss | netapp volumes (aka shares in Manila :p) | 15:55 |
| carloss | gouthamr: I might be completely wrong here ^ | 15:56 |
| * gouthamr is looking | 15:56 | |
| vhari | gireesh I moved #link https://bugs.launchpad.net/manila/+bug/2069270 to next week list | 15:57 |
| gireesh | sure | 15:57 |
| vhari | if you would like earlier discussions, pls bring it up in #openstack-manila | 15:57 |
| vhari | gireesh, ty for sharing the bug | 15:58 |
| gireesh | ur welcome | 15:58 |
| gouthamr | carloss: sorry was in another meeting | 15:58 |
| carloss | gireesh++ :) | 15:58 |
| gouthamr | carloss: yeah that bug doesn't look relevant to manila | 15:58 |
| carloss | gouthamr: np | 15:59 |
| gouthamr | but, gireesh would probably know better :) | 15:59 |
| gouthamr | basically it says we should name LUNs according to a different standard; the netapp driver in manila doesn't create any LUNs - all good | 15:59 |
| carloss | yep | 15:59 |
| carloss | alright, so we are at the top of the hour | 16:00 |
| gireesh | i need to go through to this bug, I think saravana was looking into this bug | 16:01 |
| carloss | sure, thank you! please update the bug accordingly | 16:01 |
| carloss | and validate if the issue is indeed manila related | 16:01 |
| carloss | gireesh: as vhari said, if you'd like to discuss the bug you brought up earlier, please bring it up in #openstack-manila | 16:02 |
| carloss | let's wrap up | 16:02 |
| carloss | thank you for participating | 16:02 |
| gireesh | sure | 16:02 |
| carloss | let's get back to #openstack-manila | 16:02 |
| carloss | #endmeeting | 16:02 |
| opendevmeet | Meeting ended Thu Jun 13 16:02:37 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:02 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/manila/2024/manila.2024-06-13-15.00.html | 16:02 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/manila/2024/manila.2024-06-13-15.00.txt | 16:02 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/manila/2024/manila.2024-06-13-15.00.log.html | 16:02 |
| *** bauzas_ is now known as bauzas | 17:07 | |
| *** bauzas_ is now known as bauzas | 18:29 | |
| *** bauzas_ is now known as bauzas | 18:46 | |
| *** bauzas_ is now known as bauzas | 19:51 | |
| *** bauzas_ is now known as bauzas | 20:21 | |
| *** bauzas_ is now known as bauzas | 20:42 | |
| *** bauzas_ is now known as bauzas | 22:52 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!