Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On Wed, Jun 22, 2016, at 09:07 AM, Chris Dent wrote: > On Tue, 21 Jun 2016, Sylvain Bauza wrote: > > > To be honest, Chris and you were saying that you don't like Flask, and I'm > > a > > bit agreeing with you. Why now it's a good possibility ? > > As I said when I started the other version of

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Sean Dague wrote: > If we look at the iaas base layer: > > Keystone - custom WSGI with Routes / Paste > Glance - WSME + Routes / Paste > Cinder - custom WSGI with Routes / Paste > Neutron - pecan + Routes / Paste > Nova - custom WSGI with Routes / Paste Neutron's pecan code is still fairly new.

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

2016-06-22 22:52 GMT+08:00 Chris Dent : > On Tue, 21 Jun 2016, Sean Dague wrote: > > I honestly don't think raw WSGI is a bad choice here. People are going >> to be pretty familiar with it in related projects at this level. >> > > Yeah, WSGI itself is a framework, one that

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On Tue, 21 Jun 2016, Sean Dague wrote: I honestly don't think raw WSGI is a bad choice here. People are going to be pretty familiar with it in related projects at this level. Yeah, WSGI itself is a framework, one that is clearly defined and works well for the types of things we are currently

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On 06/21/2016 10:10 AM, Clint Byrum wrote: > Excerpts from Sean Dague's message of 2016-06-21 08:00:50 -0400: >> On 06/21/2016 07:39 AM, Jay Pipes wrote: >>> On 06/21/2016 05:43 AM, Sylvain Bauza wrote: Le 21/06/2016 10:04, Chris Dent a écrit : > On Mon, 20 Jun 2016, Jay Pipes wrote:

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On 06/21/2016 10:11 AM, Clint Byrum wrote: > Excerpts from Sean Dague's message of 2016-06-21 09:10:00 -0400: >> The amount of wsgi glue above Routes / Paste is pretty minimal (after >> you get rid of all the extensions facilities). >> >> Templating and Session handling are things we don't need.

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

[Non-specific to nova] I generated a list of which frameworks were in use in Mitaka - it's at the top of the blog post I reference below, so you don't have to dig into it too much to get the data. TL/DR: - falcon: 4 projects - custom + routes: 12 projects - pecan: 12 projects - flask: 2 projects

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Excerpts from Sean Dague's message of 2016-06-21 08:00:50 -0400: > On 06/21/2016 07:39 AM, Jay Pipes wrote: > > On 06/21/2016 05:43 AM, Sylvain Bauza wrote: > >> Le 21/06/2016 10:04, Chris Dent a écrit : > >>> On Mon, 20 Jun 2016, Jay Pipes wrote: > >>> > Flask seems to be the most widely

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Excerpts from Sean Dague's message of 2016-06-21 09:10:00 -0400: > The amount of wsgi glue above Routes / Paste is pretty minimal (after > you get rid of all the extensions facilities). > > Templating and Session handling are things we don't need. We're not a > webapp, we're a REST service.

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On Tue, Jun 21, 2016 at 08:00:50AM -0400, Sean Dague wrote: > > Keystone - custom WSGI with Routes / Paste > Keystone is moving toward Flask. I have an experimental patch that moves us in that direction. I'm in the process to rebasing and fixing it up since it's wildly out of date. -- David

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On 21/06/2016 13:04, Sean Dague wrote: > On 06/21/2016 07:39 AM, Jay Pipes wrote: >> On 06/21/2016 05:43 AM, Sylvain Bauza wrote: >>> Le 21/06/2016 10:04, Chris Dent a écrit : On Mon, 20 Jun 2016, Jay Pipes wrote: > Flask seems to be the most widely used and known WSGI framework so

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On 06/21/2016 08:42 AM, Doug Hellmann wrote: > Excerpts from Sean Dague's message of 2016-06-21 08:00:50 -0400: >> On 06/21/2016 07:39 AM, Jay Pipes wrote: >>> On 06/21/2016 05:43 AM, Sylvain Bauza wrote: Le 21/06/2016 10:04, Chris Dent a écrit : > On Mon, 20 Jun 2016, Jay Pipes wrote:

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Excerpts from Sean Dague's message of 2016-06-21 08:00:50 -0400: > On 06/21/2016 07:39 AM, Jay Pipes wrote: > > On 06/21/2016 05:43 AM, Sylvain Bauza wrote: > >> Le 21/06/2016 10:04, Chris Dent a écrit : > >>> On Mon, 20 Jun 2016, Jay Pipes wrote: > >>> > Flask seems to be the most widely

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Le 21/06/2016 14:00, Sean Dague a écrit : On 06/21/2016 07:39 AM, Jay Pipes wrote: On 06/21/2016 05:43 AM, Sylvain Bauza wrote: Le 21/06/2016 10:04, Chris Dent a écrit : On Mon, 20 Jun 2016, Jay Pipes wrote: Flask seems to be the most widely used and known WSGI framework so for

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On 06/21/2016 07:39 AM, Jay Pipes wrote: > On 06/21/2016 05:43 AM, Sylvain Bauza wrote: >> Le 21/06/2016 10:04, Chris Dent a écrit : >>> On Mon, 20 Jun 2016, Jay Pipes wrote: >>> Flask seems to be the most widely used and known WSGI framework so for consistency's sake, I'm recommending

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On 06/21/2016 05:43 AM, Sylvain Bauza wrote: Le 21/06/2016 10:04, Chris Dent a écrit : On Mon, 20 Jun 2016, Jay Pipes wrote: Flask seems to be the most widely used and known WSGI framework so for consistency's sake, I'm recommending we just use it and not rock this boat. There are more

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Le 21/06/2016 10:04, Chris Dent a écrit : On Mon, 20 Jun 2016, Jay Pipes wrote: Flask seems to be the most widely used and known WSGI framework so for consistency's sake, I'm recommending we just use it and not rock this boat. There are more important things to get hung up on than this

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On Mon, 20 Jun 2016, Jay Pipes wrote: Flask seems to be the most widely used and known WSGI framework so for consistency's sake, I'm recommending we just use it and not rock this boat. There are more important things to get hung up on than this battle right now. That seems perfectly

[openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Hi Chris, stackers, OK, so I've been a pretty vocal proponent of Chris' approach to the new placement REST API endpoint, which is to use no WSGI frameworks and instead just use the selector library (or Routes as a second choice) for defining the URI mappings. However, I had a chat with Doug