13:02:44 <Qiming> #startmeeting senlin
13:02:45 <openstack> Meeting started Tue Jan 19 13:02:44 2016 UTC and is due to finish in 60 minutes.  The chair is Qiming. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:02:46 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:02:48 <openstack> The meeting name has been set to 'senlin'
13:02:56 <Qiming> sorry, a bit late
13:03:08 <elynn_> o/
13:03:22 <Qiming> trapped by the placement policy
13:03:22 <yanyanhu> hi
13:03:53 <Qiming> pls check meeting agenda
13:04:09 <Qiming> very short one, :)
13:04:12 <Qiming> #link https://wiki.openstack.org/wiki/Meetings/SenlinAgenda
13:04:35 <Qiming> first things first, work items etherpad
13:04:43 <Qiming> #link https://etherpad.openstack.org/p/senlin-mitaka-workitems
13:05:13 <Qiming> I tried keep updating this page
13:05:34 <Qiming> location header can be got now, elynn?
13:06:01 <elynn_> yes
13:06:16 <elynn_> I try and can get location now.
13:06:21 <Qiming> cool
13:06:27 <elynn_> But openstacksdk doesn't release new tag.
13:06:39 <Qiming> for action header, may need to add that asap
13:06:45 <elynn_> only master support location.
13:07:05 <elynn_> Action header?
13:07:05 <Qiming> yes, after action header is added, we can push them to do a 1.0 release
13:07:27 <Qiming> oh, sorry, location header points to action
13:07:54 <Qiming> see what a mess I'm
13:08:19 <elynn_> we can get location header now
13:08:31 <Qiming> great
13:08:41 <elynn_> I can split location string and get action id in heat.
13:09:04 <Qiming> moving on, I don't think anyone is working on advanced filters
13:09:26 <Qiming> so you will continue to work on the heat resource type thing
13:09:34 <haiwei> have forgotten it
13:09:42 <elynn_> Qiming: yes
13:09:54 <Qiming> haiwei, no worry, we have been talking empty, :P
13:09:55 <elynn_> I will add more resource type in heat for senlin in this release
13:10:02 <Qiming> great
13:10:12 <Qiming> senlinclient test case coverage is 91%
13:10:38 <Qiming> there are a few units a little bit tricky to test
13:10:53 <haiwei> will make a new release?
13:10:53 <Qiming> we can get back to that after this m2 release
13:11:12 <Qiming> yes, haiwei, client should be released first
13:11:22 <Qiming> I think it is in pretty good shape now
13:11:37 <haiwei> seems so
13:12:21 <Qiming> health management part, xinhui has been pushing that end
13:12:29 <Qiming> great progress so far
13:12:56 <Qiming> we won't expose those interfaces from API in m2
13:13:22 <haiwei> why not
13:13:25 <Qiming> we can discuss later when those bits all merged
13:13:38 <Qiming> and see if it is approriate
13:13:58 <Qiming> haiwei, we can never deprecate things once exposed from API
13:14:19 <Qiming> that's the reason why we spent so much effort on deleting things
13:14:46 <haiwei> will we make a release of API, and put health polices into micro-version?
13:14:50 <Qiming> Documentation part, no progress, I guess
13:15:01 <Qiming> haiwei, that is an option
13:15:17 <Qiming> before doing micro-versioning, we need an infra to support it
13:15:34 <Qiming> micro-version specs are under review in openstack-specs project
13:15:37 <haiwei> ok, we don't need to make API release so fast I think
13:15:41 <Qiming> we should watch that
13:16:05 <Qiming> sure, keep the minimum set of APIs, and make them usable, stable
13:16:28 <Qiming> no progress on profile update, right?
13:16:45 <yanyanhu> yes
13:16:53 <yanyanhu> didn't get time to work on it...
13:17:09 <Qiming> no worry, not high priority at the moment
13:17:36 <yanyanhu> yea, will focus on policy this week
13:17:46 <Qiming> okay, the highest priority is to make policies work
13:18:20 <Qiming> especially those ones which used to work before we remove soft-delete, priority, level, cooldown ... etc
13:18:39 <Qiming> that will be the baseline for this m2 release
13:18:49 <yanyanhu> yes, lots of thing need to clean
13:18:57 <Qiming> yep
13:20:16 <Qiming> deleting clusters which have receivers associated
13:20:25 <Qiming> this one has been solved
13:20:35 <Qiming> em ... can be improved though
13:20:58 <Qiming> so it is no longer a bug
13:21:13 <Qiming> can we remove it?
13:21:19 <yanyanhu> yes, I think so
13:21:23 <haiwei> yes
13:22:14 <Qiming> policy fix is not related to receiver
13:22:31 <Qiming> lb rework was listed on line 46
13:22:48 <Qiming> builtin policy captured on line 43
13:22:49 <yanyanhu> yes, so we can remove this item
13:22:55 <Qiming> do it!
13:22:56 <yanyanhu> it is in wrong place
13:23:05 <yanyanhu> done
13:23:06 <yanyanhu> :P
13:23:10 <Qiming> it feels good deleting things!
13:23:20 <yanyanhu> sure, haha
13:23:24 <Qiming> engine status listing
13:23:38 <yanyanhu> haven't started working on functional test for receiver as well
13:23:39 <Qiming> that depends on a db table, which means a db version bump
13:23:47 <elynn_> Qiming: yes
13:23:50 <Qiming> yanyanhu, no worry
13:23:52 <yanyanhu> hope can start this work from next week
13:23:53 <elynn_> I will modify my patch
13:24:14 <Qiming> have to prioritize things
13:24:26 <Qiming> okay, done
13:24:26 <elynn_> add 02_xxx.py for db migration.
13:24:29 <Qiming> :)
13:24:52 <Qiming> anything missed from work items etherpad?
13:25:26 <yanyanhu> nope, I think
13:25:28 <haiwei> can you give me the link?
13:25:46 <yanyanhu> https://etherpad.openstack.org/p/senlin-mitaka-workitems
13:26:35 <Qiming> #topic high priority reviews/bugs
13:26:50 <haiwei> about deletion policy for cross az/region one, It seems I am not in the right way
13:27:38 <Qiming> haiwei, will propose a revision to region placement policy, hopefully today
13:28:20 <haiwei> ok, I will do deletion policy fix based on it
13:28:35 <Qiming> cool
13:29:32 <Qiming> reviews
13:29:37 <Qiming> #link https://review.openstack.org/#/q/project:openstack/senlin+status:open
13:30:52 <yanyanhu> still lots of patches need review
13:31:20 <Qiming> yep, wondering if we can/should swallow them all
13:32:16 <yanyanhu> hope so. In worst case, leave those ones which are not necessary for m2 release
13:32:21 <yanyanhu> to next week
13:32:40 <Qiming> okay, just need eyes from everyone
13:32:51 <Qiming> #topic open discussion
13:33:11 <elynn_> Will~
13:33:18 <Qiming> a link to share with you: http://superuser.openstack.org/articles/what-s-new-under-the-openstack-big-tent-monasca-and-senlin
13:33:38 <Qiming> may and may not need a proxy to check it
13:34:11 <yanyanhu> I can access it
13:34:22 <elynn_> I can see it.
13:34:27 <lixinhui_> cool
13:34:28 <Qiming> it was very slow last time I checked it
13:34:33 <elynn_> Cool , now we get more attention.
13:34:38 <yanyanhu> nice article :)
13:34:42 <Qiming> ghost ... :D
13:35:06 <Qiming> truth is we need more
13:35:08 <haiwei> who made this?
13:35:32 <Qiming> we can use openstack wiki as the platform
13:35:37 <yanyanhu> Qiming, yep, we need more, both eyes and hands :)
13:36:22 <Qiming> haiwei, Nicole is responsible for publishing this kind of info
13:37:45 <Qiming> another thing, we have got some helps again, on api spec
13:37:46 <Qiming> https://review.openstack.org/#/c/263579/
13:38:48 <yanyanhu> nice
13:39:01 <yanyanhu> thanks for those kind help
13:39:26 <haiwei> great job
13:39:30 <Qiming> I have put your name into corresponding tables here: https://wiki.openstack.org/wiki/CrossProjectLiaisons
13:40:28 <haiwei> ok
13:40:36 <lixinhui_> ok
13:40:44 <yanyanhu> got it
13:41:01 <Qiming> speak up if you want to take away some job roles from me, :)
13:41:14 <Qiming> my name still appears here and there
13:42:15 <Qiming> I'll do my best to serve you well, but I am still grateful to the ones who are sharing the workload, :P
13:42:35 <Qiming> okay
13:42:41 <yanyanhu> sure, will be glad to undertake some jobs
13:42:43 <Qiming> anything else?
13:43:04 <yanyanhu> no further topic from me:)
13:43:10 <haiwei> I have one
13:43:19 <elynn_> I will be glad to help you :)
13:43:32 <haiwei> have anyone tried to create a node with the latest source?
13:44:02 <haiwei> I tried, but failed
13:44:03 <elynn_> Not yet...
13:44:05 <yanyanhu> latest resource?
13:44:08 <Qiming> not yet
13:44:08 <yanyanhu> you mean
13:44:12 <cschulz> There appears to be an error in the Senlin article, it states this meeting occurs "Tuesdays at 13:00 UTC in #senlin on IRC"
13:44:17 <yanyanhu> oh, my eye... sigh
13:44:23 <yanyanhu> latest source...
13:44:34 <Qiming> cschulz, oh, ...
13:45:38 <yanyanhu> ...
13:45:55 <haiwei> Qiming has made a fix a few days ago, make a node's cluster_id '' instead of None if the node is not in a cluster
13:46:27 <Qiming> seems introducing new bugs?
13:46:31 <haiwei> I seems it is related to that fix
13:46:39 <haiwei> I am not sure it is a bug
13:47:16 <haiwei> the unit test passed, but when doing by command line it failed with an DB error
13:47:36 <Qiming> okay, keep digging
13:47:59 <Qiming> see if any traces from senlin-engine
13:48:49 <Qiming> maybe it is related to the default None value or something
13:48:52 <haiwei> https://github.com/openstack/senlin/blob/master/senlin/engine/service.py#L970
13:48:56 <haiwei> this line
13:49:21 <Qiming> that line is good
13:49:41 <haiwei> if make cluster_id equal None, it will pass
13:50:10 <haiwei> I also think current source is OK, but it really failed in my test
13:50:13 <Qiming> maybe line 980 should be checked?
13:50:35 <haiwei> not sure about it
13:50:47 <haiwei> will dig it tomorrow
13:50:49 <Qiming> that fix was necessary
13:50:56 <haiwei> maybe it is my fault
13:51:20 <Qiming> but I'm not 100% sure I have covered all possible places where we are assigning value to node.cluster_id
13:51:46 <Qiming> thx, haiwei
13:51:54 <haiwei> nope
13:52:05 <Qiming> are we done?
13:52:16 <haiwei> it is ok for me
13:52:31 <yanyanhu> ok for me too
13:52:38 <Qiming> thanks for joining, guys, talk to you next week
13:52:42 <Qiming> #endmeeting