Skip to content
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

mantle/api: gcloud: remove FCOS specific image GuestOSFeatures #1333

Conversation

dustymabe
Copy link
Member

We consider the VIRTIO_SCSI_MULTIQUEUE, UEFI_COMPATIBLE,
and SECURE_BOOT flags to be standard now so we can
unconditionally add them to GCP images we create and get
rid of the --fcos option.

@dustymabe
Copy link
Member Author

This is a follow-up from #1319 (comment)

We consider the VIRTIO_SCSI_MULTIQUEUE, UEFI_COMPATIBLE,
and SECURE_BOOT flags to be standard now so we can
unconditionally add them to GCP images we create and get
rid of the --fcos option.
@dustymabe dustymabe force-pushed the dusty-gcp-ore-no-more-fcos-flag branch from 7b4045b to 6e2ab0f Compare April 9, 2020 17:08
@dustymabe dustymabe changed the title mantle/ore: glcoud: remove --fcos option from upload mantle/api: gcloud: remove FCOS specific image GuestOSFeatures Apr 9, 2020
@cgwalters
Copy link
Member

cgwalters commented Apr 9, 2020

LGTM...I wrote all this stuff below then changed my mind, just attaching it for reference.


I'm OK with this, though I think I'd vote instead we:

  • change the argument to default to true in ore
  • remove the arg from cosa

The idea here is it's slightly more convenienent for someone testing something interactively w/ore to pass --fcos=false or so than to hack the source. But

@dustymabe
Copy link
Member Author

Note that AFAICT this will change the defaults for the RHCOS pipeline. I'm guessing that openshift/installer#2921 only changes it at runtime when the instance is launched.

@cgwalters
Copy link
Member

Note that AFAICT this will change the defaults for the RHCOS pipeline. I'm guessing that openshift/installer#2921 only changes it at runtime when the instance is launched.

No, as you discovered in internal chat, the openshift installer today always creates the image in GCP. That's precisely why that PR was needed (and indeed works without this one).

@bgilbert
Copy link
Contributor

bgilbert commented Apr 9, 2020

/lgtm

Thanks for the cleanup!

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bgilbert, dustymabe

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit a6329fa into coreos:master Apr 9, 2020
@dustymabe dustymabe deleted the dusty-gcp-ore-no-more-fcos-flag branch May 9, 2020 03:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants