17:01:18 #startmeeting RefStack 17:01:18 Meeting started Tue Nov 21 17:01:18 2017 UTC and is due to finish in 60 minutes. The chair is hogepodge. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:01:21 The meeting name has been set to 'refstack' 17:01:41 o/ 17:01:44 #link https://etherpad.openstack.org/p/refstack-meeting-17-11-21 Agenda 17:02:18 Agenda is mostly reviews, but please add topics that you would like to cover today. 17:02:34 o/ 17:04:14 #topic Current Work: RefStack 17:04:34 #link https://review.openstack.org/#/c/507695/ Disable Anonymous Upload 17:05:11 This is part of the work we're doing to mark tag all results that are being used for product validation 17:05:28 Reminder that once this lands and is deployed, no more anonymous results will be allowed in the database. 17:05:43 mguiney: anything to say about this patch? 17:06:17 Saw you posted new comments, they looked super helpful, but havent finished updating 17:06:55 (sorry, was tied up in other task most of last night) 17:07:09 At the same time we deploy this patch, we'll also have to communicate the changes to the community and update documentation. 17:07:45 I'm going to create an etherpad to begin writing the communication and documentation changes 17:07:53 * mguiney nods 17:08:05 #link https://etherpad.openstack.org/p/refstack-disable-anonymous-upload 17:08:27 probably should land at the same time - are the sources of the documentation in the repository/ 17:08:28 ? 17:08:44 tosky: The repository, but also on the openstack.org/interop page 17:09:15 so maybe the documentation in the repository could be patches too in the same patch, especially if the patch needs to be amended anyway 17:09:16 And the user and dev mailing lists. 17:09:38 Yes, that's a good idea 17:09:48 I can lump the doc changes in with the actual patch, if that helps 17:09:53 ah lol 17:09:55 ^ 17:09:58 already suggested 17:10:42 It's important to remember that this is a configuration option, and it's not mandatory within the project itself. It will become mandatory once we push the change to infra for deployment. 17:11:50 and that will be the change to infra documentation 17:12:19 No, to the documentation that describes how to run refstack for the interop program 17:12:35 oh, I see 17:13:15 Anything else on this topic? 17:14:02 #link https://review.openstack.org/#/c/506826/ Subunit API Spec 17:14:22 I think this is ready to merge, just waiting on one more +2 17:14:42 Still, take a look. We'd like to get this implemented in December if possible. 17:14:57 Any comments mguiney? 17:15:19 luzC: does it look good to you with the updates around delete behavior? 17:16:07 nothing particularly new, got it updated, it (of course) looks good to me 17:16:26 but it would, given that i've spent a fair bit of time staring at it 17:17:12 One more RefStack review, a WIP 17:17:16 #link https://review.openstack.org/#/c/521343/ RefStack API Documentation 17:18:12 Looking at breaking out the API documentation from the specs into proper API docs. It's assigned to mguiney, but if there's anyone looking for a bit of extra work you should feel free to take a run at it. 17:20:00 #topic Current Work: Infra Jobs 17:20:15 #link https://review.openstack.org/#/c/512943/ Remove Legacy Jobs in RefStack 17:20:58 #link https://review.openstack.org/#/c/512936/ Convert Legacy Jobs in Tree (merged) 17:21:11 yeah, if anyone is interested in helping out on that, it is still very wip 17:21:20 Are there any other infra reviews that I'm missing on this? 17:21:41 i'll try and crank some out each time i am out of internet range, but itll still take a bit 17:21:50 (not to pop the stack, sorry) 17:21:56 no problem :-) 17:23:07 Any more items on either of those topics? 17:24:11 #topic Current Work: RefStack Client 17:24:27 #link https://review.openstack.org/#/c/489421/ Tempest Config Generation 17:24:45 Spec for automated tempest config generation. Lots of good work that brought up lots of new questions 17:25:21 I think most of the information is there, but can use some clarification on some points. 17:26:10 yep; Chandan is away for few days, can it wait a bit? 17:26:39 yes, just wanted to bring it to everyone's attention 17:27:02 Later this week is a US holiday too 17:27:24 If anyone hasn't reviewed it yet, please take this opportunity to do so. 17:27:50 Somewhat related to that work is a patch that just updates some documentation with a minimal tempest.conf 17:27:52 #link https://review.openstack.org/#/c/515494/ Sample Tempest Configuration 17:28:56 I had just a small note about the syntax of the ini file, but it was addressed 17:29:32 Finally, more docs work 17:29:35 #link https://review.openstack.org/#/c/521208/ Fixed documentation tree 17:29:58 LuzC has cleaned up the documentation tree 17:30:19 It looks good to merge to me, just waiting for another +2 on it. 17:30:50 i can take a look real quick 17:30:59 thanks mguiney 17:31:08 are the changes to that existing spec relevant for the patch? 17:31:59 done! :) 17:32:22 luzC: wrote the patch to generically capture the specs 17:32:50 and there don't appear to be any merge conflicts 17:35:09 #topic Current Work: Python TempestConf 17:36:00 A few weeks ago the python-tempestconf project was added to RefStack governance, so we should start paying attention to the development trajectory in these meetings :-) 17:36:35 Everyone working on RefStack, please add this project to your review notification queues and give feed back and send patches. 17:36:36 right now the focus is adding back the jobs, which is proving a bit complex due some missing blocks in the set of default zuul jobs and roles 17:36:51 and that's why https://review.openstack.org/#/c/513330/ is still failing 17:37:07 but Martin is definitely investigating it actively 17:37:24 #link https://review.openstack.org/#/c/513330/ Add initial .zuul file, devstack and packstack job 17:38:26 tosky: do you need more eyes on it? Can we help out with debugging it in any way? 17:39:08 hogepodge: I would ask Martin when he is around (not today :); I think he already poked (or plan to) people on -infra about the issues with the devstack job 17:39:27 and that's why he started to investigate the usage of the packstack job in parallel, in addition to devstack 17:39:57 packstack is nice for standing up stable openstack, one of my favorite RDO projects 17:41:09 (although I find the choice to automatically install ceilometer but not heat a bit strange, but that's a topic for a different meeting) ;-) 17:41:40 it can be tuned :) 17:41:47 There's also a patch to add ec2-api discovery. https://review.openstack.org/#/c/519714/ Add EC2-API support 17:42:36 tosky: is there anything else we should be aware of on the project? What's in the plan for future work on it? 17:42:56 about the EC2 patch, apparently the author added -W because he needs to test it properly before 17:43:26 about future directions, yes, mainly an internal refactor of the codebase which makes it difficult to extend it with service-specific settings, for example 17:43:41 I think we will propose a meeting when Chandan is back 17:43:53 that sounds good 17:44:46 Anything else? 17:45:20 #topic Current Work: Governance 17:45:34 #link https://review.openstack.org/#/c/521602/ Clarify testing for interop programs 17:45:46 #link https://review.openstack.org/#/c/521587/ Add designate to the tc:approved-release tag 17:47:33 I was hoping grahamhayes was around to talk about this 17:48:40 The first is a governance patch that addresses the need to consider tempest plugins as official sources for refstack testing. 17:48:48 To support the add on programs 17:49:14 definitely needed 17:49:28 RefStack support Tempest Plug Ins, and we need to be aware of how this will change testing and how we can communicate and document the usage of it 17:50:14 Please take a look at those patches, especially the first, and get a sense of what they say and how we would be impacted. 17:51:34 #topic Open Discussion 17:51:40 Anything else before we close out the meeting? 17:53:15 Notification to everyone, I'll be taking of the majority of December, once I'm back from KubeCon on Dec 9. 17:53:31 We'll work out who will lead the meetings during that time. 17:54:07 Have a great week everybody. Thanks for attending! 17:54:14 o/ 17:54:21 have a good day, all! 17:55:23 #endmeeting