microshift
microshift copied to clipboard
openshift
NO-ISSUE: Port bootc build procedure to directly use mirror registry instead of local storage
The functional changes include:
- Consolidation of Web and Registry URL definition using VM bridge interface, or host name if libvirt is not configured
- Mirror registry script uses an external storage and configuration file
- Bootc containerfile and container encapsulate builds save artifacts to the mirror registry directly bypassing file system export.
- Mirror registry startup is implicit when running bootc builds
These changes should result in reduced resource consumption and reduced runtime of the builds.
Test prerequisites
- Delete
_output sudo podman rmi -af && podman rmi -af && podman volume rm -af- Run
./test/bin/build_rpms.shand download cache. - Compare bootc build times and disk space
Test results on AWS c5n.metal host
- Registry creation of 1m is included in the build time and 34G of disk saved.
- Registry recreation is fast due to external persistent storage
| What | Before | After |
|---|---|---|
| Bootc build time | 10m | 10m |
| Create mirror reg | 1.5m | 20s |
| sudo podman df | 11G | 11G |
| podman df | 16G | 0G |
| _output du | 53G | 35G |
@ggiguash: This pull request explicitly references no jira issue.
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.
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[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@ggiguash: The following commands are available to trigger required jobs:
/test e2e-aws-footprint-and-performance/test e2e-aws-tests/test e2e-aws-tests-arm/test e2e-aws-tests-bootc/test e2e-aws-tests-bootc-arm/test e2e-aws-tests-bootc-periodic/test e2e-aws-tests-bootc-periodic-arm/test e2e-aws-tests-cache/test e2e-aws-tests-cache-arm/test e2e-aws-tests-periodic/test e2e-aws-tests-periodic-arm/test images/test ocp-full-conformance-rhel-eus/test ocp-full-conformance-rhel-eus-arm/test ocp-full-conformance-serial-rhel-eus/test ocp-full-conformance-serial-rhel-eus-arm/test test-rpm/test test-unit/test verify
The following commands are available to trigger optional jobs:
/test test-rebase
Use /test all to run the following jobs that were automatically triggered:
pull-ci-openshift-microshift-main-e2e-aws-testspull-ci-openshift-microshift-main-e2e-aws-tests-armpull-ci-openshift-microshift-main-e2e-aws-tests-bootcpull-ci-openshift-microshift-main-e2e-aws-tests-bootc-armpull-ci-openshift-microshift-main-e2e-aws-tests-bootc-periodicpull-ci-openshift-microshift-main-e2e-aws-tests-bootc-periodic-armpull-ci-openshift-microshift-main-e2e-aws-tests-periodicpull-ci-openshift-microshift-main-e2e-aws-tests-periodic-armpull-ci-openshift-microshift-main-imagespull-ci-openshift-microshift-main-test-unitpull-ci-openshift-microshift-main-verify
In response to this:
/test ?
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.
@ggiguash: This pull request references USHIFT-4704 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:
The functional changes include:
- Consolidation of Web and Registry URL definition using VM bridge interface, or host name if libvirt is not configured
- Mirror registry script uses an external storage and configuration file
- Bootc containerfile and container encapsulate builds save artifacts to the mirror registry directly bypassing file system export.
- Mirror registry startup is implicit when running bootc builds
- Mirror registry is no longer optional
These changes should result in reduced resource consumption and reduced runtime of the builds.
Test prerequisites
- Delete
_outputsudo podman rmi -af && podman rmi -af && podman volume rm -af- Run
./test/bin/build_rpms.shand download cache.- Compare bootc build times and disk space
Test results on AWS
c5n.metalhost
- Registry creation of 1m is included in the build time and 34G of disk saved.
- Registry recreation is fast due to external persistent storage
What Before After Bootc build time 10m 10m Create mirror reg 1.5m 20s sudo podman df 11G 11G podman df 16G 0G _output du 53G 35G
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.
@ggiguash: all tests passed!
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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ggiguash, pmtk
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [ggiguash,pmtk]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment