Re: [openstack-dev] [keystone]Why not common definition about normal HTTP status code like 2xx and 3xx?

2015-06-03 Thread Neo Liu
On Thu, Jun 4, 2015 at 4:43 AM Brant Knudson wrote: > > > On Tue, Jun 2, 2015 at 4:32 AM, Chenhong Liu > wrote: > >> There is keystone/exception.py which contains Exceptions defined and used >> inside keystone provide 4xx and 5xx status code. And we can use it like: >> exception.Forbidden.co

Re: [openstack-dev] [keystone]Why not common definition about normal HTTP status code like 2xx and 3xx?

2015-06-03 Thread Brant Knudson
On Tue, Jun 2, 2015 at 4:32 AM, Chenhong Liu wrote: > There is keystone/exception.py which contains Exceptions defined and used > inside keystone provide 4xx and 5xx status code. And we can use it like: > exception.Forbidden.code, exception.forbiddent.title > exception.NotFound.code, exce

Re: [openstack-dev] [keystone]Why not common definition about normal HTTP status code like 2xx and 3xx?

2015-06-02 Thread Ian Cordasco
On 6/2/15, 04:45, "Boris Bobrov" wrote: >On Tuesday 02 June 2015 09:32:45 Chenhong Liu wrote: >> There is keystone/exception.py which contains Exceptions defined and >>used >> inside keystone provide 4xx and 5xx status code. And we can use it like: >> exception.Forbidden.code, exception.for

Re: [openstack-dev] [keystone]Why not common definition about normal HTTP status code like 2xx and 3xx?

2015-06-02 Thread Neo Liu
On Tue, Jun 2, 2015 at 7:24 PM samuel wrote: > Hi Chenhong Liu, > > In addition, I think creating a common file to place non-error HTTP > status code > is a good idea and can be discussed with the Keystone cores. > > Feel free to add a point to our weekly meeting, Tuesdays 18:00 UTC. [1] > > Than

Re: [openstack-dev] [keystone]Why not common definition about normal HTTP status code like 2xx and 3xx?

2015-06-02 Thread samuel
Hi Chenhong Liu, In addition, I think creating a common file to place non-error HTTP status code is a good idea and can be discussed with the Keystone cores. Feel free to add a point to our weekly meeting, Tuesdays 18:00 UTC. [1] Sincerely, Samuel [1] https://wiki.openstack.org/wiki/Meetings

Re: [openstack-dev] [keystone]Why not common definition about normal HTTP status code like 2xx and 3xx?

2015-06-02 Thread samuel
Hi Chenhong Liu, encapsulated into the WSGI application, Keystone is architecturally organized as follows: Application <-> Router <-> Controller <-> Manager <-> Driver The Router connects called URLs with the code in the Controller, which delegates actions to Manager, which manages the busin

Re: [openstack-dev] [keystone]Why not common definition about normal HTTP status code like 2xx and 3xx?

2015-06-02 Thread Neo Liu
On Tue, Jun 2, 2015 at 5:46 PM Boris Bobrov wrote: > On Tuesday 02 June 2015 09:32:45 Chenhong Liu wrote: > > There is keystone/exception.py which contains Exceptions defined and used > > inside keystone provide 4xx and 5xx status code. And we can use it like: > > exception.Forbidden.code, ex

Re: [openstack-dev] [keystone]Why not common definition about normal HTTP status code like 2xx and 3xx?

2015-06-02 Thread Boris Bobrov
On Tuesday 02 June 2015 09:32:45 Chenhong Liu wrote: > There is keystone/exception.py which contains Exceptions defined and used > inside keystone provide 4xx and 5xx status code. And we can use it like: > exception.Forbidden.code, exception.forbiddent.title > exception.NotFound.code, excep

[openstack-dev] [keystone]Why not common definition about normal HTTP status code like 2xx and 3xx?

2015-06-02 Thread Chenhong Liu
There is keystone/exception.py which contains Exceptions defined and used inside keystone provide 4xx and 5xx status code. And we can use it like: exception.Forbidden.code, exception.forbiddent.title exception.NotFound.code, exception.NotFound.title This makes the code looks pretty and avo