01:00:19 <shuoy> #startmeeting Compass online design session 01:00:20 <openstack> Meeting started Thu Aug 20 01:00:19 2015 UTC and is due to finish in 60 minutes. The chair is shuoy. Information about MeetBot at http://wiki.debian.org/MeetBot. 01:00:21 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 01:00:23 <openstack> The meeting name has been set to 'compass_online_design_session' 01:01:44 <shuoy> Hi everyone, let’s get started for the meeting with 3 topics: 1) Status on Ansible; 2) Improved support of networking config; 3) Shall we prepare for "rule the stack" contest, which is sponsored by Intel at past Summits. 01:01:55 <shuoy> Let’s go through them one by one 01:02:23 <shuoy> #topic 1) Status on Ansible; 01:03:08 <shuoy> xichengc, can you give the context and update this? 01:03:59 <xichengc> yes, the upstream OSAD(openstack-ansible-deployment) repo deploys openstack components onto baremetal servers, with some of the components in Linux containers 01:04:35 <xichengc> I have created an etherpad at https://etherpad.openstack.org/p/compass-osad-integration 01:05:14 <shuoy> xichengc: have you talked/engaged with the OSAD developers? 01:06:01 <xichengc> I have not. I think the interactions should be based on further understanding of OSAD playbooks. 01:06:17 <xichengc> which is the ungoing effort, and should be done soon. 01:07:31 <xichengc> I am iterating through the playbooks to assess all the necessary parameters that will have to come from compass. 01:08:08 <xichengc> after I have finished updating the etherpad, I will engage more with OSAD developers, with questions. 01:08:14 <shuoy> #action xichengc, try to reach out OSAD developer and see if they are willing to help out accelerate the OSAD understanding repos; and give OSAD developers the context and background of this engagement. 01:08:30 <chigang> xichengc: is it support HA controller? 01:08:53 <xichengc> it does, as well as active/active queue and galera mysql db HA 01:09:12 <chigang> well 01:09:27 <xichengc> #action xichengc: wrap up OSAD understanding process. 01:09:37 <xichengc> chigang 01:09:57 <xichengc> Has baiguoku got a chance to look at OSAD? 01:10:43 <baigk> a little 01:11:19 <xichengc> could you take some time to see if you can deploy a minimal environment using OSAD? 01:12:20 <chigang> what is mean of minial environment? Can you clear it more? In one baremetal? 01:12:38 <xichengc> all in one would be good enough 01:13:42 <shuoy> chigang/baigk: the high level idea is this: ‘if we can use OSAD solution as our Ansible playbook for the containerized components, then we are going to use OSAD as our target system driver’ — this is what OpenStack community would love to see: avoid duplicated work if possible 01:13:42 <baigk> OK, I will try 01:14:26 <shuoy> baigk: and the upside of doing this is that in the long run, OSAD become a solution plug-in for Compass. 01:14:43 <xichengc> #action baigk: try to deploy an openstack cluster onto one baremetal machine using OSAD solutions. 01:15:29 <shuoy> xichengc: please involve baigk at the right moment during conversation with OSAD team. 01:15:45 <xichengc> will do. 01:16:00 <xichengc> moving on? 01:16:11 <chigang> I think OSAD will be online deployment. 01:16:55 <chigang> #unod 01:16:58 <chigang> #undo 01:17:14 <chigang> sorry, I misunderstand 01:17:18 <shuoy> I would love to see the OPNFV requirement (which is basically some kind of spec) get translated into OSAD code — one stone two birds to maximize the OSAD code base usage. 01:17:27 <shuoy> Let’s move on the next topic. 01:17:40 <chigang> sure 01:17:58 <shuoy> #topic 2) Improved support of networking config 01:18:26 <shuoy> chigang, can you please explain the context and problem statement for this item? 01:19:20 <xuhan> now, al network is configured by os_installer 01:20:00 <xuhan> it's unable to support more complex networking 01:20:27 <shuoy> xuhan: so we would love to see network configuration “late binding”, is that the correct interpretation? 01:20:32 <xuhan> for example, we can not use one intf support two logic network 01:20:43 <xuhan> yes 01:20:44 <xichengc> #agreed 01:20:48 <xuhan> like bonding 01:20:54 <xuhan> vlan setting 01:21:15 <xuhan> ovs bridge prepare 01:21:48 <shuoy> xichangc, will this be a proper task for late stage configuration? (e.g., Ansible stage) 01:21:52 <xichengc> xuhan, so the networking config should be independent from any installers, in a global level> 01:22:19 <xuhan> yes 01:22:21 <xuhan> I has completed the preliminary implemention 01:22:21 <xuhan> install network is configured by the cobblerm, use DHCP 01:22:21 <xuhan> and other network(mgmt, storage, tenant, external) is configured by Ansible. 01:22:21 <xuhan> config file reference to FusionSphere's config file 01:22:57 <xichengc> shuoy, yes 01:23:26 <xichengc> OSAD should be able to do that as well. 01:24:05 <shuoy> xuhan: try to make sure our solution follow the OSAD framework — i.e., make the networking configuration part a relatively independent module so that OSAD community is more willing to accept it. 01:24:38 <shuoy> ok, any action item on this one? 01:25:56 <chigang> #action Xuhan try to contribute the network config in OSAD framework 01:26:07 <xuhan> OK, I'd like a general outline to begin with OSAD 01:26:35 <chigang> xuhan: shuoy: is it OK? 01:28:17 <shuoy> #action Xuhan co-ordinate with xichengc to reach out OSAD team regarding our motivation, and why this is valuable to OSAD (I suppose they may also want to achieve ’network configuration late binding’) 01:28:46 <shuoy> chigang: yes, this is great. Let’s move on to next topic. 01:29:03 <chigang> sure:) 01:29:26 <shuoy> #topic 3) Shall we prepare for "rule the stack" contest? 01:30:30 <shuoy> #info https://01.org/openstack/openstacksummitvancouverbc2015/rule-stack-vancouver is the context of this topic. 01:31:51 <chigang> Is it ongoing? 01:32:42 <shuoy> here is what I would suggest on this subject, let Compass developers in Shanghai read the ‘rule the stack’ document, may even engage Intel Shanghai OTG (opensource technology group) and see whether we can do this. 01:33:27 <shuoy> chigang, it is a kind of contest across openstack installers — to see which one is a robust and quick installer. 01:33:34 <xichengc> #info xicheng chang 01:33:53 <xichengc> Got disconnected, sorry 01:34:01 <shuoy> welcome back 01:34:43 <xichengc> Are we on the 3rd topic? 01:35:22 <shuoy> so let’s defer the decision of this (whether we want to participate that kind of contest) to the next IRC meeting 01:35:29 <chigang> shuoy: interesting! it is game in intallers. 01:35:30 <shuoy> yes, we are on the 3rd topic. 01:35:46 <shuoy> chigang: yes 01:36:05 <xichengc> preparing for this would require some time, I don't think we have a chance to win this contest 01:37:10 <shuoy> xichengc: I just said that we at least defer this decision to next IRC meeting. 01:37:31 <xichengc> Sure. Thanks, shuoy 01:38:35 <shuoy> chigang, for better community building-up, it does not hurt if you guys can engage Intel OTG in the Shanghai office. 01:39:56 <shuoy> Ok, I think we have already have all the topics discussed. Any thing that ppl in this meeting want to bring up? 01:40:16 <chigang> shuoy: do you know someone from OTG? 01:40:45 <shuoy> I will try to help you link with someone. 01:40:56 <chigang> shuoy: thanks 01:41:54 <shuoy> #action: shuoy to engages Intel developers and see if they are interested in Compass project 01:42:20 <xichengc> question: what did we conclude from the 2nd topic? 01:42:29 <xichengc> sorry i missed that part 01:43:07 <shuoy> 1) Xuhan co-ordinate with xichengc to reach out OSAD team regarding our motivation, and why this is valuable to OSAD (I suppose they may also want to achieve ’network configuration late binding’); 2) Xuhan try to contribute the network config in OSAD framework 01:43:55 <shuoy> no other topics? counting once… 01:44:14 <shuoy> no other topics? counting twice… 01:44:22 <xichengc> thanks 01:44:42 <shuoy> ok, thanks to everyone for the time. See you next time 01:44:54 <shuoy> #endmeeting