| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2018-09-06 | |||
| 16:51:30 | melwitt | (I just commented on the review but now see it's being discussed still here) | |
| 16:51:48 | stephenfin | melwitt: We don't want/need to do that. It's a feature. The bug is in the documentation, IMO | |
| 16:51:51 | efried | melwitt: or as stephenfin put it, fixing it to take a list would be a "feature". | |
| 16:52:26 | melwitt | oh, okay. stephenfin definitely knows more than me about the intention when it was created, so if a list was not meant to work, then I agree, doc bug | |
| 16:52:57 | melwitt | I had thought because of the examples in the config help, it was supposed to work as a list | |
| 16:53:04 | stephenfin | `MultiStrOpt`s are meant to be defined multiple times in a nova.conf. No reason to support defining it multiple ways. More JSON is the last thing anyone needs | |
| 16:53:21 | stephenfin | melwitt: Clearly so did whoever wrote the docs (probably me, tbf) :) It's wrong though | |
| 16:53:37 | melwitt | I see | |
| 16:54:31 | stephenfin | ouch | |
| 16:55:28 | stephenfin | efried: Personally, I'd stick in a comment saying "this means the option is undefined" and leave it at that. There are bigger battles to be fought | |
| 16:55:38 | stephenfin | I'll see if I can clear up the oslo.config docs post-PTG | |
| 16:56:03 | efried | yup, agreed; just want to be encouraging here :) | |
| 16:56:59 | stephenfin | and with that I take my leave. See y'all in Denver o/ | |
| 17:24:01 | cfriesen | do we have any idea when the stein spec freeze would end up? | |
| 17:26:54 | cfriesen | never mind, found it | |
| 17:28:18 | melwitt | cfriesen: I think we're going to discuss that as part of the rocky retro, but I expect it'll be at s-1 | |
| 17:30:13 | melwitt | last time we made it later (2nd milestone) because of runways, but we're going to reassess now that we know how runways went last time http://lists.openstack.org/pipermail/openstack-dev/2018-August/133757.html | |
| 17:42:27 | mriedem | nicolasbock: did you get an answer? | |
| 17:45:18 | mriedem | nicolasbock: if you have an evacuated instance with allocations against multiple resource providers (compute nodes) in placement, and one is against the old source host you evacuated *from*, you should be able to cleanup those bogus allocations using the OSC placement CLI | |
| 17:45:35 | mriedem | https://docs.openstack.org/osc-placement/latest/cli/index.html#resource-provider-allocation-show | |
| 17:59:00 | mriedem | jaypipes: super fun questions about metadata api and config drive in https://review.openstack.org/#/c/599598/ | |
| 18:29:03 | nicolasbock | mriedem, Ah thanks! | |
| 18:30:19 | mriedem | nicolasbock: w/o knowing your full situation, that's my first guess - let me know if that doesn't align with what you're dealing with | |
| 18:30:54 | nicolasbock | mriedem, Thanks. Is there a command line client for placement? | |
| 18:31:04 | nicolasbock | Or is that done directly through the API via curl? | |
| 18:31:23 | mriedem | that's the osc-placement plugin | |
| 18:31:26 | mriedem | in the docs i linked | |
| 18:31:37 | mriedem | https://docs.openstack.org/osc-placement/latest/ | |
| 18:31:54 | mriedem | https://pypi.org/project/osc-placement/ | |
| 18:32:52 | nicolasbock | Thanks! | |
| 19:02:47 | mriedem | so grenade hasn't been working in stein yet just fyi https://review.openstack.org/#/c/591594/ | |
| 19:03:04 | mriedem | good news is you can skip level from queens to stein! | |
| 19:03:10 | mriedem | FFU MISSION ACCOMPLISHED! | |
| 19:03:20 | jroll | congrats | |
| 19:15:53 | mriedem | mnaser: you've been summoned to https://review.openstack.org/#/c/600157/ | |
| 19:16:03 | mriedem | discussion about how extracted placement is going to deal with config | |
| 19:16:21 | mnaser | hi | |
| 19:16:29 | mriedem | right now, as written, deployers would need to copy/rename nova.conf to placement.conf *or* write a fresh placement.conf with the needed stuff that was in nova.conf before | |
| 19:16:43 | mriedem | there is no "if nova.conf: use it; else placement.conf" | |
| 19:17:00 | mriedem | we'll likely be doing the latter in grenade | |
| 19:18:43 | mnaser | well | |
| 19:18:49 | mnaser | we've always deprecated things | |
| 19:19:14 | mnaser | so i don't see why this would be any different | |
| 19:19:33 | mnaser | if anything this is way more critical than any other config disappearing | |
| 19:21:16 | mriedem | you mean as in deprecated but still rely on nova.conf in extracted placement, and drop support for placement using nova.conf in T? | |
| 19:22:00 | mnaser | mriedem: load in order of /etc/placement.conf => /etc/nova/nova.conf in S with a giant warning | |
| 19:22:01 | mnaser | drop that in T | |
| 19:22:33 | mriedem | i believe that's what jaypipes asked for on the review | |
| 19:23:36 | jaypipes | correct. | |
| 19:24:13 | mnaser | i really hope to try and loop in other deployment tools into this | |
| 19:24:15 | mnaser | i.e. tripleo | |
| 19:24:35 | mriedem | beyond config, the other major thing is obviously the db | |
| 19:25:08 | mriedem | if placement does use nova.conf in stein (use/supports as a bridge), it would rely on the [api_database]/connection config | |
| 19:25:57 | mnaser | yeah and also | |
| 19:26:00 | mriedem | looks like that code is still there | |
| 19:26:01 | mnaser | wasnt placement_database a thing | |
| 19:26:07 | mnaser | but i think that was removed cause it wasn't wired | |
| 19:26:09 | mriedem | in openstack/placement, to support that | |
| 19:26:11 | mnaser | i cant remember if it was fixed | |
| 19:26:22 | mriedem | CONF.placement_database is a thing in rocky | |
| 19:26:29 | mriedem | optional thing | |
| 19:26:31 | mnaser | ok so that's back | |
| 19:26:37 | mriedem | yes | |
| 19:26:42 | mnaser | so the logic to determine the db source would be useful there | |
| 19:26:48 | mriedem | if not set, it still uses the nova_api db | |
| 19:27:05 | mnaser | i remember some deployment tools actually creating a placement db | |
| 19:27:08 | mnaser | and pointing that stuff to it | |
| 19:27:10 | mriedem | https://github.com/openstack/placement/blob/master/placement/db_api.py#L27 | |
| 19:27:24 | mriedem | yeah i think i remember that, maybe kolla? | |
| 19:27:44 | mriedem | i do remember it triggering that we needed to remove some shit from the nova config that was missed when that was originally reverted | |
| 19:28:52 | mnaser | mriedem: i added a comment with my pov | |
| 19:31:59 | jaypipes | mriedem: again, my primary concern is the use of default values if /etc/placement.conf doesn't exist and how that would be quite difficult to diagnose if there were changed values in the /etc/nova.conf for placement-related stuffs. | |
| 19:32:50 | mnaser | yeah i can imagine that being so confusing | |
| 19:33:55 | mriedem | there's not actually a ton of configuration options for placement, mostly policy, db, and some other small things, | |
| 19:34:06 | mriedem | but yeah if your db is pointing at the wrong thing, i.e. nothing, you're f'ed | |
| 20:18:54 | efried | edmondsw: You'll be interested in this discussion from the nova mtg this morning: http://eavesdrop.openstack.org/meetings/nova/2018/nova.2018-09-06-14.00.log.html#l-120 | |
| 20:20:09 | efried | edmondsw: TL;DR: we should proceed as if cyborg ain't a thing, and worry about integrating with cyborg later as it matures. | |
| 20:20:41 | efried | edmondsw: Which means pretty much sticking with the direction of the spec(s) as written. | |
| 20:20:50 | efried | which is good timeline-wise :) | |
| 20:21:08 | edmondsw | that sounds good to me, assuming we'll be able to squeeze cyborg in when the time comes without reinventing too much | |
| 20:21:19 | edmondsw | s/assuming/hoping/ ? | |
| 20:21:53 | efried | yeah, that was my concern, but it's between that rock and the hard place of trying to anticipate $world-with-cyborg before that's a thing. | |
| 20:22:07 | edmondsw | yep | |
| 20:22:20 | edmondsw | I see many interesting PTG conversations in your future... | |
| 20:22:43 | edmondsw | wish I could be there | |
| 21:01:01 | gryf | +++++++++++++++++ | |
| 21:32:59 | mnaser | fun fact | |
| 21:33:02 | mnaser | console logs disappear on live migration | |
| 21:33:19 | mnaser | themoreyouknow.gif | |
| 21:47:37 | mriedem | you're welcome | |
| 21:53:59 | mriedem | so i thought artom changed direction on numa-aware live migration https://review.openstack.org/#/c/599587/ ? | |
| 21:54:04 | mriedem | because the re-proposed spec is the same old thing | |
| 21:54:21 | mriedem | stephenfin: ^ | |
| 21:54:31 | mriedem | btw, GET /artom is a 404 | |
| 21:54:33 | mriedem | wtf? | |
| 22:05:09 | openstackgerrit | Merged openstack/nova-specs master: Add serial numbers for local disks https://review.openstack.org/595247 | |
| #openstack-nova - 2018-09-07 | |||
| 00:32:25 | alex_xu | good morning nova | |
| 01:07:04 | openstackgerrit | Elancheran S proposed openstack/nova stable/pike: Add apply_cells to nova-manage https://review.openstack.org/599050 | |
| 01:18:24 | openstackgerrit | fupingxie proposed openstack/nova master: Add an example to add more pci devices in nova.conf https://review.openstack.org/592243 | |
| 02:08:16 | openstackgerrit | Zhenyu Zheng proposed openstack/nova-specs master: Add live-migration-force-after-timeout-stein spec https://review.openstack.org/600608 | |