USHIFT-4742: Bootc and ostree blueprint structure reorganization

[ggiguash]

Attempt to optimize and document ostree and bootc blueprint hierarchy.

CentOS image fetch will be removed as a follow-up in USHIFT-4868.
Bootc build times may be further optimized as a follow-up in USHIFT-4881 and USHIFT-4720

OSTree Summary
I could not make the overall build times faster. Layer 1 is the heaviest (~30m), but it's cached. Pre-submits and periodics take up to 10 and 15 minutes respectively.
I hope the "optimized" hierarchy is clearer and it is extensible if we add another OS version for instance.

Bootc Summary
Created a separate image-blueprints-bootc directory to be consistent with other bootc-specific sources.
The new hierarchy only results in a couple of minutes of time saving for builds, which are not significant. The main benefit atm is like for ostree - clear and extensible hierarchy.

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-4742 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to this:

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash

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:

• OWNERS [ggiguash]

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]

@ggiguash: This pull request references USHIFT-4742 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to this:

Attempt to optimize and document ostree and bootc blueprints. Note that CentOS image fetch will be removed as a follow-up in USHIFT-4868.

OSTree Summary
I could not make the overall build times faster. Layer 1 is the heaviest (~30m), but it's cached. Pre-submits and periodics take up to 10 and 15 minutes respectively.

Bootc Summary

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-4742 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to this:

Attempt to optimize and document ostree and bootc blueprint hierarchy.

CentOS image fetch will be removed as a follow-up in USHIFT-4868.

OSTree Summary
I could not make the overall build times faster. Layer 1 is the heaviest (~30m), but it's cached. Pre-submits and periodics take up to 10 and 15 minutes respectively.

Bootc Summary

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-4742 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to this:

Attempt to optimize and document ostree and bootc blueprint hierarchy.

CentOS image fetch will be removed as a follow-up in USHIFT-4868.

OSTree Summary
I could not make the overall build times faster. Layer 1 is the heaviest (~30m), but it's cached. Pre-submits and periodics take up to 10 and 15 minutes respectively.
I hope the "optimized" hierarchy is clearer and it is extensible if we add another OS version for instance.

Bootc Summary

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-4742 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to this:

Attempt to optimize and document ostree and bootc blueprint hierarchy.

CentOS image fetch will be removed as a follow-up in USHIFT-4868.
Bootc build times may be further optimized as a follow-up in USHIFT-4881

OSTree Summary
I could not make the overall build times faster. Layer 1 is the heaviest (~30m), but it's cached. Pre-submits and periodics take up to 10 and 15 minutes respectively.
I hope the "optimized" hierarchy is clearer and it is extensible if we add another OS version for instance.

Bootc Summary
Created a separate image-blueprints-bootc directory to be consistent with other bootc-specific sources.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-4742 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to this:

Attempt to optimize and document ostree and bootc blueprint hierarchy.

CentOS image fetch will be removed as a follow-up in USHIFT-4868.
Bootc build times may be further optimized as a follow-up in USHIFT-4881 and USHIFT-4720

OSTree Summary
I could not make the overall build times faster. Layer 1 is the heaviest (~30m), but it's cached. Pre-submits and periodics take up to 10 and 15 minutes respectively.
I hope the "optimized" hierarchy is clearer and it is extensible if we add another OS version for instance.

Bootc Summary
Created a separate image-blueprints-bootc directory to be consistent with other bootc-specific sources.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-4742 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to this:

Attempt to optimize and document ostree and bootc blueprint hierarchy.

CentOS image fetch will be removed as a follow-up in USHIFT-4868.
Bootc build times may be further optimized as a follow-up in USHIFT-4881 and USHIFT-4720

OSTree Summary
I could not make the overall build times faster. Layer 1 is the heaviest (~30m), but it's cached. Pre-submits and periodics take up to 10 and 15 minutes respectively.
I hope the "optimized" hierarchy is clearer and it is extensible if we add another OS version for instance.

Bootc Summary
Created a separate image-blueprints-bootc directory to be consistent with other bootc-specific sources.
The new hierarchy only results in a couple of minutes of time saving for builds, which are not significant. The main benefit atm is like for ostree - clear and extensible hierarchy.

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 openshift-eng/jira-lifecycle-plugin repository.

[pmtk]

I noticed that following is duplicated:

• test/image-blueprints/layer2-presubmit/group1/rhel94-source-with-optionals.toml
• test/image-blueprints/layer3-periodic/group1/rhel94-source-with-optionals.toml

Why do we need

• test/image-blueprints-bootc/layer1-base/group1/rhel94-bootc-base.containerfile
• test/image-blueprints-bootc/layer1-base/group2/rhel94-bootc.image-bootc

[ggiguash]

/test e2e-aws-tests-bootc

[ggiguash]

I noticed that following is duplicated:

• test/image-blueprints/layer2-presubmit/group1/rhel94-source-with-optionals.toml
• test/image-blueprints/layer3-periodic/group1/rhel94-source-with-optionals.toml

I removed the duplication, leaving the file in pre-submits

Why do we need

• test/image-blueprints-bootc/layer1-base/group1/rhel94-bootc-base.containerfile
• test/image-blueprints-bootc/layer1-base/group2/rhel94-bootc.image-bootc

The containerfile build a bootc layer, while .image-bootc is used to run bib for creating an ISO from that layer. Both are required.

[openshift-ci]

@ggiguash: The following test 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/security	8116dc6	link	false	/test security

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-sigs/prow repository. I understand the commands that are listed here.

[pmtk]

/lgtm