On 12 May 2017 at 11:47, Morales, Victor <[email protected]> wrote:

> Armando,
>
>
>
> I noticed that Tricircle is mentioned there.  Shouldn’t be better to
> extend its current functionality or what are the things that are missing
> there?
>

Tricircle aims at coordinating independent neutron systems that exist in
separated openstack deployments. Making Neutron cell-aware will work in the
context of the same openstack deployment.


>
>
> Regards,
>
> Victor Morales
>
>
>
> *From: *"Armando M." <[email protected]>
> *Reply-To: *"OpenStack Development Mailing List (not for usage
> questions)" <[email protected]>
> *Date: *Friday, May 12, 2017 at 1:06 PM
> *To: *"OpenStack Development Mailing List (not for usage questions)" <
> [email protected]>
> *Subject: *[openstack-dev] [neutron] multi-site forum discussion
>
>
>
> Hi folks,
>
>
>
> At the summit we had a discussion on how to deploy a single neutron system
> across multiple geographical sites [1]. You can find notes of the
> discussion on [2].
>
>
>
> One key requirement that came from the discussion was to make Neutron more
> Nova cells friendly. I filed an RFE bug [3] so that we can move this
> forward on Lauchpad.
>
>
>
> Please, do provide feedback in case I omitted some other key takeaway.
>
>
>
> Thanks,
>
> Armando
>
>
>
> [1] https://www.openstack.org/summit/boston-2017/summit-
> schedule/events/18757/neutron-multi-site
>
> [2] https://etherpad.openstack.org/p/pike-neutron-multi-site
>
> [3] https://bugs.launchpad.net/neutron/+bug/1690425
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: [email protected]?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to