Re: [openstack-dev] [ironic] [API] Evolving our REST API

[Everett Toews]

On Oct 13, 2016, at 10:00 AM, Devananda van der Veen  
wrote:
> 
> So I have finalized five proposals of substantial changes we can make, that
> folks agreed were important to work on, and which I believe we can do within 
> the
> microversion framework starting immediately. Four of them will, I think, be
> fairly straight forward. The fifth, adding a /tasks/ resource, has the most
> challenges, and its own session planned.

I just want to point out some prior art for a tasks resource [1] in Glance. It 
might help inform your discussion a bit. I can understand how it will be 
challenging. If an API guideline for tasks eventually came out as a result of 
this discussion, it would reduce the challenges for future projects. ;)

Cheers,
Everett

[1] http://developer.openstack.org/api-ref/image/v2/#tasks


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic] [API] Evolving our REST API

[Devananda van der Veen]

Hi all,

We discussed a little at the last summit, and discussed further at the midcycle
[1], about how we might go about remedying some of the frustrations and missing
functionality in our API, and I volunteered to work on it during the Newton 
cycle.

As I looked at all of the feedback we collected and thought about these issues,
I became convinced we could make most, if not all, of the changes with small
steps. Together, they bring a lot of new functionality, but without a complete
API rewrite and the accompanying burden of carrying two versions of the API.

So I have finalized five proposals of substantial changes we can make, that
folks agreed were important to work on, and which I believe we can do within the
microversion framework starting immediately. Four of them will, I think, be
fairly straight forward. The fifth, adding a /tasks/ resource, has the most
challenges, and its own session planned.

I have posted the specs here:

https://review.openstack.org/#/q/status:open+project:openstack/ironic-specs+branch:master+topic:api-evolution

Please give them a read, and let's discuss them in Barcelona [2].

It would be great to have someone from the API working group also peruse these
proposals and validate the direction.

Cheers,
Devananda


[1] https://etherpad.openstack.org/p/ironic-newton-midcycle around L390
[2] https://etherpad.openstack.org/p/ironic-ocata-summit-api-evolution

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev