05:30:56 <dtruong> #startmeeting senlin
05:30:57 <openstack> Meeting started Fri Oct 12 05:30:56 2018 UTC and is due to finish in 60 minutes.  The chair is dtruong. Information about MeetBot at http://wiki.debian.org/MeetBot.
05:30:58 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
05:31:01 <openstack> The meeting name has been set to 'senlin'
05:31:12 <dtruong> it's time for senlin meeting
05:31:16 <dtruong> anyone here to join?
05:34:58 <Qiming> hi
05:35:19 <dtruong> hi qiming
05:36:19 <dtruong> ok, let's get started then.
05:36:52 <dtruong> #topic autoscaling forum in berlin
05:37:24 <dtruong> #link http://lists.openstack.org/pipermail/openstack-dev/2018-September/134770.html
05:37:40 <dtruong> Qiming: I saw your replies to the ML
05:37:54 <dtruong> do you have anything else to add on this topic?
05:39:07 <Qiming> If you mean something I want to stress again, I would say ... users first
05:39:42 <dtruong> yes, i agree with that 100%
05:40:29 <Qiming> If there are people who just want to find something to work on for a particular project or play games ... we can just ignore them
05:41:22 <dtruong> i think the important thing to recognize is that there are different types of users as well
05:41:37 <Qiming> yes
05:42:25 <dtruong> there are users of heat ASG or senlin.  but then there is k8s users who want autoscaling but have different use cases
05:43:06 <Qiming> yep. I would vote for supporting the k8s use cases
05:44:33 <Qiming> a k8s cluster can live and scale happily on google cloud or aws, it would be desirable to have it better supported on openstack
05:46:07 <Qiming> again, at the end of the day, the community agenda should be driven by use cases
05:46:10 <dtruong> yes. but i think it is important to support the use cases of clustering or autoscaling with only openstack
05:46:26 <dtruong> that is the traditional scaling use case
05:46:39 <Qiming> if no one seems interested in running k8s on openstack, the above assumption won't be true
05:46:53 <Qiming> right
05:47:15 <Qiming> back to the proposed forum topic
05:48:02 <Qiming> IIUC, the key pain point from Heat team's perspective is that "there are existing users already doing autoscaling using ASG..."
05:49:03 <Qiming> a valid concern but they won't reinvent a new thing seriously, i guess
05:49:04 <dtruong> yes, so i proposed that you could potentially switch the Heat ASG implementation to use Senlin
05:49:26 <dtruong> and then slowly deprecate Heat ASG in favor of Senlin resource in Heat
05:49:29 <Qiming> exactly
05:50:07 <Qiming> long live Heat ASG resource type, but .... just kill the implementation
05:50:21 <dtruong> to me this follows what other openstack projects have done.
05:50:31 <dtruong> e.g. cinder split from nova-volume
05:50:45 <Qiming> if there are feature requirement to autoscaling, the requirements should be redirected to Senlin team
05:50:58 <dtruong> yes
05:51:32 <Qiming> Heat should only cares about orchestration, period
05:51:32 <dtruong> i think we are in agreement.  so i'll discuss that proposal with the Heat team at the forum
05:52:11 <dtruong> ok, moving on to the next topic then
05:52:26 <dtruong> #topic blueprint status
05:53:04 <dtruong> fail-fast blueprint is implemented.  waiting for more reviews.
05:53:19 <dtruong> multiple detection type implementation has been merged.
05:53:28 <dtruong> i need to add documentation and release notes.
05:53:41 <Qiming> cool
05:54:18 <dtruong> about the documentation, i thinking we should add a sphinx extension so that we can automatically generate docs for policy and profiles
05:54:37 <Qiming> could you please double check if the gate failures are real for #602460?
05:54:38 <dtruong> using the schema defined in the policy and profile
05:54:46 <Qiming> https://review.openstack.org/#/c/602460/
05:55:07 <Qiming> that is a great idea
05:55:15 <dtruong> about the gate failure, the health policy tempest are broken
05:55:21 <dtruong> seems to be a timing issue
05:55:30 <dtruong> so i merged a patch to disable them for now
05:55:38 <Qiming> i see. that is the reason I didn't w+1 it
05:55:44 <dtruong> https://review.openstack.org/#/c/609563/
05:55:49 <Qiming> understood
05:56:47 <dtruong> let me recheck #602460 to make sure that the failures are gone with my patchset to disable health policy tempest test
05:58:10 <dtruong> looks like you did already =)
05:58:58 <dtruong> going back to the sphinx extension, i want to extract the description in the schema for each field
05:59:01 <Qiming> impatient me
05:59:26 <dtruong> and build it into the docs
05:59:41 <dtruong> so that we don't have to change the docs every time the policy or profile changes
05:59:58 <Qiming> I have no idea how to do that, although I have the same requirement in a different project
06:00:11 <Qiming> ya, that would be awesome
06:00:45 <Qiming> my requirement is to generate web UIs from the class definition
06:00:56 <dtruong> it's new for me too.  so i'm looking into it right now.  mainly because i rather write code than documentation =P
06:01:28 <Qiming> great, looking forward to your findings
06:02:04 <XueFeng> That's great
06:02:13 <dtruong> hi xuefeng
06:02:34 <XueFeng> hi dtruong Qiming
06:02:49 <Qiming> you scared me XueFeng
06:02:58 <dtruong> sphinx has the ability to create your own extension so hopefully it won't be too difficult
06:03:15 <Qiming> suddenly showed up from nowhere
06:03:17 <XueFeng> Why?
06:03:33 <Qiming> em
06:03:33 <XueFeng> HAHA
06:04:07 <Qiming> so it is basically walking  through the class field definitions and to extract the docstrings for those fields?
06:04:12 <dtruong> yes
06:04:40 <Qiming> that was my guess, but it looked to me not so straightforward how to get the doc string for a class field
06:04:47 <dtruong> actually, extract the description in the schema field
06:05:16 <dtruong> https://github.com/openstack/senlin/blob/master/senlin/policies/health_policy.py#L119
06:05:18 <Qiming> okay ... that is a much easier job
06:05:35 <dtruong> sphinx can already get the docstring
06:06:21 <dtruong> that have something called autodoc built-in that extract docstring for classes and their attributes and members
06:07:00 <Qiming> em ...
06:07:01 <dtruong> but in our case that is not that useful because we keep the usage information inside the description string
06:07:04 <Qiming> like this line? http://git.openstack.org/cgit/openstack/openstacksdk/tree/openstack/clustering/v1/profile.py#n36
06:07:47 <dtruong> yes, that would get extracted by sphinx
06:08:13 <Qiming> okay, maybe I should try dig into it again
06:08:28 <dtruong> but it's too generic for profile spec and policy spec
06:09:10 <dtruong> the policy spec is a dictionary with lots of parameters and the description string has the most useful information
06:09:28 <Qiming> indeed
06:10:12 <Qiming> the so called "doc" can be extracted from python variable/field values, that is making things a lot easier
06:10:36 <dtruong> yes
06:11:24 <Qiming> I'm looking for something that can help extract data from comments such as:
06:11:53 <Qiming> # max=1200,optional=true
06:12:10 <Qiming> repeatable
06:12:42 <Qiming> sorry, repeat_interval is more appropriate here
06:13:25 <Qiming> then by reading the source code I can generate a jsonschema for this particular field and even web form input for validation
06:13:49 <Qiming> or else I will have to do the schema definition again ... boring
06:15:05 <dtruong> if the comment is formatted with the #: then sphinx can extract using autoattribute
06:15:06 <dtruong> http://www.sphinx-doc.org/en/master/usage/extensions/autodoc.html#directive-autoattribute
06:15:52 <Qiming> I see, there is the trick
06:16:00 <dtruong> so maybe you can reuse the autodoc implementation to generate a web form instead of a doc
06:16:12 <Qiming> em, worth a try
06:18:36 <dtruong> ok, let's move on
06:18:45 <dtruong> #topic stein community goals
06:19:10 <dtruong> no updates for python 3 goal or upgrade checkers goal
06:20:10 <dtruong> #topic reviews
06:20:34 <dtruong> i added functional tests for senlin in openstacksdk
06:20:37 <dtruong> #link https://review.openstack.org/#/c/607061/
06:20:48 <dtruong> please review it when you have time
06:21:56 <Qiming> wow ... I still have w+1 privilege there ...
06:21:57 <dtruong> i only added the basic tests for senlin but that should be enough to detect any breaking change in openstacksdk that could affect senlin
06:22:35 <Qiming> I see
06:22:43 <dtruong> a good time to use that privilege =)
06:22:51 <Qiming> :D
06:23:15 <dtruong> #topic open discussion
06:23:23 <dtruong> that's all i had an the agenda
06:23:33 <dtruong> anybody have anything else to discuss>
06:23:37 <dtruong> ?
06:23:59 <Qiming> no from me
06:24:49 <Qiming> XueFeng has vapored into thin air again
06:25:01 <dtruong> lol
06:25:13 <dtruong> ok, let's end the meeting then
06:25:19 <dtruong> thanks everyone for attending
06:25:33 <Qiming> thx
06:25:37 <dtruong> #endmeeting