01:01:04 #startmeeting tricircle 01:01:05 Meeting started Wed Jun 21 01:01:04 2017 UTC and is due to finish in 60 minutes. The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot. 01:01:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 01:01:08 The meeting name has been set to 'tricircle' 01:01:23 #topic rollcall 01:01:28 #info joehuang 01:01:30 #info dongfeng 01:01:41 #info Yipei 01:01:42 #info xiulin 01:02:08 #info zhiyuan 01:02:13 Hi all, I am Liyongle 01:02:25 hello, fred, welcome to join 01:03:08 #topic summary of tricircle demo in OPNFV summit 01:03:22 before the summary of the summit 01:03:37 one info about storyboard 01:04:13 the launchpad will be switched to storyboard in recent future 01:04:41 so please try storyboard and community is collecting feedback 01:05:01 https://storyboard.openstack.org 01:05:32 the migration has not been started yet, but we have to be prepared for this 01:05:52 that means all blueprint and bug management will be migrated to storyboard 01:06:21 #info feedback for the storyboard https://storyboard.openstack.org 01:06:54 #info Ronghui 01:07:05 for opnfv tricircle demo, it's quite successful 01:07:08 As soon as I get the okay from you I can set a date to migrate Tricircle. 01:07:42 to diablo_rojo_phon: ok, will let you know when we are ready 01:08:02 shall we submit a patch to open a space for Tricircle in storyboard? 01:08:34 feedback from me: storyboard is convenient for tracking blueprint, since we can create several tasks for one blueprint. 01:09:09 in launchpad, we have to put the tasks in the single white board 01:10:39 ok, I'll dive into storyboard in more detail and check to see if a patch is needed for tricircle 01:11:28 for the opnfv tricricle demo, video and slides are available 01:12:11 #info opnfv tricircle and demo video: https://www.youtube.com/watch?v=tbcc7-eZnkY 01:12:43 #info slides is available here https://docs.google.com/presentation/d/1WBdra-ZaiB-K8_m3Pv76o_jhylEqJXTTxzEZ-cu8u2A/ 01:13:19 and video conference demo is recorded at https://www.youtube.com/watch?v=nK1nWnH45gI 01:13:50 BoucherV will record vIMS video this week, once the link is available I'll share to you 01:14:20 there are several groups showed interest to integrate tricircle in OPNFV 01:15:05 and several guys told me they would like to contribute in tricircle, hope that they will join soon 01:15:42 that's the major info from tricircle demo in OPNFV summit 01:15:54 any questions 01:17:32 ok, next topic 01:17:39 #topic feature implementation review 01:18:13 before the feature implementation discussion, the milestone 3 of pike will be July 28 01:18:31 #info milestone 3 on July 28 01:18:59 so if you want your features to be landed, please submit your patch ASAP 01:19:45 please share your feature implementation and challenge to be discussed here 01:20:40 for me, 1) a patch for resource routing pagination has been committed. 2) job cli feature is under development. 01:21:45 for labs, have some problems with plugging vip via the AmphoraAPIClient. it responses with 500 status code. still working on it 01:21:52 thanks dongfeng, will review the patch soon 01:21:59 oh, I see "merge conflict" for the resource routing pagination patch 01:22:06 en, 01:22:16 s/labs/lbaas 01:22:17 I base this patch on your previous patch 01:23:15 to dongfeng, rebasing is needed I think 01:23:22 ok 01:23:45 local repo has been rebased, I am waitting your comment and then update the next version 01:24:00 i see 01:24:16 ok 01:24:30 for Tricircle can work with cells v2 now 01:25:19 i'am modify sfc's patch according to yesterday's discussion 01:25:38 it's good to update the term of "cross OpenStack L2 network" to "cross Neutron L2 network", can someone help to update this in all document? 01:26:13 to joehuang, i would like to do it 01:26:13 it's easy, I can do it. 01:26:18 oh 01:26:37 got it. 01:26:39 ok, please submit a patch, because Nova support cells V2 in pike 01:26:52 for Qos, we will update all the patch today and submit the last patch ASAP 01:27:09 if Tricricle can support cells V2 in networking side, it'll bring lots of value to cloud operators 01:28:16 and metering spec has passed the test, so other guys can continue to review 01:28:46 to ronghui, since you are going to update all the patches, please change to title of the patches to reflect to correct order. in fact, the current part2 needs to be merged first 01:29:01 s/to correct/the correct 01:29:32 ok just like we talk before 01:30:12 part 2 is the base 01:30:31 does QoS require some special configuration to make it work? 01:30:38 part 2 is the base? are you using reverse order 01:31:12 if so, we need to document them 01:31:38 to zhiyuan: just like openstack qos configuration 01:31:42 yes, documentation for the guide is need 01:31:55 ubuntu_: have you responded all the comments zhiyuan 01:32:36 yes 01:33:05 to joe: yes 01:33:05 to fred, yes, we have discussed the patch in the review page yesterday afternoon 01:33:19 part 2 is the base 01:33:30 so I am waiting for the update 01:33:46 we need to adjust the order of merge 01:34:56 Xiongqiu is try to update the patch and solve the problem you submit and will update the patch today 01:35:27 who is updating the patch, I am confused 01:35:48 Xiongqiu 01:36:20 ok, hope that xiongqiu can talk to us directly 01:36:48 there is some problem with his network 01:36:49 seems that we have reviewed all features in queue, next topic 01:36:58 ok, I see 01:37:10 #topic open discussion 01:37:26 any topic to discuss 01:37:46 nothing more from my side. 01:38:05 one topic from mine is tricircle integration support 01:39:23 just as what I mentioned in the first topic, there are several installer showed interest to integrate tricircle, and Vikram also said whether it's possible to integrate Tricricle with OVN 01:40:14 so if there are lots of integration, some one may ask help, how can we help? 01:42:36 firstly I think we need to investigate that if it's easy to integrate Tricircle with other components. Is there any required patches to be implemented for that intergration. 01:43:12 what actions do we need to do if we support? 01:43:32 currently passive reaction is good enough I think 01:43:52 is it possible to provide one document/script so that partners can do it by themselves? 01:43:59 as I know, if the component is not using l2pop, we need some works to support sdn/l2 gateway mode for vxlan networking 01:44:21 this part is not tested 01:45:01 for OVN if it can recognize the shadow agent/port, I think it can deal with itself 01:46:19 and seems that cells V2 also have its own devstack plugin for multi-cells installation 01:47:16 Tricricle plugin multi-cells installation may not work well with cells V2 multi-cell installation, though function works 01:47:24 that script has been already merged? if so, we can write our own script to integrate cell V2 based on that script 01:47:38 only use Tricricle plugin? 01:48:13 #link https://review.openstack.org/#/c/436094/ 01:48:37 I am thinking that cell V2 script may provide some functions that we can call 01:48:55 not merged yet, but I am sure it'll merge soon 01:49:38 ah, lib/nova is updated in that patch 01:49:48 so except feature implementation, lots of engineering work is needed after more and more integration will be done, and bugs will be reported 01:52:42 tricricle provides documentation for installation/configuration/networking, https://docs.openstack.org/developer/tricircle/ 01:53:05 have you found that it's not clear enough? does it work according to the guide? 01:53:15 what's missing in the guide? 01:53:48 I remembered that the transport URL configuration is missing in configuration or manual installation guide 01:54:40 #link https://docs.openstack.org/developer/tricircle/configuration.html#common-options 01:54:48 could some one update this guide 01:55:05 in the configuration guide, we just mention that "Logging, messaging, database, keystonemiddleware etc configuration which are generated from OpenStack Oslo library, will not be described here" 01:55:42 so transport URL is not covered in the guide 01:56:26 ok 01:56:59 transport_url is discussed in the manual installation guide 01:57:14 ok, any other topic? 01:57:23 no from me 01:57:26 no from me 01:57:37 no for me 01:57:45 no for me 01:57:57 good 01:58:15 ok, thank you for attending the meeting 01:58:18 #endmeeting