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