13:00:32 <Qiming> #startmeeting senlin
13:00:33 <openstack> Meeting started Tue Jun  6 13:00:32 2017 UTC and is due to finish in 60 minutes.  The chair is Qiming. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:34 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:37 <openstack> The meeting name has been set to 'senlin'
13:05:41 <Qiming> seems no one is in?
13:06:15 <XueFeng> hi QiMing
13:06:27 <Qiming> hi, XueFeng
13:06:36 <xinhuili> hi
13:06:41 <XueFeng> Meeting will start?
13:06:51 <Qiming> already started I think
13:06:55 <Qiming> :)
13:07:18 <Qiming> I'm terribly sorry for accidentally skipped two meetings during the past weeks
13:08:04 <XueFeng> No matter:)
13:08:13 <Qiming> both were due to my daughter
13:08:31 <Qiming> she was sick last week, I was in hospital ...
13:08:53 <Qiming> and we have had quite a few holidays since boston summit
13:09:08 <XueFeng> So we need your lead
13:09:13 <Qiming> let's get started, anyway
13:09:25 <XueFeng> OK
13:09:40 <Qiming> it doesn't have  to be me, when it is meeting time, anyone can start the meeting by typing '#startmeeting senlin' here
13:09:56 <Qiming> #topic pike work items
13:10:06 <Qiming> #link https://etherpad.openstack.org/p/senlin-pike-workitems
13:10:17 <Qiming> duno if elynn is online
13:10:29 <elynn> I'm here
13:10:37 <Qiming> I saw he was pushing a new patchset for the vdu profile
13:10:42 <Qiming> evening, elynn
13:11:07 <elynn> Oh, I almost thought you can't see my message...
13:11:11 <elynn> evening
13:11:29 <elynn> Yes, I push a init patch
13:11:33 <Qiming> https://review.openstack.org/#/c/467108/
13:11:50 <Qiming> everyone pls help review when possible
13:11:57 <elynn> Just porting some features from vdu to server profile.
13:12:08 <elynn> And fixed some unittests.
13:12:31 <elynn> Still need more unittests and integrated tests.
13:12:41 <Qiming> ah, right, it is a porting effort
13:12:46 <Qiming> okay
13:12:49 <elynn> I'm still working on it, just a little slow...
13:13:19 <Qiming> pretty big a change, will jump onto it this week
13:13:50 <Qiming> thanks for pushing this forward
13:14:04 <Qiming> next item: check action
13:14:15 <elynn> Hoping this patch don't breaking any existing functions, please review it thoroughly
13:14:28 <Qiming> no activity for a few weeks now: https://review.openstack.org/#/c/435822/
13:14:56 <Qiming> elynn, really hope so, but review itself cannot reveal all problems, I promise you, :)
13:15:14 <shark> hi~
13:15:15 <Qiming> XueFeng, still on that patch?
13:15:33 <Qiming> or you want a discussion on senlin channel later?
13:15:35 <Qiming> hi, shark
13:15:35 <XueFeng> hi,Qiming
13:15:53 <XueFeng> Yes ,need discuss
13:16:07 <XueFeng> in senlin channel later
13:16:19 <Qiming> alright, moving on
13:16:24 <Qiming> node adopt
13:16:34 <Qiming> almost finished the first round
13:16:44 <Qiming> need to add api test and functional test
13:16:49 <XueFeng> great
13:17:03 <Qiming> not sure if we can add integration test for this
13:17:03 <XueFeng> Will test it:)
13:17:20 <Qiming> there are quite a few holes in the current poc
13:17:28 <XueFeng> and shark is using it
13:17:47 <shark> yes
13:17:51 <Qiming> for most of them I have left some comments in the source code so that we won't forget them
13:18:11 <Qiming> so you mean it is already usable?
13:18:16 <Qiming> my goshhhhh
13:18:25 <shark> I need add some function
13:18:38 <Qiming> feel free to propose patches, shark
13:18:47 <Qiming> we (usually) don't bite
13:19:18 <Qiming> next item is about scaling improvement, Ruijie is onto it now
13:19:32 <Ruijie_> yes, effers are still needed
13:19:35 <Ruijie_> for deletion process
13:19:36 <Qiming> and Ruijie is also optimizing the DB interactions
13:19:46 <Qiming> ah, Hero is online
13:19:59 <Ruijie_> :)
13:19:59 <Qiming> okay
13:20:16 <Qiming> let's try get it fully landed in Pike
13:20:30 <Ruijie_> okay
13:21:06 <shark> I want to compete the bp existed-pool-support-in-lb-policy
13:21:07 <Qiming> Revise runtime_data implementation, I think Ruijie and I both did something in that space
13:21:22 <Qiming> no problem, shark
13:22:03 <Qiming> if you want that work thread tracked, please add it to the etherpad
13:22:33 <Qiming> backport to Ocata (the runtime_data optimization) seems pretty difficult
13:22:58 <shark> ok
13:23:01 <Qiming> next item: RDO packaging
13:23:15 <Qiming> is it working now, XueFeng ?
13:23:29 <XueFeng> sorry no process these days
13:23:43 <XueFeng> will continue to do it
13:23:51 <Qiming> okay
13:23:57 <Qiming> health management
13:24:23 <Qiming> I believe the master branch still needs some work regarding mistral workflow support
13:25:36 <Qiming> 'run_workflow()' is now a method of Node, but it is not invoked anywhere
13:25:48 <Qiming> I'll fix it
13:26:07 <XueFeng> ok
13:26:27 <Qiming> no progress on rally test or senlinclient functional test as far as I can tell
13:27:08 <Qiming> that's all for things on etherpad, anything to add, guys?
13:27:18 <XueFeng> rally test problem seems solved in rally project
13:27:35 <Qiming> oh really?
13:27:58 <XueFeng> Will check and update  etherpad
13:28:03 <Qiming> then the work item should be revised to 'add more rally test cases'?
13:28:10 <Qiming> sounds great, thanks
13:28:22 <XueFeng> yes
13:29:42 <Qiming> okay, moving on
13:29:56 <Qiming> #topic boston summit recap
13:30:11 <Qiming> anything new to share with team after the boston summit?
13:30:43 <Qiming> we had three sessions there, presentation was well prepared
13:31:13 <Qiming> however, the attendance was not exciting
13:31:31 <XueFeng> QiMing, I want to know the session by you and xinhui
13:31:53 <Qiming> one of the reasons could be that we could have stress more on problems solved than the projects/services backing that solution
13:32:33 <Qiming> most of the materials were prepared by xinhui
13:32:55 <Qiming> I was there just to repeat "what senlin is about" ...
13:33:50 <XueFeng> I have watched that video
13:34:07 <Qiming> a million thanks to xinhui and elynn
13:34:47 <XueFeng> yes
13:34:50 <Qiming> it was almost 1 month ago, now it is time for a new milestone pike-2
13:35:00 <Qiming> we about cutting pike-2 this week
13:35:23 <Qiming> please help scan the review backlog and approve things you feel good about
13:35:38 <XueFeng> ok , we wil
13:35:44 <Qiming> thanks.
13:36:03 <Qiming> next thing we need help is about blueprints review
13:36:13 <Qiming> #topic blueprints to review
13:36:23 <Qiming> we have got quite a few proposed recently
13:36:48 <Qiming> some can be merged, some needs more discussion, others are already good to go
13:37:08 <Qiming> for example, https://blueprints.launchpad.net/senlin/+spec/support-node-protect-operation
13:37:23 <Qiming> this one needs some clarification then it is good to go
13:37:47 <Qiming> this one: https://blueprints.launchpad.net/senlin/+spec/improve-vm-name
13:37:53 <XueFeng> ok.seems good
13:37:58 <Qiming> is about naming VMs
13:38:04 <Ruijie_> Qiming, for this process, we are tring to use policy data first
13:38:08 <Qiming> we need a design for that support
13:38:15 <XueFeng> yes, vm name need improve
13:38:32 <Qiming> Ruijie_, which one?
13:38:34 <Ruijie_> maybe we can change to use request.body first, so that the process is much easier to be controlled?
13:38:37 <Qiming> node proection?
13:38:41 <Ruijie_> about the bp
13:39:10 <Ruijie_> it says that we want to protect the node not to be destroyed by scaling actions
13:39:38 <Qiming> well, implementation details can be discussed during code review
13:40:00 <Qiming> what I'm curious about is the scope of such a 'locked' tag
13:40:28 <Qiming> is it only designed to protect node from being deleted, or we can use it for guarding node update as well?
13:40:37 <Ruijie_> I'd suggest we use request parameter to controll it, will leave comments ~
13:41:22 <Qiming> maybe a 'locked' or 'protected' node should be tagged so in database,
13:41:27 <elynn> Maybe adding a new property named 'protected'?
13:41:46 <Qiming> yes, that is about the implementation
13:42:12 <Qiming> we can use new property, we can add tag support, we can use metadata, whatever works for this
13:42:32 <Qiming> but the first thing I want to clarify is the definition of 'protected'
13:42:50 <elynn> okay
13:43:00 <Qiming> then we can together figure out how big a scope is such a "lock"
13:43:14 <Qiming> and its impact on cluster/node actions and policies
13:43:26 <elynn> yes
13:43:51 <Qiming> I have talked to Hongbin on this, but he said he is busy on his thesis work ...
13:44:15 <Qiming> my suggestion was that he draft a spec for team to review, and comment
13:44:30 <Qiming> the same goes with VM naming
13:44:37 <Qiming> current default naming is terrible
13:44:53 <Qiming> we need a better solution
13:45:25 <Qiming> there are other bps for review as well: https://blueprints.launchpad.net/senlin
13:45:28 <chenyb4_> I have some time to work
13:45:35 <Qiming> pls feel free to take a look on them
13:46:00 <Qiming> cool, chenyb4_, maybe you can grab a few BPs to work on, :)
13:46:21 <Qiming> post your questions to senlin channel when you need help
13:46:31 <chenyb4_> ok
13:46:58 <Qiming> alright, that's all on my mind for the meeting today
13:47:07 <Qiming> #topic open discussions
13:47:16 <Qiming> please speak up
13:47:23 <Qiming> we still have some time, :D
13:47:27 <shark> I want to discuss health policy how to handle the adopt node
13:48:08 <Qiming> how about just treat them the same as other nodes?
13:49:04 <XueFeng> yes, we can think them the same as other node.
13:49:06 <shark> we rebuild user vm,is this good
13:49:07 <XueFeng> nodes
13:49:33 <chenyb4_> I don't understand profile support snapshot and restore, the profile is about single vm configure, so the snapshot how can i create?
13:50:32 <Qiming> snapshot/restore is an operation supported by backend service, modeled into a profile operation in senlin
13:50:49 <Qiming> just compare it to 'update'
13:50:57 <shark> how about remove the node from senlin?
13:51:15 <Qiming> shark, you can do that
13:51:28 <Qiming> just as if you have nevered created such a node
13:52:16 <Qiming> wait ... did you mean delete a senlin node without deleting the physical resource (which could be a VM)?
13:52:27 <shark> yes
13:52:41 <Qiming> why are you doing that?
13:53:18 <Qiming> you can leave it as an orphan node (not member of any cluster) in senlin
13:53:52 <Qiming> I will not call it 'delete', it sounds more like an 'abandon' operation
13:54:07 <shark> yes
13:54:23 <Qiming> I'm interested in the use case -- why do you need it
13:54:23 <shark> becauser it is a adopt node
13:55:10 <Qiming> so ... we have to define "abandon" because we have defined "adopt" ?
13:55:45 <Qiming> then the design looks beautiful? :D
13:56:18 <XueFeng> sounds feasible
13:56:46 <Qiming> it is doable, although ... I'm not sure it would be useful
13:56:54 <Qiming> I'm not against it, to be honest
13:57:13 <XueFeng> ok
13:57:41 <Qiming> anything else?
13:57:46 <Qiming> 3 mins left
13:57:46 <XueFeng> Qiming, I have a last question today
13:57:48 <elynn> Since we are going to have 'protected' node
13:58:09 <Ruijie_> and then force delete ..
13:58:14 <elynn> maybe we should also need to consider health policy on them.
13:58:18 <XueFeng> Intergation enterprise monitoring product, senlin and mistral for auto-healing.Can this session fall to the ground? I would like to refer to this architecture deployment
13:58:24 <Qiming> elynn, sure
13:58:41 <Qiming> that is why I think we need a spec for more discussions on the implications
13:58:57 <Qiming> XueFeng, it is
13:59:03 <Qiming> it is real
13:59:24 <Qiming> buy xinhui a rose, she will tell you the full story
13:59:44 <Qiming> time's up, guys, thanks for joining, gooooooood night
13:59:45 <XueFeng> haha
13:59:48 <Qiming> #endmeeting