Re: [openstack-dev] [Tricircle] Using the reserved keywords reserved as field name
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 <joehu...@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...@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: > shin...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Email: shin...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Tricircle] Using the reserved keywords reserved as field name
Thanks Shinobu, I quite like the gRPC idea and we could continue to discuss and work on it :) On Sat, Mar 26, 2016 at 11:38 PM, Shinobu Kinjo <shinobu...@gmail.com> wrote: > Hi Zhipeng, > > I've not elaborate on gRPC in detail at all. > > What I meant about one of possibilities is that, since gRPC was > designed for fully distributed computing system, the features of this > framework would be available in any kind of distributed computing > system potentially. > Of course it may be necessary to build a new feature of infrastructure > to make use of it, which is quite challenge and would cause a big > change on some layer. But since the OpenStack wouldn't stop growing > because of demands by end-users (I guess), it's worth thinking of that > features for our future. > > Cheers, > Shinobu > > > On Sat, Mar 26, 2016 at 9:48 PM, Zhipeng Huang <zhipengh...@gmail.com> > wrote: > > Great:) Do you have any more thoughts on that ? > > > > It might need both Tricircle and bottom OpenStack entity to deploy gRPC > > server and client, while it is ok for Tricircle, it is not easy to > mandate > > gRPC endpoints as part of official OpenStack functionality. > > > > The whole point about Tricircle is to ensure Users could manage multiple > > cloud via normal OpenStack API. > > > > Or shall we only use gRPC endpoints internally in Tricircle ? That is to > say > > to use it between gateways and Xjobs > > > > On Sat, Mar 26, 2016 at 8:11 PM, Shinobu Kinjo <shinobu...@gmail.com> > wrote: > >> > >> Yes, that's one of possibilities. > >> > >> Cheers, > >> Shinobu > >> > >> On Sat, Mar 26, 2016 at 8:55 PM, Zhipeng Huang <zhipengh...@gmail.com> > >> wrote: > >> > any possible that we use gRPC for Tricircle ? > >> > > >> > On Sat, Mar 26, 2016 at 6:11 PM, Shinobu Kinjo <shinobu...@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 <joehu...@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...@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 > >&
Re: [openstack-dev] [Tricircle] Using the reserved keywords reserved as field name
Hi Zhipeng, I've not elaborate on gRPC in detail at all. What I meant about one of possibilities is that, since gRPC was designed for fully distributed computing system, the features of this framework would be available in any kind of distributed computing system potentially. Of course it may be necessary to build a new feature of infrastructure to make use of it, which is quite challenge and would cause a big change on some layer. But since the OpenStack wouldn't stop growing because of demands by end-users (I guess), it's worth thinking of that features for our future. Cheers, Shinobu On Sat, Mar 26, 2016 at 9:48 PM, Zhipeng Huang <zhipengh...@gmail.com> wrote: > Great:) Do you have any more thoughts on that ? > > It might need both Tricircle and bottom OpenStack entity to deploy gRPC > server and client, while it is ok for Tricircle, it is not easy to mandate > gRPC endpoints as part of official OpenStack functionality. > > The whole point about Tricircle is to ensure Users could manage multiple > cloud via normal OpenStack API. > > Or shall we only use gRPC endpoints internally in Tricircle ? That is to say > to use it between gateways and Xjobs > > On Sat, Mar 26, 2016 at 8:11 PM, Shinobu Kinjo <shinobu...@gmail.com> wrote: >> >> Yes, that's one of possibilities. >> >> Cheers, >> Shinobu >> >> On Sat, Mar 26, 2016 at 8:55 PM, Zhipeng Huang <zhipengh...@gmail.com> >> wrote: >> > any possible that we use gRPC for Tricircle ? >> > >> > On Sat, Mar 26, 2016 at 6:11 PM, Shinobu Kinjo <shinobu...@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 <joehu...@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...@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: >> >> > shin...@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-requ...@lists.openstack.org?subject:unsubscribe >> >> > http://lists.openstack.org/cgi-bin/mailma
Re: [openstack-dev] [Tricircle] Using the reserved keywords reserved as field name
Great:) Do you have any more thoughts on that ? It might need both Tricircle and bottom OpenStack entity to deploy gRPC server and client, while it is ok for Tricircle, it is not easy to mandate gRPC endpoints as part of official OpenStack functionality. The whole point about Tricircle is to ensure Users could manage multiple cloud via normal OpenStack API. Or shall we only use gRPC endpoints internally in Tricircle ? That is to say to use it between gateways and Xjobs On Sat, Mar 26, 2016 at 8:11 PM, Shinobu Kinjo <shinobu...@gmail.com> wrote: > Yes, that's one of possibilities. > > Cheers, > Shinobu > > On Sat, Mar 26, 2016 at 8:55 PM, Zhipeng Huang <zhipengh...@gmail.com> > wrote: > > any possible that we use gRPC for Tricircle ? > > > > On Sat, Mar 26, 2016 at 6:11 PM, Shinobu Kinjo <shinobu...@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 <joehu...@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...@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: > >> > shin...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe > >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >> > >> > >> > >> -- > >> Email: > >> shin...@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-requ...@lists.openstack.org?subject:unsubscribe > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > > > > > -- > &
Re: [openstack-dev] [Tricircle] Using the reserved keywords reserved as field name
Yes, that's one of possibilities. Cheers, Shinobu On Sat, Mar 26, 2016 at 8:55 PM, Zhipeng Huang <zhipengh...@gmail.com> wrote: > any possible that we use gRPC for Tricircle ? > > On Sat, Mar 26, 2016 at 6:11 PM, Shinobu Kinjo <shinobu...@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 <joehu...@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...@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: >> > shin...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> >> -- >> Email: >> shin...@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-requ...@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: huangzhip...@huawei.com > Office: Huawei Industrial Base, Longgang, Shenzhen > > (Previous) > Research Assistant > Mobile Ad-Hoc Network Lab, Calit2 > University of California, Irvine > Email: zhipe...@uci.edu > Office: Calit2 Building Room 2402 > > OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Email: shin...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Tricircle] Using the reserved keywords reserved as field name
any possible that we use gRPC for Tricircle ? On Sat, Mar 26, 2016 at 6:11 PM, Shinobu Kinjo <shinobu...@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 <joehu...@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...@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: > > shin...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > -- > Email: > shin...@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-requ...@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: huangzhip...@huawei.com Office: Huawei Industrial Base, Longgang, Shenzhen (Previous) Research Assistant Mobile Ad-Hoc Network Lab, Calit2 University of California, Irvine Email: zhipe...@uci.edu Office: Calit2 Building Room 2402 OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Tricircle] Using the reserved keywords reserved as field name
Hi Vega, Thank you for your quick action. Cheers, Shinobu On Sat, Mar 26, 2016 at 6:39 PM, Vega Cai <luckyveg...@gmail.com> wrote: > Added a work item in phase 4 in our todo list: > > https://etherpad.openstack.org/p/TricircleToDo > > On 26 March 2016 at 17:31, joehuang <joehu...@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...@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: >> shin...@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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Email: shin...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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 <joehu...@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...@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: > shin...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Email: shin...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Tricircle] Using the reserved keywords reserved as field name
Added a work item in phase 4 in our todo list: https://etherpad.openstack.org/p/TricircleToDo On 26 March 2016 at 17:31, joehuang <joehu...@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...@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: > shin...@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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Tricircle] Using the reserved keywords reserved as field name
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...@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: shin...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Tricircle] Using the reserved keywords reserved as field name
Yes, It would be better to avoid the field name duplicated with DB key words. These tables are ported from Nova and Neutron, it would be good to change the field name. Best Regards Chaoyi Huang ( Joe Huang ) -Original Message- From: Shinobu Kinjo [mailto:shinobu...@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: shin...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[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: shin...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
