16:00:06 <hongbin> #startmeeting containers
16:00:08 <openstack> Meeting started Tue Jul 26 16:00:06 2016 UTC and is due to finish in 60 minutes.  The chair is hongbin. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:09 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:11 <openstack> The meeting name has been set to 'containers'
16:00:12 <hongbin> #topic Roll Call
16:00:19 <muralia> Murali Allada
16:00:19 <strigazi> o/
16:00:21 <swatson> o/
16:00:22 <Drago> o/
16:00:23 <rochaporto> Ricardo Rocha
16:00:26 <jvgrant_> Jaycen Grant
16:00:28 <mkrai> Madhuri Kumari
16:00:46 <eghobo> o/
16:01:07 <hongbin> Thanks for joining the meeting muralia strigazi swatson Drago rochaporto jvgrant_ mkrai eghobo
16:01:15 <hongbin> #link https://wiki.openstack.org/wiki/Meetings/Containers#Agenda_for_2016-07-26_1600_UTC Today's agenda
16:01:19 <tonanhngo> o/
16:01:21 <hongbin> Anything needs to be added to the agenda?
16:01:55 <hongbin> #topic Announcements
16:02:04 <hongbin> I have no annoucement
16:02:13 <hongbin> Any annoucement from our team member?
16:02:29 <hongbin> #topic Review Action Items
16:02:39 <hongbin> 1. Support baremetal container clusters (strigazi)
16:02:45 <hongbin> #link https://blueprints.launchpad.net/magnum/+spec/magnum-baremetal-full-support
16:02:54 <hongbin> strigazi: ^^
16:03:25 <strigazi> Not much progress since last week, I was trying to setup the gate job properly and replicate the issues locally.
16:03:42 <mkrai> I submitted patches for swarm last week
16:04:01 <strigazi> This week I'll test mkrai's patches
16:04:14 <mkrai> Thanks strigazi
16:04:20 <adrian_otto> o/
16:04:24 <hongbin> strigazi: Did the gate work properly?
16:04:48 <strigazi> no, we have only 8GB or ram and 80GB disk
16:05:16 <hongbin> Yes, that is the limitation
16:05:42 <strigazi> another issue
16:05:45 <rochaporto> we might add a couple larger nodes at cern to get this going (still needs setup)
16:06:42 <strigazi> the fake ironic nodes were not approachable from ironic conductor
16:07:35 <strigazi> The good thing is
16:08:08 <strigazi> that the issue with the size of insstance_info will be solved in ironic, I'm helping a developer on than
16:08:18 <strigazi> that's all
16:08:23 <hongbin> Thanks strigazi
16:08:35 <hongbin> 2. Magnum User Guide for Cloud Operator (tango)
16:08:40 <hongbin> #link https://blueprints.launchpad.net/magnum/+spec/user-guide
16:08:44 <hongbin> tonanhngo: ^^
16:08:56 <tonanhngo> The section for mesos was merged
16:09:15 <tonanhngo> I just revised and update the section for TLS:  https://review.openstack.org/#/c/347077/
16:09:40 <tonanhngo> The section on bay got some feedback, I will update shortly
16:10:19 <tonanhngo> I think we got all the major sections, now we can wrap up the minor sections
16:10:41 <tonanhngo> and do a round of update on various new features.
16:10:55 <tonanhngo> So generally, we are in decent shape
16:11:03 <hongbin> Yes, we are
16:11:12 <tonanhngo> That's all I have for now
16:11:25 <hongbin> Thanks tonanhngo . Question? Comment?
16:11:37 <strigazi> After a while we are going to split the guide?
16:11:45 <strigazi> In smaller sections?
16:12:04 <tonanhngo> strigazi:  What do you have in mind?
16:12:31 <strigazi> eg this configuration option is related to performance https://review.openstack.org/#/c/326428/15/doc/source/userguide.rst
16:12:54 <strigazi> we could have a section for futher configuration after the basic installation
16:13:13 <strigazi> add lbaas, add barbican
16:13:16 <tonanhngo> Like tuning?
16:13:19 <strigazi> yes
16:13:27 <strigazi> tuning and features
16:13:35 <tonanhngo> That's a good idea.
16:13:41 <strigazi> I mean extra features
16:13:56 <tonanhngo> Let's put those ideas on the BP so we can track
16:14:02 <strigazi> ok
16:14:05 <strigazi> thanks
16:14:26 <hongbin> OK. Advance topic
16:14:29 <hongbin> 3. COE Bay Drivers (jamie_h, muralia)
16:14:44 <hongbin> #link https://blueprints.launchpad.net/magnum/+spec/bay-drivers
16:14:46 <hongbin> muralia: ^^
16:14:52 <muralia> I don't any major updates. I need to do a lot more testing. Especially around installing a new driver and using it.
16:15:24 <muralia> just working on that. Will have more updates soon.
16:15:40 <hongbin> muralia: I saw a few patches were merged
16:15:56 <hongbin> muralia: maybe update the team which parts are done, which parts are TODO
16:16:19 <strigazi> muralia: Could I continue this one https://review.openstack.org/#/c/324470/ ?
16:16:28 <strigazi> It will us clean things up
16:16:32 <strigazi> It will help us clean things up
16:16:52 <muralia> yes, the patches that got merged move the common and driver files to the driver folder. basically the refactor part is done
16:17:06 <muralia> whats remaining is the integration with stevedore
16:17:15 <muralia> strigazi: yes, you can work on that
16:17:20 <strigazi> thanks
16:17:43 <strigazi> about refactoring, I have a question/comment
16:17:48 <muralia> yes
16:18:09 <strigazi> there is this change up for review https://review.openstack.org/#/c/346209/
16:18:43 <strigazi> I think it's very large and without planing and discussion with the team
16:19:24 <hongbin> strigazi: I think you can relay your comments to the reviews
16:19:29 <strigazi> moving lbaas was a work done by Drago who wrote this part and hence it was done carefully
16:19:55 <Drago> I think at the least the patch should be split up a little
16:19:59 <strigazi> That I want to say is, we should start a discussion on who to avoid code duplication with the bay drivers
16:20:16 <muralia> yes, lets add all these comments in the patch
16:20:18 <strigazi> *on how
16:20:48 <strigazi> ok, I'll add it also as discussion topic for the midcycle
16:20:52 <hongbin> How to avoid code duplication between drivers is a good topic for midcycle
16:21:09 <Drago> I have added "Supporting the install of bay drivers that use different versions of the common directory" which is very similar
16:21:18 <muralia> hongbin: yes, let me add that to the etherpad. strigazi, we should be ok to move duplicated files to the common folder
16:21:23 <tonanhngo> There is some cleaning up we can do also after the bay driver refactoring.
16:21:25 <Drago> Because that is the issue we face when we start de-duplicating
16:21:26 <rajiv_> I found some more code duplicacy in heat templates also.
16:21:37 <strigazi> Drago, didn't see it, thanks
16:21:58 <muralia> de-duplicating files for the 4 drivers that come by default with magnum should be fine.
16:22:02 <rajiv_> may be we can refactor heat templates also.
16:22:58 <hongbin> OK. any other comment?
16:23:10 <strigazi> We should discuss how this is going to happen first
16:23:18 <rajiv_> ok
16:23:30 <hongbin> 4. Create a magnum installation guide (strigazi)
16:23:30 <muralia> yes, its been added as a topic to the mid-cycle agenda
16:23:39 <hongbin> #link https://blueprints.launchpad.net/magnum/+spec/magnum-installation-guide
16:23:46 <hongbin> strigazi: ^^
16:24:27 <strigazi> The guide is complete and merged for the 4 distros documented across all projects.
16:24:45 <hongbin> Yes, I think we can close the BP
16:24:47 <tonanhngo> Very nice!
16:25:02 <hongbin> strigazi: are you able to close the BP?
16:25:03 <strigazi> we can leave it until the end of the cycle
16:25:16 <strigazi> because I'll have to test it again
16:25:27 <adrian_otto> thanks strigazi for all your work on the install guides.
16:25:28 <strigazi> the functionality might change
16:25:54 <strigazi> But, we can remove it from the meeting agenda
16:26:04 <hongbin> strigazi: OK. Will do that
16:26:25 <strigazi> I'll work again when the official packages are ready
16:27:02 <strigazi> adrian_otto: It was my pleasure
16:27:03 <hongbin> strigazi: Thanks strigazi
16:27:15 <hongbin> Next topic
16:27:18 <hongbin> #topic Kuryr Integration Update (tango)
16:27:25 <hongbin> tonanhngo: ^^
16:27:44 <tonanhngo> I attended the IRC last night but the meeting didn't occur
16:28:02 <tonanhngo> There is some discussion on the ML for a new meeting time, so I will keep an eye on that
16:28:33 <tonanhngo> The code refactoring is still not complete, so we can't quite build yet.  I am still using the old copy
16:28:56 <tonanhngo> For us it should be OK, since we will just pull the container image for Kuryr
16:29:27 <tonanhngo> I do have the openvswitch and L2 agent working in a Fedora 23 container in Swarm
16:29:38 <hongbin> cool
16:29:56 <tonanhngo> I just register the new BP with some details on the implementation
16:30:24 <tonanhngo> I will wrap up the prototype and start the patches
16:30:53 <tonanhngo> One question for the team, I think this was brought up before.
16:31:25 <tonanhngo> Should we upload custom container image to Docker Hub, for Magnum use?
16:31:58 <tonanhngo> We can implement the openvswitch container as Dockerfile, but a ready built image would be faster
16:32:23 <muralia> +1
16:32:24 <hongbin> For me, it is fine.
16:32:29 <strigazi> tonanhngo: This will raise the same issue I had with rexray
16:32:51 <tonanhngo> Is there a Magnum user account already on Docker Hub?
16:33:03 <strigazi> yes but we don't know the owner
16:33:12 <strigazi> it's openstackmagnum
16:33:29 <tonanhngo> Should we try to find the owner, or just create a new account?
16:33:39 <hongbin> We can create a new one with different name
16:33:45 <strigazi> We can do both
16:33:59 <tonanhngo> OK, let me send to the ML to ask first
16:34:17 <tonanhngo> If no answer, we can create a new account
16:34:39 <tonanhngo> That's all I have for now
16:34:47 <hongbin> Thanks tonanhngo
16:34:59 <adrian_otto> I don't know who controls the "openstackmagnum" hub.docker.com account.
16:35:48 <hongbin> me either
16:35:59 <adrian_otto> but whatever accounts we have, I suggest that it be held only by the PTL, and transferred to the next PTL upon any change in control.
16:36:00 <hongbin> Let's find the owner in ML
16:36:19 <hongbin> adrian_otto: sure
16:36:43 <hongbin> Any other comment?
16:37:01 <hongbin> #topic Other blueprints/Bugs/Reviews/Ideas
16:37:06 <adrian_otto> and there should be reviewed instructions for how to verify those images, so the fear of tampering can be addressed.
16:37:07 <hongbin> 1. Select our project mascot/logo
16:37:20 <hongbin> #link http://lists.openstack.org/pipermail/openstack-dev/2016-July/100011.html
16:37:49 <hongbin> Proposed mascots:
16:38:06 <hongbin> Stallion - http://free-icon-download.com/modules/PDdownloads/singlefile.php?cid=11&lid=44
16:38:11 <hongbin> Snake - http://www.freeiconspng.com/uploads/snake-jungle-22.png
16:38:13 <tcammann> Think we should have a Magnum Moose
16:38:16 <hongbin> Wave - http://www.123rf.com/photo_11649085_set-of-waves.html
16:38:23 <hongbin> Paraponera clavata - https://en.wikipedia.org/wiki/Paraponera_clavata
16:38:28 <hongbin> Bombardier beetle - https://en.wikipedia.org/wiki/Bombardier_beetle
16:38:32 <hongbin> shark - http://www.logoground.com/logo.php?id=10554
16:38:36 <hongbin> kangaroo with a joey in its pouch - http://www.supercoloring.com/pages/red-kangaroo
16:38:42 <hongbin> koala bear with a joey in its pouch - http://web.stanford.edu/~jay/koalas/koala%20mums.jpg
16:38:46 <hongbin> beaver - https://commons.wikimedia.org/wiki/File:Beaver_%28PSF%29.jpg
16:39:00 <hongbin> tcammann: what is Magnum Moose? picture?
16:39:50 <tcammann> majestic moose https://images.indiegogo.com/file_attachments/1328366/files/20150326083908-Mooselaughing.jpg?1427384348
16:39:59 <jvgrant_> Kangaroo, Stallion, and shark are my favorites so far, though a moose might be pretty cool
16:40:00 <Drago> My question is, should we have it relate to what magnum does or where it gets its name? Or does it matter at all?
16:40:17 <Drago> i.e. what significance does the mascot have to Magnum
16:40:17 <hongbin> tcammann: +1
16:40:31 <adrian_otto> Drago: it can be any animal or natural feature.
16:40:43 <jvgrant_> it can relate but it doesn't have to
16:41:01 <adrian_otto> The actual story of the magnum name can't be connected in this case. Our name came from a Magnum of Champagne.
16:41:13 <tcammann> I like the waves one as it relates to whales (docker)
16:41:27 <rajiv_> +1 wave
16:41:29 <mkrai> I like tonanhngo idea of kangaroo carrying joey in its pouch
16:41:32 <rochaporto> waves, kangaroo, moose (in this order)
16:41:35 <jvgrant_> they have an artist who will make an icon that has a similar style to all the others in Openstack
16:41:53 <adrian_otto> Shark, Waves, Kangaroo, Moose
16:42:00 <jvgrant_> if what they have on the site is the style they will be cartoony like drawings
16:42:05 <strigazi> something related to the sea since we have bays
16:42:08 <mkrai> As it can relate to kangaroo being magnum carrying containers(joey)
16:42:36 <tcammann> more "badass" waves http://images.metmuseum.org/CRDImages/as/original/DP130155.jpg
16:43:03 <tonanhngo> How are we going to choose with so many choices? :)
16:43:17 <adrian_otto> we only need to identify a short list
16:43:21 <Drago> Waves makes me think Hawaii (Magnum P.I.)
16:43:23 <adrian_otto> by tomorrow
16:43:49 <hongbin> Yes, let's get a short list first
16:44:22 <adrian_otto> so maybe if three of us can agree on an item being on the list, then it makes it in?
16:44:46 <adrian_otto> and we can use whatever formal voting process to narrow it down form there
16:45:27 <jvgrant_> Looks like Waves, Kangaroo, Shark, and Moose are top so far
16:45:50 <hongbin> jvgrant_: yes
16:45:55 <adrian_otto> so if you feel strongly about adding to that list, make your case.
16:46:45 <hongbin> Yes, let's assume here is the list : Waves, Kangaroo, Shark, and Moose
16:46:58 <hongbin> If you want to add to this list, let me know by the end of today
16:47:14 <tonanhngo> Sounds good.
16:47:21 <hongbin> The, I will send the list to OpenStack foundation
16:47:54 <hongbin> OK. Anything else for this topic?
16:48:13 <hongbin> 2. Midcycle topics
16:48:20 <hongbin> #link https://etherpad.openstack.org/p/magnum-newton-midcycle-topics
16:48:53 <hongbin> For everyone, please feel free to add your topics, and +1 on the existing topics if you want
16:49:13 <hongbin> We can collaborate on the etherpad offline
16:49:23 <hongbin> #topic Open Discussion
16:50:06 <yatin> my small query: for magnum there are lot of bugs that are open and those seems invalid. Some bugs are there which do not have description at all. Can someone from core reviewers mark them invalid/won't fix. This will narrow down the bug list of magnum and this will result in closing the
16:50:28 <tonanhngo> +1
16:50:29 <Drago> +1
16:50:32 <hongbin> yatin: good suggestion
16:50:38 <rajiv_> +1
16:50:49 <hongbin> I think the core team can do that
16:51:02 <tonanhngo> Maybe a good session for the midcycle
16:51:07 <strigazi> +1
16:51:07 <Drago> The pod/container bugs should be easy
16:51:56 <rochaporto> i would like to simplify the user commands to create a baymodel/bay by making most of the params optional (external-network, keypair, image, dns-nameserver). in most cases these are not needed, coe (bay driver) specific or better defined by the operator (in the service config). blueprint first or should i go for a patch?
16:52:41 <tonanhngo> I would suggest BP first, since this involves the user experience
16:52:42 <hongbin> rochaporto: I think both bugs and BP will work
16:52:53 <rochaporto> ok
16:53:06 <hongbin> I think it is a good idea
16:53:24 <hongbin> We need to hard-code the default value to read the default value from config file
16:54:06 <hongbin> but the direction is OK for me.
16:54:16 <rochaporto> ok i'll work on this
16:54:47 <hongbin> If nobody else has a topic, I want to raise this one: #link https://review.openstack.org/#/c/331614/
16:55:40 <hongbin> In the patch, there is a discussion about whether Magnum needs a feature to disallow duplicate bay/baymodel name
16:56:05 <hongbin> Some folks think this feature is unnecessary, others think the opposite
16:56:24 <muralia> all openstack services allow duplicate names today, so i prefer to not merging this patch
16:56:36 <hongbin> muralia: ack
16:57:03 <rajiv_> muralia: +1
16:57:19 <tonanhngo> My concern is that it can cause confusion and degrade the user experience with Magnum.
16:57:41 <akhilakishore> I have a question, I' having trouble creating bay behind proxy
16:57:58 <akhilakishore> http://paste.openstack.org/show/542148/
16:58:09 <adrian_otto> tonanhngo: can you detail the scenario(s) you are concerned about?
16:58:16 <akhilakishore> It says create in progress and times out
16:59:01 <hongbin> akhilakishore: Please ping us in the #openstack-containers channel offline. I believe someone will help you to troubleshoot that
16:59:11 <rochaporto> akhilakishore: that's often the callback to heat (for the wait condition) failing. check the heat nodes are reachable from your vms
16:59:12 <mkrai> akhilakishore, It would be better if you show us baymodel parameters
16:59:14 <akhilakishore> Oh ok
16:59:53 <hongbin> 1 minute left
17:00:08 <rajiv_> https://bugs.launchpad.net/magnum/+bug/1605416  i want to discuss this bug
17:00:08 <openstack> Launchpad bug 1605416 in Magnum "neutron loadbalancer uses incorrect security group" [Critical,Triaged] - Assigned to rajiv (rajiv-kumar)
17:00:24 <hongbin> Time is up. Let' move the discussion to the project channel
17:00:28 <adrian_otto> time  up
17:00:29 <hongbin> Thanks everyone
17:00:31 <tonanhngo> adrian_otto: I mentioned in the comment.  Basically different clouds can be configured to behave differently with respect to duplicate name, and which baymodel is referenced.
17:00:33 <hongbin> #endmeeting