18:57:07 <davidlenwell> #startmeeting refstack 18:57:08 <openstack> Meeting started Mon Apr 27 18:57:07 2015 UTC and is due to finish in 60 minutes. The chair is davidlenwell. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:57:09 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:57:13 <openstack> The meeting name has been set to 'refstack' 18:58:17 <Rockyg> o/ 18:59:25 <davidlenwell> 1) Refstack PTL election 2) Vancouver cross team design session 3) Recap last week agreements 4) Plan for Refstack to demo to DefCore on May 6 5) pending reviews 6) open discussion 18:59:46 <hogepodge> o/ 18:59:55 <catherineD> o/ 19:00:21 <pvaneck> o/ 19:00:26 <davidlenwell> #topic Refstack PTL election 19:00:38 <davidlenwell> We as a project have grown from just a few people hacking on this code in our spare time to a fully functional upstream project.. that means that we have to behave like the other projects do and have elected governance.. So Its time to have a PTL election. 19:01:21 <davidlenwell> After much introspection and thought.. I've decided to take my name out of the running and instead nominate and fully support Catherine Diep to replace me in this post.. 19:02:37 <sslypushenko__> o/ 19:02:44 <davidlenwell> Elections will follow the traditional pattern.. If anyone else wants to run for PTL please inform the group this week. 19:03:17 <Rockyg> ++ Thanks for all your hard work, davidlenwell. We've really gotten a lot done and will be able to have a respectable demo backed up by *real* working code 19:03:28 <davidlenwell> We will orginize voting through the propper channels 19:04:53 <davidlenwell> I intend to stay an active member of the team and be a part of bringing our vision to life. But I feel the time is right to give someone else the reigns for a term. 19:05:03 <catherineD> davidlenwell: You will still be active with Refstack as a technical core reviewer right /// 19:05:08 <davidlenwell> yes 19:05:12 <vladiskuz|2> o/ 19:05:12 <catherineD> ++1 19:05:27 <davidlenwell> any questions? concerns? any other candidates? 19:05:33 <edleafe-> o/ 19:06:32 * edleafe- is just here, not a candidate! 19:06:49 <davidlenwell> thanks for clearing that up edleafe- 19:07:21 <davidlenwell> anyways .. put some thought into it.. We're actually late .. so this will be considered a special election.. 19:07:25 <Rockyg> will you be posting the election info, canditate(s), etc to the dev list? We need to start doing that. 19:08:04 <Rockyg> Do you think we can abandon fits and start using dev? 19:08:10 <davidlenwell> if nobody else is going to run.. then catherine will be running unopposed and we don't have to be as formal about it. 19:08:21 <Rockyg> kewl 19:08:37 <davidlenwell> but I wanted to give others time to think if over and throw a hat in the ring.. 19:09:10 <davidlenwell> So we'll set a deadline of next meeting to nominate yourself or another individual.. if nobody pops up then we'll just make it official and bypass the voting process 19:09:19 <Rockyg> no freakin' way would I run against CatherineD ;-) 19:09:32 <catherineD> Rockyg: :-) 19:09:41 <davidlenwell> she's the best fit for the job 19:09:47 <davidlenwell> in my humble opinion 19:09:51 <sslypushenko__> +1 19:10:04 <davidlenwell> anyways ..we'll revisit in a week. 19:10:07 <vladiskuz|2> ++ 19:10:08 <catherineD> davidlenwell: thanks 19:10:09 <davidlenwell> lets move on for now.. 19:10:13 <davidlenwell> #topic 2) Vancouver cross team design session 19:10:37 <davidlenwell> did anyone add us to the list of q/a topics ? because I believe the deadline has passed. 19:10:41 <catherineD> so I enter one topic in https://etherpad.openstack.org/p/refstack-qa-vancouver-design-session 19:11:03 <catherineD> after we review here ... I will add that in the list of q/a topics ... 19:11:18 <davidlenwell> I think we've already passed their deadline to submit 19:11:18 <catherineD> please take a look at https://etherpad.openstack.org/p/refstack-qa-vancouver-design-session 19:11:58 <catherineD> hogepodge: mentioned last week that May 30 is the last day .. 19:12:07 <davidlenwell> ahh.. okay 19:12:11 <davidlenwell> it needs to be added here.. https://etherpad.openstack.org/p/kilo-qa-summit-topics 19:12:23 <Rockyg> I think we need to recruit a keystone dev or two as liaisons to help with getting testing on outside clouds in good shape. And maybe a keystone test suite. 19:12:55 <davidlenwell> um .. may 30th is after the summit by the way 19:12:59 <davidlenwell> did you mean april 30th? 19:13:08 <Rockyg> That sounds more likely 19:13:13 <catherineD> davidlenwell: yes 19:13:22 <catherineD> April 30 19:13:23 <davidlenwell> okay that makes more sense 19:13:44 <morganfainberg> Rockyg: i'm sure keystone folks could be convinced to discuss helping. 19:14:02 <Rockyg> morganfainberg: cool 19:14:06 <catherineD> should we go ahead adding the topic to the q/a session .. 19:14:11 <davidlenwell> I'm sure we can just informally start talking to them 19:14:17 <morganfainberg> Rockyg: come to our IRC meeting tomorrow, and say something about what you'd like. 19:14:19 <davidlenwell> yes catherineD lets just add it 19:14:23 <morganfainberg> davidlenwell^ cc 19:14:30 <Rockyg> The api test session is also one that the refstack team needs to participate in 19:14:37 <catherineD> ok will add it ... 19:14:43 <morganfainberg> Rockyg: toss something on our agenda. most eyes will be available there. 19:14:50 <davidlenwell> morganfainberg and Rockyg we don't need a design session for that .. we can just raise our hands and speak up about our needs 19:15:03 <morganfainberg> davidlenwell: start talking to us before the summit :) 19:15:07 <davidlenwell> yes 19:15:18 <davidlenwell> Rockyg: do you want to take that on? 19:15:23 <Rockyg> morganfainberg: I'll try to be there tomorrow. Might try to get on the agenda 19:15:33 <Rockyg> davidlenwell: I guess so ;-) 19:15:41 <davidlenwell> thank you! 19:15:47 <davidlenwell> so 19:15:53 <catherineD> sslypushenko__: and hogepodge: do we need a session to reserve time for the UUID topic ? 19:15:53 <morganfainberg> Rockyg: just add yourself to the agenda. if you don't show up, we can defer to a following week. 19:16:02 <sslypushenko__> Rockyg What kind of issues do we have with keystone? 19:16:03 <Rockyg> k. thanks 19:16:11 <davidlenwell> #agreed catherineD to add our topic to the q/a summit topics here .. https://etherpad.openstack.org/p/kilo-qa-summit-topics 19:16:31 <davidlenwell> sslypushenko__: lets save that for open discussion 19:16:38 <sslypushenko__> ok 19:16:43 <davidlenwell> I want to get throught he rest of the agenda first. 19:16:50 <hogepodge> catherineD: probably, althogh it's going to be tough to advance. we should make a case, though. At least have a chance to have mtreinish explain his reasoning about naming and why it isn't necessary 19:17:03 <Rockyg> sslypushenko__: just getting help maybe for test tools to be better equipped for testing on public clouds. And with expanding test suites to be able to run some keystone tests through the refstack client 19:17:27 <catherineD> hogepodge: so we should log a session so that we have the time slot? 19:17:36 <hogepodge> catherineD: sure 19:17:57 <davidlenwell> no gaurantees that it will be accepted .. but we can speak up and try 19:18:25 <davidlenwell> lets move on.. 19:18:29 <davidlenwell> #topic 3) Recap last week agreements 19:18:42 <davidlenwell> catherineD: can you go through those please? 19:19:04 <catherineD> ok 19:19:11 <catherineD> 1. we will find a time to set aside at the summit to discuss the api in better detail. 19:19:37 <davidlenwell> I think we have had success with breakfast meetings in the past. 19:19:38 <catherineD> I think we can defer that to next week since we have more important items to discuss this week 19:19:59 <davidlenwell> lets tenetively say we'll meet for breakfast early in the week. 19:20:12 <catherineD> ok 19:20:42 <catherineD> #action need to define Refstack team face-2-face meeting at the summit on May 4, 2015 ... pick a day for breakfast early i nthe week 19:21:03 <catherineD> 2) David to follow up with infra team on the possibility for Refstack server hosting at infra 19:21:28 <Rockyg> o/ 19:21:30 <davidlenwell> Rockyg had already picked this back up and krotscheck started to help us with this process 19:21:39 <davidlenwell> however I am not sure what the current status of this is. 19:22:11 <davidlenwell> I reached out to jeblair and let him know what our intentions are.. he offered no objections at this time.. 19:22:14 <krotscheck> ohai 19:22:15 <Rockyg> Yup. pvaneck is working with krotscheck to break out the webserver into its own repository 19:22:34 <davidlenwell> So we should proceed with their recomendations and keep things moving along.. 19:22:38 <krotscheck> Actually, I've reversed positions on that. I don't think it makes sense for refstack. 19:22:39 <mtreinish> hogepodge: we can probably have a work room slot for it 19:22:48 <mtreinish> hogepodge: or if it gets too full the sprint day on friday works too 19:22:56 <mtreinish> oh actually that would probably be a better time for it 19:23:13 <davidlenwell> mtreinish: sounds good 19:23:24 <Rockyg> ok. krotscheck, pvaneck any other update on that? 19:23:42 <davidlenwell> krotscheck: can you elaborate? 19:23:52 <krotscheck> Ok, first the update: 19:24:15 <krotscheck> I'm working on the puppet module, though it took up more of my time than I wanted last week and so paused late last week. 19:24:30 <catherineD> mtreinish: I just add the Password topic to https://etherpad.openstack.org/p/kilo-qa-summit-topics 19:24:43 <krotscheck> There's one major missing piece, which is a wsgi file for refstack 19:24:54 <Rockyg> I think we should have a backup plan just in case. I want to approach the rackspace defcore chair and get a vm as a hot standby 19:24:55 <davidlenwell> krotscheck: I can commit that today 19:25:00 <mtreinish> catherineD: I'm not sure that will require it's own session, but ok :) 19:25:06 <krotscheck> davidlenwell: Cool! 19:25:28 <catherineD> mtreinish: thx 19:25:31 <Rockyg> mtreinish: I think we can expand on the topics ;-) 19:25:34 <krotscheck> Once the puppet module is done, we'll want to add the project under the openstack-infra namespace. 19:26:07 <krotscheck> Once that's done, we can add a manifest to openstack-infra/system-config to create a refstack server. 19:26:15 <krotscheck> Once that's done, you ask infra to provision the server for you. 19:26:22 <krotscheck> And set up the domain name. 19:26:27 <krotscheck> And then you're golden. 19:26:40 <krotscheck> As for the Why-one-project-not-two: 19:26:42 <davidlenwell> Thank you for the update and the help krotscheck 19:27:05 <hogepodge> krotscheck: a few weeks ago piston transferred refstack.org to the foundation, so the staff here can help with the dns 19:27:19 <davidlenwell> oh good! 19:27:25 <krotscheck> The things you get for separate projects: Separability, whitelabeling, etc - you don't really need any of those. 19:27:48 <catherineD> krotscheck: base on your experiences with all the activities .. do you think we we have the server before May 6? 19:28:03 <davidlenwell> catherineD: I would think it will take longer than that 19:28:06 <krotscheck> catherineD: Unlikely. 19:28:07 <catherineD> We plan to demo the Refstack UI to DefCore on that date .. 19:28:25 <davidlenwell> catherineD: we can update the refstack.net server I setup and use it for the demo 19:28:39 <krotscheck> catherineD: At that point you should be able to create a demo VM on the presentation laptop. That'd be a bit more stable 19:28:54 <catherineD> davidlenwell: great ... it is best to have a demo on a public site so people can really access to it ... 19:29:08 <davidlenwell> if we don't have any other agreements to review this is a good segway into our next topic 19:29:24 <krotscheck> im good 19:29:38 <davidlenwell> #topic 4) Plan for Refstack to demo to DefCore on May 6 19:30:41 <davidlenwell> we've decided to demo our progress for the defcore group durring the may 6th meeting.. 19:30:51 <davidlenwell> catherine and I will perform the demo 19:30:59 <catherineD> davidlenwell: so most likely we will use refstack.net for the demo .. 19:31:07 <davidlenwell> agreed 19:31:16 <davidlenwell> I'll get you access to that server asap 19:31:27 <catherineD> davidlenwell: +1 .. 19:31:38 <davidlenwell> #agreed davidlenwell to privide login access for catherine to refstack.net server 19:33:00 <pvaneck> davidlenwell: do you currently use apache on that server to server the api? 19:33:03 <davidlenwell> I think we should prep what we are going to say durring the demo .. highlight progress and longer term goals.. then some q and a to wrap it up 19:33:05 <pvaneck> serve* 19:33:13 <davidlenwell> yes .. I serve the api with apache wsgi 19:33:26 <davidlenwell> I will commit the wsgi file today 19:33:34 <davidlenwell> or tomorrow .. I have a lot of meetings today 19:33:34 <pvaneck> ah okay 19:34:06 <davidlenwell> catherineD: anything to add? 19:34:11 <catherineD> #action David to commit the wsgi file asap 19:34:42 <catherineD> davidlenwell: once I have access we will prep the server ... 19:34:57 <catherineD> nothing else from me for this topic ... 19:35:04 <davidlenwell> okay .. lets move on 19:35:06 <davidlenwell> #topic 5) pending reviews 19:36:18 <catherineD> for https://review.openstack.org/#/c/176364/ 19:37:03 <catherineD> sslypushenko__: is concern about explicit selection of engine ... 19:37:23 <sslypushenko__> I did manual testing for it and it works for me... 19:37:34 <sslypushenko__> About engine... 19:38:03 <sslypushenko__> Is it really necessary to select engine? 19:38:38 <davidlenwell> I don't think its a must.. but we have to be very clear that we are only testing and running this in mysql 19:38:58 <hogepodge> I think it's ok to make a hard decision about what the backend is. 19:39:17 <davidlenwell> +1 19:39:18 <catherineD> so we just need to clarify that in our README? 19:39:45 <hogepodge> yup. It will also be made clear in the puppet deployment manifests 19:40:32 <mtreinish> so realize that's not a backwards compatible change either, if you have existing users that could lead to them being an unknown state 19:40:48 <mtreinish> you should probably do something like that as a new migration instead 19:41:34 <davidlenwell> mtreinish: I believe the only user we have running our api outside of of this group is catherineD at ibm .. 19:42:39 <mtreinish> davidlenwell: sure, that's a project policy decision. But, if you add onto an old migrations just thought the risks of doing it should be brought up 19:43:08 <davidlenwell> okay .. next review .. https://review.openstack.org/#/c/177872/1 19:43:19 <davidlenwell> pvaneck: has been hard at work on our ui code.. 19:43:28 <davidlenwell> I'd like eyes on the javascript 19:43:48 <sslypushenko__> Looks good! 19:44:02 <davidlenwell> and special attention on the readme file pvaneck make sure instructions are easy to get this running. 19:44:15 <hogepodge> Is there a javascript linter that can be added to the gate? Would it be useful? 19:44:40 <pvaneck> Yea, a js gate would be good to have 19:44:57 <mtreinish> hogepodge: heh, jslint. Enjoy that license quagmire :) 19:45:58 <davidlenwell> for the time being lets have a few folks actually run the code and test it manually 19:46:57 <davidlenwell> next .. https://review.openstack.org/#/c/177340/ 19:47:36 <davidlenwell> that one looks good to me.. I've +2'd it 19:47:45 <davidlenwell> catherineD: you can merge if you are happy with it 19:48:06 <catherineD> yes testing it ... shoudl be an easy one to merge .. 19:48:10 <sslypushenko__> This patch should works with https://review.openstack.org/#/c/177357/ 19:48:26 <davidlenwell> yes .. https://review.openstack.org/#/c/177357/ also looks good to me 19:49:51 <davidlenwell> that leaves .. https://review.openstack.org/#/c/177872/ 19:50:26 <davidlenwell> sorry .. meant to paste this .. https://review.openstack.org/#/c/176335/ 19:51:20 <sslypushenko__> Vlad is working on UI part now 19:51:25 <catherineD> that is WIP ... 19:51:47 <davidlenwell> yes .. but its the last remaining pending review so I figured we'd talk about it ;) 19:51:51 <sslypushenko__> We hope that auth will work next week 19:51:59 <davidlenwell> awesome! 19:52:12 <davidlenwell> I will continue to monitor 19:52:21 <davidlenwell> we have a little time left now for open discussion 19:52:29 <davidlenwell> #topic open discussion 19:52:52 <davidlenwell> sslypushenko__: Rockyg did you communicate enough about the keystone topic? 19:53:15 <sslypushenko__> We can do it in #refstack channel 19:53:16 <Rockyg> For this round, yes, I think. 19:53:21 <davidlenwell> okay 19:53:35 <davidlenwell> So who is not going to the summit? 19:53:44 <davidlenwell> vladiskuz|2: and sslypushenko__ you aren't attending right? 19:53:50 <catherineD> sslypushenko__: we merge this one https://review.openstack.org/#/c/161315/ so now the JSON include idempotent_id ... but we are not storing the id in refstack .. 19:54:03 <sslypushenko__> Yes, We are not going 19:54:21 <davidlenwell> we will do our best to include you in team meetings 19:54:46 <sslypushenko__> catherineD We did it. Refstack is storing uuid in db 19:55:04 <sslypushenko__> davidlenwell Thx 19:55:14 <catherineD> sslypushenko__: ok let review some more ... 19:55:16 <davidlenwell> idempotent_id == uuid .. no reason to change tis name in our database 19:55:59 <davidlenwell> if nothing else we'll make a google hangout from my cell phone and invite you guys to it for our team breakfast .. my data plan still works in canada 19:56:02 <hogepodge> it's important to understand that uuid is only unique for function, not for test 19:58:01 <davidlenwell> okay folks.. thats all the time we have for today in this channel .. as always please feel free to keep the conversation going in #refstack! 19:58:18 <davidlenwell> #endmeeting