Earlier  
Posted Nick Remark
#openstack-nova - 2017-03-08
22:02:46 jaypipes rfolco: https://review.openstack.org/#/c/416669/ ready for rebasing.
22:02:52 mriedem like, i already noticed some issues in the searchlight docs just reading it
22:02:59 mriedem and pushed fixes
22:03:42 rfolco jaypipes, I just saw. Would work on that firt hour tomorrow morning. Thanks for your help on that.
22:04:04 rfolco jaypipes, need a microversion bump also
22:04:05 jaypipes rfolco: np. I'll look for it and review tomorrow. should be able to merge that pretty quickly.
22:04:10 jaypipes rfolco: yup.
22:04:55 macsz mriedem: ok, I will try to push this further, will keep you posted on the progress and if anything pops up
22:05:02 mriedem macsz: awesome, thank you
22:05:52 rfolco jaypipes, and I would bother you for keeping active on some upstream work too, if any pointer on where you need some help, let me know pls.
22:06:29 jaypipes rfolco: what's your level of tolerance for NUMA? :)
22:06:58 macsz mriedem: np :)
22:07:06 rfolco jaypipes, very very interested. I found some bugs on ppc testing numa :)
22:08:29 rfolco jaypipes, like this one https://review.openstack.org/#/c/340599/
22:08:31 jaypipes rfolco: k. read this spec and thoroughly understand the concepts in it: https://review.openstack.org/#/c/284094/10/specs/ocata/approved/libvirt-emulator-threads-policy.rst. Then come help sfinucan and I on the review series here: https://review.openstack.org/#/c/400875/. While reviewing, consider how such resources might be represented in the new placement API (once nested resource providers are mergerd)
22:08:55 dansmith jaypipes: I threw up a bit in my mouth just *reading* that
22:09:00 jaypipes dansmith: yup.
22:09:10 jaypipes NUMA and I have a love-hate relationship.
22:09:26 dansmith like it loves you and you hate it?
22:10:06 jaypipes heh
22:10:32 mriedem jaypipes: you forgot to tell him to understand wtf nested resource providers are
22:11:25 jaypipes mriedem: tru enough. rfolco we can discuss tomorrow what nested resource providers are :) but in case you're interested in some "light" reading. https://review.openstack.org/#/c/386710/1/specs/ocata/approved/nested-resource-providers.rst
22:14:49 rfolco jaypipes, cool. Thanks!
22:15:09 jaypipes rfolco: don't thank me until you read those ;P
22:16:52 edleafe rfolco: you can't hide :)
22:19:29 rfolco edleafe, :-/
22:25:34 mriedem pcidevice.address is a mac?
22:25:36 mriedem jaypipes: ^?
22:25:56 dansmith mriedem: no it's a pci address I think, like 1.34
22:26:00 mriedem oh
22:26:03 dansmith or 0:1.34 or something like that
22:26:16 mriedem ok, was wondering why we needed the compute node id to uniquely identify a pcidevice by address
22:26:17 mriedem in pci_device_get_by_addr
22:26:38 openstackgerrit Dan Smith proposed openstack/nova master: Change MQ targeting to honor only what is in the context https://review.openstack.org/438023
22:26:38 openstackgerrit Dan Smith proposed openstack/nova master: Teach os-migrations about cells https://review.openstack.org/442685
22:26:39 openstackgerrit Dan Smith proposed openstack/nova master: Add cell field to Destination object https://review.openstack.org/438024
22:26:39 openstackgerrit Dan Smith proposed openstack/nova master: Teach simple_tenant_usage about cells https://review.openstack.org/441388
22:26:40 openstackgerrit Dan Smith proposed openstack/nova master: Teach os-aggregates about cells https://review.openstack.org/442200
22:26:40 openstackgerrit Dan Smith proposed openstack/nova master: Refactor cell loading in compute/api https://review.openstack.org/443337
22:26:44 mriedem if we don't want to expose the pcidevice.id in the rest api, and get them by that id, and we don't have a uuid, we need something else
22:27:16 mriedem unless we add a uuid to the pcidevices table/object
22:27:31 dansmith *shudder*
22:27:45 mriedem yeah the only unique constraints are the id (primary key) and node_id/address
22:27:52 mriedem so, we'd have to add a uuid
22:28:14 mriedem heh, or we just deprecate that dumbass api and say you can't use it with multiple cells :)
22:28:22 dansmith heh
22:28:31 mriedem i feel like that was a half-baked api
22:28:42 dansmith s/api//
22:29:06 mriedem and if you want to know what pci devices are on a given compute node, you get them via the compute node resource provider
22:29:12 mriedem traits on the resource provider
22:29:23 mriedem jaypipes: will pcidevices be a trait on a compute node resource provider?
22:29:34 mriedem will/can
22:31:56 jaypipes mriedem: depends on what kind of PCI device.
22:32:06 mriedem dansmith: shart, services table doesn't have uuid either
22:32:57 jaypipes mriedem: SRIOV physical functions will be either child providers of a compute node *or* child providers of a NUMA socket resource provider, depending on whether the SRIOV NIC is affined to a particular NUMA socket.
22:33:29 efried mikal - Any chance we can start getting some reviews on change sets under https://review.openstack.org/#/q/topic:bp/powervm-nova-compute-driver ? The ones with +1s from nova-powervm cores (e.g. thorst adreznec esberglu) are ready for your look. Conveniently numbered, too ;-)
22:33:48 jaypipes mriedem: but pcidevices will definitely not be a "trait". Rather, things like the physical network tag would be a trait on the SRIOV physical function resource provider.
22:33:59 mriedem jaypipes: ack
22:34:24 mriedem i was looking for a way to weasle out of the compute rest api needing to show pcidevice per node information
22:34:54 openstackgerrit Sarafraj Singh proposed openstack/nova-specs master: WIP: Replace live migration steps and delays with memory iteration logic https://review.openstack.org/443339
22:34:57 mriedem it's all information in os-pci, like all pcidevices on a node, and all pcidevices for a server
22:35:08 mriedem *informational
22:35:11 jaypipes mriedem: right.
22:35:24 mriedem and if i could say, get that information elsewhere...
22:35:26 mriedem my life would be easier
22:35:54 mriedem seems to fall into the 'nova does not want to be a metrics gatherer' anymore stadium
22:36:02 jaypipes mriedem: eventually the placement API will be able to represent the tree of providers on a compute node, yes. But things like PCI address information will not be in the placement API.
22:36:14 mriedem sure
22:36:24 mriedem ok, well i'll just spec this up with the way things are today then
22:36:33 jaypipes kk
22:36:45 jaypipes mriedem: I'm still yet to get to that spec though...
22:36:53 jaypipes the pcidevices one you linked to earlier.
22:36:56 jaypipes have it on the list.
22:37:11 jaypipes currently working on a review of moshele's SRIOV port pair allocation one.
22:37:18 jaypipes https://review.openstack.org/#/c/182242/33/specs/pike/approved/user-controlled-sriov-ports-allocation.rst
22:37:30 mriedem jaypipes: yeah this is different actually
22:37:33 mriedem related to cells v2
22:37:37 mriedem shenanigans
22:37:37 jaypipes ah, ok.
22:37:39 jaypipes sorry
22:37:42 mriedem don't be
22:38:01 mriedem i just use you as my encyclopedia of nova horrors
22:44:38 openstackgerrit Sujitha proposed openstack/nova master: Reduce calls to load_tags() to 0 https://review.openstack.org/435146
22:47:08 mriedem jaypipes: dansmith: i'm going to head home, but wrote up the abstract for the spec i'm going to work on later https://blueprints.launchpad.net/nova/+spec/service-hyper-pci-uuid-in-api
22:47:15 mriedem let me know if i screwed anything up in there
22:47:22 jaypipes mriedem: will do. thx.
22:53:04 openstackgerrit Dan Peschman proposed openstack/nova master: No API cell up-call to delete consoleauth tokens https://review.openstack.org/415922
22:53:35 openstackgerrit Eric Fried proposed openstack/nova master: WIP: PowerVM Driver: SSP emphemeral disk support https://review.openstack.org/443189
22:54:07 openstackgerrit Eric Fried proposed openstack/nova master: WIP: PowerVM Driver: SSP emphemeral disk support https://review.openstack.org/443189
23:13:41 openstackgerrit Eric Fried proposed openstack/nova master: WIP: PowerVM Driver: SSP emphemeral disk support https://review.openstack.org/443189
23:28:32 openstackgerrit OpenStack Proposal Bot proposed openstack/nova master: Updated from global requirements https://review.openstack.org/443357
23:33:07 openstackgerrit Jay Pipes proposed openstack/nova master: virt: implement get_inventory() for Ironic https://review.openstack.org/441544
23:33:12 jaypipes dansmith: ^^
23:34:56 dansmith jaypipes: done thanks
23:35:03 jaypipes dansmith: danke
#openstack-nova - 2017-03-09
00:03:09 alex_xu mriedem: will check that patch in the morning
00:03:47 alex_xu jaypipes: something looking for your feedback https://review.openstack.org/441829, cdent didn't want the cache :)
00:04:23 jaypipes alex_xu: yeah, it's next on my list. currently reviewing https://review.openstack.org/#/c/435954/6/specs/pike/approved/enable-sriov-nic-features.rst
00:05:00 alex_xu jaypipes: thanks :)
00:09:59 dansmith what kind of monster doesn't want a cache?

Earlier   Later