16:01:47 #startmeeting containers 16:01:47 Meeting started Tue Sep 5 16:01:47 2017 UTC and is due to finish in 60 minutes. The chair is strigazi. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:48 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:50 The meeting name has been set to 'containers' 16:02:03 #topic Roll Call 16:02:12 Spyros Trigazis 16:02:38 Adrian Otto 16:02:47 Sayali Lunkad 16:02:54 Yatin Karel 16:03:16 o/ 16:04:06 Thanks for joining the meeting adrian_otto slunkad ykarel mnaser 16:04:24 MVP Nitesh 16:04:29 Our agenda is at https://wiki.openstack.org/wiki/Meetings/Containers#Agenda_for_2017-09-05_1600_UTC 16:04:33 hello mvpnitesh 16:04:38 #link https://wiki.openstack.org/wiki/Meetings/Containers#Agenda_for_2017-09-05_1600_UTC 16:04:48 #topic Announcements 16:05:17 A minor one, chandankumar is working on https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html 16:05:26 #link https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html 16:05:38 #topic Review Action Items 16:05:54 strigazi to review existing BPs and complete the list for Queens blueprints 16:05:59 #link https://etherpad.openstack.org/p/magnum-queens-planning 16:06:49 I want through all of them, There are some that I will manage but contributions are welcome. The first section 16:06:57 s/want/went 16:07:31 The bps in the second section need a assignee 16:07:45 #topic Essential Blueprints Review 16:07:45 i personally can help in roboustness/stability of things as we see issues come up in prod. i can help in assistance in reviewing stuff as well 16:08:02 mnaser: Thanks 16:08:13 Review Federation API specification https://review.openstack.org/#/c/489609/ 16:08:50 I would like you to have a look in this spec ^^ so that we can finilize it 16:09:15 We have already a contributor who started the spec, testing and implementation 16:09:54 We tested a magnum cluster federated with one more magnum cluster + one in GCP + Azure + Oracle Cloud 16:09:58 and for those who want to read it in a much easier way - you can click on the build link and get this - http://docs-draft.openstack.org/09/489609/9/check/gate-magnum-specs-docs-ubuntu-xenial/f1da039//doc/build/html/ :) 16:10:07 It looks promising if we can have it ready 16:10:42 strigazi assign me 2 or 3 blueprints, i'll work on them. 16:11:00 To federate clusters with one api call or click in horizon 16:11:39 mvpnitesh: you can select from the Short-list 16:12:26 @all, Do you any input on the Federation API specification ? 16:12:31 Sure, i'll select them and i'll inform you 16:12:41 adrian_otto ykarel ? 16:12:57 strigazi, haven't gone through it yet 16:12:59 mnaser Are you interested in it? 16:13:01 will go this week 16:13:22 strigazi reading, but so far so good. in a public cloud pov, it's a great idea because it promotes easy multicloud architecture 16:13:24 strigazi not yet, but I can check it out 16:13:40 slunkad: Would it be a fit for you? once we have the core code in we can add implementation for the suse driver 16:14:10 "Add support for including external Kubernetes clusters (deployed in GKE, ACS, AWS, ...) in a Magnum federation." 16:14:18 would be nice if that included... deployed in Magnum :D 16:14:26 but i assume that's a given :p 16:14:54 you mean federate magnum cluster together? 16:14:58 yep 16:14:59 strigazi: yeah as far as I understand it does 16:15:20 mnaser: that is the first to be supported :) 16:15:26 strigazi i assumed so :) 16:15:44 We can clear that up :) 16:16:13 other than that, it wfm 16:17:12 i think down the line we should look into using the heat agents, it should be a bit of a priority 16:17:20 we're getting really close to the 64K limit for cloud-init 16:17:48 mnaser: I have started it this 16:17:50 and it will also help make scale-up and down easier with some quiscing code and things like ugprades possible 16:18:01 #link https://review.openstack.org/#/c/468816/ 16:18:20 And the implementation I'm working in uses the heat-agent 16:18:22 strigazi, is kubernetes support for federation cluster production ready? last week i was in a meetup there they told it's not production ready yet, 16:18:44 I mean for the upgrades. 16:19:17 ykarel: We have federated magnum clusters with 3 different public clouds 16:19:36 By the time Queens is released we will have two more kubernetes releases 16:20:00 strigazi, Ok, may be the guys were outdated with the updates 16:20:30 So it is ready not sure what production ready means, but we can iterate on it if there are bugs 16:20:44 Ok 16:20:56 strigazi that's great (re: heat-container-agent). it should be a priority imho :) good to hear! 16:21:01 (anyways, we should stick to the agenda) 16:21:37 mnaser: yeap, the heat-container-agent will be ready, it is almost done. 16:21:45 ++ 16:22:19 So, for new features I'll manage the first section an slunkad will take the suse driver 16:22:28 s/an/and 16:23:12 I have created the milestones in launchpad and I'll target the BPs this week. 16:23:40 awesome 16:23:44 #action strigazi to target BPs for specific queens milestones 16:24:45 If more people want to take some BP I'll target it later. 16:24:53 Do you want to add anything? 16:25:22 I'm good for now 16:26:09 ok, let's move to Open Discussion then 16:26:19 before that 16:26:48 Prepare magnum 5.0.2 16:27:46 There are some patches in stable/pike already. We can do a point release next Thursday, what do you think? 16:27:49 mnaser: ^^ 16:28:04 i submitted something to backpotr 16:28:08 let me check if it merged 16:28:17 one week sounds good? 16:28:22 https://review.openstack.org/#/c/499842/ + a backport 16:28:52 so if we can just keep an eye out on those 16:28:57 it wfm 16:30:01 So, release 5.0.2 in a week after those fixes, potentially more. ok for all? 16:30:39 ++ 16:30:42 yes 16:30:49 yes 16:31:04 mnaser, i commented on it, i tried that patch 16:31:45 #agreed release magnum 5.0.2 at 2017-09-14 16:31:56 #topic Open Discussion 16:32:25 Any other business? 16:32:26 ykarel cool we can discuss that further in the review 16:32:34 mnaser, Ok 16:32:46 everything is good at our side, perhaps aim to get 1.7.5 once we can get it and lookout for coredns 1.0.0 16:33:56 mnaser: 1.7.5 is a matter of time. And as soon as we get it you can use the kube_tag label 16:34:08 coredns will be released this week too 16:34:36 I added the fix that interest us in the release notes of coredns too 16:35:26 I think we are covered, wrap the meeting early? 16:35:59 i agree :) 16:36:05 +1 16:36:10 +1 16:36:15 cool 16:36:23 Thanks for joining folks 16:36:28 #endmeeting