Re: [Openstack-operators] Tricircle

2017-07-11 Thread Ignazio Cassano 
We need either multicloud based in openstack or DR.
Ignazio

Il 11/Lug/2017 09:16 PM, "Curtis"  ha scritto:

> On Tue, Jul 11, 2017 at 1:13 PM, Curtis  wrote:
> > On Tue, Jul 11, 2017 at 12:43 PM, Ignazio Cassano
> >  wrote:
> >> Many thanks.
> >> As far as networking is concerned in a multipod environment, tricircle
> is
> >> the official project that openstack will support?
> >
> > It's one project. :)
> >
> > I believe there were also some sessions at the last summit regarding
> > "neutron multi site" in that the neutron project is looking at ways to
> > accomplish this as well. I didn't attend any, but if you google that
> > you'll probably find some etherpads.
> >
> > Potentially there would be solutions available via SDN controllers,
> > and each solution would be different.
> >
> >> 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.
> >
> > Yeah I'm not sure what has happened in that area either, but I'm
> > fairly sure that Ceph can backup to another Ceph cluster and it would
> > be interesting if OpenStack could somehow be made aware of that, but
> > of course you have all kinds of other issues in terms of IP migration
> > etc. I would imagine many people would suggest having applications
> > that can exist across multiple clouds as opposed to doing some kind of
> > "openstack aware disaster recovery" though. It would be superb if
> > there was an OpenStack way of managing that kind of
> > deployment...perhaps there is and I'm just not aware of it. :)
>
> Sorry, just to clarify, by "that kind of deployment" I mean
> multi-cloud applications not openstack aware disaster recovery. :)
>
> >
> > Thanks,
> > Curtis.
> >
> >> 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"  ha scritto:
> >>>
> >>> On Tue, Jul 11, 2017 at 10:47 AM, Ignazio Cassano
> >>>  wrote:
> >>> > I would like bothnetworking 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"  ha
> scritto:
> >>> >>
> >>> >> On Tue, Jul 11, 2017 at 9:54 AM, Ignazio Cassano
> >>> >>  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@lists.openstack.org
> >>> >> >
> >>> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack-operators
> >>> >> >
> >>> >>
> >>> >>
> >>> >>
> >>> >> --
> >>> >> Blog: serverascode.com
> >>>
> >>>
> >>>
> >>> --
> >>> Blog: serverascode.com
> >
> >
> >
> > --
> > Blog: serverascode.com
>
>
>
> --
> Blog: serverascode.com
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Tricircle

2017-07-11 Thread joehuang 
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 [ignaziocass...@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" 
<serverasc...@gmail.com<mailto:serverasc...@gmail.com>> ha scritto:
On Tue, Jul 11, 2017 at 10:47 AM, Ignazio Cassano
<ignaziocass...@gmail.com<mailto:ignaziocass...@gmail.com>> wrote:
> I would like bothnetworking 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" 
> <serverasc...@gmail.com<mailto:serverasc...@gmail.com>> ha scritto:
>>
>> On Tue, Jul 11, 2017 at 9:54 AM, Ignazio Cassano
>> <ignaziocass...@gmail.com<mailto:ignaziocass...@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@lists.openstack.org<mailto:OpenStack-operators@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>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Tricircle

2017-07-11 Thread Curtis 
On Tue, Jul 11, 2017 at 1:13 PM, Curtis  wrote:
> On Tue, Jul 11, 2017 at 12:43 PM, Ignazio Cassano
>  wrote:
>> Many thanks.
>> As far as networking is concerned in a multipod environment, tricircle is
>> the official project that openstack will support?
>
> It's one project. :)
>
> I believe there were also some sessions at the last summit regarding
> "neutron multi site" in that the neutron project is looking at ways to
> accomplish this as well. I didn't attend any, but if you google that
> you'll probably find some etherpads.
>
> Potentially there would be solutions available via SDN controllers,
> and each solution would be different.
>
>> 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.
>
> Yeah I'm not sure what has happened in that area either, but I'm
> fairly sure that Ceph can backup to another Ceph cluster and it would
> be interesting if OpenStack could somehow be made aware of that, but
> of course you have all kinds of other issues in terms of IP migration
> etc. I would imagine many people would suggest having applications
> that can exist across multiple clouds as opposed to doing some kind of
> "openstack aware disaster recovery" though. It would be superb if
> there was an OpenStack way of managing that kind of
> deployment...perhaps there is and I'm just not aware of it. :)

Sorry, just to clarify, by "that kind of deployment" I mean
multi-cloud applications not openstack aware disaster recovery. :)

>
> Thanks,
> Curtis.
>
>> 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"  ha scritto:
>>>
>>> On Tue, Jul 11, 2017 at 10:47 AM, Ignazio Cassano
>>>  wrote:
>>> > I would like bothnetworking 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"  ha scritto:
>>> >>
>>> >> On Tue, Jul 11, 2017 at 9:54 AM, Ignazio Cassano
>>> >>  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@lists.openstack.org
>>> >> >
>>> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Blog: serverascode.com
>>>
>>>
>>>
>>> --
>>> Blog: serverascode.com
>
>
>
> --
> Blog: serverascode.com



-- 
Blog: serverascode.com

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Tricircle

2017-07-11 Thread Curtis 
On Tue, Jul 11, 2017 at 12:43 PM, Ignazio Cassano
 wrote:
> Many thanks.
> As far as networking is concerned in a multipod environment, tricircle is
> the official project that openstack will support?

It's one project. :)

I believe there were also some sessions at the last summit regarding
"neutron multi site" in that the neutron project is looking at ways to
accomplish this as well. I didn't attend any, but if you google that
you'll probably find some etherpads.

Potentially there would be solutions available via SDN controllers,
and each solution would be different.

> 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.

Yeah I'm not sure what has happened in that area either, but I'm
fairly sure that Ceph can backup to another Ceph cluster and it would
be interesting if OpenStack could somehow be made aware of that, but
of course you have all kinds of other issues in terms of IP migration
etc. I would imagine many people would suggest having applications
that can exist across multiple clouds as opposed to doing some kind of
"openstack aware disaster recovery" though. It would be superb if
there was an OpenStack way of managing that kind of
deployment...perhaps there is and I'm just not aware of it. :)

Thanks,
Curtis.

> 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"  ha scritto:
>>
>> On Tue, Jul 11, 2017 at 10:47 AM, Ignazio Cassano
>>  wrote:
>> > I would like bothnetworking 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"  ha scritto:
>> >>
>> >> On Tue, Jul 11, 2017 at 9:54 AM, Ignazio Cassano
>> >>  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@lists.openstack.org
>> >> >
>> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Blog: serverascode.com
>>
>>
>>
>> --
>> Blog: serverascode.com



-- 
Blog: serverascode.com

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Tricircle

2017-07-11 Thread John van Ommen 
My team at HPE did a few projects like that:

https://saas.hpe.com/en-us/software/cloud-service-automation

I believe BMC also offers products in that space, but you'd have to contact
them to find out what they're capable of.

For the past year, most customers I've talked to have been leaning towards
container solutions. IE, instead of buying a product that can provision
resources in two disparate clouds, they're deploying containers and using a
container orchestration product to bridge the environments. (Figuratively,
not literally.)

Hybrid cloud is not a trivial endeavor.

John



On Tue, Jul 11, 2017 at 11:10 AM, Curtis  wrote:

> On Tue, Jul 11, 2017 at 10:47 AM, Ignazio Cassano
>  wrote:
> > I would like bothnetworking 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"  ha scritto:
> >>
> >> On Tue, Jul 11, 2017 at 9:54 AM, Ignazio Cassano
> >>  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@lists.openstack.org
> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack-operators
> >> >
> >>
> >>
> >>
> >> --
> >> Blog: serverascode.com
>
>
>
> --
> Blog: serverascode.com
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Tricircle

2017-07-11 Thread Curtis 
On Tue, Jul 11, 2017 at 10:47 AM, Ignazio Cassano
 wrote:
> I would like bothnetworking 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"  ha scritto:
>>
>> On Tue, Jul 11, 2017 at 9:54 AM, Ignazio Cassano
>>  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@lists.openstack.org
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>> >
>>
>>
>>
>> --
>> Blog: serverascode.com



-- 
Blog: serverascode.com

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Tricircle

2017-07-11 Thread Curtis 
On Tue, Jul 11, 2017 at 9:54 AM, Ignazio Cassano
 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@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>



-- 
Blog: serverascode.com

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators