13:00:29 #startmeeting senlin 13:00:30 Meeting started Tue Jun 16 13:00:29 2015 UTC and is due to finish in 60 minutes. The chair is Qiming. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:31 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:00:34 The meeting name has been set to 'senlin' 13:00:50 #topic roll call 13:01:16 o/ 13:01:17 o/ 13:01:21 hi 13:01:33 Jaivish Kothari 13:01:38 don't think a lot of us will show up, this is the first meeting for senlin anyway 13:02:22 #topic get to know each other 13:02:24 at least four :) 13:03:10 I'm expecting everyone to say a few words about yourself 13:03:32 ok, I am xuhaiwei from NEC, nice to meet you 13:03:38 I am in Tokyo 13:03:43 so people get to know your name, where you are located, and your expertise, etc 13:04:02 Hi i am Jaivish from NEC :) india 13:04:25 Hi, i'm Lisa from IBM in Austin, TX 13:04:30 Qiming Teng, with IBM Research, in China 13:05:38 currently four of us? 13:06:20 I normally work in swift , keystone and ceilometer . 13:06:32 anyone else? 13:06:55 janonymous, you are in India office? 13:06:58 cool, not a big team so far 13:07:07 let's move on 13:07:14 #topic project status report 13:07:44 Senlin was started last December, positioned as a generic clustering service for OpenStack 13:08:03 the project is now located on stackforge, with both server side and client side code 13:08:30 we have presented the design in the Heat design summit, because we were deeply rooted from Heat 13:08:54 haiwei : yes . 13:09:03 the top priority for the project for the first release (Liberty) would be making autoscaling work 13:09:21 and hopefully, bridge the Heat support to autoscaling to Senlin 13:09:39 Qiming, so how far are we there? 13:09:44 there are a lot of work to do for us to achieve that goal 13:10:17 to support autoscaling, we are developing a scaling policy spec and the supporting plugin 13:10:32 hopefully, that will be done by Liberty-2 13:11:12 Yes i am ready to work hard . but i could only work after my office hours because it's my priority :) . will that be ok? 13:11:15 I have to say, it is not a trivial thing, considering that we may need to explore message queue service (zaqar) some time 13:11:35 sure 13:11:48 any kinds of contributions are welcomed, sir 13:11:48 Thanks :) 13:12:05 time for you to pour questions on me 13:12:43 what about the short time goal? 13:12:50 short-term 13:13:26 supporting autoscaling is pretty short-term a goal 13:13:27 Sorry to say but i want to know about senlin , i have very little idea about it. 13:13:43 janonymous_, don't worry 13:13:56 we are working hard to add some documents for developers 13:14:04 for example: https://review.openstack.org/#/c/190447/ 13:14:42 you can find us on the #senlin channel most of the time, just jump in and ask questions 13:15:15 Yes sure sir. is there a mailing list , group for serlin also ? 13:15:19 Qiming, what is not done to support auto-scaling 13:15:36 haiwei, the scaling policy is not done 13:15:49 we have some dependencies on python-openstacksdk project 13:15:57 Just to understand where this is going, once senlin has the scaling policies implemented, the idea is to have something like OS::Senlin::Cluster OS::Senlin::Policy in a heat template to do autoscaling through heat? But then you can also do autoscaling without heat at all right? 13:16:07 we need to push some patches there first 13:16:31 lkarm, right 13:17:12 If you are using Heat for autoscaling, we don't want to break you 13:17:45 however, Senlin has its own APIs and client, that means you can do autoscaling in other ways as well 13:18:00 are you planning on implementing scaling policies in a similar way heat implemented them? 13:18:47 lkarm, yes and no, from user's perspective, we hope we can support their existing autoscaling templates 13:19:15 but implementation perspective, there will be quite some differences 13:19:38 for example, we don't want users to specify alarms, at least that is our current idea 13:20:18 you can check the senlin/examples/policies subdirectory to see how scaling policies will look like 13:20:23 by that you mean no ceilometer dependencies required to do autoscaling? 13:20:49 lkarm, the dependency may exist, but won't be hard-coded 13:21:26 we plan to provide users a choice, use ceilometer, monasca, or whatever 3rd-party monitoring tools 13:22:23 there are plenty of details to be discussed 13:22:51 What I want to say in this meeting is that we need to make all of them a team decision 13:23:39 scaling policy is just one type of policies to be supported, for example 13:24:02 we want to support placement policies, deletion policies, update policies, etc 13:24:31 these policies are all plugins that you can instantiate and attach to a cluster 13:24:42 we believe they are orthogonal to each other 13:25:32 we also plan to submit a talk proposal for the coming Tokyo summit, give the community a deep dive and status update 13:25:58 there have been some requests for Senlin to support clusters of containers, for instance 13:25:59 hi, sorry for late, using my phone as hot spot 13:26:45 does that mean magnum integration? 13:26:46 in that case, Magnum will call senlin to create their pool of containers 13:26:54 Qiming, that is an important job I think 13:27:15 Apart from senlin wiki ,can i get more info about it. because i m not from heat background so i would be needing some docs. 13:27:31 yip, we have talked to Adrian and Steven Dake for this, the only concern they have today is that we are still on stackforge 13:27:46 and they want no dependencies on stackforge projects 13:28:05 so what is the plan for moving from stackforge 13:28:11 janonymous_, okay, we will work on more docs 13:28:16 so it's better to push openstacksdk to be a openstack project 13:28:42 or maybe we can start to implement some drivers directly based on other services client? 13:28:50 Senlin project itself, based on the community's criteria, can be proposed as a openstack project today 13:29:03 janonymous_, maybe understanding heat autoscaling first is helpful 13:29:24 the only reason we are not pushing that line is that we have dependencies on python-openstacksdk 13:29:38 and python-opentacksdk is today a stackforge project 13:29:49 we are actively helping that project as well 13:30:15 python-openstacksdk can be a openstack project today, but they just don't want to be? 13:30:32 em, don't have an answer for that, haiwei 13:31:02 Seems to me, though, the SDK project wants their API design stabilized before proposing 13:31:15 that makes sense to me 13:31:31 and ... it will just be a issue of time 13:31:53 how long it will take ? 13:32:18 yanyanhu, if we introduce dependencies on python-***client into Senlin, we are still eventually throwing them away 13:32:29 and what can we do for that 13:32:40 haiwei, not sure how long it will take 13:32:51 Qiming, that's true, openstack-sdk should be the choice 13:33:06 my personal opinin is focus on Senlin feature development, stability improvement 13:33:16 what about setting a deadline for that 13:33:49 the migration to openstack is just one of the many channels to get this service mature and widely used 13:34:21 haiwei, good point, we need to sync with SDK team on a timeline 13:34:38 #action Qiming to sync with SDK team for timeline 13:34:48 actually we still have several import features need to implement including customized action, complicated scaling policy 13:35:09 yanyanhu, +1 13:35:35 let's move on 13:35:50 #topic low-hanging fruits for new contributors 13:36:10 :) 13:36:24 Many of us are new contributors to Senlin, or new developers for OpenStack 13:36:53 it will be a journey, but it won't be very long one 13:37:15 We are currently filing some bugs for your reference 13:37:19 https://bugs.launchpad.net/senlin/ 13:38:16 I have question.. What about core contributors of senlin.. 13:38:22 Some bugs are really easy to fix, but they will help you understand the architecture of Senlin, the development process for fixing bugs, propose patches etc. 13:38:41 janonymous_, currently we have only two cores, yanyanhu and me 13:38:58 I believe we will need more soon, pretty soon 13:39:19 Qiming, currently I am doing this kind of bug fix 13:39:32 Yes , i would be one .. i hope :) 13:39:37 thanks, haiwei, keep the good work 13:39:48 janonymous_, you will, if you want 13:39:59 hope you guys can get familiar with the project soon : ) 13:40:13 Yes. 13:40:18 some low hanging fruits, out of the bug list: Bug #1465565, Bug #1465211, Bug #1465509, Bug #1465518, Bug #1465620 13:40:21 bug 1465565 in senlin "Policy attach should use policy defaults if not specified" [High,Triaged] https://launchpad.net/bugs/1465565 13:40:22 bug 1465211 in senlin "profile type matching should be checked earlier" [Medium,Triaged] https://launchpad.net/bugs/1465211 13:40:23 bug 1465509 in senlin "Policy attach API should perform parameter validations" [Medium,Triaged] https://launchpad.net/bugs/1465509 13:40:25 bug 1465518 in senlin "Policy detach action API should do some early validation" [Medium,Triaged] https://launchpad.net/bugs/1465518 13:40:26 bug 1465620 in senlin "Policy update API is not checking the JSON body" [Medium,Triaged] https://launchpad.net/bugs/1465620 13:40:35 just some examples 13:41:17 hi, Qiming, maybe completing exception translation is also one? 13:41:26 btw, we have two files maintained for short-term and long-term jobs 13:41:42 yanyanhu, that sounds more like a TODO item, not a bug 13:41:48 yes 13:41:51 http://git.openstack.org/cgit/stackforge/senlin/tree/TODO.rst 13:42:18 we maintain a TODO file in the code repo, listing things we need to do 13:42:44 items in the TODO.rst file doesn't require a design discussion 13:43:11 if you know how to get it done, claim it by signing your name after that item, do it 13:43:23 remove it when it is finished 13:43:35 another file: http://git.openstack.org/cgit/stackforge/senlin/tree/FEATURES.rst 13:44:10 this is a list of feature request we collected, most of them need some discussions among the team before coding 13:44:34 feel free to start a thread on any of them 13:45:13 if needed, we may create a senlin-specs project for reviewing things like these 13:45:41 questions, comments, suggestions? 13:46:04 that was helpful. 13:46:45 the FEATURES.rst, to some extent, give you a sense where we are heading, hopefully 13:47:17 okay, let's move on 13:47:24 #topic open discussions 13:48:39 hi, Qiming, do we need to arrange some phone calls to answer some questions which may need detailed explaination? 13:49:07 during the Vancouver summit, I met some guys from Alcatel-Lucent, they may join us some day 13:49:35 good news 13:49:37 Kindly add me on your mailing lists if possible. janonymous.codevulture@gmail.com 13:49:39 phone calls? we can discuss that 13:50:14 janonymous_, all openstack/stackforge projects are supposed to use the official mailinglist for discussion 13:50:14 phone calls means call by phone??:) 13:50:24 yes ;) 13:50:41 personal phone call? 13:50:58 when posting your message, be sure to tag your subject with '[Senlin]' so that people can filter it 13:51:01 hmm, not sure about the way 13:51:10 I will add your wechat :) 13:51:24 nice 13:51:30 phone calls in general is not encouraged, if I'm understanding it correctly 13:51:39 it is kind of private communication 13:52:00 yes, I mean something like call conference 13:52:03 i agree with you 13:52:09 I believe all discussions should be open to the public 13:52:17 if we can find a way to let everybody join 13:52:28 ok, agree 13:52:40 +1 13:52:48 yep, stay awake on the #senlin channel, be an answer machine, :) 13:53:26 Qiming, that's great 13:53:37 what about your back?:) 13:53:47 not good, recovering 13:53:47 yep I think IRC is best way to commuincate and discuss 13:53:59 yes, lkarm 13:53:59 agree 13:54:15 so let join the channel :) 13:54:32 eventually, when we become an openstack project, IRC chats will be logged, you can find whatever discussions you have missed 13:54:58 ah I was wondering why they weren't currently being logged 13:55:19 that said, the best way to answer questions at the moment is to work on some documents, for users, for developers 13:55:28 stackforge project doesn't have the right? 13:55:49 haiwei, I don't think so, maybe I'm missing something 13:56:00 let the team know if you find a way to log the chats 13:56:17 agree, Qiming, will try to complete the doc and wiki 13:56:38 what tool are you using? Qiming 13:56:40 thanks, we then don't have to answer the same questions time and time again 13:56:45 it's easy to miss some import topics for time difference 13:56:51 I'm using HexChat 13:57:00 right 13:57:01 whn is the next meeting.. 13:57:26 so if you have something for discussion, you may want to post a note to the mailing list 13:57:35 janonymous_, https://wiki.openstack.org/wiki/Meetings/SenlinAgenda 13:57:37 the same time next week 13:57:48 1300 UTC, every Tuesday 13:58:02 thank u 13:58:03 time is up 13:58:09 thank you all for joining 13:58:24 thanks, ttyl 13:58:25 see you, see your patches 13:58:40 see you 13:58:42 :) o/ 13:58:47 discussions can continue on #senlin 13:58:55 #endmeeting