🥇 Di OpenShift de bi karanîna Jenkins Pipeline testên JMeter dimeşînin

Hemûyan re merheba!

Di vê gotarê de ez dixwazim yek ji awayên ku ceribandinên performansa JMeter-ê li OpenShift-ê bi karanîna Jenkins-ê wekî otomatîk bikar tîne parve bikim. Pêşî em ê hemî gavên hewce bikin (çêkirin ImageStreams, BuildConfig, Job hwd.) di moda destan de. Piştî wê, em werin Jenkins Pipeline binivîsin.

Wek xala destpêkê divê em:

koma OpenShift (v3.11) dimeşîne
Pêşkêşkara Jenkins bi pêbaweriyên mîhengkirî ye ku di OpenShift de bixebite
pelê apache-jmeter-5.2.tgz

Wekî testan ew ê hêsan be HTTP Request li ser ya.ru di yek çemê de.

Afirandina projeyek di OpenShift de

Werin em bi afirandina jîngehek nû dest pê bikin. Werin em biafirînin perftest ji hêla tîmek ve hatî dorpêç kirin:

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

Em ê bixweber werin veguheztin hawîrdora ku nû hatî afirandin perftest, em kontrol bikin ku ev wusa ye:

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

Afirandina Storage

Raporên testê dê bi servera webê re hevbeş werin hilanîn û jmeter-meter'cihek - /jmeter/reports.

Çêtir e ku niha Storajs biafirînin, ji ber ku POD dê bi wan re bêne girêdan jmeter-web и jmeter-master.

Hûn ê di belgeya fermî de agahdariya berfirehtir li ser hilanînê bibînin Storage domdar.

Ka em ji bo pelên yaml biafirînin 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

Werin em biafirînin PV и PVC ji hêla OpenShift ve hatî dorpêç kirin:

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

Ji bo kontrolkirina statûyê 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

Li vir ew ê di GUI de çawa xuya bike:

Afirandina Wêneyek Bingeha JMeter

Werin em ber bi afirandinê ve biçin ImageStream и BuildConfig.

Hûn dikarin hemî agahdariya pêwîst di belgeyê de bibînin - Avakirin û Streamên Wêne.

Stratejiya avakirina wêneyê ye Docker ji çavkaniyek herêmî.

Ka em wêneyek bingehîn çêbikin jmeter-base, ku dê bibe bingeh 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

ye.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

Werin em tiştan biafirînin IS и BC:

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

Naha werin em wêneya bingehîn berhev bikin jmeter-base:

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

JMeter WEB

jmeter-web Ev serverek webê ya Apache ye. Karê wê ew e ku pelrêçek bi encamên testê ji bo temaşekirinê peyda bike.

Amade kirin Dockerfile û pelê veavakirinê httpd.conf. Ji bo rêbernameyê DocumentRoot nirxa set /jmeter/reports, yanî pelrêça ku tê de encamên testê têne tomar kirin.

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

ye.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

Werin em biafirînin ImageStream и BuildConfig objects:

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

Komkirina wêneyekî ji 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

Werin em tiştan biafirînin Service и DeploymentConfig:

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

Jmeter-master

Werin em dest bi bicîhkirina servera webê ya Apache bikin.

Ev Dockerfile ye jmeter-master'a, li ser bingeha jmeter-base, ku dê ceribandinan bimeşîne û encaman hilîne hilanînê.

dockerfile

Dockerfile bo jmeter-master, çi qewimî 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"]

bireve.ş

run.sh ev skrîptek e ku JMeter dimeşîne û encaman li pelrêçekê hildide files.

Her gava ku skrîpt tê destpêkirin, ew ceribandinên berê jêdibe, ji ber vê yekê hûn dikarin tenê bi daneyên herî dawî re bixebitin. Lê ev ne pirsgirêk e, ji ber ku hûn dikarin wê li gorî hewcedariyên xwe biguhezînin.

#!/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

ye.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

Werin em biafirînin IS и BC objects:

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

Em kom dikin jmeter-master wêne:

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

Kar

Job's tê bikaranîn OpenShift'e ji bo ku yek an jî zêdetir bimeşîne POD's û piştî pêkanîna fermanê/skrîptê temamkirina wan a serfiraz garantî dikin.

$ 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

Tiştek çêbikin Job:

$ oc create -f job.yaml -n perftest

Ka em rewşa kar kontrol bikin:

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

To jêbirin Job em fermanê bikar bînin:

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

Jenkins Pipeline

Niha otomasyon. Ka em dîsa li ser gavan biçin:

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

Li jêr boriyek heye ku tê de klonkirina depoyê, jêbirin û çêkirina OpenShift tê kirin Job's.

#!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}"
            }
        }

    }
}

Piştî ku Pipeline xebata xwe qedand, em ê bi e-nameyê agahdariyek bistînin '[email protected] ji [email protected].

Bi tikandina lînkê http://jmeter-web.127.0.0.1.nip.io/ em ê pelrêça bibînin files, ku raporên testê hilîne:

Naveroka pelê 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

encamê

Vê gotarê yek ji vebijarkan ji bo meşandina ceribandinên JMeter di hawîrdora OpenShift de destnîşan kir. Me hemî gavan bi destan qedand, dûv re me Jenkins Pipeline çêkir da ku pêvajoya ceribandina ceribandinan otomatîk bike.

Çavkanî û belge

Source: www.habr.com

Di OpenShift de bi karanîna Jenkins Pipeline ceribandinên JMeter dimeşînin

Afirandina projeyek di OpenShift de

Afirandina Storage

Afirandina Wêneyek Bingeha JMeter

JMeter WEB

Jmeter-master

Jenkins Pipeline

encamê

Çavkanî û belge

Add a comment cancel reply