22:00:38 <sdake_> #startmeeting kolla
22:00:39 <openstack> Meeting started Wed Jul  1 22:00:38 2015 UTC and is due to finish in 60 minutes.  The chair is sdake_. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:00:40 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:00:43 <openstack> The meeting name has been set to 'kolla'
22:00:48 <sdake_> #topic rollcall
22:00:52 <harmw> 0/
22:00:54 <mstachow> olla !
22:01:00 <sdake_> o/ sorry for the typo there folks :)
22:01:02 <mfalatic> o/
22:01:03 <mandre> here o/
22:01:05 <sdake_> keyboard getting warn
22:01:11 <sdake_> worn
22:01:50 <jpeeler> hey
22:02:08 <sdake_> i'll give it couple more mins for stragglers ;)
22:02:29 <harmw> mstachow: shouldn't you be in bed? :p
22:02:45 <mstachow> and You ;) ?
22:02:50 <harmw> :P
22:02:55 <sdake_> #topic announcements
22:03:06 <harmw> L1! woohoo
22:03:18 <sdake_> midcycle information is avilable now: https://wiki.openstack.org/wiki/Sprints/KollaLibertySprint#Cisco_Specifics
22:03:35 <sdake_> rather
22:03:37 <sdake_> #link https://wiki.openstack.org/wiki/Sprints/KollaLibertySprint
22:03:45 <sdake_> I'll flesh that page out as I get more details
22:03:51 <sdake_> please book your travel if you intend to attend ;)
22:04:11 <sdake_> note bay area hotel rates will crank up over next couple weeks, so please please book your hotels now
22:04:20 <sdake_> we have room for 25 seats
22:04:31 <sdake_> i'll send out eventbrite info later today
22:04:49 <sdake_> if you can't make it because of budget issues, pleae mark the time in your calendar for remote participation
22:04:56 <harmw> I won't be attending in person
22:05:00 <sdake_> would like to see as many folks there as possible either remote or local
22:05:13 <sdake_> harmw ya it will be hard for non-us citizens to make it to the summit because of the timelines
22:05:24 <sdake_> we have alot of work to do in teh midcycle
22:05:26 <harmw> various reasons, but yes
22:05:32 <sdake_> I'm not sure if we will always have a midcycle
22:05:40 * mstachow happy because of remote participation !
22:05:43 <sdake_> but right now we have many unanswered questions that a good face to face meeting can fix :)
22:05:50 <harmw> yea
22:06:00 <sdake_> now I should warn, the remote participation will be pretty terrible ;)
22:06:00 <sdake_> it may be mostly one way unfortunately
22:06:10 <sdake_> its really hard to get a word in edgewise on the computer
22:06:15 <sdake_> with a room full of people talking
22:06:16 <harmw> we'll see how it rolls
22:06:30 <sdake_> second announcement
22:06:33 <sdake_> liberty-1 was released couple days ago
22:06:36 <sdake_> it all seemed to work for me
22:06:41 <sdake_> heat seems a bit buggy
22:06:45 <sdake_> but working
22:06:53 <sdake_> for example the heat demo deosn't work properly
22:07:00 <sdake_> also horizon is completely busted
22:07:04 <sdake_> it would be cool if someone could fix that :)
22:07:19 <harmw> and thanks for everyone rushing out all those fixes in such a limited window!
22:07:25 <harmw> horizon was upstream, right?
22:07:27 <mandre> do we have bugs logged for all the things you mentioned?
22:07:35 <sdake_> yes there are bugs
22:08:00 <sdake_> so we went from 35 bugs at release announcement creation time to 60 bugs at release
22:08:02 <sdake_> that meanss our ci needs some serious love
22:08:04 <harmw> yea, I think most if not all issues were logged in our own LP
22:08:07 <sdake_> #topic continuous integration
22:08:29 <harmw> single nic, period
22:09:35 <sdake_> ok well before we can do single nick we need internal config of openvswitch working
22:11:53 <sdake_> any taers?
22:12:11 <harmw> there is work underway on that right?
22:12:16 <sdake_> nobody owns it
22:12:19 <harmw> hm
22:12:35 <harmw> I could just take a look
22:12:48 <sdake_> ok this should come behind that other work we talked about today harmw
22:12:48 <harmw> isn't this something Sam wanted to tackle?
22:12:55 <harmw> yep
22:13:01 <sdake_> sam tackled external config
22:13:01 <sdake_> and then didn't do internal config
22:13:07 <sdake_> now he wants someone else to do internal config i guess
22:13:12 <sdake_> we ar egating on internal config to begin
22:13:14 <harmw> it's on my list anyway, to do something with openvswitch :)
22:13:30 <sdake_> cool harmw can you make a blueprint
22:13:33 <harmw> ok, assign me
22:13:40 <sdake_> ok i'll make a blueprint
22:14:02 <sdake_> #topic liberty-2 planning
22:14:16 <sdake_> #link https://launchpad.net/kolla/+milestone/liberty-2
22:14:33 <sdake_> please open that up
22:14:48 <harmw> tempest! wanted to say that in terms of the previous item :)
22:15:05 <sdake_> harmw I htink jpeeler will tackle that
22:15:07 <harmw> I'm seeing tons of new containers
22:15:25 <sdake_> lets focus on one problem at a time - which is the aio networ
22:15:30 <sdake_> and tempest next
22:15:42 <sdake_> so lots of started blueprints
22:15:44 <sdake_> yay ;-)
22:15:49 <sdake_> our deadline is July 31
22:15:53 <sdake_> or midcycle is 28,29th
22:16:00 <sdake_> or/our
22:16:21 <sdake_> so our midcycle will define what work we do for the remainder of liberty
22:16:39 <harmw> yep, though there is something on that list already
22:16:41 <harmw> for L3
22:16:48 <sdake_> where
22:17:02 <sdake> which item
22:17:04 <harmw> https://launchpad.net/kolla/+milestone/liberty-3
22:17:09 <sdake> oh ya
22:17:15 <sdake> i just push stuff out there that isn't in l2
22:17:20 <sdake> i should probably move that to l2
22:17:24 <sdake> i don't even know whats in l3 atm
22:17:31 <sdake> oh its ironic probably - jpeleer said he is doing in l3
22:17:32 <sdake> not in l2
22:17:39 <harmw> :)
22:17:48 <sdake> in terms of priorities, I think we have
22:17:51 <sdake> 1. Make ansible work properly
22:18:04 <sdake> 2. Make from source install work properly
22:18:16 <sdake> 3. Make HA containers work properly
22:18:17 <harmw> shoudln't 2 be: multinode?
22:18:30 <sdake> underlying these 3 main priorities is ci
22:18:31 <sdake> harms 1 = multinode bro
22:18:38 <harmw> oh ok
22:19:07 <sdake> does anyone see a different set of priorities we should have?
22:19:12 <mandre> seems good
22:19:22 <mstachow> +1
22:19:25 <harmw> maybe putting HA first?
22:19:38 <sdake> ansible is definately first
22:19:44 <sdake> since it givs multinode
22:19:45 <sdake> to test ha
22:19:49 <harmw> sdake: excuse me, ansible is #1 period
22:19:51 <sdake> we can swap src and ha, i'm good with that change
22:19:58 <harmw> I meant HA in favor of source
22:20:21 <harmw> would our users benefit from source based, our would that affect only us developers?
22:20:38 <harmw> (which is good as well, but targets a different audience)
22:20:40 <sdake> ok vote of A = sdake's priority vote of B = harmw's priority vote of -1 is different priority
22:20:42 <sdake> please vote
22:20:55 <mstachow> A
22:20:56 <mandre> agreed HA should have higher priority than source install
22:20:57 <nihilifer> A
22:21:03 <mandre> B for me
22:21:03 <harmw> B
22:21:19 <sdake> ya i think ha is higher prior then src
22:21:26 <sdake> so B
22:21:37 <jpeeler> i kind of liked A...
22:21:40 <sdake> seems like we don't really have the entire team here to make a consensus on it
22:21:41 <sdake> lets just put it this way
22:21:50 <sdake> we need to get all 3 done in liberty 2
22:22:01 <harmw> yea, whats in a month anyway :)
22:22:30 <jpeeler> that consensus topic reminded me about something for open discussion
22:22:36 <sdake> we are going to go over a few blueprints
22:22:39 <mandre> the month of july harmw…
22:22:42 <sdake> #link https://blueprints.launchpad.net/kolla/+spec/standard-start
22:22:48 <sdake> harmw can you give us an update on this blueprint
22:22:58 <sdake> with relevant links for those to catch up
22:23:14 <harmw> yea, it's been drafted quite recently so work has yet to take off
22:23:39 <sdake> would you mind linking the etherpad
22:23:57 <harmw> we're dividing containers between several devs, this has been listed on https://etherpad.openstack.org/p/kolla-standard-start
22:24:31 <harmw> a separation has been made into two distinct groups of containers, as to where to target our focus first
22:24:58 <harmw> I'll be adding Glance tomorrow, which can serve as base (well...) for the others
22:25:25 <harmw> comments on that epad are, as always, appreciated
22:25:39 <sdake> cool so looks like that is mostly covered by assignees
22:25:50 <sdake> the reason harmw is reporting out is he is the asignee on the blueprint
22:26:00 <sdake> which means he is responsible for wrangling the status
22:26:09 <sdake> i'll still be responsible for wrangling the blueprints overall :)
22:26:18 <harmw> next week I hope to report real progress on this :)
22:26:47 <sdake> #link https://blueprints.launchpad.net/kolla/+spec/ansible-service
22:27:00 <sdake> harmw I hope your done by next week ;-)
22:27:06 <sdake> this is adding the ansible framework to each of the services
22:27:11 <sdake> samyaple is out so I'll report the status
22:27:26 <harmw> with an epad as well: https://etherpad.openstack.org/p/ansibalising-containers
22:27:33 <sdake> #link https://etherpad.openstack.org/p/ansibalising-containers
22:27:42 <sdake> thsi one doesn't have alot of assignees
22:27:54 <sdake> if your looing to contribute assign yourself as a contributor please
22:28:02 <sdake> mandre would love for your involvement here ;)
22:29:11 <sdake> I am going to leave the midcycle planning until next week
22:29:15 <mandre> i'll add my name to some of the containers
22:29:20 <sdake> because that meeting has better attendeance
22:29:22 <sdake> thanks mandre
22:29:35 <sdake> #topic open discussion
22:29:52 <sdake_> #topic open discussion
22:30:04 <harmw> there was a recent discussion on the ML regarding meetingtimeslot
22:30:12 <harmw> the slot for next week
22:30:51 <sdake_> ok well I am not changing next week's slot
22:30:53 <harmw> was there concensus on moving from 16:00 to 16:30 ?
22:31:00 <sdake_> but I can change 3 weeks slot around
22:31:00 <sdake_> and see what happens
22:31:12 <harmw> not next week, sure, but that weeknmbr
22:31:17 <harmw> you know, odd/even :)
22:31:20 <sdake_> right
22:31:33 <sdake_> ok well i'll change it, and we will see if people complain
22:31:39 <harmw> great
22:31:40 <sdake_> meetings on the half hour are harder to remember ;(
22:31:54 <sdake_> jpeeler you said you had something for open discussion?
22:31:56 <harmw> we'll see what happens
22:32:10 <jpeeler> i was just wondering if  anybody felt like we rely on IRC more than we should in contrast to using the mailing list? or perhaps this is just a natural progression as the project continues to develop
22:32:34 <sdake_> i would really like to see more ml usage
22:32:39 <sdake_> but I think our usage of irc is fantastic!
22:32:48 <harmw> jpeeler: in what kind of way?
22:32:54 <mandre> and now our irc channel is logged anyway
22:33:00 <sdake_> the nice thing about ml usage is that it shows people its not just me out there
22:33:17 <jpeeler> harmw: i just feel like we make a lot of decisions on IRC rather than taking it to the list
22:33:20 <sdake_> if they join our irc channel at 1am they will see a whoel bunch of contribs that have never posted on the ml
22:33:30 <sdake_> jpeeler agree
22:33:32 <harmw> jpeeler: true
22:34:23 <mfalatic> Mailing lists tend to be better for larger discussions (things that may span days or weeks of back and forth, like architecture)
22:34:23 <harmw> but isn't this in a some way 'our game' then? forgive me if I'm way off though
22:34:30 <sdake_> jpeeler do you have suggestions to improve things
22:34:54 <mfalatic> Perhaps it's an outgrowth of greater complexity that drives such discussions naturally to mailing lists.
22:35:03 <jpeeler> well first i just wanted to see if people agreed and then if so, we can just make more of an effort to do so
22:35:45 <sdake_> well I think we should use the ml more
22:35:46 <harmw> are other folks on the ML in some way affected by our lack of ML usage btw?
22:35:49 <sdake_> but I don't know how to encourage it
22:36:00 <sdake_> harmw YES
22:36:10 <sdake_> harmw they have to read irc logs to see how decisions are made
22:36:13 <sdake_> which  they wont do
22:36:14 <mandre> jpeeler, agreed, it's nice you bring this up
22:36:15 <jpeeler> IRC logs tend to be litered with lots of fluff - no offense to anybody!
22:36:23 <harmw> jpeeler: fully agree on that
22:36:29 <harmw> log reading sucks
22:36:31 <mfalatic> IRC logs are a PITA to read.
22:36:31 <sdake_> ya like steak talking about his new audio gear ;)
22:36:40 <harmw> yep
22:36:41 <mfalatic> Yeah! Wait...
22:36:55 <harmw> so, what's the last decision we've made?
22:37:08 <sdake_> good q harmw
22:37:14 <sdake_> jpeeler got any examples ;)
22:37:23 <mfalatic> Logs come in handy sometimes, but they're generally not a good way to keep up with an intricate or ongoing architectural debate.
22:37:23 <jpeeler> well making decisions here in the official meeting log is fine
22:37:33 <jpeeler> but perhaps discussion the priorities on the ML would have been good
22:37:38 <sdake_> this meeting is constrained to 4 hrs a week
22:37:41 <sdake_> irc is 24 hours a day
22:37:46 <sdake_> 4 hrs a month i mean
22:38:03 <sdake_> irc meeting is for our highest prioirty topics of discussion
22:38:06 <sdake_> ml medium priority
22:38:08 <sdake_> irc low priority
22:38:10 <sdake_> imo ;)
22:38:17 <mfalatic> email is 24x7 but allows greater participation IMHO, when consensus en masse counts.
22:38:22 <harmw> so all is either high or low :>
22:38:38 <mstachow> so we should set more medium priorities imo
22:38:49 <sdake_> our irc meeting is 4 hours a month but our irc time is 24 hrs a day
22:39:03 <harmw> which we actually make good use of
22:39:24 <sdake_> hey pdb ;)
22:39:30 <pdb-mobile> Hi
22:39:39 <pdb-mobile> Hmm, am i late
22:39:43 <pdb-mobile> Or early
22:39:51 <sdake_> well if someone thinks i have the priorities wrong feel free to correct them ;-)
22:39:54 <harmw> perhaps we could settle on deciding what to put to the ML when the next decision has to be made
22:40:10 <harmw> or something like that
22:40:20 <sdake_> a good topic for ml is something that crosses time boundaries
22:40:30 <sdake_> that could take multiple days to figure out as mfalatyc pointed out
22:40:42 <jpeeler> i tend to think of the ML as more of an archive
22:41:04 <sdake_> the irc meetings are archived
22:41:07 <sdake_> the irc logs are archived
22:41:10 <sdake_> everything is archived
22:41:17 <jpeeler> a readable archive :)
22:41:34 <sdake_> readable lol :) clearly you dont read the ml very often ;)
22:41:37 * mstachow is thinking: is archive archived?
22:41:51 <sdake_> ok well i'm all for using the ml more
22:42:06 <mfalatic> Archive is printed using a pin-fed line printer on triplicate paper.
22:42:08 <sdake_> lets all make an effort when discussing changes in architecture that span multiple days worth of discussion to do it on irc
22:42:15 <sdake_> minus those that are done via our god awful specs process
22:42:35 <harmw> don't you mean the ML there?
22:42:36 <jpeeler> i assume you meant ML there
22:42:44 <sdake_> ya ml
22:42:45 <sdake_> sorry
22:42:57 <harmw> cool
22:43:16 * jpeeler is done with that
22:43:16 <sdake_> ya folks it would really hlpe our project grow as well to see us conversing on the mailing list
22:43:30 <sdake_> part of how projects are measured is by a term called "engagement"
22:43:31 <harmw> exposure
22:43:38 <sdake_> engagement is measured by ml participation
22:43:46 <sdake_> almost exclusively
22:43:55 <harmw> hm, can't say I like that but ok
22:44:00 <sdake_> even though our engagement imo is measured by our irc logs which are quite long each day :)
22:44:06 <sdake_> harmw ya its backwards
22:44:06 <harmw> indeed
22:44:24 <pdb-mobile> Ml is useful
22:44:51 <pdb-mobile> Focused streams of conversion you can choose to track or ignore
22:45:24 <pdb-mobile> Easier to miss important stuff on irc
22:45:33 <harmw> so true
22:45:50 <harmw> more topics?
22:45:52 <mandre> ML is also an invitation for other devs to get involved in the project
22:46:17 <sdake_> ya we beat that one into the ground
22:46:44 <sdake_> hey nih*
22:46:52 <sdake_> any other open topics for discussion
22:47:00 <harmw> https://etherpad.openstack.org/p/kolla-summit-talk-proposals
22:47:00 <sdake_> or shall we conclude the meeting?
22:47:12 <harmw> if anyone has input on that, your welcome to add
22:48:20 <harmw> some reasoning: there was recent talk in #kolla about interesting stuff to talk about, now I don't know if this was regarding midcycle or summit, but the etherpad may be used to keep track of what could be of interest
22:48:42 <sdake_> harmw we wil lhave midcycle planning next wendesday
22:48:58 <harmw> it wasn't much talking btw, more enthusiasm :)
22:49:00 <sdake_> if you want to do a talk at summit id' suggest keeping it secret until yo submit it so somoene doesn't jack your ideas ;)
22:49:10 <harmw> I'm not talking, lol
22:49:17 <sdake_> daneyon and I are doing one
22:49:43 <sdake_> it would be interesting t osee a talk on someone that is a downstream of olla using kolla in deployment products
22:49:58 <harmw> probably to soon for that, but yes
22:50:00 <sdake_> so for those that watch the logs after, tr yto think how to get that sort of talk into summit :)
22:50:12 <sdake_> the deadline is july 15th for summit proposals
22:50:47 <sdake_> but tose are 40 minute talsk, like what daneyon and I gave at summit
22:50:53 <sdake_> anyway lets not mix things up too much :)
22:51:07 <sdake_> if you want to do that, recommend working together - 2 people in a talk wor well together
22:51:11 <sdake_> any other subjects?
22:51:30 <sdake_> on that note, please book your travel for summit
22:51:31 <harmw> opionions on Q/A for coding, or should we skip on that for now?
22:51:38 <sdake_> reference the sprints page for travel info
22:51:49 <sdake_> harmw lets do that at midcycle
22:51:55 <sdake_> that is a perfect midcycle discussion topic
22:51:57 <harmw> perhaps best
22:52:00 <harmw> yea
22:52:36 <sdake_> ok, rememeber, priority #1 - Anisbleize Kolla
22:52:39 <sdake_> lets get cracking!
22:52:41 <sdake_> #endmeeting