[magnum][heat][requirements][release] Potential blocker for release with python-magnumclient 4.0.0
Tony Breeds
tony at bakeyournoodle.com
Wed Sep 21 05:25:26 UTC 2022
Hello all,
In [1] baymodel code was removed, although it still seems to be
listed in the API-ref. Story [2] states it's been deprecated for a
long time, but a quick check failed to see this documented anywhere.
Heat still supports baymodel and the removal is causing failures.
Blocking the use of python-magnumclient 4.0.0[3] inzed, even though
the 4.0.0 release is clearly meant for zed.
I can see a couple of paths forward.
0. Remove the documentation in the api-ref for baymodels
1. Remove the support in heat for baymodels (I think the newer
clusters API can be used instead?)
2. Revert the change in magnumclient and re-release etc etc
3. Keep 4.0.0 for the Antelope release, and reset the stable/zed
branch python-magnumclient to fd0cb1e (before the removal of
baymodels)
Obviously option 1 looks like the least disruptive change, but
potentially causes a problem for heat depending on the published state
of baymodel support
[1] https://review.opendev.org/c/openstack/python-magnumclient/+/803629
[2] https://storyboard.openstack.org/#!/story/2009104
[3] https://review.opendev.org/c/openstack/requirements/+/858089
--
Yours Tony.
More information about the openstack-discuss
mailing list