Speeding Up Pulling Container Images/CRI-O Additional Storage Support#110809
Speeding Up Pulling Container Images/CRI-O Additional Storage Support#110809mburke5678 wants to merge 9 commits intoopenshift:mainfrom
Conversation
openshift-ci
Bot
added
the
size/L
|
/retest |
saschagrunert
left a comment
saschagrunert
left a comment
There was a problem hiding this comment.
Reviewed against the openshift/api types, MCO implementation (helpers.go), CRI-O PR cri-o/cri-o#9702, the Red Hat developer blog post, and the Jira epics (OCPSTRAT-2623, OCPSTRAT-1285, OCPNODE-4051). Main issues: copy-paste error in the definition list terms, wrong assembly path/context, missing CRI-O artifacts/ subdirectory convention, and the :ref suffix description should be scoped to layer stores only (not image stores). The :ref auto-append by MCO is the agreed approach but depends on the openshift/machine-config-operator#5858 rework landing.
|
|
||
| For example, large OCI artifacts, such as machine learning models, are stored on the default location, consuming space and preventing the use of faster dedicated storage. By configuring the `additionalArtifactStores` parameter, you can store large AI/ML models on high-performance storage (SSD) separate from the root file system space storage. As a result, your workloads can experience faster start times and your clusters can use storage more efficiently. | ||
|
|
||
| Also, you could use the `additionalImageStores` parameter to mount an NFS share with pre-populated images across all worker nodes. Nodes read from the shared cache instead of pulling from an external registry. This is useful in a disconnected environments or when many nodes run the same workloads. |
There was a problem hiding this comment.
Grammar: "in a disconnected environments"
| Also, you could use the `additionalImageStores` parameter to mount an NFS share with pre-populated images across all worker nodes. Nodes read from the shared cache instead of pulling from an external registry. This is useful in a disconnected environments or when many nodes run the same workloads. | |
| Also, you could use the `additionalImageStores` parameter to mount an NFS share with pre-populated images across all worker nodes. Nodes read from the shared cache instead of pulling from an external registry. This is useful in disconnected environments or when many nodes run the same workloads. |
| sh-5.1# chroot /host | ||
| ---- | ||
|
|
||
| .. For an artifact store, look at the contents of the `etc/crio/crio.conf.d/01-ctrcfg-additionalArtifactStores` directory: |
There was a problem hiding this comment.
This is a file, not a directory. Also missing leading / in the path.
| .. For an artifact store, look at the contents of the `etc/crio/crio.conf.d/01-ctrcfg-additionalArtifactStores` directory: | |
| .. For an artifact store, look at the contents of the `/etc/crio/crio.conf.d/01-ctrcfg-additionalArtifactStores` file: |
There was a problem hiding this comment.
Ugh. I saw that, meant to circle back and fix it, but forgot apparently!
|
@BhargaviGudi PTAL. Thank you! |
|
@mburke5678: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
4 participants
OSDOCS-19406
OSDOCS-19402
Link to docs preview:
QE review: