16:03:58 #startmeeting containers 16:03:59 Meeting started Tue Aug 5 16:03:58 2014 UTC and is due to finish in 60 minutes. The chair is adrian_otto. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:04:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:04:02 The meeting name has been set to 'containers' 16:04:06 o/ 16:04:06 o/ 16:04:13 o/ 16:04:23 #link https://wiki.openstack.org/wiki/Meetings/Containers Agenda 16:04:29 #topic Roll Call 16:04:36 Adrian Otto 16:04:39 Eric Windisch 16:04:50 hi funzo, erw, and s1rp 16:05:00 hi! 16:05:37 #topic Announcements 16:05:50 first, we had the Midcycle meetup last week. 16:06:08 I set an intent to email the dev list summarizing our activity there 16:06:32 but have not been back in the office since I left Oregon, so I have not completed this yet 16:06:52 so what we will do today is give a quick high level summary, and follow that up with additional detail on the ML 16:07:10 excellent 16:07:38 ok, so the good news is that we have an outline for a proposal for adding containers support to OpenStack that the Nova team is happy with 16:07:58 there is bad news? 16:08:00 the virt drivers for containers stay on the same track they are on 16:08:12 no, this is not paired with bad news ;-) 16:08:37 so we still continue with efforts related to nova-docker and libvirt/lxc 16:09:12 we use Nova for producing an instance 16:09:22 which can be of any virt type that nova has drivers for 16:09:32 so it can be a bare metal instance, a VM, a container, etc. 16:09:46 within that instance we place an agent 16:10:05 it uses a relay to connect to the control plane where it can be controlled by the (drumroll please) 16:10:11 containers service 16:11:01 which has a containers centric API for handling OS level things, including shell ENV vars, exit status, stdio, etc. 16:11:26 we are producing spec documents that detail the API, and the system architecture 16:11:40 you should expect to see drafts of those for review next week. 16:11:46 comments or questions so far? 16:12:12 adrian_otto: will the conatiner service load the nova-docker plugin, and provide extensions to it? 16:12:15 the nova guys like the agent because it fits in with a long-term goal of having an 'openstack-agent' in instances 16:12:21 or is this all net new for docker container management 16:12:27 funzo: excellent question, no. 16:13:02 the virt drivers in Nova are only intended to provide the level of features that the current Nova drivers do, not more. 16:13:04 o/ 16:13:21 the container specific features will go into the containers service, and the host agent. 16:13:37 we will make an effort to reuse existing art to implement early versions of those 16:13:56 so things like docker, libswarm, libct, etc will be under consideration as building blocks. 16:14:09 but this plan should not require extensions to Nova 16:14:40 s1rp: +1 16:14:49 adrian_otto: what do you think the timeframe will play out as for getting a container service incubated? 16:15:06 funzo: another great question... 16:15:13 we did discuss this with the Nova team 16:15:18 adrian_otto: i know the timeing thing is always hard to guestimate 16:15:47 while we are building it, we will run it as a stackforge project, and then propose it as a new project under the existing Compute program 16:15:57 adrian_otto: I'm assuming when the container service is up to snuff, we'll depricate the nova-docker driver 16:15:57 so it can have its own core reviewer team 16:16:11 funzo: actually no, that's a funny detail 16:16:23 this plan assumes nested containers 16:16:31 funzo: to clarify on your earlier question… this does not eliminate the need for nova-docker 16:16:33 ah ok 16:16:48 and that we will get features into Linux to allow unprivileged nesting 16:16:50 Is there a link to the plan? 16:17:00 Sorry .. Joined a bit late 16:17:02 o/