Earlier  
Posted Nick Remark
#openstack-nova - 2019-03-26
06:08:23 ileixe s/(all / project scope)/(not all / project project)
06:09:06 ileixe Getting access per every projects for flavor is not fun
06:09:08 ileixe T_T
06:19:08 openstackgerrit Merged openstack/nova stable/pike: Null out instance.availability_zone on shelve offload https://review.openstack.org/606161
06:42:36 openstackgerrit Merged openstack/nova master: Use Selection object to fill request group mapping https://review.openstack.org/638711
06:42:52 openstackgerrit Merged openstack/nova stable/ocata: Handle binding_failed vif plug errors on compute restart https://review.openstack.org/626369
06:43:00 openstackgerrit Merged openstack/nova stable/ocata: Handle unbound vif plug errors on compute restart https://review.openstack.org/626556
06:43:08 openstackgerrit Merged openstack/nova stable/pike: Replace openstack.org git:// URLs with https:// https://review.openstack.org/646684
07:37:41 openstackgerrit Merged openstack/nova stable/ocata: Ensure rbd auth fallback uses matching credentials https://review.openstack.org/627012
07:40:42 openstackgerrit Boxiang Zhu proposed openstack/nova master: Remove unsafe convert of lvm imagebackend https://review.openstack.org/642667
07:54:32 openstackgerrit Boxiang Zhu proposed openstack/python-novaclient master: [WIP] Add force_scheduler in boot instance https://review.openstack.org/647671
07:55:10 openstackgerrit Merged openstack/nova stable/queens: Document unset/reset wrinkle for *_allocation_ratio options https://review.openstack.org/647291
08:10:03 openstackgerrit Eric Fried proposed openstack/nova-specs master: re add numa aware live migration for train https://review.openstack.org/647581
08:21:46 openstackgerrit Eric Fried proposed openstack/nova-specs master: forward port sriov live migration spec to train https://review.openstack.org/647582
08:22:50 openstackgerrit Eric Fried proposed openstack/nova-specs master: forward port sriov live migration spec to train https://review.openstack.org/647582
08:24:17 openstackgerrit Merged openstack/nova master: Re-enable testing of console with TLS in nova-next job https://review.openstack.org/645432
08:24:23 openstackgerrit Merged openstack/nova master: Add description about sort order in API ref guideline https://review.openstack.org/627282
08:30:54 openstackgerrit Merged openstack/nova-specs master: re add numa aware live migration for train https://review.openstack.org/647581
08:34:05 openstackgerrit Merged openstack/nova master: Override the 'get' method in DriverBlockDevice class https://review.openstack.org/638821
08:37:48 openstackgerrit Boxiang Zhu proposed openstack/nova master: [WIP] Scheduler filters evaluated even forced host https://review.openstack.org/645520
08:41:48 openstackgerrit Merged openstack/nova-specs master: forward port sriov live migration spec to train https://review.openstack.org/647582
10:45:42 openstackgerrit Sylvain Bauza proposed openstack/nova master: Add doc on VGPU allocs and inventories for nrp https://review.openstack.org/647519
11:10:05 openstackgerrit Elod Illes proposed openstack/nova stable/stein: Use Selection object to fill request group mapping https://review.openstack.org/647713
11:11:19 openstackgerrit Merged openstack/nova master: Add functional regression test for bug 1669054 https://review.openstack.org/646006
11:11:20 openstack bug 1669054 in OpenStack Compute (nova) "RequestSpec.ignore_hosts from resize is reused in subsequent evacuate" [Medium,In progress] https://launchpad.net/bugs/1669054 - Assigned to Matt Riedemann (mriedem)
11:46:40 openstackgerrit Merged openstack/nova master: Remove last use of rc_fields https://review.openstack.org/645991
13:15:59 openstackgerrit sean mooney proposed openstack/nova master: extend libvirt video model support https://review.openstack.org/647733
13:17:55 mriedem bauzas: want to tweak this quick? https://review.openstack.org/#/c/647519/
13:23:27 mriedem tonyb: is it ok to land the stable/stein upper-constraints change even if we end up doing an rc2 https://review.openstack.org/#/c/645462/ ?
13:23:35 mriedem i would think so
13:28:04 dansmith mriedem: mnaser lyarwood: have we actually got the deployment tools able to deploy and upgrade to new placement yet?
13:28:39 dansmith usually upgrades to new releases don't even start happening until a while after all the projects have cut their final releases, AFAIK, so I would think we haven't seen that yet
13:29:59 mriedem tripleo supports deploy of extracted placement but not yet upgrade from placement-in-nova according to lyarwood's last update
13:30:13 mriedem kolla supports deploy extracted placement from source / pypi i think
13:30:14 mriedem cdent: ^
13:30:29 mriedem some of the deployment tools can't deploy from packages yet b/c there aren't packages yet
13:30:32 dansmith right, deploy but not upgrade right?
13:30:35 dansmith right
13:30:38 mriedem as far as i know
13:30:50 cdent yeah, deploy but not upgrade is my understanding as well
13:30:59 cdent I haven't checked in the last week or so, though
13:31:07 dansmith I'm just thinking that this early into train, nothing has changed from the situation a month ago where the deployment tools are the sticking point
13:32:16 cdent is this referencing some earlier discussion? which "we haven't seen that yet" is this?
13:32:41 dansmith just the placement delete patch
13:32:58 cdent ah, okay, I thought perhaps that was it, but wasn't sure
13:34:05 dansmith we can cut and run and they'll just have to catch up, but it means they'll have to implement that and/or resolve issues before they can get their stein->master upgrades working at all
13:34:16 dansmith so just wondering what progress they have made or how close that is for them
13:34:50 shilpasd mriedem: Hi, going through https://bugs.launchpad.net/nova/+bug/1784020, can you help me to understand more points mentioned here in 2.a and 2.b, want to reproduce and figure out the fixes for it
13:34:51 openstack Launchpad bug 1784020 in OpenStack Compute (nova) "Shared storage providers are not supported and will break things if used" [Medium,Fix released]
13:34:53 cdent I kinda feel like some sort of forcing function is required, but that may be either unrealistic or rude
13:35:59 dansmith yeah could be, but before the previous release is even out might be a teensy bit aggresive
13:36:04 dansmith (but spelled properly)
13:36:58 dansmith the deployment projects also receive the forcing-function love from all projects simultaneously, which isn't super fun :)
13:37:15 cdent if we choose to wait, I will keep the patch up to date
13:37:33 cdent somebody just keep me informed please
13:37:57 mriedem oh i didn't realize there were +2s stacked up on https://review.openstack.org/#/c/618215/
13:38:02 mriedem yeah that's way too aggressive IMO
13:38:15 dansmith easy for me to say, but it doesn't look like there are too many places that it will be conflict-heavy
13:38:36 dansmith mriedem: yeah, that was my concern
13:39:24 cdent I think only conf and cmd stuff is likely to conflict, if at all
13:39:54 mriedem honestly i'd probably proceduraly -2 that for now
13:39:57 mriedem efried: stephenfin: ^
13:40:20 cdent it was until yesterday
13:40:37 stephenfin mriedem: Yup, I wasn't sure so I held off on the +W. Happy for someone -2 that for now, yup
13:41:06 cdent If this turns into nova-net, I'm going to burn a hole through the earth
13:41:34 dansmith could we maybe tell the deployment projects that we're going to merge this the week of the PTG, so they should either get it done before then or show up with lots of reasons and gifts if not?
13:41:50 cdent seems a reasonable plan
13:43:08 mriedem i think dropping at the ptg is a good idea b/c there is a forum session on extraction right before that as well
13:43:21 mriedem as a final 'in 2 days we're going to drop this code from nova, any questions?'
13:43:23 dansmith yeah
13:56:06 mnaser dansmith, mriedem, cdent: OSA hasn’t progressed unfortunately. However, having an official timeline would be nice
13:56:29 mnaser So I’m supportive of at least knowing when it will be done.
13:56:53 mnaser We can probably get deploy from extracted easily but orchestrating the upgrade is the hard part
13:57:58 openstackgerrit Matt Riedemann proposed openstack/nova master: api-ref: add more details to confirmResize troubleshooting https://review.openstack.org/647741
13:58:16 mriedem efried: there is some wording for the API reference ^
13:59:23 dansmith mnaser: oh I thought deploy from extracted was already working, but I'm sure I was just confusing that with tripleo or something
14:01:48 mnaser Yeah, well, we have an ansible role that deploys placement only. But we have not integrated the role with our playbooks
14:01:55 dansmith ah, okay
14:12:31 mriedem mdbooth: if you're busy do you care if i add the unit test for https://review.openstack.org/#/c/645546/ ?
14:14:19 trident Hmm. Is trait:CUSTOM_FOO=forbidden set as flavor property expected to work in stable/rocky? I get instances spun up with flavors with that set ending up on resource providers (compute nodes) with that trait set. The other way around seem to work - a flavor with trait:CUSTOM_FOO=required makes instances with that flavor end up on the resource providers with that trait set.
14:15:51 mriedem trident: says it should https://docs.openstack.org/nova/rocky/user/flavors.html
14:15:58 mriedem "Added in the 18.0.0 Rocky release."
14:16:49 mdbooth mriedem: I'd be delighted :) I'm currently working on https://bugs.launchpad.net/nova/+bug/1821373
14:16:50 openstack Launchpad bug 1821373 in OpenStack Compute (nova) "Most instance actions can be called concurrently" [Undecided,New]
14:17:52 trident mriedem: Yeah, that's what I thought as well, so I am a bit surprised. Didn't really find any bugs that seem relevant either.
14:17:58 mriedem mdbooth: ok will do. another thing was https://review.openstack.org/#/c/551349/ just needs some tweaks i think, but it looks like maybe lyarwood is working that now
14:18:08 mriedem unless lyarwood is stuck in tripleo limbo for the next month
14:18:27 openstackgerrit Sylvain Bauza proposed openstack/nova master: Add doc on VGPU allocs and inventories for nrp https://review.openstack.org/647519
14:18:46 mdbooth mriedem: He's away this week, but he has taken that patch.
14:19:29 mriedem trident: if it's helpful, here is a functional test that does traits-based scheduling https://github.com/openstack/nova/blob/358776a303b0c5dba3c279f242c82b7a12ff5ce8/nova/tests/functional/test_servers.py#L4451
14:20:09 trident mriedem: Butt still the API call to placement /allocation_candidates doesn't seem to pass the forbidden trait (which if I understand it correctly should be "required=!CUSTOM_FOO" while it does pass it for the flavor with trait required: "required=CUSTOM_FOO"
14:21:08 trident mriedem: Thanks, I'll keep looking then, just wanted to check that I am not missing anything obvious.
14:21:33 mriedem hmm, looking at the test in there that uses a forbidden trait on a flavor https://github.com/openstack/nova/blob/358776a303b0c5dba3c279f242c82b7a12ff5ce8/nova/tests/functional/test_servers.py#L4824 it doesn't seem like the forbidden trait is actually testing anything useful
14:22:26 mriedem meaning, a better test would be to have something like 2 computes, one with trait CUSTOM_FOO and one without, and disable the one without so we can't schedule there, then schedule with forbidden CUSTOM_FOO and it should have a NoValidHost result,
14:22:33 mriedem but you're saying it sounds like it might just pass
14:23:42 trident mriedem: I'll see what I find continuing the troubleshooting and get back...
14:24:13 mriedem ack, this is the code that builds the GET /allocation_candidates query string fwiw https://github.com/openstack/nova/blob/358776a303b0c5dba3c279f242c82b7a12ff5ce8/nova/scheduler/utils.py#L257
14:28:03 trident mriedem: Thanks. that's exactly where I am currently looking :)
15:01:36 brandor5 hello everyone: I'm trying to use hypervisor_hostname as a scheduler hint and it's worked in the past but I'm running into issues now... I get a 400 bad request back... anyone have any ideas why that could be?
15:02:12 openstackgerrit Matt Riedemann proposed openstack/nova master: Fix incomplete instance data returned after build failure https://review.openstack.org/645546

Earlier   Later