Support Service Mesh 2.0 on OSD

Splitting the epic into:

Repo work

Repository to support publishing via Pv2 for SM on OSD:

• Request Pv2 access for the SM team
  • Status: DONE - https://projects.engineering.redhat.com/browse/CCSOPS-739
• Request Pv2 enablement session with Andrew Dahms
  • Status: DONE
• Assess existing SM on OCP content for reuse for OSD
  • Status: WIP - Waiting on SM on OSD stories but we do have some initial information from Jamie to start with this.
• Create a new repo for hosting SM source to be published on OSD splash page

• • Status: WIP - ETA - 15 Feb
• Establish complete end-to-end workflow  for documenting and publishing SM on OSD docs via Pv2.
  • Status: TBD - This will be done after the repo is created.
• List is wip

Content work

• TOC
• Content
  • Strategy to reuse/duplicate content: Status - TBD - The reuse or duplicate strategy will depend on the commonalities between "SM on OCP" and "SM on OSD".  If we decide to opt for a new repo for SM on OSD, we would plan a phased approach to first create just the "SM on OSD" content to a separate repo and then move the "SM on OCP" content.
  • Assess any cross reference needs between SM on OSD and OSD docs - Need to check OSD stories and talk to Aly about this - TBD
  • List of "SM on OSD" docs - TBD - Waiting on SM on OSD user stories and list of end deliverables.
  • Draft the content - TBD - Will create task jiras for each deliverable.
• File changes to support Pantheon 2
  • Since we don't follow the FCC file naming convention....which is to pre-fix file names with assembly, con, proc, ref , we need a :_module-type:  tag at the top of every module that defines whether it is a concept, procedure, or reference.
  • Add _abstract and _additional-resources  tags to files.

• List is wip