13:01:18 #startmeeting tricircle 13:01:19 Meeting started Wed Mar 30 13:01:18 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:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:01:22 The meeting name has been set to 'tricircle' 13:01:59 #topic rollcall 13:02:04 #info joehuang 13:02:14 #info zhiyuan 13:02:16 #info Yipei 13:02:35 #iinfo Ronghui 13:02:38 #info Ronghui 13:02:48 #topic agenda 13:02:57 #info ztang 13:03:07 we have three topic to be discussed in today's meeting 13:03:20 #info cross pod L2 networking 13:03:31 #info pod scheduling 13:03:47 #info reliability async. job 13:04:03 #topic cross pod L2 networking 13:04:45 #info cross pod L2 networking is one of most important feature in next release 13:05:16 and will be used both for tenant L2 networking, and L3 networking(bridge network) 13:05:20 hi, joe i meet a problem i run the destack on node2 and could not find resoure admin and interrupt the devstack 13:05:54 did the node1 run normal 13:05:58 yes 13:06:56 and VM is success running 13:08:05 so it's the problem we met before? 13:08:05 ok, do you guys have any topics about L2 networking 13:08:23 and at the same time, help Ronhui solve the issue 13:08:38 and question about L2 networking 13:08:56 i run on the physical server 13:09:40 have you -export OS_REGION_NAME=$REGION_NAME +export OS_REGION_NAME=RegionOne 13:10:10 fix the script in the devstack 13:11:11 ok it run the keystone create_keystone_accounts:379 openstack project show admin -f value -c id 13:11:12 check this: https://github.com/openstack/tricircle#prerequisite 13:11:34 and Could not find resource admin 13:11:40 for L2 networking cross pod, maybe inside one AZ, or across AZ 13:12:21 Hi Ronghui, could add --debug to see where the command was sent to 13:12:53 ok 13:14:04 xiaojie, how about your recent work about L2 networking 13:14:43 @zhiyuan_ i did not set the admin-openerc on node2 13:16:20 no, the environment variables are exported by DevStack 13:17:30 @joehuang,today ,i start to think about thant,we can discuss friday, ok? 13:18:26 i got it and in the local.conf i and miss the command OS_REGION_NAME=$REGION_NAME 13:19:28 hi ,Joe the -export OS_REGION_NAME=$REGION_NAME is in the local.conf or just a command 13:20:14 oh, that is a diff result of stack.sh 13:20:20 not in local.conf 13:20:21 no, you need to update the script, replace export OS_REGION_NAME=$REGION_NAME with export OS_REGION_NAME=RegionOne 13:21:13 I think Shinobu is correct, we need either trainning, or review the README.MD in github 13:22:10 u mean in the admin-openerc in node1? 13:22:52 stack.sh 13:22:53 @ronghui, modify devstack/stack.sh in node2 13:23:19 ok 13:23:40 i got it i try to modify the keystone but failed 13:23:44 yeah, but i feel a bit strange that after updaring all the projects, i didn't change stack.sh but devstack starts successfully 13:24:15 Hi, Yipei, your segment error need a patch which caused by Neutron. https://github.com/openstack/tricircle/commit/d8d1940b9e43bd11e74017399ae3ba296214cf63 13:24:48 Maybe devstack already fix the bug for multi-region setup 13:24:49 @zhiyuan_ u are run in the virtual environment or truth? 13:25:15 virtual machine 13:25:22 yes, i think i can try it tomorrow 13:25:49 for L2 networking, I think we need a team working on it, it's quite a big features 13:25:54 i thought it is in the truth so this problem happened 13:26:28 if you have phiscial server, you can run virtual box like what pengfei didi 13:26:37 pengfei did 13:27:09 i have 2 physical server 13:27:10 we can design the framework for l2 networking first, then we can code together 13:27:10 Hi, Zhiyuan and Yipei, how do you think about the L2 networking 13:27:11 I think we spent many time in the system congiguration. Not like i in the Spark resource project, some module are easy to modify and rewrite directly. 13:27:34 so i run in diff physical node 13:27:40 not virtual box 13:28:40 run VM will be easy to destroy devstack and dependency package. just create a new VM and get latest devstack 13:28:53 @joe, sorry, I do not have much idea about the L2 networking. i think i still need to do more research on it 13:29:59 Spark is single application, may be modulated better. 13:30:32 agree with Zhiyuan, we can have a framework for L2 networking first 13:30:59 joe, as you mentioned before, we need to build a plugable mechanism for l2 networking, so i think we need to list all the scenario we want to support first 13:31:33 then we can abstract the model and logic 13:31:41 great 13:31:47 i agree with zhiyuan_ 13:32:09 How about ztang and ronghui, your idea about L2 networking 13:32:23 may discuss with xiaojie on Friday 13:33:09 #action let's discuss L2 networking in #openstack-tricircle on Friday 13:33:40 i think we should list all the scenario with nova cinder nerturn before framework 13:34:30 the vedio about cascading is simpleness 13:34:43 Yes, so we can add one ether pad for the discussion, to put some items in the etherpad to be discussed 13:35:01 I agree with zhiyuan, the framework should be a plugable. 13:35:49 pluggable to deal with different scenario 13:36:07 #info L2 Networking framework should be pluggable 13:36:45 ok create a new etherpad for L2 networking discussion 13:36:51 #link https://etherpad.openstack.org/p/TricircleCrossPodL2Networking 13:37:47 should we consider the migration? 13:38:28 you mean VM/volume migration? 13:38:40 yes 13:39:08 of course, are you interested in this topic? 13:40:06 i have done before the migration of VM between diff node in physical enviroment 13:40:40 great, if you are interested in this one, it would be great to work on it in tricircle 13:41:08 I have researched some algorithms about VM migration using bin-packing method 13:41:54 can it be applied in cross pod scenario, for tricircle is more about coordinator for different bottom openstack instances 13:42:02 but some experiments are implemented under cloudsim platform. 13:42:36 hi joe. i hava read the tricircle resource and also read the keystone and nova and cinder doc,but i dont familiar with the neutron ,can you give some suggestions about how to start joining project for me? 13:42:39 o, a little different with OpenStack, but some technology may be reused 13:43:20 lxq can not connent xchat, the above question is proposed by him. 13:43:57 from lxq: hi joe. i hava read the tricircle resource and also read the keystone and nova and cinder doc,but i dont familiar with the neutron ,can you give some suggestions about how to start joining project for me? 13:44:13 ok. I think you can find some material on SlideShare for neutron, and some blog in mirantis/redhat are also very good 13:45:36 the migration before is based on shared storage on compute node and in tricircle is same or diff? 13:46:08 and i done it on L2 networking 13:46:18 I suggested that we have a meeting in #openstack-tricircle on Friday about L2 networking, at UTC+8(China time, 4:00pm) 13:46:48 we must over the wall to access the SlideShare 13:46:49 it's different, because no shared storage between pod 13:47:05 oh sorry joe, i would like to ask for a leave Friday afternoon 13:47:38 yes there is no shared storage between pod 13:47:55 ok, what time you suggest would better work for you 13:49:07 I am leaving on 3pm 13:49:14 you can try VPN service, Zhiyuan can give you some infomation 13:49:34 so let's have meeting 9:00AM, friday 13:49:43 that's fine for me 13:50:26 that's great 13:50:48 @zhiyuan what about your email address? 13:50:52 Ok, Let's continue the discussion on Friday. And if you have any question on devstack, we can communicate in the channel #openstack-tricircle daily 13:51:24 you can ping zhiyuan in #openstack-tricircle, or me 13:51:32 luckyvega.g@gmail.com 13:51:41 thank for answero for all of u 13:51:44 what about xiaojie? time is ok? 13:52:05 ok. We have two topics not discussed today, let's discuss next time 13:52:08 actually you can send mail to openstack-dev maillist 13:52:15 xiaojie, are you online 13:53:11 yes, like what Yipei did 13:53:25 ok, Xiaojie's connection is lost. 13:53:31 let's end the meeting. 13:53:45 #endmeeting