Earlier  
Posted Nick Remark
#openstack-nova - 2018-02-27
10:24:03 Kevin_Zheng So I guess after calling cyborg/neutron, nova will have filter hosts by names to get allocation candidates?
10:24:25 Kevin_Zheng if we have specific network/accelerator requests?
10:24:35 tonyb mriedem: okay I'll look over them
10:28:37 exarr Anyone able to tell me, if I try to create a server, and it fails for $random_reason and hits an error state - is there a good way to retry the rebuild?
10:28:48 gibi Kevin_Zheng: whta do you mean by specific accelerator request?
10:28:49 exarr (Currently I delete, and supply all the detail over again)
10:28:52 openstackgerrit Jianghua Wang proposed openstack/nova master: XenAPI: provide VGPU_DISPLAY_HEAD inventory in compute node https://review.openstack.org/523342
10:29:47 Kevin_Zheng gibi create instances with accelerator=xxx in the flavor extra_spec
10:29:51 Kevin_Zheng for example
10:31:15 gibi Kevin_Zheng: is that xxx a type of accelerator or one given physical accelerator instance on some specific compute?
10:31:42 Kevin_Zheng type
10:32:31 Kevin_Zheng nova and cyborg will try to allocate the instance to the most suitable host
10:32:41 Kevin_Zheng in whatever way
10:35:12 gibi Kevin_Zheng: then in your example it is a VM boot case. In that case nova has to get the needed resources/traits for the accelerator either from cyborg or alternatively from flavor extra spec and include that in the GET allocation_candidate request for placement
10:35:49 gibi Kevin_Zheng: then placement will return candidates that satisfy both nova and cyborg related resouces
10:38:02 Kevin_Zheng gibi, yeah, as for now cyborg can only connect their own resource providers with nova resource providers by name, maybe the filter by hostname should be added to nova allocation candidates process together with CPU/RAM/Disk filtering?
10:41:55 gibi Kevin_Zheng: cyborg connect the accelerator RPs to the related compute RPs by name, then nova asks placement, where are those RPs (RP trees) that satisfy the resource request (that includes both cpu/ram/disk and accelerator resources/traits) then so placement will already only return those RP trees that can provide both cpu/ram/disk and accelerator resources. No additional filtering is needed by nova
10:42:11 gmann_ gibi: we are discussing job template and irrelevant files in Davin suit 4th floor, if you want to join
10:42:37 gibi gmann_: thanks for the heads up. on my way
10:42:58 gmann_ cool
10:43:24 Kevin_Zheng gibi got it
10:49:10 openstackgerrit Chris Dent proposed openstack/nova-specs master: Provide error codes for placement API https://review.openstack.org/418393
10:53:05 stelucz_ Hello is there any way how to update or sync `OS-EXT-SRV-ATTR:host` and `OS-EXT-SRV-ATTR:hypervisor_hostname` properties? because `nova show` reports different hypervisor than where vm is hosted. This happened after live migration. Thanks
11:04:20 Kevin_Zheng Just poping to my head, since we have instance task states like networking, block_device_mapping, we might also have something for FPGA?
11:07:00 mriedem fpga-a-ing
11:07:08 mriedem accelerating
11:08:10 melwitt I vote for fpga-a-ing
11:08:47 gibi Kevin_Zheng: I think we have networking as we instruct neutron to bind ports. so the question for FPGA case is do nova needs to "bind" FPGAs?
11:10:24 Kevin_Zheng gibi I thought the idea is to call cyborg to do "bind" actions in nova-compute? but correct me if I'm wrong
11:11:19 gibi Kevin_Zheng: I'm not up to date about that part of the cyborg-nova interaction
11:12:10 Kevin_Zheng mridem decelerating for detach?
11:12:20 Kevin_Zheng :)
11:15:53 Kevin_Zheng gibi, I think we can find it out this afternoon
11:19:49 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove unused LOG variables https://review.openstack.org/546097
11:32:30 openstackgerrit Matt Riedemann proposed openstack/nova master: libvirt: mask InjectionInfo.admin_pass https://review.openstack.org/526772
11:36:35 bauzas Kevin_Zheng: gibi: mriedem: alex_xu: huh, just saw https://review.openstack.org/#/c/318047/6/specs/backlog/approved/fpga-use-cases.rst
11:36:58 openstackgerrit Murali Annamneni proposed openstack/nova master: Enables MySQL Cluster Support for Nova https://review.openstack.org/446643
11:37:25 bauzas I refrain commenting here about late binding, but I just feel that's up to the compute manager to make the device available to the instance
11:37:54 bauzas the only thing we need to care is to make sure the host that the instance is going is having *that* accelerator
11:38:09 mriedem that is pretty old, and i think came up from another spec that was in cyborg that was abandoned
11:38:09 bauzas how the binding is done, meh to me
11:38:26 mriedem this https://review.openstack.org/#/c/448228/
11:38:33 bauzas it's a backlog spec, I'm fine with reviewing it
11:38:37 mriedem i guess that's actually newer
11:38:52 alex_xu bauzas: thinking of the late binding, there still have dependence between nova and cyborg, since there need a way to get requested resource class from the cyborg, special with the way of neutron bandwidth
11:39:00 mriedem i haven't been paying attention to any of the cyborg hoopla you guys have all been talking about all day
11:39:12 bauzas mriedem: yeah the new one is https://review.openstack.org/#/c/508572/5/specs/proposal/cyborg-nova-interaction.rst
11:39:42 bauzas I'm just done with discussing about cyborg :p
11:39:48 alex_xu bauzas: to get rid of the dependence there should be a way to boot instance like 'nova boot --device <cyborg_accelerator_uuid> --resource-class RC_FPGA...
11:40:11 bauzas alex_xu: yeah, I was thinking of saying it was a pci device...
11:40:28 bauzas but then, you could have some usb accelerator device...
11:40:48 alex_xu ok~ usb accelerator...
11:41:28 alex_xu bauzas: if using the pci device, how to get the required pci device in Nova, for the sriov, we have API call to neutron to get the physnet
11:41:56 alex_xu And whatever, that sounds like we have API call to cyborg, a dependence again
11:42:47 bauzas alex_xu: if it's a regular PCI device, we don't call Neutron, right?
11:43:15 alex_xu bauzas: yes, something in the flavor extra spec, right?
11:43:17 bauzas https://docs.openstack.org/nova/latest/admin/pci-passthrough.html
11:43:55 bauzas I was thinking of something like Cyborg modifying the pci whitelist and then modify the flavors, et voila :p
11:44:40 bauzas keep it easy :)
11:48:12 edleafe bauzas: Room 665 at 2pm :)
11:48:45 bauzas I know the room, I was there yesterday all the afternoon :p
11:48:56 edleafe I'm here now :)
11:49:04 bauzas it's f***ing way off the other roomd
11:49:16 bauzas it feels like you're in another city
11:49:31 bauzas edleafe: I guess they're done with my face :p
11:49:49 edleafe bauzas: no comment :P
11:49:58 bauzas edleafe: just an advice, keep it secret that you work on nova or you'll be discussing about bugs :p
11:50:14 edleafe bauzas: already had a few placemnt discussions
11:51:28 bauzas edleafe: ok, I guess nothing new but how to flow the placing decision to have a fresh FPGA ?
11:51:44 edleafe still working on that :)
11:51:56 bauzas ok, I can join
11:52:07 openstackgerrit Chris Dent proposed openstack/nova-specs master: Update placement aggregates spec to clarify generation handling https://review.openstack.org/548237
11:55:53 stelucz_ Hello is there any way how to update or sync `OS-EXT-SRV-ATTR:host` and `OS-EXT-SRV-ATTR:hypervisor_hostname` properties? because `nova show` reports different hypervisor than where vm is hosted. This happened after live migration. Thanks
11:58:18 efried stelucz_: Responsiveness may be spotty this week during the PTG. Is there a LP bug for this issue? If not, please open one, paying attention to the template (e.g. so we know the details of your release, environment etc.)
12:04:18 stelucz_ efried: Hi, no, there isn't LP bug. Probably just bad timing of some actions and migration as this didn't happen in past. I am just curious if there is some way to force update of these properties or way to edit them.
12:09:55 efried stelucz_: I'm afraid I don't know that answer, sorry. Perhaps an email to the openstack-dev and/or openstack-operators mailing list will get you a better (asynchronous) response this week.
12:13:42 stelucz_ efried: thanks a lot!
12:14:00 efried Good luck
12:21:43 openstackgerrit Merged openstack/nova stable/ocata: Rollback instance.image_ref on failed rebuild https://review.openstack.org/539008
12:28:13 openstackgerrit Chris Dent proposed openstack/nova master: Provide framework for setting placement error codes https://review.openstack.org/546177
12:29:52 openstackgerrit Eric Fried proposed openstack/nova master: WIP: placement: generation in RP agg APIs https://review.openstack.org/548249
13:30:04 openstackgerrit Merged openstack/nova master: compute: Cleans up allocations after failed resize https://review.openstack.org/543971
14:03:24 openstackgerrit Matt Riedemann proposed openstack/nova stable/queens: libvirt: mask InjectionInfo.admin_pass https://review.openstack.org/548289
14:05:39 openstackgerrit Merged openstack/python-novaclient master: Fix a comment in novaclient/api_versions.py https://review.openstack.org/546897
14:07:16 openstackgerrit Chris Dent proposed openstack/nova master: Move db MAX constants to own file https://review.openstack.org/543469
14:11:27 maciejjozefczyk mriedem: I reproduced the problem I mentioned during PublicCloud working group (missing ports); https://bugs.launchpad.net/nova/+bug/1751923
14:11:28 openstack Launchpad bug 1751923 in OpenStack Compute (nova) "_heal_instance_info_cache periodic task bases on port list from nova db, not from neutron server" [Undecided,New] - Assigned to Maciej Jozefczyk (maciej.jozefczyk)
14:11:43 maciejjozefczyk mriedem: Please take a look :)
14:12:29 mriedem ack
14:18:19 omegapoint hey, can anyone tell me what needs to happen for an instance to leave task_state SCHEDULING? i have a very odd problem, all my nova services are healthy and not reporting any warnings / errors (nothing suspicious in debug log either) but instances aren't getting scheduled. all hypervisors are up and updating their resources properly
14:18:54 omegapoint updated the cell mappings
14:20:11 openstackgerrit Maciej Jozefczyk proposed openstack/nova master: Add default values for allocation ratios https://review.openstack.org/532924
14:23:08 openstackgerrit Claudiu Belu proposed openstack/nova stable/queens: compute: Cleans up allocations after failed resize https://review.openstack.org/548300
14:24:12 openstackgerrit Claudiu Belu proposed openstack/nova master: compute: Adds instance live-resize https://review.openstack.org/248581
14:24:13 openstackgerrit Claudiu Belu proposed openstack/nova master: API: Adds instance live-resize https://review.openstack.org/184584
14:24:13 openstackgerrit Claudiu Belu proposed openstack/nova master: conductor: add live_resize task https://review.openstack.org/248579
14:30:24 openstackgerrit Merged openstack/nova master: Make _get_sharing_providers more efficient https://review.openstack.org/547008
14:55:29 openstackgerrit Chris Dent proposed openstack/nova master: Provide framework for setting placement error codes https://review.openstack.org/546177
15:04:53 openstackgerrit Merged openstack/nova stable/pike: Store block device mappings in cell0 https://review.openstack.org/546219
15:06:22 openstackgerrit Matt Riedemann proposed openstack/nova stable/pike: libvirt: mask InjectionInfo.admin_pass https://review.openstack.org/548312

Earlier   Later