WIP: AGENT-601: support for okd-scos

[andfasano]

This is PoC to explore the required changes to support okd-scos for agent-based installer.

Notes:

• The scos.json is identical to the previous fcos.json except for x86_64 metal iso
• The extraction of the base ISO from machine-os-images has been excluded because not yet available for scos, so using a direct download (that would be required for disconnected installs)

[openshift-ci-robot]

@andfasano: This pull request references AGENT-601 which is a valid jira issue.

In response to this:

This is PoC to explore the required changes to support okd-scos for agent-based installer.

The scos.json is identical to the previous fcos.json except for x86_64 metal iso

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[andfasano]

/draft

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign sdodson for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@andfasano: This pull request references AGENT-601 which is a valid jira issue.

In response to this:

This is PoC to explore the required changes to support okd-scos for agent-based installer.

Notes:

• The scos.json is identical to the previous fcos.json except for x86_64 metal iso
• The extraction of the base ISO from machine-os-images has been excluded because not yet available for scos, so using a direct download (that would be required for disconnected installs)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[LorbusChris]

Suggested change

	fcosTAG = "okd"
	scosTAG = "scos"
	okdTag = "okd"
	fcosTAG = "fcos"
	scosTAG = "scos"

the okd and fcos Go build tags used elsewhere in the installer are synonymous. Let's add an okdTAG here and treat it like fcosTAG.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-merge-robot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[LorbusChris]

We're not going to add an scos.json that references SCOS bootimages in the near term, as we don't currently have any distribution channels for these boot images.
We might revisit this once:

• tooling to derive bootimages from ostree containers has been built out (Create tooling to take a FCOS-derived container and generate bootable images from it coreos/fedora-coreos-tracker#1151, https://gitlab.com/CentOS/cloud/sagano-builder)
• bootimages are distributed as OCI artifacts through OCI registries

Voting to close this PR.

[andfasano]

We're not going to add an scos.json that references SCOS bootimages in the near term, as we don't currently have any distribution channels for these boot images. We might revisit this once:

* tooling to derive bootimages from ostree containers has been built out ([Create tooling to take a FCOS-derived container and generate bootable images from it coreos/fedora-coreos-tracker#1151](https://github.com/coreos/fedora-coreos-tracker/issues/1151), https://gitlab.com/CentOS/cloud/sagano-builder)

* bootimages are distributed as OCI artifacts through OCI registries

Voting to close this PR.

Not a problem, as this PR was meant just to explore the ABI gaps to support OKD scos. Is there any documentation available about the current distribution?

[openshift-ci]

@andfasano: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/okd-e2e-aws-ovn-upgrade	eda97a6	link	false	/test okd-e2e-aws-ovn-upgrade
ci/prow/e2e-agent-sno-ipv6	eda97a6	link	false	/test e2e-agent-sno-ipv6
ci/prow/e2e-agent-ha-dualstack	eda97a6	link	false	/test e2e-agent-ha-dualstack
ci/prow/e2e-aws-ovn	eda97a6	link	true	/test e2e-aws-ovn
ci/prow/okd-e2e-aws-ovn	eda97a6	link	false	/test okd-e2e-aws-ovn
ci/prow/altinfra-images	eda97a6	link	true	/test altinfra-images
ci/prow/terraform-images	eda97a6	link	true	/test terraform-images
ci/prow/terraform-verify-vendor	eda97a6	link	true	/test terraform-verify-vendor

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.