[openstack-dev] [magnum] Removing pod, rcs and service APIs
hongbin.lu at huawei.com
Wed Dec 16 15:57:29 UTC 2015
If I remember correctly, the decision is to drop the COE-specific API (Pod, Service, Replication Controller) in the next API version. I think a good way to do that is to put a deprecated warning in current API version (v1) for the removed resources, and remove them in the next API version (v2).
An alternative is to drop them in current API version. If we decide to do that, we need to bump the micro-version , and ask users to specify the microversion as part of the requests when they want the removed APIs.
From: Cammann, Tom [mailto:tom.cammann at hpe.com]
Sent: December-16-15 8:21 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [magnum] Removing pod, rcs and service APIs
I have been noticing a fair amount of redundant work going on in magnum, python-magnumclient and magnum-ui with regards to APIs we have been intending to drop support for. During the Tokyo summit it was decided that we should support for only COE APIs that all COEs can support which means dropping support for Kubernetes specific APIs for Pod, Service and Replication Controller.
Egor has submitted a blueprint “Unify container actions between all COEs” which has been approved to cover this work and I have submitted the first of many patches that will be needed to unify the APIs.
The controversial patches are here: https://review.openstack.org/#/c/258485/ and https://review.openstack.org/#/c/258454/
These patches are more a forcing function for our team to decide how to correctly deprecate these APIs as I mention there is a lot of redundant work going on these APIs. Please let me know your thoughts.
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev