Hi team,
I submit a forum [1] named "Cross-project Open API 3.0 support".
We can make more discussions about that in this forum in berlin.
Feel free to add your ideas here [2].
Welcome to join us.
Thanks very much.
[1]
On 11/10/18 00:18, Jeremy Stanley wrote:
On 2018-10-10 13:24:28 +1100 (+1100), Gilles Dubreuil wrote:
On 09/10/18 23:58, Jeremy Stanley wrote:
On 2018-10-09 08:52:52 -0400 (-0400), Jim Rollenhagen wrote:
[...]
It seems to me that a major goal of openstacksdk is to hide
differences between
On 2018-10-10 13:24:28 +1100 (+1100), Gilles Dubreuil wrote:
> On 09/10/18 23:58, Jeremy Stanley wrote:
> > On 2018-10-09 08:52:52 -0400 (-0400), Jim Rollenhagen wrote:
> > [...]
> > > It seems to me that a major goal of openstacksdk is to hide
> > > differences between clouds from the user. If
On Tue, Oct 9, 2018 at 10:25 PM Gilles Dubreuil wrote:
>
>
> On 09/10/18 23:58, Jeremy Stanley wrote:
> > On 2018-10-09 08:52:52 -0400 (-0400), Jim Rollenhagen wrote:
> > [...]
> >> It seems to me that a major goal of openstacksdk is to hide differences
> >> between clouds from the user. If the
On 09/10/18 23:58, Jeremy Stanley wrote:
On 2018-10-09 08:52:52 -0400 (-0400), Jim Rollenhagen wrote:
[...]
It seems to me that a major goal of openstacksdk is to hide differences
between clouds from the user. If the user is meant to use a GraphQL library
themselves, we lose this and the user
On 2018-10-09 08:52:52 -0400 (-0400), Jim Rollenhagen wrote:
[...]
> It seems to me that a major goal of openstacksdk is to hide differences
> between clouds from the user. If the user is meant to use a GraphQL library
> themselves, we lose this and the user needs to figure it out themselves.
>
On Mon, Oct 8, 2018 at 5:58 AM Gilles Dubreuil wrote:
>
> On 05/10/18 21:54, Jim Rollenhagen wrote:
>
> GraphQL has introspection features that allow clients to pull the schema
> (types, queries, mutations, etc): https://graphql.org/learn/introspection/
>
> That said, it seems like using this in
On 05/10/18 21:54, Jim Rollenhagen wrote:
GraphQL has introspection features that allow clients to pull the
schema (types, queries, mutations, etc):
https://graphql.org/learn/introspection/
That said, it seems like using this in a client like OpenStackSDK
would get messy quickly. Instead of
GraphQL has introspection features that allow clients to pull the schema
(types, queries, mutations, etc): https://graphql.org/learn/introspection/
That said, it seems like using this in a client like OpenStackSDK would get
messy quickly. Instead of asking for which versions are supported, you'd
Gilles Dubreuil writes:
>> About the micro version, we discuss with your team mate dmitry in
>> another email [1]
>
> Obviously micro version is a point of contention.
> My take on this is because consuming them has been proven harder than
> developing them.
> The beauty of GraphQL is that
Hi Edison,
Sorry for the delay.
Please see inline...
Cheers,
Gilles
On 07/09/18 12:03, Edison Xiang wrote:
Hey gilles,
Thanks your introduction for GraphQL and Relay.
> GraphQL and OpenAPI have a different feature scope and both have pros and
cons.
I totally agree with you. They can work
Hey gilles,
Thanks your introduction for GraphQL and Relay.
> GraphQL and OpenAPI have a different feature scope and both have pros and
cons.
I totally agree with you. They can work together.
Right now, I think we have no more work to adapt OpenStack APIs for Open
API.
Firstly we could sort out
Hi Dmitry,
Thanks your reply. Absolutely you are a sdk expert.
> This is a good first step, but if I get it right it does not specify
which
> response corresponds to which request.
You got it. I think it depends on how to use the API schemas.
We could define some rules to make sure which
Hi,
On 08/29/2018 08:36 AM, Edison Xiang wrote:
Hi team,
As we know, Open API 3.0 was released on July, 2017, it is about one year ago.
Open API 3.0 support some new features like anyof, oneof and allof than Open API
2.0(Swagger 2.0).
Now OpenStack projects do not support Open API.
Also I
On 30/08/18 13:56, Edison Xiang wrote:
Hi Ed Leafe,
Thanks your reply.
Open API defines a standard interface description for REST APIs.
Open API 3.0 can make a description(schema) for current OpenStack REST
API.
It will not change current OpenStack API.
I am not a GraphQL expert. I look up
Hey doug,
Thanks your reply. Very good question.
It is not a conflict with current API Documents work that has already been
done.
We can use some tools to generate Open API schema from existing machine
readable API-def in every project like nova [1]
We can still use the existing tools to generate
Excerpts from Edison Xiang's message of 2018-08-30 14:08:12 +0800:
> Hey dims,
>
> Thanks your reply. Your suggestion is very important.
>
> > what would be the impact to projects?
> > what steps they would have to take?
>
> We can launch a project to publish OpenStack Projects APIs Schema for
Hey dims,
Thanks your reply. Your suggestion is very important.
> what would be the impact to projects?
> what steps they would have to take?
We can launch a project to publish OpenStack Projects APIs Schema for users
and developers.
But now OpenStack Projects have no APIs Schema definition.
Hi Jay,
Thanks your reply.
As we know, we can automatically generate API Documents, different language
of Clients(SDK),
cloud tool adapters for OpenStack based on Open API 3.0 Schema.
About the other self-defined development for 3rd party developers,
based on the Open API 3.0 schema, developers
Hi Ed Leafe,
Thanks your reply.
Open API defines a standard interface description for REST APIs.
Open API 3.0 can make a description(schema) for current OpenStack REST API.
It will not change current OpenStack API.
I am not a GraphQL expert. I look up something about GraphQL.
In my understanding,
On Aug 29, 2018, at 1:36 AM, Edison Xiang wrote:
>
> As we know, Open API 3.0 was released on July, 2017, it is about one year ago.
> Open API 3.0 support some new features like anyof, oneof and allof than Open
> API 2.0(Swagger 2.0).
> Now OpenStack projects do not support Open API.
> Also I
On 08/29/2018 02:36 AM, Edison Xiang wrote:
Based on Open API 3.0, it can bring lots of benefits for OpenStack
Community and does not impact the current features the Community has.
3rd party developers can also do some self-defined development.
Hi Edison,
Would you mind expanding on what
Edison,
This is definitely a step in the right direction if we can pull it off.
Given the previous experiences and the current situation of how and where
we store the information currently and how we generate the website for the
API(s), can you please outline
- what would be the impact to
23 matches
Mail list logo
