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

Incorporate dedicated host level scripts in the network-diagnostic hostNetwork:true daemonset

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Obsolete
    • Icon: Undefined Undefined
    • None
    • None
    • SDN Core
    • None
    • 5
    • False
    • False
    • Hide
      * The network-diagnostics component running hostNetwork: true should be initialized by running a set of scripts retrieving host level network configuration - network related rpms, sysctl settings, ethtool output, etc. That should be logged to stdout so that we can retrieve the information in the pod logs when reading a must-gather.
      Show
      * The network-diagnostics component running hostNetwork: true should be initialized by running a set of scripts retrieving host level network configuration - network related rpms, sysctl settings, ethtool output, etc. That should be logged to stdout so that we can retrieve the information in the pod logs when reading a must-gather.
    • OCPPLAN-6007 - OpenShift Core Networking Improvements
    • Undefined
    • 0
    • 0.0

      As a user of OpsnShift I want to be able to tell if my underlying network is providing a solid foundation for my SDN.

      I also want to be sure that my SDN is performing correctly.

      We need to make sure there is an easy way to see the node-to-node performance numbers across the cluster.  We also need to see if we can alert on bad underlay performance (without too many false positives) and we need to see if we can push any meaningful metrics up to insights (can we do a median and a standard distribution across nodes?)

            Unassigned Unassigned
            bbennett@redhat.com Ben Bennett
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: