-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
drop capability to specify image in install-config #1052
drop capability to specify image in install-config #1052
Conversation
None of the options, other than Image, that were in the Libvirt MachinePool were being used. They have been removed. The Image has been pulled up to the Libvirt Platform, as there was no way to use a different image for different machines pools. For consistency with the AWS and OpenStack platforms, the Libvirt MachinePool has been retained, even though it is empty. The DefaultMachinePlatform has been retained in the Libvirt Platform as well. The code in the Master Machines and Worker Machines assets that determines the configuration to use for the machines has been adjusted for Libvirt to rectify the machine-pool-specific configuration against the default machine-pool configuration. This is not strictly necessary as, again, the Libvirt configuration is empty. It keeps the logic consistent with the other platforms, though. https://jira.coreos.com/browse/CORS-911
8477a8b
to
d656937
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.
Changes look good.
Can we remove this function?
func (f realValidValuesFetcher) GetImageNames(cloud string) ([]string, error) { |
done with 83d9bf8 |
@@ -34,6 +35,7 @@ func (t *TerraformVariables) Name() string { | |||
func (t *TerraformVariables) Dependencies() []asset.Asset { | |||
return []asset.Asset{ | |||
&installconfig.InstallConfig{}, | |||
new(rhcos.Image), |
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.
Why is this not &rhcos.Image{}
like its neighbors? And the same elsewhere in this commit:
$ git show d65693719 | grep 'new('
+ new(rhcos.Image),
+ rhcosImage := new(rhcos.Image)
+ new(rhcos.Image),
+ rhcosImage := new(rhcos.Image)
+ new(rhcos.Image),
+ rhcosImage := new(rhcos.Image)
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.
https://play.golang.org/p/NUhwmraqAtM
prog.go:10:7: invalid pointer type *Image for composite literal
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.
0795a7c
to
2b24684
Compare
case libvirt.Name: | ||
osimage, err = rhcos.QEMU(ctx, rhcos.DefaultChannel) | ||
case openstack.Name: | ||
osimage = "rhcos" |
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.
This is much-simplified from the previous GetImageNames
you're removing in 83d9bf8d523. @hardys added that image-name select widget in #766, and sometimes OpenStack doesn't have reliable defaults (e.g. #788). Are we comfortable with a hard-coded value here, or do we need to retain some lookup logic or user input?
Yeah, my original thought was somebody seeing this commit of dropping image fields from InstallConfig might benefit from it... but i can move it if you like? |
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 have one OpenStack concern and one Git nit, but I'm still fine with this PR landing as it stands before we address those. We can always circle back to OpenStack post-freeze.
Maybe mention "in follow-up work" in the commit message? Or squash this PR down a bit, currently there are commits removing properties from structs before commits removing the property consumers and things like that. On the other hand, it's nice to see smaller pivots too. I don't really care either way at this stage ;). |
added OPENSHIFT_INSTALL_OS_IMAGE_OVERRIDE env with warning to override the image that will be used.
With baseimage user query removed from TUI, this function is no longer required. This also - drops the vendored files - updates the mocks using `hack/go-genmock.sh`
RHCOS image that needs to be used for installation must be sources from RHCOS build pipeline and RHCOS build. Keeping the image related fields in install-config allows users to change these values as part of valid configuration, but we do not want users to configure this option as the RHCOS image controls the runtime and kubelet versions we depend on.
2b24684
to
38e8cad
Compare
commit 38e8cad784a118df38ac4f0e10cffce70455a711 (HEAD -> drop_ami)
Author: Abhinav Dahiya <[email protected]>
Date: Fri Jan 11 13:02:55 2019 -0800
docs: update the resource dep graph
commit b07f23e0a2dafb889ac97087c78bcf4a303ddd68
Author: Abhinav Dahiya <[email protected]>
Date: Fri Jan 11 10:33:15 2019 -0800
types: drop image options from install config for all platforms
RHCOS image that needs to be used for installation must be sources from RHCOS build pipeline and RHCOS build.
Keeping the image related fields in install-config allows users to change these values as part of valid configuration, but we do not want users to configure this option as
the RHCOS image controls the runtime and kubelet versions we depend on.
commit 255566fa916bd1e40e8b9e5b3ec688105afc32d0
Author: Abhinav Dahiya <[email protected]>
Date: Fri Jan 11 12:51:22 2019 -0800
types/openstack: drop GetImageNames method
With baseimage user query removed from TUI, this function is no longer required.
This also
- drops the vendored files
- updates the mocks using `hack/go-genmock.sh`
commit 94d99583dd7d65e6a6812485c82eadab1ffd6b97
Author: Abhinav Dahiya <[email protected]>
Date: Fri Jan 11 11:17:33 2019 -0800
asset/installconfig: drop image related code paths
commit 3eb958b278b67acc616c56d76b1ec85e17fcb5dd
Author: Abhinav Dahiya <[email protected]>
Date: Fri Jan 11 10:42:49 2019 -0800
pkg: use rhcos Image to fetch ami for AWS
commit 2bd6c9d1293bab2d7b50046d61f7d385c0588054
Author: Abhinav Dahiya <[email protected]>
Date: Fri Jan 11 10:41:46 2019 -0800
asset: add rhcos Image asset to generate image location
added OPENSHIFT_INSTALL_OS_IMAGE_OVERRIDE env with warning to override the image that will be used. @wking does this look more appropriate? i'm changing all consumers first then dropping the property..? |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, wking The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
e2e-aws had lots of:
ending up with:
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
The `baseImage` option is no longer doing anything: openshift/installer#1052 The image must be called `rhcos`.
Breaking change for Hive. :( But the env var should cover us for now. Will raise in arch call about how we should handle this image ID long term, across upgrades, in an external system like Hive. |
includes commit from #812
RHCOS image that needs to be used for installation must be sources from RHCOS build pipeline and RHCOS build.
Keeping the image related fields in install-config allows users to change these values as part of valid configuration, but we do not want users to configure this option as
the RHCOS image controls the runtime and kubelet versions we depend on.
added
OPENSHIFT_INSTALL_OS_IMAGE_OVERRIDE
env with warning to override the image that will be used./cc @crawford @wking