Earlier  
Posted Nick Remark
#openstack-nova - 2018-02-13
09:19:22 stephenfin It's probably good for jaypipes' mental health
09:19:53 stephenfin Indeed. They're very much against configuring any defaults at all in libvirt
09:20:24 stephenfin besides legacy stuff (as hrw discovered with the USB tablet under ARM issue)
09:22:48 gibi I totally for jaypipes' mental well being
09:23:49 gibi stephenfin: if you summarize your view on the spec then I can second that based on this short chat and then we can call in jaypipes for a review
09:25:20 ameeda Hi, just a question about gerrit review, I have 3 nova reviews waiting for reviewers (both of them got +2c, waiting for +2w) , do you follow scheduler to check them or I have to ask you to check them ?
09:28:14 openstackgerrit Rong Han proposed openstack/nova master: Clean up ports and volumes when deleting ERROR instance https://review.openstack.org/340614
09:46:01 stephenfin gibi: ALL the comments left :)
09:46:52 openstackgerrit jichenjc proposed openstack/nova master: WIP: add zvm document into https://review.openstack.org/532720
09:46:53 openstackgerrit jichenjc proposed openstack/nova master: WIP: Add zvm CI information https://review.openstack.org/533512
09:46:53 openstackgerrit jichenjc proposed openstack/nova master: WIP: Add zvm admin doc https://review.openstack.org/533125
09:48:43 hrw stephenfin: I will get some next stuff around libvirt soon ;D
09:49:45 gibi stephenfin: thanks
10:16:19 openstackgerrit Lee Yarwood proposed openstack/nova master: DNM: Test LM with encrypted volumes https://review.openstack.org/536350
10:40:29 gibi stephenfin: I think we are on the same page about https://review.openstack.org/#/c/539605
10:40:45 gibi stephenfin: thanks for the reply, I seconded it
10:45:05 bauzas I haven't started to review specs yet :)
10:45:16 bauzas for the moment, bug triaging, my lobe
10:45:18 bauzas love
10:50:01 bauzas stephenfin: sahid: not sure it's a bug, needing more details but still FYI https://bugs.launchpad.net/nova/+bug/1749045
10:50:02 openstack Launchpad bug 1749045 in OpenStack Compute (nova) "Used mem in numa_topology do not include mem used by instance which is not fix mem_page_size" [Undecided,Incomplete]
10:50:52 stephenfin bauzas: Yup, that's a known issue. There's an issue in RH Bugzilla about it alright. sahid was working on it
10:51:16 bauzas stephenfin: okay, could you please mark it as Confirmed then, unless it's a duplicate ?
10:52:44 stephenfin bauzas: Yup, #1689753 looks pretty much the same
10:53:01 stephenfin That's something that (hopefully) placement will solve for us
10:53:38 bauzas stephenfin: ok, marking 1749045 as duplicate of 1689753
10:53:45 stephenfin bauzas: Already done :P
10:53:52 bauzas cool
10:54:22 bauzas stephenfin: known issue too here https://bugs.launchpad.net/nova/+bug/1748799
10:54:23 openstack Launchpad bug 1748799 in OpenStack Compute (nova) "cpu binding conflict when multiple VMs execute unshelve at the same time" [Undecided,New] - Assigned to tangxing (tang-xing)
10:54:48 stephenfin bauzas: Yup. That's the "we don't recalculate CPU pinning" issue
10:55:02 stephenfin That's on the agenda for the PTG
10:56:11 bauzas stephenfin: I know, any upstream bug I could say it's duplicate ?
10:56:37 stephenfin bauzas: 1417667 ?
10:57:11 stephenfin Maybe update the title if shelve is also affected
10:59:11 bauzas stephenfin: yep, that's actually a problem for *any* move ops
11:32:28 openstackgerrit Stephen Finucane proposed openstack/nova-specs master: Add 'numa-aware-vswitches' spec https://review.openstack.org/541290
11:37:11 stephenfin sean-k-mooney: When you're about, could you have a look at that to make sure the "problem description" section actually makes sense now? Still trying to configure a machine to evaluate this myself https://review.openstack.org/#/c/541290/2/specs/rocky/approved/numa-aware-vswitches.rst
11:49:58 openstackgerrit Tetsuro Nakamura proposed openstack/nova-specs master: Enable NUMA Features for Libvirt/QEMU Driver https://review.openstack.org/533077
11:50:45 openstackgerrit Merged openstack/nova master: Move the nova-next job in-tree and update it https://review.openstack.org/541474
13:54:54 openstackgerrit Matt Riedemann proposed openstack/nova master: Test websocketproxy with TLS in the nova-next job https://review.openstack.org/513160
14:00:21 esberglu #startmeeting powervm_driver_meeting
14:00:22 openstack Meeting started Tue Feb 13 14:00:21 2018 UTC and is due to finish in 60 minutes. The chair is esberglu. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:23 openstack Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:25 openstack The meeting name has been set to 'powervm_driver_meeting'
14:00:44 esberglu #topic In-tree Driver
14:01:15 esberglu #endmeeting
14:01:18 openstack Meeting ended Tue Feb 13 14:01:15 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
14:01:19 openstack Minutes: http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-02-13-14.00.html
14:01:20 openstack Minutes (text): http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-02-13-14.00.txt
14:01:21 openstack Log: http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-02-13-14.00.log.html
14:01:24 esberglu Sorry thought I was in a different channel
14:19:10 bauzas mriedem: some possible race when trying to delete a BuildRequest instance https://bugs.launchpad.net/nova/+bug/1749167
14:19:11 openstack Launchpad bug 1749167 in OpenStack Compute (nova) "nova show can not get an instance information, and this instance can be queried from nova list." [Undecided,New]
14:19:20 bauzas dansmith: when you're up, see above $
14:19:54 bauzas what I'm confused is that I can see a "too many connections'" SQL exception
14:26:42 openstackgerrit Jiri Suchomel proposed openstack/nova master: Retry few times when creating the initial connection to libvirtd. https://review.openstack.org/416928
14:34:06 dansmith bauzas: why is that confusing? I think it means there are too many connections :)
14:34:33 dansmith I can also imagine that we hit that while trying to do the BR->RS->IM dance and thus it's in the cell and not mapped
14:35:16 bauzas dansmith: yeah, I actually provided a comment
14:35:23 dansmith I saw :)
14:35:27 bauzas it impacted the scheduler call
14:35:36 dansmith and probably other things
14:35:51 bauzas so, yeah, let's ask to reproduce and if not, close it
14:36:11 bauzas dansmith: unrelated, other evacuate thing https://bugs.launchpad.net/nova/+bug/1745977
14:36:12 openstack Launchpad bug 1745977 in OpenStack Compute (nova) "When source compute service up, will not destroy and clean up those instances which be evacuated then be deleted." [Undecided,New]
14:38:35 dansmith okay
14:57:47 mriedem lyarwood: want to get this pike backport? https://review.openstack.org/#/c/537811/
14:57:54 mriedem i'm going to push a pike release today
14:58:41 mriedem dansmith: can you get this one? https://review.openstack.org/#/c/541036/
14:58:55 lyarwood mriedem: ack looking
14:59:37 mriedem i can't remember if you guys needed this for product either https://review.openstack.org/#/c/539003/
15:00:43 dansmith erm, not sure I've looked at that one in depth, we should ask her when she's around
15:02:46 mriedem lyarwood: i'm not sure about this one https://review.openstack.org/#/c/533733/ - i suppose it's ok since it fails fast in the api rather than silently on the compute,
15:02:56 mriedem the problem with swap volume is that i don't think anyone uses it directly,
15:03:07 mriedem it happens as a result of a cinder volume retype or migration
15:03:30 lyarwood mriedem: right but wouldn't this result in a cleaner failure in that case as well?
15:03:32 mriedem so really, the doc updates should be in the cinder api-ref for retype saying that you can't retype an attached volume where the server instance is in one of those states
15:04:03 mriedem i don't know if/how cinder handles a 409 from swap volume, and if it rolls back the retype
15:04:31 lyarwood mriedem: that was an assumption on my part, we'd actually return a 409 to cinder now at least.
15:04:36 mriedem it is better to get a 409 though so cinder at least has a chance to do some kind of rollback
15:06:25 mriedem looks like cinder will delete the new volume (for a retype), and then set the old volume.migration_status='error'
15:06:49 mriedem and set the old volume status back to in-use
15:06:54 mriedem (i think)
15:10:14 mriedem lyarwood: ok +2 on that one; want to get https://review.openstack.org/#/c/541036/ and then i'll cut the release?
15:11:47 lyarwood mriedem: yup will do, thanks
15:23:03 mriedem lyarwood: this is re-introducing a regression from queens https://review.openstack.org/#/c/543569/
15:23:06 mriedem i'm pretty sure anyway
15:24:13 lyarwood mriedem: How so? We also block swap_volume for encrypted volumes when using native LUKS in >=Queens
15:24:26 mriedem lyarwood: https://github.com/openstack/nova/commit/cafe3d066ef7021c18961d4b239a10f61db23f2d#diff-f4019782d93a196a0d026479e6aa61b1
15:24:41 mriedem you're not backporting that regression fix, introduced by the native luks support patch
15:24:46 mriedem that broke several cinder backends
15:25:16 openstackgerrit Boris Bobrov proposed openstack/python-novaclient stable/queens: Fix listing of instances above API max_limit https://review.openstack.org/543968
15:26:13 lyarwood mriedem: crap, yeah my bad
15:31:52 mriedem stephenfin: you would probably enjoy the honors here https://review.openstack.org/#/c/513160/
15:31:58 mriedem nova-next job + tls proxy enabled
15:32:14 stephenfin mriedem: Ooh, snazzy
15:32:57 openstackgerrit Dan Smith proposed openstack/nova master: Lazy-load instance attributes with read_deleted=yes https://review.openstack.org/543970
15:33:11 mriedem i think once we drop the legacy nova-next job that's defined in openstack-zuul-jobs, we should look at making nova-next (defined in tree) voting and gating
15:33:25 mriedem and we should probably also make it run with py3

Earlier   Later