update_service: Add docs for the OpenShift Update Service #29630
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jottofar
requested review from
aburdenthehand,
codyhoag,
jeana-redhat and
vikram-redhat
as code owners
openshift-ci-robot
added
the
size/L
|
✔️ Deploy Preview for osdocs ready! 🔨 Explore the source changes: 5558a0e 🔍 Inspect the deploy log: https://app.netlify.com/sites/osdocs/deploys/60ba41c89124710007591278 😎 Browse the preview: https://deploy-preview-29630--osdocs.netlify.app |
jottofar
force-pushed
the
update-service-doc
branch
from
02542f1 to
abef79d
Compare
openshift-ci-robot
added
size/XL
jottofar
force-pushed
the
update-service-doc
branch
7 times, most recently
from
bfb053a to
d6c54be
Compare
bobfuru
force-pushed
the
update-service-doc
branch
from
9843707 to
5558a0e
Compare
|
New changes are detected. LGTM label has been removed. |
bobfuru
reviewed
Jun 4, 2021
Contributor
bobfuru
left a comment
bobfuru
left a comment
There was a problem hiding this comment.
I have squashed all commits and will merge and CP back to 4.6. Upon completion, I will open a new PR for docs peer review feedback.
Contributor
|
/cherrypick enterprise-4.8 |
Contributor
|
/cherrypick enterprise-4.7 |
Contributor
|
/cherrypick enterprise-4.6 |
|
@bobfuru: new pull request created: #33070 DetailsIn 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 kubernetes/test-infra repository. |
|
@bobfuru: new pull request created: #33071 DetailsIn 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 kubernetes/test-infra repository. |
|
@bobfuru: #29630 failed to apply on top of branch "enterprise-4.6": DetailsIn 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 kubernetes/test-infra repository. |
bobfuru
reviewed
Jun 4, 2021
| component Operators. The edges in the graph show which versions you can safely | ||
| update to, and the vertices are update payloads that specify the intended state | ||
| of the managed cluster components. | ||
| The OpenShift Update Service (OSUS) is the service that provides over-the-air updates to both {product-title} and {op-system-first}. It provides a graph, or diagram, that contains _vertices_ and the _edges_ that connect them, of component Operators. The edges in the graph show which versions you can safely update to, and the vertices are update payloads that specify the intended state of the managed cluster components. |
Contributor
There was a problem hiding this comment.
Looks like we only refer to the initialism in this one spot, so I'm removing OSUS because elsewhere in the PR it's always spelled out.
Member
There was a problem hiding this comment.
We mention OSUS in other places like in the container image metadata etc. It would be a good idea to say that OSUS stands for OpenShift update service.
Contributor
There was a problem hiding this comment.
Ah, good point. I've added it back in, thanks.
wking
added a commit
to wking/openshift-docs
that referenced
this pull request
Jul 27, 2021
…the release image
We can't use:
$ oc adm release mirror ...
to split the release image out into LOCAL_RELEASE_IMAGES_REPOSITORY,
because oc does not currently understand mirroring. So there's no way
to tell it "the referenced images you're looking for are actually in
${LOCAL_REGISTRY}/${TEMP_REPOSITORY}", and it fails with:
error: unable to connect to quay.io/openshift-release-dev/ocp-v4.0-art-dev: Get "https://quay.io/v2/"...
error: an error occurred during planning
Instead, send the images from disk directly to the target repositoy
for referenced images, and then use 'oc image mirror' again to copy
the release image over to the release-image repository without
worrying about referenced images. We still need the release images in
that separate repository to avoid Cincinnati consuming excessive
memory trying to load referenced-image layers as if they were release
images [1,2].
I've also softened some REMOVABLE_MEDIA_PATH wording. The important
point is that REMOVABLE_MEDIA_PATH points to where the removable media
is mounted for both commands, not that you use the same path string.
For example, maybe you mounted to /mnt/a on your external machine, and
then mounted that media to /mnt/b on your internal machine. You'd
want to use /mnt/b for REMOVABLE_MEDIA_PATH when mirroring from disk,
not /mnt/a.
[1]: openshift#29630 (comment)
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=1850781
openshift-cherrypick-robot
pushed a commit
to openshift-cherrypick-robot/openshift-docs
that referenced
this pull request
Jul 28, 2021
…the release image
We can't use:
$ oc adm release mirror ...
to split the release image out into LOCAL_RELEASE_IMAGES_REPOSITORY,
because oc does not currently understand mirroring. So there's no way
to tell it "the referenced images you're looking for are actually in
${LOCAL_REGISTRY}/${TEMP_REPOSITORY}", and it fails with:
error: unable to connect to quay.io/openshift-release-dev/ocp-v4.0-art-dev: Get "https://quay.io/v2/"...
error: an error occurred during planning
Instead, send the images from disk directly to the target repositoy
for referenced images, and then use 'oc image mirror' again to copy
the release image over to the release-image repository without
worrying about referenced images. We still need the release images in
that separate repository to avoid Cincinnati consuming excessive
memory trying to load referenced-image layers as if they were release
images [1,2].
I've also softened some REMOVABLE_MEDIA_PATH wording. The important
point is that REMOVABLE_MEDIA_PATH points to where the removable media
is mounted for both commands, not that you use the same path string.
For example, maybe you mounted to /mnt/a on your external machine, and
then mounted that media to /mnt/b on your internal machine. You'd
want to use /mnt/b for REMOVABLE_MEDIA_PATH when mirroring from disk,
not /mnt/a.
[1]: openshift#29630 (comment)
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=1850781
openshift-cherrypick-robot
pushed a commit
to openshift-cherrypick-robot/openshift-docs
that referenced
this pull request
Jul 28, 2021
…the release image
We can't use:
$ oc adm release mirror ...
to split the release image out into LOCAL_RELEASE_IMAGES_REPOSITORY,
because oc does not currently understand mirroring. So there's no way
to tell it "the referenced images you're looking for are actually in
${LOCAL_REGISTRY}/${TEMP_REPOSITORY}", and it fails with:
error: unable to connect to quay.io/openshift-release-dev/ocp-v4.0-art-dev: Get "https://quay.io/v2/"...
error: an error occurred during planning
Instead, send the images from disk directly to the target repositoy
for referenced images, and then use 'oc image mirror' again to copy
the release image over to the release-image repository without
worrying about referenced images. We still need the release images in
that separate repository to avoid Cincinnati consuming excessive
memory trying to load referenced-image layers as if they were release
images [1,2].
I've also softened some REMOVABLE_MEDIA_PATH wording. The important
point is that REMOVABLE_MEDIA_PATH points to where the removable media
is mounted for both commands, not that you use the same path string.
For example, maybe you mounted to /mnt/a on your external machine, and
then mounted that media to /mnt/b on your internal machine. You'd
want to use /mnt/b for REMOVABLE_MEDIA_PATH when mirroring from disk,
not /mnt/a.
[1]: openshift#29630 (comment)
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=1850781
openshift-cherrypick-robot
pushed a commit
to openshift-cherrypick-robot/openshift-docs
that referenced
this pull request
Jul 28, 2021
…the release image
We can't use:
$ oc adm release mirror ...
to split the release image out into LOCAL_RELEASE_IMAGES_REPOSITORY,
because oc does not currently understand mirroring. So there's no way
to tell it "the referenced images you're looking for are actually in
${LOCAL_REGISTRY}/${TEMP_REPOSITORY}", and it fails with:
error: unable to connect to quay.io/openshift-release-dev/ocp-v4.0-art-dev: Get "https://quay.io/v2/"...
error: an error occurred during planning
Instead, send the images from disk directly to the target repositoy
for referenced images, and then use 'oc image mirror' again to copy
the release image over to the release-image repository without
worrying about referenced images. We still need the release images in
that separate repository to avoid Cincinnati consuming excessive
memory trying to load referenced-image layers as if they were release
images [1,2].
I've also softened some REMOVABLE_MEDIA_PATH wording. The important
point is that REMOVABLE_MEDIA_PATH points to where the removable media
is mounted for both commands, not that you use the same path string.
For example, maybe you mounted to /mnt/a on your external machine, and
then mounted that media to /mnt/b on your internal machine. You'd
want to use /mnt/b for REMOVABLE_MEDIA_PATH when mirroring from disk,
not /mnt/a.
[1]: openshift#29630 (comment)
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=1850781
openshift-cherrypick-robot
pushed a commit
to openshift-cherrypick-robot/openshift-docs
that referenced
this pull request
Jul 28, 2021
…the release image
We can't use:
$ oc adm release mirror ...
to split the release image out into LOCAL_RELEASE_IMAGES_REPOSITORY,
because oc does not currently understand mirroring. So there's no way
to tell it "the referenced images you're looking for are actually in
${LOCAL_REGISTRY}/${TEMP_REPOSITORY}", and it fails with:
error: unable to connect to quay.io/openshift-release-dev/ocp-v4.0-art-dev: Get "https://quay.io/v2/"...
error: an error occurred during planning
Instead, send the images from disk directly to the target repositoy
for referenced images, and then use 'oc image mirror' again to copy
the release image over to the release-image repository without
worrying about referenced images. We still need the release images in
that separate repository to avoid Cincinnati consuming excessive
memory trying to load referenced-image layers as if they were release
images [1,2].
I've also softened some REMOVABLE_MEDIA_PATH wording. The important
point is that REMOVABLE_MEDIA_PATH points to where the removable media
is mounted for both commands, not that you use the same path string.
For example, maybe you mounted to /mnt/a on your external machine, and
then mounted that media to /mnt/b on your internal machine. You'd
want to use /mnt/b for REMOVABLE_MEDIA_PATH when mirroring from disk,
not /mnt/a.
[1]: openshift#29630 (comment)
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=1850781
emarcusRH
pushed a commit
to emarcusRH/openshift-docs
that referenced
this pull request
Oct 28, 2021
…the release image
We can't use:
$ oc adm release mirror ...
to split the release image out into LOCAL_RELEASE_IMAGES_REPOSITORY,
because oc does not currently understand mirroring. So there's no way
to tell it "the referenced images you're looking for are actually in
${LOCAL_REGISTRY}/${TEMP_REPOSITORY}", and it fails with:
error: unable to connect to quay.io/openshift-release-dev/ocp-v4.0-art-dev: Get "https://quay.io/v2/"...
error: an error occurred during planning
Instead, send the images from disk directly to the target repositoy
for referenced images, and then use 'oc image mirror' again to copy
the release image over to the release-image repository without
worrying about referenced images. We still need the release images in
that separate repository to avoid Cincinnati consuming excessive
memory trying to load referenced-image layers as if they were release
images [1,2].
I've also softened some REMOVABLE_MEDIA_PATH wording. The important
point is that REMOVABLE_MEDIA_PATH points to where the removable media
is mounted for both commands, not that you use the same path string.
For example, maybe you mounted to /mnt/a on your external machine, and
then mounted that media to /mnt/b on your internal machine. You'd
want to use /mnt/b for REMOVABLE_MEDIA_PATH when mirroring from disk,
not /mnt/a.
[1]: openshift#29630 (comment)
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=1850781
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This doc is required for errata https://errata.devel.redhat.com/errata/details/67040.