14:00:22 #startmeeting sahara 14:00:26 Meeting started Thu Nov 19 14:00:22 2015 UTC and is due to finish in 60 minutes. The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:28 hi 14:00:29 #link https://wiki.openstack.org/wiki/Meetings/SaharaAgenda 14:00:30 The meeting name has been set to 'sahara' 14:00:37 let's wait a few mins for more attendees 14:01:21 hi 14:02:22 o/ 14:02:49 o/ 14:03:02 #topic sahara@horizon status (crobertsrh, vgridnev) 14:03:07 folks, please 14:03:36 Hoping to have our code back in sahara-dashboard sometime in the next week or so. 14:03:44 I have nothing in this topic 14:03:50 crobertsrh, great! 14:04:01 That will mean rebasing quite a few existing changes, of course. 14:04:09 any news from david lyle? 14:04:18 That is the news from him :) 14:04:29 cool 14:04:52 are there any current issues preventing it? 14:05:27 i've also noticed that we have new group in gerrit, sahara-dashboard core 14:06:04 yup 14:06:16 it currently includes sahara-core 14:06:31 and I think that we should add crobertsrh and NikitaKonovalov to it 14:06:42 He mentioned that there are some integration test issues, but thinks that he might work those out separately. 14:06:47 +1 14:06:56 do we need to vote for it? any objections? 14:07:14 do we even have to vote on the mailing list? Can we just do it? 14:07:19 heh :) 14:07:25 no objections 14:07:26 I think we can just do it ;) 14:07:42 nobody who is not crazy would ever object to a dashboard core 14:08:10 done :) 14:08:28 anything else to chat about re dashboard? 14:08:50 nothing from me 14:09:01 Nope 14:09:05 Move to this channel? 14:09:11 crobertsrh, congrats, those patches are going to merge before they even cool off ;-) 14:09:28 heh 14:09:53 #topic News / updates 14:10:14 direct engine finally removed! 14:13:44 tmckay: Scheduled edp job has been long time reviewed, and modified according to all review comments, wish to be reviewed quickly T_T 14:13:51 not much from me, I put up a few specs that I hope I will get to soon 14:14:15 huichun, ok. 14:14:45 is elmiko here? 14:15:49 * tmckay thought maybe he had something to add about secret store or V2 API 14:15:58 vgridnev, please take a look on scheduled edp job patches 14:16:13 huichun, are you going to add integration tests for scheduled jobs? 14:16:31 Yes but another patch 14:16:45 Because they are separated 14:17:02 separated from what? 14:17:20 huichun, I will look today, too. I have not done many reviews since Tokyo. 14:17:46 I will write another patch to submit 14:18:24 * tmckay goes to lots of meetings it seems :) 14:18:28 tmckay: hi 14:18:36 doh... dst... 14:18:47 elmiko, hey, any updates on secret store or v2 API or anytihng? 14:19:03 just posted a new patch for secret store last night, the config wrapping is in place 14:19:07 vgridnev: I think one patch is for feature , one patch for interagration test will be clearly 14:19:12 api v2, still working on gathering changes for the spec 14:19:57 elmiko, do we need separated topic on today's meeting re v2? 14:20:14 SergeyLukjanov: not this week, thanks 14:20:37 i'd like to keep it as a separate item though, so we can keep it current 14:21:22 tmckay: thx Trevor 14:22:07 #topic Open discussion 14:22:09 huichun, it's clear but it all-in-one case we will be sure that everything works well 14:25:59 huichun, ok, waiting for a change with scheduled tests 14:26:06 oh, related to protected/public 14:26:29 so it's possible now, but it came up when we were talking about allowing public to be changed on protected items 14:26:54 vgridnev: for integration test, I will make resume suspend scheduled as one 14:27:00 we probably need to investigate what happens when a public ng or cluster template is made non-public when it is referenced in a cluster by another tenant 14:27:21 what might break? Do we need to disallow public -> non-public for referenced templates? 14:27:26 I have no idea, haven't tried 14:27:31 not sure what will happen 14:27:39 db lookups will fail, that's for certain 14:27:57 but there might be enough cached in the cluster object that it doesn't matter 14:28:23 anybody ever try this? 14:28:26 huichun, let's do scheduled first 14:29:21 tmckay: I have not tried such a thing. 14:30:41 crobertsrh, I'll make a note to try it 14:31:52 is there any news about the ci lab with respect to the "Quota exceeded for port" errors we are seeing? 14:32:16 esikachev, ^^ 14:32:37 yes, this problem is resolved 14:33:08 \o/ 14:33:10 thanks 14:33:26 there was a problem with reinstalling devstack on ci 14:33:50 i knew devstack was in there somehow ;) 14:36:09 vgridnev: maybe I add integration test as one patch followed this scheduled patch? Cause everytime I should resubmit and it will clear over the passed review 14:36:11 tmckay, i haven't tried this, but it's pretty much the same case as if referenced public template would be deleted 14:36:28 the problem is how to control such situations 14:37:25 AndreyPavlov, ack. In the general case, we don't allow deletion of referenced templates, so maybe we just need those checks on public -> non-public 14:37:51 same logic would work, I think 14:38:04 I'll poke at it 14:39:16 actually this template can be referenced by private resource created in another tenant 14:39:32 huichun, you can make the change based on scheduled patch, I think we will not have any issues with that 14:39:47 in this case it will be invisible for sahara when it comes to deletion 14:39:55 or update op public field 14:40:25 do we want to let sahara search across all tenants? 14:40:32 huichun, you can ping me in case of problems by mail or in irc, I will help you 14:41:02 AndreyPavlov, why not? It has admin credentials under the hood anyway, and superuser db access 14:41:12 filtering search by tenant is only a filter 14:41:35 it wouldn't expose any information, except that "someone is using the thing you shared, sorry!" 14:42:00 the only other thing I can think of is to auto-copy templates (we have talked about this kind of thing before) 14:42:24 since tenant/name is unique, it could just be automatically injected into the tenant that is consuming it 14:42:40 but, ids and tables and things would be messed up 14:42:48 vgridnev: so I write another patch(integration test)depends on this scheduled patch, does this make sense? So you can keep review on this scheduled patch, because it really take long time(many times has two +2,nearly merged,but comes -1,then restart) 14:42:50 (which is why I think we have not tried such a thing in the past) 14:43:09 AndreyPavlov, I'll see what happens and write some kind of spec, we can talk about more there :) 14:43:11 vgridnev: thx for your help Vitaly 14:45:20 Yes, that make sense, I think. If we would tests we can merge that as we will have two +2, I think) 14:45:31 huichun, ^^ 14:46:09 vgridnev: thx Vitaly ^^ 14:46:09 tmckay, i guess we need to think about concerns of across-tenant searching 14:46:36 cause if we will not find them, it would be much easier and clear to implement 14:47:03 AndreyPavlov, yes, good thought. spec spec spec :) We will beat it into submission :) 14:47:25 I'll plan to try it this week, and put something up for discussion 14:47:42 tmckay, ok :) 14:50:14 oh, folks. We moved all bugs that lost activities for 180 days to Incomplete state, so, please if the bug that still should be fixed move that from incomplete state 14:51:57 Ok :) 14:55:12 5 mins left 14:55:13 any topic to discuss? 14:55:29 nothing from me 14:57:19 #endmeeting