Open Stack

If you're going with the approach of having a master region (which seems
sensible), you're going to want an admin API that checks all of the regions
setup matches in terms of these objects existing in all regions, for
validation.

On 31 August 2016 at 10:16, joehuang <joehuang at huawei.com> wrote:

> Hello, team,
>
> During last weekly meeting, we discussed how to address TCs concerns in
> Tricircle big-tent application. After the weekly meeting, the proposal was
> co-prepared by our contributors: https://docs.google.com/presentation/d/
> 1kpVo5rsL6p_rq9TvkuczjommJSsisDiKJiurbhaQg7E
>
> The more doable way is to divide Tricircle into two independent and
> decoupled projects, only one of the projects which deal with networking
> automation will try to become an big-tent project, And Nova/Cinder API-GW
> will be removed from the scope of big-tent project application, and put
> them into another project:
>
> *TricircleNetworking:* Dedicated for cross Neutron networking automation
> in multi-region OpenStack deployment, run without or with TricircleGateway.
> Try to become big-tent project in the current application of
> https://review.openstack.org/#/c/338796/.
>
>
> *TricircleGateway:* Dedicated to provide API gateway for those who need
> single Nova/Cinder API endpoint in multi-region OpenStack deployment, run
> without or with TricircleNetworking. Live as non-big-tent,
> non-offical-openstack project, just like Tricircle toady’s status. And not
> pursue big-tent only if the consensus can be achieved in OpenStack
> community, including Arch WG and TCs, then decide how to get it on board in
> OpenStack. A new repository is needed to be applied for this project.
>
> And consider to remove some overlapping implementation in Nova/Cinder
> API-GW for global objects like flavor, volume type, we can configure one
> region as master region, all global objects like flavor, volume type,
> server group, etc will be managed in the master Nova/Cinder service. In
> Nova API-GW/Cinder API-GW, all requests for these global objects will be
> forwarded to the master Nova/Cinder, then to get rid of any API
> overlapping-implementation.
>
> More information, you can refer to the proposal draft
> https://docs.google.com/presentation/d/1kpVo5rsL6p_
> rq9TvkuczjommJSsisDiKJiurbhaQg7E,
> your thoughts are welcome, and let's have more discussion in this weekly
> meeting.
>
> Best Regards
> Chaoyi Huang(joehuang)
>
> *From:* joehuang
> *Sent:* 24 August 2016 16:35
> *To:* openstack-dev
> *Subject:* [openstack-dev][tricircle]agenda of weekly meeting Aug.24
>
> Hello, team,
>
>
>
> Agenda of Aug.24 weekly meeting:
>
>
> # progress review and concerns on the features like micro versions, policy
> control, dynamic pod binding, cross pod L2 networking
>
> # How to address TCs concerns in Tricircle big-tent application
>
> # open discussion
>
>
>
> How to join:
>
>
>
> #  IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting
> on every Wednesday starting from UTC 13:00.
>
>
>
> If you  have other topics to be discussed in the weekly meeting, please
> reply the mail.
>
>
>
> Best Regards
>
> Chaoyi Huang ( joehuang )
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
-- 
Duncan Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160831/2287675e/attachment.html>