Open Stack

On 01/21/2018 07:08 PM, joehuang wrote:
> Hello, Monty,
> 
> Tricircle did not develop any extra Neutron network resources, Tricircle provide plugins under Neutron, and same support resources as Neutron have. To ease the management of multiple Neutron servers, one Tricircle Admin API is provided to manage the resource routings between local neutron(s) and central neutron, it's one standalone service, and only for cloud administrator, therefore python-tricircleclient adn CLI were developed to support these administration functions.
> 
> do you mean to put  Tricircle Admin API sdk under openstacksdk tree?

Yes - if you want to, you are welcome to put them there.

> Best Regards
> Chaoyi Huang (joehuang)
> 
> ________________________________________
> From: Monty Taylor [mordred at inaugust.com]
> Sent: 21 January 2018 1:22
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [sdk][masakari][tricircle] Inclusion of SDK classes in openstacksdk tree
> 
> Hey everybody,
> 
> Wanted to send a quick note to let people know that all OpenStack
> services are more than welcome to put any openstacksdk proxy and
> resource classes they have directly into the openstacksdk tree.
> 
> Looking through codesearch.openstack.org, masakariclient and tricircle
> each have SDK-related classes in their trees.
> 
> You don't HAVE to put the code into openstacksdk. In fact, I wrote a
> patch for masakariclient to register the classes with
> openstack.connection.Connection:
> 
> https://review.openstack.org/#/c/534883/
> 
> But I wanted to be clear that the code is **welcome** directly in tree,
> and that anyone working on an OpenStack service is welcome to put
> support code directly in the openstacksdk tree.
> 
> Monty
> 
> PS. Joe - you've also got some classes in the tricircle test suite
> extending the network service. I haven't followed all the things ... are
> the tricircle network extensions done as neutron plugins now? (It looks
> like they are) If so, why don't we figure out getting your network
> resources in-tree as well.
> 
> __________________________________________________________________________
> 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
> 
> __________________________________________________________________________
> 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
>