Hi matt, everyone,
I just read your analysis and would like to thank you for such work. I
really think there are numerous features included/used on this Nova rework
that would be highly beneficial for Nova and users of it.
I hope people will fairly appreciate you work.
I didn’t had time to
Oh! That’s its truly a sweet sweet attention, that will indeed really help
us to focus on what we have to do without having to goes through an
extensive email back and forth :-)
Thanks a lot!!
Le ven. 22 juin 2018 à 22:48, Ed Leafe a écrit :
> On Jun 15, 2018, at 5:42 PM, Gilles Dubreuil
08:42, Gilles Dubreuil a
écrit :
>
>
> On 22/06/18 15:57, Flint WALRUS wrote:
>
> Hi everyone,
>
> Thanks for the updates and support, that appreciated.
>
> @Gilles, did you already implemented all the service types?
>
>
> We have query types for networks and s
don’t want to mess up having pieces of code everywhere.
Thanks!
Le ven. 22 juin 2018 à 06:44, Gilles Dubreuil a
écrit :
>
> On 22/06/18 09:21, Tristan Cacqueray wrote:
>
> Hi Flint,
>
> On June 21, 2018 5:32 pm, Flint WALRUS wrote:
>
> Hi everyone, sorry for the late answer b
Hi everyone, sorry for the late answer but I’m currently trapped into a
cluster issue with cinder-volume that doesn’t give me that much time.
That being said, I’ll have some times to work on this feature during the
summer (July/August) and so do some coding once I’ll have catched up with
your
t;
> I've also been told that Zuul nees GraphQL.
>
> Well basically the question is who doesn't need it?
>
> Cheers,
> Gilles
>
>
>
> On 31/05/18 03:34, Flint WALRUS wrote:
>
> Hi Gilles, I hope you enjoyed your Summit!?
>
> Did you had any interesting talk to rep
> PS: Flint, Thank you for offering to be the advocate for Berlin. That's
> great!
>
>
> On 06/05/18 02:23, Flint WALRUS wrote:
>
> Hi Akihiro,
>
> Thanks a lot for this insight on how neutron behave.
>
> We would love to get support and backing from the neut
Hi Akihiro,
Thanks a lot for this insight on how neutron behave.
We would love to get support and backing from the neutron team in order to
be able to get the best PoC possible.
Someone suggested neutron as a good choice because of it simple database
model. As GraphQL can manage your behavior
Yeah, when I said foundation I’m talking about the community.
@Gilles, count me on if you need someone to work with.
Le sam. 5 mai 2018 à 17:20, Jeremy Stanley <fu...@yuggoth.org> a écrit :
> On 2018-05-04 23:42:59 + (+0000), Flint WALRUS wrote:
> [...]
> > what opera
is discussion on the coming project thread.
>
> Thank you everyone and see you there.
>
> Cheers,
> Gilles
>
> On 04/05/18 23:16, Flint WALRUS wrote:
>
> As clarify by Gilles and Kevin we absolutely can get GraphQL with the
> control plan API and the workers api.
>
As clarify by Gilles and Kevin we absolutely can get GraphQL with the
control plan API and the workers api.
Ok, how do start to work on that? What’s the next step?
Which server library do we want to use?
I personally use graphene with python as it is the library listed by the
official GraphQL
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
Exactly !
Le jeu. 3 mai 2018 à 19:55, Flint WALRUS <gael.ther...@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 definitel
t to help with future ML
> searches.
>
> Please see inline too.
>
> On 02/05/18 07:37, Flint WALRUS wrote:
>
> Ok, here are my two cents regarding GraphQL integration within Openstack
> and some thoughts around this topic.
>
> 1°/- Openstack SDK should still e
highly help Openstack on more than just
interfacing topics.
Le mar. 1 mai 2018 à 05:00, Gilles Dubreuil <gdubr...@redhat.com> a écrit :
>
>
> On 01/05/18 11:31, Flint WALRUS wrote:
>
> Yes, that’s was indeed the sens of my point.
>
>
> I was just enforcing it, no worr
of ops to keep
their day to day tools by just having to convert their existing collections
of handful requests.
Or alternatively to provide a tool with similar features at least.
Le mar. 1 mai 2018 à 03:18, Gilles Dubreuil <gdubr...@redhat.com> a écrit :
>
>
> On 30/04/18 20:16, Fli
I would very much second that question! Indeed it have been one of my own
wondering since many times.
Of course GraphQL is not intended to replace REST as is and have to live in
parallel but it would likely and highly accelerate all requests within
heavily loaded environments.
So +1 for this
+1
Le lun. 12 mars 2018 à 10:09, Marcin Juszkiewicz <
marcin.juszkiew...@linaro.org> a écrit :
> W dniu 12.03.2018 o 03:06, Jeffrey Zhang pisze:
> > It is my pleasure to nominate caoyuan for kolla core team.
>
> +1
>
> __
>
To simply answer the question:
Yes I have experience about this specific matter of things as I’m now
working with the exact setup for more than 5 years. I’m even exclusively
working remotely with some studios of my employer.
It’s not that expensive as long as you get correct rules, hardware and
Pretty easy, put the PTG online with a livestream on
YouTube/Hangout/whatever platform that will then be saved and could even be
watched later on!
It’s just a matter of some hardware and a decent internet bandwidth that’s
already available to almost every places where a PTG took place.
Problem
20 matches
Mail list logo
