Skip to content

Latest commit

 

History

History
247 lines (217 loc) · 8.7 KB

README.md

File metadata and controls

247 lines (217 loc) · 8.7 KB
Raw

Workload-stress

Workload for stress testing.
The repository contains Helm Charts that allow running Jobs in Kubernetes for stress-testing the cluster.

Usage

The application allows you to generate load on CPU, memory and MinIO storage.

helm install workload-stress <helm-chart>
  --set arguments.time=<duration of the load, sec.>
  --set arguments.cpu=<CPU load percentage, %>
  --set arguments.ram=<RAM load percentage, %>
  --set arguments.minioHost=<URL MinIO API, localhost:9000 by default>
  --set arguments.minioAccessKey=<your_access_key>
  --set arguments.minioSecretKey=<your_secret_key>
  --set arguments.minioBucketCount=<number of buckets>
  --set arguments.minioFileCount=<number of files>
  --set arguments.minioMinSize=<minimum file size, MB>
  --set arguments.minioMaxSize=<maximum file size, MB>
  --set arguments.storageProccessCount=<number of proccess>
  --set arguments.storageFileCount=<number of files>
  --set arguments.storageMinSize=<minimum file size, MB>
  --set arguments.storageMaxSize=<maximum file size, MB>

By changing the parameters you can simulate different types of loads.

  1. CPU load is generated by performing mathematical operations on all cores.
  2. RAM load is created by writing a large amount of information into RAM.
  3. The load on the MinIO storage is managed as follows:
  • A specified number of buckets minioBucketCount is created.
  • A specified number of files minioFileCount with random sizes from the range [minioMinSize, minioMaxSize] is generated. The first file is created in the first bucket, the second file in the second bucket, and so on. If there are more files than buckets, the next file is stored again in the first bucket and so on.
  • The load is generated by moving all files from the current bucket to the next one in a circular manner. If the current file is in the last bucket, the next move for that file will be to the first bucket and so on.
  1. The storage load is generated by creating and reading storageFileCount files with random sizes from the range [minioMinSize, minioMaxSize] across storageProcessCount processes.

Example:

helm repo add workload-stress-repo https://hiro-microdatacenters-bv.github.io/workload-stress/helm-charts/
helm repo update
helm search repo workload-stress
helm install workload-stress workload-stress-repo/workload-stress
  --set arguments.time=30
  --set arguments.cpu=80
  --set arguments.ram=80
  --set arguments.minioHost=localhost:9000
  --set arguments.minioAccessKey=<your_access_key>
  --set arguments.minioSecretKey=<your_secret_key>
  --set arguments.minioBucketCount=3
  --set arguments.minioFileCount=5
  --set arguments.minioMinSize=1
  --set arguments.minioMaxSize=10
  --set arguments.storageProccessCount=10
  --set arguments.storageFileCount=10
  --set arguments.storageMinSize=10
  --set arguments.storageMaxSize=100

Development

Prerequisites

Installation and running

  1. If you don't have Python installed run:

    Install Python 3.12 if it is not available in your package manager

    These instructions are for Ubuntu 22.04 and may not work for other versions.

    Also, these instructions are about using Poetry with Pyenv-managed (non-system) Python.

    Step 1: Update and Install Dependencies

    Before we install pyenv, we need to update our package lists for upgrades and new package installations. We also need to install dependencies for pyenv.

    Open your terminal and type:

    sudo apt-get update
sudo apt-get install -y make build-essential libssl-dev zlib1g-dev libbz2-dev \
libreadline-dev libsqlite3-dev wget curl llvm libncursesw5-dev xz-utils \
tk-dev libxml2-dev libxmlsec1-dev libffi-dev liblzma-dev

    Step 2: Install Pyenv

    We will clone pyenv from the official GitHub repository and add it to our system path.

    git clone https://github.com/pyenv/pyenv.git ~/.pyenv
echo 'export PYENV_ROOT="$HOME/.pyenv"' >> ~/.bashrc
echo 'export PATH="$PYENV_ROOT/bin:$PATH"' >> ~/.bashrc
echo 'eval "$(pyenv init -)"' >> ~/.bashrc
exec "$SHELL"

    For additional information visit official docs

    Step 3: Install Python 3.12

    Now that pyenv is installed, we can install different Python versions. To install Python 3.12, use the following command:

    pyenv install 3.12

    Step 4: Connect Poetry to it

    Do this in the template dir. Pycharm will automatically connect to it later

    poetry env use ~/.pyenv/versions/3.12.1/bin/python

    (change the version number accordingly to what is installed)

    Finally, verify that Poetry indeed is connected to the proper version:

    poetry enf info

  2. If you don't have Poetry installed run:

pipx install poetry
  1. Install dependencies:
poetry config virtualenvs.in-project true
poetry install --no-root --with dev,test
  1. Install pre-commit hooks:
poetry run pre-commit install
  1. Launch the project:
poetry run python main.py
  1. Running tests:
poetry run pytest

Manual build and deployment on Minikube

  1. Install Minikube.
  2. Install MinIO.
  3. Start Minikube:
minikube start
  1. Create minio-dev.yaml file contains the following Kubernetes resources:
apiVersion: v1
kind: Pod
metadata:
  labels:
    app: minio
  name: minio
  namespace: default
spec:
  containers:
  - name: minio
    image: quay.io/minio/minio:latest
    command:
    - /bin/bash
    - -c
    args: 
    - minio server /mnt/disk1/minio-data --console-address :9090
    volumeMounts:
    - mountPath: /mnt/disk1/minio-data
      name: localvolume
  nodeSelector:
    kubernetes.io/hostname: minikube
  volumes:
  - name: localvolume
    hostPath:
      path: /mnt/disk1/minio-data
      type: DirectoryOrCreate
  1. Apply minio-dev.yaml:
kubectl apply -f minio-dev.yaml
  1. Forward ports:
kubectl port-forward minio 9000:9000
kubectl port-forward minio 9090:9090
  1. Open UI MinIO (login is minioadmin, password is minioadmin) and create access and secret keys on the page Access Keys.
  2. Build a docker image:
docker build . -t workload-stress:latest
  1. Upload the docker image to minikube:
minikube image load workload-stress:latest
  1. Deploy the job:
helm install workload-stress ./charts/workload-stress
  --version 0.1.0
  --set image.repository=workload-stress
  --set image.tag=latest
  --set arguments.time=30
  --set arguments.cpu=80
  --set arguments.ram=80
  --set arguments.minioHost=localhost:9000
  --set arguments.minioAccessKey=<your_access_key>
  --set arguments.minioSecretKey=<your_secret_key>
  --set arguments.minioBucketCount=3
  --set arguments.minioFileCount=5
  --set arguments.minioMinSize=1
  --set arguments.minioMaxSize=10
  --set arguments.storageProccessCount=10
  --set arguments.storageFileCount=10
  --set arguments.storageMinSize=10
  --set arguments.storageMaxSize=100

Release

To create a release, add a tag in GIT with the format a.a.a, where 'a' is an integer.

git tag 0.1.0
git push origin 0.1.0

The release version for branches, pull requests, and other tags will be generated based on the last tag of the form a.a.a.

Helm Chart Versioning

The Helm chart version changed automatically when a new release is created. The version of the Helm chart is equal to the version of the release.

GitHub Actions

GitHub Actions triggers testing and builds for each release.

Initial setup
Create the branch gh-pages and use it as a GitHub page.

After execution

  • The index.yaml file containing the list of Helm Charts will be available at https://hiro-microdatacenters-bv.github.io/workload-stress/helm-charts/index.yaml.
  • The Docker image will be available at https://github.com/orgs/hiro-microdatacenters-bv/packages?repo_name=workload-stress.

Collaboration guidelines

HIRO uses and requires from its partners GitFlow with Forks

License

MIT