13:00:42 <yanyanhu_> #startmeeting senlin
13:00:43 <openstack> Meeting started Tue Mar 14 13:00:42 2017 UTC and is due to finish in 60 minutes.  The chair is yanyanhu_. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:44 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:47 <openstack> The meeting name has been set to 'senlin'
13:00:48 <openstack> Qiming: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.
13:00:59 <yanyanhu_> oops
13:01:16 <elynn> oops
13:01:32 <XueFeng> :)
13:01:32 <Qiming> thanks yanyan
13:01:33 <yanyanhu_> hi, Qiming, sorry a little bit later. the network is unstable, have to use vpn to connect
13:01:39 <yanyanhu_> Qiming, please go ahead : )
13:01:51 <Qiming> alright
13:01:52 <yanyanhu_> my pleasure :)
13:01:55 <Qiming> meeting agenda posted
13:02:04 <Qiming> #link https://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Weekly_Senlin_.28Clustering.29_meeting
13:02:32 <Qiming> basically the things on the list is about work items update, pike goal tunings, summit pre
13:02:45 <Qiming> pls add items if any
13:03:23 <Qiming> let's get started
13:03:37 <Qiming> #topic pike work items
13:03:40 <Qiming> #link https://etherpad.openstack.org/p/senlin-pike-workitems
13:04:21 <Qiming> api - profile_only
13:04:43 <Qiming> 444100 is in now
13:05:10 <Qiming> API test just added: https://review.openstack.org/#/c/445298/
13:05:24 <Qiming> found a serious bug in version negotiation
13:05:42 <Qiming> need more eyes on it
13:06:02 <Qiming> there could be similar bugs in other request objects
13:06:13 <XueFeng> which problme?
13:06:22 <XueFeng> problem
13:06:32 <Qiming> see the about patch: https://review.openstack.org/#/c/445298/
13:06:56 <XueFeng> ok
13:07:54 <Qiming> the obj_make_compatible is not deleting the primitive keys properly
13:08:07 <XueFeng> if 'profile_only' in primitive['senlin_object.data']:
13:08:07 <XueFeng> del primitive['senlin_object.data']['profile_only']
13:08:10 <Qiming> right
13:08:23 <Qiming> moving on to next topic?
13:08:29 <XueFeng> move
13:08:32 <Qiming> feature rich nova server
13:08:53 <elynn> I guess current patches are in now
13:09:02 <Qiming> both 438891 and 432587 are in
13:09:14 <yanyanhu_> got merged this afternoon
13:09:32 <Qiming> let's see if there are more patches coming in
13:09:33 <elynn> Need some tuning and address Qiming's -1 :)
13:09:46 <elynn> I think it's done for now
13:09:51 <Qiming> you can leave those to your backport work
13:09:55 <elynn> And I plan to move it to nova.server
13:10:07 <elynn> piece by piece
13:10:09 <Qiming> I believe the top priority is to make it work
13:10:16 <yanyanhu_> +1
13:10:30 <elynn> Actually xinhui did a demo internal
13:10:32 <Qiming> and make sure the summit sessions are well prepared
13:10:39 <elynn> successfully
13:11:24 <elynn> Use this vdu profile together with monitor from vmware, to create a NFV scenario .
13:11:33 <Qiming> nice!
13:11:55 <Qiming> moving on
13:12:03 <Qiming> engine improvement -- cluster check
13:12:17 <XueFeng> no update this week
13:12:21 <Qiming> are we working on self-destroyable actions?
13:12:28 <Qiming> okay
13:12:32 <Qiming> node adopt
13:12:38 <XueFeng> prepare for the meetup 2017.3.18
13:12:46 <Qiming> proposed a patch:
13:13:04 <Qiming> https://review.openstack.org/444817
13:13:24 <yanyanhu_> great
13:13:30 <yanyanhu_> this is what we are expecting
13:13:32 <Qiming> there are things very tricky
13:13:44 <Qiming> personality
13:13:55 <Qiming> is an attribute you cannot get back from a server
13:14:21 <Qiming> networks, we cannot get the original request if it was created from port ids
13:14:38 <Qiming> and, port id, even extracted, doesn't seem that useful
13:14:58 <Qiming> with elynn's suggestion, I'm only extracting network name
13:15:27 <XueFeng> Yes
13:15:32 <Qiming> the worst thing is about user_data
13:15:38 <Qiming> we really need them back
13:15:46 <elynn> I always thought we can not get user_data...
13:15:53 <Qiming> nova api microversion 2.3 added this support
13:15:57 <elynn> Since I didn't find a rest API for it...
13:16:18 <Qiming> however, the attribute is renamed to OS-EXT-SRV-ATTR:user_data ...
13:16:18 <elynn> okay, good to know
13:16:29 <yanyanhu_> yes, user_data is important for further scaling operation
13:16:30 <Qiming> and it is limited to admin users, as of now
13:16:45 <Qiming> talked to nova-api group, they are onto it.
13:17:08 <Qiming> they won't fix the name issue in near future, but they will fix the privilege restriction
13:17:22 <XueFeng> sounds good
13:17:45 <Qiming> from sdk side, brian came up with a hack: https://review.openstack.org/#/c/444933/
13:17:56 <Qiming> it is not an easy choice to make
13:18:08 <Qiming> things are always complicated when we are talking about nova
13:18:44 <Qiming> until that is released, we cannot get user_data back
13:19:06 <Qiming> another todo is about creating snapshot when adopting a server node
13:19:18 <Qiming> this is made optional
13:19:38 <Qiming> will need to work on profile level and then engine -> api -> sdk -> client path
13:19:47 <Qiming> moving on
13:19:58 <Qiming> RDO
13:20:01 <XueFeng> ok
13:20:20 <XueFeng> sorry, this week rdo is also no update
13:20:54 <Qiming> okay, pls keep pushing
13:20:59 <Qiming> next, health management
13:21:05 <XueFeng> Will
13:21:17 <Qiming> xinhui is not in?
13:21:27 <yanyanhu_> seems so
13:21:39 <yanyanhu_> she has been back in last week
13:21:52 <Qiming> alright, we have got a talk about enterprise monitoring + senlin + mistral
13:22:04 <Qiming> that story has to be made ready
13:22:09 <yanyanhu_> yes, there is a presentation on it
13:22:43 <Qiming> maybe we should move fencing support back to TODO list?
13:22:49 <Qiming> it is not a trivial job
13:22:59 <yanyanhu_> maybe another meet in vmware :P
13:22:59 <yanyanhu_> for the summit preparation
13:23:19 <Qiming> em, xinhui called me the other day
13:23:34 <Qiming> talking about having senlin make placement decisions
13:23:48 <Qiming> because we are already there, with quite a few policies
13:24:04 <yanyanhu_> agree
13:24:04 <yanyanhu_> placement policy?
13:24:15 <Qiming> her question was about how to make it work with the new placement api from nova
13:24:35 <Qiming> I don't have a vision on that either
13:24:42 <elynn> Xinhui is busy recent days and she is sick..
13:24:58 <Qiming> I'm not sure how the placement API is positioned, where it is heading
13:25:05 <yanyanhu_> so nova has new api for advanced placement operations?
13:25:20 <yanyanhu_> if so, that could be helpful
13:25:30 <Qiming> is it very ambitious to cover all aspects of placement decision? including network and storage factors?
13:25:44 <yanyanhu_> sure
13:25:47 <yanyanhu_> that is ambitious
13:26:07 <Qiming> or is it only about host resources and many also other multi-az, multi-region scheduling?
13:26:08 <yanyanhu_> especially for network
13:26:08 <elynn> yanyanhu_, yes, nova has a placement API in nova codes now.
13:26:30 <Qiming> it is mandatory if an devstack installation now
13:26:56 <Qiming> anyway, let's see what will happen
13:26:57 <elynn> I guess recent days she will get more details of this requirement, and later we could figure out how we fit in this requirement.
13:27:50 <Qiming> at the same time, I really don't want to waste time duplicating features from another project
13:28:09 <Qiming> okay, so we can stick to our own agenda
13:28:54 <elynn> yes, we won't reinvent the wheels.
13:28:58 <Qiming> we have less than one month to release p-1
13:29:06 <yanyanhu_> ...
13:29:08 <Qiming> +1
13:29:15 <XueFeng> Yes
13:29:29 <elynn> Just need to fill the gap.
13:29:34 <Qiming> we hope we can may operators life easier, not more painful
13:29:53 <Qiming> #link https://releases.openstack.org/pike/schedule.html
13:30:11 <Qiming> moving on?
13:30:15 <yanyanhu_> ok
13:30:17 <elynn> okay
13:30:26 <Qiming> I guess no progress on client functional tests?
13:30:38 <Qiming> though the gate job (non-voting) is ready
13:30:47 <XueFeng> Yes:)
13:30:59 <Qiming> okay
13:31:15 <Qiming> policy improvement, wrt LB policy and CLUSTER_RECOVER
13:31:31 <Ruijie> em, this can be removed ..
13:31:38 <Qiming> done?
13:31:57 <Qiming> or ... still some minor improvements needed?
13:32:03 <Ruijie> may need to improve the data
13:32:06 <XueFeng> After meetup will do all things hard
13:32:09 <XueFeng> :)
13:32:37 <Qiming> okay, thx
13:32:39 <Ruijie> yes Qiming, still some improvements needed, will look forword to it
13:33:01 <Qiming> leaving that item there for a while
13:33:18 <Ruijie> okay
13:33:22 <Qiming> NFV support is on the wishlist
13:33:41 <Qiming> got no news from Haiwei, although we have a talk on that
13:33:59 <Qiming> Xinhui's live demo is for that session, elynn ?
13:34:21 <elynn> For haiwei's session?
13:34:37 <elynn> No, xinhui's demo is for internal review.
13:34:39 <XueFeng> haiwei is busy, and he said he will do the patch in tacker
13:35:00 <elynn> But could do some modify and be prepare to other presentation.
13:35:04 <Qiming> okay
13:35:17 <Qiming> no matter what we are talking about
13:35:18 <XueFeng> And then we prepare for the session
13:35:38 <Qiming> it has to be in the master, for users to try out
13:36:00 <elynn> Cause it's not purely openstack, including some vmware software. But definitely for NFV.
13:36:32 <Qiming> okay, then  the openstack part has to be ready
13:36:55 <Qiming> and possibly an alternative to vmware software as a generic solution would be great
13:37:17 <Qiming> there is nothing wrong to present vendor specific solution
13:37:27 <XueFeng> Yes, that will be great
13:37:27 <elynn> :)
13:37:37 <Qiming> but a generic one would be more useful to most audience
13:37:46 <elynn> We can find a day to let her show us again.
13:37:53 <Qiming> cool.
13:38:10 <elynn> Until she is not busy and recover from cough .
13:38:12 <Qiming> anything else on pike work items, the etherpad?
13:38:29 <yanyanhu_> write a article for senlin[XueFeng Finished
13:38:30 <Qiming> I'm suffering too from coughing lately
13:38:32 <yanyanhu_> great job from xuefeng
13:38:58 <Ruijie> +1
13:38:59 <Qiming> would be nice if we have an English version, :)
13:39:00 <yanyanhu_> Qiming, take a good rest
13:39:24 <Qiming> cannot reset, man
13:39:32 <yanyanhu_> understand...
13:39:39 <yanyanhu_> really busy recently
13:39:47 <XueFeng> So we need a English version?
13:39:50 <Qiming> got some instructions to share your workload, just this afternoon
13:40:09 <yanyanhu_> Qiming, yes, I also got the call...
13:40:14 <yanyanhu_> need more discussion on it tomorrow
13:40:17 <Qiming> ok
13:40:22 <yanyanhu_> you know, about the handover
13:40:28 <Qiming> okay
13:40:28 <yanyanhu_> which will come soon
13:40:30 <Qiming> moving on
13:40:42 <elynn> handover what?
13:40:46 <Qiming> #topic pike goals
13:40:53 <XueFeng> QiMing
13:40:57 <yanyanhu_> elynn, you will get it soon :P
13:41:06 <elynn> senlin?
13:41:28 <Qiming> we talked about this very briefly last week
13:41:41 <XueFeng> ironic container adoption health improve ;do some use cases
13:41:49 <elynn> okay...bless it's a good news
13:41:51 <XueFeng> My option in pike
13:42:14 <Qiming> great.
13:42:23 <Qiming> more thoughts?
13:42:57 <XueFeng> container is hot now maybe
13:43:00 <Qiming> ironic has a bp, container is there for improvement, adoption is already started, health improvement needs update from xinhui
13:44:02 <XueFeng> Yes
13:44:05 <Qiming> XueFeng, when ironic support work has started, please help ensure it is tracked in the workitems etherpad
13:44:13 <yanyanhu_> in my mind, both ha and container are very important. For HA, we need a practical use case, for container, we need deployment and orchestration support
13:44:19 <XueFeng> And maybe some stories container in baremetel
13:44:47 <yanyanhu_> I mean something like k8s deployment(or at least something like compose)
13:44:53 <Qiming> container on baremetal would be next step when both components are stable
13:45:07 <Qiming> right
13:45:19 <Qiming> I'm thinking of a cluster config property
13:45:33 <XueFeng> Ok
13:45:46 <Qiming> introducing yet another abstraction is gonna make things difficult to understand
13:45:48 <XueFeng> Recently, some guys put into zun, and I talk with them
13:46:17 <elynn> Agree with you, Qiming
13:46:34 <Qiming> zun is good if it can really make the container runtime easy to use/manage
13:47:09 <Qiming> still a lot of things to do in the HA space
13:47:20 <Qiming> more thoughts?
13:47:23 <XueFeng> And we need to let them know senlin and zun
13:47:31 <yanyanhu_> yes, if it is reliable for managing container, will be really helpful
13:47:33 <XueFeng> Which is different
13:48:01 <Qiming> I think that team is aware of both projects' mission
13:48:24 <Qiming> I'd like to see closer integration happen earlier than later
13:48:54 <XueFeng> So we can integrate zun+senlin
13:48:57 <XueFeng> Right?
13:49:03 <Qiming> why not?
13:49:10 <XueFeng> Yes
13:49:32 <Qiming> #topic boston summit prep
13:50:05 <Qiming> I'm only included in one of the talks accepted, the senlin + mistral one
13:50:18 <Qiming> so that will be my top priority
13:50:43 <Qiming> I believe xinhui is involved in all three talks?
13:50:57 <XueFeng> Yes
13:51:10 <Qiming> maybe she will be the best driver for this
13:51:26 <Qiming> will sync with her offline
13:51:33 <elynn> :) you add a lot work to her.
13:51:50 <Qiming> or better yet, online, when she stops by the #senlin channel
13:51:57 <XueFeng> congratulate senlin:accepted three sessions in bostion summit.
13:52:12 <Qiming> elynn, I think she enjoys driving things
13:52:31 <yanyanhu> sorry just dropped
13:52:34 <Qiming> or, she may want to offload that to you, elynn
13:52:42 <XueFeng> /s/bostion/boston
13:52:48 <elynn> Qiming, I believe what you say.
13:53:01 <Qiming> :D
13:53:06 <XueFeng> HaHa
13:53:17 <elynn> I will handle all trivial things :)
13:53:36 <Qiming> alright, people need some believes, no matter what he/she is working on
13:53:58 <Qiming> #topic open discussions
13:54:24 <Qiming> since we cannot talk about talks without xinhui joining us
13:54:33 <Qiming> moving on to open discussions
13:54:58 <elynn> Will you go to boston summit Qiming ?
13:55:03 <yanyanhu_> what is the exact date of summit
13:55:15 <elynn> May 5-11
13:55:20 <yanyanhu_> May 08 - May 12
13:55:23 <elynn> May 8-11
13:55:25 <Qiming> https://review.openstack.org/#/c/445298/
13:55:35 <Qiming> \o/
13:55:39 <Qiming> I love pep8 errors
13:56:04 <yanyanhu_> LoL
13:56:24 <elynn> :D
13:56:31 <XueFeng> :)
13:56:43 <Qiming> it took me almost 3 hours to narrow this down to a pep8 error, :)
13:57:28 <Qiming> anything else, gentlemen?
13:57:34 <yanyanhu_> nope from me
13:58:04 <elynn> no~
13:58:22 <XueFeng> Hi all, I think  container is important in pike cycle:)
13:58:25 <Qiming> thanks for joining, I have saved one minute for you, remember it
13:58:33 <Qiming> #endmeeting
13:58:56 <Qiming> yanhan has to end the meeting
13:59:52 <yanyanhu> network connection is terrible...
14:00:03 <yanyanhu> hi, Qiming, has the meeting finished?
14:00:14 <yanyanhu> if so, I will end the meeting
14:00:37 <yanyanhu> ok, seems so
14:00:40 <yanyanhu> #endmeeting
14:01:37 <jlibosva> yanyanhu: maybe you need to rename to yanyanhu_ ?
14:01:39 <yanyanhu> #endmeeting