Anuket Project

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »


Participants

Please add your name to the list

Antitrust policies

Action item register

Organisation topics

  • N/A

Technical topics

Containerization of traffic generators with Xtesting - Sridhar Rao

Notes

Discussion of traffic generators.  Where do they need to be installed?  They need to have additional tools installed either inside or outside the environment to test.  Need to deploy the tools (Rapid and Prox), then use K8S APIs to run the tests and collect results.  For this work the test results are pass/fail.  Stdout from "rapid" is additional results.  Should Anuket specify the mandatory service level – Potential approaches: Nodeport, LoadBalancer, External-IP.  So where

  • One approach
    • There is a need for an application to LCM the test framework pods (Rapid, Prox), collect the results and calculate the test results
    • If this application is outside of the cluster and uses the Kubernetes API-s
    • For this the integration between Rapid and Xtesting needs to be modified
    • Presentation of the output needs to be also changed
  • Maybe there are alternate approaches
    • If the complete Xtesting runs within the cluster the integration will be more easy
  • In RA2 there are no guidelines about what are the mandatory service types
    • E.g.: Nodeport, Loadbalancer, External IP
    • There is an RA2 issue about this: https://github.com/cntt-n/CNTT/issues/2453
    • The approach for SSH connection is not defined without this
      • Best candidate would be Loadbalancer, for this RA2 should add Loadbalancer as a mandatory service
    • There are tests about Ingress in the Kubernetes conformance test suite
    • We are not sure if KubeRef has Loadbalancer or External IP installed
    • This is a pre requisite for successful testing

AoB


  • No labels