-
Notifications
You must be signed in to change notification settings - Fork 276
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.
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
[ci] Manual trigger workflow to start Load testing #3734
Comments
after talking with Vasily and Ekaterina, they came to the following implementation postpone automatic deployment by commit the product will be deployed manually - responsible Vasily Zyabkin
Longevity booth remains in current configuration with current features Deploy two virtual machines outside of k8s in the same geographic area as longevity stand
|
We have:
|
Feature request
Need a trigger with manual dispatch that takes the current
iroha2-dev
andiroha2-stable
and deploys it on a k8s cluster with 4 peers. The peers are physically separated.Important Not all builds of the
java
SDK are compatible with all builds ofiroha2-dev
and sometimes not all builds ofiroha2-stable
.Then we deploy
gatling
as tuned by @timofeevmd, with theiroha-java
SDK, and Grafana + Graphite.Gatling should be pointed at the peers in the k8s cluster, the cluster must pass initial consensus and monitoring for all machines should be done to at least gather the
RAM + CPU +
optional
prometheus
metrics.Gatling also needs RAM + CPU monitoring.
The Graphite needs to be ran on a separate machine to prevent a cascading failure.
Motivation
Need load testing to know about Iroha's performance metrics and behaviour under a stress load.
Who can help?
No response
The text was updated successfully, but these errors were encountered: