| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-10-24 | |||
| 15:58:37 | bauzas | anyway | |
| 15:58:38 | efried | bauzas And you'll have to use numbered syntax to specify them. | |
| 15:58:44 | stephenfin | But I should run that by AJaeger or dhellmann first | |
| 15:58:46 | mriedem | stephenfin: ah you're right https://docs.openstack.org/queens/user/ | |
| 15:58:46 | efried | s/specify/request/ | |
| 15:59:16 | mriedem | stephenfin: yeah ok so i'll backport the user/index in-tree page before https://review.openstack.org/514723 when i do the backports | |
| 15:59:22 | stephenfin | (y) | |
| 16:00:02 | stephenfin | mriedem: I do realize I said I'd do that doc and the other ones too. I'll get them done soon as the summit is behind us | |
| 16:01:53 | efried | bauzas e.g. ?resources1=VGPU:1&required1=VGPU_TYPE_GRID_M10_0B&resources2=VGPU_1&required2=VGPU_TYPE_GRID_M10_8Q | |
| 16:05:51 | edleafe | I will take that ^^ as an opportunity to reiterate my request for multiple 'request=' qs params | |
| 16:07:02 | mriedem | stephenfin: why doesn't user/index include the links to the API stuff we have in the main index? | |
| 16:07:09 | mriedem | shouldn't a user guide care about end users of the API? | |
| 16:07:22 | efried | edleafe We still need the so-called "unnumbered" group. | |
| 16:07:31 | mriedem | stephenfin: looks like user/index is more for operators | |
| 16:08:20 | jmccarthy | Hmm are permissions like this ok for the console.log ? root qemu 0 Oct 24 15:46 console.log (nothing logged) | |
| 16:08:35 | stephenfin | mriedem: To be honest, I'm still confused by the divide between 'user' and 'admin'. The lines are blurred | |
| 16:08:54 | stephenfin | I think the API is documented in the developer section, whatever that's called | |
| 16:09:02 | sdague | stephenfin: user == "only have access to the API, not the physical machines" | |
| 16:09:13 | sdague | admin == "people with access to the machines" | |
| 16:09:20 | efried | edleafe Hm, I guess you could get away with not doing that if we changed the semantic for resources= to always be "same RP"; then you would have to split up all of your resource requests that you didn't need to be in the same RP. | |
| 16:09:23 | mriedem | sdague: then the content here is wrong https://docs.openstack.org/nova/latest/user/ | |
| 16:09:34 | sdague | mriedem: yes, it is | |
| 16:10:05 | stephenfin | mriedem, sdague: I think this is where my confusion stems from https://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html | |
| 16:10:12 | sdague | but things were stuck merging, and we were going to have nothing, so we ran it through | |
| 16:10:17 | stephenfin | "end-user content such as concept guides, advice, tutorials, step-by-step instructions for using the CLI to perform specific tasks, etc." | |
| 16:10:25 | stephenfin | the concept-guides bit | |
| 16:10:42 | stephenfin | anything that was clear "do this to achieve that" was shoved into 'user' | |
| 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 | |