13:00:57 #startmeeting senlin 13:00:58 Meeting started Tue Jul 11 13:00:57 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:59 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:01:01 The meeting name has been set to 'senlin' 13:01:15 evening, guys 13:01:39 hi,all 13:03:04 hi 13:03:04 anyone online? 13:03:09 hi, elynn 13:03:16 hi ,Qiming 13:03:40 Parallel attending other meetings at the same time... 13:03:44 hi, everyone 13:03:48 Thanks you drafting the agenda, XueFeng 13:03:59 hi xinhui and ruijie 13:04:05 let's get started 13:04:13 :) 13:04:13 #topic agenda 13:04:26 #link https://wiki.openstack.org/wiki/Meetings/SenlinAgenda 13:04:27 h 13:04:28 hi 13:04:32 Hi, Qiming ,my pleasure 13:04:42 pls add items if you have one 13:04:55 #topic pike work items 13:05:13 let's see if there are any updates on the work items etherpad 13:05:19 #link https://etherpad.openstack.org/p/senlin-pike-workitems 13:05:22 hi Guest53985, 13:05:44 just noticed the new item about API test 13:05:46 use /nick name can change you nick 13:06:21 but no one has yet claimed that item 13:07:03 elynn has committed a new patch to "feature rich nova server" 13:07:31 https://review.openstack.org/467108 13:07:35 I test it locally today, and I think it could work as expected. 13:07:37 it is still a WIP 13:08:08 I didn't add any version information to those new properties, 13:08:17 I think liyi is test api and do pathch for the doc. We can leave a comment in his patch 13:08:19 So I just leave it as WIP 13:08:20 486 lines added to the server profile, not counting the test cases, :) 13:08:38 got it, elynn 13:08:59 Guest53985 is liyi probably? 13:09:01 What do you suggest about adding version info to those new properties? 13:10:16 ideally, I'd suggest we port all profile implementation to oslo.versionedobjects 13:11:02 okay.. I will look into that. 13:11:08 however, if we can hide the details from end users, maybe it is still okay to use the current versioning support 13:11:10 Guest53983 is yaofenghua I think 13:11:13 https://review.openstack.org/#/c/482370/1 13:11:20 yes 13:11:23 I leave a comment in liyi's patch 13:12:13 XueFeng, thanks 13:12:41 I'm not aware of any other changes to senlin engine 13:13:28 do we still have a lot to do regarding runtime_data implementation? 13:13:52 Qiming, I want to add some data to action.outputs after execute is 13:14:16 em, that is good suggestion 13:14:45 although we don't have a strict schema for action inputs or outputs 13:15:09 but that may need to query databases, e.g nodes created 13:15:21 I'd still prefer a systematic way to get it done 13:16:11 different actions produce different data as outputs 13:16:29 maybe we should document them in the design docs 13:16:42 yes, that should be formatted 13:17:16 so at least we are still not losing control of what was dumped in P version and what was added later in Q version ... so on and so forth 13:18:02 we don't need a strict protocol on that, right? 13:18:24 I mean we don't want to check if a field exists and if it is actually an integer for example 13:18:53 actions are primarily provided as a debugging tool 13:19:05 it could be something like the action payload? 13:19:40 just document what are expected as inputs and/or outputs would be okay 13:20:15 the action.outputs only surface when you do 'action show' 13:20:34 it is mainly used for later processing in policies and dumping events to MQ 13:20:40 although internally it may get checked by some policies 13:20:54 right, events ... 13:21:30 go ahead and do it, :) 13:21:41 okay :) 13:22:03 moving on 13:22:18 we got some progress on RDO packaging, right? 13:22:28 Yes 13:22:29 Qiming 13:22:35 https://bugzilla.redhat.com/show_bug.cgi?id=1426551 13:22:37 bugzilla.redhat.com bug 1426551 in Package Review "Review Request: Senlin - is a clustering service for OpenStack" [Unspecified,Assigned] - Assigned to jpena 13:22:47 someone has taken over that job 13:22:47 Got process these days 13:22:54 cool 13:23:12 https://review.rdoproject.org/r/#/c/7470/ 13:23:27 and in rdo project code is in review 13:23:28 if there are things needed from senlin side, just let yell in #senlin channel 13:23:42 ok 13:25:22 any other updates regarding pike work items? 13:26:30 https://blueprints.launchpad.net/senlin/+spec/improve-vm-name 13:27:39 any updates to that bp, XueFeng ? 13:27:59 what kind of order? could you explain more,XueFeng 13:28:31 I want to ask which state about this bp 13:28:50 it is there 13:30:00 no follow up after the review 13:30:06 no new patch 13:30:14 no response to the comments 13:30:42 So the better way is to add a column to the cluster table, followed by an upgrade of the cluster apis? 13:30:55 why index is important 13:31:05 I do not get the point of this BP 13:31:14 index will be used as part of node name 13:31:41 if name can be predictable, the 'hostname' of a VM is predictable 13:31:44 is any dependency on the node name 13:31:54 by exited adoption? 13:32:03 exsited 13:32:04 and it will help applications running in nodes 13:32:31 currently, there are two possibilities, all nodes named the same 13:32:42 or names have random suffixes 13:32:58 neither one meets the requirement sketched above 13:33:52 if anyone is interested in working on this, I can share my thoughts on it 13:34:22 ok 13:35:01 actually, I wrote some ideas in the first review 13:35:06 current the name is the same, it's better to improve I think 13:35:32 If we don't specify name in profile, I think it's different? 13:35:37 it is definitely a good feature 13:36:00 different is not enough 13:36:07 users want the name predictable 13:36:38 say, 'k8sworker-1', 'k8sworker-2' 13:36:49 Like cluster_name-index? 13:36:50 or 'redis-1', 'redis-2', ... 13:36:55 yes 13:37:20 Yes, that's reasonable. 13:37:22 then user can predict the node names 13:37:41 not 'node-blah', 'node-xyz123', ... 13:37:51 I remember our node name have some rules like that. 13:38:13 Why not just make it the same as node name? 13:39:25 or in order words, what kind of name protocal will be preferred 13:39:25 It's easy to do so, some monitoring system is based on vm name I guess. 13:39:35 for this BP 13:39:40 easy to map? 13:39:45 keep unified? 13:39:54 fir for different use cases? 13:39:59 fit 13:40:36 xinhuili_, read the first comment I left there 13:41:09 #link https://review.openstack.org/#/c/461673/ 13:41:32 I was suggesting we may this configurable 13:41:46 reading ... 13:42:07 good idea to make the rule configurable 13:42:42 okay, back to the agenda 13:43:30 don't know if people have interests in standing up a k8s cluster using senlin 13:44:06 I don't see that a big challenge, just need hands to work it out 13:44:10 Qiming , share the idea to us 13:44:30 XueFeng, not today, the agenda is already too long 13:44:31 More detail 13:44:43 we are not supposed to overrun 13:45:19 * Qiming trying to find a pointer 13:45:50 here: https://github.com/kubernetes/kubernetes/tree/master/cluster/openstack-heat/kubernetes-heat 13:46:07 some hints for those who are interested 13:46:44 it is part of official k8s code 13:46:48 I guess that heat template is not easy to use :P 13:47:03 yes, that is where we can help 13:47:59 recent feedbacks: users still have lock problems 13:48:12 maybe because they were using old version 13:48:19 Yes ,in Ocata version 13:48:23 the complaint I got is about 3.0.0 13:48:44 I am :) 13:49:06 ruijie, you got lock problems recently? 13:49:27 Can't clean lock when restart engine 13:49:27 didnt't see that problem again 13:49:36 okay 13:49:48 I said I am interested in the interations of senlin & k8s 13:50:00 please ring the bell when you see things abnormal 13:50:05 http://eavesdrop.openstack.org/irclogs/%23senlin/%23senlin.2017-07-07.log.html 13:50:25 #topic sydney proposals 13:50:31 it is drawing near 13:50:49 pls think about what you want to propose if any 13:51:17 ok 13:51:33 if you want, you can pass your draft across the team for comments 13:51:50 Do you have any proposals? 13:51:50 About adoptation we can do a proposal 13:52:20 adoption be one, but the story is not that attractive for users 13:52:37 I'd like to see k8s standing up on senlin 13:52:55 with very few parametes to tune 13:53:04 Good 13:53:21 That's another proposal I guess 13:53:30 And if we use k8s+ senlin 13:53:33 but ... I myself is overrrrr committed at the time 13:53:48 Should we intergate kuryr? 13:54:12 I could try to do some poc codes if you like 13:54:16 XueFeng, it depends 13:54:28 I am interested 13:54:32 so .... good elynn 13:55:17 from k8s side, they are assumming the cloud provider provides a clustering service 13:55:30 on openstack that interface has not been claimed 13:55:43 But you have to share more info to us, ur the expert of k8s :) 13:55:52 we are almost a perfect fit for that role 13:55:56 Like how lb and network work. 13:56:01 https://blueprints.launchpad.net/senlin/+spec/integration-kuryr-for-container-network 13:56:08 lb should be hidden, ideally 13:56:15 This is the bp fo integration kuryr 13:56:29 just expose one IP for a cluster as the service IP 13:56:56 I remember that k8s has api service and can be integrate with lb I assume? 13:57:02 thanks for proposing that, XueFeng 13:57:22 it would be better if someone has started the coding/testing work, :D 13:57:30 My pleasure 13:57:36 yes, k8s has that 13:57:52 but ... I'm very disappointed by lbaas on openstack 13:57:59 tbh 13:58:51 I'd prefer calling out to haproxy or nginx directly ... 13:59:05 You mean we can get rid of laas in k8s cluster? 13:59:26 Hmm, that's another approach 13:59:27 avoid ocativa when possible, I mean 13:59:33 it is terrible 13:59:40 We can do in this way 13:59:41 sorry, running out of time 13:59:53 thanks for joining boys & girls 13:59:57 good night 14:00:02 #endmeeting