Exactly ! Le jeu. 3 mai 2018 à 19:55, Flint WALRUS <[email protected]> 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 <[email protected]> a écrit : > >> On May 2, 2018, at 2:40 AM, Gilles Dubreuil <[email protected]> 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: >> [email protected]?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
