Remove Storage Cluster from Virtual Site Deployments #153
Assignees
Labels
enhancement
New feature or request
priority/critical
Items critical to be implemented, usually by the next release
size m
2-5 days [moderate complexity, generic code, or enhancement to existing feature]]
Milestone
Comments
mattmceuen
added
priority/critical
|
Please assign this to me |
|
Size would be 'M' |
eak13
added
the
size m
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem description
The Zuul gates which do the virtual site deployments have been failing often with timeouts. It is believed that some of this may be related to the Rook deployment of the Ceph storage cluster using too many resources within the virtual environments. It is suggested to remove the storage cluster composite deployment from the virtual test sites. The storage cluster deployment would remain in the reference baremetal site deployments.
Proposed change
This patchset (https://review.opendev.org/c/airship/treasuremap/+/792694) makes the storage cluster composite deployment a part of the target workload phase for both the airship-core and multi-tenant types. Once merged, this makes the storage cluster deployment a part of any site inheriting one of these types. We are requesting that target workload phase for the virtual sites (test-site and virtual-network-cloud) overrides the type setting to omit the deployment of the storage cluster (
manifests/composite/storage-cluster).The storage-cluster composite needs to continue to be deployed as part of the baremetal reference sites.
The text was updated successfully, but these errors were encountered: