| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-08-21 | |||
| 15:01:09 | maciejjozefczyk | mriedem: So it should wait for stable pike? | |
| 15:01:25 | mriedem | maciejjozefczyk: it has to be in stable/pike before we can merge it in stable/ocata, yes | |
| 15:01:32 | mriedem | i'm not sure yet if it should be in rc2 for pike | |
| 15:03:08 | maciejjozefczyk | mriedem: ok | |
| 15:05:47 | mriedem | man i guess you guys were busy last week https://review.openstack.org/#/q/status:merged+project:openstack/nova+branch:stable/pike | |
| 15:06:44 | dansmith | mriedem: anything you see in there that wasn't legit? | |
| 15:06:47 | dtantsur | folks, do you by chance know who is leading https://etherpad.openstack.org/p/queens-PTG-vmbm ? I should have been aware of it, but I'm not :) | |
| 15:07:02 | cdent | dtantsur: probably johnthetubaguy ? | |
| 15:07:03 | dansmith | mriedem: some of the work required some test backports for cleanliness | |
| 15:07:20 | mriedem | dansmith: yeah that looks like the evacuate/shelve offload tests from givi | |
| 15:07:22 | mriedem | *gib | |
| 15:07:23 | mriedem | gdi | |
| 15:07:24 | mriedem | gibi | |
| 15:07:26 | dansmith | yeah | |
| 15:07:42 | dtantsur | johnthetubaguy: is it you? :) | |
| 15:09:12 | mriedem | dansmith: i found one major issue here https://review.openstack.org/#/c/493037/4/nova/compute/resource_tracker.py@1225 | |
| 15:09:39 | dansmith | mriedem: oh the humanity | |
| 15:10:13 | gibi | mriedem: welcome back. :) | |
| 15:13:04 | mriedem | thanks | |
| 15:16:31 | mriedem | it's going to be a rough couple of days so give me softballs if you have them | |
| 15:17:51 | gibi | I'm going for vacation this week so I can promise that I will not file yet another resource allocation bugs. :) | |
| 15:19:01 | mriedem | q | |
| 15:19:04 | mriedem | oops | |
| 15:22:22 | mriedem | ocata 15.0.7 release request https://review.openstack.org/495903 | |
| 15:26:27 | guimaluf | maciejjozefczyk, the error I mentioned is happening on nova-compute node, no errs on conductor logs. I'll enable debug to see if there is something meaningful | |
| 15:28:03 | dansmith | mriedem: I left this for you to make a call on: https://review.openstack.org/#/c/494973/ | |
| 15:29:20 | openstackgerrit | Merged openstack/nova master: replace chance with filter scheduler in func tests https://review.openstack.org/491529 | |
| 15:29:41 | openstackgerrit | Merged openstack/nova master: Clarify that vlan feature means nova-network support https://review.openstack.org/478551 | |
| 15:33:39 | mriedem | dansmith: yeah saw that, wasn't sure since it's not a regression in pike | |
| 15:34:17 | dansmith | mriedem: yeah thought that was the right call, but figured I'd leave it to you.. can wait until after pike releases and then push the backport like normal | |
| 15:45:13 | openstackgerrit | Stephen Finucane proposed openstack/nova master: Remove plug_ovs_hybrid, unplug_ovs_hybrid https://review.openstack.org/483030 | |
| 15:48:48 | lvdombrkr | hello guys, im trieng deploy tripleO , and after trying deploy overcloud get error: http://paste.openstack.org/raw/618917/ , in nova scheduler logs i see that tha node is filtred out http://paste.openstack.org/raw/618930/ | |
| 15:48:54 | lvdombrkr | but i dont uderstand why | |
| 15:49:12 | lvdombrkr | any ideas? | |
| 15:50:18 | openstackgerrit | Stephen Finucane proposed openstack/nova master: tests: Remove useless test https://review.openstack.org/483031 | |
| 15:55:19 | openstackgerrit | Stephen Finucane proposed openstack/nova master: console: introduce basic framework for security proxying https://review.openstack.org/345396 | |
| 15:55:20 | openstackgerrit | Stephen Finucane proposed openstack/nova master: console: introduce framework for RFB authentication https://review.openstack.org/345397 | |
| 15:55:20 | openstackgerrit | Stephen Finucane proposed openstack/nova master: console: introduce the VeNCrypt RFB authentication scheme https://review.openstack.org/345398 | |
| 15:55:21 | openstackgerrit | Stephen Finucane proposed openstack/nova master: console: provide an RFB security proxy implementation https://review.openstack.org/345399 | |
| 15:57:08 | mriedem | disabling RamFilter by default hits it's first victim https://bugs.launchpad.net/nova/+bug/1712057 | |
| 15:57:09 | openstack | Launchpad bug 1712057 in OpenStack Compute (nova) "When the specified destination host deploys the virtual machine, the allocation ratio is not valid" [Undecided,Invalid] - Assigned to wangyicheng (wang-yicheng) | |
| 15:58:23 | mriedem | dansmith: did anyone mention this https://review.openstack.org/#/c/495811/ ? | |
| 15:58:26 | cfriesen_ | mriedem: whee! do we want to fill in the limits filter somewhere else? | |
| 15:58:38 | cfriesen_ | make that just limits, not filter | |
| 15:58:51 | mriedem | cfriesen_: the intent is to remove all of that stuff eventually, so i don't think so | |
| 15:58:59 | mriedem | the limits are used in the claims code in the compute | |
| 15:59:16 | mriedem | i suspect the reporter of that bug has out of tree code that's relying on the limits | |
| 16:03:16 | cdent | mriedem: what do you mean by “mention this”? gibi posted about it this morning, the author of the new live migration tests is his colleague. gibi’s going on vacation, so “left it to us” | |
| 16:03:43 | mriedem | mention as in, this could be an rc2 blocker | |
| 16:03:47 | mriedem | since it wasn't tagged | |
| 16:03:51 | mriedem | or in the etherpad | |
| 16:05:00 | cdent | I think it’s new since the weekend | |
| 16:09:48 | openstackgerrit | Stephen Finucane proposed openstack/nova master: trivial: Remove dead function, variable https://review.openstack.org/491512 | |
| 16:15:06 | dansmith | mriedem: mention what? | |
| 16:15:10 | dansmith | mriedem: oh no | |
| 16:17:07 | openstackgerrit | Stephen Finucane proposed openstack/nova master: conf: Convert 'live_migration_inbound_addr' to HostAddressOpt https://review.openstack.org/456573 | |
| 16:23:18 | lvdombrkr | hello guys, im trieng deploy tripleO , and after trying deploy overcloud get error: http://paste.openstack.org/raw/618917/ , in nova scheduler logs i see that tha node is filtred out http://paste.openstack.org/raw/618930/ | |
| 16:23:29 | lvdombrkr | but i dont uderstand why | |
| 16:23:36 | lvdombrkr | any ideas? | |
| 16:24:55 | stephenfin | lvdombrkr: Looks like you'd be better asking #openstack or #tripleo | |
| 16:28:37 | mriedem | mnestratov|2: fyi https://bugs.launchpad.net/nova/+bug/1711547 | |
| 16:28:38 | openstack | Launchpad bug 1711547 in OpenStack Compute (nova) "Nova service restart disconnects vzstorage volumes" [Undecided,New] | |
| 16:29:16 | mnestratov|2 | thanks | |
| 16:32:40 | mnestratov|2 | we will take care of it | |
| 16:32:47 | openstackgerrit | Stephen Finucane proposed openstack/nova master: doc: Address review comments for main index https://review.openstack.org/492645 | |
| 16:33:49 | mriedem | here is that fun ip filtering known issue rearing it's head https://bugs.launchpad.net/nova/+bug/1711303 | |
| 16:33:49 | openstack | Launchpad bug 1711303 in OpenStack Compute (nova) "Filter instances by IP when listing is not efficient enough" [Undecided,Confirmed] | |
| 16:47:58 | cfriesen_ | is anyone aware of a spec around enabling L3 cache in the guests in libvirt? | |
| 16:48:13 | cfriesen_ | or even a blueprint | |
| 16:49:37 | openstackgerrit | Eric Young proposed openstack/nova-specs master: Add ScaleIO ephemeral storage backend https://review.openstack.org/495922 | |
| 17:11:52 | openstackgerrit | Sumedh Degaonkar proposed openstack/nova master: Adds 'sata' as a valid disk bus for qemu and kvm hypervisors https://review.openstack.org/459794 | |
| 17:21:07 | openstackgerrit | Chris Dent proposed openstack/nova master: WIP: [placement] manage cache headers https://review.openstack.org/495380 | |
| 18:37:55 | mriedem | https://review.openstack.org/#/c/495170/ looks legit, just needs some small things cleaned up | |
| 18:47:26 | dansmith | is anyone working on the actual fix for that? | |
| 18:47:42 | mriedem | i'm investigating | |
| 18:47:48 | mriedem | found some more fun | |
| 18:48:47 | mriedem | when you're force live migrating to a specific destination host, conductor checks that there is enough ram https://github.com/openstack/nova/blob/16.0.0.0rc1/nova/conductor/tasks/live_migrate.py#L103 | |
| 18:48:54 | mriedem | via the compute node info, not placement | |
| 18:49:17 | dansmith | ah interesting | |
| 18:49:18 | mriedem | not an immediate problem, | |
| 18:49:32 | mriedem | but will be once we don't track that anymore in the RT/claim | |
| 18:49:35 | dansmith | yeah | |
| 18:49:53 | mriedem | i'll report a bug to track that | |
| 18:49:55 | sean-k-mooney | is there an equivelent to nova reset-state in the openstack client? | |
| 18:54:43 | mriedem | dansmith: i think this existing bug will suffice to track that https://bugs.launchpad.net/nova/+bug/1427772 | |
| 18:54:44 | openstack | Launchpad bug 1427772 in OpenStack Compute (nova) "Instance that uses force-host still needs to run some filters" [Low,Confirmed] | |
| 18:55:00 | mriedem | i just left a new comment for the new state of the world wrt scheduler and compute and RT | |
| 18:55:13 | mriedem | and tagged with placement so it shows up in cdent's weekly email | |
| 18:56:11 | dansmith | I guess.. the link between the two is a little vague | |
| 18:56:56 | mriedem | it could be a separate bug | |
| 18:59:43 | mriedem | dansmith: so the bug is that when forcing the live migration to a specific host, we don't call scheduler_client.select_destinations | |
| 18:59:55 | mriedem | which is eventually the thing that does the double claim on source and dest | |
| 19:00:16 | mriedem | and we don't 'heal' the allocations since everything, at least in this scenario, is pike, so the RT isn't healing | |
| 19:00:48 | mriedem | because of https://review.openstack.org/#/c/491012/ | |
| 19:01:13 | mriedem | in both cases, conductor calls def check_can_live_migrate_destination on the dest host | |
| 19:01:33 | mriedem | so we could create the allocation for the instance and that compute there, or just do it in conductor if we're bypassing the scheduler | |
| 19:02:07 | mriedem | probably simpler to just do it in from conductor, plus then we don't have to worry about check_can_live_migrate_destination trampling over allocations that the scheduler already created | |
| 19:06:41 | dansmith | mriedem: right | |
| 19:07:31 | dansmith | mriedem: I guess I was thinking we should do select_destinations with a force_host of where we're expecting to go so that it creates the allocations properly | |
| 19:08:10 | dansmith | the whole point of the mess we made in pike was to stop managing allocations from separate places (i.e. the compute nodes) so adding another one is not ideal | |