13:02:00 #startmeeting senlin 13:02:01 Meeting started Tue Sep 19 13:02:00 2017 UTC and is due to finish in 60 minutes. The chair is ruijie_. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:02:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:02:05 The meeting name has been set to 'senlin' 13:02:05 here we go .. 13:02:10 :) 13:02:12 sorry 13:02:20 https://wiki.openstack.org/wiki/Meetings/SenlinAgenda 13:02:24 Hi everyone! It nice to meet you guys 13:02:32 please feel free to add items to the agenda 13:02:36 hi longkb_ 13:03:32 let's wait for a while :) 13:03:47 hi chenyb4_ 13:04:48 okay, let's get started 13:04:58 https://etherpad.openstack.org/p/senlin-queens-workitems 13:05:42 hi Qiming, we discussed about the extra field/policy to add hook to scaling process 13:06:15 yes 13:07:40 so, that policy could contains how to get approved or how to send notifications? 13:08:03 there are two sub-topics here 13:08:40 one is about how to inject something into an API request to indicate whether a request is an "original" one 13:09:45 the other one is about how to add hooks (possibly a general policy) that examines this 'something' and decide whether a hook will be triggered 13:10:18 we are supposed to be following the global api-wg guidelines, for api requests and responses 13:10:45 by the "original" request, you mean we will send a request or notification to someone, and they will call back? 13:11:25 yes 13:13:00 once the "original" comes in, we need to record it somewhere to wait for callback, after that the process could pass to next step? 13:15:29 we don't wait 13:15:59 that request has been "processed" and "redirected" 13:17:41 these kind of info are have to be either sent in the body or embedded in the header 13:18:41 if we carry these info in header, it would be something like this: https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS 13:18:59 request(with special field) --> create action with special status --> return/call/notify ; callback to trigger that action --> scale in/out 13:20:56 the original request doesn't have to be changed 13:21:13 most of the time, requests should be processed as usual 13:21:37 it is only those requests mutated by a third party software that need a special tag 13:23:11 okay, Qiming, may need to look forward to it :) thought it a little bit simple 13:24:06 to get it done in a disciplined way is not straightforward 13:24:25 although get it done in an adhoc way is simple enough 13:25:14 reference: http://specs.openstack.org/openstack/api-wg/guidelines/headers.html#avoid-proliferating-headers 13:25:24 yes Qiming 13:26:22 also this: http://specs.openstack.org/openstack/api-wg/guidelines/http.html 13:26:38 we are supposed to return a proper status code for this 13:28:10 I don't think we should add an 'extra' field to each and every API request ... 13:28:15 it is gonna be dirty 13:30:04 thanks Qiming, let's talk about it a little bit later :) 13:30:20 alright 13:30:50 another one is about this patch https://review.openstack.org/#/c/504830/ 13:31:06 to revisit the documentation of event dispatcher 13:31:49 the developer part of the event dispatcher looks good now? 13:32:46 yes I think so 13:33:33 however, I think we are supposed to split that rst file into two 13:33:37 http://git.openstack.org/cgit/openstack/senlin/tree/doc/source/contributor/event_dispatcher.rst 13:33:45 one for user, one for developer 13:34:03 this one is about how to extend the event plugin 13:34:36 Qiming, you mean we may need to divid the user reference to 2 parts? 13:34:53 the contents under 'contributor' subdir are there for developers 13:35:11 the one in your patch is targeting users 13:35:40 yes Qiming 13:35:51 I see, we already have guide for developers 13:36:10 yes Qiming :) 13:36:51 next one. the tempest-plugin 13:37:06 https://review.openstack.org/#/c/504870/ 13:37:39 the patch is already there, will keep checking it 13:38:21 that's all from my side :) 13:38:48 cool 13:39:00 I noticed longkb_ is here :) 13:39:23 we will need to revise some gate jobs later when the github project is migrated 13:39:59 yes Qiming, after that, will move the gate jobs from senlin to the plugin step by step 13:40:34 to be honest, I'm not sure 13:41:11 the gate jobs are there to ensure changes to senlin repo won't break anything, they are not there to protect the tempest plugin 13:41:58 so maybe the jobs are supposed to be revised to invoke tempest plugin project, and they still vote for senlin patches 13:43:00 also speaking of your event doc improvement 13:43:09 when reading this: https://docs.openstack.org/senlin/latest/user/events.html 13:43:43 I felt that we may need a subsection for the dispatcher configuration so that users will easily find the info 13:44:32 one for the database and another for the messaging 13:44:54 we need a subsection in that article 13:45:06 for readability's purpose 13:45:19 just a quick thought 13:45:35 okay, that makes sense 13:46:24 next one is about the meetup 13:47:30 we can organize the meetup in Beijing in the 2nd/3rd week of Oct 13:47:40 any suggestion on the date/location ? 13:48:30 how about 15th Oct 13:49:30 Queens-1 milestone :) 13:49:32 it is okay for me 13:49:54 I may have a conflicting schedule but not yet fixed 13:50:48 the date could be discussed, will send an email to mailing list. I think the location could be Beijing :) 13:52:30 :< >: that's all from me 13:54:11 no topic from me 13:54:36 okay, we can end it a little bit early 13:54:46 thanks for joining :) 13:55:04 #endmeeting