[Openstack-operators] Tricircle

joehuang joehuang at huawei.com
Wed Jul 12 00:26:00 UTC 2017


Hello, Ignazio and Curtis,

A stretched cluster is a better viable solution for connected pods. Not only happened in OPNFV(telecom area), but also happened in real production in AWS: I just wrote one blog to compare the solution in Tricircle+OpenStack and AWS "Doing better, "Moving Mission Critical Apps from One Region to Multi-Region" https://www.linkedin.com/pulse/moving-mission-critical-apps-from-one-region-joe-huang

In short, both vIMS and PlayStation store make the backend db Cassandra cluster stretched into multi-region with the networking capability, and then support the application running in multi-region with multi-master (active-active) mode, to achieve high availability across multi-region(multi-cloud).


Best Regards
Chaoyi Huang (joehuang)
________________________________
From: Ignazio Cassano [ignaziocassano at gmail.com]
Sent: 12 July 2017 2:43
To: Curtis
Cc: OpenStack Operators
Subject: Re: [Openstack-operators] Tricircle

Many thanks.
As far as networking is concerned in a multipod environment, tricircle is the official project that openstack will support?
Cinder,  for example, is another element to consider: ceph or other storage replication solutions are
not enough for moving instance from a pod to another because they have their own cinder db.
Probably in this case we should export the volume from a pod and import to another ....this could get a long time.
Heat stack is more than e single vm and it could require an important effort for moving.
Stretched cluster coulb be a solution in case of well connected pods ?
Regards
Ignazio


Il 11/Lug/2017 08:10 PM, "Curtis" <serverascode at gmail.com<mailto:serverascode at gmail.com>> ha scritto:
On Tue, Jul 11, 2017 at 10:47 AM, Ignazio Cassano
<ignaziocassano at gmail.com<mailto:ignaziocassano at gmail.com>> wrote:
> I would like both....networking is important but an heat multi pod
> Orchestrator could be fantastic.

So like a higher level system that can manage multiple clouds via
their heat API?

I'm only familiar with some work in the NFV area around MANO
(management and orchestration). There are several systems that can
manage multiple clouds, some using heat and others using the standard
APIs. One OpenStack related example would be the Tacker system.

I think a higher level heat system that could manage other heat
systems would be interesting. I see some mention of heat multicloud
but I'm not sure where that ended up. I should look into that...

Thanks,
Curtis.


> Regards
> Ignazio
>
> Il 11/Lug/2017 06:20 PM, "Curtis" <serverascode at gmail.com<mailto:serverascode at gmail.com>> ha scritto:
>>
>> On Tue, Jul 11, 2017 at 9:54 AM, Ignazio Cassano
>> <ignaziocassano at gmail.com<mailto:ignaziocassano at gmail.com>> wrote:
>> > Hi openstackers,
>> > anyone is using tricircle in production environment?
>> > Any alternative for e multi pod openstack like tricircle?
>>
>> What is it you want to do?
>>
>> AFAIK tricircle has pivoted recently to accomplish networking across
>> multi-region openstack deployments.
>>
>> Are you mostly looking for networking across clouds or are you looking
>> to tie a bunch of clouds together with some higher level abstraction?
>> Or both. :)
>>
>> Thanks,
>> Curtis.
>>
>> > Regards
>> > Ignazio
>> >
>> >
>> > _______________________________________________
>> > OpenStack-operators mailing list
>> > OpenStack-operators at lists.openstack.org<mailto:OpenStack-operators at lists.openstack.org>
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>> >
>>
>>
>>
>> --
>> Blog: serverascode.com<http://serverascode.com>



--
Blog: serverascode.com<http://serverascode.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20170712/cfd69726/attachment.html>


More information about the OpenStack-operators mailing list