Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-16073

Document Network Flow Matrix -- Cloudops DFG

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • documentation
    • None
    • Document Network Flow Matrix
    • False
    • Hide

      None

      Show
      None
    • False
    • RHOSSTRAT-591Document RHOSO Network Flow Matrix (aka Firewall Rules Guide)
    • Not Selected
    • Proposed
    • Proposed
    • To Do
    • RHOSSTRAT-591 - Document RHOSO Network Flow Matrix (aka Firewall Rules Guide)
    • Proposed
    • Proposed

      In OSP 17.1, we document the network flows used by OpenStack, and provide a very detailed flow csv file that customers can use to build/manage/secure their network traffic flows: 

      https://docs.redhat.com/en/documentation/red_hat_openstack_platform/17.1/html-single/firewall_rules_for_red_hat_openstack_platform/index#network-flow-matrix

      We need to provide a similar document for RHOSO 18.0, with the extra burden of the OpenShift cluster. We should have:

      • Minimum traffic flow of the base OCP cluster (or link to the corresponding documentation in OCP)
      • Traffic flow of the control plane pods
      • Traffic flow of the compute nodes
      • Traffic flow in between control plane and compute nodes

      Please have your DFG (cloudops) review RHOSO 18.0 Flow Matrix Draft 1.

      Find the rows that apply to your DFG/area of expertise and verify the rows or delegate the task to someone. As you do so, please fill in the DFG and Verified by name/date columns. Feel free to fill in the DFG column if you know what DFG should look at a row. That will help.

      If you make a change to a value in a cell, please change the text color of that cell to red. Feel free to use the Reviewer notes column (col M). 
      If you think we're missing a service, add a row and render the text as red and add a note in the Reviewer notes column. For example we might need some new rows based on adoption. 

      If you can't verify or fix any value, use the Reviewer notes column to explain/ask.

      Consider using Jira sub-tasks if you need to share this task among multiple squads.

              rhn-engineering-mrunge Matthias Runge
              jjung@redhat.com JP Jung
              rhos-conplat-observability
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: