XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • rhos-18.0.18 FR 5
    • rhos-18.0.14 FR 4
    • documentation
    • None
    • Document Proteccio HSM Adoption
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • RHOSSTRAT-946Feature - Proteccio HSM Adoption
    • Not Selected
    • ?
    • ?
    • To Do
    • RHOSSTRAT-946 - Feature - Proteccio HSM Adoption
    • ?
    • ?
    • DFG Security: Test Sprint 9
    • 1

      Goal: 

      Create a clear technical runbook for the RHOSO 18 Barbican and Eviden HSM integration, enabling the Operations team to independently manage and troubleshoot the configuration.

      Acceptance Criteria:

      • A final document detailing the full configuration and validation procedure is published in the company knowledge base.
      • The document has been reviewed and formally approved by both a technical peer and a member of the Operations team.

      Mini content journey

      Reviewers:

      • Technical: Mauricio Harley
      • Peer: To be determined.
      • QE: Jeremy Agee. He has more knowledge than Milana regarding HSMs. Jeremy can provision HSM-enabled environments for development and testing, and frequently visits data centers for physical tasks related to HSM devices.

      NOTE: This Epic does not relate to a feature in its own right, but instead is concerned with the documentation of the adoption of an existing feature - hence some of these questions are Not Applicable.

      Is this feature fully supported or technical preview? **

      • Not Applicable - this relates to the adoption of a fully-supported feature

      Does the procedural content need to be tested by QE?

      Does the documentation epic need a release note in addition to the feature?

      What stage of the user journey are you targeting?

      • Adopt: Adoption

      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 adoption

      Are there any existing upstream or internal resources that the writer can use for planning and drafting the content? 

      • No.

      Does the content require input from multiple DFGs?

      • No: Content is provided by the Security DFG, that will be incorporated into the relevant adoption guide.

      This content does not need to be included in any other guides apart from the Adoption guide.

              rhn-support-ifrangs Ian Frangs
              rh-ee-mharley Mauricio Harley
              rhos-dfg-security
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: