03:00:03 <hongbin> #startmeeting zun
03:00:04 <openstack> Meeting started Tue May  2 03:00:03 2017 UTC and is due to finish in 60 minutes.  The chair is hongbin. Information about MeetBot at http://wiki.debian.org/MeetBot.
03:00:06 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
03:00:08 <openstack> The meeting name has been set to 'zun'
03:00:10 <hongbin> #link https://wiki.openstack.org/wiki/Zun#Agenda_for_2017-05-02_0300_UTC Today's agenda
03:00:15 <hongbin> #topic Roll Call
03:00:27 <Namrata> Namrata
03:00:41 <mkrai> Madhuri
03:00:51 <kevinz> kevinz
03:02:02 <hongbin> thanks for joining the meeting Namrata mkrai kevinz
03:02:22 <Shunli> sorry for late
03:02:27 <shubhams> shubhams \o
03:02:41 <hongbin> thanks for joining Shunli shubhams , you are not late :)
03:02:48 <hongbin> ok, let's get started
03:02:55 <hongbin> #topic Announcements
03:03:01 <hongbin> 1. We have a "Boston Summit" release by the end of April
03:03:07 <hongbin> #link https://review.openstack.org/#/c/459160/
03:03:11 <hongbin> #link https://review.openstack.org/#/c/461187/
03:03:16 <hongbin> #link https://review.openstack.org/#/c/460763/
03:03:30 <hongbin> they are the releases of zun, zunclient, and zun-ui respectively
03:03:48 <hongbin> you could see the new tag on the github now
03:03:58 <hongbin> they are 0.1.0 or 0.2.0
03:04:09 <hongbin> hope you enjoy them
03:04:18 <hongbin> 2. A proposed change of Zun core team
03:04:25 <hongbin> #link http://lists.openstack.org/pipermail/openstack-dev/2017-April/116112.html
03:04:41 <hongbin> look forward to your vote on this proposal
03:04:57 <shubhams> Great that we have a release
03:05:08 <hongbin> i saw qiming, pradeep and kevin already voted for it
03:05:20 <hongbin> thanks for that
03:05:21 <mkrai> I will vote too today
03:05:23 <shubhams> Good to see Feng in Core team .. I will cast my vote soon
03:05:32 <hongbin> thx
03:05:40 <hongbin> 3. No meeting next week due to OpenStack Summit
03:05:52 <hongbin> that is all from me
03:06:18 <hongbin> any remark/announment from you?
03:06:54 <hongbin> seems no
03:07:02 <hongbin> #topic Review Action Items
03:07:09 <hongbin> 1. hongbin create a bp for floating ip association to containers
03:07:15 <hongbin> #link https://blueprints.launchpad.net/zun/+spec/floating-ip-association
03:07:17 <hongbin> done
03:07:24 <hongbin> 2. hongbin create a bp to track the idea of labeling hosts
03:07:28 <hongbin> #link https://blueprints.launchpad.net/zun/+spec/label-compute-host
03:07:40 <hongbin> that conclude the review action items
03:07:52 <hongbin> any comment on these?
03:08:19 <hongbin> seems no
03:08:28 <hongbin> ok, advance topic
03:08:31 <hongbin> #topic Kuryr integration (hongbin)
03:08:39 <hongbin> #link https://blueprints.launchpad.net/zun/+spec/kuryr-integration The BP
03:08:57 <hongbin> i marked this bp as implemented, and created another bp for the network api design
03:09:15 <hongbin> #link https://blueprints.launchpad.net/zun/+spec/network-rest-api
03:09:32 <hongbin> feel free to take it if anyone interest on it
03:09:44 <mkrai> I will assign it to myself
03:09:49 <hongbin> mkrai: ack
03:10:59 <FengShengqin> Last week , i met the bug https://bugs.launchpad.net/zun/+bug/1686617
03:10:59 <openstack> Launchpad bug 1686617 in Zun "Auth plugin requires parameters which were not given: auth_url" [Undecided,New] - Assigned to <email address hidden> (feng-shengqin)
03:11:00 <hongbin> mkrai: i am open for idea about the idea, a requirement from my side is i) to make it easy to use, ii) make it similar to nova
03:11:32 <mkrai> hongbin: Ok I will create an etherpad for that
03:11:37 <mkrai> I will start this after Boston summit
03:11:40 <hongbin> mkrai: for ii), the rational is to make it orchestratable in a heat teamplate
03:12:14 <hongbin> mkrai: after digging into the heat zun-plugin, i found that the resource will be more intuitive if it is similar to nova::server
03:12:22 <hongbin> that is my personal feeling
03:12:38 <hongbin> mkrai: sure, thx
03:12:40 <mkrai> hongbin: Ok I will look into nova network API for more details
03:12:54 <hongbin> mkrai: ack
03:13:27 <hongbin> FengShengqin: do you have any comment about that bug?
03:13:49 <FengShengqin> No, i will try later
03:14:02 <hongbin> ok
03:14:36 <hongbin> any other comment for this topic
03:14:38 <hongbin> ?
03:14:46 <mkrai> No
03:15:08 <shubhams> none from me
03:15:14 <hongbin> ok, next topic
03:15:17 <hongbin> #topic Introduce container composition
03:15:22 <hongbin> #link https://review.openstack.org/#/c/437759/
03:15:32 <hongbin> #link https://etherpad.openstack.org/p/zun-container-composition The etherpad
03:15:39 <hongbin> kevinz: want to drive this one?
03:15:50 <kevinz> kevinz: Yeah
03:15:55 <kevinz> hongbin: Yeah
03:16:24 <kevinz> I remember last week we discussed about the API
03:16:36 <hongbin> yes
03:16:46 <kevinz> which can be used in capsule and which is not
03:17:16 <kevinz> https://etherpad.openstack.org/p/zun-container-composition
03:18:04 <kevinz> From the Line 142 to Line 169 are the container API and capsule API
03:18:27 <kevinz> Feel free to give some comments on this
03:18:43 <hongbin> ok, all, want to cast your inputs into the etherpad now?
03:18:51 <mkrai> ok
03:19:10 <hongbin> in particular, in line #142 - #169
03:21:27 <mkrai> I was thinking can we have a new input to all container commands which take 'capsule' as input
03:21:42 <FengShengqin> l#l142 list capsule-id , IMO, list  all  capsules , show  a capsule by its uuid
03:21:47 <mkrai> which means zun list capsule1 will list all container in capsule1
03:22:27 <mkrai> similarly zun delete capsule1 container1 will delete container1 in capsule1
03:22:38 <mkrai> just my 2 cents ;)
03:22:53 <hongbin> mkrai: i think we could add an option (i.e. zun list --capsule xxx) for that, however, the option needs to be optional
03:23:17 <kevinz> +1 for hongbin
03:23:33 <mkrai> yes i meant the same hongbin :)
03:23:50 <mkrai> and this could be done to all container APIs as well
03:23:56 <mkrai> hongbin: kevinz WDYT?
03:23:58 <hongbin> FengShengqin: feel free to relay your inputs to the therpad
03:24:59 <hongbin> kevinz: as FengShengqin mentioned, list capsule should not take a id?
03:25:15 <kevinz> mkrai: That's a good idea
03:26:36 <kevinz> FengShengqin:hongbin: Yes, UUID is a preferred one
03:27:22 <hongbin> kevinz: i mean the capsule api, it is "list capsule-id"
03:27:42 <hongbin> kevinz: however, capsule-id doesn't seem to make sence in list
03:29:22 <kevinz> hongbin: sure, you're right
03:29:25 <kevinz> I will remove it
03:31:10 <hongbin> kevinz: thx
03:31:19 <hongbin> seems we are well agreed on most of hte apis
03:32:07 <mkrai> Yes
03:32:15 <mkrai> We have a clear picture now
03:32:31 <kevinz> yes
03:33:13 <hongbin> kevinz: is any part of the api design that you want more clarification?
03:34:42 <kevinz> hongbin: thx hongbin, I have one. For capsule delete, I think we should add the support for delete capsule with "special labels"
03:35:33 <kevinz> For example, Some capsules will be labeled as "web-server".
03:36:05 <hongbin> i am not strong at this one, would like to consider opinions from others
03:36:09 <kevinz> They are doing the same functions, so delete with label can make the API more flexible
03:36:13 <Shunli> -1 for delete by label
03:36:43 <Shunli> I think containers in capsule should delete all or none.
03:36:54 <Shunli> should not be deleted separately.
03:37:10 <mkrai> kevinz: Will it delete all the containers in a capsule?
03:37:11 <FengShengqin> +1  delete with label can make the API more flexible
03:37:35 <kevinz> Shunli: Yeah, delete lables also means delete "all containers in one capsule"
03:38:27 <kevinz> Just delete all the capsules which have the same labels. Not seperately delete special containers
03:38:29 <mkrai> kevinz: If so, I think I am ok to have it. Given that it deletes all the container in a capsule
03:39:02 <Shunli> If just use the lable to indentify the capsule. Then delete all or none containers in capsule. I'm +1 for delete by label.
03:39:51 <hongbin> ok, seems we have an agreement on this as well
03:39:53 <kevinz> mkrai: Shunli: Thx for that! as you say, this label is for identify the capsule
03:40:17 <kevinz> hongbin: Yes that's great
03:40:49 <hongbin> one last thing, could you revisit the capsule api in the etherpad, inparticular, option #2
03:41:01 <hongbin> needs your opinion for 2.1, 2.2, and 2.3
03:41:06 <mkrai> kevinz: It will be great if you can write the new capsule_id param to container APIs in etherpad also.
03:42:02 <mkrai> hongbin: Do you mean to check the delete API?
03:42:10 <hongbin> mkrai: the update api
03:42:22 <mkrai> ok
03:42:23 <hongbin> line #166 - #168
03:43:05 <hongbin> the question is how to update a container in capsule
03:43:11 <hongbin> there are 3 options listed
03:43:12 <mkrai> I vote for 2.3
03:43:40 <kevinz> mkrai: you mean the capsule_id just occurs in API "list"?
03:44:39 <kevinz> mkrai: Maybe this is a typo, I'd like to choose the uuid instead, the same with containers
03:45:24 <hongbin> ok, i lean to 2.3 as well
03:46:16 <mkrai> kevinz: Ex. zun list --capsule <id>, zun update --capsule <capsule> container
03:46:43 <hongbin> +1
03:47:13 <hongbin> ok, seems we agree on this one as well
03:47:29 <hongbin> kevinz: anything else you want to bring up about this topic?
03:48:20 <kevinz> hongbin: just consider the capsule id which mkrai referred
03:49:23 <kevinz> hongbin: besides this, that's all from me. Thx everyone for the kindly comments:-)
03:49:56 <hongbin> i lean to let capsule operation can take a name or uuid (similar to containers)
03:50:20 <mkrai> +1 for both name or uuid
03:50:36 <kevinz> +1
03:51:01 <hongbin> ok, seems we agreed again
03:51:08 <kevinz> Cool
03:51:31 <hongbin> all, any other remark on this topic?
03:51:46 <mkrai> No that's all
03:51:54 <hongbin> ok
03:51:57 <hongbin> #topic Open Discussion
03:52:01 <hongbin> Namrata: there?
03:52:03 <mkrai> Thanks kevinz for your hard work on this :)
03:52:10 <hongbin> Thanks kevinz
03:52:14 <Namrata> Hi
03:52:29 <kevinz> mkrai: hongbin: My pleasure :-)
03:52:29 <hongbin> Namrata: want to give the team an update for your heat work ?
03:52:30 <Namrata> I have seen the reviews I will update the patch
03:53:00 <hongbin> Namrata: thx
03:53:04 <Namrata> https://review.openstack.org/#/c/437810/
03:53:14 <hongbin> Namrata: i like your patch, it improves a lot
03:53:26 <Namrata> Thanks and it needs improvement also
03:53:31 <Namrata> will update the same
03:53:55 <hongbin> Namrata: look forward to your revision
03:54:10 <Namrata> yeah sure
03:54:24 <hongbin> for all, Namrata is working on the Heat integration feature, which is very cool
03:54:43 <hongbin> with that, you could orchestrate zun container with any openstack resource in a heat template
03:54:57 <hongbin> i play with it, and like it a lot
03:55:06 <mkrai> We will try to include an example in Boston summit
03:55:16 <mkrai> Namrata: will help me :)
03:55:47 <Namrata> mkrai : sure
03:56:12 <hongbin> thanks Namrata
03:56:23 <hongbin> all, any other topic you want to bring it up?
03:57:29 <hongbin> seems no
03:57:37 <hongbin> all, thanks for joining the meeting
03:57:48 <hongbin> remember there is no meeting next week
03:58:00 <hongbin> see you all the week after the next week
03:58:07 <hongbin> #endmeeting