| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-04-21 | |||
| 08:59:23 | bauzas | https://bugzilla.redhat.com/show_bug.cgi?id=1434944 | |
| 08:59:43 | asettle | I always liked the name 'bugzilla' | |
| 08:59:51 | asettle | cdent: okay, thanks, that's a start :) | |
| 09:00:27 | asettle | Ah, this was after I pushed sgordon with a stick | |
| 09:00:34 | bauzas | asettle: indeed :) | |
| 09:00:47 | bauzas | that came back to my ears a week or so ago | |
| 09:00:54 | asettle | Thanks for finding this, bauzas | |
| 09:01:15 | bauzas | so I'd say the problem is on track for RDO, fix needs to go on its way | |
| 09:01:15 | asettle | Okay, looks like Petr is on this. | |
| 09:01:52 | bauzas | asettle: FWIW, Red Hat product-based OpenStack Platform is not impacted because we use TripleO | |
| 09:01:52 | cdent | bauzas: this issue is different: it is making sure that the docs are aligned with the rdo config | |
| 09:02:15 | cdent | the directory thing causes a different issue | |
| 09:02:19 | bauzas | asettle: where Puppet nukes that file and replaces by a correct config | |
| 09:02:26 | asettle | Okay | |
| 09:02:38 | bauzas | cdent: probably, have very few context | |
| 09:02:48 | bauzas | cdent: just saying that RDO .rpms aren't working anyway | |
| 09:02:52 | cdent | here's another semi-related thing the other day that I made: https://bugzilla.redhat.com/show_bug.cgi?id=1441200 | |
| 09:02:53 | openstack | bugzilla.redhat.com bug 1441200 in openstack-nova "openstack-placement-api.conf not configured properly by the openstack-nova-placement-api rpm" [Unspecified,Post] - Assigned to nlevinki | |
| 09:03:13 | openstack | bugzilla.redhat.com bug 1441208 in openstack-nova "placement api apache configuration does not align with documentation, ensure system does not work" [High,Closed: duplicate] - Assigned to nlevinki | |
| 09:03:13 | cdent | sorry, I mean this one: https://bugzilla.redhat.com/show_bug.cgi?id=1441208 | |
| 09:03:49 | bauzas | cdent: BZ1441200 points to the same fix for RDO than 1434944 for resolution | |
| 09:03:55 | cdent | the first one is a duplicate of the one I created, mine has more context | |
| 09:04:17 | cdent | bauzas: I'm providing these so asettle has context, which is what was asked for, not to find the right bug | |
| 09:04:28 | asettle | Yep, context me ahoy. | |
| 09:04:31 | asettle | Thanks cdent | |
| 09:04:40 | bauzas | cdent: np, just trying to understand the missing bits and the resolution path | |
| 09:05:21 | cdent | asettle: in my bug report there are a lot of lurking "warnings" | |
| 09:06:40 | bauzas | anyway, seems like the RDO fix needs to be aligned with docs, or the other way | |
| 09:06:52 | bauzas | since both are pulling on two different directions | |
| 09:07:07 | asettle | I completely agree. | |
| 09:07:22 | bauzas | but FWIW, whatever lands in RDO needs to properly amend the upstream docs, I do agree | |
| 09:07:35 | bauzas | if those docs become wrong of course | |
| 09:07:36 | asettle | Provided we're not going to have substantially broken docs for another month, I'm happy to do what we need to do. | |
| 09:10:56 | bauzas | asettle: cdent: we have an internal bug triaging meeting today, will raise it up | |
| 09:11:05 | cdent | bauzas++ | |
| 09:11:22 | asettle | Thank you bauzas :) | |
| 09:11:32 | asettle | Could you keep us up to date on the launchpad bug if I'm not around? | |
| 09:11:39 | asettle | I mean, I'm sure I will be :( | |
| 09:11:39 | bauzas | we = Nova team in Red Hat, not RDO team | |
| 09:12:30 | bauzas | asettle: that's at 1400UTC | |
| 09:12:37 | asettle | Lovely. Just in time for tea. | |
| 09:12:59 | cdent | asettle: I think it is pretty clear that the communication for "how to do placement" went awry to many parties over the past... six months? So we can probably do some kind of retrospective or something to figure out what to do better in the future. From my standpoint I didn't have enough insight into the process and made too many assumptions about it being under control | |
| 09:13:42 | bauzas | cdent: well, mostly because that's deployment choices | |
| 09:14:09 | bauzas | cdent: so that's hard to find a common denominator for all | |
| 09:14:37 | bauzas | and we all say that Service Catalog serves the purpose to enable services the way you want | |
| 09:14:49 | cdent | bauzas: sure, but I think there's been a lot of confusion that we could have made less of a problem. The <Directory> thing, for example, seems like something that never should have happened because when that's wrong things simply don't work. | |
| 09:15:10 | bauzas | so, you, as a deployer, just needs to make consistent what you have in your service catalog entry and what you configure server-side | |
| 09:15:41 | asettle | cdent: thanks for your honesty. What can I do to help? | |
| 09:16:00 | bauzas | cdent: the port discussion clearly showed up that a lot people were having wrong expectations | |
| 09:16:33 | bauzas | the fact that the service catalog exists is for the exact reason that you can provide any endpoint you want | |
| 09:16:52 | bauzas | this is not aimed to be consistent across all openstack deployments | |
| 09:17:13 | cdent | bauzas: yes, I know, I'm not suggesting we change any of that. but the docs process has been more fraught with error than it should have been. we should figure out why and try to make it better | |
| 09:17:17 | cdent | asettle: will you be in boston? | |
| 09:17:29 | asettle | cdent: sure will be. You? | |
| 09:17:29 | bauzas | and application developers wanting to integrate with APIs need to use the Service Catalog as the discovery system | |
| 09:18:09 | cdent | yup, we should gather and chat | |
| 09:18:17 | bauzas | cdent: sure, I guess that's the crux of providing upstream documentation that sets kind of de-facto standard | |
| 09:19:15 | asettle | Okay, let's aim for that. I've got a shitty tight schedule Mon - Wed with updates and all that jazz. | |
| 09:19:29 | asettle | But I'm there until Friday :) | |
| 09:19:41 | asettle | bauzas: you gonna be there? | |
| 09:20:17 | bauzas | yup | |
| 09:20:33 | bauzas | we have a couple of sessions around placement | |
| 09:20:39 | asettle | Lucky meeee | |
| 09:20:48 | bauzas | both in the Forum and the conference itself | |
| 09:21:15 | bauzas | like, jay (pipes) has 2 sessions for talking $placement, one targeted for users and architects, the other more for devs | |
| 09:21:17 | asettle | Well, it should be interesting. | |
| 09:21:19 | bauzas | 2 talks | |
| 09:21:33 | asettle | Okay. Well. I'll try and make sure I get along to some of them. I'm a bit of a lone wolf this summit. | |
| 09:33:08 | openstackgerrit | fengzhr proposed openstack/nova master: Modify the description of flat_injected in nova.conf https://review.openstack.org/458789 | |
| 09:35:07 | frickler | it seems that the scheduler docs are outdated, can anyone confirm that it should mention e.g. filter_scheduler.enabled_filters instead of scheduler_default_filters here? https://docs.openstack.org/ocata/config-reference/compute/schedulers.html | |
| 09:35:33 | frickler | I'm also struggling to get scheduling to a specific az to work with Ocata, are there known issues? | |
| 09:39:44 | frickler | bauzas: cdent: regarding deployment of placement-api, are end users supposed to talk to it or would it rather be for admins/operators only? i.e. do I really need to deploy a public endpoint for it or would I rather only do an internal one? | |
| 09:40:52 | cdent | frickler: it is admin _for now_ but the expectation is that might change in the future, as having dashboard views over one's own usage is expected | |
| 09:42:32 | openstackgerrit | Lee Yarwood proposed openstack/nova master: compute: Detach volumes on _rebuild_default_impl failure https://review.openstack.org/442105 | |
| 09:42:33 | frickler | cdent: ah, that is a good point, so a public endpoint will make sense in the long run. | |
| 09:42:46 | cdent | frickler: another one of the things that might happen in the future warnings (like described above with asettle) is that the preference is for interface type to notmatter | |
| 09:42:55 | cdent | but that's a long way off | |
| 09:46:18 | asettle | Hey cdent since you're loving doc nova bugs, want another one? :D | |
| 09:46:37 | cdent | asettle: I can certainly look, but I'm making no promises | |
| 09:46:44 | asettle | Hooray! | |
| 09:46:46 | asettle | :p thanks | |
| 09:46:47 | openstack | Launchpad bug 1683104 in openstack-manuals "instance is not created rightly" [Undecided,New] | |
| 09:46:47 | asettle | https://bugs.launchpad.net/openstack-manuals/+bug/1683104 | |
| 09:47:00 | asettle | I'm not convinced of this one, let's put it that way | |
| 09:47:57 | asettle | But, my nova deep dive konwledge is bad :( | |
| 09:48:06 | cdent | mine too! | |
| 09:49:36 | cdent | asettle: heh, interesting. their solution works but is undesirable :) | |
| 09:49:40 | cdent | s | |
| 09:50:10 | asettle | cdent: I guess my real concern is whether or not what we have is going to work or not. | |
| 09:51:03 | cdent | asettle: while the apache configuration is incorrect things will not work and the bugs that cascade from that will be various | |
| 09:51:15 | asettle | -.- | |
| 09:51:33 | cdent | the original cause of this person's problem is that their apache config is wrong and they have worked around it by not using apache at all for the placement service | |
| 09:52:00 | asettle | Well, that's info I can work with. | |
| 09:52:11 | asettle | Okay. | |
| 09:52:18 | asettle | Thanks cdent. I can reply to the reporter with that :) | |
| 09:52:32 | asettle | Unless you've already said something? | |
| 09:52:43 | cdent | I've started something, yeah, but haven't finished it yet | |
| 09:52:50 | asettle | Okay :) tahnks cdent I appreciate this | |
| 09:56:47 | cdent | asettle: I left a comment but more might be needed | |
| 09:59:18 | asettle | cdent: lgtm. | |