-
Epic
-
Resolution: Unresolved
-
Critical
-
rhos-18.0.14 FR 4
-
None
-
Document Keystone Adoption LDAP support
-
M
-
False
-
-
False
-
Not Selected
-
Proposed
-
Proposed
-
Done
-
RHOSSTRAT-853 - Keystone Adoption LDAP support
-
Proposed
-
rhos-docs
-
Proposed
-
100% To Do, 0% In Progress, 0% Done
-
-
-
This adoption is a Top item for the Security DFG in FR4 that is currently in Progress and will be done fr FR4, see the comments below for where the LDAP Adoption documentation has been merged.
Mini Content Journey
Reviewers:
- Technical: Grzegorz Grasza
- Peer:
- QE: Jeremy Agee
Is this feature fully supported or technical preview?
- Full support: Documentation will be published on the customer portal
Does the procedural content need to be tested by QE?
- Yes: QE needs to create a doc testing ticket per How-to Jira with the docs team
Does the documentation epic need a release note in addition to the feature?
- No: The engineering feature or epic might still need a release note. Engineers need to follow the guidance set in[ _ How-to Jira with the docs team|https://spaces.redhat.com/display/RHOSPDOC/How-to-Jira+with+the+RHOS+docs+team].{_}
What stage of the user journey are you targeting?
- Adopt: Adoption or Greenfield feature (Early stage customer use)
Who is your target persona?
- OpenStack user: SysAdmin or Developer
What type of information does the user need to know in order to use the feature?
- Procedures or considerations for upgrades, adoption, or minor updates
Are there any existing upstream or internal resources that the writer can use for planning and drafting the content? Consider the situational context of the existing content. Do a Google search for any possible resources that might help.
- The PR is merged and needs to be verified by QE: https://github.com/openstack-k8s-operators/data-plane-adoption/pull/980
Does the content require input from multiple DFGs?
- No: Stories are not required unless the epic needs to be divided to user stories that can be delivered separately (for personal use, consider sub-tasks instead)
Does the content need to be included in any of the following guides?
- No