13:01:23 #startmeeting tricircle 13:01:24 Meeting started Wed Jun 8 13:01:23 2016 UTC and is due to finish in 60 minutes. The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:01:25 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:01:28 The meeting name has been set to 'tricircle' 13:02:13 hello, tomorrow is China's public holiday 13:02:17 hi 13:02:41 I am afraid some team members will not be available 13:02:48 #rollcall 13:02:55 #topic rollcall 13:03:01 #info joehuang 13:03:11 #info Yipei 13:03:43 hi Zhiyuan 13:03:55 #info zhiyuan 13:04:43 #info the PyPI package has been registered and the publish to pypi job also has been configured 13:05:38 so it would be good to have a release to test the process work or not, that means if there is a new tag or release 13:05:56 the package should be able to be published to pypi 13:06:11 and can install Tricircle through pip install 13:07:05 so I prepare a list of patches which could be cherrypick to the stable/mitaka branch, so that we can have a new tag like 2.0.1 release 13:07:21 please have a look in the maillist 13:07:35 check to see whether it's ok 13:07:43 but previously we tried to cherry-pick to stable/mitaks branch and failed 13:08:01 now this issue has been fixed by infra team 13:08:17 and all patches were successfully merged now 13:08:34 cool 13:09:34 #action cherrypick select patches to stable/mitaka, then have a new tag 2.0.1 in stable/mitaka branch for release 13:10:16 ok, Yipei, how about your progress in dynamic pod binding? 13:12:19 i read the source code of nova scheduler, but still don't have idea about how to start designing the framework 13:12:39 it seems a lot work to do 13:13:16 design a filter first? 13:14:08 i think not a filter, but a framework to allow the filter to work 13:14:47 zhiyuan is correct 13:15:17 when nova api gateway starts, load the filters. when provision VM, apply filters to select a pod 13:15:57 you should design the interfaces of the filters 13:16:42 like what functions should be implemented, what parameters these functions should have 13:16:45 it's a common functionalities both for Nova and cinder 13:17:24 ok. i see 13:17:35 oh, then cinder api gateway also loads the filters 13:17:56 Hello, Zhiyuan, there is a good news from L2GW? 13:18:00 ok. got it. i will take it into consideration 13:19:18 yes, i have successfully connected two OpenStack instances with L2 gateway. the original L2 gateway plugin is extended to support remote L2 gateway. also, hardware_vtep schema needs to be extended. 13:20:11 another problem, when i execute unit tests by tox, the error "no module named cinderclient". does it mean i need to run unit tests in complete openstack environment? 13:21:04 Great news, zhiyuan 13:21:26 #info successfully connected two OpenStack instances with L2 gateway. the original L2 gateway plugin is extended to support remote L2 gateway. also, hardware_vtep schema needs to be extended 13:22:26 strange, i remember that tox will install the dependency and cinderclient is in the requirement list 13:22:39 python-cinderclient is installed in my environment 13:22:41 the cinderclient should be installed in the venv when you execute the tox 13:23:37 tox will start a venv and install dependency in the venv 13:24:49 i first execute tox -e py27 --notest, and tox install all the dependency 13:25:08 in py27 environment 13:26:03 no need to plus --notest 13:26:24 and try in a clean environment 13:26:46 ok, i will try again 13:26:54 good 13:26:54 in a clean environment 13:27:13 other topics? 13:27:22 about my spec file 13:28:00 do i miss any content in spec file? 13:28:59 Shinobu's comment not covered 13:29:06 and new patch is needed 13:30:37 ok, i will add some description about key concept, and update the commit message 13:31:12 The title of " Add specification file of dynamic pod binding" is not good 13:31:54 ok, i will revise it 13:31:57 Add specification for dynamic pod binding will be better 13:32:17 "Add specification for dynamic pod binding" will be better 13:32:38 other topics could be discussed in next weekly meeting 13:32:56 ok 13:33:15 let's end the meeting here 13:33:26 #endmeeting