Skip to content

Conversation

kowen-rh
Copy link
Contributor

@kowen-rh kowen-rh commented Mar 7, 2022

Solution/Idea

Add documentation for the use and configuration of container runtime presets.

Note that this PR also contains the introduction of the {openshift} and {ocp} attributes and fixes a few small errors I encountered while updating the content. These changes have all been isolated to their own commits.

Proposed changes

  1. Add a new module to conceptually define presets.
  2. Add a new module for configuring the desired preset.
  3. Modify the minimum system requirements to reflect the resources needed by each preset.
  4. Modify crc setup documentation to include information about selecting the podman preset for Linux users.

kowen-rh added 2 commits March 7, 2022 11:48
This will help us avoid any unfortunate typos.

This commit does not replace instances of the term "OpenShift" in the
documentation at this time. This will be addressed in the future.
@kowen-rh kowen-rh added the status/peer review required Peer review by assignee is required before being merged; label Mar 7, 2022
@openshift-ci openshift-ci bot requested review from anjannath and gbraad March 7, 2022 18:22
@openshift-ci openshift-ci bot added the approved label Mar 7, 2022

[role="_abstract"]
{prod} presets represent a managed container runtime and the lower bounds of system resources required by the instance to run it.
{prod} offers presets for {ocp} and the Podman container runtime.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no variable for Podman?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't see the need to create one. The attributes for OpenShift largely exist to avoid unfortunate typos when the "f" key is missed. ;)

If we foresee the name of Podman itself (or the podman preset) to change, we should probably create an attribute for it.

====
You cannot change the preset of an existing {prod} instance.
Preset changes are only applied when a {prod} instance is created.
To enable preset changes, you must delete the existing instance and start a new one.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure how this will stand out in the documentation. It briefly touches on 'delete'. Will have to check the rendered version.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I placed the content under an "important" admonition to (hopefully) encourage careful reading of it. Do you think we should make this more visible somehow?

gbraad
gbraad previously requested changes Mar 8, 2022
Copy link
Contributor

@gbraad gbraad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall OK, but perhaps the M1 support should not be mentioned
This is better suited for a blog post.

@bburt-rh
Copy link

bburt-rh commented Mar 8, 2022

Approved

@kowen-rh
Copy link
Contributor Author

kowen-rh commented Mar 8, 2022

@gbraad Addressed Brian's concerns and the M1 support (just reverted back to our original wording). Are there any other requested changes?

@gbraad gbraad dismissed their stale review March 9, 2022 00:42

Approved

@openshift-ci openshift-ci bot added the lgtm label Mar 9, 2022
@openshift-ci
Copy link

openshift-ci bot commented Mar 9, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gbraad, robin-owen

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:

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

@praveenkumar praveenkumar merged commit 4aa2dad into crc-org:main Mar 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved lgtm status/peer review required Peer review by assignee is required before being merged;

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants