07:01:14 <stevebaker> #startmeeting heat
07:01:15 <openstack> Meeting started Wed Jul 22 07:01:14 2015 UTC and is due to finish in 60 minutes.  The chair is stevebaker. Information about MeetBot at http://wiki.debian.org/MeetBot.
07:01:16 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
07:01:18 <openstack> The meeting name has been set to 'heat'
07:01:22 <stevebaker> #topic rollcall
07:01:31 <asalkeld> o/
07:01:38 <therve> Hey
07:02:02 <stevebaker> Qiming: ping
07:02:09 <Qiming> yes
07:02:22 <pas-ha> o/
07:02:31 <ochuprykov> o/
07:02:35 <tspatzier> hi
07:02:41 <stevebaker> #topic Adding items to agenda
07:02:42 <tlashchova_> hi
07:02:48 <KanagarajM> hi
07:02:52 <stevebaker> bring them on
07:02:57 <skraynev_> o/
07:02:59 <stevebaker> #link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282015-07-23_0700_UTC.29
07:03:32 <kairat_kushaev> o/
07:03:56 <stevebaker> #topic heat reviews https://etherpad.openstack.org/p/heat-reviews
07:04:38 <stevebaker> I've just gone through them and its looking like a reasonable list. Unless anyone has changes which they want to add?
07:04:58 <asalkeld> seems ok
07:05:33 <therve> stevebaker, Not in the critical list, but to wrap up the zaqar transport I need tripleO review
07:05:43 <therve> stevebaker, Any idea who I can harass?
07:05:57 <stevebaker> asalkeld: I've been out of the loop for a week, can you give a general update on how convergence changes are going?
07:06:06 <asalkeld> stevebaker: going well
07:06:11 <stevebaker> therve: on os-collect-config?
07:06:28 <asalkeld> stevebaker: there are some patches up for review
07:06:36 <asalkeld> but functional tests improving
07:06:54 <therve> stevebaker, Yeah and tripleo-templates
07:07:02 <asalkeld> ishant_: how can we help with the converg. tests?
07:07:13 <stevebaker> #link https://review.openstack.org/#/q/message:convergence+project:openstack/heat+status:open,n,z
07:07:17 <asalkeld> (or are you mostly done)
07:07:33 <therve> I've seen start on the scenario import, that's pretty cool
07:07:52 <ishant_> asalkeld: Its almost done. Jenkins is failing because of bugs in convergence
07:07:54 <asalkeld> #link https://review.openstack.org/203661
07:08:19 <stevebaker> therve: downstream is about to release, so there will be frantic bug fixing rather than feature reviews :) It will happen. I'll check them out too but I don't have +2
07:08:20 <asalkeld> ishant_: ok, so we should just help with fixing the tests?
07:08:35 <therve> Ah snap
07:08:37 <ishant_> asalkeld: Just need to fix update replace tests
07:08:54 <asalkeld> is someone busy with that?
07:08:57 <ishant_> asalkeld: yes someone needs to fix those
07:09:05 <asalkeld> ok, i could do that
07:09:34 <asalkeld> tho' when i tried, there were lots of other failures
07:09:37 <rakesh_hs> asalkeld: I am working on concurrent update bug
07:09:42 <asalkeld> ok rakesh_hs
07:09:54 <stevebaker> btw I'd prefer the convergence gate to run all heat_integrationtests https://review.openstack.org/#/c/198273/
07:10:48 <ananta_> stevebaker: sure
07:11:11 <stevebaker> #topic High priority bugs http://bit.ly/1FnhaIK
07:11:21 <stevebaker> #link http://bit.ly/1FnhaIK
07:12:43 <huangtianhua> I can't open it:(
07:13:07 <Qiming> huangtianhua, neither can I, bit.ly is blocked
07:13:24 <pas-ha> huangtianhua, works for me (in Ukraine)
07:13:32 <therve> Qiming, https://bugs.launchpad.net/heat/+bugs?field.searchtext=&orderby=-importance&field.status:list=NEW&field.status:list=CONFIRMED&field.status:list=TRIAGED&field.importance:list=CRITICAL&field.importance:list=HIGH&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.om
07:13:32 <therve> it_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search
07:13:34 <stevebaker> here is the full url http://paste.openstack.org/show/398878/
07:13:42 <Qiming> thx!
07:13:50 <pas-ha> https://goo.gl/Nltp9m
07:13:59 <stevebaker> bit.ly? good grief
07:14:31 <therve> Dang oslo crypt is biting us :/
07:14:48 <stevebaker> ricolin: are you working on https://bugs.launchpad.net/heat/+bug/1475057 ?
07:14:49 <openstack> Launchpad bug 1475057 in heat "Resource failure causes nested stacks to be rolled back" [High,New] - Assigned to Rico Lin (rico-lin)
07:14:49 <uvirtbot> Launchpad bug 1475057 in heat "Resource failure causes nested stacks to be rolled back" [High,New]
07:14:50 <uvirtbot> Launchpad bug 1475057 in heat "Resource failure causes nested stacks to be rolled back" [High,New] https://launchpad.net/bugs/1475057
07:15:09 <pas-ha> lol, bot overdrive
07:15:42 <ricolin> survey on it
07:16:05 <ricolin> but not start coding yet
07:16:51 <stevebaker> btw this backport should really get into kilo https://review.openstack.org/#/c/204301/
07:18:25 <pas-ha> stevebaker, kilo is blocked for now, l-2 release coming
07:18:34 <pas-ha> k-2 that is
07:18:40 <stevebaker> oh thats right, bummer
07:19:12 <stevebaker> #topic Tempest checking on resource type list
07:19:20 <stevebaker> Qiming: go
07:19:24 <Qiming> ah, this is mine
07:19:48 <Qiming> refer to link: https://review.openstack.org/#/c/150720/
07:19:56 <Qiming> and link: https://review.openstack.org/#/c/147761/
07:20:18 <Qiming> was tring to "fix" the resource-type-list behavior, for 2 reasons:
07:20:28 <stevebaker> so the current resource type list REST API call returns a list of type strings, which is not extendable
07:20:30 <therve> It's disturbing there isn't a blueprint or a bug
07:20:31 <Qiming> currently, GET /resource_types returns a list of strings: ["OS::Nova::Server", ...]
07:21:03 <Qiming> this is not conforming to API WG guideline here: http://specs.openstack.org/openstack/api-wg/guidelines/representation_structure.html#collection-resources
07:21:21 <Qiming> and it is causing problems in OpenStack SDK: http://git.openstack.org/cgit/stackforge/python-openstacksdk/tree/openstack/resource.py#n859
07:21:21 <stevebaker> we need to keep that behaviour for REST API stability, but we need to decide on how to request the rich type list (a list of dicts)
07:21:43 <Qiming> yes, breaking existing users is really really bad
07:22:03 <Qiming> that is why I'd like to hear what people would suggest
07:22:10 <stevebaker> what did we end up doing for the details flag on resource-list?
07:22:41 <Qiming> the default output from 'GET /resource_types' should be a list of dicts
07:22:55 <therve> Qiming, You can't break compatibility
07:22:58 <asalkeld> i think the only option is to add a new option
07:23:01 <asalkeld> ;)
07:23:08 <Qiming> agreed, therve
07:23:19 <therve> Qiming, So you can't change the default right away
07:23:41 <Qiming> so I was thinking of adding 'resource-types' resource, in addition to to the 'resource_types' resource
07:23:53 <Qiming> not sure this sounds crazy or not
07:23:59 <therve> Yep
07:24:01 <asalkeld> Qiming: yip, crazy
07:24:04 <therve> :)
07:24:05 <Qiming> :)
07:24:25 <Qiming> http://specs.openstack.org/openstack/api-wg/guidelines/naming.html says this:  we should not include underscores in resource names
07:24:32 <stevebaker> how about resource_types?with_detail=true <- this is consistent with the new resource details call
07:24:46 <Qiming> if we strictly follow the guidelines, we should rename resource_types to resource-types
07:25:02 <Qiming> well, the guideline itself sounds crazy too, en?
07:25:22 <therve> It doesn't say to do renames, though
07:25:29 <stevebaker> Qiming: we can fully follow the guidelines when we implement v2
07:25:57 <Qiming> so, for v1, maybe just add a query string?
07:26:29 <therve> Yeah that sounds okay
07:26:45 <Qiming> if that is the right way to go, I will start looking into sdk code and see if it can work there
07:26:52 <stevebaker> yes, we just need to decide whether with_details is appropriate for a list of strings vs a list of dicts. Personally I'm OK with it
07:27:00 <Qiming> also I'll revise the Heat patch and the tempest patch
07:27:13 <asalkeld> stevebaker: seems ok to me
07:27:14 <therve> I don't think it needs a tempest patch
07:27:18 <therve> If you keep compatibility
07:27:28 <Qiming> right, tempest one can be abandoned then
07:27:44 <Qiming> okay, got it, will do
07:28:17 <Qiming> one more thing, do we need a bp for this as therve mentioned?
07:28:29 <therve> At *least* a bug
07:28:41 <Qiming> okay, a bug is it
07:28:43 <stevebaker> Qiming: it would be good if the heat patch had a format function in heat.engine.api. The current dict creating is happening deep elsewhere (environment>)
07:29:10 <Qiming> ah, I see
07:29:19 <stevebaker> #topic Open Discussion
07:30:21 <therve> The review list is huge :/
07:30:27 <stevebaker> that it is
07:30:43 <KanagarajM> stevebaker: updated the heat-review with pending desigante and monasca plugin change-sets.
07:30:53 <stevebaker> KanagarajM: thanks
07:31:34 <KanagarajM> stevebaker: could you approve the monasca https://blueprints.launchpad.net/heat/+spec/support-monasca-alarm-notification in launchpad for l2?
07:32:24 <stevebaker> KanagarajM: sure
07:32:39 <stevebaker> therve: it may well be time to evaluate potentials for heat-core
07:32:46 <KanagarajM> stevebaker: thanks.
07:33:03 <therve> stevebaker, Or just encourage the existing ones :)
07:33:47 <stevebaker> therve: my stick isn't long enough
07:34:01 <therve> :)
07:34:58 <stevebaker> hey, openstack stats is still running http://russellbryant.net/openstack-stats/heat-reviewers-30.txt
07:35:30 <stevebaker> ok, lets finish up unless anyone else has anything
07:35:40 <stevebaker> 3
07:35:42 <pas-ha> +1
07:35:44 <stevebaker> 2
07:35:46 <asalkeld> http://stackalytics.com/report/contribution/heat-group/30
07:35:47 <stevebaker> 1
07:35:49 <asalkeld> also there ^
07:35:50 <stevebaker> #endmeeting