#20 - merge traffic generation work from csr

Author: obriensystems

README.md

@@ -12,5 +12,56 @@ start/stop thread http://127.0.0.1:8888/nbi/forward/reset
 - message
 - timestamps
   - node
-  - timestanp
+  - timestamp
+
+# Example Google Cloud Run
+
+HTTPS support is added via Google Cloud Run
+
+source swagger: https://traffic-generation-source-vyua7q27tq-nn.a.run.app/nbi/swagger-ui.html#/application-service-controller/getHealthUsingGET_1
+source: https://traffic-generation-source-vyua7q27tq-nn.a.run.app/nbi/api
+
+target: https://traffic-generation-target-vyua7q27tq-pd.a.run.app/nbi/api
+
+Traffic gen API: 
+```
+https://traffic-generation-source-vyua7q27tq-nn.a.run.app/nbi/swagger-ui.html#/forwarding-controller/getPacketUsingGET
+
+source
+
+https://traffic-generation-source-vyua7q27tq-nn.a.run.app/nbi/forward/packet?delay=1000&dnsFrom=traffic-generation-source-vyua7q27tq-nn.a.run.app&dnsTo=traffic-generation-target-vyua7q27tq-pd.a.run.app&from=80&to=80
+
+curl -X GET "https://traffic-generation-source-vyua7q27tq-nn.a.run.app/nbi/forward/packet?delay=1000&dnsFrom=traffic-generation-source-vyua7q27tq-nn.a.run.app&dnsTo=traffic-generation-target-vyua7q27tq-pd.a.run.app&from=80&to=80" -H "accept: */*"
+
+target
+
+https://traffic-generation-target-vyua7q27tq-pd.a.run.app/nbi/forward/packet?delay=1000&dnsFrom=traffic-generation-target-vyua7q27tq-pd.a.run.app&dnsTo=traffic-generation-source-vyua7q27tq-nn.a.run.app&from=80&to=80
+
+
+## Traffic Generation
+
+2 copies of the traffic gen containers are currently running on cloud run until I move them over to the GKE cluster.
+The health check doubles as the target REST endpoint for now.
+Note: HTTPS termination is on the cloud run gateway - if we don't terminate on the API Gateway and/or the LB fronting the GKE cluster then I'll add a self signed to the app - for now we use the Google cert for https.
+
+CICD
+Currently there is a CSR trigger on cloud build to run the maven build and build/push the container into artifact registry.  The cloud run builds are static but can be switched to trigger.  I expect we can add a trigger on the cloud deploy job once I have moved the container to GKE.
+
+To view - open swagger or use direct curls or the browser
+https://traffic-generation-source-vyua7q27tq-nn.a.run.app/nbi/swagger-ui.html#/forwarding-controller/getTrafficUsingGET
+enter for example 120k 1ms traffic https://traffic-generation-source-vyua7q27tq-nn.a.run.app/nbi/forward/traffic?delay=1&dns=traffic-generation-target-vyua7q27tq-pd.a.run.app&iterations=120000&to=80 
+
+view the metrics on both source and target.  These requests have no real load on the backend (db marshall/unmarshall as part of orm) therefore 1k requests/sec only scales a smaller than normal 1g/1vCore container up to 3 instances.  Once we get backend load scaling should occur with over 1k req/sec traffic
+
+https://console.cloud.google.com/run/detail/northamerica-northeast1/traffic-generation-source/metrics
+
+https://console.cloud.google.com/run/detail/northamerica-northeast2/traffic-generation-target/metrics
+
+
+# local development testing in cloud shell
+curl -X GET "http://127.0.0.1:8080/nbi/forward/traffic?dns=127.0.0.1&to=8080&delay=1000&iterations=20"
+
+curl -X GET  "http://127.0.0.1:8080/nbi/forward/reset"
+```
+
 

cloudbuild.yaml

@@ -28,9 +28,5 @@ images:
   ["northamerica-northeast1-docker.pkg.dev/$PROJECT_ID/traffic-generation/traffic-generation:latest"]
 
 
-  #ERROR: failed to find one or more images after execution of build steps: ["gcr.io/innovapost-351413/magellan-nbi:latest"]
-#options:
-#  logging: CLOUD_LOGGING_ONLY
-# [END cloudbuild_maven]