19:01:41 <hogepodge> #startmeeting refstack
19:01:42 <openstack> Meeting started Tue Sep  5 19:01:41 2017 UTC and is due to finish in 60 minutes.  The chair is hogepodge. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:01:43 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:01:46 <openstack> The meeting name has been set to 'refstack'
19:01:53 <catherineD> o/
19:02:03 <rockyg> o/
19:02:20 <hogepodge> #link Agenda https://etherpad.openstack.org/p/refstack-meeting-17-09-05
19:03:07 <mguiney> o/
19:03:10 <hogepodge> Give a few minutes for people to arrive.
19:03:24 <hogepodge> In the meantime, please add agenda items
19:04:31 <hogepodge> #topic PTG
19:04:49 <pvaneck> o/
19:05:54 <hogepodge> #link PTG Agenda https://etherpad.openstack.org/p/InteropDenver2017PTG
19:06:20 <hogepodge> Unless we need to reorganize things, Monday will be dedicated to InteropWG and Tuesday will be dedicated to RefStack.
19:07:30 <hogepodge> I'll be filling out exact times, if you have preferences for when we discuss topics, please indicate them. I'm working out remote attendance information. We'll probably use zoom conferencing and I'm looking for bluetooth speakers/microphones
19:07:36 <rockyg> do we have a conference call number or zoom sessionyet?
19:08:00 <rockyg> You type too fast
19:08:01 <hogepodge> I have the zoom conferencing, I'll put it into the etherpad.
19:08:59 <hogepodge> Related to that, we won't have our regularly scheduled IRC meeting next week because of the PTG. Regular meetings will resume on September 19.
19:10:23 <hogepodge> What I'm going to try and do is use my phone for the zoom link, and attach a bluetooth microphone/speaker and use the phone camera for video.
19:10:41 <hogepodge> Any other comments on the PTG?
19:11:04 <rockyg> We'v3e got some request on timing for microversion session
19:11:15 <hogepodge> sure
19:11:17 <rockyg> So, maybe some timeslots?
19:11:33 <rockyg> Also, might n
19:11:49 <hogepodge> How long do we want sessions to last? 45 minutes with 15 minute breaks?
19:11:52 <rockyg> want to have an overview of what subunit inclusion means
19:12:04 <hogepodge> I can build out a schedule from that.
19:12:14 <rockyg> Great.
19:13:58 <hogepodge> Without further comments, moving on
19:14:09 <hogepodge> #topic verification field update
19:14:22 <hogepodge> mguiney: looks like we ran into some problems?
19:14:40 <mguiney> yep! found some issues, documentations holes, etc
19:15:52 <mguiney> the thing that's got it failing gate tests is just a issue that happens in unit testing. i think i just need to use a different method of checking whether the object is iterable, given that the method i'm currently using seems to be throwing some errors
19:16:24 <hogepodge> mguiney: catherineD: we have a data set to test against, right?
19:16:34 <mguiney> but while i was cleaning up the bugs, i also cleaned up a big of code flow as well, for the sake of easier debugging, so those are included in this patch set as well
19:16:47 <mguiney> I do.
19:16:55 <hogepodge> Is there a way we could get that database dump somewhere in a public place where we could use it for testing?
19:16:59 <rockyg> Great.
19:17:12 <mguiney> ^ was just going to ask about that
19:17:57 <mguiney> I have a small (very small) toolkit that I use for refstack dev and debugging, as well as a decent dataset with a number of test cases
19:18:27 <hogepodge> I'm not sure how other projects manage a mock dataset like that
19:18:41 <hogepodge> (or if they do... it might be a difficult thing to maintain)
19:18:56 <hogepodge> Could be a small PTG topic and work item.
19:19:07 <rockyg> sounds good.
19:19:11 <hogepodge> mguiney: do you have an estimate on when the update tool might be ready to try out again?
19:19:12 <mguiney> I was wondering if it would make sense to make those publicly available, to ease the barrier to entry to new/casual contributors, anyone looking to grab a quick dataset, etc
19:19:22 <mguiney> as soon as this patch is merged.
19:19:47 <rockyg> good ideas
19:19:56 <hogepodge> mguiney: ok
19:19:59 <rockyg> add the testsets to the repo
19:20:14 <rockyg> with a good readme
19:21:09 <mguiney> sounds good. I also have one more thing I want to do with this tool, but it in no way affects functionality- it just does a little more to make sure you have a proper auth token, etc
19:21:20 <hogepodge> catherineD: pvaneck: luzC: any thoughts on that?
19:21:44 <hogepodge> mguiney: +1
19:21:52 <mguiney> this was something suggested to me at the boston summit by catherineD, but it would be a very minor patch
19:22:11 <mguiney> so it wouldnt hold up the run on the prod server
19:22:30 <catherineD> mguiney: yup
19:23:36 <mguiney> It seemed a bit more daunting back then, but given that I currently have a script of my own that does tokengen and auth checking anyways, it should be trivial to implement as a built in part of the tool itself.
19:24:04 <hogepodge> Cool, I think it's a good idea.
19:24:34 <hogepodge> any other items on this topic?
19:24:40 <mguiney> but regardless: for the current bugfix, I just need reviews, so that we can get this merged and hand it to infra
19:24:58 <mguiney> nope, nothing more :)
19:25:55 <hogepodge> #topic subunit result upload
19:26:21 <hogepodge> #link merged spec https://review.openstack.org/#/c/480298/
19:26:27 <mguiney> \o/
19:26:29 <hogepodge> The spec merged this morning
19:26:44 <hogepodge> Implementation is in progress. Starting with database management
19:27:14 <hogepodge> #link alembic table update https://review.openstack.org/#/c/498735/
19:27:55 <hogepodge> Also WIP. I'm hoping we'll have time to move the needle forward on this during the PTG. Maybe some later day work sessions.
19:28:04 <hogepodge> mguiney: any comments on the work?
19:28:08 <hogepodge> anyone else too?
19:28:57 <catherineD> no will review when it is ready (WIP removed)
19:29:16 <mguiney> ah yes
19:29:40 <mguiney> so it works!
19:30:09 <hogepodge> Still waiting on gate jobs to pass?
19:30:25 <hogepodge> We'll keep an eye on it this week and review.
19:30:51 <mguiney> to get it there, i ended up iterating through a number of solutions, etc, but it's fully automatic in that it checks and updates from conf on its own, without having to concern the user, which is nice
19:31:13 <hogepodge> that sounds great
19:31:25 <mguiney> but yes, stylefixes/gate check stuff. which is interesting, because it is passing tox checks in my env
19:31:25 <rockyg> ++
19:32:52 <mguiney> because of the fact that it's passing tests locally and then throwing them when pushed for review, i'm concerned about the fact that i'm essentially error checking/debugging blind
19:33:11 <mguiney> but it should be fine shortly
19:33:35 <hogepodge> mguiney: we can take a look at that. I'd like to be able to reproduce the testing locally
19:34:21 <hogepodge> ok, any other discussion?
19:34:44 <mguiney> nope, other than that, all good!
19:34:57 <catherineD> nope I am good
19:35:13 <hogepodge> #topic pending reviews
19:35:21 <hogepodge> Two reviews
19:35:31 <hogepodge> #link https://review.openstack.org/#/c/489421/  Tempest Configuration Script Spec
19:35:53 <hogepodge> #link https://review.openstack.org/#/c/395426/ Style cleanup (hogepodge)
19:36:35 <hogepodge> For the tempest configuration spec script, we'll look for an owner to follow up on that work at the PTG if David isn't available to work on it
19:36:49 <hogepodge> On the style cleanup, I've taken ownership of it, just have to get the work in on it.
19:36:51 <catherineD> maybe check with David at PTG for https://review.openstack.org/#/c/489421/
19:37:09 <hogepodge> catherineD: I haven't seen him on irc much, but I can send him an email
19:37:58 <catherineD> sure I think he will be at PTG then a f-2-f would be great
19:38:27 <hogepodge> agreed
19:39:14 <hogepodge> nothing else more? moving on.
19:39:24 <hogepodge> #topic open discussion
19:42:14 <hogepodge> Have a great week everybody. See you at the PTG! (In person or remotely)
19:42:17 <hogepodge> Thanks!
19:42:21 <catherineD> bye
19:42:27 <mguiney> have a good week, y'all!
19:42:30 <rockyg> next week on zoom!
19:42:44 <hogepodge> #endmeeting