14:00:34 #startmeeting sahara 14:00:35 Meeting started Thu Mar 9 14:00:34 2017 UTC and is due to finish in 60 minutes. The chair is tellesnobrega. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:36 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:38 The meeting name has been set to 'sahara' 14:00:40 o/ 14:00:50 o/ 14:00:57 o/ 14:01:42 lets wait a couple minutes for more people to join 14:02:12 o/ 14:02:18 hi 14:03:13 #topic News/Updates 14:03:45 Basically I've been concentrated on the internal stuff and also I spent some time to request experimental multinode job for sahara test needs; + draft change to enable sahara with Apache + mod_wsgi. I hope that soon I'll be able to prepare a separate job to test that 14:04:04 I'm working on images generations and coordinating the api v2 effort. Special thanks to shuyingya for taking a lot of that work 14:04:14 #link https://review.openstack.org/#/c/442382/ 14:04:27 #link https://review.openstack.org/#/c/443568/ 14:04:33 i am working on adding new cli tests to tempest plugin 14:04:39 also, I'm trying to read all info I have to read on being ptl (it is a lot) but I'm catching up to it 14:04:54 hi. i am working on spec for sahara-scenario api 14:05:12 and sahara-ci stability 14:05:22 I have a question for vgridnev, there is this bug https://bugs.launchpad.net/openstack-manuals/+bug/1669264 do you know what is the approach for fixing it? 14:05:22 Launchpad bug 1669264 in openstack-manuals "Update Data Processing service options in Configuration Reference for Ocata" [High,Confirmed] 14:05:38 I am working on APIv2 recently 14:05:53 I was investigating an issue which is visible when you need to pass parameters for data-processing in tempest.conf, there are some bugs in the way plugins are implemented 14:06:03 QA team was really helpful 14:06:37 also, still planning a release of sahara-tests 0.4.1 "really soon" 14:06:58 tosky, is that related to the patch the andrea upload just now? 14:07:09 tellesnobrega, to be honest, no 14:07:23 vgridnev, no problem, I'll ask around 14:07:34 tellesnobrega: yes, even if that patch is not really required to fix the issue; it is a cleanup to not hide possible future issues, there are two other fixes in tempest which are relevant 14:07:42 o/ 14:08:01 we need to check what options added or removed in ocata, I don't think that there is so much of such stuff 14:08:03 tosky, great 14:08:18 vgridnev, I don't think so too 14:09:16 any more news? 14:09:52 not so much sahara news but I had a talk accepted to the summit 14:10:07 jeremyfreudberg, nice 14:10:10 kk_ is working on refactoring CDH plugin 14:10:19 can you post a link, jeremyfreudberg ? 14:10:22 jeremyfreudberg, will you be able to attend it? 14:11:00 vgridnev, they don't have a finalized schedule yet. so no link yet 14:11:01 kk_, hi, I believe we haven't met? it appears you work with shuyingya let me know if you need anything from me 14:12:04 #topic Specs / features status 14:12:30 I'm linjiasen , kk is my nickname. hi tellesnobrega. 14:12:51 Image gen status we are moving forward, not as fast as I expected but we are moving, hopefully we will have something up for review soon 14:13:26 jeremyfreudberg, https://www.openstack.org/summit/boston-2017/vote-for-speakers/#/18278 ? 14:13:35 I recently think about how to refactor CDH plugin 14:13:52 APIv2 finally got some momentum and we already have some patches merged and some on the way to be merged, this is exciting and faster than I expected 14:13:58 vgridnev, yes that is my accepted talk 14:14:04 thanks to all involved 14:15:09 jeremyfreudberg: how did you know that your talk is accepted? 14:15:37 zemuvier, go to https://www.openstack.org/summit/boston-2017/call-for-presentations/ and one of my talks says "Accepted" instead of "Received" 14:15:40 congratulations jeremyfreudberg~ 14:16:21 i have only 'received' one :( 14:16:35 zemuvier I think they are still deciding 14:17:20 as far as I know the final decision will be on the end of march 14:17:33 so we are still waiting for acceptance 14:17:33 anyone else on spec and features status? 14:17:49 we are also expecting results on a talk 14:18:02 tellesnobrega, vgridnev what should I do to change the field in database as you commented in my patch 14:18:04 nothing from me 14:18:22 https://review.openstack.org/#/c/443155/ 14:18:39 I don't think anyone started plugin updates, that is our highest prio, we should get that started asap 14:18:55 I show concern last time to contribute on code review and testing but still waiting 14:18:58 what field in the database? 14:19:12 tellesnobrega, are we planning to just do copy-paste for CDH 5.10 or do we want to try refactor 14:19:13 I think we should rename the field job_id -> job_templates_id, but that may lead to saharaclient error 14:19:25 jeremyfreudberg, it would be best to refactor cdh first 14:19:43 shuyingya: does saharaclient access the database directly, or do you talk about a parameter in the API? 14:19:49 jon_id -> job_templates_id in job_executions 14:19:56 shuyingya, would this break compatibility? 14:19:56 yes 14:20:06 I think so 14:20:29 tellesnobrega, vgridnev . could you please give some advice about refactoring CDH ? ^^ 14:20:39 Just do it 14:21:04 kk_, you have to think on what is common code and should be in the same place 14:21:06 https://github.com/openstack/python-saharaclient/blob/master/saharaclient/osc/v1/jobs.py#L234-L249 14:21:09 Ok, not so much, actually, we need to remove deprecated versions first 14:21:10 this will avoid copy and paste 14:21:56 armstrong, what concern? 14:22:02 shuyingya: but we should not break compatibility 14:22:03 i guess this will be first step, then you can think of ways to avoid future situations like this 14:22:40 shuyingya, breaking compatibility is not good at all. If this is the case you should leave as it is and we update when we move to apiv2 for good 14:22:55 vgridnev to start contributing, I am new to this working group and showed interest not concern sorry 14:23:14 yep, I think so. So I want to confirm with you. ^^ 14:23:19 tellesnobrega 14:23:40 ok , I see . Thank you! tellesnobrega , vgridnev. 14:24:29 kk_, no problem 14:25:26 kk_ \o/ 14:26:40 ^^, hi , yingya. 14:27:08 armstrong, I can't understand you. You don't have plans to contribute, right? If so, what's wrong and what we should fix? Just wondering 14:27:36 vgridnev I want to contribute 14:27:55 and need a good starting place (point) 14:28:07 how do I go about it? 14:28:27 armstrong, have you used sahara before? 14:28:38 armstrong, you could take a look updating plugin version, it is a good way to get to know the code 14:28:46 spark and storm are easy ones to do so 14:29:03 Yes I used it but not intensively 14:29:30 tellesnobrega OK I will take a look at that 14:29:36 thanks 14:29:57 no problem 14:30:06 let me know how it goes and I will help you 14:30:16 armstrong, please keep us updated on this, if you have questions / problem, just ping me, or tellesnobrega 14:30:22 armstrong, easy task can also be adding some more unit tests, check out the sahara-coverage job on a recent patch 14:30:33 good way to get familiar with code base 14:31:03 jeremyfreudberg, true 14:31:43 and tellesnobrega, what do you mean in the mail list about the cross project liaisons? If you need more hands, let me know. 14:31:57 #topic Open Discussion 14:32:06 shuyingya, I was going to bring this up now 14:32:37 We need people to act as bridge between projects, I'm working with elise on documentation and I'm also release management liaison but I can't do it all 14:32:51 #link https://wiki.openstack.org/wiki/CrossProjectLiaisons 14:33:09 please take a look on this list, and find something that you think you could help and let me know 14:33:23 jeremyfreudberg I will do just that 14:33:26 thanks 14:33:58 tellesnobrega, you've been added to vulnerability management group for sahara project 14:34:22 https://launchpad.net/~sahara-coresec 14:34:43 I saw that, thanks 14:35:12 so, you will be able to see all security issues for sahara; but we don't have them now 14:35:30 vgridnev, great for both :) 14:37:08 so, we have some slots without assignee 14:37:24 Oslo, for example 14:38:02 Vulnerability Mg 14:38:15 I think I can be oslo project liaisons 14:39:24 tellesnobrega 14:39:44 shuyingya, awesome, I want to help with that, I will set us both 14:39:48 agreed? 14:39:59 of course. 14:40:07 my pleasure 14:40:30 QA: tosky for sure : ) 14:40:44 thanks :) 14:41:31 tosky, you are free to say no, but please don't :) 14:41:37 :D 14:41:50 I will continue to nag the QA team :D 14:41:55 thanks :) 14:42:19 about Vulnerabilities, I think that tellesnobrega should coordinate that job (no so large to work right there) 14:42:40 vgridnev, I was thinking the same thing 14:42:51 I will assign myself 14:43:50 Logging working group, that is a group to improve logging in the project, shuyingya do you work with that? 14:44:08 Quite similar to oslo stuff 14:44:40 that would be nice 14:44:43 ^^ 14:44:52 great guys 14:46:16 Product Working Gr & I18n & Cross project spec volunteers? 14:48:16 i could do i18n 14:50:43 sorry guys internet dropped 14:50:49 are you still here? 14:51:05 yes 14:51:08 yes 14:51:19 I believe we closed the liaisons topic 14:51:26 do we have anything else for today? 14:52:03 we almost closed that, yep 14:52:17 Product Working Gr & Cross project spec are still without liaison 14:52:52 cross project spec I can do that, product working group anyone wants to handle it? 14:53:27 that would be more for product managers and co iirc, is it still relevant? 14:53:48 not sure, we can leave it empty for now and they will ping me if they need anything 14:54:07 oh, yes, they have even goals for Ocata 14:54:52 have to leave, nothing else from me 14:56:09 ok 14:56:17 thank you guys 14:56:26 I will update the liaisons and next week we talk more 14:56:32 #endmeeting