19:04:34 <hogepodge> #startmeeting refstack
19:04:35 <openstack> Meeting started Tue Aug 22 19:04:34 2017 UTC and is due to finish in 60 minutes.  The chair is hogepodge. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:04:36 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:04:39 <openstack> The meeting name has been set to 'refstack'
19:05:33 <pvaneck> o/
19:05:36 <catherineD> o/
19:05:56 <hogepodge> Hey everybody, sorry for being a few minutes late.
19:05:56 <mguiney> o/
19:06:15 <catherineD> hogepodge: np
19:06:24 <hogepodge> Agenda is here
19:06:31 <hogepodge> #link Agenda https://etherpad.openstack.org/p/refstack-meeting-17-08-22
19:06:51 <hogepodge> #topic PTL Transition
19:07:28 <hogepodge> Want to make sure we have a good transition between catherineD and myself
19:07:35 <catherineD> for sure
19:07:46 <hogepodge> #link Updated the meeting invitation https://review.openstack.org/#/c/496296/
19:08:02 <hogepodge> Can anyone think of anything else we need to update?
19:08:31 <catherineD> athough we are not using launchpad but sometime people still use it .. I think we need to update the lauchpad too ..
19:08:39 <hogepodge> I also wanted to check in and see what catherineD and pvaneck availablity was like
19:08:48 <catherineD> so I will add your name to the launchpad team just incase
19:08:51 <hogepodge> catherineD: Ok, let's add that as an action item.
19:08:55 <hogepodge> catherineD: thank you
19:09:32 <catherineD> the next thing I think of is go thru code release to the website one time with you ...
19:09:55 <catherineD> whenever we want to update the website
19:09:56 <hogepodge> catherineD: cool. Let's schedule that. With the 2.0 schema patch I was wondering about how that worked
19:10:38 <catherineD> yea let's merge Paul's https://review.openstack.org/#/c/484625/
19:10:42 <pvaneck> hogepodge: refstack availability will be sparse, but I can still continue to submit patches for fixes and maintenance
19:11:12 <catherineD> pvaneck: ++
19:11:16 <hogepodge> pvaneck: ok, so starting now :-/
19:11:22 <hogepodge> that's good to know
19:12:17 <catherineD> hogepodge: same for me ... mainly for transition, fixes, etc .. won't have time for new features
19:12:23 <hogepodge> ok
19:12:53 <hogepodge> Anything else we need to think about for the transition?
19:13:37 <hogepodge> #topic Update Verification Field
19:13:52 <hogepodge> mguiney: catherineD: updates on this?
19:14:38 <mguiney> ok! so i have been testing, and ran into a couple cases which seem to break my script
19:15:20 <mguiney> i will be fixing the hole in the code that is causing that as well as cleaning it up a bit in general, and then pushing a patch
19:15:26 <hogepodge> ok, great
19:15:35 <mguiney> (it is a fairly gaping hole, unfortunately)
19:15:40 <hogepodge> mguiney: are you using a mock database to test this?
19:15:50 <mguiney> oh yes
19:16:20 <hogepodge> catherineD: pvaneck: do you have a development database we can use for further testing? I'd hate to have to rebuild something from scratch.
19:16:28 <mguiney> i took some time to spin up a whole bunch of test cases, and am running my results against my local refstack server
19:17:27 <catherineD> In my testing, I always built the env inclduding db from the scratches using the README file ..
19:17:46 <mguiney> ok, that's the same thing i'm doing
19:18:03 <hogepodge> mguiney: cool, let's try to capture that in some way for future testing
19:18:19 <catherineD> I would suggest that you build one development env from scratch and then do a image save etc for your env
19:18:30 <catherineD> like a snapshot
19:18:47 <hogepodge> if we could do a db dump, we could make it publicly available as part of a testing toolkit
19:18:53 <mguiney> i have canned results, a canned spreadsheet based on those results, and an automation script for consistent setup/teardown/testing of the script
19:18:58 <mguiney> just for faster testing
19:19:04 <hogepodge> Then if there are additions to handle test and corner cases they are available to everyone
19:19:24 <hogepodge> or something like mguiney has to generate a standard test db
19:19:28 <catherineD> mguiney: I just sent you one subunit file ..
19:19:41 <mguiney> i saw, thank you. that is much appreciated
19:20:05 <catherineD> you can use that to submit to your test system repeatly and use that as your db
19:20:46 <mguiney> ah, ok. I will add that to my existing setup, thank you
19:21:55 <hogepodge> Ok, we'll check in next week on this topic.
19:22:25 <mguiney> excellent!
19:22:26 <hogepodge> #topic subunit result file upload
19:23:17 <hogepodge> starting from the bottom spec review
19:23:30 <hogepodge> #link https://review.openstack.org/#/c/480298/
19:23:41 <hogepodge> still a wip, where are we on that?
19:23:47 <hogepodge> mguiney: ?
19:24:23 <mguiney> the only change to that is that i changed it ever so slightly to reflect that we may add a config flag to allow for using an external db, as was requested in last week's meeting
19:24:49 <hogepodge> ok, so we should be close to final?
19:24:55 <hogepodge> any other comments on the spec?
19:25:32 <mguiney> yep. the implementation pivots i've had to do are well withing the bounds described in the current spec version
19:26:13 <pvaneck> yea, i think the spec is fine from what I can tell.
19:26:51 <hogepodge> So the order will be to have the spec land, then first implementation detail is
19:26:54 <hogepodge> #link https://review.openstack.org/#/c/487185/
19:27:38 <hogepodge> We should probably update the high-level tasks in the agenda to reflect that
19:28:01 * hogepodge notes he also needs to check in storyboard to make sure everything is synched up...
19:28:28 <mguiney> i may also make one last revision to the spec to update the actionable items
19:28:49 <mguiney> they are technically accurate, but not particularly helpful in terms of laying out a plan
19:28:50 <hogepodge> mguiney: ok
19:30:09 <mguiney> yeah, it looks like these are based on a past set of assumptions that is no longer true
19:30:47 <mguiney> though the changes shouldn't be super major. as is, the actionable items in the agenda are probably a better representation, at the moment
19:31:05 <hogepodge> ok
19:31:28 <hogepodge> any other comments on this work?
19:32:52 <hogepodge> ok moving on
19:32:59 <hogepodge> #topic Pending Reviews
19:33:15 <hogepodge> #link https://review.openstack.org/#/c/484625/ (Add UI support for interop schema 2.0)
19:33:26 <hogepodge> This one looks ready to merge
19:33:29 <catherineD> we should merge this patch
19:33:45 <hogepodge> catherineD: then you can show me how to update the production site? :-D
19:33:52 <catherineD> hogepodge: exactly
19:34:04 <catherineD> take that as an exercise
19:34:51 <hogepodge> haha yes. Just +2/+1ed it. Thank you pvaneck for that work!
19:35:05 <pvaneck> :)
19:35:08 <catherineD> great ...
19:35:19 <hogepodge> This is an older patch
19:35:21 <hogepodge> #link https://review.openstack.org/#/c/395426/ (Assert style fix)
19:35:39 <catherineD> I will document some note and email to you ...
19:35:44 <hogepodge> Seems simple enough, but appears abandoned. I'll take it over and implement the suggestions from the patches.
19:35:46 <hogepodge> catherineD: thank you
19:36:02 <catherineD> I usually update the site on Friday hope for less traffice and just incase something happen
19:36:13 <hogepodge> catherineD: good plan
19:37:32 <catherineD> hogepodge: go for it with  the assert style fix
19:38:02 <hogepodge> catherineD: thanks
19:38:21 <hogepodge> #link https://review.openstack.org/#/c/226902/ (Add spec for vendor registration)
19:38:35 <hogepodge> This one is pretty old. Any reason we should keep it around?
19:38:43 <catherineD> oh we should abandon that one
19:39:26 <mguiney> dang, that *is* old
19:39:34 <catherineD> the entire vendor registration process had already implemented ...
19:39:43 <hogepodge> catherineD: ok.
19:40:52 <hogepodge> #link https://review.openstack.org/#/c/491936/ (Update default Tempest version to tag 16.1.0 (July 10, 2017))
19:41:04 <hogepodge> I don't see any reason to hold this one back
19:41:15 <hogepodge> Although with the new release it will be updated soon.
19:41:36 <hogepodge> Do we have a protocol for testing tempest releases against old clouds?
19:42:20 <catherineD> I have 3 clouds env internally ... I do test them
19:42:48 <hogepodge> catherineD: covering different releases?
19:43:09 <catherineD> basically whenever there is a new guideline, and whenever we update default tempest release
19:43:28 <catherineD> yes different OpenStack releases that is covered by the guideline
19:43:36 <catherineD> not the newest one
19:43:44 <hogepodge> I think long term we might want to set up a gate process that can test interop tests against the version of tempest as far back in releases as we can go.
19:44:04 <catherineD> yea
19:44:32 <catherineD> ++
19:44:37 <hogepodge> #action hogepodge mguiney to look at adding gate processes for tempest against releases
19:44:54 <hogepodge> catherineD: we good to merge on that patch?
19:45:07 <catherineD> yes I think so
19:45:24 <catherineD> already tested
19:45:29 <hogepodge> mguiney: do you want to +2/+1 that patch?
19:45:37 <mguiney> can do
19:45:58 <hogepodge> alright!
19:46:07 <catherineD> mguiney: hogepodge: thx
19:46:13 <hogepodge> #link https://review.openstack.org/#/c/489421/ (Tempest Configuration Script Spec)
19:47:02 <hogepodge> This is from David Paterson (don't know his irc handle)
19:47:02 <catherineD> I guess David is still working on that patch
19:47:24 <hogepodge> dpaterson ?
19:47:43 <catherineD> I think so
19:47:58 <hogepodge> Please leave comments on it regardless to give feedback on the direction, keeping in mind it's WIP
19:48:56 <hogepodge> moving on
19:49:04 <hogepodge> #topic Open Discussion
19:49:23 <hogepodge> I probably should have added this to the agenda, but PTG plans?
19:49:55 <hogepodge> I apologize if you answered this last week, but pvaneck catherineD are you planning on attending?
19:50:11 <catherineD> RefStack use the same etherpad with Interop-wg for PTG
19:50:28 <hogepodge> catherineD: good to know
19:50:31 <hogepodge> link?
19:50:32 <catherineD> hogepodge: most likely not from me
19:50:49 <pvaneck> hogepodge: Currently no plan for me as well
19:51:44 <hogepodge> :-(
19:52:28 <mguiney> :( indeed
19:53:02 <catherineD> here is the etherpad https://etherpad.openstack.org/p/InteropDenver2017PTG
19:53:35 <hogepodge> #link PTG Etherpad https://etherpad.openstack.org/p/InteropDenver2017PTG
19:54:11 <hogepodge> I'd like to set up remote connections for some sessions.
19:54:19 <hogepodge> Details will be forthcoming.
19:55:08 <catherineD> hogepodge: ++
19:55:09 <hogepodge> catherineD: pvaneck: luzC: would you be able to attend scheduled remote sessions
19:55:24 <hogepodge> With five minutes left, any other open topics?
19:55:26 <catherineD> hogepodge: yea
19:55:40 <pvaneck> hogepodge: most likely can
19:55:46 <hogepodge> catherineD: excellent
19:55:51 <hogepodge> pvaneck: +1
19:56:30 <catherineD> hogepodge: I willsend you email and schedule for a RefStack wegsite update Friday?
19:56:42 <hogepodge> catherineD: yes please
19:56:59 <catherineD> ok
19:57:51 <hogepodge> Hearing nothing else, I'm going to end the meeting.
19:57:55 <hogepodge> Thanks everybody!
19:58:09 <hogepodge> #endmeeting