On 12/06/2013 03:57 PM, Ken'ichi Ohmichi wrote:
Hi,
We are implementing Nova v3 API validation with jsonschema.
The schemas of API parameters are defined under
nova/api/openstack/compute/schemas/v3/.
I guess the shemas would be used for checking the difference between
doc and Nova v3 API
parameters as another approach.
example:
https://review.openstack.org/#/c/59616/1/nova/api/openstack/compute/schemas/v3/agents_schema.py
Thanks
Ken'ichi Ohmichi
Thanks, Ken'ichi. These could be useful. But I don't think they are a
substitute for the document for two reason. First, these schemas only
have info for the json dict part, not any changes to the url suffix or
return values. Second, there really needs to be a release note to help
users upgrade their apps from v2 to v3.
-David
---
2013/12/7 David Kranz <dkr...@redhat.com>:
On 11/13/2013 06:09 PM, Christopher Yeoh wrote:
On Thu, Nov 14, 2013 at 7:52 AM, David Kranz <dkr...@redhat.com> wrote:
On 11/13/2013 08:30 AM, Alex Xu wrote:
Hi, guys
This is the document for the changes from Nova v2 api to v3:
https://wiki.openstack.org/wiki/NovaAPIv2tov3
I will appreciate if anyone can help for review it.
Another problem comes up - how to keep the doc updated. So can we ask
people, who change
something of api v3, update the doc accordingly? I think it's a way to
resolve it.
Thanks
Alex
_______________________________________________
openstack-qa mailing list
openstack...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-qa
Thanks, this is great. I fixed a bug in the os-services section. BTW,
openstack...@lists.openstack.org list is obsolete. openstack-dev with
subject starting with [qa] is the current "qa list". About updating, I think
this will have to be heavily socialized in the nova team. The initial review
should happen by those reviewing the tempest v3 api changes. That is how I
found the os-services bug.
While reviewing https://review.openstack.org/#/c/59939/ I found that a lot
of the flavors changes are missing from this doc. Hopefully some one closer
to the code changes can update it.
-David
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
