IRR - pip_lock_down¶
Split out the pip_lock_down role into it’s own repository.
Roles are all contained within a single monolithic repository making it impossible/difficult to consume the OSA roles outside of deploying the entire stack.
To ensure that the OSA project is consumable by other stacks using different architectures, deployment methods, and capabilities the role “pip_lock_down” need to be moved from the monolithic stack and into the it’s own role repository.
Leave everything the way it is. However doing that will hurt general OSA adoption.
No impact to the playbooks.
The role will be removed from the main stack. The plugins, filters, and libraries may need to be locally updated.
While the change will impact the placement of the role it will not impact
upgrade-ability of the stack. The general workflow will need to be updated
to ensure that users are updating roles on upgrade using the Ansible
galaxy interface however generally speaking this is already being done for
the deployer when running the
Moving the role to an external repository will cause an impact in time to role resolution however that impact should be minimal.
End user impact¶
Deployers will need to be aware of the new role locations and how to update existing roles however this should be minimal considering the tooling for updating existing roles already exists
Developers will need focus work within the roles which will exist within separate repositories.
With the role moved, tests will be created within the role via OpenStack CI to ensure that the role is performing the actions that its supposed to.
Updated documentation via the “README.rst” will be created to show how the role can be used standalone.
Example local inventory will be created to show how the role can be used. The local only inventory will also be used for testing the role.
The test cases will deploy the role into a regular DSVM image
The role will execute itself locally
Once the role has completed an Ansible test play will run through several assert tasks to ensure the role functioned as intended.
The base README.rst file will be updated to explain how the role can be used as a standalone role.