Thursday, 2016-02-04

*** sdake has joined #openstack-meeting-cp00:36
*** sdake_ has joined #openstack-meeting-cp00:50
*** sdake has quit IRC00:54
*** nikhil has quit IRC01:21
*** sdake_ has quit IRC01:33
*** nikhil has joined #openstack-meeting-cp01:35
*** angdraug has quit IRC01:53
*** nikhil_k has joined #openstack-meeting-cp02:24
*** nikhil has quit IRC02:27
*** sdake has joined #openstack-meeting-cp03:01
*** dims has joined #openstack-meeting-cp03:37
*** sdake has quit IRC03:45
*** sdake has joined #openstack-meeting-cp03:53
*** dims has quit IRC03:53
*** tpeoples has quit IRC04:12
*** jroll has quit IRC04:13
*** sdake has quit IRC04:13
*** sdague has quit IRC04:13
*** elmiko has quit IRC04:13
*** elmiko has joined #openstack-meeting-cp04:14
*** sdague has joined #openstack-meeting-cp04:14
*** jroll has joined #openstack-meeting-cp04:14
*** tpeoples has joined #openstack-meeting-cp04:16
*** SergeyLukjanov has quit IRC04:19
*** smcginnis has quit IRC04:19
*** russellb has quit IRC04:19
*** SergeyLukjanov has joined #openstack-meeting-cp04:20
*** russellb has joined #openstack-meeting-cp04:20
*** smcginnis has joined #openstack-meeting-cp04:20
*** markvoelker_ has quit IRC05:34
*** sdake has joined #openstack-meeting-cp05:40
*** sdake_ has joined #openstack-meeting-cp05:45
*** sdake has quit IRC05:45
*** sdake_ has quit IRC06:13
*** sdake has joined #openstack-meeting-cp06:13
*** markvoelker has joined #openstack-meeting-cp06:35
*** markvoelker has quit IRC06:39
*** markvoelker has joined #openstack-meeting-cp07:36
*** markvoelker has quit IRC07:41
*** evgenyf has joined #openstack-meeting-cp07:49
*** sdake has quit IRC07:56
*** sdake has joined #openstack-meeting-cp08:26
*** markvoelker has joined #openstack-meeting-cp09:37
*** markvoelker has quit IRC09:41
*** mugsie has quit IRC10:39
*** mugsie has joined #openstack-meeting-cp10:40
*** sdake has quit IRC10:44
*** dims has joined #openstack-meeting-cp11:12
*** markvoelker has joined #openstack-meeting-cp11:38
*** markvoelker has quit IRC11:43
*** markvoelker has joined #openstack-meeting-cp12:53
*** markvoelker has quit IRC12:58
*** markvoelker has joined #openstack-meeting-cp13:11
*** david-lyle has quit IRC13:38
*** sdake has joined #openstack-meeting-cp13:50
*** NanosatC-BR1 has joined #openstack-meeting-cp14:07
*** dims_ has joined #openstack-meeting-cp14:10
*** dims has quit IRC14:12
sdaguehey folks, who's around for service catalog?15:01
bknudson_me15:01
sdagueok, lets do it. Though no anne or chris15:02
sdague#startmeeting service-catalog-tng15:02
openstackMeeting started Thu Feb  4 15:02:57 2016 UTC and is due to finish in 60 minutes.  The chair is sdague. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: service-catalog-tng)"15:03
openstackThe meeting name has been set to 'service_catalog_tng'15:03
bknudson_they can check the logs later15:03
sdagueAgenda is - https://wiki.openstack.org/wiki/Meetings/ServiceCatalogTNG#Next_Agenda15:03
sdague#topic Project Id Optionality in projects15:03
*** openstack changes topic to "Project Id Optionality in projects (Meeting topic: service-catalog-tng)"15:03
bknudson_anne said there was some problem with optional project id.15:03
sdague#info nova patch to make project id optional has landed - https://review.openstack.org/#/c/23307615:04
sdaguebknudson_: do you remember what that was?15:04
bknudson_she didn't say what it was.15:04
bknudson_I figured you'd know15:04
sdagueI guess not15:05
sdagueI have a patch up to make this default configuration in devstack, however there are Tempest tests blocking that15:05
sdaguethose are proposed for removal - https://review.openstack.org/#/c/271467/ - ETA TBD15:06
bknudson_the tempest change has a -2 so I guess that needs to be resolved15:06
sdagueit has a procedural -215:06
sdaguebecause there is a tempest test removal process15:06
sdagueI think it's resolvable15:06
bknudson_shouldn't be any objection to removing this one15:07
sdagueagree15:07
*** annegentle has joined #openstack-meeting-cp15:07
annegentlehere! Sorry.15:07
sdagueannegentle: bknudson_ said you had said there was a problem with optional project id15:08
sdaguebefore we move on I wanted to figure out what that issue was15:08
annegentlesdague: yes I might just be behind15:08
annegentlesdague: I read your note to the mailing list15:08
*** nikhil_k is now known as nikhil15:08
annegentlesdague: so maybe I misunderstood15:08
sdagueannegentle: ah, right, about routing overlap15:08
bknudson_might be nice to be able to test the same thing somehow, but then the test would have to build the URL itself.15:08
annegentleright15:08
sdaguewhich we solved with specifying a project id regex15:09
annegentlesdague: did you find a workournd?15:09
annegentlesdague: ah ok15:09
sdagueyes, the nova solution is a default project id regex which is [0-9a-f]+15:09
bknudson_since I assume a user with a token in one project won't even see an instance in another project15:09
sdaguebknudson_: right, all decisions in nova are based on the context value of project_id15:09
annegentlebknudson_: well, some providers can set up projects as billing dividers15:10
annegentlebknudson_: so a scientist might have two projects15:10
sdagueannegentle: sure, but they have to specify which project they are acting in when they get the token15:10
annegentlebknudson_: but, the token would not be scoped for only two projects.15:10
annegentlesdague: yeah, is there still a super-admin token?15:10
annegentlesdague: those calls might require indicating which project15:10
bknudson_keystone doesn't support getting a token scoped to 2 projects.15:10
sdagueannegentle: I'm not sure I know what that means?15:10
bknudson_in order to operate in nova you need a token scoped to a project15:11
annegentlebknudson_: sdague: just a sec I'll find the super token ref I'm thinking of15:11
sdaguebknudson_: right15:11
annegentlebknudson_: as a cloud provider sometimes you need to shut down someone else's server. Is that a scoped project token an admin gets?15:12
sdagueand admistrative commands that operate on resources either take the resource id, and admin is allowed to do things because they have the admin role15:12
sdagueor there is an all_tenants param for display on list things15:12
sdaguewhich again, requires admin role15:12
sdaguewithout which the user would just get their own tenant15:13
annegentlebknudson_: ah, I'm thinking of a domain scoped token, http://docs.openstack.org/developer/keystone/configuration.html#keystone-api-protection-with-role-based-access-control-rbac15:13
bknudson_is there an example api? I'm not familiar enough with the nova apis15:13
sdaguebknudson_: for which?15:13
bknudson_sdague: an admin shutting down a compute in a different project15:14
annegentlehttp://developer.openstack.org/api-ref-compute-v2.1.html#os-admin-actions-v2.115:14
annegentlespecifically, http://developer.openstack.org/api-ref-compute-v2.1.html#resetState15:14
sdagueyeh, but DELETE is also admin_or_owner in policy15:15
bknudson_so in the case of these admin actions the new project ID is in the URL.15:15
sdaguethe project_id in the url is never actionable15:16
annegentleok15:16
sdagueif there is something specifically about a new project_id, it's passed as a query param15:16
bknudson_the old request would be POST http://openstack/compute/{tenant_id_1}/v2.1/​{tenant_id}​/servers/​{server_id}​/action15:16
sdaguenot quite15:16
bknudson_and the new one is POST http://openstack/compute/v2.1/​{tenant_id}​/servers/​{server_id}​/action15:16
sdaguehttp://openstack/compute/v2.1/​{tenant_id_1}​/servers/​{server_id}​/action15:16
sdagueand new one is15:17
sdaguehttp://openstack/compute/v2.1/​servers/​{server_id}​/action15:17
bknudson_oh, the first tenant_id was in the catalog?15:17
sdaguethe catalog entry returned today is15:17
annegentleright15:17
sdaguehttp://openstack/compute/v2.1/​{tenant_id_1}​15:17
bknudson_I assume the server_id is unique across projects15:18
sdagueserver_id is globally unique15:18
bknudson_so nova doesn't look in the project to find the server15:18
sdaguecorrect15:18
bknudson_is that only for the admin actions?15:18
sdagueno, for everything15:18
sdaguethis is part of why removing project id was pretty sensible and easy, it's not really a first order construct in our resources15:19
bknudson_all these docs will have to change!15:19
sdaguebknudson_: yep15:19
sdaguebut, they will be massively less confusing15:19
sdagueswift is really the only project where tenant_id is really a container15:20
bknudson_hopefully nova has some code to verify that the user access to the server15:20
annegentlebknudson_: it's funny, WADL has a wrapper, so the docs aren't too hard to change15:20
sdagueyes, admin_or_owner policy enforcement15:20
sdaguehttps://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/models.py#L25315:21
annegentlegood15:21
sdagueok, we good with all that and can move on?15:22
bknudson_yes, thanks for the explanation15:22
sdagueit was a good summary of some of where we stand15:22
sdagueyep15:22
sdagueannegentle: lastly, were you building the list of projects that would also need this?15:22
annegentlesdague: I only got so far15:22
annegentlesdague:thinking, just a se15:23
annegentlesec15:23
sdaguewell, if we start from oldest projects first and move forward we can hopefully at least reset expectations a bit, I still expect that to be a Newton thing at this point15:23
annegentlesdague: yeah, this is the list that is not investigated https://wiki.openstack.org/wiki/API_Working_Group/Current_Design/Service_Catalog#Projects_that_I_couldn.27t_find_in_a_service_catalog_and_will_need_to_investigate_further15:24
sdagueok, great!15:24
annegentlesdague: so does anything need to happen with this list? https://wiki.openstack.org/wiki/API_Working_Group/Current_Design/Service_Catalog#These_projects_have_a_TENANT_ID_in_one_of_the_example_service_catalogs15:25
sdagueI think for Mitaka we are probably out of runway, but we should come up with a Newton push plan. We can wait until M3 for that15:25
bknudson_we can put nova in a new category -- projects that have tenant_id in the catalog but it's optional15:26
sdague#action around M3 revisit how we'll push for project_id optionality in projects for Newton15:26
sdaguebknudson_: yep15:26
annegentlebknudson_: ok, that's for mitaka right?15:26
sdagueannegentle: yes, we've landed the code15:26
annegentlesdague: ok15:26
sdagueok, moving on....15:26
bknudson_I'll make that change in the wiki15:26
annegentlebknudson_: sounds goo15:26
annegentlegood even15:26
sdague#topic Service Common Names15:27
*** openstack changes topic to "Service Common Names (Meeting topic: service-catalog-tng)"15:27
sdagueI kicked this one off on the list this morning, it's been bubbling about recently quite a bit15:27
sdaguehttp://lists.openstack.org/pipermail/openstack-dev/2016-February/085748.html15:27
sdagueI think we can mostly drive the discussion there and let people settle on the fact that we need to do this thing15:28
sdaguewhich is the way the wind is blowing now15:28
sdagueI think there is just a mechanics issue of where the registry actually is15:28
annegentlesdague: do you think there's pushback on where?15:28
annegentlesdague: or "who will do the work and be responsible?" <-- that's more my take15:29
bknudson_I always thought the name registry should be in projects.yaml or some TC repo, not keystone.15:29
sdagueI think the question seemed to be whether etowes was ok with it being part of API-WG repo15:29
bknudson_keystone just stores whatever you put in it.15:29
sdaguebknudson_: right, definitely agree with that15:29
sdagueit's just whether the TC does this directly, or basically gives API WG authority to do it15:30
sdagueI figured I'd let that one just simmer a bit15:30
sdaguepersonally, mostly don't care, as long as we get vague concensus15:30
bknudson_it'll be interesting to see how keystone gets at the info if we think we need keystone to enforce it.15:31
sdaguebknudson_: I don't think keystone should enforce it15:31
sdagueI'm ok with keystone being dumb store for what people say15:31
*** angdraug has joined #openstack-meeting-cp15:31
bknudson_works for me15:32
sdagueok, that was mostly an FYI, please get onto the thread and we'll drive discussion there15:32
sdague#topic JSON Schema for SC15:32
*** openstack changes topic to "JSON Schema for SC (Meeting topic: service-catalog-tng)"15:32
sdaguebknudson_: I think 2 weeks ago you said you'd take a first swipe at such a thing15:32
sdagueany progress so far?15:32
bknudson_y, I didn't get this done.15:33
sdagueok, no prob15:33
bknudson_didn't happen at the keystone meetup15:33
bknudson_I'll throw it at the top of my work queue15:33
sdagueI'll keep it as standing item on the agenda so we don't forget15:33
annegentlesounds good15:33
sdague#topic Open Discussion15:33
*** openstack changes topic to "Open Discussion (Meeting topic: service-catalog-tng)"15:33
annegentleI got nuthin'15:33
bknudson_I'm actually pretty familiar with the JSONSchema spec now since I was reviewing some changes.15:34
annegentleI can talk to Everett etowes this morning15:34
sdaguethe only thing there is I've been bad advertising this meeting. So if anyone knows anyone that wants to help step up as meeting promoter for this, let me know. I'll put a call out to a few folks as well.15:34
annegentlesdague: I think some of the discussion also is in https://review.openstack.org/#/c/273158/15:34
sdagueannegentle: yeh, the experimental APIs one15:35
annegentlesdague: as far as differentiation at the resource level15:35
annegentlesdague: I'm not sure we should offer experimental at all15:36
sdagueannegentle: I mostly agree15:36
annegentlesdague: most API designs have to be fully baked to be competitive in the market15:36
sdaguebut if people want to, it shouldn't be in the same API15:36
bknudson_keystone as JSONHome and that's where we specify experimental.15:36
annegentleit's a trust thing15:36
annegentlesdague: yeah we need to be precise -- API or endpoint?15:36
sdagueendpoint15:36
annegentlesdague: I'm all for a second experimental endpoint, I think.15:36
annegentlesdague: ok yeah15:36
annegentleand the API is the GET /blah/resources right? In that spec ^^15:37
bknudson_we also called some APIs extensions and they could be disabled15:37
annegentlesdague: I need to write a review there15:37
sdagueyeh, I'll go pile on a bit later on that15:37
annegentlebknudson_: ugh those are the worst to document and use tho15:37
annegentlesdague: ok15:37
annegentle"If you're going to experiment, put it on a separate endpoint"15:37
bknudson_I agree that it's not fun to have optional apis.15:37
sdagueok, anything else from folks?15:37
annegentlenopety15:37
sdaguegreat, thanks folks15:38
annegentleheh a nope and a thank you combo15:38
sdague#endmeeting15:38
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:38
openstackMeeting ended Thu Feb  4 15:38:07 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_catalog_tng/2016/service_catalog_tng.2016-02-04-15.02.html15:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_catalog_tng/2016/service_catalog_tng.2016-02-04-15.02.txt15:38
openstackLog:            http://eavesdrop.openstack.org/meetings/service_catalog_tng/2016/service_catalog_tng.2016-02-04-15.02.log.html15:38
*** annegentle has quit IRC15:46
*** david-lyle has joined #openstack-meeting-cp16:24
*** sdake has quit IRC16:51
*** sdake has joined #openstack-meeting-cp16:52
*** evgenyf has quit IRC17:05
*** NanosatC-BR1 has quit IRC17:09
*** sdake has quit IRC18:12
*** sdake has joined #openstack-meeting-cp19:05
*** david-lyle has quit IRC19:11
*** nikhil_k has joined #openstack-meeting-cp19:52
*** nikhil has quit IRC19:55
*** stevemar has quit IRC19:56
*** sdake_ has joined #openstack-meeting-cp20:02
*** sdake has quit IRC20:03
*** sdake has joined #openstack-meeting-cp20:04
*** sdake_ has quit IRC20:08
*** russellb_ has joined #openstack-meeting-cp20:40
*** angdraug has quit IRC20:47
*** russellb has quit IRC20:47
*** bswartz has quit IRC20:47
*** ttx has quit IRC20:47
*** angdraug has joined #openstack-meeting-cp20:49
*** ttx has joined #openstack-meeting-cp20:49
*** angdraug has quit IRC20:50
*** bswartz has joined #openstack-meeting-cp20:51
*** sdake has quit IRC21:49
*** russellb_ is now known as russellb21:57
*** russellb has joined #openstack-meeting-cp21:57
*** sdake has joined #openstack-meeting-cp22:41
*** david-lyle has joined #openstack-meeting-cp22:48
*** david-lyle has quit IRC22:52
*** angdraug has joined #openstack-meeting-cp23:21
*** dims_ has quit IRC23:31
*** dims has joined #openstack-meeting-cp23:32

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!