13:00:11 <yanyanhu> #startmeeting senlin
13:00:11 <openstack> Meeting started Tue Feb  7 13:00:11 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:13 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:15 <openstack> The meeting name has been set to 'senlin'
13:00:27 <Qiming> hello
13:00:28 <yanyanhu> hello
13:00:31 <yanyanhu> hi, Qiming
13:01:15 <yanyanhu> I guess some guys are still in vacation :)
13:01:38 <Qiming> yep
13:01:49 <elynn> hi
13:01:52 <yanyanhu> hi, elynn
13:02:29 <elynn> Saw xinhui's email, she might be on vacation.
13:02:36 <yanyanhu> lets wait for a while for other attenders
13:02:40 <yanyanhu> elynn, yep
13:03:49 <yanyanhu> ok, lets get started
13:03:51 <yanyanhu> https://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Agenda_.282017-02-07_1300_UTC.29
13:04:04 <yanyanhu> here is the agenda, please feel free to add items
13:04:10 <yanyanhu> just a short one :)
13:04:31 <yanyanhu> #topic Ocata final RC
13:04:41 <yanyanhu> Ocata final RC will be in two weeks
13:05:00 <yanyanhu> and we have cut the rc1 release and the stable/ocata branch was built on it
13:05:30 <elynn> nice
13:05:34 <yanyanhu> if there is any critical fix coming in next two weeks, we can consider to port them back
13:05:53 <yanyanhu> so pike cycle will come soon :)
13:05:56 <Qiming> I've already merged two backports
13:06:14 <yanyanhu> Qiming, cool :)
13:06:22 <yanyanhu> so the back port will be done automatically?
13:06:36 <yanyanhu> at the end of O cycle
13:06:38 <Qiming> ... no
13:06:55 <yanyanhu> so it needs release team's help?
13:07:08 <Qiming> cherry pick, propose, review, gate, approve, merge
13:07:24 <yanyanhu> I see
13:08:41 <yanyanhu> and I noticed that doug send a mail said they will wait for a while for several projects who haven't had ocata release candidiate yet
13:08:55 <yanyanhu> so after that, the cycle will be switched to pike?
13:09:28 <Qiming> after official release
13:09:43 <yanyanhu> I see
13:10:31 <yanyanhu> ok, lets move to next topic
13:10:42 <yanyanhu> #topic Pike workitems
13:10:56 <yanyanhu> I just initialized an etherpad for senlin pike workitem
13:11:02 <yanyanhu> https://etherpad.openstack.org/p/senlin-pike-workitems
13:11:16 <yanyanhu> and moved those backlogs from ocata workitems list
13:11:47 <Qiming> em ... we are not in pike cycle yet
13:12:20 <Qiming> but it is fine if we just keep a single etherpad for progress tracking
13:12:30 <yanyanhu> Qiming, yes, so before pike cycle starts, lets keep using ocata page :)
13:12:48 <yanyanhu> https://etherpad.openstack.org/p/senlin-ocata-workitems
13:13:05 <yanyanhu> they are same now
13:13:30 <yanyanhu> so I will revise the pike list after ocata cycle is done
13:13:45 <yanyanhu> lets quick go through the list?
13:13:51 <yanyanhu> hi, XueFeng
13:14:04 <XueFeng> hi,YanYan
13:14:11 <yanyanhu> "Feature Rich" Nova Server
13:14:11 <XueFeng> Sorry for late
13:14:17 <yanyanhu> XueFeng, no problem
13:14:25 <yanyanhu> elynn is working on it
13:14:32 <elynn> yes,
13:14:40 <yanyanhu> and one of our summit proposal will be based on it
13:14:48 <Qiming> I tried to review it ... but it is difficult
13:14:54 <elynn> basic support for rich network properties is done
13:15:16 <Qiming> it is not easy to tell which are newly added code
13:15:28 <elynn> Qiming, use diff and compare it with original server profile...
13:15:43 <elynn> Or should I just change the original server profile?
13:16:00 <Qiming> that means the comparison cannot be done using gerrit directly?
13:16:06 <yanyanhu> hmm, it is difficult if it is totally a new file
13:16:45 <Qiming> another workaround is to propose a copy of server profile
13:16:52 <yanyanhu> or we can copy the original nova server profile to contribute dir in the first patch
13:16:52 <Qiming> then rebase your changes onto it
13:16:55 <yanyanhu> then merge it
13:17:04 <elynn> a copy of server profile?
13:17:06 <yanyanhu> then propose the current change based on it?
13:17:14 <elynn> how to do it with git?
13:17:14 <yanyanhu> Qiming, :)
13:17:23 <yanyanhu> exact what I mean
13:17:41 <elynn> okay, I see.
13:17:57 <elynn> That would be a workaround.
13:18:01 <yanyanhu> then we can easily tell the difference
13:18:05 <elynn> could do that.
13:18:41 <elynn> btw, I'm working on the handle_update part for networks.
13:18:52 <yanyanhu> ok
13:19:04 <elynn> and bran from vmware is testing it in mitaka version of openstack.
13:19:24 <yanyanhu> it is for updating network resource property?
13:19:37 <elynn> yes, yanyanhu
13:19:48 <elynn> update is not yet done.
13:19:53 <yanyanhu> I see
13:19:58 <elynn> and volume is not added yet.
13:20:23 <elynn> I'm not sure if volume is necessary.
13:20:42 <yanyanhu> may need to talk with xinhui about it
13:20:58 <yanyanhu> to see what is the requirement from nfv app
13:21:09 <elynn> yes, after her vacation :)
13:21:14 <yanyanhu> yep :)
13:21:49 <yanyanhu> ok, if there is no more question about this work, lets move on
13:21:51 <Qiming> have any of you encountered this ? https://bugs.launchpad.net/senlin/+bug/1662053
13:21:51 <openstack> Launchpad bug 1662053 in senlin "node-show -D image error" [Undecided,New] - Assigned to Yuanbin.Chen (yuanbin.chen)
13:22:13 <Qiming> it is also related to nova server profile
13:22:20 <yanyanhu> no
13:22:33 <yanyanhu> we haven't used block_device_mapping_v2 before
13:22:43 <Qiming> the complaint is that if a server has a volume attached
13:22:57 <Qiming> the returned server data JSON will look different
13:23:06 <yanyanhu> yes, seems so
13:23:11 <Qiming> the image key doesn't have an id entry any more
13:23:27 <yanyanhu> elynn, have you met this issue before?
13:23:39 <elynn> never used this property
13:23:41 <elynn> before.
13:23:44 <yanyanhu> when vm node has extra volume attached
13:24:12 <Qiming> okay
13:24:28 <Qiming> need to check nova api docs there
13:24:40 <yanyanhu> ok
13:25:19 <yanyanhu> so next work item
13:25:22 <yanyanhu> Improve tempest API test
13:25:27 <yanyanhu> ruijie has been working on it
13:25:43 <yanyanhu> he is not here now, so will talk with him to see the progress
13:26:01 <yanyanhu> some works have been done before spring festival
13:26:23 <yanyanhu> Engine Improvement
13:26:38 <yanyanhu> automatic action purge
13:26:53 <yanyanhu> haven't picked up the patch yet
13:27:01 <yanyanhu> will revisit it soon
13:27:21 <yanyanhu> and hongbao has started working on db purge
13:27:44 <Qiming> that patch is still very dirty
13:27:54 <yanyanhu> https://review.openstack.org/420666
13:27:56 <yanyanhu> this one
13:28:19 <yanyanhu> yes, still some questions there
13:28:33 <Qiming> I don't get the requirement about so many parameters
13:28:49 <Qiming> purge events based on object status?
13:28:52 <yanyanhu> actually me neither, so maybe we can consider to start from a simple one
13:28:56 <Qiming> based on object names?
13:29:06 <yanyanhu> and add more params support if there is requirement
13:29:15 <Qiming> right
13:29:35 <Qiming> in the latest patch, the age is still a 'nargs='?'' parameter
13:29:47 <Qiming> that means I can specify --age 3 --age 4
13:30:01 <yanyanhu> that is not beautiful
13:30:08 <Qiming> it won't work actually
13:30:27 <yanyanhu> right
13:30:40 <Qiming> it has to be a single value
13:31:44 <yanyanhu> ok, lets talk with hongbao to see how to improve this patch
13:32:19 <yanyanhu> ok next one
13:32:22 <yanyanhu> cluster check
13:32:26 <yanyanhu> hi, XueFeng
13:32:47 <XueFeng> hi
13:32:57 <yanyanhu> this patch https://review.openstack.org/#/c/421615/
13:33:45 <XueFeng> Will modify again
13:33:50 <yanyanhu> it is for decreasing the action records
13:34:14 <yanyanhu> XueFeng, thanks, I guess it is close to be done
13:34:55 <yanyanhu> and also this one :)
13:34:57 <yanyanhu> https://review.openstack.org/#/c/424073/
13:35:55 <yanyanhu> ok, next
13:35:58 <yanyanhu> Health Management
13:36:06 <yanyanhu> will sync with xinhui after she comes back
13:36:37 <XueFeng> About health management sitll has some problem
13:37:13 <yanyanhu> yes
13:37:27 <XueFeng> The new field in health_registry 'enabled' is confused
13:37:56 <Qiming> it is an internal field for use by the health manager only
13:38:18 <Qiming> the health registry table is designed to be used by health manager only
13:38:28 <XueFeng> en
13:38:34 <Qiming> the long term goal is to separate health registry into a separate service
13:39:01 <Qiming> we are trying to make it as independent as possible
13:39:21 <XueFeng> Now we only set this field =1
13:39:22 <yanyanhu> Qiming, you mean splitting it from engine?
13:39:37 <Qiming> yes
13:39:58 <XueFeng> That mean we do prepare for later?
13:40:08 <Qiming> health manager, when doing polling, may introduce a lot of CPU overhead
13:40:09 <XueFeng> s/mean/means
13:40:23 <Qiming> it will hurt the senlin-engine performance
13:40:28 <XueFeng> Yes
13:40:38 <yanyanhu> it is reasonable
13:41:00 <yanyanhu> maybe we can start a bp for it in pike cycle
13:41:19 <Qiming> yep, if there are hands working on it
13:41:23 <XueFeng> I mentioned this before
13:41:39 <yanyanhu> nice
13:41:47 <Qiming> health management and container support, these are the top two priorities for Pike in my minde
13:41:52 <Qiming> s/minde/mind
13:42:16 <yanyanhu> yes, ha definitely should be
13:42:28 <XueFeng> Also, another problem.In current health_registry pick desinge
13:43:06 <XueFeng> It can't support concurrent mechanism
13:44:11 <Qiming> you mean ? two health manager pick the same cluster for monitoring?
13:44:38 <XueFeng> we can't loadbalance health mangager to many engine
13:44:51 <XueFeng> engines
13:45:36 <yanyanhu> you mean?
13:46:33 <yanyanhu> ok, lets talk more about it offline
13:46:39 <Qiming> the notify() method in the health-manager module has a engine_id which can be set to None
13:46:48 <XueFeng> ok
13:46:59 <XueFeng> will discuss more later
13:47:06 <Qiming> if it is set to None, any health manager can pick that cluster for monitoring
13:47:12 <yanyanhu> engine_id=none means broadcasting?
13:47:17 <Qiming> yes
13:47:31 <Qiming> it is a trivial issue
13:48:42 <yanyanhu> ok, maybe we can have further disucssion later. we have only 10 minutes left
13:49:06 <yanyanhu> document for HA policy
13:49:08 <yanyanhu> has been done
13:49:38 <yanyanhu> https://review.openstack.org/423174
13:49:47 <yanyanhu> ok next one
13:49:52 <yanyanhu> functional test for client
13:50:01 <yanyanhu> hasn't been started yet
13:50:12 <yanyanhu> maybe we can postpone it to next cycle
13:50:19 <XueFeng> OK
13:50:28 <yanyanhu> no maybe, the final release of senlinclient has been done actually :)
13:50:40 <yanyanhu> ok, next one
13:50:41 <XueFeng> :)
13:50:49 <yanyanhu> container profile
13:51:00 <yanyanhu> will be another important work item in pike cycle
13:51:08 <yanyanhu> will talk with haiwe about it later
13:51:23 <yanyanhu> ok, that's all items in the list
13:51:41 <yanyanhu> and please pay attention on those new items added to TODO.rst
13:52:09 <yanyanhu> and pick up them freely if you are interested on them
13:52:15 <XueFeng> Will
13:52:24 <yanyanhu> thanks :)
13:52:28 <yanyanhu> #topic PTL election result
13:52:38 <yanyanhu> pike ptl election has been done
13:52:50 <yanyanhu> Qiming will play the role in next cycle :)
13:53:11 <XueFeng> congratulation
13:53:13 <elynn> congratulates ;)
13:53:17 <yanyanhu> :)
13:53:20 <XueFeng> :)
13:53:30 <yanyanhu> thanks god, u're back, haha
13:53:32 <Qiming> I figured ... that no one was stepping up
13:53:34 <elynn> The king is back.
13:53:38 <yanyanhu> yep
13:53:51 <Qiming> and the deadline has passed, ...
13:54:08 <yanyanhu> yes...
13:54:19 <yanyanhu> it was in spring vacation
13:54:22 <Qiming> seems no one enjoys this servant role, :)
13:54:33 <elynn> I figured ... that some one will step up ;)
13:54:57 <Qiming> ft!
13:55:01 <yanyanhu> anyone, welcome back, to lead us :)
13:55:16 <Qiming> someone has to jump into this
13:55:17 <XueFeng> :)
13:55:29 <Qiming> let it be me >:
13:55:43 <yanyanhu> cool
13:55:50 <elynn> Qiming! Qiming! Qiming!
13:55:55 <elynn> :D
13:56:13 <elynn> See, you are the best.
13:56:46 <Qiming> it is always about a team work
13:57:02 <Qiming> be prepared, next one could be you
13:57:17 <elynn> We will be with you :)
13:57:31 <yanyanhu> :)
13:57:44 <yanyanhu> ok, those are all topics in the agenda
13:57:48 <yanyanhu> open discussion now
13:57:52 <yanyanhu> #open discussion
13:58:00 <Qiming> next week is final rc
13:58:14 <Qiming> and the week after that would be final release
13:58:32 <yanyanhu> #topic open discussion
13:58:35 <Qiming> I'll try get listener to heat events implemented
13:58:47 <XueFeng> About rdo if we need to do?
13:58:49 <Qiming> so the loop is closed
13:58:49 <yanyanhu> the first two patches have landed
13:59:06 <yanyanhu> yes, looks some guys need it
13:59:07 <Qiming> XueFeng, we need volunteers to work on that
13:59:16 <Qiming> RDO needs a maintainer for a project
13:59:29 <yanyanhu> no have to be redhat guy?
13:59:30 <XueFeng> Yes
13:59:35 <yanyanhu> s/no/not
13:59:37 <Qiming> time's up, maybe can continue on #senlin
13:59:42 <yanyanhu> ok
13:59:45 <XueFeng> Ok
13:59:46 <elynn> okay
13:59:49 <Qiming> doesn't have to be RH employee
13:59:56 <yanyanhu> thanks you guys for joining, lets move back to senlin channel
13:59:58 <yanyanhu> I see
14:00:08 <yanyanhu> #endmeeting