<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle">P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body fPStyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">
<p>Hi, Iben,</p>
<p> </p>
<p>You are correct, Tricircle mainly focuses on use of APIs of OpenStack services, for example, all APIs pass the DefCore test, so that different infrastructure (like different hypervisor, different SDN controller, etc) in underclouds can work together in multisite
cloud. </p>
<p> </p>
<p>Tricircle is a PoC project ( to verify idea ) in the past, unfortunately IPv6 not tried in the PoC. We can do that after tricircle begins to run in open source /open community way. I also assume that's why Zhipeng start the polling for weekly meeting,
to build the community to work together on the tricircle from scratch, with a PoC as reference.</p>
<p> </p>
<p>Best regards</p>
<p>Chaoyi Huang ( joehuang )</p>
<p> </p>
<p></p>
<hr tabindex="-1">
<p></p>
<div style="FONT-FAMILY: Times New Roman; COLOR: #000000; FONT-SIZE: 16px">
<div style="DIRECTION: ltr" id="divRpF889220"><font color="#000000" size="2" face="Tahoma"><b>From:</b> opnfv-tech-discuss-bounces@lists.opnfv.org [opnfv-tech-discuss-bounces@lists.opnfv.org] on behalf of Rodriguez, Iben [Iben.Rodriguez@spirent.com]<br>
<b>Sent:</b> 05 June 2015 23:03<br>
<b>To:</b> zhipengh512@gmail.com; openstack-dev@lists.openstack.org<br>
<b>Cc:</b> opnfv-tech-discuss@lists.opnfv.org<br>
<b>Subject:</b> Re: [opnfv-tech-discuss] [openstack-dev][Tricircle] Polling for weekly team meeting<br>
</font><br>
</div>
<div></div>
<div>
<p dir="ltr">Hello Joe,</p>
<p dir="ltr">This is very cool. A few questions...</p>
<p dir="ltr">Tricircle seems to deal mostly with the use of many environments and not their setup or configuration, is that right?</p>
<p dir="ltr">We have a few multi-site projects already like pharos and IPv6. Can we make an assessment to understand where each one fits in the workflow of the platform lifecycle?</p>
<p dir="ltr">Do the underclouds need to be similar for tricycle to function properly? What if some openstack are different from others? Are we just looking for api compatability or will certain features or functions also be needed?</p>
<p dir="ltr">Many thanks for sharing this project. It is good to understand the concepts.
<br>
</p>
<p dir="ltr">I b e n<br>
4087824726<br>
</p>
<blockquote type="cite">
<p dir="ltr">From: Zhipeng Huang<br>
Sent: Friday, June 5, 07:44<br>
Subject: [opnfv-tech-discuss] [openstack-dev][Tricircle] Polling for weeklyteam meeting<br>
To: OpenStack Development Mailing List (not for usage questions)<br>
Cc: opnfv-tech-discuss@lists.opnfv.org<br>
</p>
<p dir="ltr">Hi All, <br>
</p>
<p dir="ltr">The Tricircle Project has been on stackforge for a while, and without much activities.
<br>
</p>
<p dir="ltr">Now we will completely restructure the code base to make it more community open source friendly, less corporate PoC looking hopefully :P
<br>
</p>
<p dir="ltr">At the mean time I want to call for attention for people who are interested in this project, to participate in a time poll for our weekly meeting:
<br>
</p>
<p dir="ltr"><a href="http://doodle.com/d7fvmgvrwv8y3bqv" target="_blank">http://doodle.com/d7fvmgvrwv8y3bqv</a>
<br>
</p>
<p dir="ltr">I would recommend UTC 13:00 coz it is the only few time period when all the continent are able to be awake (tougher on US tho).
<br>
</p>
<p dir="ltr">Please find more info on Tricircle at <a href="https://github.com/stackforge/tricircle" target="_blank">
https://github.com/stackforge/tricircle</a> (new code base would come in the next few weeks). It mainly aim to solve OpenStack deployment acorss multiple sites.
<br>
</p>
<p dir="ltr">Also depending on OPNFV Multisite Project's decision, Tricircle might be one of the upstream projects of Multisite, which aims at developing requirements for NFV multi-NFVI-PoPs VIM deployment. More info :
<a href="https://wiki.opnfv.org/multisite" target="_blank">https://wiki.opnfv.org/multisite</a>
<a href="https://www.opnfv.org/arno" target="_blank">https://www.opnfv.org/arno</a>
</p>
<p dir="ltr">-- </p>
<p dir="ltr">Zhipeng (Howard) Huang <br>
</p>
<p dir="ltr">Standard Engineer </p>
<p dir="ltr">IT Standard & Patent/IT Prooduct Line </p>
<p dir="ltr">Huawei Technologies Co,. Ltd </p>
<p dir="ltr">Email: <a href="mailto:huangzhipeng@huawei.com" target="_blank">huangzhipeng@huawei.com</a>
</p>
<p dir="ltr">Office: Huawei Industrial Base, Longgang, Shenzhen <br>
</p>
<p dir="ltr">(Previous) </p>
<p dir="ltr">Research Assistant </p>
<p dir="ltr">Mobile Ad-Hoc Network Lab, Calit2 </p>
<p dir="ltr">University of California, Irvine </p>
<p dir="ltr">Email: <a href="mailto:zhipengh@uci.edu" target="_blank">zhipengh@uci.edu</a>
</p>
<p dir="ltr">Office: Calit2 Building Room 2402 <br>
</p>
<p dir="ltr">OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado <br>
<br>
</p>
</blockquote>
<div><font size="1">Spirent Communications e-mail confidentiality.<br>
------------------------------------------------------------------------<br>
This e-mail contains confidential and / or privileged information belonging to Spirent Communications plc, its affiliates and / or subsidiaries. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution and /
or the taking of any action based upon reliance on the contents of this transmission is strictly forbidden. If you have received this message in error please notify the sender by return e-mail and delete it from your system.<br>
<br>
Spirent Communications plc<br>
Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.<br>
Tel No. +44 (0) 1293 767676<br>
Fax No. +44 (0) 1293 767677<br>
<br>
Registered in England Number 470893<br>
Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.<br>
<br>
Or if within the US, <br>
<br>
Spirent Communications,<br>
27349 Agoura Road, Calabasas, CA, 91301, USA.<br>
Tel No. 1-818-676- 2300 <br>
</font></div>
</div>
</div>
</div>
</body>
</html>