Posted	Nick	Remark
#openstack-sdks - 2019-05-17
13:19:13	dtantsur	stingrayza: https://docs.openstack.org/reno/latest/user/usage.html
13:21:06	brtknr	any other Ansible reviewers please able to look at/apply shipit to: https://review.opendev.org/659366/
13:21:07	stingrayza	dtantsur: gotcha, thanks!
13:21:30	brtknr	any other Ansible reviewers please able to look at/apply shipit to: https://github.com/ansible/ansible/pull/56575
13:30:59	openstackgerrit	Raimund Hook (stingrayza) proposed openstack/openstacksdk master: Adding dns_domain parameter into create_network https://review.opendev.org/659366
13:36:18	stingrayza	dtantsur: thanks! :D
14:03:10	dtantsur	np
15:06:00	openstackgerrit	Surya Seetharaman proposed openstack/python-openstackclient master: Microversion 2.73: Support adding the reason behind a server lock https://review.opendev.org/659124
16:02:30	openstackgerrit	Merged openstack/openstacksdk master: Cap sphinx for py2 to match global requirements https://review.opendev.org/659442
17:08:57	openstackgerrit	Artem Goncharov proposed openstack/openstacksdk master: WIP add influxdb stats reporting. https://review.opendev.org/659841
17:27:43	openstackgerrit	Artem Goncharov proposed openstack/openstacksdk master: WIP rework statistics reporting https://review.opendev.org/659841
17:28:24	openstackgerrit	Merged openstack/openstacksdk master: Add image.stage methods https://review.opendev.org/652981
19:11:32	efried	mordred: I forgot to hit you up yesterday, now a good time to brainstorm sdk config bootstrap in nova?
20:58:36	openstackgerrit	Dean Troyer proposed openstack/python-openstackclient master: Compute: Add description support for server https://review.opendev.org/568549
21:33:34	openstackgerrit	Merged openstack/python-openstackclient master: Fix bug in endpoint group deletion https://review.opendev.org/655889
21:44:20	openstackgerrit	Dean Troyer proposed openstack/python-openstackclient master: Serialize more aggregate functional tests https://review.opendev.org/659883
23:07:58	openstackgerrit	Merged openstack/python-openstackclient master: Fix RuntimeError when showing project which has extra properties https://review.opendev.org/530207
#openstack-sdks - 2019-05-18
00:15:36	openstackgerrit	Dean Troyer proposed openstack/python-openstackclient master: Serialize more aggregate functional tests https://review.opendev.org/659883
02:42:35	openstackgerrit	Brin Zhang proposed openstack/python-openstackclient master: Add changes-before attribute to server list https://review.opendev.org/657373
03:51:53	openstackgerrit	Brin Zhang proposed openstack/python-openstackclient master: Add changes-before attribute to server list https://review.opendev.org/657373
12:57:09	openstackgerrit	Merged openstack/openstacksdk master: Adding dns_domain parameter into create_network https://review.opendev.org/659366
18:06:04	openstackgerrit	Merged openstack/python-openstackclient master: Serialize more aggregate functional tests https://review.opendev.org/659883
18:47:44	openstackgerrit	Merged openstack/python-openstackclient master: Remove code migrated to osc-lib long ago https://review.opendev.org/659693
#openstack-sdks - 2019-05-19
17:03:08	openstackgerrit	Dean Troyer proposed openstack/python-openstackclient master: Remove deprecated compute commands https://review.opendev.org/612781
17:16:17	openstackgerrit	Dean Troyer proposed openstack/python-openstackclient master: Remove deprecated compute commands https://review.opendev.org/612781
17:57:55	openstackgerrit	Dean Troyer proposed openstack/python-openstackclient master: Remove deprecated compute commands https://review.opendev.org/612781
17:57:55	openstackgerrit	Dean Troyer proposed openstack/python-openstackclient master: Remove deprecated identity commands and args https://review.opendev.org/612798
19:44:22	openstackgerrit	Dean Troyer proposed openstack/python-openstackclient master: Batch up minor cleanups for release https://review.opendev.org/659982
21:30:12	olaph	B556
22:07:56	openstackgerrit	Dean Troyer proposed openstack/python-openstackclient master: Remove deprecated image commands https://review.opendev.org/659431
23:22:38	openstackgerrit	Dean Troyer proposed openstack/python-openstackclient master: Remove deprecated network options https://review.opendev.org/613644
#openstack-sdks - 2019-05-20
07:25:25	openstackgerrit	yanpuqing proposed openstack/python-openstackclient master: Client should parse string to boolean for valuse 'is_domain' https://review.opendev.org/660038
08:17:37	openstackgerrit	yanpuqing proposed openstack/python-openstackclient master: Client should parse string to boolean for valuse 'is_domain' https://review.opendev.org/660038
10:10:27	openstackgerrit	yanpuqing proposed openstack/python-openstackclient master: Client should parse string to boolean for valuse 'is_domain' https://review.opendev.org/660038
10:28:22	openstackgerrit	Artem Goncharov proposed openstack/openstacksdk master: WIP rework statistics reporting https://review.opendev.org/659841
12:05:56	openstackgerrit	Artem Goncharov proposed openstack/openstacksdk master: WIP rework statistics reporting https://review.opendev.org/659841
13:41:51	openstackgerrit	Dean Troyer proposed openstack/python-openstackclient master: Batch up minor cleanups for release https://review.opendev.org/659982
13:48:07	efried	mordred: ...or today?
13:51:42	mordred	efried: yes!
13:51:50	mordred	efried: today is a great day to discuss such things
13:52:00	efried	(gtema, dustinc, dtantsur)
13:52:39	efried	mordred: So today we have oslo.config for e.g. [placement]=>ks_loading.get_{auth|session|adapter}_config_opts
13:53:00	efried	I'm thinking we could inject [placement]cloud_region=<str>
13:53:12	efried	(is it called a "cloud region", this section in clouds.yaml?)
13:53:50	efried	The code looking at that config section will use the presence of 'cloud_region' to decide whether to use the ksa opts or look at clouds.yaml.
13:54:28	efried	that's... pretty much it.
13:55:13	mordred	yes - I think that's about right. and I think maybe what we want is a function similar to get_{}_config_opts in sdk that ads the parameter
13:55:43	efried	yeah, that would work. Except it's only one opt, so meh?
13:55:46	mordred	(the section and parameter in sdk is just called "cloud" - a CloudRegion object is a cloud + a region_name
13:56:04	efried	oh, okay. I definitely want to be told what a good name for the opt is.
13:56:23	mordred	yeah - might just be meh - mostly thinking about how we can make it easy for other non-nova services to follow the lead
13:56:29	dtantsur	cloud_name is probably fine
13:56:34	efried	'cloud' might be a bit too broad. But I don't know ...
13:56:49	mordred	well - cloud is what is used everywhere else such a value is consumed
13:57:08	mordred	so while I do wish we'd named it better ... probably more confusing for the oslo opt to be different
13:58:02	efried	I can live with 'cloud'. I don't think we have anything else in nova that'll conflict, at least.
13:58:35	mordred	oh - also - fwiw, if there is only one cloud entry defined in clouds.yaml, the won't need to put a cloud= setting in nova.ini
13:58:54	efried	Yeah, but then we would have no way to know that we're looking for clouds.yaml instead of ksa opts.
13:59:36	mordred	efried: this is a good point, actually
13:59:51	efried	And I'm an opt conservative - fewer options rather than more wherever possible - so I'd like to avoid use_clouds_yaml = $bool; cloud = <str:optional>
14:00:03	mordred	efried: and in fact, we ignore clouds.yaml files in the current patch - so we'll probably want someone to be explicit anyway so we can avoid avoiding the file
14:00:14	mordred	++
14:00:25	mordred	I agree = no use_clouds_yaml = $bool
14:00:35	efried	cool, so here's another angle:
14:00:45	efried	eventually I think we probably want to deprecate and remove the ksa oslo.config stuff entirely.
14:01:07	efried	And the theory behind clouds.yaml is more like define-once...
14:01:25	efried	so eventually I would think we want to have the 'cloud' option defined in just one place in nova.conf, rather than in every section.
14:01:40	efried	Because presumably one nova wouldn't want different services to talk to different clouds?
14:03:08	efried	so like [DEFAULT]cloud=$str, or a section that somehow denotes [shit-the-sdk-uses]
14:03:48	mordred	yes. I think this is spot on
14:04:07	efried	Would rather not put it in [DEFAULT] I guess; suggestions for what to call that second thing?
14:04:24	efried	Is [openstacksdk] too crazy?
14:04:48	efried	want something that makes sense from an operator pov, not sure that's it.
14:05:57	mordred	yeah. I'm not sure it is either. maybe [openstackapi]? or just [openstack] ?
14:06:33	efried	again my initial reaction is "too broad", but letting it settle for a sec, maybe it's the right thing.
14:06:39	mordred	efried: do we think people still might want to make multiple accounts for nova to use to talk to things?
14:06:50	efried	see, I don't know that answer.
14:07:04	efried	But there's another wrinkle to bring up, so maybe I'll mention that and we can come back to --^ in a sec.
14:07:43	mordred	like - I'd love to deprecate per-service options - but I could see deployers maybe being unhappy with a design that there's only one account for nova to use?
14:07:43	efried	It's this: some operations, like glance stuff, are done at the behest of the user - using the user's auth token. Other things, like ironic, are done with an admin auth, pulled from the config.
14:08:00	mordred	yah
14:08:09	efried	and for extra craziness, there's other stuff - neutron - where sometimes it's user and sometimes it's admin.
14:08:45	mordred	we've got a connect_as method to allow starting with an existing connection and connecting with a new set of credentials
14:08:49	efried	This is probably just a matter for careful coding on the nova side, because I assume I can create my Connection with whatever auth ...
14:08:50	efried	yeah.
14:08:59	efried	well, in this case it's going to be the other way around.
14:09:08	efried	Get session/adapter from clouds.yaml, but use <this> auth.
14:09:12	mordred	yes
14:09:41	mordred	that's right -we might have to adapt the connect_as to understand being handed an auth - but in general that's how that should work
14:09:53	efried	okay
14:10:11	mordred	so you'll have a "get me the connectino I use to talk to neutron" and then, now that I have that, please get me a connection that uses all of those details but with $auth object
14:10:35	mordred	(that way things like version discovery cache get shared :) )
14:10:58	efried	Yes, or just two separate connection objects. Construct one by saying "go to clouds.yaml section X" and the other by saying "go to clouds.yaml section X but use <this auth> instead"
14:11:09	efried	mm, yeah, or that.
14:11:32	efried	so, details to be worked out, but I think we agree on the broad strokes and it all sounds possible.
14:11:58	efried	so back to 'multiple accounts'... since we're going to need to have a transition period anyway, we could have [openstack]cloud=$str and then per-section overrides of the same name to allow the multiple accounts.
14:12:28	efried	I need to look into whether I can reliably/easily detect whether ksa auth options are present, though.
14:12:57	efried	because if [openstack]cloud=$str and [placement]$ksa_opts, I need to use the latter
14:13:23	efried	I think I've seen this done based on detecting the `auth_type` option, but not sure if that's the accepted/canonical way to do it.
14:13:24	efried	and

Earlier   Later