*** bauzas_ is now known as bauzas | 04:41 | |
*** chuanm0 is now known as chuanm | 07:25 | |
*** bauzas_ is now known as bauzas | 07:29 | |
carloss | #startmeeting manila | 15:00 |
---|---|---|
opendevmeet | Meeting started Thu Jul 18 15:00:10 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 |
vhari | hi | 15:00 |
carloss | courtesy ping: dviroel vhari gouthamr carthaca msaravan pulluri ashrodri | 15:00 |
carloss | sorry vhari, you were a couple of seconds faster than me :) | 15:00 |
jayaanand | hi | 15:01 |
haixin | o/ | 15:01 |
gouthamr | o/ | 15:02 |
gireesh | hi | 15:02 |
carloss | o/ hello folks | 15:04 |
carloss | I think more people will join as we go | 15:04 |
carloss | #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting (Meeting agenda) | 15:05 |
carloss | packed agenda today, hope we can get to the bottom of the list :) | 15:05 |
carloss | first up: | 15:06 |
carloss | #topic Announcements | 15:06 |
carloss | Schedule and Deadlines | 15:06 |
carloss | #link https://releases.openstack.org/dalmatian/schedule.html (Dalmatian release schedule]) | 15:07 |
carloss | so, we are 2 weeks away from feature proposal freeze | 15:07 |
carloss | and as I shared over the last week, a couple of things have changed for this, so please check the new definition on the schedule | 15:08 |
carloss | in short: a collab review should also be proposedss | 15:08 |
carloss | s/proposedss/proposed | 15:08 |
carloss | we said we'd have a mid cycle and settled on the dates | 15:08 |
carloss | and I had another idea | 15:09 |
carloss | why don't we use half of our mid cycle only for the collab reviews? | 15:09 |
carloss | first half we'd discuss what we had planned for the cycle and check on status of how it is going | 15:10 |
carloss | and the second half we can get some time for change authors to talk about their work to the reviewers | 15:10 |
carloss | that way I think we can attract more audience to the collab reviews as well | 15:10 |
carloss | thoughts? | 15:10 |
gouthamr | that works | 15:11 |
kpdev | +1 | 15:11 |
carloss | great, thank you | 15:12 |
*** bauzas_ is now known as bauzas | 15:12 | |
carloss | I can circle back on this with more details next week then :) | 15:12 |
carloss | another announcement for today: | 15:13 |
carloss | Outreachy internship blogs | 15:13 |
carloss | ccokeke[m] and tspyderboy[m] are working with us through outreachy, and they are making good progress on the feature gap from our manila-ui | 15:13 |
carloss | one of the asks from outreachy (that we as mentors try to reinforce) is: try to write down interesting things you learn as you go | 15:14 |
carloss | so that more people can benefit from your learning, and the community can get to know your work | 15:14 |
carloss | they've been producing great blog posts | 15:14 |
carloss | #link https://medium.com/@tspyderboy (tspyderboy's blog) | 15:14 |
carloss | #link https://dev.to/ccokeke (ccokeke's blog) | 15:15 |
carloss | please take a look at their blog posts | 15:15 |
gouthamr | great job indeed; thanks for highlighting these carloss | 15:15 |
gouthamr | ccokeke[m]++ tspyderboy++ | 15:15 |
carloss | I'm sure there will be some interesting things as you read | 15:15 |
carloss | and last on the announcements for today (but not least important) | 15:16 |
carloss | Proposals for core additions | 15:16 |
carloss | you might have seen two emails I sent to openstack-discuss earlier today | 15:17 |
carloss | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/BUDLA7LMEK6MGXRNTLO4RBIGFWYI4IN7/ (ashrodri ui and client core proposal) | 15:17 |
carloss | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/GHPSMH62X6JSIP2OVSONDGPXLYUK4VZV/ (kpdev core proposal) | 15:17 |
carloss | I am proposing kpdev to manila core, and ashrodri to python-manilaclient and manila-ui core :) | 15:18 |
carloss | the impact of their work is imminent | 15:18 |
carloss | and I believe this is a step in the direction we always wanted to go: having a healthy number of people maintaining the repositories and sharing the responsibilities | 15:19 |
carloss | + having more affiliation diversity in the core team (as is the case of kpdev) | 15:19 |
carloss | as usual, the email will sit on the mailing list for one week, and we will wait for feedback | 15:20 |
gouthamr | \o/ | 15:20 |
vhari | ashrodri++ kpdev++ | 15:20 |
gouthamr | good job on these proposals, carloss | 15:20 |
carloss | then, if we have consensus, they will be added to the respective core team in the respective repositories in a week | 15:20 |
vhari | carloss++ :) | 15:21 |
ashrodri | \o/ thanks! happy to help in any way i can :D | 15:21 |
carloss | ashrodri kpdev: thank you for the hard work you have been putting into this community, and I hope the nomination email reflects that very well | 15:21 |
vhari | +1 | 15:21 |
carloss | of course you'll have more responsibilities as a result of this, but that is another conversation 😅 | 15:22 |
carloss | we intend to have more people being added to the core team, following the same ideas: making affiliation more diverse, and sharing the workload of the project maintenance with more people | 15:23 |
* gouthamr cues Admiral Ackbar meme | 15:23 | |
kpdev | thanks for consideration :) I second that we need more people in core-team. | 15:23 |
carloss | gouthamr: haha, perfect meme for this occasion :D | 15:24 |
carloss | thank you everyone! very excited with this | 15:25 |
carloss | > we intend to have more people being added to the core team, following the same ideas: making affiliation more diverse, and sharing the workload of the project maintenance with more people | 15:25 |
carloss | if you are interested, please let us know. We'll be happy to work with you to get to the core team :) | 15:25 |
carloss | that's all I had for Announcements. Do you have an announcement to share? | 15:25 |
ccokeke[m] | Apologies for joining late | 15:26 |
carloss | ccokeke[m]: no problem :D | 15:27 |
msaravan | Apologies for joining late.. congrats ashrodri and kpdev | 15:28 |
msaravan | more responsiblities | 15:28 |
ccokeke[m] | Congratulations Kpdev and my mentor ashrodri: | 15:29 |
gireesh | congrats Kpdev and ashrodri | 15:30 |
carloss | #topic Bugsquash follow-up | 15:31 |
carloss | #link https://ethercalc.net/o2qsmjpagsfb (Bugsquash ethercalc) | 15:31 |
msaravan | I am almost done with this, will update the patch tomorrow - https://review.opendev.org/c/openstack/manila/+/913213 | 15:32 |
carloss | tyvm for the update msaravan - this documentation is very important for people consuming the feature | 15:32 |
msaravan | ack | 15:33 |
jayaanand | same with https://review.opendev.org/c/openstack/manila/+/913709. | 15:33 |
vhari | msaravan++ | 15:33 |
carloss | jayaanand: good stuff | 15:33 |
jayaanand | thank you! | 15:34 |
carloss | not many bug fixes were merged, but we had good progress on some changes that required attention and are good bug fixes to be addressed | 15:35 |
carloss | I think we'll see the effect of the assignments and the work from this bugsquash in a couple of weeks | 15:35 |
carloss | do you have any further updates? | 15:37 |
* carloss brought this up because wanted to thank you for participating and also open it for questions and discussions on things that are in the list | 15:38 | |
carloss | alright, taking silence as no | 15:41 |
carloss | #topic Bug Triage (vhari) | 15:41 |
carloss | #link https://etherpad.openstack.org/p/manila-bug-triage-pad-new (Bug Triage etherpad) | 15:41 |
carloss | vhari: o/ | 15:41 |
vhari | ty car | 15:41 |
vhari | carloss, | 15:41 |
vhari | so we have one bug to triage today | 15:41 |
vhari | #link https://bugs.launchpad.net/manila/+bug/2073129 | 15:41 |
carloss | I see we already have an assignee here :) | 15:44 |
carloss | jayaanand: do you have an update or would like to share something? | 15:44 |
jayaanand | i am good. nothing now | 15:45 |
vhari | ty jayaanand | 15:45 |
vhari | moving on to #link https://bugs.launchpad.net/manila/+bug/2072552 | 15:45 |
msaravan | We worked with the customer.. and we only asked them to log a bug.. | 15:45 |
msaravan | We'll share our analysis on the bug and working on fixing that.. as it is blocking them @jayaanand | 15:45 |
carloss | jayaanand msaravan: thank you! | 15:46 |
carloss | so for the bug, as it prevents some operations from happening, I'd say medium and m-3 | 15:46 |
vhari | carloss, done | 15:47 |
vhari | if no other considerations .. | 15:47 |
jayaanand | ack | 15:47 |
vhari | wrt #link https://bugs.launchpad.net/manila/+bug/2072552 | 15:47 |
vhari | we reviewed at bugsquash | 15:48 |
vhari | looking for thoughts on how the implementation ideas | 15:49 |
carloss | ah, yes! thanks for bringing this up, vhari | 15:49 |
carloss | kpdev: thanks for the report | 15:49 |
kpdev | yes, this is important feature/fix we can have similar to Nova | 15:49 |
carloss | > B)[preferred] using scheduler hints the share gets scheduled directly without going to the scheduler | 15:51 |
carloss | doesn't sound bad honestly, unless I am not considering something major. Do you know how nova is tracking these requests though? would they just sit and wait until the service is enabled? | 15:51 |
gouthamr | kpdev: is this the nova feature? https://docs.openstack.org/nova/latest/admin/scheduling.html#compute-disabled-status-support | 15:54 |
kpdev | No, I have not checked implementation. For manila, scheduler hints are good option. The service should be up but disabled so it can listen requests. | 15:55 |
kpdev | >is this the nova feature? | 15:56 |
gouthamr | hmm, the service disable knob today just disables the host entirely.. what you're looking for is for a service to be marked disabled for generic requests, but when the scheduler sees the "only_host" hint, we should go ahead and forward the request to the host.. | 15:56 |
gouthamr | i don't think skipping the scheduler is wise; but i can imagine an enhancement to the service disable workflow to do something like that ^ | 15:57 |
kpdev | the service should be differentiated between up/down vs enabled/disabled.. the disabled one is up but disabled and user can enable it. wdyt . | 15:57 |
carloss | > i don't think skipping the scheduler is wise; but i can imagine an enhancement to the service disable workflow to do something like that ^ | 15:58 |
carloss | ++ | 15:58 |
carloss | > the service should be differentiated between up/down vs enabled/disabled.. the disabled one is up but disabled and user can enable it. wdyt . | 16:02 |
carloss | sounds okay as well | 16:02 |
carloss | alright, we're 2 minutes over time | 16:02 |
carloss | please let's take this discussion to #openstack-manila | 16:02 |
carloss | thank you for putting the bug list together, vhari | 16:02 |
carloss | thank you all for participating | 16:02 |
carloss | #endmeeting | 16:02 |
opendevmeet | Meeting ended Thu Jul 18 16:02:36 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-07-18-15.00.html | 16:02 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/manila/2024/manila.2024-07-18-15.00.txt | 16:02 |
opendevmeet | Log: https://meetings.opendev.org/meetings/manila/2024/manila.2024-07-18-15.00.log.html | 16:02 |
*** bauzas_ is now known as bauzas | 19:26 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!