18:00:29 #startmeeting sahara 18:00:29 Meeting started Thu Mar 3 18:00:29 2016 UTC and is due to finish in 60 minutes. The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:33 The meeting name has been set to 'sahara' 18:00:38 hey 18:00:43 #link https://wiki.openstack.org/wiki/Meetings/SaharaAgenda 18:00:48 hello 18:00:49 hello 18:00:51 #topic News / updates 18:00:51 hello 18:00:55 hi folks 18:01:03 o; 18:01:06 o/ 18:01:14 yo 18:01:58 i'm continuing to do api v2 work, i think we will have a few more hands to help out with it \o/ 18:02:07 also bandit should be cleared up this week 18:02:20 and i've got a security bug that needs review, and a few more coming... 18:02:25 working on resume EDP patch 18:02:40 i am working on ci improvements and updating scenario framework 18:02:43 I'm busy with bug fixing and testing sahara, little improvements for the health checks 18:04:00 Hi 18:04:04 hey Poornima 18:04:09 I think I will do 2 small improvements to health checks, should I request FFE for that? 18:04:21 hi 18:04:24 elmiko, ;) 18:04:29 i wanted to introduce, Poornima and pgadiya are fellow red hatters who are interested in working on sahara =) 18:04:37 hey tosky 0/ 18:04:45 welcome! 18:04:46 welcome 18:04:48 Hello everyone 18:04:53 welcome 18:04:58 hi 18:04:59 hi Poornima 18:04:59 welcome aboard :) 18:05:01 Hello Everyone 18:05:08 热烈欢迎 18:05:10 hello pgadiya 18:05:14 #info Sahara Mitaka-3 proposed 18:05:24 https://review.openstack.org/#/c/287965/ 18:05:58 SergeyLukjanov, we should not merge features from this point? 18:06:06 vgridnev correct 18:06:12 any more news / updates/ 18:06:13 ? 18:06:30 FFE request? for merge features 18:06:34 SergeyLukjanov: 18:06:49 let's discuss FFEs as a separated topic 18:06:54 Ok 18:07:13 SergeyLukjanov: +1, i know Akanksha08 is curious about this too 18:07:27 elmiko, +1 18:07:37 seems like it's time to switch :) 18:07:40 #topic Mitaka release & FFEs 18:07:41 hehe 18:07:50 hello folks 18:07:57 welcome rickflare 18:07:59 we're going to have the mitaka-3 today, it's already proposed https://review.openstack.org/#/c/287965/ 18:08:11 so, from this point no features should be approved 18:08:17 only through the FFEs 18:08:34 to request FFE please write to the ml 18:08:51 can we have FFE for this https://review.openstack.org/#/c/269202/ 18:09:07 for improving anti-affinity feature 18:09:08 we can discuss all FFE cases right now 18:09:21 SergeyLukjanov: do we have a launchpad txt for FFE 18:09:28 FFE wouldn't be granted if spec isn't yet approved 18:09:54 I want FFE for 2 small enhancement for health checks - one to sahara and the second for sahara-dashboard, should I request FFE in ML? 18:10:00 For tracking all FFE request like before 18:10:04 SergeyLukjanov, i think we can discuss now, but it would be best to send something to the ML just for record keeping 18:10:15 #link https://etherpad.openstack.org/p/sahara-mitaka-ff 18:10:24 tellesnobrega: +1, we should have all FFEs on ML 18:10:27 tellesnobrega yes 18:10:41 to have the FFE granted it should be sent to ML 18:10:49 just so everyone is clear on that 18:10:56 I'm only talking about discussing 'em now 18:11:00 yea 18:11:12 SergeyLukjanov, +1 18:12:54 few comments re FFEs 18:13:29 * if spec isn't approved - no way (we need to fix bugs but not review specs and then code, I'm considering code non-reviewable while spec isn't approved) 18:13:44 * avg. FFE should be around 1 week 18:15:23 any FFEs so far to raise? 18:16:02 SergeyLukjanov, what do think about this: I want FFE for 2 small enhancement for health checks - one to sahara and the second for sahara-dashboard, should I request FFE in ML? 18:16:03 core reviewers, please, don't approve features w/o FFE :) 18:16:36 SergeyLukjanov: ack 18:16:54 SergeyLukjanov: I have one resume EDP patch for FFE, spec is merged, suspend EDP patch is merged also 18:17:13 SergeyLukjanov: send a request in ML? 18:18:36 huichun, i think all FFE need to go through ML 18:19:33 tellesnobrega: roger 18:21:29 SergeyLukjanov, are you ask? 18:21:42 ask -> afk? 18:22:39 needs more #chair ;) 18:22:55 always use HA mode 18:23:25 elmiko: you are master now 18:23:33 master server 18:24:03 master without permissions is not a master 18:24:10 ) 18:24:14 i guess SergeyLukjanov is out, can anyone else lead the meeting? 18:24:15 vgridnev: ^^ 18:24:24 elmiko++ huichun++ 18:24:32 vgridnev: sadly... yes 18:24:45 vgridnev, +1 ;) 18:25:25 vgridnev: do you know if anyone at mirantis is looking at a kolla playbook for sahara? 18:26:00 sorry, I've been checking current specs, need one minute 18:26:16 we can go ahead, I'll share some thoughts during open discussion 18:26:21 cool 18:26:25 elmiko could you please lead 18:26:33 SergeyLukjanov: sure, make me a chair 18:27:06 elmiko, I am not sure about this 18:27:06 i think we are done with FFE business, are there any other questions about it? 18:27:28 vgridnev: ack, i'll ask again in open discussion 18:27:49 sounds like no more FFE questions 18:27:51 hi, sorry I'm laste 18:27:53 late 18:27:57 welcome =) 18:28:37 Just the right time 18:28:56 so, i guess i'll give a quick api v2 update, sans topic change 18:29:13 the initial commit is in place, and i am starting to arrange the work items on the wiki 18:29:20 #link https://wiki.openstack.org/wiki/Sahara/api-v2 18:29:33 i think we will have a few more folks working on the api as well 18:29:54 so, i am going to start ramping up the patches that will come for it. 18:30:16 i have a feeling we will need to wait until the final mitaka rc is released before we merge them though 18:30:23 so it will be slow for the next month or os 18:30:49 any questions about v2? 18:31:06 elmiko: I am interested, will be volunteer 18:31:13 huichun: great! 18:31:30 elmiko, I am in :) 18:31:31 elmiko, I am also interested in working on that 18:31:35 would it be easier for those who want to be involved if i write the specs needed for the work? 18:31:56 elmiko, count me too :) 18:32:01 awesome! 18:32:05 V2 api covers lots of EDP parts, I think I can help on that 18:32:14 so V2 now has a team :) 18:32:19 yea, seriously 18:32:36 so, i'm hoping we can use the wiki page to organize our efforts 18:32:45 yeah 18:33:01 sounds good 18:33:06 if you see a task there that you are interested in, please put your name in the assignee part and talk to me if you need further guidance 18:33:17 i will be adding more to it soon 18:33:24 perfect, looks like we'll get some traction on this 18:33:24 sure 18:33:41 also, this is just to complete the initial v2 api. once we have it in place, we can start to iterate on adding more features to the api 18:33:50 the initial goal should be to implement everything in the spec 18:34:13 #link http://specs.openstack.org/openstack/sahara-specs/specs/backlog/api-v2-experimental-impl.html 18:35:03 elmiko: you mean put name on that wiki asignee in every work item? 18:35:15 huichun: just the one you'd like to work on 18:35:22 or ones 18:35:53 hopefully, we can work out a good arrangement where everyone can get something to help with 18:36:07 elmiko: did you list all work items? Currently I can see 7 items 18:36:18 huichun: i am still working to get them all up there 18:36:30 Clearly 18:36:30 since this has been slow moving so far, i haven't gotten them all up yet 18:36:53 and, as i said, we most likely won't be merging any v2 reviews until the freeze is over 18:37:19 but, now is a good time to get up to speed on how to enable the v2 api for testing and to familiarize yourself with the tasks you are interested in 18:37:43 for those who are interested, i'd like to know if there are any suggestions on things i could do to make this process better 18:38:33 elmiko, ack we will come with those soon 18:39:06 ok, let's move on then 18:39:14 So how is the working process? First choose one item, write the name on it, then just submit the patch? Any other places should record this? 18:39:48 huichun: pretty much, yes. write your name down so we know who is working on what. create a spec if it is needed, then generate a patch 18:40:35 Clearly 18:40:36 elmiko, are we looking for filing issue tracker bug ? 18:41:02 Poornima: well, these are bugs per se 18:41:17 these are all features that will be covered by the original spec, and then supplemental specs 18:41:29 much of this is discussed in the original spec 18:41:58 next topic? 18:42:10 alright 18:42:13 elmiko: should we add one parts in that wiki, bugs which is related or due to V2 api? Separate the other bugs 18:42:35 and as we create new reviews and specs, we should continue to add "Partial-Implements: bp v2-api-experimental-impl" 18:42:48 Just for tracking no other means 18:43:00 good question 18:43:13 the original spec describes this work, i don't think we need bugs for each feature 18:43:37 as long as we keep referencing back to the blueprint in our reviews, we will be able to track the progress from the bp page 18:43:46 even for new specs we create. 18:43:52 also, yea, lets move on 18:43:57 we only have 15min left 18:44:04 any more v2 questions, post them on the ML 18:44:16 "Scenario tests releases and launchpad project"? 18:44:21 yes 18:44:26 who's topic is this? 18:44:33 let's release sahara_tests :) 18:44:35 i am 18:44:41 ok, go for it! 18:44:47 release criteria: framework ready for testing the new release of sahara 18:45:19 What do you think about it? 18:45:46 when you say release, will it be in parity with the sahara release version? 18:45:52 no 18:46:03 if I understand it correctly, a release is required to publish official tarballs and pypi 18:46:12 what is the release cycle for sahara-tests going to be like? 18:46:15 ah, ok 18:46:15 tosky: yes 18:46:16 also tempest does async releases 18:46:31 will sahara-tests follow tempest then? 18:46:43 well, the criteria are different 18:47:03 tempest creates a release when they have some important change (like recently they remerged the code previously in tempest-lib, and then tagged a release) 18:47:12 or they tag when they stop supporting an openstack release 18:47:22 tempest have not releases 18:47:47 it does: https://pypi.python.org/pypi/Tempest 18:48:01 tags is a just mark 18:48:02 but they are independent from other openstack project, as I explained 18:48:18 #chair elmiko 18:48:18 Current chairs: SergeyLukjanov elmiko 18:48:32 yes, it's required also for test dependencies, so that other projects can depend from a certain version of tempest (aka: when a certain feature is available) 18:48:38 anyway 18:48:39 #topic Scenario tests releases and launchpad project 18:48:50 huichun, re EDP FFE, please send to ML, I think it's fine to grant 18:49:05 thanks for the explanation, i don't have an objection to a sahara-tests release 18:49:10 what needs to be done? 18:49:15 an initial relase, now that sahara-tests is working, is fine; do you have any suggestions when to create further tags? 18:49:23 SergeyLukjanov: clearly 18:49:44 tosky: all patches merged. sahara-test ready for release 18:49:47 elmiko we aren't doing any ansible stuff now in mirantis, we're looking for sahara impl in kolla-mesos some day 18:49:57 SergeyLukjanov: gotcha 18:50:12 tosky: also, i am propose create a launchpad project for bugs in framework or tests 18:50:22 because is independent dproject 18:50:25 esikachev: yes, no objection for a release now; I was asking for the future, if we want to discuss when to create other tags now, or if we want to do it when it's needed 18:50:48 uhm, we didn't create a launchpad project for the dashboard; no strong opinion on this, let's hear from the others 18:51:16 dashboard not released 18:51:20 yea, given that we didn't split for dashboard. i'm not so sure about sahara-tests 18:51:28 good point esikachev 18:51:48 for what purpose we need separate project at launchpad? 18:51:50 i don't have a strong opinion on this, except that it creates a new place to look for sahara related bugs 18:51:53 if i am found a bug i am specify series for him 18:52:08 I guess dashboard will release 18:52:38 and it was released before it was moved to horizon, and still no separate project; but as I said, no opinion 18:52:42 vgridnev: sahara-tests or dashboard? :) 18:52:52 esikachev, sahara-tests, sure 18:53:12 vgridnev: for separating bugs by projects and versions 18:53:14 i think it sounds like, release: yes, launchpad: we need to discuss more 18:53:30 elmiko: ok 18:53:32 i think single launchpad, with some kind of [ ] tag is fine 18:53:43 re sahara-tests release let's discuss probably in mailing list 18:53:48 esikachev: could you put this in an email, your reasons for wanting to create a new launchpad. then we can debate on ML? 18:53:50 esikachev could you propose it to ML 18:54:02 SergeyLukjanov: ;) 18:54:02 I wanna to ensure that we'll raise issues before releasei 18:54:04 SergeyLukjanov: ok 18:54:06 hmm, do we have separate launchpad for the client? sie? I forget 18:54:06 elmiko: ok) 18:54:15 tmckay: yes 18:54:42 tmckay, only for client we have separate project at launched 18:54:50 tmckay, only for client we have separate project at launchpad 18:55:01 let's move on, only 5 min left 18:55:09 #topic Sahara nightly jobs 18:55:18 who added this topic? 18:55:26 i am) 18:55:31 \o/ 18:55:34 #link https://review.openstack.org/#/c/288015/ 18:55:51 i am working on adding nightly jobs for sahara 18:56:14 Like nightly build? 18:56:18 i'm not familiar with this, could you describe briefly esikachev ? 18:56:46 elmiko: sure 18:57:18 i propose every night run full-stack of jobs for testing sahara master 18:57:39 and add new scenario for it 18:57:59 this is different than the tests we run for each review? 18:58:29 in plans: Ambari and CDH (all processes), HA for all services, All EDP jobs, External HDFS, Fake plugin on Python 3 18:58:55 elmiko: yes is different scenarios 18:59:12 #link https://review.openstack.org/#/c/285663/ 18:59:19 for cdh and ambari ^^ 18:59:28 ok, cool 18:59:35 also, 1 min... 18:59:40 do you have any ideas for nightly builds? 18:59:47 it sounds good to me =) 18:59:48 esikachev: so everytime when we submit patches, it will trigger tests, passed, then merged, then will run nightly extra? 19:00:06 At night 19:00:06 ok, times up 19:00:16 huichun: yes 19:00:17 please take the discussion to openstack-sahara 19:00:25 ok 19:00:32 thank you everyone! 19:00:34 #endmeeting