20:01:30 <sdake> #startmeeting kolla
20:01:31 <openstack> Meeting started Mon Dec  1 20:01:30 2014 UTC and is due to finish in 60 minutes.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:01:32 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
20:01:35 <openstack> The meeting name has been set to 'kolla'
20:01:40 <sdake> howdy folks
20:01:46 <rhallisey> hey
20:01:47 <daneyon> hi!
20:01:47 <sdake> #topic rollcall
20:01:52 <sdake> \o/ yay:)
20:01:53 <rhallisey> hi
20:02:04 <daneyon> hey
20:02:12 <jpeeler> here
20:02:28 <sdake> #topic milestone #2
20:02:57 <sdake> IIRC we set the 9th for a release date for milestone #2
20:03:15 <sdake> https://blueprints.launchpad.net/kolla
20:03:42 <sdake> rhallisey does horizon still need code review?
20:03:55 <rhallisey> sdake, it has been merged
20:04:25 <sdake> cluster-vip daneyon?
20:04:30 <sdake> ddin't we decide to move tha to m3?
20:04:37 <sdake> oh nm ;-)
20:04:43 <sdake> kube-swift-container
20:04:47 <sdake> not sure if chmouel is around
20:04:57 <sdake> probably best to move that to milestone #3
20:05:04 <daneyon> I have not started cluster-vip yet. That is for ML3 correct?
20:05:17 <sdake> ya I misread it as 2, but it is indeed 3
20:05:44 <sdake> that leaves sahara
20:05:54 <sdake> I have bad news about that - I had it working and lost my repo
20:06:04 <sdake> but its really easy to knock out again
20:06:13 <sdake> in fact I lost all my repos :(
20:06:22 <daneyon> We still need #link https://github.com/larsks/heat-kubernetes/pull/8 merged to support functional nova/neutron networking.
20:06:25 <rhallisey> :(
20:06:48 <rhallisey> sdake, do you have a testing environment I could borrow?
20:06:49 <sdake> daneyon I'll shoot an emial to larsks
20:07:01 * rhallisey still has no hardware
20:07:02 <sdake> rhallisey I indeed do I'll set you up after the meeting, but atm I need it for sahara
20:07:12 <rhallisey> ok thanks
20:07:28 <sdake> I got a peice of hardware for you, didn't I share the info?
20:07:45 <sdake> lets connect after the meeting
20:07:53 <rhallisey> sdake, ok
20:07:56 <sdake> daneyon is all of the neutron work merged then?
20:08:21 <daneyon> As a follow-on from last week's discussion, it sounds like flannel is recommended by the k8s team. I provided the feedback to larsks and the relevant PR conversation to provide add'l background.
20:08:23 <sdake> I think we need https://review.openstack.org/#/c/133965/
20:08:30 <daneyon> sdake: yes
20:08:43 <sdake> daneyon can yo urebase today?
20:09:12 <sdake> I'll sort out sahara today
20:09:32 <sdake> and release milestone #2 when all the reviews land
20:09:33 <rhallisey> cool
20:09:34 <daneyon> I'll rebase the nova-networking change
20:09:39 <sdake> cool thanks daneyon
20:09:40 <daneyon> otherwise, neutron has been merged
20:09:45 <sdake> sweet !
20:09:50 <sdake> that is really our huge feature this release
20:09:56 <sdake> #topic release notes
20:10:21 <sdake> https://etherpad.openstack.org/p/kolla-2-ann
20:10:55 <daneyon> sdake: we just need to make sure #link https://github.com/larsks/heat-kubernetes/pull/8 is merged. Otherwise none of the networking stuff will work.
20:11:12 <sdake> couldn't peopel manually merge that?
20:12:14 <sdake> https://blueprints.launchpad.net/kolla/milestone-2
20:12:15 <sdake> features
20:12:50 <daneyon> sdake: the other option is to point people to my repo with the merged changes #link https://github.com/danehans/heat-kubernetes/tree/multi_int
20:13:01 <sdake> lets do that
20:13:07 <sdake> we can fork if necessary for a short time
20:13:12 <sdake> can you alter the text in the etherpad
20:13:19 <daneyon> sure
20:18:03 <sdake> sorry for the long delay
20:18:06 <sdake> looking pretty good now?
20:18:23 <daneyon> so far, so good.
20:18:27 <sdake> cool
20:18:31 <sdake> #topic open discussion
20:18:44 <sdake> I'd like to st art out with future plans around holidays
20:18:56 <sdake> I pretty much expect everyone will be shutdwon from about now until Jan 5th or so ;-)
20:19:04 <sdake> If I could, I'd take it as pto, but  Ican't :(
20:19:16 <daneyon> just so i understand, the m2 release is 12/9?
20:19:17 <sdake> so I suggest we hold off on a milestone #3 release
20:19:34 <sdake> daneyon I think that is what we said wasn't it?
20:19:37 <sdake> or did we say the 2nd?
20:19:50 <sdake> pretty sure it wa the 9th
20:20:17 <sdake> lets just set it as the 9th
20:20:18 <daneyon> I'm fine with the 9th. I wouldn't actually mind being able to test the neutron stuff a little more.
20:20:20 <rhallisey> sdake, I'd rather do the 9th just so we have time to tighten up everything
20:20:27 <sdake> sounds good
20:20:35 <sdake> there is no rush, 16th is almost too late tho
20:20:37 <sdake> so 9th is a good date
20:20:42 <rhallisey> agreed
20:21:04 <sdake> but as for milestone #3, I think we should look at setting that when we have our Jan 5th meeting
20:21:26 <sdake> we should likely cancel the meetings for the 15th, 22nd, and 29th unless folks are opposed
20:21:53 <daneyon> +1 to 1/5 release planning and meeting cancelations
20:22:09 <sdake> rhallisey jpeeler wfu?
20:22:27 <daneyon> sdake: do you want to update the meeting wiki so all others are aware of the shutdown?
20:22:30 <jpeeler> sdake: yep
20:22:36 <jpeeler> +1
20:22:39 <rhallisey> sdake, where is the link to m3
20:22:40 <sdake> daneyon I will do that after the meeting thanks for the suggestion
20:22:48 <daneyon> sdake: thx
20:23:14 <sdake> rhallisey https://launchpad.net/kolla/mliestone-3
20:23:39 <rhallisey> sdake, I'd like to be able to have the m3 blueprints around just in case I can make some progress
20:23:43 <sdake> https://blueprints.launchpad.net/kolla
20:23:50 <sdake> ya feel free to work on st uff during the holidays ;)
20:23:54 <rhallisey> ah there they are
20:23:54 <sdake> I am sure I will be working on something
20:24:02 <rhallisey> works for me then
20:24:04 <jpeeler> sdake: i recently found this project: https://git.openstack.org/cgit/stackforge/dox . i believe it's exactly what i was thinking as far as how we should be testing our work
20:24:42 <sdake> interesting
20:24:50 <sdake> we definately need to tackle testing
20:24:52 <sdake> we don't have any atm
20:24:54 <sdake> which is not ideal
20:25:13 <rhallisey> chmouel, is working on swift container maybe he can also help on that front
20:25:24 <sdake> oh i wanted to bring something else up
20:25:54 <sdake> some folks want to use a PID-less namespaced docker to provide upgrades of nova/libvirt without destroying kvms on the hardware
20:26:22 <sdake> in other words, the container is a packaging tool for upgrades for nova-compute
20:26:50 <sdake> imain (community guy) is working on this, so I would expect he may start attending these meetings
20:27:04 <sdake> just a fyi - seems inline with our charter
20:27:06 <sdake> any objections?
20:27:35 <sdake> cool
20:27:39 <sdake> ok well I don't have anything else
20:27:44 <daneyon> no objections
20:27:55 <sdake> I'll leave channel open for a few minutes if anyone else has htings they want to chat about ;)
20:28:54 <daneyon> In case you did not see this #link https://coreos.com/blog/rocket/
20:29:09 <daneyon> CoreOS is building a container runtime
20:29:34 <sdake> I think the ybuilt it actually:)
20:30:13 <daneyon> I don't envision us supporting OS in Rocket containers any time soon, but I think it's worth keeping an eye on for kolla and magnum
20:30:24 <rhallisey> cool
20:30:28 <sdake> yup agree
20:30:45 <sdake> got pushback on supporting centos for a container, so if we can't handle that, don't think we can handle an entire new container packaging format ;-)
20:31:14 <jpeeler> yeah not currently, but it is certainly interesting
20:31:46 <daneyon> sdake: right on. Just mkaing the group aware of it. If it gains momentum, maybe it's something we consider longer-term.
20:31:57 <sdake> yup wfm
20:32:53 <sdake> ok well I guess we can wrap up
20:32:55 <sdake> thanks folks
20:32:57 <sdake> #endmeeting