Earlier  
Posted Nick Remark
#openstack-nova - 2019-02-13
15:09:30 bauzas gibi: http://logs.openstack.org/59/631559/5/check/nova-tox-functional/100cfb6/job-output.txt.gz#_2019-02-13_11_19_37_217415
15:09:40 bauzas gibi: any reason why you don't provide the VGPU inventory first ?
15:19:41 openstackgerrit Kashyap Chamarthy proposed openstack/nova master: libvirt: Drop MIN_LIBVIRT_PARALLELS_SET_ADMIN_PASSWD https://review.openstack.org/632514
15:39:14 gibi bauzas: sorry I was dragged away from the keyboard
15:39:24 bauzas gibi: heh, we all are
15:39:38 bauzas or, rather, always dragged from upstream
15:42:56 gibi bauzas: if https://review.openstack.org/#/c/631559/5/nova/tests/functional/libvirt/test_reshape.py@130 fails then it means that the reshape does not moved the VGPU resource away from the compute RP to the GPU RP
15:43:15 gibi bauzas: https://review.openstack.org/#/c/631559/5/nova/tests/functional/libvirt/test_reshape.py@123 should trigger the reshape
15:43:41 bauzas I'll dig into pdbing it
15:43:58 bauzas in the meantime, lemme mark my series as -2
15:54:04 openstackgerrit Alexandra Settle proposed openstack/nova master: Adding cross refs for config options in scheduler filter guide https://review.openstack.org/636635
15:59:07 gibi bauzas: http://logs.openstack.org/59/631559/5/check/nova-tox-functional/100cfb6/job-output.txt.gz#_2019-02-13_11_19_37_215302 here is when the compute is restarted and should do the reshape
16:02:00 openstackgerrit Jack Ding proposed openstack/nova master: Flavor extra spec and image properties validation https://review.openstack.org/620706
16:24:19 melwitt o/
16:50:45 openstackgerrit Matt Riedemann proposed openstack/nova master: Use math.gcd starting with python 3.5 https://review.openstack.org/636669
16:51:40 melwitt mriedem: there's a patch proposed to add basic info about projects to the openstack-map, if you're interested in reviewing the nova info https://review.openstack.org/636604
17:01:46 openstackgerrit Vlad Gusev proposed openstack/nova stable/queens: Handle unicode characters in migration params https://review.openstack.org/636678
17:09:09 mriedem melwitt: commented
17:09:13 mriedem dansmith: replied on https://review.openstack.org/#/c/469675/
17:09:34 mriedem dansmith: for sanity, i think we likely just want to stop using check_availability_zone in both the api and compute
17:09:39 mriedem and write an api-specific version of that
17:10:26 mriedem from the api, gather all the precreated volumes and their azs,
17:10:30 mriedem if any are different, it's an error
17:10:38 mriedem if any are different from the requested server az, it's an error
17:10:58 mriedem if the server is created without a specific az, and the volumes all have the same az, then put that on the request spec
17:12:32 dansmith mriedem: yeah, collect the data and make the call in the compute api
17:12:55 dansmith mriedem: like I said, if the "user requested an az and it doesn't match the volume" case still needs to be handled deep for cleanup reasons, then okay,
17:13:34 dansmith but (a) default_az means something totally different to me when reading the compute/api code and (b) I don't expect either of these mismatch checks to happen so deep down in that file
17:14:03 dansmith so if you don't want to refactor this at all, I'd at least ask that you change the name of that parameter with commentage up in compute/api aboutit
17:15:28 mriedem "the "user requested an az and it doesn't match the volume" case" is what would be in nova-compute after a volume is created
17:15:33 mriedem so yeah i think that remains
17:16:01 dansmith wait
17:16:23 dansmith oh right, yeah
17:17:00 mriedem which reminds me of https://bugs.launchpad.net/nova/+bug/1497253
17:17:02 openstack Launchpad bug 1497253 in OpenStack Compute (nova) "different availability zone for nova and cinder when AZ is not explicitly given" [Low,Fix released] - Assigned to Dan Smith (danms)
17:19:21 openstackgerrit Stephen Finucane proposed openstack/nova master: Remove get_config_vhostuser https://review.openstack.org/565471
17:19:32 openstackgerrit Stephen Finucane proposed openstack/nova master: Validate bandwidth configuration for other VIF types https://review.openstack.org/636383
17:19:44 openstackgerrit Stephen Finucane proposed openstack/nova master: Further de-dupe os-vif VIF tests https://review.openstack.org/636384
17:21:12 stephenfin gibi: Trivial doc fix here, if you fancy taking a look https://review.openstack.org/#/c/636635/
17:26:09 mriedem dansmith: right so i'm thinking leaving the nova-compute behavior the same, and probably move that check_availability_zone method to nova.virt.block_device where it's actually used
17:26:16 mriedem and writing something new in the API
17:26:22 dansmith makes sense
17:26:25 mriedem that has the user-requested (or not) AZ context
17:26:59 mriedem having said that, it's pot-pie-o-clock and i've got a physical this afternoon (first in 10+ years) so my attendance will be spotty
17:27:14 mriedem oh and (don't tell laura) i have to get a valentine
17:27:44 dansmith mriedem: you might be approaching that age where the doctor starts wanting to take your relationship to the next level
17:27:58 mriedem i'm holding out for my 40s
17:28:03 dansmith heh
17:34:32 tzumainn hi! quick question about the expected behavior with nova and ironic; I have four baremetal nodes, and I've created one server that runs on one of the nodes, but if I run "nova hypervisor-servers" against each node, that server shows up for every single node
17:40:36 melwitt tzumainn: are you running one nova-compute service for all four baremetal nodes? if so, I think that might be why it shows up for every node
17:41:08 melwitt I'd have to look into the code to find how the hostname => server lookup is done to confirm
17:41:30 melwitt jroll ^
17:41:43 tzumainn melwitt, ah, yeah, I am
17:42:44 jroll I'm not sure what "nova hypervisor-servers" is
17:42:56 jroll but yeah, probably only goes by compute service hostname, not node name
17:43:26 melwitt it's a command to get a list of servers given a hostname
17:46:29 bauzas dansmith: stop me 1 sec, do we now need to set the host mappings when deploying with devstack ?
17:46:56 dansmith bauzas: devstack should do that for you
17:47:06 jroll melwitt: ah, sounds like a bug in that API response
17:47:26 bauzas dansmith: that was my assumption but I got a Host 'XXX' is not mapped to any cell
17:47:54 dansmith bauzas: on a vanilla devstack setup? shouldn't happen afaik
17:48:30 bauzas technically, a reinstalled devstack but with a ./clean.sh and a reclone=true
17:48:38 melwitt jroll: I get what you mean now, might be returning host instead of node
17:48:41 bauzas weirdo
17:49:02 jroll melwitt: yeah
17:49:34 melwitt thanks
17:50:39 bauzas dansmith: nevermind, looks like a rabbit issue
17:50:50 mriedem bauzas: i'm pretty sure clean.sh isn't maintained
17:50:54 mriedem i never use it
17:51:13 bauzas mriedem: okay, how do we clean the data then ?
17:51:16 bauzas rm -rf ?
17:51:19 melwitt tzumainn: ok, there might be a bug there. I can do some digging later to confirm and check if we have any open bugs or patches about it already
17:51:46 mriedem bauzas: if i need a clean slate i create a new devstack vm
17:51:54 bauzas lucky you :p
17:52:09 mriedem lemme guess, you're running devstack on baremetal with gpus
17:52:12 bauzas here I'm talking of some internal server that I got by accident
17:52:37 bauzas mriedem: yeah, I want to test the reshape series on real hardware
17:53:11 bauzas -where we have RHEL7.5... -
17:53:22 bauzas but anyway, will continue to look
17:53:35 tzumainn melwitt, thanks! I didn't see an existing bug, but looking at https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/hypervisors.py#L167-L168 maybe what I'm seeing is intended behavior, and it's matching based on the hypervisor host_ip (which is the same for all four baremetal nodes)?
17:55:09 mriedem tzumainn: it's a fuzzy search on hypervisor hostname https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py#L680
17:55:42 mriedem for ironic nodes that should actually be a uuid
17:55:47 tzumainn mriedem, yep, that's what I'm using
17:56:47 mriedem and the API code is taking that compute node record and getting all instances on that compute_nodes.host
17:56:50 mriedem which is the same for all of your nodes
17:57:05 mriedem compute_nodes.host == nova-compute service hostname == instances.host
17:57:22 mriedem so it's working as expected, i.e. that API is not ironic-aware
17:57:25 mriedem nor is most of the compute API
17:57:27 mriedem hence MOGAN
17:57:30 melwitt tzumainn: yeah, internally in nova we have hypervisor "hostname" which is associated with the nova-compute service and we have "nodename" which is the ironic nodename. if you're not using ironic hostname == nodename. else, it will be different and to get the right answer (better answer?) for ironic, we'd need to do a lookup based on nodename, not "hostname"
17:57:44 openstackgerrit Adrian Chiris proposed openstack/nova master: Libvirt: do not set MAC when unplugging macvtap VF https://review.openstack.org/624842
17:57:45 openstackgerrit Adrian Chiris proposed openstack/nova master: Add free for claimed, allocated devices https://review.openstack.org/616120
17:57:46 openstackgerrit Adrian Chiris proposed openstack/nova master: Allow per-port modification of vnic_type and profile https://review.openstack.org/607365
17:57:46 openstackgerrit Adrian Chiris proposed openstack/nova master: Add get_instance_pci_request_from_vif https://review.openstack.org/619929
17:57:46 openstackgerrit Adrian Chiris proposed openstack/nova master: SR-IOV Live migration indirect port support https://review.openstack.org/620115
17:57:47 openstackgerrit Adrian Chiris proposed openstack/nova master: libvirt: auto detach/attach sriov ports on migration https://review.openstack.org/629589
17:59:54 tzumainn mriedem, melwitt gotcha - okay, thanks!
18:00:16 mriedem tzumainn: without an api change the best we can do right now is document the wrinkle in the api reference
18:01:11 tzumainn mriedem, would an API change be possible in the longer-term, or would you consider this a tragic wrinkle in how nova/ironic interact?
18:01:42 mriedem tzumainn: i think it could be a possible change on a new microversion - if the resulting compute node we found is of type ironic, we have to lookup instances by nodename, not host

Earlier   Later