15:00:37 <sdague> #startmeeting service-catalog-tng
15:00:38 <openstack> Meeting started Thu Jan 14 15:00:37 2016 UTC and is due to finish in 60 minutes.  The chair is sdague. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:39 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:42 <openstack> The meeting name has been set to 'service_catalog_tng'
15:00:42 <annegentle> mostly because I want to do a spec merge happy dance
15:00:50 <thingee> meee too
15:00:53 <bknudson_> hi
15:00:56 <cdent> holda
15:00:58 <cdent> oops
15:01:10 <annegentle> combo of holla, hola, and holdon :)
15:01:19 <cdent> that'll work
15:01:21 <sdague> ok, agenda for this week - https://wiki.openstack.org/wiki/Meetings/ServiceCatalogTNG
15:01:27 <sdague> #link https://wiki.openstack.org/wiki/Meetings/ServiceCatalogTNG
15:01:45 <sdague> #info Service Catalog Spec has merged!
15:01:54 <sdague> thanks much to annegentle for getting that sorted
15:02:31 <sdague> #topic Project Id Optionality in projects
15:02:41 * cdent celebrates
15:02:52 <sdague> this has hit an interesting wrinkle in doing the work in nova
15:02:58 <annegentle> oo do tell
15:03:05 <sdague> in that project_id has no formal schema in keystone
15:03:11 <bknudson_> there's always a catch.
15:03:27 <sdague> http://lists.openstack.org/pipermail/openstack-dev/2016-January/083976.html
15:03:39 <sdague> yeh, it makes overlapping routes a problem
15:03:56 <sdague> so in nova we just agreed we'd make a stab at a regex
15:04:03 <bknudson_> typically the project_id is a uuid but if you use ldap for assignments it can be a name or whatever
15:04:16 <annegentle> huh
15:04:16 <bknudson_> we're removing the ldap assignments this release
15:04:36 <bknudson_> but somebody could always write their own assignment driver that doesn't use uuid
15:04:46 <sdague> bknudson_: so it would be really nice if keystone provided a contract on that
15:04:56 <sdague> ids in most projects are enforced to a schema
15:05:26 <sdague> which is something autogenerated, names and other attributes can be whatever
15:05:27 <bknudson_> you'll have issues if the project id is too long for the sql column.
15:05:32 * stevemar lurks
15:05:54 <bknudson_> the ldap assignment backend was a bad idea
15:06:03 <sdague> anyway, hopefully I'll have patches ready to go for this next week
15:06:09 <bknudson_> but it came from identity backend
15:06:18 <sdague> cdent has also volunteered to help me with test fixes
15:06:27 <cdent> I have indeed
15:06:56 <sdague> I do kind of wonder if other projects will get hit by this kind of thing
15:07:17 <sdague> ok, open discussion time
15:07:22 <sdague> #topic Open Discussion
15:07:30 <bknudson_> are you able to deprecate the project ID paths?
15:07:32 <annegentle> interesting, thanks for the research
15:07:45 <sdague> bknudson_: for the time being we'll just support both
15:08:43 <sdague> I don't know that we can deprecate project_id until we have the new SC schema
15:08:49 <annegentle> ah ok
15:08:55 <annegentle> yeah doesn't seem like it
15:08:56 <sdague> but honestly I just haven't gotten that far
15:09:14 <bknudson_> I've got some WIP changes proposed to tempest-lib to get it to work with unversioned keystone endpoint... not working yet.
15:09:21 <bknudson_> also, need to stop doing reviews so I can work on it.
15:09:39 <bknudson_> where does the schema wind up?
15:09:53 <sdague> no volunteers yet to do anything with it
15:09:53 <stevemar> probably a new feature for keystone, i would think
15:10:43 <sdague> ok, anything else from folks? I'm going to go dive into some code and see what other issues I run into
15:11:16 <annegentle> not from me
15:11:19 <cdent> sdague: I think have a few cycles I can spend in this area (not just on the aforementioned but stuff)
15:11:22 <cdent> bug
15:12:00 <cdent> we'll talk, have cawfee
15:12:18 <sdague> sounds good
15:12:23 <sdague> ok, thanks folks
15:12:25 <sdague> #endmeeting