Earlier  
Posted Nick Remark
#openstack-nova - 2018-03-21
14:05:18 bauzas I have a devstack running somewhere
14:05:21 bauzas I can show it
14:05:44 bauzas mriedem: replied on https://bugs.launchpad.net/nova/+bug/1752463
14:05:46 openstack Launchpad bug 1752463 in OpenStack Compute (nova) "Attaching virtual GPU devices to guests in nova" [Medium,Incomplete]
14:05:55 bauzas mriedem: thoughts on providing docs related to a specific device ?
14:06:02 mriedem yeah so vgpu will show up in placement, and you can use osc-placement to get the CLI
14:06:20 mriedem simple tenant usage is going to be woefully out of date wrt the new fangled placement resources
14:06:33 bauzas mriedem: IMHO, those kinds of driver-specific docs should be done downstream (like with RH OSP)
14:06:55 edmondsw use case 1... need to query inventory data (type, whether / to what VM they are allocated, etc.) of GPUs and vGPUs on a given host
14:07:04 bauzas mriedem: but if you'd like to get some nvidia specific details in https://docs.openstack.org/nova/queens/admin/virtual-gpu.html , lemme know
14:07:05 mriedem bauzas: a small 'driver notes' section or something for known issues seems ok in the openstack docs
14:07:14 bauzas mriedem: okay,n
14:07:18 bauzas mriedem: I can add a note then
14:07:19 edmondsw use case 2... need to query inventory data of GPUs and vGPUs allocated to a given VM
14:07:22 mriedem doesn't answer my question if https://review.openstack.org/#/c/459753/ handles this
14:07:24 mriedem for nvidia
14:07:31 edmondsw I think we can get some of that from placement, but not all?
14:07:32 bauzas mriedem: no, it's not helping
14:07:46 mriedem edmondsw: i think you can get all of that from placement
14:07:48 bauzas mriedem: hiding is just for PCI passthrough
14:08:02 mriedem edmondsw: and with what's already available in the CLI https://docs.openstack.org/osc-placement/latest/index.html
14:08:21 bauzas mriedem: the problem with OVH is that they use some product lines that are not accepted by the nvidia driver :p
14:08:35 bauzas mriedem: so they hide the fact they're virtualizging
14:08:58 bauzas mriedem: but in order to make virtual GPUs, you need a specific product line anyway
14:10:47 edmondsw mriedem can you query the placement API by server instance?
14:10:52 bauzas shit, pilgrimstack isn't here
14:11:28 edmondsw if not, then placement doesn't give you use case 2
14:11:30 bauzas can't remember the product that OVH used for their production boxes, but it's not a Tesla line
14:11:45 bauzas hence the need for hiding the virt driver
14:13:26 bauzas edmondsw: https://developer.openstack.org/api-ref/placement/#list-allocations
14:13:44 bauzas edmondsw: the consumer_uuid is the instance UUID
14:14:00 mriedem edmondsw: yes
14:14:01 edmondsw bauzas ah tx
14:14:06 bauzas edmondsw: it'll show up the existing allocations for each RP
14:14:18 mriedem edmondsw: in the CLI, the instance == the consumer
14:14:33 mriedem edmondsw: https://docs.openstack.org/osc-placement/latest/cli/index.html#resource-provider-allocation-show
14:14:37 mriedem that's the one you want i think
14:14:43 mriedem shows allocations for a given consumer (instance)
14:15:03 mriedem https://docs.openstack.org/osc-placement/latest/cli/index.html#resource-provider-inventory-show shows inventory for a given provider (compute node)
14:15:11 edmondsw thanks
14:15:38 mriedem if you love that stuff, https://review.openstack.org/#/q/status:open+project:openstack/osc-placement+branch:master+topic:bp/placement-osc-plugin-rocky
14:15:42 mriedem reviews welcome
14:20:12 bauzas jaypipes: cfriesen: stephenfin: efried: thanks for your reviews on https://review.openstack.org/#/c/552924/3
14:20:25 bauzas I need to look at all of them
14:22:25 Kevin_Zheng Hi, could anyone kindly provide some suggestions on funcional tests in https://review.openstack.org/#/c/553288/
14:24:39 bauzas jaypipes: efried: stephenfin: could we maybe do a hangout based on https://review.openstack.org/#/c/552924/3/specs/rocky/approved/numa-topology-with-rps.rst ?
14:25:13 jaypipes bauzas: maybe tomorrow morning?
14:25:23 jaypipes bauzas: currently working on a number of things that might affect that
14:25:25 Kevin_Zheng I'm adding 'request_id' field to the nofitications, while testing, I have to compare the 'request_id' field in the payload with the reference, as req_id is in the response header, so it seems I have to modify the return value in common methods in nova.tests.functional.api.client, don't know if this is a suitable approach or not
14:25:44 bauzas jaypipes: I'm not in a rush
14:25:56 efried bauzas: I'm game. Just let me know.
14:26:06 bauzas jaypipes: I just felt that sharding our resources between NUMA nodes is at risk
14:26:20 bauzas jaypipes: hence the use of specific RCs
14:26:48 openstackgerrit Dan Smith proposed openstack/nova stable/queens: Add --by-service to discover_hosts https://review.openstack.org/554600
14:30:54 stephenfin bauzas, jaypipes: Tomorrow afternoon (GMT) would be OK with me, yes
14:31:07 bauzas k
14:31:11 bauzas we could need cfriesen too
14:31:22 bauzas but he's in another TZ
14:36:43 mriedem Kevin_Zheng: it looks like that patch is already testing what you want
14:36:51 mriedem the sample in https://review.openstack.org/#/c/553288/4/doc/notification_samples/common_payloads/InstanceActionPayload.json is just for docs,
14:36:59 mriedem the request id generated in the functional test run is going to be unique,
14:37:21 mriedem which is why you are doing the replacement stuff in https://review.openstack.org/#/c/553288/4/nova/tests/functional/notification_sample_tests/test_instance.py
14:38:45 mriedem Kevin_Zheng: left a comment / suggestion about possibly cleaning up the copy/paste in ^
14:39:47 mriedem seems you have a bug in the functional tests http://logs.openstack.org/88/553288/4/check/nova-tox-functional/6049993/testr_results.html.gz
14:40:28 Kevin_Zheng actually I only changed test_create_server_error thistest
14:40:33 Kevin_Zheng for testing
14:40:46 Kevin_Zheng you can check the result for this one
14:41:02 Kevin_Zheng the req_id didn't match
14:41:11 Kevin_Zheng which I did replaced
14:43:06 mriedem is an admin context getting generated somewhere?
14:43:22 mriedem context.get_admin_context() will return a unique request id
14:44:51 Kevin_Zheng I will check
14:47:05 openstackgerrit Merged openstack/nova master: trivialfix: cleanup _pack_instance_onto_cores() https://review.openstack.org/538698
14:47:39 openstackgerrit Merged openstack/nova master: Handle EndpointNotFound when building image_ref_url in notifications https://review.openstack.org/554703
14:47:52 openstackgerrit Merged openstack/nova stable/queens: Only attempt a rebuild claim for an evacuation to a new host https://review.openstack.org/550545
14:48:12 openstackgerrit Merged openstack/nova stable/queens: Unmap compute nodes when deleting host mappings in delete cell operation https://review.openstack.org/553496
14:48:42 jaypipes bauzas: cfriesen is in EST timezone I think?
14:48:47 openstackgerrit Merged openstack/nova stable/pike: Detach volumes when VM creation fails https://review.openstack.org/544143
14:49:00 bauzas jaypipes: living in Alberta IIRC
14:49:16 jaypipes ah.. I thought it was Ottawa
14:53:56 mriedem dansmith: thoughts on a better name for this thing in tssurya's disabled cells series? https://review.openstack.org/#/c/550188/12/nova/objects/cell_mapping.py@165
14:54:02 Kevin_Zheng mriedem thanks for the comment and advise, I will have to check the details tomorrow, it is late here :)
14:54:11 mriedem Kevin_Zheng: np, ttyl
14:54:27 mriedem tssurya: also, i wonder if it would be better if the 'disabled' param doesn't have a default
14:54:48 mriedem since 'enabled_or_disabled' is further confused by the fact it has a default behavior
14:55:02 tssurya yea I was waiting for inputs regarding the name for that function
14:55:34 openstackgerrit Silvan Kaiser proposed openstack/nova master: Exec systemd-run with privileges in Quobyte driver https://review.openstack.org/554195
14:55:42 dansmith mriedem: commented
14:56:25 mriedem i'm cool with get_by_disabled, but don't default the 'disabled' param?
14:56:32 mriedem so caller has to know what they are asking for
14:56:41 dansmith yep
14:57:08 mriedem ok wfm
14:57:12 tssurya wiat, so get_by_disabled() will give enabled by default right ?
14:57:16 mriedem no
14:57:18 mriedem no default
14:57:21 mriedem no kwarg
14:57:22 stephenfin Is there another stable core that could take a look at this, please? https://review.openstack.org/#/c/550079/
14:57:29 tssurya ah so the user has to pass a value
14:57:34 mriedem stephenfin: i can
14:57:37 mriedem tssurya: yeah

Earlier   Later