17:01:23 <hogepodge> #startmeeting refstack 17:01:24 <openstack> Meeting started Tue Apr 3 17:01:23 2018 UTC and is due to finish in 60 minutes. The chair is hogepodge. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:25 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:01:28 <openstack> The meeting name has been set to 'refstack' 17:01:39 <hogepodge> #link https://etherpad.openstack.org/p/refstack-meeting-18-04-03 agenda 17:01:53 <tosky> o/ (even if I need to leave a bit earlier) 17:02:53 <hogepodge> We can start with the tempestconf work 17:03:02 <hogepodge> #chair tosky 17:03:03 <openstack> Current chairs: hogepodge tosky 17:03:15 <hogepodge> #topic python-tempestconf 17:04:22 <tosky> so, Chandan is working on the refstack integration, I don't have much updates on this specific review 17:04:39 <tosky> #link https://review.openstack.org/#/c/541273/ Genereate tempest.conf in refstack client (WIP) 17:05:18 <tosky> but I see comments there, so I guess it's taken care of 17:06:04 <tosky> about the tempestconf specific work, few refactoring patches went in 17:06:23 <tosky> now we need Chandan and Martin to rebase two of their patches: 17:06:54 <mguiney> o/ (connection spotty, but i should clear up shortly) 17:07:04 <hogepodge> cool 17:07:15 <tosky> uhm, the previous was info, not link 17:07:18 <tosky> #undo 17:07:19 <openstack> Removing item from minutes: #link https://review.openstack.org/#/c/541273/ 17:07:24 <tosky> #info https://review.openstack.org/#/c/541273/ Genereate tempest.conf in refstack client (WIP) 17:07:40 <tosky> ok, about the refactoring reviews, I'm talking about 17:08:18 <tosky> #info https://review.openstack.org/#/c/540177/ Refactor to improve modularity, scalability, OOP 17:08:19 <tosky> #info https://review.openstack.org/#/c/546115/ Make main function more modular 17:08:58 <tosky> another relevant change (required in order to proper test the non-admin execution of tempestconf) is 17:09:02 <tosky> #info https://review.openstack.org/#/c/554480/ Use --non-admin for non admin users in zuul jobs 17:09:20 <tosky> we had a bit of exchange of messages in the review, I'm still not sure about how it could have worked so far, but let's see 17:10:27 <tosky> and finally we have two reviews which are stale now, we probably need to reping the authors 17:10:28 <tosky> namely 17:10:59 <tosky> #info https://review.openstack.org/#/c/519714/ WIP: Add EC2-API support 17:11:01 <tosky> #info https://review.openstack.org/#/c/528380/ Make tempest setup image verification aware 17:11:11 <tosky> they will need a refactor anyway when https://review.openstack.org/#/c/540177/ lands 17:11:56 <tosky> Chandan created 3 stories following the discussions during the PTG, they are linked in the etherpad but just for reference: 17:12:59 <tosky> #info Generate accounts.yaml when --os-cloud is used with python-tempestconf - https://storyboard.openstack.org/#!/story/2001693 17:13:04 <tosky> #info Fix tempestconf job having demo user - https://storyboard.openstack.org/#!/story/2001695 17:13:13 <tosky> #info Refactor tempestconf in order to integrate with refstack_client tool - https://storyboard.openstack.org/#!/story/2001696 17:13:30 <tosky> and at least 554480 is directly linked to one of them 17:13:49 <tosky> feel free to comment on them 17:14:06 <tosky> I think that's it from my side 17:14:47 <hogepodge> ok, great work 17:14:47 <tosky> so... next :) 17:14:52 <hogepodge> Looks like things are moving along. 17:15:03 <hogepodge> #topic RefStack 17:15:03 <tosky> yep 17:15:24 <hogepodge> So, high level there are a few threads moving forward in RefStack 17:15:54 <hogepodge> We need to update the server to handle the new add on programs. 17:16:08 <hogepodge> Our Javascript libraries need to be updated 17:16:22 <hogepodge> We need to build out functionality for uploading subunit data. 17:16:42 <hogepodge> #link https://review.openstack.org/#/c/547246/ New Capability Sources 17:17:37 <mguiney> alright! 17:17:39 <hogepodge> For the new capability sources, there's a bit work that needs to be done on the javascript side. A lot of assumptions about the OpenStack Powered program were hard coded into that framework, and sadly given our time constraints we may need to keep some of that hard coding in place. 17:18:33 <mguiney> i have a new solution that i'm currently working on, and the api functionality is solid and ready, but i'm still debuggin ui stuff and refactoring the unit tests 17:19:00 <hogepodge> Good, a maintainable solution would be nice. :-) 17:19:44 <hogepodge> I'm not fully sure of the scope for updating javascript. Hopefully it will be easy, but these sorts of easy things have a tendency to become tricky. ¯\_(ツ)_/¯ 17:20:06 <mguiney> basically, the idea behind the new implementation is that rather than a flat array of guidelines, we should have the api retun a json dict of types and their correspondign array of applicable guidelines 17:20:42 <mguiney> that way, it will be impossible to select a guideline for one of the addons that exists for powered but not for one of the add-ons 17:20:48 <hogepodge> that's probably a good design. We have multiple things that combine, program and date, and sometimes they overlap, so rendering that properly just takes some logic 17:21:24 <mguiney> the other nice thing about that is that we should hopefully be able to use that to add new guideline types to the interface dynamically, because we (hopefully) won't have to hard code the new things anymore 17:22:10 <hogepodge> The main blockers on the subunit upload is in finalizing some patches we need for an updated subunit2sql, and figuring out how to handle multiple CONF sources in oslo, especially in testing. 17:22:22 <mguiney> given, i'm still trying to get base case up and running, but this is the first time i've ever really done JavaScript debugging at any level, so most of my struggle is figuring out how to debug properly 17:23:18 <mguiney> yes! re: oslo, i actually did get a pointer on that in #openstack-oslo, so it looks like i have a good place to start in getting that sorted 17:24:07 <hogepodge> Oh good! I just checked in with them too and asked about our failing patch. 17:24:13 <mguiney> i may have more questions to ask of them as i go, but hopefully i can get that sorted shortly 17:24:24 <hogepodge> Cool. 17:24:34 <hogepodge> That's pretty much it, unless you have more to add mguiney 17:25:40 <mguiney> not yet, no! working on getting those debugged, as well as finishing off unit tests for one of the subunit2sql patches upon which the api is reliant (the one that allows for the usage of kwargs) 17:26:06 <mguiney> the delete uuid patch could use new reviews, so i'll copypaste the link in here 17:26:40 <mguiney> #link https://review.openstack.org/#/c/537775/ 17:26:44 <hogepodge> ok, cool 17:27:19 <mguiney> it has some small updates suggested by mtreinish (thank you mtreinish for the super helpful feedback) 17:27:34 <mguiney> but hopefully should look good now 17:28:19 <hogepodge> Anything else? 17:29:07 <hogepodge> Ok, have a great week everybody! 17:29:10 <hogepodge> #endmeeting