Every openstack client is built in the repo build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Confirmed
|
Wishlist
|
Major Hayden |
Bug Description
While investigating some of the repo build slowdowns in CentOS, I found that every single OpenStack client is built (along with dependencies) during the repo build process.
For some clients, like python-swiftclient, this isn't a big deal.
However, some clients like python-
All of these client requirements flow in through heat: https:/
Should we go through the list of clients during a selective wheel build and remove any clients that correspond to OpenStack services that are not being deployed. As an example, if monasca is being deployed, why should we build, store, and venv-itize the monasca client and its dependencies?
Changed in openstack-ansible: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
I think it would make sense not to inlude all the clients. since they will never be used anyway.
If the deployer want to deploy a new service the repobuild process will need to be re-ran anyway.