Open
Conversation
jsc#DOCTEAM-1775
a501f66 to
5e3f1f0
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR creator: Description
At long last, here are the articles for managing resources and constraints. Sorry it's such a big PR; the content was too inter-related to split up.
These aren't the most ideal Smart Docs, but this generic content does need to exist as it's the foundation of how to use the product. I will be doing plenty of focused articles on specific tasks later.
PDFs:
Configuring HA Cluster Resources: HA-resources-configuring_en.pdf
Adding Constraints to HA Cluster Resources: HA-resources-adding-constraints_en.pdf
Managing HA Cluster Resources: HA-resources-managing_en.pdf
Note that the crmsh/Hawk procedures appear one after the other in the PDFs, but in the published HTML they'll look like this:
This was the the smoothest solution I could see for having two methods to do things; having a separate topic for each method would blow out to way too many topics to reasonably keep track of.
Tasks for later:
There was more I still wanted to do, but I can't keep working on one PR forever, so I split some things off for later. If a topic seems to be missing, it might be in this list:
PR creator: Are there any relevant issues/feature requests?
PR reviewer: Checklist for editorial review
Apart from the usual checks, please double-check also the following: