14:00:03 #startmeeting sahara 14:00:07 Meeting started Thu Jan 3 14:00:03 2019 UTC and is due to finish in 60 minutes. The chair is tellesnobrega. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:10 The meeting name has been set to 'sahara' 14:00:18 o/ 14:00:36 o/ 14:00:37 o/ 14:00:59 hi folks 14:01:16 hope you all had a great time on the holidays 14:01:59 lets start with usual 14:02:04 #topic News/Updates 14:02:41 I've been working on the split plugins 14:02:51 which should be mergeable now 14:03:00 a) feature sets and its usage to implement S3; b) review of the split repositories; c) fix some python3 issues (almost there); d) rechecked APIv2, called for help 14:03:01 also, working on some apiv2 stuf 14:03:03 stuff 14:03:41 (and help came) 14:04:08 jumped in on the tempest problem related to unversioned endpoint, reviewed some other patches, will continue on with more apiv2 work next 14:05:24 any more news/updates? 14:06:10 lets move on then 14:06:22 #topic Split Plugins 14:07:13 so, right now we have the plugins split, tosky have reviewed it a lot this last weeks (thanks a lot tosky) and we should be moving today with the patches to create the repos 14:07:21 right tosky? 14:08:58 yes, correct; I prepared two draft patches to start the import process and setup the new repositories 14:09:01 according, uhm, moment 14:10:21 I will find the document, anyway, we need a patch against project-config (or two, if we need to define the repositories first and their properties base jobs later instead of having a unified patch) 14:10:26 and another one for governance 14:10:41 this way we can import sahara-plugin-* without breaking sahara 14:11:09 and start adding the basic jobs (pep8) 14:11:13 then we can apply the patch which cleans sahara.git, and everything should work as before 14:11:15 hopefully 14:11:26 hopefully being the key word 14:11:28 :) 14:12:20 tosky, do you need help with any of those patches? or do you have them ready? 14:12:44 I can submit them and at most W-1 until we go through few iteractions 14:12:58 I can also try to ask on -infra now that there are more people around 14:13:29 nice 14:13:41 if you need help feel free to ping me 14:13:54 if I'm not on irc, just email :) 14:14:20 jeremyfreudberg, any questions on the split? 14:15:09 not at the moment 14:15:29 cool 14:15:51 moving on 14:16:06 actually, tosky anything else on the topic? 14:16:20 no, I think I don't have anything else to add right now 14:16:28 sure 14:16:31 or better: 14:16:48 the work will start after the import; we can help RDO people with packaging the new plugins 14:17:26 then another batch of work will be needed after the patch on sahara.git to fix at least puppet-sahara and ansible-sahara 14:17:40 but at least the import should be easy 14:18:25 and that's it 14:18:32 awesome, thanks tosky 14:19:17 moving on now 14:19:24 #topic APIv2 14:19:55 so, APIv2 is moving on well lately 14:20:01 the payload patch merged 14:20:12 api ref has a +2 14:20:25 we still have the unversioned endpoints patch 14:20:39 and we are missing microversioning from jeremyfreudberg 14:20:45 anything else I missed? 14:20:59 I had a question on the unversioned endpoint patch, or better, on the sahara-tempest patch 14:21:08 I mean, it's working but I was a bit puzzled 14:21:36 you have the floor 14:22:33 uhm, I wrote it last night and I'm starting to doubt that what I wrote makes sense 14:23:40 you mean the v1.1 calls using the v2 url format? 14:25:10 yep 14:26:00 my last comment here: https://review.openstack.org/#/c/622330/ 14:26:09 it is expected, even if strange 14:27:29 would you have some time to try to call that v1.1 endpoint API with unversioned endpoint from a curl or anyway without tempest or saharaclient to see if the old format still really work as documented? 14:28:32 I can run that on monday if jeremyfreudberg doesn't have time 14:29:06 ok, I guess I won't have a finished tempest v2 client anyway before Monday 14:29:32 and for sure I won't have the answer on how to organize the v2 tests before that (the QA PTL has still holidays) 14:29:43 sure, current master to test that is ok? or do I need to apply any patches? 14:29:48 tosky: not sure if i totally understand your message, you mean to see if both with and without project id in url work 14:30:50 jeremyfreudberg: that's the idea, if I'm not missing anything; the APIv1.1 with unversioned endpoints seems to be working, but there is some magic in the middle 14:31:03 I'd like to ensure that a 3rd-party client is not broken 14:32:19 tosky: ok, i will check it 14:32:22 thanks! 14:33:57 anything else on apiv2 that I missed? 14:34:29 one thing 14:34:47 not necessarily needed to be answered instantly: some further clarity on https://storyboard.openstack.org/#!/story/2004675 14:34:58 oh, that 14:35:36 I can take the action to fix those files 14:35:39 job_templates enforces a mix of data-processing:job-templates:... and data-processing:jobs:... rules 14:35:53 the problem is how to fix them without breaking anything 14:36:52 hmm, I will take a look 14:37:18 in hindsight (when it's easier to speak) it should have been better not to reuse jobs/ but to use a different endpoint, maybe 14:37:49 also, i retract my comment (From the story) that job_templates.py looks fine 14:37:53 because it's also inconsistent 14:38:14 sure 14:38:29 if I need help I will ping you 14:38:49 i think we'll definitely need to invent a new name 14:39:11 if so, we need to do it now 14:39:34 to be clear, just a new name in the policies, the actual api is fine 14:39:53 ok 14:39:57 got it 14:41:13 I will take a look and get back with questions 14:41:25 the simplest solution is a sudden jump to have apiv1 using v2-styled policy names 14:41:31 but i guess "sudden jump" is not okay 14:43:03 maybe not, I have not looked into the issue properly, but I guess we can create under sahara/common/policies 14:43:18 a v2 folder and add job there and use 14:43:29 I will see how to best make that 14:43:47 something similar to what we did on the client 14:44:03 where we added v2 for the jobs and job-templates 14:44:52 yes, but we only get one policy file (i assume) to control both v1, and v2, so the names still can't conflict 14:45:00 i think the answer will come with a bit more exploring 14:45:34 yes 14:45:45 I will dig that 14:45:59 jeremyfreudberg, how is the microversining stuff coming along? 14:47:59 i'll be resuming it soon 14:50:01 great, do you think you would be able to finish by M2? 14:52:00 i'll say it like this, i really hope there is a meaningful patch ready by then 14:52:10 ok 14:52:11 and there's a good chance there will be 14:52:11 thanks 14:52:48 I strongly encourage you to make that happen :) 14:53:05 if it doesn't its ok, but I would like to see all apiv2 done 14:53:14 me too 14:53:54 thanks 14:54:19 we have 6 minutes left 14:54:28 anything else to discuss? 14:54:46 yeah, i still don't know where "long" comes from in the query string checking patch 14:55:03 (by the way, the patch looks really really good otherwise) 14:55:10 thanks 14:55:33 I see that parameter when I run openstack dataprocessing some command 14:55:57 long is there and from my debug it shows up as one of the parameters if you pass it on 14:56:18 which command? do you mean with --long ? or something else 14:56:22 I left it there so it would be allowed, I can double check if it is really necessary 14:56:23 yes 14:56:28 --long 14:56:41 iirc, it showed up on the parameters list 14:56:57 if passed 14:57:03 interesting, i didn't think that --long went to the request params but it might in some case 14:57:12 if you don't mind double checking 14:57:18 i can look a little bit too 14:58:03 I will do 14:58:58 anything else? 14:59:08 that's it from me 14:59:14 veeery quickly, as there is another meeting here after us: python 3 14:59:29 this patch https://review.openstack.org/#/c/626643/ brings us a bit forward, now sahara-eng start but it gets stuck when connecting to the nodes using ssh, something related to pickle 14:59:44 I've seen this issue locally 15:00:13 do you have ideas on how to fix it? 15:00:20 we have to close now 15:00:26 lets continue on #openstack-sahara 15:00:28 thanks all 15:00:29 yep 15:00:33 #endmeeting