Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2022-11-08
16:18:47 elodilles #info wallaby transitioned to Extended Maintenance ( https://review.opendev.org/c/openstack/releases/+/862298 )
16:19:21 elodilles and we have released a final wallaby release
16:19:31 elodilles #info stable branches state should be OK (except stein and older)
16:19:41 elodilles #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
16:19:47 elodilles and last but not least:
16:20:02 elodilles as said 2 weeks ago: stein, rocky and queens EOL'ing patch was proposed: https://review.opendev.org/862520 + mail was sent to ML https://lists.openstack.org/pipermail/openstack-discuss/2022-October/030980.html
16:20:26 elodilles as I see no mail replies arrived on the thread
16:20:39 elodilles so I propose to continue with the EOL'ing
16:20:49 bauzas yup, agreed
16:20:54 bauzas I just +1d the change
16:21:02 bauzas we agreed on it during the PTG
16:21:02 elodilles bauzas: thanks!
16:21:20 bauzas and given none has concerns by the email, that means we can EOL
16:21:43 bauzas elodilles: I guess you can now remove the -W
16:22:29 elodilles removed it now
16:22:53 bauzas thbanks
16:23:19 bauzas anything else to discuss about the stable branches ?
16:23:27 elodilles nothing from me
16:24:53 bauzas ok, last topic then
16:24:59 bauzas #topic Open discussion
16:25:05 bauzas we have an item today
16:25:21 bauzas Kirill_ : vnc console for baremetal. new spec: https://review.opendev.org/c/openstack/nova-specs/+/863773
16:25:30 bauzas I guess you want reviews ?
16:26:03 Kirill_ hi! yes. also i've emplemented it)
16:27:14 bauzas Kirill_: OK, then no worries, we'll look at your spec at least on next Tuesday
16:27:17 sean-k-mooney so you used to be able to do this in the past
16:27:46 bauzas but if you can discuss about the design, sure, let us knwo
16:27:49 sean-k-mooney with the ipmi driver and vncinabox or something like that
16:27:51 bauzas if you *want
16:28:09 sean-k-mooney shellinabox
16:28:28 sean-k-mooney that was the ironic optional component
16:28:49 sean-k-mooney https://docs.openstack.org/ironic/latest/admin/console.html
16:29:11 sean-k-mooney if you use that you can enabel the console to work in horizong today
16:29:34 Kirill_ i work on idrac servers+adding ilo console
16:29:51 Kirill_ but the main gaul is
16:29:59 Kirill_ new graphical console interface
16:30:33 Kirill_ i also emplemented it. but will create mr after approve of this spec
16:31:09 Kirill_ in my spec i added all links. also link to new graphical console interface approved spec
16:31:10 sean-k-mooney ok i would liek to see some context in the spec why the existing horizon integration which used to work with nova provisiond server no longer works
16:32:02 sean-k-mooney ok the reaons im asking this i si used ot have ironic deployed with the geniric ipmi driver and shellinabox at home a few years ago and it worked fine in horizon
16:32:16 sean-k-mooney useing a difffent ironic driver ideally shoudl not requrie changed to nova
16:32:31 sean-k-mooney so if we add this new feature i would hope it will work for all ironic drivers
16:32:42 Kirill_ for vnc
16:32:50 Kirill_ we need to create a handshake
16:33:02 Kirill_ for this handshake we need a password from ironic
16:33:21 sean-k-mooney oh the old solution used the serial console proxy
16:33:28 sean-k-mooney not the novnc proxy
16:33:32 sean-k-mooney that the delta
16:33:35 sean-k-mooney ok makes sense
16:33:41 Kirill_ we need a graphical console not serial
16:34:05 sean-k-mooney ack ya just was trying to figure out why this is fiddernt then https://docs.openstack.org/ironic/latest/admin/console.html
16:34:21 sean-k-mooney its the grapical console not serial
16:35:02 Kirill_ it is not the same console as vnc
16:36:22 bauzas sean-k-mooney: Kirill_: could you maybe discuss this in the spec then ?
16:36:30 bauzas or after the meeting ?
16:36:31 Kirill_ ++
16:36:35 bauzas I'm about to end the meeting
16:36:45 bauzas so you can continue to discuss in the IRC channel after
16:37:02 bauzas ok, anyone else having an item to discuss ?
16:37:09 Kirill_ just to sum up. on 15th November we will review all specs (and mine too)?)))
16:38:06 bauzas yes
16:38:41 Kirill_ got it, thanks
16:39:30 bauzas ok, then let's close the meeting
16:39:41 bauzas thanks all
16:39:45 opendevmeet Log: https://meetings.opendev.org/meetings/nova/2022/nova.2022-11-08-16.00.log.html
16:39:45 opendevmeet Minutes (text): https://meetings.opendev.org/meetings/nova/2022/nova.2022-11-08-16.00.txt
16:39:45 opendevmeet Minutes: https://meetings.opendev.org/meetings/nova/2022/nova.2022-11-08-16.00.html
16:39:45 opendevmeet Meeting ended Tue Nov 8 16:39:45 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
16:39:45 bauzas #endmeeting
16:40:57 elodilles thanks bauzas o/
17:12:45 opendevreview Dan Smith proposed openstack/nova master: Test ceph-multistore with a real image https://review.opendev.org/c/openstack/nova/+/860864
19:05:56 opendevreview Amit Uniyal proposed openstack/nova stable/train: Adds a repoducer for post live migration fail https://review.opendev.org/c/openstack/nova/+/863806
19:05:57 opendevreview Amit Uniyal proposed openstack/nova stable/train: [compute] always set instance.host in post_livemigration https://review.opendev.org/c/openstack/nova/+/864055
20:08:25 opendevreview Amit Uniyal proposed openstack/nova stable/train: Adds a repoducer for post live migration fail https://review.opendev.org/c/openstack/nova/+/863806
20:08:26 opendevreview Amit Uniyal proposed openstack/nova stable/train: [compute] always set instance.host in post_livemigration https://review.opendev.org/c/openstack/nova/+/864055
23:00:12 clarkb Hello nova. I've been testing server rescue behavior recently and run into two different interesting behaviors. The first is when rescuing a non bfv instance if the rootfs label configured in grub and fstab is the same between the rescue image and the instance being recsued you can boot into the rescue image kernel but have the rescued instance / mounted
23:00:57 clarkb This is problematic because if the problem is say in systemd init steps you'd still be broken in the rescued setup. Additionally it may not always be the case that the kernel and your rescued filesystem are compatbile enough to boot
23:01:26 clarkb That said I'm not sure if nova can do anything to deal with this problem direclty. I suspect one of the best options is for clouds to have a purpose built rescue image that isn't likely to collide in this way
23:02:22 clarkb The other issue is when doing rescue on a bfv instance the api accepts the request (as long as yo uset the api version high enough) but then the instance promptly goes into an error state with Driver Error: Cannot access storage file and no such file or directory with a path.
23:02:47 clarkb It almost looks like nova / libvirt are looking for a disk file rather than looking for the volume via whatever the volume provider mechansim is
23:03:11 clarkb I don't have enough access on the cloud side to debug this further so I'm not sure if this is a nova issue or a cloud configuration issue etc.
23:03:50 clarkb It does make me wonder if we've got any rescue testing to ensure this generally works? Also, should we try to write more docs on how to ensure rescues work?
23:04:26 clarkb I'm coming at this as an end user wishing this functioned bette rand wondering what I/we can do to get there. But I lack a lot of background and knowledge on the inner working here :)
23:05:11 clarkb separately, I do wonder if it makes more sense for bfv rescue to be a process more like "stop instnace, detach volume from instance, attach volume to another instance, make changes, reattach to original instance and start original instance" but this fails because you can't detach a root device
23:29:32 opendevreview melanie witt proposed openstack/nova master: DNM testing images_type = raw with resize enabled https://review.opendev.org/c/openstack/nova/+/862416
#openstack-nova - 2022-11-09
01:37:45 melwitt clarkb: this is the test coverage we have for rescue https://github.com/openstack/tempest/blob/master/tempest/api/compute/servers/test_server_rescue.py and it's enabled in the tempest-integrated-compute job for example https://zuul.opendev.org/t/openstack/build/c35d560c76a24e45959aa609ac372d67/log/controller/logs/tempest_conf.txt#70
06:23:09 opendevreview Amit Uniyal proposed openstack/nova stable/train: Adds a repoducer for post live migration fail https://review.opendev.org/c/openstack/nova/+/863806
06:23:10 opendevreview Amit Uniyal proposed openstack/nova stable/train: [compute] always set instance.host in post_livemigration https://review.opendev.org/c/openstack/nova/+/864055
07:48:03 opendevreview Amit Uniyal proposed openstack/nova stable/train: Adds a repoducer for post live migration fail https://review.opendev.org/c/openstack/nova/+/863806
07:48:04 opendevreview Amit Uniyal proposed openstack/nova stable/train: [compute] always set instance.host in post_livemigration https://review.opendev.org/c/openstack/nova/+/864055
08:20:39 opendevreview Nobuhiro MIKI proposed openstack/nova master: libvirt: add maxphysaddr support https://review.opendev.org/c/openstack/nova/+/864091
10:06:50 samuelkunkel[m] Good morning,... (full message at <https://matrix.org/_matrix/media/r0/download/matrix.org/rADMLssdKgBpMiHEvywbsOpx>)
10:21:50 frickler samuelkunkel[m]: your message has been truncated by the matrix bridge. I suggest not to use matrix in order to join IRC. if you think that this is still the right solution for you, make sure your messages are not too long
10:22:37 frickler in particular avoiding to send multiline messages may be helpful
10:23:20 samuelkunkel[m] ah sure, sorry. I can try to make it single line. Links still should work? gonna look for a different client...
10:23:51 samuelkunkel[m] we are currently facing an issue in yoga with libvirt 8.0 for reporting mdev devices
10:23:57 samuelkunkel[m] in particular https://review.opendev.org/c/openstack/nova/+/838976
10:24:03 samuelkunkel[m] is this still being worked on?
10:24:10 samuelkunkel[m] (hope it is readable now)
10:25:18 frickler seem bauzas was the last one working on it

Earlier   Later