13:00:08 #startmeeting senlin 13:00:09 Meeting started Tue Feb 21 13:00:08 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:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:00:12 The meeting name has been set to 'senlin' 13:00:17 hi 13:00:31 hi yanyanhu 13:00:37 hi, ruijie_, evening 13:00:38 hello 13:00:42 hi, Qiming 13:01:01 Evening all :) 13:01:07 :) 13:01:15 lets wait for a while for other attenders 13:02:32 ok, lets get started 13:02:35 https://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Agenda_.282017-02-21_1300_UTC.29 13:02:38 o/ 13:02:43 hi, elynn 13:02:47 https://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Agenda_.282017-02-21_1300_UTC.29 13:02:51 here is the agenda 13:02:55 please feel free to add items 13:03:09 #topic Ocata workitems 13:03:18 https://etherpad.openstack.org/p/senlin-ocata-workitems 13:03:26 the master is actually pike now 13:03:46 and ocata final release will be done in this week 13:03:59 lets go through the list 13:04:11 "Feature Rich" Nova Server 13:04:17 hi, elynn, your turn 13:04:21 okay 13:04:34 The patch for ports update is under reviewing 13:04:40 I update it yesterday. 13:04:41 https://review.openstack.org/432587 13:04:42 this one 13:05:11 It is a little complicated. 13:05:25 about? 13:05:36 about the ports update logic 13:06:07 But could work I think, I tested it in some simple cases. 13:06:09 so what kind of update will be supported in this initial version? 13:06:25 e.g. replacing an existing port with a new one 13:06:27 for VM 13:06:39 For now, only replacing will supported. 13:06:46 be supported. 13:06:47 I see 13:07:00 so the final goal is support the update of network spec 13:07:11 I mean entire network property of vm 13:07:45 yea 13:07:58 although that seems very difficult for some cases 13:08:04 haven't figure out how to update an existing port, since using network property to find existing port is not easy. 13:08:49 But for vdu scenario , update is not the important part. 13:08:49 if the existing vm port was defined as "port" directly, that is easy, right? 13:09:07 the deployment is more critical? 13:09:20 yes, yanyanhu , that's one case 13:09:32 Yes, the deployment is more critical. 13:09:45 I see 13:09:46 Especially the network orchestration. 13:10:15 how is the progress of deployment support? 13:10:27 Bran has a template 13:10:54 or maybe we can temporarily put the update work aside before the deployment support can meet our requirement? 13:10:59 to orchestrate senlin vdu cluster and also routers , networks, security groups. 13:11:28 you guys can focus on the orchestration part at the beginning I guess? 13:12:04 Yes, I debug this template with bran these days. 13:12:17 I think still some problems need to fix in heat... 13:12:43 For senile profile, it's enough for now. 13:12:55 in heat? You mean the entire deployment progress will be initialized by heat 13:13:00 initialized and managed by heat 13:13:14 Some problems about the sequence for creating and deleting resources. 13:13:14 and senlin cluster/node deployment will be part of it 13:13:25 yanyanhu, yes 13:13:32 I see 13:13:43 The template will create needed routers, security groups 13:13:48 and also networks 13:13:58 yes, for routers and networks 13:14:07 And then using them to fill in the senile profile. 13:14:15 understand 13:14:30 oh, btw, have you touched the application deployment yet? 13:14:41 Then senlin will create ports floating IPs. 13:14:43 I mean those nfv application running inside vms 13:15:04 They have some simple user_data, I think bran haven't touch that yet. 13:15:11 ok 13:15:23 umm, seems a lot of work to do 13:15:42 so maybe you can consider to focus on building the workflow of vdu deployment first 13:15:45 yes, some debug work need to be done. 13:16:01 after it can be done successfully, then we start to work on update functionality 13:16:25 since network property update is really very complicated I think... 13:16:52 yes 13:17:22 we can have a basic one 13:17:25 then evolve it. 13:17:29 yes 13:17:48 having a basic one is important 13:18:20 so thanks a lot for working on this and I think you can sync with xinhui to ask for her idea as well 13:18:29 she is in atlanta now I guess :) 13:18:29 Add some todos to my patch later :) 13:18:39 elynn, thanks :) 13:18:47 np 13:18:55 just doing my job. 13:19:03 :) 13:19:12 ok, any more question about this item? 13:19:32 lets move on 13:19:34 Engine Improvement 13:19:43 xuefeng is not here? 13:20:09 some works have been done in last week I think 13:20:21 especially some bug fixes about health manager 13:20:23 yep, 431401 is in 13:20:46 yes 13:20:55 424073 is in 13:21:05 but we will keep looking at/testing it 13:21:35 ok 13:21:50 and those two about health resigtry claim bug 13:22:14 one thing left is about the reduction of CLUSTER_CHECK/NODE_CHECK actions 13:22:36 https://review.openstack.org/435822 13:22:37 this one 13:22:53 right 13:23:41 hi, Qiming, should we backport this patch to ocata/stable? 13:23:42 https://review.openstack.org/435658 13:24:00 it is part of health registry fix 13:24:11 and this one https://review.openstack.org/436060 13:24:26 looking 13:25:46 em, all critical bug fixes have been backported I think 13:25:56 nice 13:26:05 so we are ready for shipping ocata release 13:26:45 and btw, many thanks for your help on backporting all those patches last friday :) 13:26:45 https://review.openstack.org/#/q/project:openstack/senlin+status:open 13:27:15 yes, looks pretty clean now 13:27:15 just a few of them needs some extra merge work 13:27:35 most were just a few mouse clicks and idle wait 13:27:43 great :) 13:28:19 so, lets move to next item? 13:28:34 Add senlin to RDO 13:28:34 np 13:28:43 no progress yet I guess 13:28:53 I think xuefeng hasn't got time to work on it yet 13:29:12 next one 13:29:13 Health Management 13:29:21 it'd be great if someone from from ZTE can sign on that role 13:29:36 yes, last meeting, xuefeng mentioned that 13:29:40 as a maintainer (focal point) of senlin in RDO 13:29:45 so hope some one can grant some hands here 13:30:00 it won't be a huge workload 13:30:24 just like what zigo did in debian? 13:30:29 the liaison will be pinged if things are broken at rdo side 13:30:39 we don't need packaging them at all 13:30:45 I see 13:30:49 generating rpm is straighforward 13:31:18 will talk with xuefeng later to see how he think about it 13:31:46 for health management, I guess there is also no progess? 13:31:56 since xinhui is traveling for ptg 13:32:03 hope she can bring us some news 13:32:15 no progress from my side 13:32:25 especially those work collaborated with mistral and also octavia 13:32:28 mistral workflow driver is in 13:32:28 Qiming, ok 13:32:45 ok 13:32:47 right, we need to sync with her next week 13:32:57 yes, maybe we can find a time to talk with her 13:33:03 through call or mail 13:33:34 to see the progress in her side and whether she needs any help 13:33:41 on the collaboration 13:34:04 ok, lets move on 13:34:11 Documentation 13:34:21 Qiming, I think you added lots of doc last week 13:34:25 for those policies 13:34:33 and they are all in the final rc now 13:34:46 em ... I think all policy types have a basic reference doc now 13:34:52 cool! 13:34:56 we can improve them later 13:35:01 that will be very helpful for users and also developers 13:35:04 yes 13:35:10 many thanks 13:35:20 I took the liberty to merge them quickly so they can be released in time 13:35:38 sure 13:35:42 no problem 13:36:20 ok, senlinclient 13:36:31 tried to setup the gate job for senlinclient functional test 13:36:32 https://review.openstack.org/#/c/436338/ 13:36:38 the patch is still under review 13:36:54 after that is done, we can work on functional test cases locally 13:36:58 need another +2 13:37:01 and add it to tox test list 13:37:15 Qiming, yes 13:37:20 hope it works as expected 13:37:30 will talk with xuefeng about it 13:37:37 to give him some guide 13:38:04 and those two patches listed in the etherpad have been done I think 13:38:12 so will remove them from the list 13:38:41 ok, next one 13:38:45 profile for container 13:38:53 haiwei is not here 13:39:07 guess we need more attention on this work in pike cycle 13:39:20 yup 13:39:25 we need hands on it 13:40:18 lets think more about it 13:40:53 sorry, just disconnected 13:41:02 win10 is insanely unstable... 13:41:24 another thing we may want to do is about a refresh of the core team 13:41:25 ok, that's all items in the list I think 13:41:44 Qiming, yes, any thoughts about this 13:42:22 or we encourage commits/reviews first 13:42:37 yes, that sounds reasonable 13:42:42 there are quite a few idle cores 13:43:16 maybe we can sync with them to see their current status 13:43:22 let's keep thinking about this 13:43:28 ok 13:43:43 ok, lets move to next topic 13:43:52 #topic Ocata final rc and Ocata release 13:44:08 so ocata final rc has been done and final release will be done by the end of this week 13:44:17 https://releases.openstack.org/ocata/schedule.html 13:44:25 then we formally enter pike cycle I guess? 13:44:45 yep, starting next week I think 13:44:46 anyway, the current master is pike now 13:44:58 it will last 8 month? 13:45:03 or 6 month as usual 13:45:13 in theory, all work done during the the past weeks should be released in pike 13:45:13 since ocata only last 4 month I think 13:45:20 Qiming, yes 13:45:22 don't know 13:45:27 it is a chaos 13:45:33 ok... 13:45:35 really lost 13:45:39 lets wait for the formal schedule 13:45:44 don't know what the community is heading 13:45:55 s/what/where/ 13:46:10 #topci open discussion 13:46:14 open discussion now 13:46:22 #topic open discussion 13:47:00 any more topics from you guys? 13:47:04 I don't have more 13:47:19 trapped by a lot of k8s details 13:47:38 ... 13:47:48 that is a hard work... 13:47:52 good luck for us 13:48:09 it is not for the poc 13:48:17 I'm also trapped by some stuff... really headache... 13:48:24 it is about an emerging trend 13:48:26 for accelerator support? 13:48:36 related 13:48:41 ok 13:48:43 So you are working on k8s? 13:49:14 just started 13:49:18 have to move on 13:49:33 new start point :) 13:49:35 losing my faith gradually on openstack 13:49:36 for all of us 13:50:14 :) have you think about any possibility to combine senlin and k8s? 13:50:27 looking at that as well 13:50:35 k8s has a cloudprovider model 13:50:41 where it needs a cluster api 13:50:46 it is empty there 13:51:04 the barrier is that we don't have a master node from any clusters today 13:51:11 that can be fixed 13:51:27 but for more details, you have to wait, ;P 13:51:44 hmm, willing to learn more from you guys :) 13:51:53 When you are ready to share. 13:52:12 :) 13:52:22 ok, I think that's all for today 13:52:29 thanks all you guys for joining 13:52:32 there are many fields the code quality is good, there are other areas ... not the case 13:52:40 good night guys 13:52:48 good night! 13:52:49 will keep working on senlin anyway 13:52:51 have a good night :) 13:52:51 Qiming, have the same feeling 13:52:52 not for openstack 13:53:15 have a good night too 13:53:20 talk to you later 13:53:28 bye 13:53:34 bye 13:53:36 #endmeeting