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
Hi,
I am happy to see the effort to explore a new API mechanism.
I would like to see good progress and help effort as API liaison from the
neutron team.
> Neutron has been selected for the PoC because of its specific data model
On the other hand, I am not sure this is the right reason to choose
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 a écrit :
> On 2018-05-04 23:42:59 + (+), Flint WALRUS wrote:
> [...]
> > what operators are expecting the
On 2018-05-04 23:42:59 + (+), Flint WALRUS wrote:
[...]
> what operators are expecting the foundation to do with such
> challenges.
[...]
If by "the foundation" you mean the OpenStack Foundation then this
isn't really their remit. You need invested members of the community
at large to
On 05/05/18 09:42, Flint WALRUS wrote:
I will not attend the vancouver summit but I’ll try to attend the
berlin one as it’s closer to me.
No worries, I hope "networking" at Vancouver will allow to grab good
support and rocket the momentum :).
Unfortunately I'm not sure to make it to Berlin
Hello,
Few of us recently discussed [1] how GraphQL [2], the next evolution
from REST, could transform OpenStack APIs for the better.
Effectively we believe OpenStack APIs provide perfect use cases for
GraphQL DSL approach, to bring among other advantages, better
performance and stability,
thanks Jeffrey
On 05/05/2018 03:03 AM, Jeffrey Zhang wrote:
Hi vladispay,
I guess you are talking rabbit_ha_queues options. It is already marked
as deprecated[0].
cfg.BoolOpt('rabbit_ha_queues',
default=False,
deprecated_group='DEFAULT',
help='Try to use