-
Notifications
You must be signed in to change notification settings - Fork 69
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Add clusterName as parameter to create cluster workflow * Add clusterName as a parameter to Run Benchmark workflow * Add clusterName as a parameter to Delete ROSA cluster workflow * Add docs for dispatch-able workflows * Address PR comments * Change concurrency to per clusterName
- Loading branch information
Showing
5 changed files
with
59 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
# Running workflows for keycloak-benchmark repository on AWS | ||
|
||
## Create secrets and variables | ||
|
||
1. Go to repository Settings -> Secrets and variables | ||
2. Create new secret `AWS_ACCESS_KEY_ID` with value of your AWS access key id. | ||
3. Create new secret `AWS_SECRET_ACCESS_KEY` with value of your AWS access key value. | ||
4. Create new secret `ROSA_TOKEN` with value of your ROSA token. See [Red Hat OpenShift Cluster Manager API](https://cloud.redhat.com/openshift/token) for more information. | ||
5. Create new variable `AWS_REGION` with value of your preferred AWS region, for example, `eu-central-1`. | ||
|
||
## Create cluster | ||
|
||
1. Go to repository Actions -> On the left side choose `ROSA Cluster - Create` | ||
2. Click on Run workflow button | ||
3. Fill in the form and click on Run workflow button | ||
1. Name of the cluster - the name of the cluster that will be later used for other workflows. Default value is `gh-${{ github.repository_owner }}`, this results in `gh-<owner of fork>`. | ||
2. Instance type for compute nodes - see [AWS EC2 instance types](https://aws.amazon.com/ec2/instance-types/). Default value is `m5.xlarge`. | ||
3. Deploy to multiple availability zones in the region - if checked, the cluster will be deployed to multiple availability zones in the region. Default value is `false`. | ||
4. Number of worker nodes to provision - number of compute nodes in the cluster. Default value is `2`. | ||
4. Wait for the workflow to finish. | ||
|
||
## Destroy cluster | ||
|
||
1. Go to repository Actions -> On the left side choose `ROSA Cluster - Destroy` | ||
2. Click on Run workflow button | ||
3. Fill in the form and click on Run workflow button | ||
1. Name of the cluster - the name of the cluster to destroy. Default value is `gh-${{ github.repository_owner }}`, this results in `gh-<owner of fork>`. | ||
4. Wait for the workflow to finish. | ||
|
||
## Run benchmark | ||
|
||
1. Go to repository Actions -> On the left side choose `ROSA Cluster - Run Benchmark` | ||
2. Click on Run workflow button | ||
3. Fill in the form and click on Run workflow button | ||
1. Name of the cluster - the name of the cluster that will be used for running benchmark. Default value is `gh-${{ github.repository_owner }}`, this results in `gh-<owner of fork>`. | ||
4. The workflow will perform the following steps | ||
1. Connect to the cluster | ||
2. Provision new Keycloak instance including monitoring stack. | ||
3. Create dataset with 1 realm, 1 client and 100 users. | ||
4. Run Keycloak benchmark with `keycloak.scenario.authentication.AuthorizationCode` scenario. | ||
5. Wait for the workflow to finish. The Gatling results will be available in the `artifacts` section of the workflow run. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters