Uploaded image for project: 'OpenShift SDN'
  1. OpenShift SDN
  2. SDN-1838

Split out network-diagnostics from the CNO

    XMLWordPrintable

Details

    • Story
    • Resolution: Obsolete
    • Undefined
    • None
    • None
    • None
    • None
    • 8
    • False
    • False
    • Hide
      * The network-diagnostics controller (currently coded in the CNO) should be included in the network-tools repo.
      * The network-tools Dockerfile will need to be modified to execute the network-diagnostics controller
      * The CNO should deploy the network-diagnostics controller from the network-tools image
      Show
      * The network-diagnostics controller (currently coded in the CNO) should be included in the network-tools repo. * The network-tools Dockerfile will need to be modified to execute the network-diagnostics controller * The CNO should deploy the network-diagnostics controller from the network-tools image
    • OCPPLAN-6007 - OpenShift Core Networking Improvements
    • Undefined
    • SDN Sprint 207
    • 0
    • 0.0

    Description

      We should split out the network-diagnostics controller from the CNO and incorporate it in the network-tools, as such we would be able to have a daemonset which launches a dedicated set of scripts existing in the network-tools image and then proceeds to launching the network-diagnostics controller. This would allow us to automatically log which network dependent rpms are on the node - during upgrades we would be able to compare version N to N+1 and verify that the rpm versions match what we expect.  

       

      This would also mean that in the CNO we re-write the deployment spec currently existing for the network-diagnostics component to specify the scripts we want to launch when the components starts.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              aconstan1@redhat.com Alexander Constantinescu Birhala (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: