13:59:52 <ricolin> #startmeeting heat
13:59:53 <openstack> Meeting started Wed Aug 29 13:59:52 2018 UTC and is due to finish in 60 minutes.  The chair is ricolin. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:59:54 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:59:56 <openstack> The meeting name has been set to 'heat'
13:59:58 <ricolin> #topic roll call
14:00:23 <ramishra> hi again
14:00:28 <ricolin> haha
14:00:47 <ricolin> #topic PTG
14:01:16 <ramishra> ricolin: I would not be there, not sure if I mentioned that earlier
14:01:38 <ramishra> But will try and join if we've remote participation possible
14:02:15 <ricolin> nope, but no worry, and will try to figure out how everything gonna work
14:02:27 <ricolin> https://etherpad.openstack.org/p/2018-Denver-PTG-Heat
14:02:29 <zaneb> we should probably try to do some remote stuff then, since therve will not be there either
14:02:59 <ricolin> zaneb, agree
14:03:16 <zaneb> we'll see how the wifi is I guess
14:03:17 <ricolin> we can use zoom
14:03:54 <ricolin> I guess I can try to ask more resource or better wifi from foundation
14:04:03 <ricolin> don't know, but will figure out
14:04:53 <ricolin> What we can do is to concentrate all session that require discussion
14:05:04 <ricolin> and leave rest time for actions
14:05:36 <ricolin> like review, do code, or document
14:05:58 <ricolin> we really need to update our document
14:07:07 <zaneb> +1
14:07:09 <ramishra> ricolin: yeah, need some new contributors help us with that
14:08:05 <ricolin> ramishra, I don't think new contributor can understand the entire thing like you guys did
14:08:16 <openstackgerrit> weizj proposed openstack/python-heatclient master: fix bug link in readme  https://review.openstack.org/597538
14:08:25 <ricolin> but we can for sure up a ML out and call for help
14:08:44 <ricolin> What we need to do first is to make a list, and ask for fill up
14:09:26 <ricolin> like we can ask for people to update software config, autoscaling, autohealing, new template function example, etc
14:10:51 <zaneb> it'd be great if we had some low-hanging-fruit bugs or something that we could point new contributors to
14:10:55 <ricolin> ramishra, so if we use Zoom as tool, will that works for you?
14:11:08 <ramishra> ricolin: I think it would
14:11:08 <zaneb> it seems like there's a large pool of people interested in updating the docs
14:11:21 <ricolin> zaneb, there are!
14:12:43 <zaneb> ricolin: RH also has a videoconferencing tool that we could try if we have trouble with zoom
14:13:08 <ricolin> zaneb, actually we can use RH's videoconferencing directly:)
14:13:23 <zaneb> that's fine too :)
14:13:24 <ricolin> if the quality is better
14:13:53 <ricolin> since we got account to access from three peers
14:14:20 <ricolin> Also I'm also plan to send ML out to collect for Use case, or requirement
14:14:36 <ricolin> maybe send out this week
14:14:38 <zaneb> the quality is ordinary as with all videoconferencing tools :D
14:15:14 <ricolin> Okay
14:15:15 <ramishra> I think I used zoom once for a PTG and it was ok not sure which one
14:15:46 <ricolin> the one in Denver
14:15:50 <ricolin> previous Denver
14:16:30 <ricolin> And this time I got a bigger speaker, the the quality in Venue will level up too
14:18:14 <ricolin> Also we not gonna use Friday this time
14:18:38 <ricolin> so it's gonna be two day, virtual+physical conference
14:18:48 * zaneb will be in the TC sessions all day Friday anyway
14:19:34 <ricolin> zaneb, I probably will show up there as well
14:21:20 <ricolin> the rest we just have to fine the right meeting time that suitable for ramishra to join
14:22:46 * ricolin will go ask venue support for better network
14:23:42 <ricolin> That's all from me for PTG now
14:24:13 <ricolin> Any thing from you guys?
14:27:00 <ramishra> ricolin: nothing on PTG
14:27:18 <ricolin> cool
14:27:23 <ricolin> #topic Open discussion
14:27:34 <ricolin> Anything you guys like to discuss?
14:28:28 <zaneb> looks like we're making good progress on the zuul/python3 updates
14:29:28 <ricolin> zaneb, actually we been missing a part, which to convert our zuul script to the new format
14:29:29 <ramishra> zaneb: I updated https://review.openstack.org/#/c/551872/ to ignore all local files when file-container is specified other than the root template
14:30:02 <ricolin> I got a patch for that to give test, but never got time to go back and keep that working
14:30:22 <ricolin> feel free to update that patch:)
14:30:24 <ramishra> We can change the server side to accept the root template name, so we can skip that later too
14:31:14 <ramishra> May be you can check if you're ok with it whenver you've time
14:32:00 <ramishra> Nothing else from my side
14:32:07 <zaneb> ramishra: thanks, I'll try to check as soon as customers stop asking for help ;)
14:32:32 <ricolin> zaneb, that will never stop for sure:(
14:32:36 <ramishra> zaneb: yeah I know;)
14:33:15 <zaneb> ricolin: I know but therve will be back next week ;)
14:35:13 <ricolin> nice
14:36:12 <ricolin> Anything else you guys like to discuss?
14:36:28 <zaneb> ricolin: was https://review.openstack.org/#/c/563082/ the one you meant?
14:36:32 <ramishra> Everything is kind of urgent now a days from customers, lab env issues too;)
14:36:46 <ricolin> zaneb, yes
14:37:00 <zaneb> yeah, that would be nice at some point
14:37:07 <ricolin> and as you can see, it's not working yet
14:37:40 <ricolin> ramishra, agree, that poll a lot of my time too :(
14:39:23 <zaneb> if everyone could just use the latest release that'd be great
14:39:50 <ramishra> converting the jobs to native devstack would need quite a bit ofwork as we create some resources before the tests, though I've not looked at it yet
14:40:25 <ramishra> I've not seen many projects who have done that yet though
14:40:59 <ricolin> ramishra, I think there is not hurry for us:)
14:41:25 <ramishra> that would help us get rid of dependency on devstack-gate
14:41:45 <zaneb> oh hey, I discovered a thing
14:42:15 <zaneb> y'all may have know this already, but I didn't realise that if you edit your profile in storyboard you can turn on email notifications
14:43:03 <zaneb> I haven't actually got any yet...
14:43:22 <ramishra> zaneb: I've it for some time
14:43:24 <zaneb> but at least there's a chance of hearing about stuff happening with bugs I have reported
14:43:44 <ramishra> And it sends too many mails though:/
14:43:49 <ricolin> I actually don't know about that before:)
14:44:07 <zaneb> ok good, I am just slow on the uptake then :)
14:44:33 * ricolin turning that on and see what ramishra mean about too many:)
14:45:05 <ricolin> zaneb, thanks for letting me know!
14:45:51 <zaneb> you can also set the default number of search results to 100 instead of 10
14:46:06 <ricolin> zaneb, that part I know:)
14:46:45 <ricolin> Forgot to put Stein goal to PTG
14:46:59 <ricolin> We need to discuss about Pre Upgrade check as well
14:47:42 <ricolin> #link https://governance.openstack.org/tc/goals/stein/upgrade-checkers.html
14:49:33 <ricolin> ramishra, btw Just got back from Vietnam Infra Day, and appears there are big telocom using Heat alot
14:50:16 <ricolin> like autoscaling and software config
14:50:46 <ricolin> s/telocom/telecom/
14:51:34 <ramishra> ricolin: good to know, hope users would lead to more contributors;)
14:52:34 <zaneb> sorry, network went bye bye
14:53:03 <ricolin> ramishra, I already ask for that
14:53:49 <ricolin> hope they will provide some contributors
14:54:42 <ricolin> I mean some big OpenStack user like OVH, also use Heat
14:55:18 <ricolin> we have to figure out how can we do more to lead people put their effort in upstream
14:56:13 <ricolin> Okay, anything from you guys?
14:57:07 <zaneb> I'm good
14:57:25 <ricolin> BTW, not like you guys don't know, but just for the record, we release some heat repos
14:57:27 <ricolin> #link https://review.openstack.org/#/q/project:openstack/releases+branch:master+topic:release-heat
14:57:49 <ricolin> not sure why https://review.openstack.org/#/c/594949/ still open
14:58:09 <ricolin> I guess it will landed soon
14:58:24 * zaneb +1s
14:58:46 <ricolin> zaneb, right! I definitely need your +1 for that!
14:58:49 <ricolin> thanks:)
14:59:32 <zaneb> we discussed it already so I don't know why I didn't review it then
15:00:08 <ricolin> zaneb, you actually did by fined the failing reason with me:)
15:00:59 <ricolin> Okay, let's end the meeting now, I will try to comes up with some schedule for PTG before next week
15:01:22 <ricolin> also a message out for collect use case/ user requirement
15:01:52 <ricolin> ramishra, zaneb thank you for your time!
15:01:55 <ricolin> #endmeeting