16:01:43 #startmeeting containers 16:01:44 Meeting started Tue Feb 2 16:01:43 2016 UTC and is due to finish in 60 minutes. The chair is adrian_otto. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:45 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:48 The meeting name has been set to 'containers' 16:02:29 o/ Hello! 16:02:33 #link https://wiki.openstack.org/wiki/Meetings/Containers#Agenda_for_2016-02-02_1600_UTC Our Agenda 16:02:37 #topic Roll Call 16:02:39 Adrian Otto 16:02:41 Thomas Maddox 16:02:46 o/ 16:02:46 murali allada 16:02:46 o/ 16:02:47 o/ 16:02:49 o/ 16:02:51 o/ 16:02:53 o/ 16:03:16 o/ 16:03:27 o/ 16:04:02 hello thomasem hongbin muralia madhuri HimanshuGarg rods rpothier levi_b eghobo and coreyob 16:04:25 hello everyone 16:04:32 o/ 16:04:35 o/ 16:04:52 o/ 16:04:55 o/ 16:05:22 hello suro-patz bradjones dimtruck localloop127 16:05:41 o/ 16:07:31 hello dane. Let's begin. 16:07:36 #topic Announcements 16:08:12 1) Welcome Ton Ngo and Egor Guz as our new core reviewers. 16:08:40 Congratulations! 16:08:45 thanks to both of you for your considerable contributions to Magnum. We are proud to have you. 16:08:55 Congratulations 16:09:07 thx 16:09:12 I will plan to revisit the addition of new members on the first day of each month going forward 16:09:34 2) Review queue swept. Inactive reviews have been set to abandoned state, meaning that they are not actionable by reviewers. If you have submitted reviews that were not merged, and you have not updated, recently, please look for them in abandoned state, and revive them: 16:09:42 #link https://review.openstack.org/#/q/status:abandoned+project:openstack/magnum Abandoned Reviews 16:09:57 Yeah, I think I saw one Andrew had worked on go inactive. 16:10:01 in my inbox 16:10:01 please keep in mind that an abandon action by the PTL is not the same as a -2 vote 16:10:18 it simply means that I recognize the review is not actionable because it is stale 16:10:31 so please scoop those up and bring them back to life 16:10:51 questions or concerns on these? 16:11:49 ok, next 16:11:54 3) Midcycle. 16:12:01 woop 16:12:02 #link https://wiki.openstack.org/wiki/Magnum/Midcycle 16:12:11 thanks to tcammann we have a swank location 16:12:17 there is an eventbrite 16:12:27 if you are attending, register with an in-person ticket 16:12:44 if you are remote, there is a special ticket for that, but I can not yet guarantee how we will accommodate you 16:12:59 in the past we have done our best to include remotes for key discussions 16:13:13 but it really depends on the facility whether that will work well 16:13:38 the address is there as well. 16:13:56 please let me and Tom know if you have any questions or concerns about the midcycle 16:14:12 I'll find out if we can do a webex or similar soon 16:14:39 I did make a standby ticket just in case we need more than 18, and we can shuffle folks around if needed 16:14:46 in the past that number has been just about right 16:15:52 ok, there is an etherpad where we will begin assembling agenda content 16:16:43 #link https://etherpad.openstack.org/p/magnum-mitaka-midcycle-topics Midcycle Agenda 16:17:06 I will source your input from that etherpad to form the agenda, and slot it by time 16:18:10 any other announcements from team members? 16:18:44 #topic Review Action Items 16:18:52 1) adrian_otto to champion consensus and merge of https://review.openstack.org/268852 16:18:59 Status: Complete. Review merged. Any opposing viewpoints remaining to consider? 16:19:37 I'm still a little dubious about the security of using a secondary domain instead of the project's domain 16:19:50 but I'll follow up with those concerns as I find concrete examples 16:20:26 ok, we'll be open to revisit this if there are concerns to address 16:21:13 my ask is that if we dislike the approach, that we make actionable suggestions for a better approach along with our criticisms. 16:21:46 any more thoughts on this topic? 16:22:26 ok, next action item 16:22:31 2) adrian_otto to produce a wiki page that explains Magnum's ability to support native API access and wrapped (limited) access to that funcitonality through our contiainers resource, and pointers to points of debate. 16:22:42 nice spelling errors in there ;-) 16:22:46 Status: in progress 16:23:03 I have been polling a few of you seeking use cases for our /containers endpoint 16:23:18 if you have one, please let me know, so I can incorporate that into our POV 16:23:39 I will expose this initially as a draft, and we can discuss it prior to finalizing the project POV 16:23:49 any questions? 16:24:15 ok, let's advance 16:24:21 #topic Magnum UI Subteam Update (bradjones) 16:24:27 hi 16:24:30 hi! 16:24:55 so the last major bp (creating bay models) finally merged which is awesome 16:25:19 #action adrian_otto to produce a wiki page that explains Magnum's ability to support native API access and wrapped (limited) access to that functionality through our containers resource, and pointers to points of debate. 16:25:35 at this point there is nothing major left to do from the bps 16:25:36 sweet 16:25:50 I think now that has merged it would be a great time to take a closer look at docs 16:25:58 explaining using and extending in the future 16:26:05 ok, so I'd like to work together with you to put a demo together of the UI 16:26:18 and we can put that on the Magnum project wiki page 16:26:23 adrian_otto: sounds great 16:26:34 and docs would be the logical follow-up to that 16:26:47 ok let's aim for demo first then docs to follow then 16:27:05 excellent. Let's take that as an action item 16:27:09 sound ok? 16:27:12 sure 16:27:32 #action bradjones and adrian_otto to work on a demo of the Magnum UI for publication on the Magnum project wiki page. 16:27:53 we can regroup after the meeting to earmark time for that. 16:28:00 sounds good 16:28:19 #topic Blueprint Review 16:28:27 #link https://review.openstack.org/#/c/206467/ Add guide for TLS support in Magnum. (abandoned) needs revival 16:28:52 madhuri: this one has an important issue where two of the images look the same 16:28:53 I will submit a revision soon 16:29:10 ok, terrific. If you need help from the team, please let us know. 16:29:21 Sure. Thank you! 16:29:27 #topic Essential Blueprint Updates 16:29:51 I will come back to the suro-patz ones in just a moment. 16:30:03 sure 16:30:26 the launchpad site has been really slow for me recently 16:30:46 takes 40 seconds or so to respond 16:31:08 actually now it's throwing errors 16:31:19 so I can do this from memory, or look at our minutes from last meeting 16:31:37 Tango, I know you have a docs BP in progress that you updated in the past 24 hours. 16:31:42 can you give us an update on that? 16:32:03 #link https://blueprints.launchpad.net/magnum/+spec/user-guide User Guide Blueprint 16:32:20 adrian_otto: I think Tango is on PTO 16:32:30 #link https://blueprints.launchpad.net/magnum/+spec/magnum-troubleshooting-guide Troubleshooting Guide Blueprint 16:32:42 ok, both of those are advancing, but rather slowly 16:33:15 vilobhmm11: you have one too 16:33:22 adrian_otto : after the discussion in weekly meeting last time the spec was updated https://review.openstack.org/#/c/266662/9 is about to get merged 16:33:23 #link https://blueprints.launchpad.net/magnum/+spec/resource-quota Resource Quota Blueprint 16:33:37 it should be merged in today or so 16:34:01 adrian_otto: there's also this #link https://blueprints.launchpad.net/magnum/+spec/magnum-tempest 16:34:13 ok, based on my research so far, it might make sense to revisit the priority of rate controls for /containers resources 16:34:45 so I'll provide that feedback in the 266662 review linked above 16:35:32 adrian_otto : sure makes sense…for now would like to start with bays but going ahead definately would propose a seperate blueprint and work on it…i m in the process f information gathering about strong usecases for rate control for container resource 16:35:44 #link https://blueprints.launchpad.net/magnum/+spec/magnum-tempest (dimtruck) 16:35:57 so we have 2 patches left 16:36:12 one coreyob is updating to remove tempest from test-requirements.txt 16:36:18 vilobhmm11: thanks I appreciate it. I just want to calibrate our efforts so that we are focused where it will make the most difference for users. 16:36:19 done ^ 16:36:32 adrian_otto : sure 16:36:37 thanks coreyob and dimtruck 16:36:38 and the second one i finally coverted to test_bays for cert testing so that it finishes in a reasonable time. 16:36:41 adrian_otto: quick question 16:36:49 how do i mark a blueprint completed? :) 16:36:53 do i just tell you or... 16:36:59 I can mark it right now 16:37:01 one sec 16:37:04 because once these two land, we are good to go 16:37:25 ok, I marked it as implemented 16:37:41 awesome! thank you! 16:37:43 I can put it to pending code review first though 16:37:48 oh yes 16:37:55 then you can just lmk when they merge 16:38:00 will do 16:38:07 ok, set accordingly 16:38:26 that concludes essential blueprint status 16:38:38 #topic Other Blueprint Updates 16:38:45 (suro-patz)Needs review: #link https://blueprints.launchpad.net/magnum/+spec/async-container-operations 16:39:05 #link https://review.openstack.org/#/c/275003/ Spec for Async Container Operations 16:39:29 #link https://review.openstack.org/#/c/267134/ Implementation of Async Container Operations 16:39:38 As requested during the ongoing review, I have put a spec for the design 16:39:57 the design was discussed over ML and recorded in the Blueprint Whiteboard 16:40:11 link for spec https://review.openstack.org/#/c/275003/ 16:40:17 thanks suro-patz 16:40:20 I request you all to take a look, review and provide feedback 16:40:40 suro-patz : i will have a look today at the spec 16:40:43 good, I will certainly provide input 16:41:04 thanks vilobhmm11, adrian_otto 16:41:27 np 16:41:45 any other blueprints, bugs, or work items to discuss as a team today? 16:42:05 #topic Open Discussion 16:43:22 I did present magnum for NASA JPL 16:43:49 Super! 16:43:56 there was a definite interest for a number of BigData projects. They are particularly interested in the Mesos bay type. 16:44:23 JPL is one of the most active scientific computing centers in the world 16:44:37 so I see that as a really compelling use case. 16:44:42 This is awesome 16:44:49 thats awesome adrian_otto 16:45:37 they also recorded the session, and redistributed it on their own network where all the scientists can learn about the cloud technology presented during the Cloud LEAP event. 16:45:37 sweet! 16:46:01 I expect we will find lots of opportunities for new security features 16:46:14 as some of their projects are rather sensitive in nature 16:46:42 and there are regulatory hurdles to clear when setting up infrastructure 16:48:40 as mentioned a while back… for those of you in the Bay area, the OpenStack meetup group for the San Francisco Bay Area will be holding a meetup about Magnum on Feb 18th, also hosted by HPE in Sunnyvale, so those of us attending the Midcycle can go to that. 16:49:01 if you'd like to have a part in the presentation, just let me know and I'll be sure to give you the stage. 16:50:00 also, you will notice a few more engineers from Rackspace have begun contributing 16:50:25 and are currently working on a number of things to add Magnum capability to Carina 16:50:43 success with this effort will mark the first public cloud use case for Magnum 16:50:54 so let's do our best to support them 16:51:41 thanks adrian_otto! 16:51:51 sure 16:52:36 we will have a good look at some of the topics during the midcycle too 16:54:05 remember to share your input on the midcycle topic list, even if you are unable to attend: 16:54:08 #link https://etherpad.openstack.org/p/magnum-mitaka-midcycle-topics 16:56:48 we have a few minutes remaining 16:56:59 any other topics to touch on before we wrap up? 16:57:42 Thanks for attending today. Our next team meeting will be on 2016-02-09 at 1600 UTC. See you then! 16:57:59 #endmeeting