-
Notifications
You must be signed in to change notification settings - Fork 26
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
Elemental validation and improvements when using SL Micro 6.0 #549
Conversation
e3bdf22
to
7030979
Compare
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.
Discussed offline - only putting out the conclusions for visibility.
- Switching up Elemental source requires a change to
artifacts.yaml
which also means some of the code here could (or would) be removed - Elemental RPMs shipped with SL Micro 6.0 are not latest yet and we're unable to rely on them at this point in time
- Validating empty directories should be part of Empty directory checks (such as custom scripts/files and rpms) should occur at validation, not build #276
Quick update: The proper RPMs are now available in the SL Micro 6.0 repo, so concern #2 from Atanas' comment is addressed. |
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.
I feel like this must land at this point... There's still no response from the ECM team.
Co-authored-by: Atanas Dinov <[email protected]>
Co-authored-by: Atanas Dinov <[email protected]>
Please drop the unused properties from |
7a103f6
to
be79636
Compare
RELEASE_NOTES.md
Outdated
@@ -9,6 +9,8 @@ | |||
* Added the ability to automatically copy files into the built images filesystem (see Image Configuration Directory Changes below) | |||
* Kubernetes manifests are now applied in a systemd service instead of using the `/manifests` directory | |||
* Helm chart installation backOffLimit changed from 1000(default) to 20 | |||
* Improved Elemental handling when using SL Micro 6.0 |
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.
Can we rephrase this and move it to the API section below? Elemental configuration now requires a registration code in order to install the necessary RPMs from the official sources
or something similar.
8841f71
to
3c01fa0
Compare
3c01fa0
to
dc86fa5
Compare
This PR changes the way Elemental is handled depending on the API Version of the image definition. The reason being: 1.1 only supports SL Micro 6.0 and 1.0 only supports 5.5 so we can operate under that assumption when working with Elemental.
What happens now is that when using 1.0, the Elemental handling is the same and it uses the repositories found in
artifacts.yaml
, however, when using 1.1, those repositories are no longer used and instead the necessary Elemental packages are found through RPM resolution inside of the SL Micro 6.0 image. This now means that when using Elemental with 6.0, you need to specify a package registration code.Additionally, to supplement this, I added validation for the Elemental configuration directory and for the registration code.