15:00:38 <zaneb> #startmeeting heat
15:00:44 <openstack> Meeting started Wed May 31 15:00:38 2017 UTC and is due to finish in 60 minutes.  The chair is zaneb. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:46 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:48 <openstack> The meeting name has been set to 'heat'
15:01:47 <zaneb> #topic roll call
15:01:48 <therve> Yop
15:02:01 <ramishra> hi
15:02:31 <zaneb> Rico asked me to help out with running the meeting this week
15:02:57 <zaneb> could be a short one
15:03:04 <ramishra> Rico seems to be away this week, so assumed no meeting;)
15:03:10 <zaneb> #topic Adding items to agenda
15:03:26 <LanceHaig> I am here sorry for being late
15:03:27 <zaneb> #link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282017-05-31_1500_UTC.29
15:03:55 <zaneb> only recurring stuff on the agenda, anybody got anything to add?
15:04:18 <LanceHaig> nothing we are not talking about on the list
15:05:12 <zaneb> #topic Weekly report
15:05:18 <zaneb> I have nothing to report :)
15:05:28 <LanceHaig> :-)
15:05:43 <zaneb> #topic pike-2 status
15:05:51 <ramishra> We had no of issues with the gate, we disbaled the newly added snapshot-restore functional tests
15:06:04 <zaneb> #link https://launchpad.net/heat/+milestone/pike-2
15:06:19 <ramishra> there are still some issues and a few fixed to land
15:06:37 <ramishra> oh, we moved on to the next topic;)
15:06:50 <zaneb> ramishra: yeah, sorry :)
15:07:01 <zaneb> we can come back to it at the end
15:07:17 <zaneb> I'm just updating some of these blueprints
15:07:27 <zaneb> https://blueprints.launchpad.net/heat/+spec/mistral-new-resource-type-workflow-execution has merged
15:07:39 <therve> Yeah, I kept it opened for tests, if they happen
15:08:30 <therve> So I'm mostly worried about trunk support
15:08:31 <zaneb> I think we should bump TrunkPort Support to pike-3
15:08:41 <therve> For sure
15:08:44 <zaneb> since pike-2 is, like, next week right?
15:08:48 <therve> But still, we don't see much progress
15:08:52 <therve> AFAIK yeah
15:09:11 <zaneb> oh, there is no pike-3 milestone in launchpad
15:09:29 <ramishra> I've been reviewinng the first patch in that series, but it's slow
15:09:42 <therve> zaneb, I can create it
15:10:12 <therve> Done
15:10:13 <zaneb> you can do that?
15:10:22 * zaneb always assumed that magic pixies did it
15:10:34 <therve> I don't think so no
15:10:46 <zaneb> cool, that's moved then
15:10:50 <zaneb> thanks therve
15:12:17 <zaneb> I think StackDefinition class is probably going to slip to pike-3 as well
15:12:21 <therve> We'll let Rico moves the bugs :)
15:12:30 <zaneb> though it's getting fairly close
15:13:10 <zaneb> I should be able to get it passing tests this week
15:13:38 <zaneb> I'll go ahead and bump it though
15:14:07 <zaneb> couple of unassigned high-priority bugs
15:14:48 <zaneb> would be nice to get eyes on those
15:14:52 <zaneb> ok
15:15:01 <zaneb> #topic Open discussion
15:15:17 <zaneb> ramishra: anything we need to discuss in the meeting about the gate issues?
15:15:40 <ramishra> uwsgi support patch is passing the gate https://review.openstack.org/#/c/462216/
15:16:39 <ramishra> so the default would be apache+uwsgi, I still kept the non-apache job as it is
15:17:49 <ramishra> grenade job uses mod_wsgi as it's using ocata
15:19:08 <ramishra> reg gate issues, https://review.openstack.org/#/c/469328/ would fix the last bit of multiple networks found for 'my_net' related failures
15:19:37 <zaneb> ramishra: so you didn't change the Apache settings in the end?
15:19:52 <ramishra> zaneb: nope
15:20:29 <ramishra> client patch fixed the issue
15:21:14 <zaneb> ramishra: I notice you also had to do https://review.openstack.org/#/c/462216/16/heat/common/identifier.py
15:22:08 <ramishra> I did change the iptables rules in the images with a project-config patch
15:22:09 <ramishra> zaneb: yeah
15:24:10 <ramishra> No hurry, but this is in the revised pike community goal:)
15:24:23 <ramishra> so good to have some reviews
15:24:24 <zaneb> ramishra: so e.g. existing alarms would break if you upgraded to this configuration
15:25:01 <ramishra> zaneb: why would they break?
15:25:04 <zaneb> of course they'd break anyway if you move the endpoint in the process of switching to Apache
15:25:29 <ramishra> ok, I understand
15:25:47 <zaneb> ramishra: because whatever it triggering the alarm would have the old URL with the % escaping, and Apache is 404ing them
15:26:26 <ramishra> zaneb: you mean '/' % is not an issue
15:26:26 <zaneb> so given that you have to move to port 80 to switch to Apache, maybe its not a big deal
15:26:54 <zaneb> I mean escaping '/' with %something
15:27:25 <ramishra> if it's running with apache, anyway apache would be doing it atm
15:28:06 <ramishra> with that directive
15:28:22 <zaneb> how are tests passing with apache now then?
15:29:51 <ramishra> We've     AllowEncodedSlashes On directive set, if I understand your question
15:30:00 <ramishra> http://logs.openstack.org/10/468010/1/check/gate-heat-dsvm-functional-convg-mysql-lbaasv2-ubuntu-xenial/895306e/logs/apache_config/heat-api.conf.txt.gz
15:30:04 <zaneb> ah, ok
15:30:41 <zaneb> I'm not clear on why we wouldn't keep that on
15:30:49 <zaneb> but we can take it up in the review
15:31:09 <ramishra> zaneb: If we can find a way to fo that
15:31:22 <zaneb> anybody got anything else?
15:31:38 <ramishra> however, it does not add any value as we anyway don't support / in stack name or resource name
15:31:58 <ramishra> I assume we discussed that in the ML thread
15:32:52 <zaneb> we did
15:34:19 <zaneb> ok, let's adjourn until next week
15:34:25 <zaneb> thanks everyone!
15:34:30 <zaneb> #endmeeting