[openstack-ansible] Retirement of repo_build and pip_install roles
On Mon, 2020-04-06 at 14:37 +0300, Dmitriy Rabotyagov wrote:
Hi,
OpenStack-Ansible has fully migrated from usage of repo_build [1] and pip_install [2] roles to python_install_venv [3] in Stein. Since then these 2 roles are not used anymore by OSA, and it's probably time we deprecated them not to release them for Ussuri. im not sure if this applies to roles but for most "features" in openstack we deprecate at least one cycle before removal so if you deprecte them now you woudl still release them in ussuri but remove them in victoria to allow time for consumers of the role that you dont know about to move to python_install_venv.
if you ar confident no one outside of osa uses thos then you could remove them early.
Corresponding patches to retire projects are: [4] for repo_build and [5] for pip_install. If someone needs these roles, they can be either used with `git checkout HEAD^1` or with reverting mentioned patches.
[1] https://opendev.org/openstack/openstack-ansible-repo_build [2] https://opendev.org/openstack/openstack-ansible-pip_install [3] https://opendev.org/openstack/ansible-role-python_venv_build [4] https://review.opendev.org/716389 [5] https://review.opendev.org/717717 -- Kind regards, Dmitriy Rabotyagov
On 2020-04-06 13:05:22 +0100 (+0100), Sean Mooney wrote: [...]
im not sure if this applies to roles but for most "features" in openstack we deprecate at least one cycle before removal [...]
This is a governance tag projects can choose to assert: https://governance.openstack.org/tc/reference/tags/assert_follows-standard-d... It's service specific and talks about API features, though I suppose the concepts there could be adapted to things like orchestration and deployment tooling. Also note that OpenStackAnsible doesn't assert this tag on any deliverables so are free to disregard the guidance therein. That said, it's for sure a bit of an error in terminology to say you're "deprecating" something and removing it in the span of the same release. That's not deprecating, it's just plain removing. -- Jeremy Stanley
Thanks for reaching out. For what it's worth, you can think of these roles as internal APIs that we're removed that we replaced by other ones. They were never meant to be directly consumed by our users, they only exist to be able to "refactor" our code On Mon, Apr 6, 2020 at 9:37 AM Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2020-04-06 13:05:22 +0100 (+0100), Sean Mooney wrote: [...]
im not sure if this applies to roles but for most "features" in openstack we deprecate at least one cycle before removal [...]
This is a governance tag projects can choose to assert:
https://governance.openstack.org/tc/reference/tags/assert_follows-standard-d...
It's service specific and talks about API features, though I suppose the concepts there could be adapted to things like orchestration and deployment tooling. Also note that OpenStackAnsible doesn't assert this tag on any deliverables so are free to disregard the guidance therein. That said, it's for sure a bit of an error in terminology to say you're "deprecating" something and removing it in the span of the same release. That's not deprecating, it's just plain removing. -- Jeremy Stanley
-- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser@vexxhost.com W. https://vexxhost.com
participants (4)
-
Dmitriy Rabotyagov
-
Jeremy Stanley
-
Mohammed Naser
-
Sean Mooney