[openstack-dev] [Tacker][Tricircle]Multi-VIM collaboration
joehuang
joehuang at huawei.com
Fri Dec 11 07:04:45 UTC 2015
Hi, Sridhar,
Great to know that Tacker also begins to address multi-VIM ( multi-OpenStack ) requirement in OPNFV cloud, and your concerns on OPNFV multisite and OpenStack Tricircle project.
I just gave some comment on the spec. And I think the most important one for Tacker integration with Tricircle is the VNF placement policy, it would be great to use region_id( in OpenStack, region is identified with region_name) + Availability Zone for VNF placement.
Such a placement policy will work in every scenario: Tacker + multi-region OpenStack, Tacker+Amazon, Tacker +Tricircle (+multi OpenStack), Tacker + multi-region OpenStack +Tricircle (+multi OpenStack). For Tricircle will integrate multi-OpenStack into one region, and each bottom OpenStack will work like one availability zone, Tacker can treat Tricircle as one OpenStack region.
It’s quite important for VNFs(the telecom application) to be deployed into multiple availability zones to achieve five 9 carrier grade reliability over the four 9 reliability of OpenStack.
Best Regards
Chaoyi Huang ( Joe Huang )
From: Sridhar Ramaswamy [mailto:srics.r at gmail.com]
Sent: Thursday, December 10, 2015 10:25 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: caizhiyuan (A)
Subject: Re: [openstack-dev] [Tacker][Tricircle]Multi-VIM collaboration
Sure.
As mentioned in the BP we stumbled into Tricycle project while researching for this feature (and hence got mentioned in the BP). It sure looks promising. The immediate asks from our user community is quite modest though, so we are trying to keep the scope small. However the integration point you mention make sense, so that Tacker + Tricircle could be one of the deployment option. Lets continue the discussion in the gerrit as we put all other suggestions coming in (like heat multi-cloud / multi-region) in perspective. It will be great to get the Tacker multi-site API bake in different multi-site deployment patterns underneath.
- Sridhar
On Tue, Dec 8, 2015 at 10:37 PM, Zhipeng Huang <zhipengh512 at gmail.com<mailto:zhipengh512 at gmail.com>> wrote:
Hi Tacker team,
As I commented in the BP[1], our team is interested in a collaboration in this area. I think one of the collaboration point would be to define a mapping between tacker multi-vim api with Tricircle resource routing api table [2].
[1]https://review.openstack.org/#/c/249085/
[2]https://docs.google.com/document/d/18kZZ1snMOCD9IQvUKI5NVDzSASpw-QKj7l2zNqMEd3g/edit#heading=h.5t71ara040n5
--
Zhipeng (Howard) Huang
Standard Engineer
IT Standard & Patent/IT Prooduct Line
Huawei Technologies Co,. Ltd
Email: huangzhipeng at huawei.com<mailto:huangzhipeng at huawei.com>
Office: Huawei Industrial Base, Longgang, Shenzhen
(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipengh at uci.edu<mailto:zhipengh at uci.edu>
Office: Calit2 Building Room 2402
OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151211/2913e5a6/attachment.html>
More information about the OpenStack-dev
mailing list