Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2024-05-28
16:07:59 sean-k-mooney oh no an ephmeral disk with the encyption format set to vfat which i think is the default
16:08:00 bauzas (all greens except nova-emulation for zed )
16:08:13 bauzas #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:08:20 bauzas #info Please try to provide meaningful comment when you recheck
16:08:23 bauzas voila
16:08:59 bauzas about the bug, we can continue to discuss about it on the open discussion section :)
16:09:06 bauzas #topic Release Planning
16:09:10 bauzas #link https://releases.openstack.org/dalmatian/schedule.html
16:09:23 bauzas #info nova deadlines are now there ^
16:09:31 bauzas #info Dalmatian-2 in 5 weeks
16:09:37 bauzas that's it
16:10:05 bauzas moving on
16:10:13 bauzas #topic Review priorities
16:10:19 bauzas #link https://etherpad.opendev.org/p/nova-dalmatian-status
16:10:38 bauzas you can now look at it
16:10:53 bauzas I provided all the series for all the specs that were accepted
16:11:15 bauzas we also have a few bugfixes for CI and other stuff in there
16:11:42 bauzas fwiw, I'll continue to review some of the series
16:12:38 bauzas #topic Stable Branches
16:12:41 bauzas elodilles: your time
16:12:55 elodilles i haven't seen much activity in stable/202*.* branches, but last time their gate were OK, so hopefully they are in the same state
16:13:21 elodilles that's all from me
16:13:30 elodilles about stable.
16:15:01 bauzas ++
16:15:13 bauzas #topic vmwareapi 3rd-party CI efforts Highlights
16:15:18 bauzas fwiesel: anything to say ?
16:15:19 fwiesel #info Hand-Over to operations of CI required some (internal) migration. Working on backlog jobs.
16:15:38 fwiesel So, if you see delays, that's the reason.
16:15:54 fwiesel Any questions?
16:16:01 bauzas not from me
16:16:58 fwiesel Okay, then that's from my side. Hopefully that is done soon, and I can focus on the bugs again.
16:17:20 bauzas ++
16:17:31 bauzas #topic Open discussion
16:17:41 bauzas nothing on the agenda
16:17:46 bauzas anything anyone ?
16:19:05 bauzas looks not
16:19:18 bauzas sean-k-mooney: gibi: want to continue discussion the vfat bug ?
16:19:26 bauzas or, can we close ?
16:19:58 sean-k-mooney we can close im updating the bug with some comments
16:20:28 bauzas ++
16:20:33 bauzas thanks all then
16:20:37 opendevmeet Log: https://meetings.opendev.org/meetings/nova/2024/nova.2024-05-28-16.00.log.html
16:20:37 opendevmeet Minutes (text): https://meetings.opendev.org/meetings/nova/2024/nova.2024-05-28-16.00.txt
16:20:37 opendevmeet Minutes: https://meetings.opendev.org/meetings/nova/2024/nova.2024-05-28-16.00.html
16:20:37 opendevmeet Meeting ended Tue May 28 16:20:37 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
16:20:37 bauzas #endmeeting
16:20:48 fwiesel Thank you too
16:21:29 elodilles thanks o/
16:22:45 gibi sean-k-mooney: thanks
16:32:43 sean-k-mooney gibi: ok i think i see where the bug is but im not sure how long its been that way
16:33:09 sean-k-mooney commented in the bug but i think its https://github.com/openstack/nova/blob/96268d4e7a0dd1872c77641a634a94f599d59fe0/nova/virt/libvirt/driver.py#L11588-L11601
16:33:25 sean-k-mooney we are passing cache_name = os.path.basename(info['backing_file']) as the fs_lable
16:33:37 sean-k-mooney which will generally be over 11 charters
16:39:05 sean-k-mooney gibi: which was changed in https://github.com/openstack/nova/commit/4289b645970
16:48:28 sean-k-mooney gibi: my inlication is to mark this as valid but which list since i think the bug predates me working on openstack and litrally ahs been there in nova since 2012 and is now a proble because of a new mkfs release that actully treats it as an error
#openstack-nova - 2024-05-29
10:36:47 opendevreview Fabian Wiesel proposed openstack/nova master: Add more password generation options https://review.opendev.org/c/openstack/nova/+/865669
17:27:58 bauzas sorry guys, I was having some optic fiber issue, so my znc server wasn't able to be called
#openstack-nova - 2024-05-30
06:04:28 opendevreview Rajesh Tailor proposed openstack/nova master: Handle neutron-client conflict https://review.opendev.org/c/openstack/nova/+/918048
06:54:09 mikal Hey sean-k-mooney, I've been out of OpenStack a while, and I'm confused on what if any my next steps with https://review.opendev.org/c/openstack/nova-specs/+/915190 should be. Is it waiting on me somehow, or is it just in a process and will eventually happen? Thanks!
07:27:13 sean-k-mooney[m] mikal: a bit of both. its still needs review but also reminding us that i was there and ready for review. we had a spec review day 2? weeks ago i think but we never got to it so the ping is enough to remind us to re review
07:36:14 mikal sean-k-mooney[m]: yeah fair enough. I updated it before the review day, but I didn't realise I needed to ping people. Is there an etherpad it should be on or something like that?
08:01:19 sean-k-mooney[m] mikal: yep https://etherpad.opendev.org/p/nova-dalmatian-status is our tracking etherpad for things that are ready for review
08:02:49 mikal sean-k-mooney[m]: I see you just did a review. I'll churn through those and then re-ping here I suppose?
08:02:53 sean-k-mooney[m] reviewing the spec quickly i still think it need some work. it could benefit form a ascii diagram showing the end user flow for how they would connect to kerbsdie
08:03:37 sean-k-mooney[m] we pinging is not stricly required but its a good way to ensure it does not get lost in our email inbox or in the walll of other reviews we have in gerrit
08:04:35 sean-k-mooney[m] its on my radar again to look at in the next few days but just an fyi im off tomorrow and monday so i likely wont get back to it until Tuesday
08:04:57 mikal Yeah, my quick take is that your comments seem reasonable to me, but clearly some parts of this you understand better than me. So for example I can try and write up how the HTML5 transcoding proxy works, but it might be faster for you to just provide a paragraph you consider accurate.
08:05:23 mikal I'm not stressed about timelines as long as the window isn't going to close in the next couple of days or something.
08:05:24 sean-k-mooney[m] it would be good to reach out to bauzas gibi or others to review
08:06:02 bauzas I'm late for specs reviews but I'll try to look at some this week
08:06:17 mikal Yeah, I'm trying to work out what's considered hassling these days vs gently reminding. I'm hesitant to just smash out a bunch of pings if that will annoy people.
08:06:25 sean-k-mooney[m] mikal: the current deadline is milestone 2 for sepc appoval
08:06:33 sean-k-mooney[m] so i think we have like 4 weeks or so
08:07:07 sean-k-mooney[m] july 4th
08:07:56 bauzas https://releases.openstack.org/dalmatian/schedule.html
08:07:57 bauzas no
08:07:59 sean-k-mooney[m] mikal: i have no issues with pings. if im busy i just wont reply
08:08:05 bauzas spec freeze is on July 14th
08:08:10 mikal Ok cool. I think as long as it doesn't stall for ages that's workable. I'll address your comments over the next few days and then I'll re-ping you and bauzas here.
08:08:29 sean-k-mooney[m] bauzas: why the 14 we said it shold be milestone 2
08:08:38 bauzas ie. 2 weeks after milestone-2, which itself is the spec review day
08:08:58 bauzas sean-k-mooney: we discussed this at the PTG and you reviewed the schedule change :)
08:09:06 sean-k-mooney[m] right but that is not what we normally do so why are we giving 2 addtional weeks
08:09:38 bauzas I can't remember the why
08:09:54 bauzas look at the etherpad
08:09:58 sean-k-mooney[m] fine i guess we can but if we are still at spec review time in the midle of july your spec is proably not going to get finsihed
08:10:12 mikal Also, I am open to horse trading. Like if someone would like me to review or assist with something else to earn karma for my stuff, then that's fine. I tried to review some other specs along those lines, but must admit I haven't in the last few weeks.
08:10:15 sean-k-mooney[m] ya i missed a lot of the ptg this time because of time zones
08:12:08 sean-k-mooney[m] i missed the reto and plannign disccustion and basiclly the firsr 90 mins or so of every day since there was no upstream ping and i was off by 1
08:13:04 bauzas mikal: that's a kind offer but you shouldn't need it :)
08:13:17 bauzas we'll review your spec like others :)
08:13:34 bauzas (I just need a way to work concurrently better :D )
08:13:45 mikal Ok. I know back in the day we used to tell people to go review some other stuff if they wanted their stuff reviewed. That is, not just the core team should be reviewing things.
08:14:18 sean-k-mooney[m] mikal: for what its worth since i didnt see an update on it for 30 days i assumd it had not changes since i last looked
08:14:20 sean-k-mooney[m] but i guess i missed the post ptg update
08:15:09 mikal sean-k-mooney[m]: "didn't see" means in email?
08:15:24 mikal But yeah, I just updated it and then went into a wait state.
08:15:55 sean-k-mooney[m] well reviews are always wellcome but that really only worked/works in my view as a side efffect of “oh this person is doing review, wasnt i ment to review there stuff too” i.e. seeing your name in gerrit reminds me of the fact i proably should have gotten back to reviewing your spec/patch
08:17:11 sean-k-mooney[m] didnt see in that on the spec review day i either looked before you updatd it or a few days after. so i had a spliting headache that day so i didnt do much review on that day and loopped back later in the week
08:17:38 sean-k-mooney[m] and i only looked at specs that had recent updates

Earlier   Later