Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Katello 4.15 release docs #3451

Open
wants to merge 1 commit into
base: 3.13
Choose a base branch
from

Conversation

ianballou
Copy link
Contributor

What changes are you introducing?

Adding release docs for Katello 4.15 so we can get RC1 out.

Copy link
Member

@ekohl ekohl left a comment

Choose a reason for hiding this comment

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

Some stylistic suggestions, but overall 👍


[id="katello-upgrade-warnings"]
== Upgrade Warnings

There are no upgrade warnings with Katello {KatelloVersion}.
Container content users will want to run 'foreman-maintain advanced procedure run pulpcore-container-handle-image-metadata' to pre-migrate data to avoid a lengthy migration in the future. There will be multiple releases to allow this before it is mandatory.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Container content users will want to run 'foreman-maintain advanced procedure run pulpcore-container-handle-image-metadata' to pre-migrate data to avoid a lengthy migration in the future. There will be multiple releases to allow this before it is mandatory.
Container content users will want to run `foreman-maintain advanced procedure run pulpcore-container-handle-image-metadata` to pre-migrate data to avoid a lengthy migration in the future.
There will be multiple releases to allow this before it is mandatory.


=== Multiple content view environments for hosts and activation keys

Hosts and (new in 4.15) activation keys can now be associated with multiple content view environments. To use this feature, turn on the allow_multiple_content_views Setting.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Hosts and (new in 4.15) activation keys can now be associated with multiple content view environments. To use this feature, turn on the allow_multiple_content_views Setting.
Hosts and (new in 4.15) activation keys can now be associated with multiple content view environments. To use this feature, turn on the `allow_multiple_content_views` Setting.

=== Multiple content view environments for hosts and activation keys

Hosts and (new in 4.15) activation keys can now be associated with multiple content view environments. To use this feature, turn on the allow_multiple_content_views Setting.
Multi-environment hosts and activation keys are displayed in the web UI, but currently can only be changed via Hammer. Use the new --content-view-environments or --content-view-environment-ids options in hammer activation-key create and hammer activation-key update.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Multi-environment hosts and activation keys are displayed in the web UI, but currently can only be changed via Hammer. Use the new --content-view-environments or --content-view-environment-ids options in hammer activation-key create and hammer activation-key update.
Multi-environment hosts and activation keys are displayed in the web UI, but currently can only be changed via Hammer. Use the new `--content-view-environments` or `--content-view-environment-ids` options in `hammer activation-key create` and `hammer activation-key update`.


Hosts and (new in 4.15) activation keys can now be associated with multiple content view environments. To use this feature, turn on the allow_multiple_content_views Setting.
Multi-environment hosts and activation keys are displayed in the web UI, but currently can only be changed via Hammer. Use the new --content-view-environments or --content-view-environment-ids options in hammer activation-key create and hammer activation-key update.
To display multi-environment hosts in the new All Hosts list page, click 'Manage columns' and add the 'Content view environments' column. The existing content view and lifecycle environment columns will still work, but will only display the host's first content view environment.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
To display multi-environment hosts in the new All Hosts list page, click 'Manage columns' and add the 'Content view environments' column. The existing content view and lifecycle environment columns will still work, but will only display the host's first content view environment.
To display multi-environment hosts in the new All Hosts list page, click **Manage columns** and add the **Content view environments** column.
The existing content view and lifecycle environment columns will still work, but will only display the host's first content view environment.

To display multi-environment hosts in the new All Hosts list page, click 'Manage columns' and add the 'Content view environments' column. The existing content view and lifecycle environment columns will still work, but will only display the host's first content view environment.
You can also set content view environments from a registered host with subscription-manager environments --set.
You can now view a list of available content view environments with a new Hammer command, hammer content-view-environment list.
Multi-environment information is now displayed in hammer host info and hammer activation-key info.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Multi-environment information is now displayed in hammer host info and hammer activation-key info.
Multi-environment information is now displayed in `hammer host info` and `hammer activation-key info`.

=== Pulpcore upgraded to 3.63

Pulpcore has been upgraded to 3.63, which brings bug fixes and new features that Katello can integrate with.
As an example, the new Pulp Container now has container image compressed size and OS information available for Katello to show.
Copy link
Member

Choose a reason for hiding this comment

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

The RH style guide suggests writing out operating system (see eec780f as well). Perhaps good to apply that?

Suggested change
As an example, the new Pulp Container now has container image compressed size and OS information available for Katello to show.
As an example, the new Pulp Container now has container image compressed size and operating system information available for Katello to show.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants