| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2020-06-03 | |||
| 23:15:50 | melwitt | np, gnight o/ | |
| #openstack-nova - 2020-06-04 | |||
| 08:41:43 | bauzas | good morning Nova | |
| 08:47:32 | gibi | bauzas: good morning | |
| 09:04:04 | xiaolin | hello guys, I'm trying to run openstack on a host with MIPS architecture, but got an error "Instance failed to spawn: libvirtError: internal error: unexpected host-model CPU for mips64el architecture" while creating an instance. | |
| 09:04:18 | xiaolin | Anyone can guide me how I can contribute a fix to upstream? need I report a bug first? | |
| 09:18:05 | gibi | xiaolin: does this similar to what belmoreira requested here? https://bugs.launchpad.net/nova/+bug/1863728 | |
| 09:18:05 | openstack | Launchpad bug 1863728 in OpenStack Compute (nova) "Nova can't create instances for a different arch" [Wishlist,Invalid] | |
| 09:19:50 | gibi | xiaolin: we will discuss ^^ today during the PTG https://etherpad.opendev.org/p/nova-victoria-ptg | |
| 09:27:50 | xiaolin | gibi: The problem I encountered is not similar to what belmoreira requested | |
| 09:28:51 | xiaolin | gibi: the host and instance are both MIPS architecture | |
| 09:28:51 | alex_xu | gibi: sean-k-mooney does neutron already report physical network interface resource provider? accroding to the spec https://specs.openstack.org/openstack/neutron-specs/specs/rocky/minimum-bandwidth-allocation-placement-api.html | |
| 09:30:40 | gibi | xiaolin: I see. Then I don't have a direct answer. the libvirt error suggest that something is missing from the libvirt side. Are you able to start a VM purely with libvirt / virsh on your host? | |
| 09:30:49 | belmoreira | gibi xiaolin unfortunately I won't be able to join | |
| 09:31:17 | gibi | belmoreira: thanks for the headsup, we will discuss it anyhow | |
| 09:31:46 | gibi | alex_xu: neutron reports SRIOV PF and OVS bridge as RP in placement with physnet and vnic type trait | |
| 09:31:58 | alex_xu | gibi: got it | |
| 09:32:05 | gibi | alex_xu: but only if bandwidth is defined in the agent conf for these devices | |
| 09:32:22 | alex_xu | gibi: just read the cyborg sriov doc, begin to think about..cyborg will report any RP for PF... | |
| 09:32:46 | alex_xu | s/report any/report another/ | |
| 09:32:56 | xiaolin | gibi: Yes, I can start a VM purely with libvirt / virsh on my host | |
| 09:33:36 | gibi | alex_xu: I guess we have to decide if neutron or cyborg owns the PF | |
| 09:33:40 | alex_xu | gibi: ok, if they are totally two feature, should be ok. Since those cyborg PF's RP should be managed by cyborg...not sure how cyborg and neutron merge them... | |
| 09:33:53 | alex_xu | gibi: yea, that is something to decide | |
| 09:36:06 | gibi | xiaolin: please look at the host-model documentation https://docs.openstack.org/nova/latest/admin/configuration/hypervisor-kvm.html#specify-the-cpu-model-of-kvm-guests you might need to configure the nova a bit differently for using your hardware. | |
| 09:37:11 | gibi | xiaolin: also I hope kashyap could help from libvirt perspective | |
| 09:41:52 | xiaolin | gibi: Thank you. I will read the documentation | |
| 10:12:21 | kashyap | xiaolin: Oh, MIPS ... you are the first I've come across here :) | |
| 10:12:59 | kashyap | gibi: xiaolin: So the error "unexpected host-model" simply means, MIPS in libvirt doesn't have the notion of 'host-model' | |
| 10:13:07 | kashyap | So, let me check what's possible there... | |
| 10:15:41 | kashyap | xiaolin: What you could try is: launch your `qemu-system-mips -cpu help` (or whatever the MIPS QEMU binary is called) | |
| 10:15:53 | kashyap | xiaolin: On the Compute host, and configure that as an explicit CPU model in Nova: | |
| 10:16:09 | gibi | kashyap: thanks for the help :) | |
| 10:16:55 | kashyap | [libvirt] | |
| 10:16:55 | kashyap | cpu_mode = custom | |
| 10:16:56 | kashyap | cpu_model = $My_MIPS_CPU_FIXME | |
| 10:17:00 | kashyap | gibi: Happy to be useful :) | |
| 10:32:49 | sean-k-mooney | alex_xu: they way the cyborg driver work there is no filtering so yes it would report any PF that the driver could manage | |
| 10:33:19 | sean-k-mooney | gibi: today nova owns the pf not neutron | |
| 10:33:35 | sean-k-mooney | neutron only owns the bandwidth | |
| 10:34:11 | sean-k-mooney | when we start reporting pci device to placement form nova we will be the ones creating the inventories for the VFs | |
| 10:43:30 | gibi | sean-k-mooney: today neutron creates the PF RPs and reports bandiwdth inventory on it, when we start reporting VF inventory from nova we need to agree with neutron who creates the PF RP or we have to create two RPs for a PF one from neutron perspective and one from nova perspective and then connect them somehow | |
| 10:44:23 | sean-k-mooney | gibi: nova need to do it because it needs to be consitient with non nic pci devices | |
| 10:44:42 | sean-k-mooney | unless we are going to specal case when the device has a physnet tag on the pci whitelist | |
| 10:44:57 | sean-k-mooney | which we coudl do but then we need two different code paths | |
| 10:45:20 | sean-k-mooney | gibi: ideally it would end up being one RP | |
| 10:45:49 | sean-k-mooney | unless we extend placemets data model with a way to link rps | |
| 10:54:04 | sean-k-mooney | gibi: quick question do you want a blueprint or a spec to track the machine type recodeing work? | |
| 10:54:56 | sean-k-mooney | as part of that i would like to start reporing avialble machine types as traits to placemnt and the schdlueling on that | |
| 10:55:49 | sean-k-mooney | e.g. if we do a move opperation on an exsting instance i want to ensure we land it on a host that supports that machine type | |
| 10:56:16 | sean-k-mooney | and if we are creating a new instance and you request a machine type in the image i want to ensure we land on a host that supports that too | |
| 10:56:29 | sean-k-mooney | both of which would be done by a prefilter | |
| 10:57:04 | sean-k-mooney | just addign the required tratit based on the instance system metadata or image metdata | |
| 11:00:12 | gibi | sean-k-mooney: sorry I was lunching. | |
| 11:00:19 | sean-k-mooney | no worries | |
| 11:01:02 | gibi | sean-k-mooney: agree that it would be nice to have on RP for one physical entity (like a PF or other PCI device) | |
| 11:01:29 | gibi | sean-k-mooney: I just wanted to note that this might requires changes both from nova and neutron | |
| 11:01:56 | gibi | btw placement has two ways today to link RPs, one is the parent-child relationship and the other is aggregates | |
| 11:02:44 | sean-k-mooney | yep altought i was thinking more of something like a symlink | |
| 11:03:00 | gibi | sean-k-mooney: I guess you don't need db schema rpc or REST API changes for the machine type recording work so I think a bp is enough | |
| 11:03:15 | sean-k-mooney | aggreate wont work because we can do member of in this case | |
| 11:03:39 | gibi | sean-k-mooney: yeah aggregates would be a bit ugly I agree | |
| 11:03:45 | sean-k-mooney | and parent-child likely wont work because we neither nova or neutron knows the uuid/name that will be used for the RP | |
| 11:04:05 | sean-k-mooney | that said we can work this out when we need too | |
| 11:05:56 | sean-k-mooney | gibi: are you ok with also doing the traits reporting and prefileter in the same specless blueprint. | |
| 11:06:13 | sean-k-mooney | ill write it up and i guess we can decide then | |
| 11:07:00 | sean-k-mooney | i assume a specless blueprint is also fine for the doc change to add the common profiles(nfv,realtime,modren) that we talked about too | |
| 11:07:35 | sean-k-mooney | im going to try and get those up before we resume today | |
| 11:11:19 | gibi | sean-k-mooney: the prefilter work is a bit of a grey area as I guess that needs a new config flag to enable since old computes will not report the traits | |
| 11:11:45 | gibi | so you might only want to enable the prefilter after all your computes are on V | |
| 11:12:11 | sean-k-mooney | yes although we could auto enable based on the min compute service version too. | |
| 11:12:16 | gibi | sean-k-mooney: specless bp for the hw:profile doc is totally OK | |
| 11:12:45 | gibi | sean-k-mooney: OK, note this upgrade wrinkel in the specless bp then I'm OK | |
| 11:13:19 | sean-k-mooney | sure will do. if i end up having to write a small spec its not the end of the world either but we will see what other think once its up | |
| 11:13:22 | gibi | sean-k-mooney: we will bring this bp up in the next nova meeting for approval so the rest of the team can complain if they need more words about it | |
| 11:13:45 | sean-k-mooney | sure works for me | |
| 11:13:50 | gibi | awesome | |
| 11:13:51 | gibi | thanks | |
| 11:48:08 | openstackgerrit | Balazs Gibizer proposed openstack/nova-specs master: Make Feature Liaison optional https://review.opendev.org/730638 | |
| 12:30:31 | gibi | nova will continue the PTG session in 30 minutes in the Juno Zoom room. | |
| 12:32:47 | sean-k-mooney | crap already i guess i better get coffee and water ready so | |
| 12:34:25 | gibi | I've just did the same, water, coffee, and replaced the air in the room :) | |
| 12:34:57 | gmann | gibi: added one more topic (in the last) about removing the old and deprecated user level policy restriction. it was reminded by current ML thread. | |
| 12:35:26 | gmann | it should be ok to remove as we already doing warning for 4 years but good to check in PTG if anyone still using that way. | |
| 12:36:11 | sean-k-mooney | gibi: i bought a https://www.amazon.co.uk/Samson-SAQ2U-Microphone-Recording-Pack/dp/B001R747SG dnymic mic and stand so i can turn on my ceiling fan without out it being picked up without having to use a headset | |
| 12:37:17 | gibi | gmann: Is it OK to for you if I move that topic up to the first slot today where we anyhow talk about removals and deprecation? | |
| 12:37:43 | gibi | sean-k-mooney: that mic look serious :) | |
| 12:37:55 | gmann | gibi: yeah, that is totally fine. | |
| 12:38:00 | gibi | gmann: cool | |
| 12:38:04 | gmann | thanks | |
| 12:40:56 | sean-k-mooney | gibi: well i work form home permently and have calls regualarly but ya its a live stage mic that alot of twitch/game stream also use. for like 60 euro its good value too | |
| 12:42:14 | openstackgerrit | Merged openstack/nova-specs master: Make Feature Liaison optional https://review.opendev.org/730638 | |
| 12:46:41 | gibi | sean-k-mooney: yeah, sounds like a good idea for a home office. I only do full home office due to COVID | |
| 12:48:48 | gmann | johnthetubaguy: you want to do quick fix on release name in https://review.opendev.org/#/c/732173/1 | |
| 12:50:23 | johnthetubaguy | gmann: oops, looking | |
| 12:51:03 | openstackgerrit | John Garbutt proposed openstack/nova-specs master: Re-propose Unified Limits in Nova https://review.opendev.org/732173 | |
| 12:53:06 | alex_xu | sean-k-mooney: gibi so for neutron sriov agent, I guess it has no way to discover the VF? since it won't read from libvirt | |
| 12:59:35 | sean-k-mooney | alex_xu: it does but not in a useful way | |
| 12:59:51 | sean-k-mooney | you have to list the netdev names of the PF in its config | |
| 13:00:05 | sean-k-mooney | and it uses iptool i think | |
| 13:00:17 | gibi | alex_xu: nova sends pci_slot information to neutron in the binding profile but yeah as sean-k-mooney said the pci whitelist is on nova side today to specify what VF and PF resource is usable | |