Open Stack

On Tue, Jul 11, 2017 at 1:13 PM, Curtis <serverascode at gmail.com> wrote:
> On Tue, Jul 11, 2017 at 12:43 PM, Ignazio Cassano
> <ignaziocassano at gmail.com> 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" <serverascode at gmail.com> ha scritto:
>>>
>>> On Tue, Jul 11, 2017 at 10:47 AM, Ignazio Cassano
>>> <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> ha scritto:
>>> >>
>>> >> On Tue, Jul 11, 2017 at 9:54 AM, Ignazio Cassano
>>> >> <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
>>> >> >
>>> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Blog: serverascode.com
>>>
>>>
>>>
>>> --
>>> Blog: serverascode.com
>
>
>
> --
> Blog: serverascode.com



-- 
Blog: serverascode.com