Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

additional test dimensions in lifecycle test environment #43

Closed
7 of 9 tasks
siggy opened this issue May 23, 2018 · 1 comment
Closed
7 of 9 tasks

additional test dimensions in lifecycle test environment #43

siggy opened this issue May 23, 2018 · 1 comment
Assignees
@siggy
Labels
benchmarking Performance testing in progress

Comments

@siggy
Copy link
Member

siggy commented May 23, 2018 •
edited
Loading

The test environment introduced in #41, intended to exercising route, telemetry, and
service discovery lifecycles in Conduit, includes the following:

  • conduit control + data plane
  • 1 slow-cooker, 100qps
  • 10 HTTP point-to-point servers
  • 10 gRPC terminus servers, with container restart every 600 requests (~1 minute)

We should extend this environment to exercise additional dimensions, namely:

The Prometheus Benchmark Grafana dashboard introduced in linkerd/linkerd2#984 should provide better performance analysis of Prometheus in Conduit.

Relates to #42.
@siggy siggy self-assigned this May 23, 2018
siggy added a commit that referenced this issue May 24, 2018
@siggy
Delete entire pods in lifecycle environment
d15938f 
The lifecycle environment was testing service discovery via bb-terminus
container exit. This did not play well with k8s's `CrashLoopBackoff`.

Disable bb-terminus container exit in favor of a `redeployer` script,
that deletes each bb-terminus pod once per minute.

Fixes #42, relates to #43.

Signed-off-by: Andrew Seigner <siggy@buoyant.io>
@siggy siggy mentioned this issue May 24, 2018
Merged
siggy added a commit that referenced this issue May 24, 2018
@siggy
Delete entire pods in lifecycle environment
0e14e43 
The lifecycle environment was testing service discovery via bb-terminus
container exit. This did not play well with k8s's `CrashLoopBackoff`.

Disable bb-terminus container exit in favor of a `redeployer` script,
that deletes each bb-terminus pod once per minute. Also create
`ServiceAccount`, `ClusterRole`, and `ClusterRoleBinding`, and install
conduit into conduit-lifecycle namespace.

Fixes #42, relates to #43.

Signed-off-by: Andrew Seigner <siggy@buoyant.io>
siggy added a commit that referenced this issue May 24, 2018
@siggy
Introduce dynamic scaling of lifecycle env
2fb5421 
Introduce scaling of lifecycle env, via a `deploy` script that deploys N
number of lifecycle namespaces, and also via a `scale` script that
increases the number of replicas per namespace. Also change slow-cooker
from a Job to a Deployment.

Part of #43.

Signed-off-by: Andrew Seigner <siggy@buoyant.io>
@siggy siggy mentioned this issue May 24, 2018
Merged
siggy added a commit that referenced this issue Jul 3, 2018
@siggy
Redeploy bb-terminus deployment in lifecycle env
8d5857a 
The lifecycle test env redeployed pods and services.

Introduce redeployment of entire deployments.

Part of #43.

Signed-off-by: Andrew Seigner <siggy@buoyant.io>
@siggy siggy mentioned this issue Jul 3, 2018
Merged
siggy added a commit that referenced this issue Jul 3, 2018
@siggy
Redeploy bb-terminus deployment in lifecycle env
e237345 
The lifecycle test env redeployed pods and services.

Introduce redeployment of entire deployments. Also introduce TLS.

Part of #43.

Signed-off-by: Andrew Seigner <siggy@buoyant.io>
siggy added a commit that referenced this issue Jul 4, 2018
@siggy
Redeploy bb-terminus deployment in lifecycle env
cfddf78 
The lifecycle test env redeployed pods and services.

Introduce redeployment of entire deployments. Also introduce TLS.

Part of #43.

Signed-off-by: Andrew Seigner <siggy@buoyant.io>
siggy added a commit that referenced this issue Jul 6, 2018
@siggy
Introduce baseline namespaces into lifecycle env
1caf310 
The existing lifecycle test environment runs a set of applications
injected with Conduit.

This change introduces a parallel set of applications that run without
Conduit, to enable comparison.

Part of #43.

Signed-off-by: Andrew Seigner <siggy@buoyant.io>
siggy added a commit that referenced this issue Jul 6, 2018
@siggy
Introduce baseline namespaces into lifecycle env
cf43492 
The existing lifecycle test environment runs a set of applications
injected with Conduit.

This change introduces a parallel set of applications that run without
Conduit, to enable comparison.

Part of #43.

Signed-off-by: Andrew Seigner <siggy@buoyant.io>
@siggy siggy mentioned this issue Jul 6, 2018
Merged
siggy added a commit that referenced this issue Jul 10, 2018
@siggy
Introduce baseline and TLS configs to lifecycle
9e982d1 
The existing lifecycle test environment runs a set of applications
injected with Conduit.

This change introduces a parallel set of applications that run without
Conduit, to enable comparison, along with a TLS-enabled config.

Part of #43.

Signed-off-by: Andrew Seigner <siggy@buoyant.io>
@siggy siggy mentioned this issue Jul 11, 2018
Closed
@siggy siggy added benchmarking Performance testing in progress labels Jul 25, 2018
@siggy siggy mentioned this issue Jul 27, 2018
Open
9 tasks
@siggy
Copy link
Member Author

siggy commented Jul 27, 2018

closing following repo move, new issue at: linkerd/linkerd-examples#225

@siggy siggy closed this as completed Jul 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@siggy siggy

Labels
benchmarking Performance testing in progress
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@siggy