-
Notifications
You must be signed in to change notification settings - Fork 871
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tests: add OS_IMAGE_TYPE setting to allow for minimal tests #5682
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -39,6 +39,17 @@ | |
# to this format internally; in this case, to "None::ubuntu::focal::20.04".) | ||
OS_IMAGE = "focal" | ||
|
||
|
||
# Determines unique image type or flavor to exercise if the cloud supports | ||
# image-type lookup for daily_image and released_images. | ||
# | ||
# One of the following pycloudlib.cloud.ImageType values: | ||
# - generic | ||
# - minimal | ||
# - Pro | ||
# - Pro FIPS | ||
OS_IMAGE_TYPE = "generic" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We keep talking about additional OS support, and this one comes across as being Ubuntu-specific in a way that might encourage a bunch of OS-specific fields to proliferate across various OSes. We could try to encode this into I think I'm ok with this now, but if we have to add another dimension to our image specification, I think we need a better solution. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @TheRealFalcon: from the looks of other distribution vendors , there are similar alternative "offers" such as BYOS (bring your own subscription) images, HA and minimal images. I wonder if it is worth representing an optional "::offering" segment in This way we'd still have the ability to configure a known offer stream of images for Ubuntu, without bloating integration-settings.py options with yet another config param. In the absence of offer-name, we'd assume For other distro support, I think we may have to rethink how we use pycloudlib.cloud.ImageType and maybe rename that OfferType to better align with how clouds label separate product images from vendors. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. After spending some time on this proposal. I can reject my suggestion for optional
For these reasons, I think it makes sense to stick with a new |
||
|
||
# Populate if you want to use a pre-launched instance instead of | ||
# creating a new one. The exact contents will be platform dependent | ||
EXISTING_INSTANCE_ID: Optional[str] = None | ||
|
@@ -47,6 +58,7 @@ | |
# IMAGE GENERATION SETTINGS | ||
################################################################## | ||
|
||
|
||
# Depending on where we are in the development / test / SRU cycle, we'll want | ||
# different methods of getting the source code to our SUT. Because of | ||
# this there are a number of different ways to initialize | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where do these names come from? I assume that this is a pycloudlib construct? Can we please include a pointer to wherever in pycloudlib this is documented to ease future maintenance of this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These come from the ImageType enum in pycloudlib. (
pycloudlib.cloud.ImageType
)