16:01:47 #startmeeting kolla 16:01:47 Meeting started Wed May 13 16:01:47 2015 UTC and is due to finish in 60 minutes. The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:48 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:52 The meeting name has been set to 'kolla' 16:01:57 #topic rollcall 16:02:10 hi 16:02:14 o/ 16:02:15 hey 16:02:33 hi 16:03:04 we will wait a few minutes for others to join in 16:03:07 since the meeting change may have thrown people :) 16:04:01 ok 16:04:21 o 16:04:25 hey fang 16:04:28 ok lets get rolling 16:04:34 #topic agenda 16:05:04 #link https://wiki.openstack.org/wiki/Meetings/Kolla#Agenda_for_next_meeting 16:05:06 anyone have anything to add to the agenda? 16:05:43 #topic announcements 16:05:54 looks good to me 16:06:04 our most important announcement is that stable/kilo, stable/juno, and stable/icehouse have branched 16:06:14 and stable/kilo works like a champ - yay team :) 16:06:26 nice job 16:06:28 yay!!!!!!! 16:06:43 we have really come a long far way since milestone #2 when we were rolling on kubernetes 16:06:44 nice 16:06:53 I hope folks feel as good as I do about the change in direction 16:06:54 woohoo 16:07:23 announcement #2, the Thanks Docker! talk has about 270 people signed up 16:07:34 the room has capacity for 360 people 16:07:49 there is about 6k people that attend the openstack conference 16:08:04 so I expect the room will e packed 16:08:04 get there early ;) 16:08:23 we are doing a live demo of kolla 16:08:25 using heat 16:08:34 so pretty much the entire stack except magnum 16:08:40 the talk will be rockin 16:09:28 announcement #3, for folks that are Kolla developers, I'm planning a get together dinner Monday night 16:09:36 my tuesday/wed are booked, so monday is the best I can do :) 16:09:49 you dont have to be core to attend 16:09:58 reviewers/committers welcome 16:10:27 @thesizzler 16:10:34 announcement #4, (last one:) 16:10:34 haha sizzler 16:10:37 :-O 16:10:44 It will be some place nice ;) 16:10:53 If your interested in attending email stdake@cisco.com plz ;) 16:11:07 k announcement 34 16:11:08 #4 16:11:17 we have a slot during ansible community day on monday 16:11:35 I plan to use this slot to gather requirements for what people would like to see out of our ansible container deployment tool 16:11:45 hold for link 16:11:54 actually I don't have a link yet 16:11:58 hold for info ;) 16:12:14 * rhallisey holds 16:12:28 Monday 16:40-17:30 16:13:09 ya I don't have the room number I am full of fail :) 16:13:18 I'll announce on the mailing list under the [kolla] tag 16:13:23 expect to see the cores there :) 16:13:34 and anyoen else interested 16:13:36 will do 16:13:45 Anyone from the community have announcements? 16:14:27 #topic continuous integration 16:14:34 jpeeler your up ;) 16:14:56 if you haven't seen the review - it's here: https://review.openstack.org/#/c/168598/ 16:15:32 as i was talking about earlier in #kolla, i'd like it to be finalized with a tox target of actually deploying the environment. but there are some patches that aren't completed yet. 16:16:01 i'm thinking that at this point it's best to go ahead and merge what's there, which would allow us to at least gate on image building verification 16:16:18 and then interate on the full functional testing 16:16:20 thoughts? 16:16:21 cool image gating would be a spectacular first start 16:16:27 good start 16:16:33 glad this is coming around 16:16:34 for functional testing, are you thinking tempest? 16:16:35 or something else 16:16:55 what would be handy is to run the functional tests of each project 16:17:04 since each project has functional tests built in now 16:17:04 sdake: i haven't looked at tempest in a long time, but the heat project had great difficulty when doing down that path 16:17:08 so we don't have to write them 16:17:39 i have a very simple example test to functionally test using the keystone API 16:17:41 what I want to avoid is writing a bunch of functional tests for things like launching vms, testing network operations, etc 16:17:52 those should belong in individual projects 16:18:04 I think keystone should have its own functional test suite in its codebase and this is probably the case 16:18:28 thoughts? 16:18:46 +1 on taking advantage of tests within each project. 16:19:06 but we need test the system deploy by kolla 16:19:14 if we didn't lanch a vm 16:19:25 the nova functioanl tets I'm sure launch vms :) 16:19:56 perhaps someone can take an action item to determine if there are functional tests we can use in the individual projects 16:20:05 e.g. check out their repo and run their functional test suite 16:20:13 against the kolla deployed system after images are buitl 16:20:38 so the action is to determine which of the projects we implement have functional tests 16:20:55 i'd be in favor of having a "smokescreen" to be able to quickly verify our deployment though 16:21:04 jpeeler +1 16:21:06 if you look at the keystone test 16:21:12 maybe we need two gates 16:21:14 https://review.openstack.org/#/c/168598/12/tests/test_keystone.py,cm 16:21:19 one nonvoting full functional gate 16:21:24 and one voting smokescreen 16:21:35 it's really easy to write these tests to get some idea of non-broken functionality 16:21:50 ok lets have a vote on that model 16:21:59 +1 = two gates, -1 = don't lilke two gates 16:22:00 +1 16:22:30 +1 16:22:35 +1 16:22:44 +1 16:22:52 sounds unanimous (for those here;) 16:23:05 ok so jpeeler proceed with the smokescreen 16:23:20 after smokescreen gate is running and operational we can revisit the full functional test gate via checking out the repos etc 16:23:29 sounds good? 16:23:40 it does, except first we'll get image buildling in the gate 16:23:46 then the smokescreen stuff, right? 16:23:49 right 16:23:51 sounds good 16:23:55 just planning ahead 16:24:00 alrighty 16:24:11 ok that shoudl do it for ci 16:24:16 anyone have any other comments? 16:24:33 i was hoping once the groundwork is done, people can help with the mini client tests 16:24:51 sounds fair 16:24:55 sounds good 16:25:00 ok cool, that's all 16:25:14 #topic Ansible Collaboration Day prep 16:25:24 Ok so we have 1 hour 16:25:34 i'd like to run the session like a design session 16:25:35 where we can gab about our requiremetns 16:25:48 "so we can take the requirements from the customers to the engineers" 16:26:03 makes sense 16:26:04 * sdake has never beat down a printer btw 16:26:34 for prep, it would be handy if we had a list of subjects to discuss during the session 16:26:58 etherpad it now? 16:27:04 https://etherpad.openstack.org/p/ansible-kolla 16:27:04 bingo 16:27:10 like magic 16:27:12 ok guys, get writing for 5-10 minutes plz :) 16:32:13 fangfenghua any chancey ou can add to the etherpad ? :) 16:36:58 make sure to name yourselves in the upper right hand corner so people know who wrote what ;-) 16:37:42 cool well we got more out of that then I expected ;) 16:37:52 thatshould be plenty to get an hour of conversation going ;) 16:37:59 i'm not familiar with osad 16:38:20 its an ansible deployment tool using lxc and fat conainers (runs full init, getty etc) 16:39:40 #topic open discussion 16:40:21 boy etherpad rocks - it multiples 5 brains into 20 ;) 16:40:45 any open discussion folks want to have? 16:41:40 does anyone know what time the tripleo session on kolla is? 16:41:46 no 16:42:47 i'll figure that out and send out an email with the relevant rooms/times of kolla sessions so folks have it in one place 16:43:00 I look forward to seeing those of you that can attend summit there :) 16:43:19 please remember if your interested in a monday 7pm dinner please contact me stdake@cisco.com 16:44:04 #endmeeting