16:01:12 <priteau> #startmeeting blazar
16:01:13 <openstack> Meeting started Thu Sep 26 16:01:12 2019 UTC and is due to finish in 60 minutes.  The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:14 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:17 <openstack> The meeting name has been set to 'blazar'
16:02:40 <priteau> #topic Roll call
16:02:51 <priteau> Hi diablo_rojo__
16:02:55 <priteau> Oops sorry
16:02:57 <priteau> Hi diurnalist
16:03:03 <diurnalist> o/
16:03:04 <diablo_rojo__> priteau, lol no worries
16:03:32 <priteau> Agenda for today:
16:03:34 <priteau> * Train release
16:03:36 <priteau> * PTG
16:03:39 <priteau> * AOB
16:03:43 <priteau> #topic Train release
16:04:33 <priteau> We're tagging rc1 this week
16:04:57 <priteau> diurnalist: Do you think you would be able to rebase your patches on top and test it by the release date?
16:05:23 <diurnalist> yes, that should be possible. remind me of the release date?
16:06:34 <priteau> Well, final RC is Oct 07 - Oct 11
16:06:38 <priteau> #link https://releases.openstack.org/train/schedule.html
16:07:14 <diurnalist> thanks, i will put it on my calendar. that should be enough time though, we'll just have to test a deployment next week. are you mostly concerned with regressions?
16:08:03 <priteau> Yes, any regression as we've had some major changes such as microversions
16:08:13 <priteau> It could impact anything in the API
16:08:39 <diurnalist> sure thing.
16:09:58 <priteau> Unfortunately we couldn't get some contributions from jake, let's try to get them merged as soon as possible in Ussuri
16:10:02 <priteau> Network reservation in particular
16:10:41 <diurnalist> yep, that will be important. i'd also be interested in formalizing the usage-enforcement mechanisms to an external service
16:11:02 <diurnalist> as we seem to keep finding rules or features to experiment with around this, and adding in blazar is a bit awkward
16:11:03 <priteau> Indeed, that would be useful.
16:11:27 <diurnalist> perhaps a topic for the PTG?
16:12:35 <priteau> Yes, let's cover it as part of PTG discussions
16:12:47 <priteau> Which brings me to the next topic
16:12:53 <priteau> #topic PTG
16:13:14 <priteau> So I understand Jake will be in Shanghai?
16:13:40 <diurnalist> Yep! he's getting that all sorted out now
16:17:40 <priteau> Great. I think it makes sense to allocate time for discussions then
16:17:49 <priteau> I will get in touch with the foundation to make sure we have some space
16:18:06 <priteau> I won't be in Shanghai but will have a meeting with the rest of the team the week before
16:18:33 <diurnalist> sounds great. - who would be participating then? are other core members going to be in shanghai?
16:18:46 <priteau> tetsuro, bertys and masahito will be there
16:19:24 <diurnalist> great
16:19:25 <priteau> Basically all core reviewers, except me
16:20:12 <priteau> I'll also create an etherpad for discussions, I will share it with you
16:20:18 <priteau> (and Jake)
16:21:09 <priteau> Anything else to discuss about the PTG?
16:22:20 <diurnalist> i don't think so
16:22:46 <priteau> #topic AOB
16:23:02 <priteau> Any other update? How is Blazar working for you?
16:23:26 <diurnalist> what does AOB mean? all other business?
16:23:32 <diurnalist> haha
16:24:07 <diurnalist> blazar is working well, BUT there is still this bug that haunts me on a weekly basis. something can happen where leases get stuck in pending and you have to restart blazar-manager to get them to start.
16:24:27 <diurnalist> my suspicion is that some SQL client gets an error and then caches some sort of bad connection and can't get out of it
16:24:33 <priteau> diurnalist: Any Other Business
16:24:34 <diurnalist> but i haven't successfully tracked it down yet
16:24:50 <diurnalist> i should really file a bug for this...
16:24:53 <priteau> It definitely seems related to SQL
16:25:05 <priteau> Have you tried enabling more sqlalchemy debug logs?
16:25:22 <priteau> They might get very verbose until you hit the error though...
16:25:49 <diurnalist> i have not. fortunately, I think the bug is pretty easy to trigger. you just have to restart the MySQL database or otherwise interrupt its connection to blazar
16:25:59 <diurnalist> how can i explicitly enable sqlalchemy debug?
16:27:44 <priteau> In the [DEFAULT]/default_log_levels, you may have sqlalchemy=WARN, you can increase the verbosity there
16:28:18 <diurnalist> great, will try that. i will also file a bug for this
16:28:38 <priteau> Thank you
16:28:50 <priteau> I have to leave shortly, let's end here for today
16:28:55 <priteau> Thanks for joining
16:29:22 <diurnalist> cheers
16:29:25 <diurnalist> bug here btw https://bugs.launchpad.net/blazar/+bug/1845531
16:29:25 <openstack> Launchpad bug 1845531 in Blazar "Leases stuck in PENDING indefinitely" [Undecided,New]
16:29:50 <priteau> Thank you
16:29:51 <priteau> #endmeeting