Tuesday, 2022-10-04

bauzasgibi: your help is needed for a janitory change https://review.opendev.org/c/openstack/nova-specs/+/85617308:15
opendevreviewSahid Orentino Ferdjaoui proposed openstack/nova-specs master: spec: allowing target state for evacuate  https://review.opendev.org/c/openstack/nova-specs/+/85783808:20
gibibauzas: done08:36
bauzasthanks08:37
opendevreviewMerged openstack/nova-specs master: Move specs to implemented  https://review.opendev.org/c/openstack/nova-specs/+/85617308:45
auniyal__Hi sean-k-mooney, gibi  08:56
auniyal__in post live migration unit test https://review.opendev.org/c/openstack/nova/+/791135/7/nova/tests/unit/compute/test_compute_mgr.py#1021208:56
auniyal__while testing this test, when controls comes here - https://review.opendev.org/c/openstack/nova/+/791135/7/nova/compute/manager.py#904508:57
auniyal__context ctxt is set to None, 08:57
auniyal__we need this to be nova.context.RequestContext, so we can get node_name08:58
auniyal__what changes I should make in unit test so context get set08:59
auniyal__this unit test is failing right now with this error - *** AttributeError: 'NoneType' object has no attribute '_enginefacade_context'09:00
opendevreviewAmit Uniyal proposed openstack/nova master: [compute] always set instnace.host in post_livemigration  https://review.opendev.org/c/openstack/nova/+/79113510:13
opendevreviewSahid Orentino Ferdjaoui proposed openstack/nova master: compute: enhance compute evacuate instance to support target state  https://review.opendev.org/c/openstack/nova/+/85838310:51
opendevreviewSahid Orentino Ferdjaoui proposed openstack/nova master: api: extend evacuate instance to support target state  https://review.opendev.org/c/openstack/nova/+/85838410:51
sean-k-mooneybauzas: im just double checking the shas now but im going to approve the final release patch for nova/placment ectra if you have no objections11:19
sean-k-mooneyto my knoladage we do not have any issues that would require another RC correct11:19
sean-k-mooneyhttps://etherpad.opendev.org/p/nova-zed-rc-potential looks clean to me11:20
sean-k-mooneyoh just noticed you did it this morning i was going to ping you about it yesterday but it was too late when i tought of it11:22
gibiauniyal__: you are passing None as ctx from the unit test right now https://review.opendev.org/c/openstack/nova/+/791135/7/nova/tests/unit/compute/test_compute_mgr.py#10223 so if you need a real context then pass one in. if you look at the tests around your test case you will see that there is self.context available to pass11:35
*** ravlew is now known as Guest225611:38
auniyal__ack gibi 11:38
auniyal__I missed this, so I moved the retriving node_name, before calling this function and it passed11:39
auniyal__also regarding error, while retriving node name I changed the exception. I have added a comment in new change11:40
*** ravlew5 is now known as ravlew11:52
opendevreviewAmit Uniyal proposed openstack/nova master: [compute] always set instnace.host in post_livemigration  https://review.opendev.org/c/openstack/nova/+/79113512:55
*** dasm|off is now known as dasm13:49
auniyal__Hi sean-k-mooney 14:15
auniyal__regarding adding functional test for VM snapshot14:15
auniyal__in continuation of older discussion14:15
auniyal__<sean-k-mooney> the libvirt fixture shoudl be mockign this out 14:16
auniyal__<sean-k-mooney> https://github.com/openstack/nova/blob/f8c91eb75fc5504a37fc3b4be1d65d33dbc9b511/nova/tests/fixtures/libvirt.py#L1993-L204514:16
auniyal__<sean-k-mooney> which makes me thing that the libvirt fixture is not currently in use14:16
auniyal__I was not sure, how to proceed further, so added fake_get_absolute_limit in fixtures.cinder14:16
auniyal__this - https://paste.opendev.org/show/bEV0xVXGyuWohgRHE9Vm/14:16
auniyal__here - https://github.com/openstack/nova/blob/master/nova/tests/fixtures/cinder.py14:16
auniyal__and then it failed at https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L323914:16
auniyal__as the properties are not set with VOLUME which is used via fixture - 14:16
auniyal__https://github.com/openstack/nova/blob/aad31e6ba489f720f5bdc765c132fd0f059a0329/nova/tests/fixtures/cinder.py#L15414:16
auniyal__So I added one more constant IMAGE_BACKED_VOL_QUIESCE14:16
auniyal__this - https://paste.opendev.org/show/bJgH2kLDa65iRCz9HuIt/14:16
auniyal__now this went further, but then again it failed at - https://github.com/openstack/nova/blob/master/nova/compute/api.py#L351114:16
auniyal__with same error which I was getting earlier14:16
auniyal__===> keystoneauth1.exceptions.catalog.EmptyCatalog: The service catalog is empty.14:16
opendevreviewSahid Orentino Ferdjaoui proposed openstack/nova master: compute: enhance compute evacuate instance to support target state  https://review.opendev.org/c/openstack/nova/+/85838314:36
opendevreviewSahid Orentino Ferdjaoui proposed openstack/nova master: api: extend evacuate instance to support target state  https://review.opendev.org/c/openstack/nova/+/85838414:36
artomsahid, ohhai, long time no see14:55
bauzasreminder: nova meeting in 54 mins15:06
bauzaslast reminder : nova meeting in 9 mins (and I have to update the agenda, oh man)15:51
bauzas#startmeeting nova16:00
opendevmeetMeeting started Tue Oct  4 16:00:15 2022 UTC and is due to finish in 60 minutes.  The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
opendevmeetThe meeting name has been set to 'nova'16:00
bauzashey stackers16:00
gibio/16:00
bauzas#link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting16:00
elodilleso/16:01
bauzasokay, let's start, hopefully people will join later16:02
bauzas#topic Bugs (stuck/critical) 16:02
bauzas#info No Critical bug16:02
bauzas#link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 4 new untriaged bugs (-1 since the last meeting)16:02
Ugglao/16:02
auniyal__O/16:02
bauzasthe etherpad I created for this week's triage https://etherpad.opendev.org/p/nova-bug-triage-2022092716:02
bauzasand I have one security bug I'd like to discuss with the team, now we made it public16:03
bauzas#link https://bugs.launchpad.net/nova/+bug/1989008 Security bug16:03
bauzasI was consider it to close it as Wontfix16:04
bauzasconsidering*16:04
JayFo/16:04
bauzastl;dr: depending on your sudoers rules, you can trick nova user16:05
bauzaswe could change our privsep rules to be more restrictive16:05
sean-k-mooney[m]i filed a downstream backlog item to adress it properly16:05
bauzasbut we prefer deferring to the host config16:05
bauzasabout the permissions rights16:05
sean-k-mooney[m]so longterm i think we shoudl rewirte how we use privesep16:06
bauzasI don't disagree16:06
sean-k-mooney[m]but i dont think we will have time in A16:06
bauzasbut this is a long-term effort16:06
bauzasyeah and very tedious effort16:06
sean-k-mooney[m]i personally would not mind tipping away at this over time16:06
bauzasfor that reason, I think this is valid to close this bug as Wontfix16:07
sean-k-mooney[m]but not sure i can do it in A16:07
bauzasas this is actually more a request for enhancement than a really butg16:07
bauzasbug*16:07
sean-k-mooney[m]i have no objection to that as its really a speless blueprint or spec in my view16:07
bauzasof course, deployers and openstack distros need to properly care about this bug16:07
bauzasand make sure the rights they give are correctly set16:08
sean-k-mooney[m]its not quite an architectual change but it is a desgin pattern change 16:08
bauzasbut from an upstream perspective, given no further effort can be simply made, we need to close it16:08
bauzassean-k-mooney: yeah a refactoring change16:08
bauzasbut,16:08
sean-k-mooney[m]so currently it cannot lead to privladge escalation if you dont already have the ablity to spwan the privsep helper16:08
sean-k-mooney[m]or have access to the unix socket of an exsiting one16:08
bauzassean-k-mooney: we correctly need to make it16:08
bauzassean-k-mooney: exactly my point16:09
bauzasunless you fucked up with your sudo rights, you shouldn't hit this bug16:09
sean-k-mooney[m]yep16:09
sean-k-mooney[m]its kind of like exposing the docker socket to a container16:10
bauzasso, agreed as Wontfix and leave a note saying we're not against modifying our privsep use, but this is deferred for now ?16:10
sean-k-mooney[m]ok with me16:10
bauzasno objections so far ?16:10
gibiplease explain in the bug (if not yet explained) that it cannot lead to escalation if you don't have the rights to spawn the privsep_helper16:11
bauzasgibi: I explained it when I replied but I'll redo it16:11
gibior talkt to the socket16:11
gibibauzas: if it is there already then it is OK16:11
bauzasgibi: quote from myself "I agree with all the above. Unless the user is accepted by sudoers to  have root priviledges, it can't use privsep to get what they want from  the kernel, so this isn't an exploit."16:11
gibicool then16:12
gibithanks16:12
bauzas(comment #9)16:12
gibisorry I not read through the bug 16:12
bauzasbut I'll make it clear on my last reply16:12
bauzas#agreed https://bugs.launchpad.net/nova/+bug/1989008 to be marked as Wontfix as this isn't a flaw if sudoers is correctly set and we don't know when we can modify our privsep usage in nova yet16:13
bauzasvoila, that's it for me unless other pings16:13
bauzas#link https://storyboard.openstack.org/#!/project/openstack/placement 26 open stories (+0 since the last meeting) in Storyboard for Placement 16:14
bauzas#info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster16:14
bauzaselodilles: still fighting with the release, man ?16:14
elodilleshopefully till tomorrow ;)16:14
elodillesso yes, i can take the baton16:14
bauzasthen you have no excuse.16:14
bauzas#info bug baton is being passed to elodilles16:14
bauzaselodilles: thanks16:14
elodilles~o~16:14
elodillesnp16:15
bauzaselodilles: you won't feel overloaded16:15
elodillesfamous last words? :)16:15
bauzasour untriaged backlog is very low todzy16:15
elodillescool :)16:15
bauzasunless something big happens, like a tornado or a earthquake, you'll be fine (tm)16:15
elodilles:]16:16
bauzasmoving on16:16
bauzas#topic Gate status 16:16
bauzas#link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:16
bauzas#link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status 16:16
bauzaslink https://zuul.openstack.org/builds?job_name=tempest-integrated-compute-centos-9-stream&project=openstack%2Fnova&pipeline=periodic-weekly Centos 9 Stream periodic job status16:16
bauzasdamn16:16
bauzas#link https://zuul.openstack.org/builds?job_name=tempest-integrated-compute-centos-9-stream&project=openstack%2Fnova&pipeline=periodic-weekly Centos 9 Stream periodic job status16:16
bauzas#link https://zuul.opendev.org/t/openstack/builds?job_name=nova-emulation&pipeline=periodic-weekly&skip=0 Emulation periodic job runs16:17
bauzasall green above ^16:17
bauzaswell, actually https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weeklyhttps://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly is still fetching info16:17
bauzasanyone having the same trouble than me when opening the url ?16:17
sean-k-mooney[m]you could just have one linke to the perodic pipeline16:17
bauzasright16:18
sean-k-mooney[m]https://zuul.opendev.org/t/openstack/builds?pipeline=periodic-weekly&skip=016:18
sean-k-mooney[m]they work ok for me16:18
bauzassean-k-mooney: so you basically let me providing those 3 links for the whole Yoga and Zed releases ?16:18
bauzasmeh p16:18
bauzas:p16:18
sean-k-mooney[m]https://zuul.opendev.org/t/openstack/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly&skip=016:19
sean-k-mooney[m]hehe16:19
sean-k-mooney[m]that one is nova and placment weekly jobs in one link16:19
bauzasyeah, I never reconsidered to make one call once we added the two other checks :)16:20
sean-k-mooney[m]anyway the are looking good  so we can move on16:20
bauzasyeah, moving on16:20
bauzasbut this was fun16:20
bauzasstupid me.16:20
bauzas#info Please look at the gate failures and file a bug report with the gate-failure tag.16:20
bauzas#info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures16:20
bauzasfyi, I think I'll start providing the weekly metrics for the recheck command in the nova project if our stats don't improve :)16:21
gmannthere is one TC monitor https://etherpad.opendev.org/p/recheck-weekly-summary16:22
bauzashttps://etherpad.opendev.org/p/recheck-weekly-summary tells me we're at 50%16:22
bauzasdamn, burned by gmann16:22
gmann:) thanks to slaweq 16:22
bauzasgmann: yeah I know and I feel 50% is a too bug number16:22
bauzasbig16:22
gmannbut its 1 out of 216:23
sean-k-mooney[m]so at this point im not sure reminding people each week is helping16:23
gmann1 bare recheck is still not so bad16:23
bauzasif my daughter was ranked 10/20 (this is a french note over 20 points), I'd ask her to change a few things16:23
bauzasactually, nevermind me 16:24
bauzasI just saw the raw stats16:24
sean-k-mooney[m]can i suggest we drop this form the meeting going forward or talk about it at the ptg16:24
bauzasyeah16:24
bauzasbut fwiw, our 90-day stat is at 25%16:24
bauzassurprinsingly, we only had 2 rechecks this week16:25
gibiI think it will only improve we can can look at the actual bare rechecks 16:25
bauzasand 1 being a bare one16:25
gmanntalking in meeting just a heads up is good reminder to all of us16:25
bauzasI'll add a point to the PTG agenda16:25
bauzasand we'll discuss it 16:25
bauzasmoving on16:25
gibiand explain if / when it is OK and NOT OK to use it in situation16:25
sean-k-mooney[m]but i dont think it s the people that are in the meeting that need to be reminded16:25
gibibut yes, move on and return to it on the PT16:25
gibiG16:25
bauzas#topic Release Planning 16:26
bauzas#link https://releases.openstack.org/zed/schedule.html16:26
bauzas#link https://releases.openstack.org/antelope/schedule.html16:26
bauzas#info Zed GA planned tomorrow16:26
bauzasso RC2 was our final RC16:26
bauzaskuds to the team for the hard work16:27
bauzaskudos*16:27
gibi\o/16:27
elodilles~o~16:27
bauzasabout this, I'll talk at the next openinfra live session on this Thursday16:28
bauzas1400UTC16:28
bauzaslike I did last cycle, I'll present our cycle highlights and I'll talk about what we plan for Antelope16:28
gibicool16:28
bauzasyou should see some metrics, they are interested to read16:28
bauzasinteresting*16:28
sean-k-mooney[m]ack16:29
bauzaswhich makes me move to the next topic16:29
bauzas#topic PTG planning 16:30
bauzas#link https://etherpad.opendev.org/p/nova-antelope-ptg Antelope PTG etherpad16:30
bauzas#link https://ptg.opendev.org/ptg.html PTG schedule16:30
bauzas#info As a reminder, please provide your PTG topics before Oct-6 (Thursday) !16:30
bauzaswhich actually suits me, as I need to present this Thursday our plans for Antelope :)16:31
bauzasso, typey typey please16:31
sean-k-mooney[m]i have one topic that im going to add but more of an fyi, i would like to repon the idea of move placment to launchpad (without copying and exitsing stories or bugs)16:31
bauzassean-k-mooney: already in the etherpad :)16:31
sean-k-mooney[m]oh ok :)16:32
bauzasyeah, that's boring to me 16:32
bauzasso, about PTG topics16:32
bauzaswe're collecting inputs from other teams too16:32
bauzasthere should be a neutron x-p session16:32
sean-k-mooney[m]there are topic in there etherpad16:33
bauzasI know16:33
bauzasI need to sync up with ralonsoh to find a proper timeslot that suits both teams16:34
bauzasalso,16:34
bauzasas you've seen in the lists, we should have a nova-ironic x-p session too16:34
bauzaswe have one hot topic that needs to be properly addressed at the PTG16:34
bauzaseven if there are already very valuable feedback from sean-k-mooney, gibi and dansmith16:35
ralonsohbauzas, we can sync tomorrow16:35
bauzasso, JayF here wanted to see whether Monday 1400UTC suited for you16:35
bauzasthis is off the Nova hours16:35
bauzasanyone having concerns by this timeslot ?16:36
sean-k-mooney[m]no issues with me16:36
JayFI appreciate everyone trying to get together to solve this for our users :)16:36
bauzaswe don't need the whole gang to attend, but I'd like to see attendance from some people at least16:36
sean-k-mooney[m]are we going to do the cross project topics all on monday16:36
bauzassean-k-mooney: I don't know16:36
sean-k-mooney[m]ok16:37
dansmithnot sure I can make that due to TC stuff, I'll have to check16:37
bauzasthe current agenda is pretty small as we speak16:37
bauzasdansmith: I have an hard stop by 1500UTC16:37
bauzasa hard* (damn English)16:37
bauzasso the session would be one hour max16:37
bauzasprobably not sufficient to cover any possible solutions, but I guess the conversation will focus more about the problem first16:38
gmannMonday 15 UTC is also TC + Leaders sessions16:38
bauzasgmann: that's my hard stop16:38
gmann+116:38
dansmithyeah, so I should be good then16:38
bauzasfwiw, I was hoping to chime on the spec 16:38
bauzasbut as I said, most of the points were already covered and explained16:39
dansmiththere's really not much to chime in on in its current form I think yeah16:39
bauzasthis is frankly not an easy problem to solve so I guess we need to focus on the use case firstr16:39
bauzasdansmith: agreed and the limitations are given 16:40
bauzasanyway16:40
bauzassold for Monday 1400-1500UTC16:40
bauzasJayF ^16:40
sean-k-mooney[m]fundementally the way the ironic driver is written today does not aling with how we expect a driver too work16:40
sean-k-mooney[m]it will not be simple to reconsile the two16:40
bauzassean-k-mooney: the first step is to admit we can't easily reconcile16:41
bauzasJayF: I'll put this in our etherpad, are you going to reserve the timeslot and book the room ?16:41
bauzashe's maybe afk, moving on16:42
JayFbauzas: I can; but if you know how I'd prefer you do it. The PTG planning for this cycle was done by outgoing PTL and I don't know the steps right off16:42
bauzasJayF: no worries, I'll book the room16:42
JayFthank you o/16:42
bauzasjust hoping the bexar room to be free at that time :)16:42
bauzasmoving on16:43
bauzasralonsoh: no worries, let's catch up tomorrow morning EU-time16:43
bauzas#agreed Nova-Ironic cross-project PTG session happening on Monday 1400-1500UTC16:44
bauzas#topic Review priorities 16:44
bauzas#link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+(label:Review-Priority%252B1+OR+label:Review-Priority%252B2)16:44
bauzasnothing from me to say16:44
bauzas(we'll discuss this flag at the PTG, btw.)16:45
bauzas#topic Stable Branches 16:45
bauzaselodilles: this is your show time16:45
elodilles#info from stable/zed back till stable/train branches' gates should be OK16:46
sean-k-mooney[m]awsome16:46
elodilles(i had only a quick look so hope it's true o:))16:46
elodilles#info stable/stein (and older) are blocked: grenade and other devstack based jobs fail16:46
elodilleswith the same timeout issue as stable/train was previously16:46
elodilles#info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci16:46
elodillesso actually nothing special, just the usual things16:47
elodillesthat was it16:47
gibican we delete stable/train ? :)16:47
gibiand older :)16:47
elodilleswell, stein and older looks like abandoned16:48
elodillesso that's for sure16:48
gibipropose a PTG topic :)16:48
gibilets decide there16:48
bauzasyeah16:48
elodilles++16:48
elodillesack16:48
bauzastechnically, we won't delete the branches, right ? :)16:49
bauzasjust EOL them :)16:49
elodillesbauzas: actually it means *deletion*16:49
elodillesonly the $series-eol tag can be retrieved16:49
bauzascool16:50
elodillesafter we EOL'd + deleted a branch16:50
bauzasyeah OK then16:50
bauzas(even if my payslip asks me to do things with newton-based environments, this is not about upstream so... :D )16:50
elodilles(so the history can be retrieved via that *-eol tag)16:50
sean-k-mooney[m]yep we can always restore16:51
bauzasanything else to mention ?16:51
sean-k-mooney[m]i would be in favor of eloing stien and older but ya ptg16:51
bauzasperfect place for this kind of discussion16:51
bauzasin particular given not a lot of people care about stein and older (in terms of branch maintainance)16:52
elodilles:)16:52
bauzasanyway, moving on16:52
elodilles(meanwhile i've added the topic to the PTG etherpad)16:52
bauzas#topic Open discussion 16:52
bauzaselodilles: great, thanks16:53
elodilles++16:53
bauzasthere is nothing to discuss in the open discussion section16:53
bauzasanyone having anything they'd like to say ?16:53
bauzasas a reminder, specless blueprints can be asked here :)16:53
bauzaslooks not,16:54
bauzasI return you 6 mins of your time16:54
bauzasthanks alll16:54
bauzasall* even16:54
bauzas#endmeeting16:54
opendevmeetMeeting ended Tue Oct  4 16:54:30 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:54
opendevmeetMinutes:        https://meetings.opendev.org/meetings/nova/2022/nova.2022-10-04-16.00.html16:54
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/nova/2022/nova.2022-10-04-16.00.txt16:54
opendevmeetLog:            https://meetings.opendev.org/meetings/nova/2022/nova.2022-10-04-16.00.log.html16:54
elodillesthanks bauzas o/16:54
Ugglao/16:54
gibio/16:56
opendevreviewribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (db)  https://review.opendev.org/c/openstack/nova/+/83119316:56
opendevreviewribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (objects)  https://review.opendev.org/c/openstack/nova/+/83940116:56
opendevreviewribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (manila abstraction)  https://review.opendev.org/c/openstack/nova/+/83119416:56
opendevreviewribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (drivers and compute manager part)  https://review.opendev.org/c/openstack/nova/+/83309016:56
opendevreviewribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (api)  https://review.opendev.org/c/openstack/nova/+/83683016:56
opendevreviewribaudr proposed openstack/nova master: Bump compute version and check shares support  https://review.opendev.org/c/openstack/nova/+/85049916:56
opendevreviewribaudr proposed openstack/nova master: Add metadata for shares  https://review.opendev.org/c/openstack/nova/+/85050016:56
opendevreviewribaudr proposed openstack/nova master: Add instance.share_attach notification  https://review.opendev.org/c/openstack/nova/+/85050116:56
opendevreviewribaudr proposed openstack/nova master: Add instance.share_detach notification  https://review.opendev.org/c/openstack/nova/+/85102816:56
opendevreviewribaudr proposed openstack/nova master: Add shares to InstancePayload  https://review.opendev.org/c/openstack/nova/+/85102916:56
opendevreviewribaudr proposed openstack/nova master: Add helper methods to attach/detach shares  https://review.opendev.org/c/openstack/nova/+/85208516:56
opendevreviewribaudr proposed openstack/nova master: Add libvirt test to ensure metadata are working.  https://review.opendev.org/c/openstack/nova/+/85208616:56
opendevreviewribaudr proposed openstack/nova master: Add virt/libvirt error test cases  https://review.opendev.org/c/openstack/nova/+/85208716:56
opendevreviewribaudr proposed openstack/nova master: Add share_info parameter to reboot method for each driver (driver part)  https://review.opendev.org/c/openstack/nova/+/85482316:56
opendevreviewribaudr proposed openstack/nova master: Support rebooting an instance with shares (compute and API part)  https://review.opendev.org/c/openstack/nova/+/85482416:56
opendevreviewribaudr proposed openstack/nova master: Change microversion to 2.94  https://review.opendev.org/c/openstack/nova/+/85208816:56
opendevreviewribaudr proposed openstack/nova master: Add instance.share_attach_error notification  https://review.opendev.org/c/openstack/nova/+/86028216:56
opendevreviewribaudr proposed openstack/nova master: Add instance.share_detach_error notification  https://review.opendev.org/c/openstack/nova/+/86028316:56
opendevreviewribaudr proposed openstack/nova master: Add share_info parameter to resume method for each driver (driver part)  https://review.opendev.org/c/openstack/nova/+/86028416:56
opendevreviewribaudr proposed openstack/nova master: Support resuming an instance with shares (compute and API part)  https://review.opendev.org/c/openstack/nova/+/86028516:56
opendevreviewribaudr proposed openstack/nova master: Add helper methods to rescue/unrescue shares  https://review.opendev.org/c/openstack/nova/+/86028616:56
opendevreviewribaudr proposed openstack/nova master: Support rescuing an instance with shares (driver part)  https://review.opendev.org/c/openstack/nova/+/86028716:56
opendevreviewribaudr proposed openstack/nova master: Support rescuing an instance with shares (compute and API part)  https://review.opendev.org/c/openstack/nova/+/86028816:56
opendevreviewMerged openstack/os-vif stable/xena: Use TCP keepalives for ovsdb connections  https://review.opendev.org/c/openstack/os-vif/+/84177118:41
opendevreviewMerged openstack/os-vif stable/xena: only register tables used by os-vif  https://review.opendev.org/c/openstack/os-vif/+/84177218:59
*** dasm is now known as dasm|off22:32

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!