<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
+1 for a PoC<br>
<br>
<br>
<div class="moz-cite-prefix">On 04/05/18 03:56, Flint WALRUS wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAG+53uY4F2Q117zXEMyXz2hcZYzz4THo1jeSifhPqpfixN+aWw@mail.gmail.com">Exactly
!<br>
<div class="gmail_quote">
<div dir="ltr">Le jeu. 3 mai 2018 à 19:55, Flint WALRUS <<a
href="mailto:gael.therond@gmail.com" moz-do-not-send="true">gael.therond@gmail.com</a>>
a écrit :<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">It seems to
be a fair way to do it. I do second the Neutron API as a good
candidate.<br>
<br>
I’ll be happy to give a hand.<br>
<br>
@jay I’ve already sum my points upper, but I could definitely
have better exemples if needed.<br>
<br>
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.<br>
<div class="gmail_quote">
<div dir="ltr">Le jeu. 3 mai 2018 à 18:57, Ed Leafe <<a
href="mailto:ed@leafe.com" target="_blank"
moz-do-not-send="true">ed@leafe.com</a>> a écrit :<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On May
2, 2018, at 2:40 AM, Gilles Dubreuil <<a
href="mailto:gdubreui@redhat.com" target="_blank"
moz-do-not-send="true">gdubreui@redhat.com</a>>
wrote:<br>
> <br>
>> • We should get a common consensus before all
projects start to implement it.<br>
> <br>
> This is going to be raised during the API SIG weekly
meeting later this week.<br>
> API developers (at least one) from every project are
strongly welcomed to participate.<br>
> I suppose it makes sense for the API SIG to be the
place to discuss it, at least initially. <br>
<br>
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.<br>
<br>
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?<br>
<br>
-- Ed Leafe<br>
<br>
<br>
<br>
<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage
questions)<br>
Unsubscribe: <a
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank" moz-do-not-send="true">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Gilles Dubreuil
Senior Software Engineer - Red Hat - Openstack DFG Integration
Email: <a class="moz-txt-link-abbreviated" href="mailto:gilles@redhat.com">gilles@redhat.com</a>
GitHub/IRC: gildub
Mobile: +61 400 894 219
</pre>
</body>
</html>