Open Stack

Hi,  Shinobu,

RPC bottlenect will be mostly in bottom
 openstack, ie, current openstack, there quite lot rpc messages(and frequence) a better RPC protocol is definitely great
 help.

In each openstack summit, there are
 some topics about message bus
 performance tunning :)

currently in Tricircle only one rpc message for configuring the cross
 openstack L3 bridging network. There
 will be very few and not frequent RPC
 message in Tricircle even in the future, these async tasks
 mainly for better user experience so that
 the response to end user as fast as
 possible.

Sent from HUAWEI AnyOffice
发件人：shinobu.kj
收件人：openstack-dev,
时间：2016-03-26 18:13:11
主题:Re: [openstack-dev] [Tricircle] Using the reserved keywords reserved as field name

Hi Chaoyi,

Thank you for the pointer.
I'm also researching privately how we can improve RPC protocol
reasonably like HTTP2.
It's quite easy to foreseen that it would be bottleneck, and be able
not to realize what the Tricircle is trying to do.
Honestly it's already bottleneck.

Cheers,
Shinobu

On Sat, Mar 26, 2016 at 6:31 PM, joehuang <joehuang at huawei.com> wrote:
> Hi, Shinobu,
>
> This BP is a good entrance for Tricircle source code, this BP listed the all basic patches building Tricircle from scratches.
>
> https://blueprints.launchpad.net/tricircle/+spec/implement-stateless
>
> Best Regards
> Chaoyi Huang ( Joe Huang )
>
>
> -----Original Message-----
> From: Shinobu Kinjo [mailto:shinobu.kj at gmail.com]
> Sent: Saturday, March 26, 2016 2:39 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [Tricircle] Using the reserved keywords reserved as field name
>
> Hi Team,
>
> In the Tricircle database, there are three tables having a field name which the MySQL (MariaDB) has as one of the reserved keywords. [1]
>
>  Table Name:
>   aggregate_metadata
>   instance_type_extra_specs
>   quality_of_service_specs
>
>  Field Name:
>   key
>
> I think it would not be best practice to use any reserved word by the any system because it could cause bug once the component is bigger.
>
> What do you think?
>
> [1] http://dev.mysql.com/doc/refman/5.0/en/keywords.html
>
> Cheers,
> Shinobu
>
> --
> Email:
> shinobu at linux.com
> GitHub:
> shinobu-x
> Blog:
> Life with Distributed Computational System based on OpenSource
>
> __________________________________________________________________________
> 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



--
Email:
shinobu at linux.com
GitHub:
shinobu-x
Blog:
Life with Distributed Computational System based on OpenSource

__________________________________________________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160327/6b572b1f/attachment.html>