Earlier  
Posted Nick Remark
#openstack-nova - 2017-09-08
14:06:16 johnthetubaguy eek
14:06:23 gibi bauwser: thanks!
14:06:47 bauwser mriedem: you already pointed that out in a ML thread, right?
14:06:49 bauwser no answer yet ?
14:06:56 bauwser (AFAICR)
14:07:40 mriedem bauwser: yes, and sdague started something to define an in-scope search vs a global search
14:07:49 mriedem in-scope meaning, within *these* docs
14:07:49 bauwser k
14:07:51 mriedem like the nova docs
14:07:54 johnthetubaguy boolman: I think you want #openstack, but look at https://developer.openstack.org/api-ref/compute/#create-server and "block_device_mapping_v2.destination_type" basically we only create volumes when requested directly, AFAIK
14:07:59 bauwser yeah, looks a good idea :)
14:08:18 sdague mriedem: that was merged, I don't know if it was released yet
14:09:10 boolman johnthetubaguy: ye sry, I read #topic after I posted.
14:09:21 johnthetubaguy boolman: no worries
14:10:10 openstackgerrit Merged openstack/nova master: Set regex flag on ostestr command for osprofiler tests https://review.openstack.org/501842
14:13:58 mriedem there are two things wrong with the note at the top of this page https://docs.openstack.org/nova/latest/admin/flavors.html
14:14:09 mriedem 1. wrong policy rule now
14:14:16 mriedem 2. the horizon thing was changed in pike i think
14:14:55 mriedem robcresswell: ^ for "The Dashboard simulates the ability to modify a flavor by deleting an existing flavor and creating a new one with the same name." what exactly does horizon do now? just warn you? or does it not allow you to 'edit' a flavor that is tied to an instance?
14:15:13 mriedem ah https://docs.openstack.org/releasenotes/horizon/pike.html#upgrade-notes
14:15:17 johnthetubaguy mriedem: wow, there is a lot more documented there than I expected to see
14:15:19 mriedem "The ability to edit flavors is disabled by default. See ENABLE_FLAVOR_EDIT in the settings documentation for more information."
14:17:27 stephenfin mriedem: Seeing as you're looking at that file, want to review https://review.openstack.org/#/c/501342/2
14:17:38 sdague TheJulia / dtantsur: this working as designed - https://bugs.launchpad.net/nova/+bug/1715646 - or a real bug
14:17:39 openstack Launchpad bug 1715646 in OpenStack Compute (nova) "Compute host for ironic is not mapped to a cell if no ironic node is created" [Undecided,New]
14:17:43 stephenfin This is the first step. I'm happy to clean that item above as a follow up
14:18:15 dtantsur sdague: it's a bug, and I thought dansmith fixed it some time ago..
14:18:34 stephenfin johnthetubaguy: Unfortunately a lot of it is wrong :( especially the stuff around extra_specs
14:18:49 johnthetubaguy stephenfin: joys
14:19:12 stephenfin I've trying to clean both that, and the specs I'm having to review for background info, this week
14:19:14 sdague dtantsur: you able to ask enough questions on that bug to figure out what is going on?
14:19:15 dansmith dtantsur: sdague: It's working as designed, we can't put compute node records in without anything reported from ironic.. that's a fundamental thing
14:19:18 stephenfin Extra specs suuuuuuuck
14:19:24 sdague dansmith: ok
14:19:37 dtantsur dansmith: except that it creates a horrible user experience
14:19:55 dansmith sdague: we write 1:1 ironic node reported from ironic into the compute nodes table.. if zero are reported (or we can't do the list) then we have nothing to write
14:20:26 dansmith sdague: there is a periodic task you can enable on scheduler that will run discovery every once in a while, which is a workaround
14:20:40 dansmith dtantsur: I dunno what to say.. I can't report things I don't know are there
14:20:44 sdague dansmith: ok, cool, I'll close as working as designed
14:20:48 dtantsur then we have to document this periodic task a mandatory for ironic..
14:20:51 dtantsur s/a/as/
14:22:57 dtantsur dansmith: https://github.com/openstack/nova/commit/62878ef5a6c9f6a2c727c91397830387425c4d37
14:23:25 dtantsur isn't it fixing precisely that?
14:24:22 dtantsur hmm, maybe not actually
14:24:30 openstackgerrit Elod Illes proposed openstack/nova master: Transform aggregate.remove_host notification https://review.openstack.org/396211
14:25:47 dtantsur dansmith: this means that we should either document running nova-manage after adding every ironic node/bulk of nodes or document using this periodic task, right?
14:25:56 mriedem stephenfin: "What flavors are why they are used."?
14:27:07 stephenfin *and
14:27:07 stephenfin damn
14:27:22 stephenfin *What are flavors and why are they used
14:28:10 openstackgerrit Merged openstack/nova master: Typo error about help resource_classes.inc https://review.openstack.org/501930
14:29:43 mriedem inspur is going on a spell check tear i've noticed recently
14:29:43 mriedem ^
14:29:51 mriedem that's the 2nd patch i've seen from the same company for the same typo
14:30:01 openstackgerrit Stephen Finucane proposed openstack/nova master: doc: Split flavors docs into admin and user guides https://review.openstack.org/501342
14:31:21 mriedem who wants to get these other two stable/pike high severity fixes? https://review.openstack.org/#/q/topic:bug/1715462+branch:stable/pike
14:31:46 sdague looking
14:32:23 sdague mriedem: +2 on both of those
14:32:28 mriedem thanks
14:32:55 mriedem gibi: i think https://review.openstack.org/#/c/500521/ might be better in some kind of 'limitations' doc
14:33:18 mriedem gibi: the ironic and fgpa thing was noted in the spec as an example, but so was shared IP allocation pools in the original resource providers spec back in i think mitaka
14:33:30 mriedem those are just examples, not declarations of what we support today
14:34:24 gibi mriedem: but we don't have limitation doc I assume
14:35:32 mriedem gibi: no, but that's easy to change
14:35:33 gibi mriedem: but I understand that release notes are not the good place either
14:35:40 mriedem gibi: i left some comments in the patch with more detailed thoughts
14:35:56 mriedem i think we could fit something in here https://docs.openstack.org/nova/latest/user/placement.html
14:36:24 mriedem we have overview, deployment, upgrade notes (per release), and REST API microversion history, we could also have a Limitations section
14:36:51 gibi mriedem: I like this idea
14:36:57 mriedem i like that you like this idea
14:37:34 gibi mriedem: I will try type up a patch during my flight tomorrow
14:38:01 mriedem cool, thanks
14:38:36 gibi thanks for the feedback
14:40:39 gibi mriedem: also thanks for the ML reply on my notification question, elod will start working on adding the new interface_attach notification next week
14:43:04 mriedem \o/
14:44:05 gibi I'm logging off for the weekend. See you in Denver
14:44:10 mriedem have a good one
14:44:16 gibi thanks
14:58:55 openstackgerrit Lee Yarwood proposed openstack/nova stable/pike: Move hash ring initialization to init_host() for ironic https://review.openstack.org/502082
15:03:54 openstackgerrit Stephen Finucane proposed openstack/nova master: Fix AZ related API docs https://review.openstack.org/456655
15:11:22 sdague stephenfin: I think you dropped a word - https://review.openstack.org/#/c/456655
15:11:30 sdague after that, +2
15:12:16 openstackgerrit Stephen Finucane proposed openstack/nova master: Fix AZ related API docs https://review.openstack.org/456655
15:12:31 stephenfin sdague: Second time I've done that today :( Done
15:12:46 sdague +2
15:12:49 stephenfin ta
15:16:44 mriedem stephenfin: couple nits inline there
15:17:17 mriedem "Typically, you use availability zones to arrange OpenStack compute hosts into logical groups."
15:17:27 mriedem you (the end user?) doesn't actually arrange the compute hosts
15:17:31 mriedem the admin does that with host aggregates
15:17:50 mriedem and labels them with AZs that the end user (non-admin) can then use for isolation
15:18:07 mriedem but maybe i'm splitting hairs
15:22:25 openstackgerrit Stephen Finucane proposed openstack/nova master: Fix AZ related API docs https://review.openstack.org/456655
15:22:45 stephenfin mriedem: I agree, and I think I've addressed it
15:27:04 mriedem cool, +2
15:28:00 mikal sdague: can I get a +W on https://review.openstack.org/#/c/472229/ please? It has two +2's but the +W fell off when we went around a corner too fast.
15:31:40 sdague mikal: done
15:31:47 mikal Ta
15:32:18 sdague mikal: so, is there actually a privsep discussion area somewhere carved out yet for PTG?
15:36:12 mriedem it's in the etherpad

Earlier   Later