On Tue, 28 Jan 2020 at 14:54, Dougal Matthews <dougal@redhat.com> wrote:
Hey all,
While doing work on the Mistral to Ansible port I was looking at the openstack overcloud plan commands. These are;
- openstack overcloud plan create - openstack overcloud plan delete - openstack overcloud plan deploy - openstack overcloud plan list - openstack overcloud plan export
There has been a useful comment on the review that export is actually useful still. Harald said; "I find the possibility to download the plan on a failed deployment quite valuable. It allows me to read the heat templates in a more human friendly fully rendered version compared to the j2, run yaml validation tools etc. There is *magic* adding stuff to plan's that I can't see by simply running process templates tools." This seems like a good reason, although it could be argued that Swift is a better tool to download a container.
I believe none of these commands make sense in a post-TripleO UI world. There is no other way to interact and update a plan. Deploys are always done via "openstack overcloud deploy" and this deletes the contents of the plan container and repopulates it with the local files[1].
I am therefore proposing that we remove these commands and skip the normal deprecation process. https://review.opendev.org/#/c/704581/1
What do you think?
Thanks, Dougal
[1]: https://github.com/openstack/python-tripleoclient/blob/3c589979ceb05d732b3c9...