I should preface this with the fact that I don't use OpenStack SDK, so you may
want to check with the project developers.
One example is that a bit over a year ago nova added a microversion to include
the flavor information directly in the server information rather than returning
a link to a flavor (that may have been modified or deleted in the meantime).
To my knowledge, the Openstack SDK does not yet support this functionality.
Chris
On 04/17/2018 02:24 PM, Volodymyr Litovka wrote:
Hi Chris and colleagues,
based on your experience, can you specify an average delay between new OS
release / new feature introduction and appearance of corresponding support in
Unified Openstack SDK if you were experiencing such issues?
Thanks.
On 4/17/18 7:23 PM, Chris Friesen wrote:
On 04/17/2018 07:13 AM, Jeremy Stanley wrote:
The various "client libraries" (e.g. python-novaclient,
python-cinderclient, et cetera) can also be used to that end, but
are mostly for service-to-service communication these days, aren't
extremely consistent with each other, and tend to eventually drop
support for older OpenStack APIs so if you're going to be
interacting with a variety of different OpenStack deployments built
on different releases you may need multiple versions of the client
libraries (depending on what it is you're trying to do).
The above is all good information.
I'd like to add that if you need bleeding-edge functionality in nova it will
often be implemented first in python-novaclient.
Chris
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
