Okay cool.  I'll take a punt at removing it

On Wed, 21 Sept 2022 at 15:50, Brendan Shephard <bshephar@redhat.com> wrote:

Hey Tony,

Thanks for the heads up. We have deprecated support for these resources some time ago:

https://review.opendev.org/c/openstack/heat/+/433549

I don't believe there are any concerns with removing this resource and subsequent use of the baymodel API from Heat now.

Brendan Shephard

Senior Software Engineer

Red Hat APAC

193 N Quay

Brisbane City QLD 4000

@RedHat   Red Hat   Red Hat

On Wed, Sep 21, 2022 at 3:37 PM Tony Breeds <tony@bakeyournoodle.com> wrote:

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.

--

Yours Tony.