17:00:49 <hogepodge> #startmeeting refstack
17:00:50 <openstack> Meeting started Tue Oct  3 17:00:49 2017 UTC and is due to finish in 60 minutes.  The chair is hogepodge. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:51 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:54 <openstack> The meeting name has been set to 'refstack'
17:02:13 <hogepodge> #link https://etherpad.openstack.org/p/refstack-meeting-17-10-03 agenda
17:02:40 <chandankumar> hogepodge: \o/
17:02:54 <hogepodge> I totally forgot to move the meeting in my calendar and nearly missed it.
17:02:58 <mguiney> awesome!
17:03:23 <hogepodge> Thank you mguiney for the reminder :-D
17:04:54 <hogepodge> #topic Tempest autoconfiguration
17:04:59 <hogepodge> #link https://review.openstack.org/#/c/489421/ spec
17:05:17 <hogepodge> no changes from last week, we might might to take it over to finish it off
17:05:28 <chandankumar> hogepodge: here is the patch https://review.openstack.org/#/c/508502/ to import tempestconf to openstack namespace
17:05:40 <hogepodge> chandankumar: I was just about to ask about that :-)
17:05:50 <chandankumar> hogepodge: one more thing RDO/Tripleo guys are ok to keep it under refstack
17:06:08 <chandankumar> hogepodge: i will send a patch under governance after the meeting
17:06:54 <hogepodge> Excellent. I just +1'ed it with approval to take under RefStack project governance.
17:07:04 <chandankumar> hogepodge: thanks :-)
17:07:10 <hogepodge> chandankumar: how would you feel about taking ownership on the spec patch?
17:07:35 <chandankumar> hogepodge: yes sure i can take that
17:07:47 <hogepodge> thank you
17:08:01 <chandankumar> hogepodge: i will update the spec before next meeting
17:09:04 <hogepodge> cool. any other comments on this item?
17:09:19 <chandankumar> nope from my side.
17:09:34 <hogepodge> #topic Subunit Upload
17:10:27 <mguiney> it looks like the current spec patch is running into zuul issues
17:10:31 <hogepodge> mguiney: you want to take this?
17:10:38 <hogepodge> mguiney: zuul is having issues
17:11:04 <mguiney> yeah, i had kind of noticed, so hopefullyit wont be too much of a hindrance.
17:11:44 <mguiney> so firstoff, if anyone hasn't reviewed, please take a look and see if you have any comments or concerns
17:12:49 <mguiney> i know its long, mea culpa, but it is up to date and ready for review
17:12:56 <hogepodge> bower angular#1.3.15         EAI_AGAIN Request to https://registry.bower.io/packages/angular failed: getaddrinfo EAI_AGAIN registry.bower.io:443
17:13:07 <hogepodge> that's what's failing
17:13:14 <mguiney> ahhh ok
17:13:30 <mguiney> so the thing I mostly wanted to bring up, other than asking for reviews, is this:
17:13:38 <hogepodge> but it looks like the request is ok, so not sure what it is. We can try to recheck
17:15:00 <mguiney> because of the security concerns of those outside of interop, most of the listed capabilities are admin ones. This has the unfortunate side effect of making it difficult, once a nonadmin user has submitted the subunit data, to check if it has successfully been added.
17:15:26 <hogepodge> mguiney: I think that catherine makes a good point, a user should be able to view their own data
17:15:59 <mguiney> oh look more reviews. heh. apologies, hadnt read through yet
17:16:03 <hogepodge> It's a pretty standard model for admin and self to be able to view something. In this case, we can also delete if data hasn't been marked as used for validation
17:16:25 <hogepodge> does that address your issue?
17:17:12 <mguiney> yep. this is a lot simpler now that we are requiring authed data upload
17:17:38 <mguiney> come to think of it. excellent, yes. that takes care of it. i'll update the spec
17:17:44 <hogepodge> great
17:17:45 <mguiney> thank you!
17:18:40 <hogepodge> I still need to disable anonymous upload. At this point it's mainly refactoring the tests to reflect the new status quo. I'm thinking of adding a config flag, though, to prevent regressions for current users.
17:18:48 <hogepodge> (users as in server deployers)
17:18:51 <mguiney> other than that, we now have the associated alembic update patch passing tests, so hopefully we can work til getting it merged
17:19:04 <hogepodge> mguiney: link?
17:19:28 <catherineD> o/  sorry
17:19:29 <mguiney> #link https://review.openstack.org/#/c/498735/
17:21:01 <hogepodge> mguiney: still have red on coverage
17:21:48 <mguiney> oh dear. ok i'll take another look
17:22:29 <hogepodge> once we sort it out we'll be good to go. Sorry to be a stickler on it.
17:22:52 <hogepodge> hi catherineD! no worries, I made the exact same mistake and mguiney saved me
17:23:14 <mguiney> no worries, it makes sense to sort it out now rather than wonder about any failure down the road
17:23:23 <catherineD> old habbit on previous time
17:25:35 <hogepodge> mguiney: anything more on this topic?
17:25:47 <mguiney> nope! just have to update the patches!
17:26:23 <hogepodge> #topic Result Verification Field and Update
17:26:35 <hogepodge> this is where I was supposed to talk about anonymous upload disabling
17:27:15 <hogepodge> It's one of the first steps forward, the work will involve creating a new config option to disable it, then writing tests to make sure functionality works
17:27:57 <hogepodge> we want to have anonymous uploads disabled before we run the script to sweep the database
17:28:04 <hogepodge> mguiney: anything else to add on this
17:28:15 <hogepodge> mguiney: particularly, any reviews that you think are ready?
17:30:17 <hogepodge> It looks like the lint job keeps failing, but it's hard for me to tell why
17:30:44 <hogepodge> actually, I guess not. zuul instability
17:31:08 <mguiney> i have an auto token gen patch for the database update script, as well as the refstack bugfix, which is just hung up on zuul jobs
17:31:26 <mguiney> #link https://review.openstack.org/#/c/499956/
17:31:28 <hogepodge> ok, once the gate settles down we'll check in on the jobs
17:31:40 <mguiney> https://review.openstack.org/#/c/503495/
17:31:47 <mguiney> o7
17:32:38 <catherineD> hogepodge: may be ask infra to help on the zuul failure?
17:32:43 <hogepodge> that last one is dependent, so I'll wait on that
17:32:54 <hogepodge> catherineD: they're aware of it, and are rolling back zuul v3 to zuul v2
17:33:31 <catherineD> ic ..
17:33:44 <hogepodge> anything else on this topic?
17:34:34 <mguiney> nope!
17:35:03 <hogepodge> #topic Replace ostestr with tempest run
17:35:45 <hogepodge> Nothing much for me to add here. I need to apply the fixes Paul suggested and just test it. I had a few emergency work items come up so I've been occupied with those
17:36:28 <hogepodge> I'll leave it open for a minute or so before moving on
17:36:58 <hogepodge> #link https://review.openstack.org/#/c/503209/
17:37:18 <hogepodge> #topic API Docs
17:37:28 <hogepodge> This work is backlogged, unless anyone wants to grab it
17:39:07 <hogepodge> hearing no takers, onward
17:39:12 <hogepodge> #topic Open Discussion
17:39:14 <mguiney> (would but notime)
17:39:24 <hogepodge> oops
17:39:31 <hogepodge> #topic Sydney Planning and Open Discussion
17:40:01 <hogepodge> If you're going to be in Sydney, add your name to the link. If you aren't, I'll try to get video conferencing for important meetings set up
17:40:09 <hogepodge> Any other topics?
17:42:04 <hogepodge> once, twice...
17:42:36 <hogepodge> Thanks everyone! Same new time next week! In two weeks I will be on travel to Austin and will likely not be able to run the meeting.
17:43:24 <hogepodge> #endmeeting