Open Stack

+1 for a PoC


On 04/05/18 03:56, Flint WALRUS wrote:
> Exactly !
> Le jeu. 3 mai 2018 à 19:55, Flint WALRUS <gael.therond at gmail.com 
> <mailto:gael.therond at gmail.com>> a écrit :
>
>     It seems to be a fair way to do it. I do second the Neutron API as
>     a good candidate.
>
>     I’ll be happy to give a hand.
>
>     @jay I’ve already sum my points upper, but I could definitely have
>     better exemples if needed.
>
>     I’m operating and dealing with a large (really) Openstack platform
>     and GraphQL would have tremendous performances impacts for sure.
>     But you’re right proof have to be made.
>     Le jeu. 3 mai 2018 à 18:57, Ed Leafe <ed at leafe.com
>     <mailto:ed at leafe.com>> a écrit :
>
>         On May 2, 2018, at 2:40 AM, Gilles Dubreuil
>         <gdubreui at redhat.com <mailto:gdubreui at redhat.com>> wrote:
>         >
>         >> • We should get a common consensus before all projects
>         start to implement it.
>         >
>         > This is going to be raised during the API SIG weekly meeting
>         later this week.
>         > API developers (at least one) from every project are
>         strongly welcomed to participate.
>         > I suppose it makes sense for the API SIG to be the place to
>         discuss it, at least initially.
>
>         It was indeed discussed, and we think that it would be a
>         worthwhile experiment. But it would be a difficult, if not
>         impossible, proposal to have adopted OpenStack-wide without
>         some data to back it up. So what we thought would be a good
>         starting point would be to have a group of individuals
>         interested in GraphQL form an informal team and proceed to
>         wrap one OpenStack API as a proof-of-concept. Monty Taylor
>         suggested Neutron as an excellent candidate, as its API
>         exposes things at an individual table level, requiring the
>         client to join that information to get the answers they need.
>
>         Once that is done, we could examine the results, and use them
>         as the basis for proceeding with something more comprehensive.
>         Does that sound like a good approach to (all of) you?
>
>         -- Ed Leafe
>
>
>
>
>
>
>         __________________________________________________________________________
>         OpenStack Development Mailing List (not for usage questions)
>         Unsubscribe:
>         OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>         <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>         http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

-- 
Gilles Dubreuil
Senior Software Engineer - Red Hat - Openstack DFG Integration
Email: gilles at redhat.com
GitHub/IRC: gildub
Mobile: +61 400 894 219

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180504/3a2afa99/attachment.html>