17:03:10 <hogepodge> #startmeeting refstack
17:03:11 <openstack> Meeting started Tue Mar 20 17:03:10 2018 UTC and is due to finish in 60 minutes.  The chair is hogepodge. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:03:12 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:03:15 <openstack> The meeting name has been set to 'refstack'
17:03:31 <hogepodge> #link https://etherpad.openstack.org/p/refstack-meeting-18-03-20 agenda
17:03:46 <hogepodge> #chair tosky chandankumar
17:03:46 <openstack> Current chairs: chandankumar hogepodge tosky
17:03:58 <hogepodge> #topic python-tempestclient
17:04:07 <hogepodge> take it away tosky and chandankumar
17:05:11 <chandankumar> hogepodge: sure
17:05:24 <chandankumar> Based on the feedback received from the ptg on tempestconf
17:05:42 <chandankumar> I have created stories
17:05:44 <chandankumar> Generate accounts.yaml when --os-cloud is used with python-tempestconf (https://storyboard.openstack.org/#!/story/2001693)]
17:05:46 <chandankumar> Fix tempestconf job having demo user (https://storyboard.openstack.org/#!/story/2001695)]
17:05:48 <chandankumar> Refactor tempestconf in order to integrate with refstack_client tool (https://storyboard.openstack.org/#!/story/2001696)]
17:06:21 <chandankumar> For first one work is in progress here: https://review.openstack.org/#/c/554480/
17:06:41 <chandankumar> Currently I am working on updating my previous integration patches
17:07:21 <tosky> maybe we need some more fine-grained tasks in the stories
17:07:24 <tosky> but let's see
17:07:41 <chandankumar> Apart from that, https://review.openstack.org/537355 [Decouple TempestConf class] is good to go from myself, unless tosky and arxcruz have something to say
17:08:02 <arxcruz> no issues for me
17:08:18 <chandankumar> https://review.openstack.org/540177 and https://review.openstack.org/533434 tripleo jobs are failing recheck done, once passed, we will do a final go through
17:08:46 <chandankumar> on https://review.openstack.org/519714 ec2api support no updates till now
17:09:03 <chandankumar> that's it from my side on tempestconf
17:09:15 <hogepodge> great, thanks
17:09:32 <hogepodge> I'm looking forward to the work being merged into the refstack client
17:10:34 <hogepodge> #topic refstack
17:11:16 <hogepodge> On Subunit upload, we're waiting on merges to subunit2sql before those API changes can move forward
17:11:51 <hogepodge> mguiney: any comments on the API updates?
17:12:25 <mguiney> yep, i have a few more things to fix on the subunit2sql delete uuid patch before it will be ready for merge
17:13:09 <mguiney> i'm also hoping to get the last of the api tests pushed fairly shortly
17:13:14 <hogepodge> ok
17:13:40 <hogepodge> there's the db naming patch
17:13:49 <hogepodge> #link https://review.openstack.org/#/c/549257/ DB Naming
17:13:50 <mguiney> apologies, ended up losing a day and a half to technical issues, so I had a short week last week
17:14:18 <hogepodge> looks like it should be a quick merge? I just have to run it locally
17:14:44 <hogepodge> The highest priority for refstack is in getting new capability sources merged
17:14:46 <hogepodge> #link https://review.openstack.org/#/c/547246/ New Capability Sources
17:15:17 <hogepodge> That takes priority over everything else right now, with the approval of the new guidelines at the PTG by the board of directors
17:15:34 <hogepodge> I set it up locally and will be testing it today.
17:15:48 <mguiney> excellent
17:16:36 <hogepodge> In setting up the build, NPM is throwing lots of warnings that I think will eventually cause us problems.
17:17:13 <hogepodge> We should be looking at how to migrate forward to newer versions and help future-proof the deployment. NPM has a nasty history of breaking the world if you're not up to date on it.
17:17:34 <hogepodge> So, I'm thinking, order of priorities is:
17:17:43 <hogepodge> 1 new capability sources
17:17:58 <hogepodge> 2 investigate npm migration
17:18:04 <hogepodge> 3 subunit upload
17:18:25 <hogepodge> (of course, if there's easy work to get done on subunit, like with subunit2sql, we shouldn't hold that work up)
17:18:37 <hogepodge> any comments on that?
17:20:02 <hogepodge> ok, hearing nothing on that
17:20:06 <hogepodge> #topic open discussion
17:20:14 <hogepodge> Any other items folks wanted to bring up?
17:20:44 <tosky> nothing from me
17:21:05 <mguiney_alt> sorry, having issues with my irc
17:21:46 <mguiney_alt> yeah, the subunit2sql work shouldnt take too long, and that sounds like a solid priority stack
17:22:07 <mguiney_alt> i'll get on that as soon as possible
17:22:55 <hogepodge> cool.
17:22:57 <hogepodge> anything else?
17:23:41 <mguiney_alt> nope!
17:24:56 <hogepodge> ok, have a great week everybody!
17:24:59 <hogepodge> #endmeeting