[openstack-dev] [Tricircle] Using the reserved keywords reserved as field name
Shinobu Kinjo
shinobu.kj at gmail.com
Sat Mar 26 12:11:37 UTC 2016
Yes, that's one of possibilities.
Cheers,
Shinobu
On Sat, Mar 26, 2016 at 8:55 PM, Zhipeng Huang <zhipengh512 at gmail.com> wrote:
> any possible that we use gRPC for Tricircle ?
>
> On Sat, Mar 26, 2016 at 6:11 PM, Shinobu Kinjo <shinobu.kj at gmail.com> wrote:
>>
>> 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
>
>
>
>
> --
> Zhipeng (Howard) Huang
>
> Standard Engineer
> IT Standard & Patent/IT Prooduct Line
> Huawei Technologies Co,. Ltd
> Email: huangzhipeng at huawei.com
> Office: Huawei Industrial Base, Longgang, Shenzhen
>
> (Previous)
> Research Assistant
> Mobile Ad-Hoc Network Lab, Calit2
> University of California, Irvine
> Email: zhipengh at uci.edu
> Office: Calit2 Building Room 2402
>
> OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
>
> __________________________________________________________________________
> 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
More information about the OpenStack-dev
mailing list