16:09:23 <schwicke> #startmeeting hierarchical_multitenancy
16:09:24 <openstack> Meeting started Fri Dec  5 16:09:23 2014 UTC and is due to finish in 60 minutes.  The chair is schwicke. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:09:25 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:09:27 <openstack> The meeting name has been set to 'hierarchical_multitenancy'
16:09:33 <schwicke> sorry for being late.
16:09:44 <sajeesh> no problem
16:09:47 <raildo> hi all :)
16:09:52 <schwicke> We don't have much on the agenda today but I think it is worth to have a quick review of where we are
16:09:58 <schwicke> #topic status
16:10:17 <raildo> sure
16:10:42 <raildo> so, for my part, we have the base code about HM merged with the branch master
16:10:53 <sajeesh> ok
16:10:55 <schwicke> raildo: that's great news
16:11:01 <raildo> now we just have the inherited roles part in review
16:11:06 <sajeesh> true
16:11:15 <raildo> schwicke, absolutely :)
16:11:27 <sajeesh> raildo great
16:11:28 <schwicke> sajeesh: if I understand correctly this allows you to submit your code, right ?
16:11:41 <sajeesh> yes
16:11:51 <schwicke> can we action item that ?
16:11:53 <sajeesh> once the bp is accepted
16:12:01 <schwicke> right.
16:12:17 <sajeesh> I am updating the bp now
16:12:19 <raildo> and we have the new spec about HM improvements in review: https://review.openstack.org/#/c/135309/ and today i'll send the Reseller spec :)
16:12:53 <sajeesh> will upload the patch within one or two days
16:12:54 <schwicke> sajeesh: any show stoppers for the bp?
16:13:11 <sajeesh> don't know
16:13:26 <sajeesh> we have to convice the reviewers
16:13:45 <schwicke> #action sajeesh will update the blue print and prepare for submitting the code
16:13:52 <sajeesh> essentially the token part
16:13:57 <raildo> do you try talk wil jaypipes, vishy to approve the bp?
16:14:24 <sajeesh> It will be nice to take his help
16:14:43 <sajeesh> I will add him as the reviewer
16:14:59 <schwicke> is vishy in the list already ?
16:15:03 <sajeesh> yes
16:15:07 <schwicke> I think he's connected ...
16:15:32 <schwicke> I will have a look at the comments as well.
16:15:57 <schwicke> #action schwicke should review the comments on the bp and comment if possible or useful
16:15:59 <raildo> schwicke, great
16:16:20 <schwicke> not that I'd have a weight as vish :-P
16:16:44 <raildo> Ih someone have any question about the keystone implementation, just ping me, or send a email and I'll respond :)
16:16:47 <raildo> If*
16:16:59 <sajeesh> raildo ,thanks
16:16:59 <schwicke> great, thanks!
16:17:25 <sajeesh> raildo,do we need to attend the nova meeting like we did last time
16:17:25 <raildo> np
16:18:10 <sajeesh> so that we can discuss about our bp there
16:18:41 <raildo> ok, I'll do that
16:19:03 <raildo> December 11, 2014 14:00 UTC, #openstack-meeting-alt
16:19:04 <raildo> right?
16:19:11 <sajeesh> right
16:19:14 <raildo> ok
16:20:04 <schwicke> yes, looks like December 11, 2014 14:00 UTC, #openstack-meeting-alt
16:20:13 <sajeesh> yes
16:20:44 <schwicke> in the stuck review section maybe ?
16:21:01 <sajeesh> yes
16:21:26 <schwicke> How does that work ? Can we just add the topic to the wiki ?
16:21:30 <raildo> and kilo spec,
16:21:41 <sajeesh> I have to check it
16:21:44 <raildo> schwicke, in keystone works in this way
16:21:54 <raildo> you just put the topic
16:21:58 <sajeesh> ok
16:23:03 <raildo> #link https://etherpad.openstack.org/p/kilo-nova-priorities
16:23:11 <raildo> that is a topic about HM here
16:23:29 <sajeesh> hi gabriel
16:23:38 <raildo> maybe you can expand this topic to explain our problem
16:23:58 <sajeesh> ok
16:24:10 <gabriel-bezerra> hi sajeesh
16:24:19 <sajeesh> hi
16:24:53 <sajeesh> raildo,I will add
16:25:25 <gabriel-bezerra> I have news from Salvatore since our last meeting
16:25:31 <sajeesh> ok
16:25:35 <gabriel-bezerra> is it a topic for today?
16:26:14 <raildo> gabriel-bezerra, we don't have a agenda today, you can just create a new topic :D
16:26:24 <sajeesh> right :-)
16:26:30 <schwicke> #action sajeesh will add a topic on HM to the nova agenda
16:26:41 <schwicke> gabriel-bezerra: yes
16:27:05 <gabriel-bezerra> salv-orlando: ^
16:27:50 <schwicke> #topic  news from Salvatore
16:28:29 <gabriel-bezerra> so, you received my e-mail with the talk, right?
16:28:32 <gabriel-bezerra> last week
16:28:42 <sajeesh> yes gabriel
16:28:51 <sajeesh> we have seen the mail
16:29:12 <gabriel-bezerra> then I sent him the answer about the case where no nesting is involved
16:29:45 <gabriel-bezerra> his answer:
16:30:07 <schwicke> #chair raildo
16:30:07 <openstack> Current chairs: raildo schwicke
16:30:47 <gabriel-bezerra> "sounds good to me. I’ll seek out this code and see how I can use it. I wonder however if the hierarchical multitenancy people have already in mind to work on a solution to provide quota management and enforcement. In which case this will probably make my work useless, and I should just hand it off to them."
16:32:32 <gabriel-bezerra> then I explained him that you have modified only nova's code to work in the hierarchical case, you didn't have made any new enforcement and management engine besides that
16:33:05 <schwicke> ok
16:33:16 <gabriel-bezerra> and sent him a link to the spec review and to the code on github/sajeesh/nested_quota
16:33:55 <sajeesh> ok
16:34:11 <schwicke> did you hear back from him since ?
16:34:29 <gabriel-bezerra> No, I didn't.
16:34:57 <gabriel-bezerra> I didn't miss anything in that explanation, did I?
16:35:10 <schwicke> don't think so, sounds fine to me
16:35:13 <sajeesh> gabriel you are right
16:35:49 <sajeesh> I have extended the existing quota driver for nested projects
16:36:07 <sajeesh> without disturbing the current set up
16:37:47 <gabriel-bezerra> ok, good then
16:38:09 <schwicke> so let's wait. I guess he needs a bit of time to review the stuff
16:38:18 <gabriel-bezerra> sure
16:38:19 <schwicke> and proceed with our code.
16:38:22 <sajeesh> right
16:39:10 <sajeesh> raildo,regarding the keystone,whether the parent list contains only the list of parents upto or root or parents well as children
16:39:20 <schwicke> #agree we'll wait for a review from their side and proceed as planned
16:39:41 <gabriel-bezerra> schwicke: from whose side?
16:40:19 <schwicke> Salvatore  et al
16:40:49 <schwicke> unfortunately I have to leave.
16:40:56 <sajeesh> ok
16:40:56 <raildo> sajeesh, imagine that we have a hierarchy A -> B -> C , so if i call "list parents of C" we respond with the A and B information
16:41:13 <schwicke> raildo will take over the chair from here. Thanks a lot for that!
16:41:22 <raildo> schwicke, no problem :)
16:41:26 <schwicke> CU!
16:41:34 <sajeesh> ok
16:41:45 <sajeesh> bye shwicke
16:42:20 <sajeesh> raildo,so child list of B and A will not be there ...right ?
16:42:34 <raildo> sajeesh, yes
16:43:02 <raildo> you have to use the subtree list to see this information
16:43:09 <sajeesh> yes
16:43:34 <sajeesh> currently I am having an extra call to keystone
16:43:35 <gabriel-bezerra> sajeesh: yes, no siblings
16:44:12 <raildo> sajeesh, but you have the option to call for the parents and subtree in one API call
16:44:26 <sajeesh> ok..that is great
16:44:40 <sajeesh> can you please tell me the api call for that
16:44:50 <sajeesh> any documentation ?
16:45:09 <raildo> sure, 1 sec
16:45:15 <sajeesh> in that case I can save a keystone call
16:46:24 <raildo> https://review.openstack.org/#/c/130103/8/api/v3/identity-api-v3.rst line3270
16:47:22 <sajeesh> raildo,thanks a lotg
16:47:49 <sajeesh> what about the keystone client....is it ready too ?
16:48:05 <raildo> sajeesh, yes
16:48:18 <raildo> but the code still in review...
16:48:35 <raildo> I think that we'll merge the code to kilo-2
16:48:44 <sajeesh> any documentation regarding that ?
16:49:28 <raildo> no... we have the patch: https://review.openstack.org/#/c/115770/
16:49:39 <sajeesh> ok thanks
16:49:53 <raildo> when we create the parameters subtree_as_list and parents_as_list
16:50:44 <raildo> adn in the Hm improvements spec, we are creating the subtree_ids and parents_ids, this is a project dict with just the projects_ids
16:50:52 <sajeesh> ok
16:51:31 <raildo> (we just have more 5 min)
16:51:45 <sajeesh> ok
16:52:13 <sajeesh> raildo ,I will read the specs and will inform you if I am having some doubts
16:52:28 <raildo> sajeesh, great
16:53:24 <sajeesh> raildo,do you have any idea regarding spec freeze dates
16:53:37 <sajeesh> I mean for nova
16:54:35 <raildo> the FeatureProposalFreeze(spec) is march, 5 and the FeatureFreeze (implementation) is march, 19
16:54:55 <sajeesh> ok
16:55:50 <raildo> but that will be great that we have this spec approval for kilo-1, dec 18 :)
16:56:04 <sajeesh> true :-)
16:56:28 <raildo> so, the time is over... thanks a lot!
16:56:41 <raildo> #endmeeting