Earlier  
Posted Nick Remark
#openstack-nova - 2017-10-24
16:10:50 efried edleafe But you *do* need to be able to specify multiple RC:amount+traits in a *single* resources= qparam. How would you do that?
16:11:11 stephenfin Fortunately it's easy to fix, and it was better have something than nothing, as sdague points out
16:11:12 sdague stephenfin: concept guides in that context are the api-guide kind of docs
16:11:18 edleafe efried: why would that be required?
16:11:23 sdague what is a server, what is a flavor
16:11:32 stephenfin Yeah, that makes sense
16:11:50 mriedem which is this thing https://developer.openstack.org/api-guide/compute/index.html
16:12:07 sdague mriedem: right, but nova is the only project that has that
16:12:18 efried edleafe Because sometimes it's important that two resources come from the exact same RP. E.g. for a VF, I need the VF itself and its corresponding bandwidth to come from the same RP. It's no good if you allocate me the VF from one PF and the bandwidth from its neighbor.
16:12:45 stephenfin sdague: I wonder if we should eventually move that into 'user/api' or something so?
16:12:56 stephenfin I know we want to keep api-ref separate, but api-guide is different
16:13:07 sdague maybe, the biggest issue is branch vs. branchless docs
16:13:14 stephenfin There's a lot more projects using https://developer.openstack.org/api-ref/
16:14:45 stephenfin Good point
16:15:51 mriedem man, in general we're missinga ton of content from https://github.com/openstack/openstack-manuals/tree/stable/ocata/doc/user-guide/source
16:15:55 stephenfin mriedem: Those indexes and some general shuffling of docs are on my radar for the next few weeks. We should probably track notes like that in a bug or something
16:16:23 openstackgerrit sean mooney proposed openstack/os-traits master: add plathform security namespaces https://review.openstack.org/514712
16:16:23 openstackgerrit sean mooney proposed openstack/os-traits master: add firmware (fw) traits namespace https://review.openstack.org/514713
16:18:09 mriedem stephenfin: ahttps://bugs.launchpad.net/nova/+bug/1726932
16:18:10 openstack Launchpad bug 1726932 in OpenStack Compute (nova) "The nova user guide is more for admins/operators than end users" [Medium,Triaged]
16:18:42 stephenfin Cool. Assigned to myself
16:19:03 openstackgerrit sean mooney proposed openstack/os-traits master: add fw common namespace https://review.openstack.org/514737
16:20:54 openstackgerrit Matt Riedemann proposed openstack/nova master: Import the config drive docs from openstack-manuals https://review.openstack.org/514723
16:20:54 openstackgerrit Matt Riedemann proposed openstack/nova master: Import user-data page from openstack-manuals https://review.openstack.org/514738
16:24:20 openstackgerrit Dan Smith proposed openstack/nova master: Make migration uuid hold allocations for migrating instances https://review.openstack.org/506420
16:24:21 openstackgerrit Dan Smith proposed openstack/nova master: Make live migration hold resources with a migration allocation https://review.openstack.org/507638
16:24:30 dansmith mriedem: would like to close this out before too long ^
16:26:09 mriedem yeah it's in the starred list
16:27:57 openstackgerrit Matt Riedemann proposed openstack/nova master: Import the config drive docs from openstack-manuals https://review.openstack.org/514723
16:27:58 openstackgerrit Matt Riedemann proposed openstack/nova master: Import user-data page from openstack-manuals https://review.openstack.org/514738
16:37:01 openstackgerrit Elod Illes proposed openstack/nova master: WIP: Transform scheduler.select_destinations notification https://review.openstack.org/508506
16:39:48 mriedem stephenfin: well 2 down, 14 to go :) https://bugs.launchpad.net/nova/+bug/1714017/comments/9
16:39:50 openstack Launchpad bug 1714017 in OpenStack Compute (nova) "User guide was not migrated to the nova repo" [Medium,In progress] - Assigned to Matt Riedemann (mriedem)
16:40:30 mgagne mriedem: yes (re cellv1)
16:41:00 mgagne mriedem: running mainly kilo and very soon mitaka
16:43:37 sdague stephenfin: well, I honestly don't think the on disk structure matters, it's the organizing portals
16:44:38 stephenfin It doesn't, but we shouldn't have content targeted at admins in the user guide (and vice versa, tbh). The folders help with that separation
16:46:15 mriedem btw, this isn't confusing at all https://github.com/openstack/openstack-manuals/blob/stable/ocata/doc/user-guide/source/configure-access-and-security-for-instances.rst vs https://github.com/openstack/openstack-manuals/blob/stable/ocata/doc/user-guide/source/cli-nova-configure-access-security-for-instances.rst
16:48:53 openstackgerrit Merged openstack/nova master: [placement] Confirm that empty resources query causes 400 https://review.openstack.org/511488
16:48:58 openstackgerrit Merged openstack/nova master: [placement] add coverage for update of standard resource class https://review.openstack.org/511485
16:49:44 mvpnitesh hi all , i'm trying to migrate the instance in multi node setup, after i run the command to migrate it is in migrating state for some time and later the migration is getting cancelled as the migration timeout has happened
16:56:11 openstackgerrit Sylvain Bauza proposed openstack/nova master: WIP: libvirt: Provide VGPU inventory for a single GPU type https://review.openstack.org/514763
16:56:32 bauzas efried: dansmith: edleafe: first attempt ^
16:57:33 efried bauzas Regardant...
16:57:36 dansmith omg -1 no tests!
16:57:46 bauzas yeah, of course
16:57:56 bauzas I'll show the UTs soon
16:59:11 openstackgerrit Merged openstack/nova master: Update libvirt volume drivers to use os-brick constants https://review.openstack.org/510311
16:59:38 dansmith bauzas: <3 L5833 of driver.py :)
17:00:41 bauzas heh, I branched mdevs from the existing PCI resources, even if libvirt config XML provides them in a PCI tree
17:03:13 efried bauzas This seems reasonable
17:03:57 efried bauzas Once virt has more control over its RPs (e.g. can add own traits) this will get more interesting.
17:22:58 openstackgerrit Dan Smith proposed openstack/nova master: Make live migration hold resources with a migration allocation https://review.openstack.org/507638
17:24:35 dansmith stephenfin: did these answer your non-blocking questions enough to earn a +W? https://review.openstack.org/#/c/508595/8
17:26:07 openstackgerrit priyaduggirala proposed openstack/nova master: Rename parameters in call() of nova/image/glance.py https://review.openstack.org/508533
17:28:05 openstackgerrit Sylvain Bauza proposed openstack/nova master: WIP: libvirt: Provide VGPU inventory for a single GPU type https://review.openstack.org/514763
17:30:08 dansmith bauzas: do you have any prototype code to actually allocate a gpu device during spawn?
17:30:19 dansmith er, allocate is a loaded term.. "configure" maybe
17:30:22 bauzas dansmith: not yet, tomorrow
17:30:26 dansmith okay
17:30:38 bauzas I mostly see the direction tho
17:30:43 dansmith cool
17:30:59 bauzas once we ask for a specific GPU in the flavor, that goes to the compute
17:31:11 bauzas then in libvirt, I'll lookup the flavor and find the extra spec
17:31:31 dansmith well, in libvirt you get the allocation now
17:31:32 bauzas once that, I'll call out the system to create a mdev if I can't find it
17:31:43 bauzas oh, good to know
17:31:59 dansmith but yeah, same difference
17:32:24 bauzas lemme see where we get those allocations
17:32:32 bauzas my master is quite new
17:32:47 bauzas oh I see
17:32:54 bauzas allocations as a param FTW
17:33:01 bauzas good good
17:33:54 bauzas dansmith: I haven't yet looked but I suspect we call placement to pass the allocation to the virt driver, right?
17:34:01 dansmith yeah
17:34:03 bauzas I mean in the compute service
17:34:06 bauzas okay
17:34:07 dansmith yep
17:34:11 bauzas for that consumer ID ?
17:34:16 dansmith yeah
17:34:21 bauzas all good then
17:34:38 bauzas now I wonder one thing tho
17:34:56 bauzas say we now have the inventory reporting VGPUs
17:35:15 bauzas if the flavor goes asking for that, does placement magically create allocation for that RC ?
17:35:19 bauzas dansmith: ^
17:35:28 bauzas I tend to do so, but I need confirmation
17:35:29 dansmith well,
17:35:35 dansmith placement doesn't create an allocation, no,
17:35:40 bauzas sorry
17:35:42 dansmith but it returns an allocation candidate with that init,
17:35:43 bauzas the claim I mean
17:35:53 dansmith and then scheduler will try to create an allocation from it yeah
17:36:04 dansmith so you should have an allocation for a vgpu when you get to spawn
17:36:12 bauzas *will* means I need to code ?
17:36:24 dansmith no, will means it will happen if it's in the flavor
17:36:31 bauzas oh, snap
17:36:34 bauzas yeah I remember
17:36:48 bauzas hence the scheduler.utils method that gives you the resource classes
17:37:09 bauzas anyway, I have a devstack, I can give it a try
17:39:11 dansmith good progress, thanks!

Earlier   Later