13:01:44 #startmeeting tricircle 13:01:45 Meeting started Wed Mar 23 13:01:44 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:46 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:01:48 The meeting name has been set to 'tricircle' 13:02:16 #topic rollcall 13:02:24 #info joehuang 13:02:48 #info Yipei 13:03:03 #info zhiyuan 13:03:15 #Huiji 13:03:22 #info Huiji 13:04:13 #topic mitaka release 13:04:23 hello 13:04:36 hi zyang 13:04:40 ztang 13:04:49 hi joe 13:05:02 for mitaka release is approching for openstack 13:05:27 we need to release tricircle too, so that for mitaka we have a preview release to run 13:06:06 this is not production ready release, but would rather call it preview release 13:06:28 only very basic functions developed during the mitaka cycle 13:06:49 let's look at https://etherpad.openstack.org/p/TricircleToDo 13:07:10 and check to see if some new basic features need to be included in the mitaka 13:09:00 #info preview release aligned with openstack mitaka 13:12:13 hi,Joe, in the command of tricircle, there is some waring. such as the VM crearting and so on. i think we can reduce this kinds of waring 13:13:26 Do you mean the microversion support or something else 13:13:59 yes 13:14:29 ok, add one todo item in the https://etherpad.openstack.org/p/TricircleToDo 13:14:34 and i try to modification the microversion and it was not work 13:15:10 #action add todo item for support microversion 13:16:55 Let's also prioritize and pickup the items to work in next release - Newton release 13:19:43 Hi, Yipei, how about your environment setup? 13:20:30 still have some problems, but i think i need to learn to solve them myself 13:20:43 joe: so not all items in phrase4 will be finished in Newton circle? 13:20:57 And which topic you would like to work in Newton release 13:21:59 we need to prioritize them, maybe more or less, depends on how much we can do 13:23:37 i think cross-pod l2 networking should have high priority 13:24:09 hi, Joe. The area RegionOne and Pod1 were set in the same PM and should they separated? 13:24:12 and also update, delete operations on network, subnet, etc which we only support creating currently 13:24:50 only when we support full operation on resource can we start to involve tempest test 13:26:43 <_lxq_> Hi, Joe, I am a student. I focus on reading the source code of openstack recently. I am thinking that whether it is a good way for developing the tricircle project or not. In other words, would it be enough for me to read the documents of the openstack learning to use openstack API and be familiar with the architecture of the openstack? 13:27:13 agree cross pod L2 networking will be high priority 13:27:20 @Joe, _lxq_ is a member of our team. 13:28:03 to Huiji, it's ok in same physical server, we usually install them by devstak in same VM 13:29:06 to Zhiyuan, part of CRUD operation missing for some objects 13:29:24 welcom lxq 13:29:39 joe: yes, resource in Neutron and server in Nova 13:29:56 you can follow the google doc and this launchpad to study the tricircle 13:30:35 i mean in the production environment, should they separated or the area Pod1 must adhere to the area Region One 13:30:38 #link https://blueprints.launchpad.net/tricircle/+spec/implement-stateless 13:30:54 _lxq_: directly dig into the source code may be a bit hard to understand OpenStack, maybe you can read some blogs and understand the architecture of OpenStack first 13:30:55 in production, it'll be seperated 13:31:13 ok i get it 13:31:27 <_lxq_> thanks. i have read the tricircle source code mostly 13:31:52 @joe, i am interested in cross neutron l2 networking. but i think i am incapable of developing all by myself. maybe i can assist somebody or chose another less complicated item 13:32:17 great, it's also helpful to read openstack arhitecture and be family with api and features 13:33:15 I remember that Yipei is also interested in pod scheduling, currently no one working on it 13:33:19 <_lxq_> ok.thanks joe and zhiyuan_ 13:33:28 for L2 networking, Xiaojie is also interested in that 13:33:35 <_lxq_> Another problem, the current version of the source code is what we download from the github. How to get the newest version in time? 13:33:40 ok, i will take pod sceduling, multiple pod binddings per AZ 13:34:35 _lxq_: do a "git pull" in your repos folder to sync the newest code 13:34:56 using devstack you can also get the latest version 13:36:19 ztang, have you succeeded in tricircle installation for two pods? 13:36:24 <_lxq_> thanks. 13:37:39 hi, Khayam 13:37:56 hi 13:37:58 just one pod now. Some preparatory work we still have to do. But we hope we can start quickly. 13:38:21 didn't got much time to work on tests for exception. currently working on it. 13:39:12 to ztang, good, you can refer to pengfei's blog to install two pods environment http://shipengfei92.cn/play_tricircle_with_virtualbox 13:39:52 to Khayam, thanks a lot, if you have any question, feel free to talk in @openstack-tricircle or mail-list 13:40:02 thanks very much! This is our required 13:40:10 sorry, #openstack-tricircle 13:40:33 ok 13:40:48 sure 13:41:06 to Khayam, I'll be in Austin next month, would it possible to meet you there? 13:41:12 And we are intalling in some physical node, not VM. 13:41:16 for the summit 13:41:43 it'll be easier in VM, especially for multiple pods networking 13:42:28 to joe , thank u so much and we run the devstack in the the real physical environment and the updates of software is a headache questions to us 13:43:49 o, that's a big issue. Is there any other way for fast and easy connection 13:43:59 Sorry no. my visa duration is ending. need to go back to Pakiatan. Hopefully be back in August 13:44:13 A little pitty 13:44:33 we now try to use the vpn to over the wall 13:44:35 yeah. no other reason to miss austin summit :( 13:44:47 ok, it's time to end our meeting, I have to leave now 13:44:54 and the speed is not optimistic 13:45:06 please keep contact in #openstack-tricircle 13:45:20 OK, see you 13:45:25 see you 13:45:27 and think over prioritization of todo list items 13:45:29 ok bye 13:45:35 bye 13:45:41 bye 13:45:41 #endmeeting