13:00:03 #startmeeting senlin 13:00:04 Meeting started Tue Apr 25 13:00:03 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:05 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:00:07 The meeting name has been set to 'senlin' 13:00:38 hi, evening 13:00:51 hi 13:01:34 don't know if others are joining 13:01:55 maybe lets wait for a while for them? 13:02:00 ya 13:02:06 evening :) 13:03:04 hi, ruijie :) 13:03:11 evening 13:03:14 let's get started 13:03:20 hi :) 13:03:29 #topic pike work items 13:03:39 evening ruijie 13:03:55 don't think we have elynn today 13:04:06 so we skip vdu topic 13:04:06 yes, you have 13:04:10 :) 13:04:22 just no update on this topic 13:04:23 engine improvement, CLUSTER_CHECK patch looks good to me 13:04:35 evening elynn 13:05:04 okay, hope we can have it by the end of this cycle, :) 13:05:35 oh, I was wrong, XueFeng's patch needs some work 13:06:00 node adopt patches are merged now 13:07:02 need to work on api support, doc and test 13:07:41 we will need to bump microversion of api soon 13:08:31 in my mind, next api microversion will include node-adopt, node-adopt-preview, service-list and some changes to cluster actions that have health_check support 13:09:25 the health_check parameter for scale in, patch 459090 looks good to me 13:09:30 please review 13:09:55 but for policy side, that is not easy to implement with current design 13:10:45 Qiming, I have a question here, when check the deletion policy 13:11:15 I found the data from region&zone policy only been used in deletion policy? 13:11:29 so far, yes 13:12:42 Qiming, a question about cluster_check, if the node is shutoff we think it was error 13:12:50 yes 13:12:52 okay .. need to think how to interact with deletion policy 13:13:33 then we do_recover, the default action is delete and create. 13:13:59 In fact we only need to start the node 13:15:20 sorry, network connection not stable 13:15:33 all nodes that are not operational should be treated unhealthy 13:16:35 and, ideally, we should be able to recover them based on their current status (deleted -> recreate, crashed -> rebuild, shutdown -> start, etc.) 13:17:04 that makes sense? 13:17:13 yes:) 13:17:19 think so 13:17:28 okay 13:17:53 next work item (just added), is about optimizing the runtime_data properties 13:18:28 they were designed to be a cache of DB entries, however, we are seeing some obvious overhead in using them 13:18:42 I'm working on some patches to optimize it 13:18:59 ok, great 13:19:05 Qiming, you mean dumping data to action.outputs? 13:19:29 for example, a cluster's rt['nodes'] now contains only OVO version of Nodes, rather than engine Node objects 13:19:57 oh, okay 13:19:58 Will you back port these patches back to coat? 13:20:03 ocata 13:20:04 in other words, we will have array of senlin.objects.node.Node instead of senlin.engine.node.Node 13:20:17 it would be a little bit difficult 13:20:30 if there is a requirement, elynn, I can do that 13:20:54 I can try cherry-pick though 13:22:11 okay for you, elynn? 13:22:34 moving on 13:22:39 rdo progress? 13:23:05 no update 13:23:12 Qiming 13:23:26 health management 13:23:45 we have basic workflow (mistral) support added to Node class now 13:23:56 I am drafting chart for Boston 13:24:00 about workflow 13:24:04 and hope 13:24:12 need to revise recover operation to invoke them 13:24:22 renat could provide 3-5 pages for us 13:24:33 oh, godess is here, below the water surface 13:24:40 cool 13:24:41 ... 13:24:55 sorry, just back home from CMCC lab 13:25:04 we are doing R2 integration these days 13:25:07 ... 13:25:13 I see. 13:25:24 for the VDU 13:25:33 health management 13:25:54 is more complex than what we think before 13:26:08 actually tocsa has add extention spec on this part 13:26:30 such as relationship bound with a VDU 13:26:32 alright, any link? 13:26:46 I will send out doc to all of you 13:27:15 great 13:27:19 thanks, we need to discuss about it after we read the docs. 13:27:21 The documents are latest VDU spec 13:27:30 sure 13:27:43 okay, looking forward to that 13:27:57 Testing 13:28:20 local tempest testing fix is done, XueFeng? 13:28:29 yes 13:28:31 Qiming 13:29:34 rally job gets problem? 13:29:49 yes, seems so 13:29:55 don't understand why admin users cannot get profile object created by non-admin 13:30:03 should be caused by this patch: https://review.openstack.org/415690 13:30:05 yes, somebody mail me and I have discuss with yanyanhu_ 13:30:11 discussed 13:30:26 it enforces the project_safe for admin user 13:30:35 right 13:30:56 even an admin should have a role in a project in order to operate things there 13:31:02 so I guess we may need to find a way to address this kind of requirement 13:31:45 the admin user, should login using the proper OS_PROJECT_ID 13:32:02 http://eavesdrop.openstack.org/irclogs/%23senlin/%23senlin.2017-04-25.log.html 13:32:17 Qiming, I guess the project_id of an user is fixed once the user is created 13:32:29 no, that is the default project id 13:32:48 yes, but using other project_id rather than default one won't work I think... 13:33:04 when you authenticate to keystone, you can still specify the target project id 13:33:08 at least it didn't last time I tried it... 13:33:13 you have to have a role in that project 13:33:14 a while ago 13:33:41 Qiming, yes... I tried it like that, but got authentication error... not sure whether it works now 13:33:53 it should work 13:34:07 oh, I tried it for trust 13:34:14 we only use project-scope tokens 13:34:16 maybe that is a special case 13:34:20 right 13:34:26 trust is different 13:34:30 for normal case, it should work 13:34:44 and maybe it is the trust that caused the problem 13:35:03 yes, it could be 13:35:14 I'd suggest they dump the context contents and see if there are roles we can check 13:35:33 ok 13:35:57 client functional test, no update? 13:36:09 yes:( 13:36:49 moving on 13:37:00 last is policy improvement 13:37:04 ruijie any update? 13:37:08 no progress 13:37:22 Qiming, no, I guess 13:37:47 okay 13:38:02 anything else wrt pike work items? 13:38:22 guess no? 13:38:48 Qiming, no I guess 13:38:57 Yes 13:38:57 sorry just dropped 13:39:00 alright 13:39:06 #topic boston summit prep 13:39:41 anyone needs other's help? 13:39:53 Qiming, one problem 13:40:20 create are alarm, and make the vm high 13:40:35 vm refused to go high? :D 13:40:47 :P 13:40:49 no 13:41:01 can't get the alarm 13:41:35 could be another ceilometer/aodh problem 13:41:45 maybe 13:41:55 reference to the doc you write 13:42:15 then better debug aodh/ceilometer first 13:42:23 ok 13:42:26 they change things every single day 13:42:36 en 13:43:39 #topic open discussion 13:43:53 anything else people want to discuss? 13:44:16 no more from me 13:44:22 just dropped again... 13:44:28 no from me :) 13:44:48 no more 13:44:56 alright, thanks for joining boys and girls 13:45:01 have a good night 13:45:09 good night 13:45:16 have a good night :) 13:45:17 we can end this earlier 13:45:17 good night :) 13:45:24 #endmeeting