06:33:13 #startmeeting taas 06:33:14 Meeting started Wed Mar 23 06:33:13 2016 UTC and is due to finish in 60 minutes. The chair is yamamoto_. Information about MeetBot at http://wiki.debian.org/MeetBot. 06:33:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 06:33:19 The meeting name has been set to 'taas' 06:33:27 #topic Agenda 06:33:29 #link https://wiki.openstack.org/wiki/Meetings/taas 06:33:50 #topic Summit planning schedule finalization 06:34:25 who added this? is this about taas session? 06:34:35 yamamoto_ yes 06:34:51 I thought that if all the members are present here, we can finalize it quickly 06:35:06 than over the email 06:35:48 unfortunately it doesn't seem to be case though. let's use email. 06:36:00 #topic Async Calls 06:36:00 Yes, okay, lets skip it 06:36:09 #link http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html 06:36:12 yamamoto_ Anil sent an email 06:36:18 for the async calls 06:36:26 and I thought we can discuss it here 06:36:32 but, I am not sure now 06:36:45 can we discuss it on the ML itself? 06:37:02 sure. 06:37:12 okay, moving on then, I guess 06:37:14 i guess we all agree async stuff is good idea. 06:37:28 yamamoto_ : as per the last meeting, yes definetly 06:37:33 definitely* 06:37:54 #topic TaaS Dashboard discussion 06:37:58 but I think we can also get some input from neutrinoes 06:38:08 #undo 06:38:10 Removing item from minutes: 06:38:35 okay, next topic ? 06:38:56 #topic TaaS Dashboard discussion 06:39:07 so kaz submitted a patch 06:39:12 yes 06:39:29 #link https://review.openstack.org/#/c/295735/ 06:39:45 kaz, I see that its 403161 Lines long 06:40:05 you copied the entire horizon onto taas? 06:40:14 yes 06:40:21 any reason ? 06:40:37 because we are based on kilo. 06:40:58 any idea what happened on "Conflicts With" ? 06:41:02 is there any reason for using Kilo and not using Mitaka? 06:41:29 yamamoto_ : Not a clue... that what triggered my thoughts on this patch 06:41:48 The Network Topology view was dramatically changed from Liberty. 06:42:01 soichi : okay 06:42:14 soichi : so if we are to support TaaS in Newton 06:42:34 soichi: would we request Horizon to be based on Kilo to see the TaaS dashboard? 06:42:49 no 06:43:30 soichi: but if our changes are made on Kilo, wont we have to rework on it again, if we get the inclusion into governance in Newton? 06:43:40 I guess one of the idea is to show the network topoloy view in kilo on the TaaS panel 06:43:49 soichi: I think its a great idea to showcase it in the Summit 06:44:13 soichi: yes, +1 , but I think some users may ask why we are showing the older topology, isnt it? 06:45:25 soichi: lets work with this implementation , but can we start also to look for integration into Horizon in its M-release version ? 06:45:27 yes, i think some users may have a question. 06:45:54 soichi: kaz: for some reasons you want to stick with kilo, or it just means not-rebased-yet? 06:45:56 reedip: agree 06:46:02 I mean we can , for now, use the dashboard as it is, and demonstrate it, and get some ideas 06:46:35 not rebased yes. 06:46:36 and then , moving forward, we can use the latest release, rebase most the changes which can be ported, and work out the other nitty gritties in N-Release 06:47:11 reedip: okay 06:47:49 soichi : great , thats all from my side for the dashboard. Any other points to discuss for the dashboard? 06:48:19 how long do you think it would take to "rebase" it to master? 06:48:55 (i have no idea how different horizon kilo vs master) 06:49:31 I am not sure , but it takes a few months. 06:49:37 yamamoto_ : huge , if I am correct 06:49:48 kaz, rebase takes months ? 06:50:06 I think a lot of manual work is required, right 06:50:08 ? 06:50:29 will it likely be re-implementation rather than a rebase? 06:51:44 we need to see a new source code. 06:54:34 ok, i understand it's a major work. 06:55:42 i guess it's better (at least easier to read) to submit a patch to horizon/kilo rather than having the entire horizon tree. 06:56:07 i see 06:57:22 let's move on 06:57:30 #topic Spec Discussion completion 06:57:55 i updated the review yesterday 06:58:05 yamamoto_ I didnt see the new spec 06:58:30 reflected many of comments and moved some more things to "future work" section to minimize the scope for the first step 06:58:39 yamamoto_ I think you put up some queries for me as well, I will check it out on the weekend/tomorrow and update it with the same 06:59:09 reedip: thank you 07:00:20 yamamoto_ I would have preferred having the discussion with Anil and Vinay as well, for the points left in the spec which I mailed on the ML. Can we discuss this point as well next week ( I know the list is getting longer for the next week's discussion) 07:01:38 #link http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html 07:02:35 let's discuss on ML and/or review. 07:03:06 #topic Open Discussion 07:03:18 yamamoto_ : nothing much from my end 07:03:50 i have no additional topic. 07:04:02 me too 07:04:08 i wanted to ask anil and vnyyad to tweak LP permissions to allow me triage bugs 07:04:19 lets skip this and end the meeting then :) 07:04:28 yamamoto_ I think you can email them 07:04:32 ?? 07:05:00 i said it here as i think anil said he will read the log :-) 07:05:32 thank you for attending everyone 07:05:45 bye 07:05:47 #endmeeting