Add smaller flavors to bgo shpc c1 variants#143
Open
danros1 wants to merge 1 commit into
Open
Conversation
danros1
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds smaller SHPC C1 BGO flavors across the existing C1 and C1AD variants.
This introduces
largeandxlargeflavor definitions for:shpc.c1a-bgoshpc.c1ad0-bgoshpc.c1ad1-bgoshpc.c1ad2-bgoshpc.c1ad3-bgoshpc.c1ad4-bgoChanges
Adds 2 vCPU / 4 GB RAM
largeflavorsAdds 4 vCPU / 8 GB RAM
xlargeflavorsKeeps disk sizes aligned with each existing variants:
c1a: 20 GBc1ad0: 80 GBc1ad1: 200 GBc1ad2: 500 GBc1ad3: 1000 GBc1ad4: 2000 GBMotivation
The existing SHPC C1 BGO flavor variants only provide larger instance sizes. However most usecases have proven not to require disk sizes. We have encountered usecases where it would be beneficial to use the local storage of the hypervisors using data that can be rebuilt. This will reduce the demand for mass-storage-ssd in the bgo region. However in many cases these usecases does not require the larger compute and memory instance sizes and thus would end up hogging resources if used. The proposed solution is these smaller flavor sizes.