16:00:00 #startmeeting containers 16:00:01 Meeting started Tue Jan 3 16:00:00 2017 UTC and is due to finish in 60 minutes. The chair is adrian_otto. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:05 The meeting name has been set to 'containers' 16:00:07 #link https://wiki.openstack.org/wiki/Meetings/Containers#Agenda_for_2017-01-03_1600_UTC Our Agenda 16:00:17 o/ 16:00:57 #topic Roll Call 16:00:57 Adrian Otto 16:01:01 o/ 16:01:02 o/ 16:01:04 o/ 16:01:05 Jaycen Grant 16:01:23 o/ 16:01:26 o/ 16:01:29 that's better 16:01:32 hello jasond jvgrant Drago randallburt and hongbin 16:02:41 While we await other attendees, I'll share that I thought it was interesting that there are five Tuesdays in January this year. 16:03:43 strigazi mentioned that he will not attend today, but will join us next week. 16:04:02 #topic Announcements 16:04:34 1) Happy New Year! I'm looking forward to a great 2017! 16:05:06 I'm glad to see you back after the holidays, and extend gratitude to those who worked straight through. 16:05:23 any announcements from team members? 16:06:01 #topic Review Action Items 16:06:04 1) ACTION: adrian_otto to add http://lists.openstack.org/pipermail/openstack-dev/2016-November/107613.html to our 2012-01-03 team meeting agenda. 16:06:10 Status: Complete 16:06:18 we will cover this later in the agenda 16:06:27 #topic Blueprints/Bugs/Reviews/Ideas 16:06:32 Essential Blueprints 16:06:47 I expect many/most of these will have no comments this meeting 16:06:53 1) #link https://blueprints.launchpad.net/magnum/+spec/flatten-attributes Flatten Attributes [strigazi] 16:07:10 strigazi is not here to comment. Anyone else have remarks on this? 16:07:32 2) #link https://blueprints.launchpad.net/magnum/+spec/nodegroups Nedegroups [Drago] 16:07:52 I'm back from vacation. Happy New Year to everyone. No update. 16:07:57 I updated the spec and review a couple weeks ago 16:08:11 to address concerns, waiting on further feedback 16:08:17 ok, I'll plan to review the spec 16:08:19 https://review.openstack.org/#/c/352734/ 16:09:17 thanks jvgrant 16:09:23 any other discussion on this BP? 16:10:07 3) #link https://blueprints.launchpad.net/magnum/+spec/secure-etcd-cluster-coe Secure Central Data store(etcd) [yatin] 16:10:17 yatin is not here to comment. Anyone else have remarks on this? 16:10:26 I see that it still has at least one review remaining open 16:10:35 but looks close to finished to me. 16:10:41 any other remarks on this? 16:11:07 4) #link https://blueprints.launchpad.net/magnum/+spec/cluster-upgrades Cluster Upgrades [strigazi] 16:11:09 strigazi is not here to comment. Anyone else have remarks on this? 16:11:42 Other Work Items (none) 16:11:48 #topic Managing cluster drivers as individual distro packages 16:11:57 #link http://lists.openstack.org/pipermail/openstack-dev/2016-November/107613.html 16:13:06 My gut reaction is to handle this in tree to keep it simple to begin with, and break it out if it becomes burdensome. Thoughts? 16:13:59 the tc was discussing a similar topic (how to deal with third party driver) 16:14:01 Is there a way to have them in-tree but be installable, so that they can be uninstalled just like a third-party driver? 16:14:18 it is better to wait for the tc to make a decision, then come back to how to deal with it in magnum 16:14:54 In-tree is good for development and trying magnum out, but I think it should be easy to remove the default drivers 16:15:07 hongbin: were they on their way to giving guidance or are they just starting discussion? 16:15:28 i think they are in the middle of the discussion 16:16:03 hongbin: cool, then yeah, I think I agree with adrian_otto and hongbin in that its fine for now and then see what tc says in a few weeks 16:16:17 i also like in-tree for ease of development 16:16:34 it worked well for heat resources 16:16:43 jasond: yeah, makes dev easy but not fun for operators 16:16:44 So we could start in-tree (option 1) and revisit that if the tc offers actionable guidance to the contrary 16:17:13 jasond: its a bit of a pita for Heat resources tbh. This same discussion comes up in Heat ever other cycle too 16:17:32 If we don't have them in-tree, we'll probably have to have a package for common driver files too or completely duplicate everything. Not fun 16:17:40 randallburt: we could always separate them out once the code becomes more stable 16:18:26 jasond: agreed. doing it now while the driver interface was just updated isn't a great idea 16:18:57 and we'll need a stable driver interface if we want to separate and encourage third party driver dev 16:19:01 hongbin: do you have any objections to starting in tree-and breaking out later? 16:19:18 adrian_otto: np from me 16:19:44 ok, I'll record an action item to respond to the thread referencing this chat 16:20:07 #action adrian_otto to respond to http://lists.openstack.org/pipermail/openstack-dev/2016-November/107613.html with a reference to this chat. 16:20:17 any other remarks on this topic? 16:20:31 #topic Open Discussion 16:21:16 We plowed through the agenda in record pace. Looks like we can afford to end early today. 16:22:00 hi adrian_otto 16:22:07 hieulq_: hi 16:22:19 I proposed the BP related to integrate OSProfiler in Magnum 16:22:20 https://blueprints.launchpad.net/magnum/+spec/osprofiler-support-in-magnum 16:22:28 Can you take a look? 16:22:31 ok 16:22:45 Thanks :) 16:25:33 hieulq: if we approved this blueprint, is this something you could commit to completion in the Ocata release cycle? That gives you less than a month. 16:26:53 #link https://releases.openstack.org/ocata/schedule.html Ocata Release Schedule 16:27:32 Jan 23 it would need to be frozen. 16:28:21 hieulq: you still there? 16:28:27 adrian_otto: yes 16:28:33 Just thinking about the plan 16:28:45 I'm preparing some patch-set related to this BP 16:29:20 But it could miss the frozen date 16:30:04 I suppose that's not a problem as long as it's added in a way that's disabled by default, and has clear comments that it's not yet supported. 16:30:04 is there any reason the bp has to land in ocata? 16:30:38 I was worried about having a partially completed feature that we may need to patch out 16:31:20 there are potentially a few partially completed features (e.g. nodegroup, upgrade). i think that is unavoidable 16:31:54 hongbin: yes 16:32:52 hongbin: so it's better to wait till next cycle, right? 16:33:43 hieulq_: personally, i don't think it is necessary to wait, just start the implementation right away should be ok. 16:34:13 hongbin: I'm on my way to implement it :-) 16:34:25 And it could help us a lot in debugging the problem 16:35:07 so I hope this BP at least got approved 16:38:22 approved 16:38:25 thanks hieulq 16:38:38 any other discussion before we wrap up today? 16:38:52 Thanks adrian_otto 16:39:24 Our next team meeting will be on 2017-01-10 at 1600 UTC. See you then! 16:39:28 #endmeeting