-
Notifications
You must be signed in to change notification settings - Fork 70
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
new butane variant: fedora-iot #487
Conversation
fad3e8a
to
b13dc89
Compare
I think you should add only the latest version as 1.0 and the experimental one as 1.1_exp. |
Why are you removing / renaming the R4E ones? You can not remove a config version once it's been released. |
Since we want butane to support both r4e and fedora-iot, so renaming the config path only for developer understanding. The end functionality and the variant names remains same. Do you see any other issue?
This is to make |
If it's the same thing, why duplicate everything? |
@travier So idea is both rfe and fedora-iot user can use butane with their respective os variant. Since
I understand this controls the variant name in the butane file which didn't change. @travier @prestist Can you please clarify how it will break for existing user? |
It feels to me that R4E variants should use version numbers based on RHEL releases where the first version config started being supported while the IoT ones should keep the 1.x version numbers as we don't have a strong "no-rebase" policy in Fedora and we land new Ignition spec support there as we go. |
The lifecycle for RHEL 4 Edge and Fedora IoT do not match and the Ignition spec versions supported for a given Fedora IoT release tells nothing for RHEL 4 Edge and vice versa, so having the same numbers will not get us much and might instead create confusion. |
Agreed, I will modify it accordingly. |
I've made #489 to track the R4E change. |
9fd761d
to
5dbd7cb
Compare
@travier made the changes as per the discussion. |
This is missing |
I think you are referring to the spec docs, updated them. |
eb576de
to
9a45a28
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.
LGTM
@say-paul Are the CI errors still valid? Looks like they are just |
590c508
to
1606137
Compare
Is there actually any "high level" sugar at all today in the r4e/fedora-iot versions? There's only a little bit for fedora-coreos around things like boot raid etc. I guess today we're disallowing partitioning in iot/edge? I wonder if it'd make sense to introduce a generic e.g. "generic-systemd" style variant that just is YAML sugar for writing files and systemd units basically... |
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.
Sorry this has been sitting for so long, and thank you for going through the steps to add a new variant. I do have a small nit on your commit message. I would prefer it be more like =>
Add new fiot variant for fedora-iot
Otherwise it lgtm
1606137
to
dd53201
Compare
@prestist done. |
To get past the ci "Test 1.21.x ..." you need to rebase and -f push. The ci was changed external to this pr. Otherwise from what I see this LGTM still. |
v1_0 is compatible with ignition 3.4.0 v1_1_exp is experimental version compatible with ignition 3.5.0 docs added for fiot Signed-off-by: Sayan Paul <[email protected]>
dd53201
to
fed77f6
Compare
@prestist done |
After speaking with @camgranella I am going to merge this as it lgtm! |
using the r4e config with
fiot
wrapperDocs added to include the new variant