13:02:06 #startmeeting tricircle 13:02:07 Meeting started Wed Jan 13 13:02:06 2016 UTC and is due to finish in 60 minutes. The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:02:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:02:11 The meeting name has been set to 'tricircle' 13:02:44 hi, Yipei, welcome to join tricircle, could you pls introduce your self? 13:03:06 OK. Hi everybody, My name is Yipei 13:03:40 I am a master student of Huazhong university of science and technology 13:04:10 great, I graduated from HUST too 13:04:11 welcome to join! 13:04:42 #topic rollcall 13:04:51 #info joehuang 13:04:56 #info zhiyuan 13:05:10 really?! Which year? 13:05:21 1999 13:05:31 old enough 13:06:18 #topic phase2 progress 13:06:32 #link https://etherpad.openstack.org/p/TricircleToDo 13:06:38 you must be experienced 13:06:50 let's look at the todolist 13:06:58 OK 13:07:44 #info cinder volume CRUD patch was merged today 13:08:19 Zhiyuan, how about your patch 13:08:51 I just submitted a refined patch, the exception when operating bottom OpenStack is considered 13:09:28 ok, review tomorrow. 13:10:18 when neutron plugin fails to attach interfaces in bottom pod, it will try to delete the interfaces on top and bottom 13:10:54 if deleting operation fails again, the top interface will remain unbound, user can use it to attach again 13:11:59 any resource either could be rolled back, or could be reused again. 13:12:27 if something failed during the operation to bottom openstack 13:12:48 I think this could be one of our design principle 13:13:23 #info any resource either could be rolled back, or could be reused again if something failed during the operation to bottom openstack 13:14:42 hi Yipei, which feature do you want to be the first step for your, or some bugs? 13:15:22 We can help you to be family with adding code to tricircle 13:15:34 I am still trying to get familiar with the project 13:15:55 more help needed? 13:16:05 Yes 13:16:16 for example 13:16:27 I read the blueprint of tircircle 13:16:55 any question 13:17:25 i feel much better than solely reading source code 13:17:50 but i just don't know where and how to get started 13:18:17 you can try playing tricircle with devstack 13:18:49 #link https://github.com/openstack/tricircle/tree/experiment 13:19:17 OK. I will try 13:19:32 you can see how the process will run, receive and process request 13:19:51 to yipei, do you know the motivation of Tricircle? 13:20:17 yes, sure 13:20:27 all services are started from the scripts located in cmd folder 13:20:57 so maybe you can start from the data model, like Pod, PodBing, ResourceRoutgin 13:21:10 s/ResourceRoutgin/ResourceRouting 13:21:34 OK, got it 13:21:39 yes, I think Yipei can try to add some fields to the pod table, 13:22:09 then you can dig into the volume controller, I think it's easy to understand than nova, neutron, since not many resource dependency 13:22:13 now the "group affinity" field is missing in the pod table 13:22:45 yes, cinder-apigw is relative easy to understand 13:22:51 the volume controller was merged just now, as Joe said 13:24:05 hi, Zhiyuan, I changed the doc update to done for the task"DHCP""networking concurrency" 13:24:27 ok, thanks joe 13:25:00 zhiyuan, if we move the experiment to master, is it a big impact to your patch? 13:26:37 I think it's better after the l3 networking part1 patch is merged 13:26:49 ok 13:27:24 otherwise I am not sure whether I can figure out which files to copy to master branch 13:27:39 understand 13:28:01 our experiment has already given us very positive feedback 13:28:11 it's time to move experiment to master 13:28:22 that's cool 13:28:26 so tricircle will use stateless design in the master 13:29:03 #info move the experiment branch to master to adopt stateless design for Tricircle service 13:29:53 any other topic to be discussed? 13:30:02 oh, maybe we can start to use #openstack-tricircle channel 13:30:03 next week, i plan to play tricircle with devstack and then understand the data model. if smooth, i will try to add some fields in the pod table 13:30:26 how about it? 13:30:27 thanks Yipei 13:30:35 so yipei can discuss with joe and me online 13:30:45 yes good ides 13:31:05 #info use openstack-tricircle channel for daily communication 13:31:40 and I'll start the "quota" feature in phase2 13:32:16 because I want to find out whether there is some issue for quota control 13:32:57 ok, I will take item1 then item4 13:33:28 we can move VM operation to phase 3 13:34:29 any more topics? 13:34:38 no for me 13:34:48 no for me 13:34:50 Yiper's suggestion is a good stat 13:35:00 stat -> start 13:35:02 ok 13:35:09 let's conclude the meeting 13:35:22 thanks for attending, have a nice day 13:35:29 #endmeeting