18:01:50 #startmeeting sahara 18:01:51 Meeting started Thu Sep 18 18:01:50 2014 UTC and is due to finish in 60 minutes. The chair is alazarev. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:01:53 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:01:55 The meeting name has been set to 'sahara' 18:02:20 I’ll chair the meeting again 18:02:36 ErikB, NikitaKonovalov, RobLevas, SergeyLukjanov, aignatov, alazarev, bob_nettleton, crobertsrh, dmitryme, elmiko, jspeidel, mattf, skostiuchenko, sreshetnyak, tellesnobrega, themistymay, tmckay, tosky, ylobankov: meeting time 18:02:41 hello/ 18:02:45 hihi 18:03:43 tosky: hihi is a giggling in Russian :) 18:04:27 ok, let’s start 18:04:43 * SergeyLukjanov in CA till October 11 18:04:50 #topic sahara@horizon status (croberts, NikitaKonovalov) 18:04:59 ok 18:05:11 I have one horizon bug merged 18:05:25 So we still have a number of bug fixes on review 18:05:27 I've just mostly been testing things. alazarev found a bug this morning, but it looks like there is already a patch in queue for it 18:05:58 some reviewers asked me to add test to Templates copying 18:06:02 two are waiting for new python client which is released, change to requirements: https://review.openstack.org/#/c/121942/ 18:06:04 so I'm working on that 18:06:35 SergeyLukjanov: should we ping requirements guys somehow? 18:07:50 alazarev, I'll do it 18:07:58 also, we should merge https://review.openstack.org/#/c/118885/ asap 18:08:16 sahara is useless without it 18:08:23 Yes, I'll see if I can get some horizon interest in reviewing it 18:08:54 ok, let’s move on 18:08:59 #topic News / updates 18:10:21 i've been looking at saharaclient and going through the documentation, i think we have room for improvement over what is documented. i'm going to write up either a bug report or propose a spec surrounding how saharaclient authenticates 18:10:25 from me it is just minor fixes, testing 18:11:02 I’ve returned back from PTO this week, promis to complete my patch for updating rest api docs https://review.openstack.org/#/c/118499/ 18:11:07 also, i'm thinking about looking into this https://bugs.launchpad.net/sahara/+bug/1319079 18:11:08 Launchpad bug 1319079 in sahara "[HDP] Threads do not depend on the state of the cluster" [High,Confirmed] 18:11:43 elmiko: it will require major changes in hdp plugin, probably too late for J 18:12:03 alazarev: oh, ok. maybe i'll look at something smaller. 18:12:22 agree with alazarev 18:12:32 elmiko: K will be opened soon :) 18:12:38 Yeah, I'm staring to look at various sahara bugs as well. It's been forever since I was in that code, so I'm starting small. 18:13:30 alazarev: ok, i can just keeping working towards K then 18:13:56 other news? 18:14:38 no action items from the last meeting 18:14:40 No news from me. I've been doing some thinking on a new UI workflow, but that is for K 18:14:41 when is a release dates/plans? 18:14:52 #topic Juno status and FFEs (SergeyLukjanov) 18:15:12 okay 18:15:17 aignatov: good topic for answer :) 18:15:30 #link https://wiki.openstack.org/wiki/Juno_Release_Schedule 18:15:40 the rc1 will be next week 18:15:53 so, now is the good time to concentrate on fixing bugs 18:16:05 release is Oct 16 18:16:12 are we ready for that, all features already landed? 18:16:17 Congratulations btw @SergeyLukjanov! 18:16:22 no more FFEs 18:16:25 crobertsrh, thx! 18:16:38 aignatov, I think mostly all work done 18:16:40 swift-auth is merged to Sahara, we just need to get this https://review.openstack.org/#/c/118972/ and the ui portion merged 18:16:46 SergeyLukjanov: except my patch for updating docs I guess 18:16:54 crobertsrh, and me, and me :) 18:17:09 Ah yes...of course DinaBelova! I didn't see you there :) 18:17:13 SergeyLukjanov, DinaBelova, grats to both =) 18:17:26 I figured that Sergey was really the luckier one though, right?? 18:17:30 folks, please, stop approving any features, refactoring and etc. 18:17:31 lol 18:17:36 thanks :) ok /me does not ruin this meeting anymore 18:18:29 that's all from me re releasing 18:18:31 oops, forgot 18:18:31 any q.? 18:19:54 it looks like no questions 18:19:56 #topic Open discussion 18:20:47 SergeyLukjanov: I want to discuss pylint stuff with you, but since you are in US now we can do it personally 18:20:54 i've been researching creating a swagger spec for Sahara's rest interface, has there been any work done on deriving the rest api using scripting tools? 18:21:50 there is review which introduces tempest-style tests, but it was temporarily blocked; will it go into K at this point? 18:22:23 swagger spec? what is it? 18:22:24 alazarev, yup, let's talk today 18:22:35 hey folks, I’ve noticed that our Upgrade Guide is missing notice that there is no more sahara-dashboard and it is merged into Horizon. Does anybody is working on a patch to add this? If not, I can write this up 18:23:10 aignatov: https://github.com/wordnik/swagger-spec it's a language agnostic way to describe rest apis, there is some great tooling that can use the spec. i think it would be nice for Sahara. 18:23:11 dmitryme: sounds like a good plan if’ll do this :) 18:23:29 *if you’ll do this :) 18:23:33 dmitryme: ++ 18:23:46 dmitryme: +1 18:23:58 ok folks, will do this 18:24:39 elmiko: how can we apply that if it’s not openstack related initiative? 18:24:47 aignatov: also, look at this http://petstore.swagger.wordnik.com/ to see one way of using the swagger spec. that page is generated by a swagger-server, i think it would be cool to have something like sahara-docs that could spawn this. 18:25:11 aignatov: i propose initially writing a tool that would parse the sahara.api module to generate the spec. 18:25:42 perhaps if we can show the power of it we could convince other openstack projects to generate interest 18:25:47 Seems like it should be simple enough to do. The output is potentially very useful. 18:26:24 most of our json validation schemas alread conform to the standard, i think it would easy to derive the endpoints with validation info. 18:26:41 *already 18:26:54 elmiko: I like it, but don’t think it will be easy get it adopted by openstack comunity 18:27:33 alazarev: maybe not, but we could generate our scripts outside of openstack. if it got accepted at some point, great, but if not we could provide another methodology for users to explore Sahara. 18:28:05 at this point, i look at the effort as a user-contrib style project 18:28:57 elmiko: openstack will never take scala solution :) 18:29:15 i had heard that there might have been some work to help auto-generate our api docs, is that the case? 18:29:25 alazarev: there are python bindings too 18:30:04 anything else to discuss? 18:30:45 ok, thank you folks! 18:30:46 #endmeeting