<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 22/06/18 09:21, Tristan Cacqueray
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1529622920.4qf1x4aqgc.tristanC@fedora">Hi Flint,
<br>
<br>
On June 21, 2018 5:32 pm, Flint WALRUS wrote:
<br>
<blockquote type="cite">Hi everyone, sorry for the late answer but
I’m currently trapped into a
<br>
cluster issue with cinder-volume that doesn’t give me that much
time.
<br>
<br>
That being said, I’ll have some times to work on this feature
during the
<br>
summer (July/August) and so do some coding once I’ll have
catched up with
<br>
your work.
<br>
<br>
</blockquote>
That's great to hear! The next step is to understand how to deal
with
<br>
oslo policy and control objects access/modification.
<br>
<br>
<blockquote type="cite">Did you created a specific tree or did you
created a new graphql folder
<br>
within the neutron/neutron/api/ path regarding the schemas etc?
<br>
</blockquote>
<br>
There is a feature/graphql branch were an initial patch[1] adds a
new
<br>
neutron/api/graphql directory as well as a new test_graphql.py
<br>
functional tests.
<br>
The api-paste is also updated to expose the '/graphql' http
endpoint.
<br>
<br>
Not sure if we want to keep on updating that change, or propose
further
<br>
code as new change on top of this skeleton?
<br>
<br>
</blockquote>
<br>
Makes sense to merge it, I think we have the base we needed to get
going.<br>
I'll make it green so we can get merge it. <br>
<br>
<br>
<blockquote type="cite"
cite="mid:1529622920.4qf1x4aqgc.tristanC@fedora">Regards,
<br>
-Tristan
<br>
<br>
<br>
<blockquote type="cite">Le sam. 16 juin 2018 à 08:42, Tristan
Cacqueray <a class="moz-txt-link-rfc2396E" href="mailto:tdecacqu@redhat.com"><tdecacqu@redhat.com></a> a
<br>
écrit :
<br>
<br>
<blockquote type="cite">On June 15, 2018 10:42 pm, Gilles
Dubreuil wrote:
<br>
> Hello,
<br>
>
<br>
> This initial patch [1] allows to retrieve networks,
subnets.
<br>
>
<br>
> This is very easy, thanks to the graphene-sqlalchemy
helper.
<br>
>
<br>
> The edges, nodes layer might be confusing at first
meanwhile they make
<br>
> the Schema Relay-compliant in order to offer re-fetching,
pagination
<br>
> features out of the box.
<br>
>
<br>
> The next priority is to set the unit test in order to
implement
<br>
mutations.
<br>
>
<br>
> Could someone help provide a base in order to respect
Neutron test
<br>
> requirements?
<br>
>
<br>
>
<br>
> [1] [abandoned]
<br>
<br>
Actually, the correct review (proposed on the feature/graphql
branch)
<br>
is:
<br>
<br>
[1] <a class="moz-txt-link-freetext" href="https://review.openstack.org/575898">https://review.openstack.org/575898</a>
<br>
<br>
>
<br>
> Thanks,
<br>
> Gilles
<br>
>
<br>
>
<br>
__________________________________________________________________________
<br>
> OpenStack Development Mailing List (not for usage
questions)
<br>
> Unsubscribe:
<br>
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<br>
>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
<br>
>
<br>
__________________________________________________________________________
<br>
OpenStack Development Mailing List (not for usage questions)
<br>
Unsubscribe:
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
<br>
<br>
</blockquote>
__________________________________________________________________________
<br>
OpenStack Development Mailing List (not for usage questions)
<br>
Unsubscribe:
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
<br>
<br>
</blockquote>
<!--'"--><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</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>