14:01:43 #startmeeting sahara 14:01:43 Meeting started Thu Dec 3 14:01:43 2015 UTC and is due to finish in 60 minutes. The chair is elmiko. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:44 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:48 The meeting name has been set to 'sahara' 14:01:56 o/ 14:02:01 hi! 14:02:04 hi 14:02:06 hi 14:02:11 hi 14:02:17 hi 14:02:41 hi 14:03:40 ok then, let's get rolling 14:04:05 #topic sahara@horizon status (crobertsrh, vgridnev) 14:04:11 the only news that sahara-dashboard is back, with devstack plugin. 14:04:13 is it time to retire this topic yet? 14:04:38 maybe we should call this horizon@sahara now ;) 14:04:43 so I need to find some time to migrate all changes from horizon to sahara-dashboard 14:05:00 cool 14:05:01 I plan to start migrating some changes today or tomorrow. 14:05:17 nice 14:05:24 We still need to get some tests going there as well. 14:05:47 so what's been going on so far, i've seen some patches from david-lyle 14:06:18 crobertsrh, do you mean integration tests, right? 14:06:46 Yes. Also, I think the unit tests need to be running. 14:07:24 uh, good to know 14:08:03 Hmm, maybe they are running. The output looks different than before though. 14:09:12 crobertsrh: link? Maybe after the meeting 14:10:02 http://logs.openstack.org/17/252017/4/check/gate-sahara-dashboard-python27/982dc6c/console.html#_2015-12-02_17_47_02_472 It does look like they are running. I just am so used to the other horizon tests running along that it looked funny to me. 14:11:01 anything else on this topic? 14:11:07 nothing from me 14:11:28 moving along 14:11:32 #topic News / updates 14:11:38 so, what's everyone been working on? 14:12:22 crobertsrh: (sorry for going back to the previous topic) not integration, they are still in horizon 14:12:36 tosky: right 14:12:44 so, I'm working on https://bugs.launchpad.net/sahara/+bug/1486653, there are some changes that improves how we are working clients and trusts 14:12:44 Launchpad bug 1486653 in Sahara "Create big cluster failed because token expired" [High,In progress] - Assigned to Vitaly Gridnev (vgridnev) 14:12:51 no updates from me 14:13:35 working on spec (in next topic) 14:13:48 i've got the first big piece of the improved secret store up, although it has some issues with the global requirements i could really use some reviews 14:13:53 #link https://review.openstack.org/#/c/220680/ 14:14:12 and the apiv2 spec has been updated 14:15:04 I've been slightly derailed by a bug: https://launchpad.net/bugs/1521266 It probably on affects people using pycharm or eclipse. 14:15:04 Launchpad bug 1521266 in Sahara "Debugging via pydev in PyCharm fails after change to use oslo.service" [Low,In progress] - Assigned to Chad Roberts (croberts) 14:15:55 any progress on that crobertsrh? (i know it's been a pain for more than a few days now) 14:16:16 I have a patch up that is working for me. 14:16:21 ooh, nice! 14:16:28 smacked by -1 this morning though 14:16:37 so, back to the drawing board 14:16:43 arg 14:16:51 m1 is coming 14:16:59 #link https://review.openstack.org/#/c/252887/ 14:18:19 any other news to share? 14:19:14 If you use the dashboard at all, be sure to adapt your setup to use the sahara-dashboard repo. 14:19:35 Also, be sure to review the patches that land there, even if it's just from a functionality point of view. 14:20:24 I'm working on cdh plugins refactoring https://review.openstack.org/#/c/252887/ but due to diffence between the v5 and other versions, i'm afraid come duplicated codes are not easily removed. 14:21:00 some... 14:21:24 crobertsrh: has the sahara stuff been disabled in the horizon repo? 14:21:47 good question, there was a patch that was up to do it...checking it now 14:22:20 Not yet: https://review.openstack.org/#/c/248838/ 14:22:49 ack, thanks. definitely something to watch, i know i'm gonna get bit by this ;) 14:23:17 ok, there were no action items from last week, so we'll move to the next topic 14:23:25 #topic Discuss sahara scenario tests extraction (esikachev, vgridnev, SergeyLukjanov) 14:23:34 esikachev, vgridnev 14:23:45 #link https://review.openstack.org/#/c/250419/ 14:23:51 thanks 14:24:42 can you review this spec and let's disscus about this idea 14:25:10 sure thing /me looks 14:25:44 i propose move scenario tests to new repository and install as plugin (like tempest) 14:26:00 Folks, please, I putted that to the agenda to mention that we need review for this spec to collect all feedback, and probably we should discuss that 14:26:57 not sure everyone are familiar with that, so I think that we need to discuss that one next meeting 14:27:18 vgridnev: probabaly, but it's a short spec 14:27:33 i am curious why we need to move them into a separate repo? 14:27:57 sounds like managing various releases is a motivation for that 14:28:20 elmiko, the general idea is to have ability of testing several stable branches with master of scenario tests 14:28:23 esikachev: as plugin for sahara? 14:28:49 I think we already discussed this many times :) 14:29:21 tosky: ack, are we just rehashing old discussions? 14:30:05 so fine with the idea, I think that the spec needs to define the details but I need to reread it, I've seen only the first update and I missed the new version of the spec 14:30:09 sreshetnyak: maybe, i want to discuss it 14:30:09 it looks more complete now 14:30:37 esikachev: i think the spec could use a more concrete example of how this would work 14:30:39 but there is one thing it seems to not clear 14:31:21 right now tempest, the other big example of branchless repository, increases the requirements following global requirements, if I'm not mistaken 14:31:55 but this means that it's complicated, after few months, to run tempest master on an older (supported) openstack without using many updated python components from pip 14:32:23 tosky, what about virtual env? 14:32:44 vgridnev: pip in virtualenv, but still you can't test with the packaged version you have around 14:32:59 almost sounds like each plugin would need its own requirements.txt 14:33:12 elmiko: that's about the test runner itself 14:33:19 ah, ok 14:33:41 so the question is: can we decide to keep the dependencies to the oldest supported branch instead? 14:35:29 i'm not sure how that would interact with the global-requirements 14:35:59 good point, I have no idea how it works in that regard 14:36:02 also, this spec may be of interest https://review.openstack.org/#/c/226157/ 14:36:20 it's about backward compatability and testing all supported branches 14:36:53 tosky: need to check that all packages from test-requirements we can install from operation system repository 14:36:54 does tempest have the ability to run each test(plugin?) with its own set of reqs? 14:37:51 sreshetnyak: that could be tough 14:38:04 elmiko: as I read the spec, it's just move the tests to a separate repository, for all supported versions 14:38:38 sreshetnyak: well, for example in RDO all requirements are packaged; not all _test_ requirements are packaged, even if the idea on the long term is to have them packaged 14:38:43 instead of using pip 14:39:32 so, it sounds like we should add some of these comments to the review 14:40:07 esikachev, vgridnev, are there some specific points you wanted to discuss about the spec? 14:40:16 to summarize my scenario, let's say this: suppose that Mitaka is out and I can run the tests using only packaged dependencies for RDO/MOS/whatever other packaging system 14:40:56 I'd like to continue to use the same dependencies, but a more updated set of tests, even during the lifetime of Mitaka; so without the need of new base dependencies (without pip and virtualenv) 14:41:06 that's the thing I'm asking, if it is possible 14:41:15 Write a comment and discuss at the next meeting again 14:41:30 tosky: good question 14:41:32 sure! 14:42:47 anything else on this one? 14:42:49 so let's move on, I think, waiting for comments on review 14:42:57 tosky: it's good, but we don't support new features in tests for stable releases 14:43:17 #topic API v2 progress 14:43:35 the main spec has been updated #link https://review.openstack.org/#/c/212172/ 14:44:01 and i am starting to refactor the wiki page to help organize the work #link https://wiki.openstack.org/wiki/Sahara/api-v2 14:44:31 not much to discuss yet, but i could use more reviews on the spec, and we need to collect all the ideas for the first version of the v2 api 14:44:40 any questions? 14:44:57 yeah, I started reading of that, now at middle. no questions right now 14:45:40 thanks 14:46:06 #topic New CLI 14:46:13 not sure who added this one 14:46:27 AndreyPavlov, ? 14:46:31 is this about moving to the openstackclient? 14:47:59 nope, i didn't add this) there is nothing much to say - new CLI is ready to use 14:48:23 magic 14:48:29 great to hear that 14:48:34 hehe, maybe it was SergeyLukjanov 14:49:12 so, the agenda talks about the process around the new cli. have those questions been answered? 14:49:13 if you have any suggestions on its improvement feel free to ping me 14:49:48 how to verify, replacing the old one, when to deprecate... 14:50:12 elmiko, old one already deprecated 14:50:23 it's already printing a warning about deprecation 14:50:26 not sure when it's supposed to be removed 14:50:38 i would guess sometime next cycle 14:50:48 (or maybe later if keystone is any indication) 14:51:24 it sounds like the questions on the agenda have already been answered then? 14:51:48 don't know when we need to remove it completely, but it's mentioned that the old one will not be updated anymore 14:52:00 sounds good 14:52:17 elmiko: start of next cycle to answer your question 14:52:30 we should probably update the documentation to reflect the usage of the new cli 14:52:35 stevemar: excellent, thanks! 14:52:42 it's already updated 14:52:48 AndreyPavlov: what about CLI tests in tempest? 14:52:55 AndreyPavlov: lol, oops, must have missed that 14:53:54 AndreyPavlov: what about http://docs.openstack.org/developer/sahara/devref/quickstart.html#register-the-image-with-the-sahara-image-registry 14:54:02 this still mentions the `sahara` cli 14:54:27 tempest contains ~2-3 tests for old CLI 14:54:35 sreshetnyak, old ones will be removed after client release, there's no reason to add new ones IMO 14:55:04 ekmiko, will update it right after the next release of our client 14:55:12 ack, thanks 14:55:26 5 minutes left 14:56:24 and what about the tempest tests? 14:57:45 there's no need to add additional tests for CLI 14:58:03 ok, so just removing the last few tests for the old cli? 14:58:31 yep 14:58:35 cool 14:58:42 #topic Open discussion 14:58:47 any last minute items? 14:59:17 AndreyPavlov: why no reason to add new tests for the new CLI? 14:59:30 at least the basic ones (it starts, it reads plugin, etc) mimicking the current ones 15:00:08 time's up folks, lets take this to the sahara channel 15:00:10 thanks everyone 15:00:13 #endmeeting