01:01:53 #startmeeting tricircle 01:01:54 Meeting started Wed Sep 6 01:01:53 2017 UTC and is due to finish in 60 minutes. The chair is zhiyuan. Information about MeetBot at http://wiki.debian.org/MeetBot. 01:01:55 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 01:01:58 The meeting name has been set to 'tricircle' 01:03:05 Joe is attending huawei connect so I think he will not attend this meeting 01:03:47 first I would like to share some information 01:04:39 yesterday when testing the qos patch, I found a bug in tricircle about client. do you meet this problem? 01:04:50 https://bugs.launchpad.net/tricircle/+bug/1715103 01:04:51 Launchpad bug 1715103 in Tricircle "create_nework in central plugin doesn't return tags filed" [Undecided,New] 01:05:29 my openstack client version is 3.12.0 01:06:28 our smoke test doesn't find out this bug because it uses openstack sdk 01:08:05 yes, I can also have this problem:http://paste.openstack.org/show/620464/ 01:09:48 the same result 01:10:34 since we don't support tag currently, we can add an empty "tags" field in the response 01:11:38 I also find that the types of resources that support tag have been increased 01:11:39 use neutron client can success to create a net: http://paste.openstack.org/show/620465/ 01:12:09 so in our later development, we can consider using tag to label resource, instead of using name 01:12:54 so neutron client doesn't try to read the "tags" field 01:15:41 does using tag to label resource affect neutron client? 01:18:44 to Yipei, don't quite get your meaning. are you asking whehter neutron cilent supports tagging resource? 01:20:07 yes, if we use tag to label resource, can neutron client support it as well 01:22:04 can neutron client work well as before 01:22:51 just check the neutron client code 01:23:03 the following resources are supported 01:23:05 TAG_RESOURCES = ['network', 'subnet', 'port', 'router', 'subnetpool'] 01:24:03 tagging port will be very useful 01:25:46 ok, got it with thx 01:28:54 next is about storyboard. I received a mail from the storyboard team. It's said that they have a script to migrate all the bugs from launchpad to storyboard, but migrating blueprint is not supported ye 01:28:59 s/ye/yet 01:30:55 And we don't have plans to support the migration of blueprints. 01:31:22 Since the concept of blueprints is launchpad specific. 01:33:37 i see, fortunately there are not many blueprints in tricircle 01:35:00 to diablo_rojo_phon, does the migration of bugs include closed bugs? 01:36:13 No, only open ones as far as I know, but the history will still exist in launchpad if you need to refer back for some reason even after you disable the ability to file new bugs there. 01:38:09 ok, thanks for the info. 01:38:42 No problem :) 01:39:33 now let's go through the progress of feature development 01:40:44 pagination of job list needs review: https://review.openstack.org/498430 01:41:41 ok will review it later 01:42:22 i am testing configure_route code in real environment. My code doesn't work well, try to fix it. And begin preparing for the spec and a guide for lbaas. 01:44:47 to yipei, maybe you can submit the spec first, it will be several runs of review before it gets merged 01:46:19 ok, got it 01:46:51 for qos, I tested the latest patch, something wrong with the xmanager so the "create_qos_policy" job fails 01:47:41 we will fix it ASAP 01:50:03 the problem is just about the function name, so it will not be hard :) 01:50:11 got it 01:50:22 any other topics? 01:51:07 no for me 01:51:09 no 01:51:17 no for me 01:51:24 ok, thanks for attending the meeting 01:51:30 #endmeeting