🥇Ngajalankeun tés JMeter di OpenShift nganggo Jenkins Pipeline

Hello dulur!

Dina artikel ieu abdi hoyong bagikeun salah sahiji cara pikeun ngajalankeun tés kinerja JMeter di OpenShift maké Jenkins salaku automation. Mimiti urang bakal ngalakukeun sagala léngkah anu diperyogikeun (nyieun ImageStreams, BuildConfig, Job jsb) dina modeu manual. Sanggeus éta, hayu urang nulis Jenkins Pipeline.

Salaku titik awal urang kedah gaduh:

ngajalankeun OpenShift (v3.11) klaster
Server Jenkins sareng kredensial anu dikonpigurasi pikeun damel di OpenShift
file apache-jmeter-5.2.tgz

Salaku tés bakal basajan HTTP Request dina ya.ru dina hiji aliran.

Nyieun proyék di OpenShift

Hayu urang mimitian ku nyieun lingkungan anyar. Hayu urang nyieun perftest dikurilingan ku tim:

$ oc new-project perftest --display-name="Performance Tests" --description="Performance Tests - JMeter"

Urang bakal otomatis dialihkeun ka lingkungan nu anyar dijieun perftest, hayu urang pariksa yén ieu téh:

$ oc project
Using project "perftest" on server "https://127.0.0.1:8443".

Nyiptakeun Panyimpenan

Laporan tés bakal disimpen sacara umum sareng pangladén wéb sareng jmeter-meter'tempat - /jmeter/reports.

Éta hadé nyieun Storajs ayeuna, sabab PODs bakal dihijikeun ka aranjeunna jmeter-web и jmeter-master.

Anjeun bakal mendakan inpormasi anu langkung rinci ngeunaan panyimpen dina dokuméntasi resmi Simpenan pengkuh.

Hayu urang nyieun file yaml pikeun PV и PVC.

pv.yaml

$ tee pv.yaml<<EOF
apiVersion: v1
kind: PersistentVolume
metadata:
  name: jmeter-reports
spec:
  capacity:
    storage: 10Gi
  accessModes:
    - ReadWriteMany
  glusterfs:
    endpoints: glusterfs-cluster
    path: /jmeter/reports
    readOnly: false
  persistentVolumeReclaimPolicy: Retain
EOF

pvc.yaml

$ tee pvc.yaml<<EOF
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: jmeter-reports
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 10Gi
EOF

Hayu urang nyieun PV и PVC dikurilingan ku OpenShift:

$ oc create -f pv.yaml -n perftest
$ oc create -f pvc.yaml -n perftest

Mariksa status pikeun PVC:

$ oc get pvc -n perftest
NAME             STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS        AGE
jmeter-reports   Bound     pvc-b0e5f152-db4b-11ea-a497-566f75280024   10Gi       RWX            glusterfs-storage   8m

Ieu kumaha éta bakal katingali dina GUI:

Nyiptakeun Gambar Dasar JMeter

Hayu urang ngaléngkah ka nyiptakeun ImageStream и BuildConfig.

Anjeun tiasa mendakan sadaya inpormasi anu diperyogikeun dina dokuméntasi - Ngawangun sareng Aliran Gambar.

Strategi ngawangun gambar nyaéta Docker ti sumber lokal.

Hayu urang nyieun gambar dasar jmeter-base, nu bakal jadi dadasar pikeun jmeter-master.

dockerfile

FROM openjdk:8u212-jdk

ARG JMETER_VER="5.2"
ENV JMETER_HOME /jmeter/apache-jmeter-$JMETER_VER
ENV PATH $JMETER_HOME/bin:$PATH

RUN mkdir -p /jmeter/results 
    && mkdir /jmeter/tests

WORKDIR /jmeter

COPY apache-jmeter-$JMETER_VER.tgz .

RUN tar -xzf $JMETER_HOME.tgz 
    && rm $JMETER_HOME.tgz 
    && ls -la

RUN sed -i s/#server.rmi.ssl.disable=false/server.rmi.ssl.disable=true/ $JMETER_HOME/bin/jmeter.properties

EXPOSE 60000

nyaéta.yaml

$ tee is.yaml<<EOF
apiVersion: v1
kind: ImageStream
metadata:
  labels:
    build: jmeter-base
  name: jmeter-base
EOF

bc.yaml

$ tee bc.yaml<<EOF
apiVersion: v1
kind: BuildConfig
metadata:
  name: jmeter-base
spec:
  failedBuildsHistoryLimit: 5
  nodeSelector: null
  output:
    to:
      kind: ImageStreamTag
      name: 'jmeter-base:latest'
  postCommit: {}
  resources: {}
  runPolicy: Serial
  source:
    binary: {}
    type: Binary
  strategy:
    dockerStrategy:
      from:
        kind: ImageStreamTag
        name: 'openjdk:8u212-jdk'
    type: Docker
  successfulBuildsHistoryLimit: 5
EOF

Hayu urang nyieun objék IS и BC:

$ oc create -f is.yaml -n perftest
$ oc create -f bc.yaml -n perftest

Ayeuna hayu urang ngumpul gambar dasar jmeter-base:

$ oc start-build jmeter-base -n perftest --from-dir=. --follow

JMeter WEB

jmeter-web Ieu mangrupikeun pangladén wéb Apache. Tugasna nyaéta nyayogikeun diréktori kalayan hasil tés pikeun ditingali.

Disayagikeun Dockerfile jeung file konfigurasi httpd.conf. Pikeun diréktif DocumentRoot set nilai /jmeter/reports, i.e. diréktori dimana hasil tés disimpen.

dockerfile

$ tee Dockerfile<<EOF
FROM httpd:2.4

COPY httpd.conf /usr/local/apache2/conf/httpd.conf
RUN chmod -R 777 /usr/local/apache2/logs

EXPOSE 8080

CMD ["httpd", "-D", "FOREGROUND"]
EOF

nyaéta.yaml

$ tee is.yaml<<EOF
apiVersion: v1
kind: ImageStream
metadata:
  generation: 1
  labels:
    build: jmeter-web
  name: jmeter-web
EOF

bc.yaml

$ tee bc.yaml<<EOF
apiVersion: v1
kind: BuildConfig
metadata:
  name: jmeter-web
spec:
  failedBuildsHistoryLimit: 5
  nodeSelector: null
  output:
    to:
      kind: ImageStreamTag
      name: 'jmeter-web:latest'
  runPolicy: Serial
  source:
    binary: {}
    type: Binary
  strategy:
    dockerStrategy:
      from:
        kind: ImageStreamTag
        name: 'httpd:2.4'
    type: Docker
  successfulBuildsHistoryLimit: 5
EOF

Hayu urang nyieun ImageStream и BuildConfig objék:

$ oc create -f is.yaml -n perftest
$ oc create -f bc.yaml -n perftest

Ngumpulkeun gambar tina Dockerfile:

$ oc start-build jmeter-web -n perftest --from-dir=. --follow

dc.yaml

$ tee dc.yaml<<EOF
apiVersion: apps.openshift.io/v1
kind: DeploymentConfig
metadata:
  name: jmeter-web
spec:
  replicas: 1
  template:
    metadata:
      labels:
        name: jmeter-web
    spec:
      containers:
        - image: 172.30.1.1:5000/perftest/jmeter-web
          name: jmeter-web
          volumeMounts:
            - mountPath: /jmeter/reports
              name: jmeter-reports
          ports:
            - containerPort: 80
              protocol: TCP
            - containerPort: 8080
              protocol: TCP
      volumes:
        - name: jmeter-reports
          persistentVolumeClaim:
            claimName: jmeter-reports
EOF

sc.yaml

$ tee sc.yaml<<EOF
apiVersion: v1
kind: Service
metadata:
  labels:
    app: jmeter-web
  name: jmeter-web
spec:
  ports:
    - name: 8080-tcp
      port: 8080
      protocol: TCP
      targetPort: 8080
  selector:
    deploymentconfig: jmeter-web
  sessionAffinity: None
  type: ClusterIP
EOF

Hayu urang nyieun objék Service и DeploymentConfig:

$ oc create -f sc.yaml -n perftest
$ oc create -f dc.yaml -n perftest

Jmeter-master

Hayu urang mimitian nyebarkeun pangladén wéb Apache.

Ieu teh Dockerfile jmeter-master'a, dumasar kana jmeter-base, anu bakal ngajalankeun tés sareng nyimpen hasil kana panyimpenan.

dockerfile

Dockerfile keur jmeter-master, dumasarkeun kana jmeter-base.

FROM jmeter-base

ARG JMETER_VER="5.2"
ENV JMETER_HOME /jmeter/apache-jmeter-$JMETER_VER
ENV PATH $JMETER_HOME/bin:$PATH

WORKDIR /jmeter
COPY run.sh /jmeter/
COPY tests/*.jmx /jmeter/tests/
RUN chmod +x /jmeter/run.sh

ENTRYPOINT ["/bin/bash"]
CMD ["/jmeter/run.sh"]

lumpat.sh

run.sh ieu naskah anu ngajalankeun JMeter tur nyimpen hasil kana diréktori a files.

Unggal waktos naskah diluncurkeun, éta ngahapus tés sateuacana, janten anjeun ngan ukur tiasa damel sareng data pangénggalna. Tapi ieu teu jadi masalah, sabab anjeun bisa ngarobah éta pikeun nyocogkeun ka kabutuhan Anjeun.

#!/bin/bash

set -e

if [ -d "/jmeter/reports/files" ]
then
    echo "Directory /jmeter/reports/files exist - OK"
else
    echo "Creating /jmeter/reports/files directory"
    mkdir /jmeter/reports/files
fi

if [ -d "/jmeter/reports/dashboards" ]
then
    echo "Directory /jmeter/reports/dashboards exist"
else
    echo "Creating /jmeter/reports/dashboards directory"
    mkdir /jmeter/reports/dashboards
fi

echo "*** JMeter START Tests ***"

for item in $(ls -1 /jmeter/tests | grep jmx)
do
    echo "*** Removing dashboard directory for $item"
    rm -rdf /jmeter/reports/dashboards/${item}*

    echo "*** Removing tests directory for $item"
    rm -rdf /jmeter/reports/files/${item}*

    echo "*** Testing a $item file ***"
    jmeter -n -t /jmeter/tests/${item} -l /jmeter/reports/files/${item}-report.jtl -e -o /jmeter/reports/dashboards/${item}-dash
done

nyaéta.yaml

$ tee is.yaml<<EOF
apiVersion: image.openshift.io/v1
kind: ImageStream
metadata:
  generation: 1
  labels:
    build: jmeter-master
  name: jmeter-master
EOF

bc.yaml

$ tee bc.yaml<<EOF
apiVersion: build.openshift.io/v1
kind: BuildConfig
metadata:
  name: jmeter-master
spec:
  failedBuildsHistoryLimit: 5
  nodeSelector: null
  output:
    to:
      kind: ImageStreamTag
      name: 'jmeter-master:latest'
  runPolicy: Serial
  source:
    binary: {}
    type: Binary
  strategy:
    dockerStrategy:
      from:
        kind: ImageStreamTag
        name: 'jmeter-base:latest'
    type: Docker
  successfulBuildsHistoryLimit: 5
EOF

Hayu urang nyieun IS и BC objék:

$ oc create -f is.yaml -n perftest
$ oc create -f bc.yaml -n perftest

Kami kumpulkeun jmeter-master gambar:

$ oc start-build jmeter-master -n perftest --from-dir=. --follow

tugas

Job's dipaké dina OpenShift'e guna ngajalankeun hiji atawa leuwih POD's sarta ngajamin parantosan suksés maranéhna sanggeus executing paréntah / naskah.

$ tee job.yaml<<EOF
apiVersion: batch/v1
kind: Job
metadata:
  name: jmeter-master
  labels:
    jobName: jmeter-master
spec:
  completions: 1
  parallelism: 1
  template:
    metadata:
      name: jmeter-master
      labels:
        jobName: jmeter-master
    spec:
      containers:
        - name: jmeter-master
          image: 172.30.1.1:5000/perftest/jmeter-master:latest
          volumeMounts:
            - mountPath: /jmeter/reports
              name: jmeter-reports
          imagePullPolicy: Always
      volumes:
        - name: jmeter-reports
          persistentVolumeClaim:
            claimName: jmeter-reports
      restartPolicy: Never
      terminationGracePeriodSeconds: 30
EOF

Jieun hiji obyék Job:

$ oc create -f job.yaml -n perftest

Hayu urang pariksa status pakasaban:

$ oc get jobs -n perftest
NAME            DESIRED   SUCCESSFUL   AGE
jmeter-master   1         1            5m

Pikeun mupus Job hayu urang nganggo paréntah:

$ oc delete jobs/jmeter-master -n perftest --ignore-not-found=true

Pipa Jenkins

Ayeuna automation. Hayu urang ngaliwat léngkah deui:

git clone
oc whoami -t
oc start-build ...
oc delete jobs/jmeter-master
oc create -f job.yaml -n perftest

Di handap ieu mangrupikeun pipa dimana kloning gudang, ngahapus sareng nyiptakeun OpenShift dilaksanakeun Joburang.

#!groovy

pipeline {

    agent any

    stages {

        stage('Start Notifications') {
            steps {
                echo "Sending Email Notification"
            }
            post {
                always {
                    echo "STARTED - Performance Tests"
                    mail(to: '[email protected]', from: "[email protected]", subject: "START - Performance Tests",mimeType: "text/html", body: "<strong>START - Performance Tests</strong><br /><br />Project: Name of Project<br />Environment: PerfTest<br />Build number: ${env.BUILD_NUMBER}<br />Build URL:   ${env.BUILD_URL}"
                }
            }
        }

        stage('Git checkout') {
            steps {
                ...
            }
        }

        stage('Perf Tests') {
            steps {
                script {
                    sh '''
                        OC_CMD1="oc login -u=username -p=PASS -n=perftest 
                        --server=https://...:8443"

                        $OC_CMD1

                        OC_TOKEN=`oc whoami -t`

                        OC_CMD2="oc --token=$OC_TOKEN --server=https://...:8443 
                        start-build jmeter-master -n=perftest --from-dir=./master 
                        --follow=true"

                        OC_CMD3="oc --token=$OC_TOKEN --server=https://...:8443 
                        delete jobs/jmeter-master -n=perftest --ignore-not-found=true"

                        OC_CMD4="oc--token=$OC_TOKEN --server=https://...:8443 
                        create -f ./master/job.yaml -n=perftest"

                        $OC_CMD2
                        $OC_CMD3
                        $OC_CMD4
                    '''
                }
            }
        }

        post {
            failure {
                echo "FAILED - Performance Tests"
                mail(to: '[email protected]', from: "[email protected]", subject: "FAILED - Performance Tests",mimeType: "text/html", body: "<strong>FAILED - Performance Tests</strong><br /><br />Project: Name of Project<br />Environment: PerfTest<br />Build number: ${env.BUILD_NUMBER}<br />Build URL: ${env.BUILD_URL}"
                }

            success {
                echo "SUCCESSED - Performance Tests"
                mail(to: '[email protected]', from: "[email protected]", subject: "SUCCESSED - Performance Tests",mimeType: "text/html", body: "<strong>SUCCESSED - Performance Tests</strong><br /><br />Project: Name of Project<br />Environment: PerfTest<br />Build number: ${env.BUILD_NUMBER}<br />Build URL:   ${env.BUILD_URL}"
            }
        }

    }
}

Saatos Pipeline parantos réngsé operasina, kami bakal nampi béwara ku email '[email protected] от [email protected].

Ku ngaklik dina link http://jmeter-web.127.0.0.1.nip.io/ urang bakal ningali diréktori files, anu nyimpen laporan tés:

eusi file ya.HTTP.Request.jmx-report.jtk:

timeStamp,elapsed,label,responseCode,responseMessage,threadName,dataType,success,failureMessage,bytes,sentBytes,grpThreads,allThreads,URL,Latency,IdleTime,Connect
1597311456443,569,Yandex - HTTP Request,200,Ok,Thread Group 1-1,text,true,,59449,220,1,1,https://ya.ru/,145,0,57
1597311456443,147,Yandex - HTTP Request-0,302,Found,Thread Group 1-1,,true,,478,110,1,1,http://ya.ru/,145,0,57
1597311456592,420,Yandex - HTTP Request-1,200,Ok,Thread Group 1-1,text,true,,58971,110,1,1,https://ya.ru/,370,0,259

kacindekan

Artikel ieu nunjukkeun salah sahiji pilihan pikeun ngajalankeun tes JMeter di lingkungan OpenShift. Urang réngsé sakabéh léngkah sacara manual, nu satutasna urang dijieun Jenkins Pipeline pikeun ngajadikeun otomatis prosés ngajalankeun tés.

Sumber jeung dokuméntasi

sumber: www.habr.com

Ngajalankeun tes JMeter di OpenShift nganggo Jenkins Pipeline

Nyieun proyék di OpenShift

Nyiptakeun Panyimpenan

Nyiptakeun Gambar Dasar JMeter

JMeter WEB

Jmeter-master

Pipa Jenkins

kacindekan

Sumber jeung dokuméntasi

Tambahkeun komentar ngabolaykeun reply