🥇I-Running JMeter ihlola ku-OpenShift isebenzisa i-Jenkins Pipeline

Sawubona wonke umuntu!

Kulesi sihloko ngifuna ukwabelana ngenye yezindlela zokuqhuba izivivinyo zokusebenza kwe-JMeter ku-OpenShift usebenzisa i-Jenkins njenge-automation. Okokuqala sizokwenza zonke izinyathelo ezidingekayo (ukudala ImageStreams, BuildConfig, Job njll.) kumodi yezandla. Ngemuva kwalokho, masibhale i-Jenkins Pipeline.

Njengesiqalo kufanele sibe:

isebenzisa iqoqo le-OpenShift (v3.11).
Iseva ye-Jenkins enemininingwane emisiwe ukuze isebenze ku-OpenShift
ifayela apache-jmeter-5.2.tgz

Njengokuhlolwa kuzoba lula HTTP Request on ya.ru emfudlaneni owodwa.

Ukudala iphrojekthi ku-OpenShift

Ake siqale ngokwakha indawo entsha. Asidale perftest uzungezwe iqembu:

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

Sizodluliselwa ngokuzenzakalela endaweni esanda kwakhiwa perftest, ake sihlole ukuthi lokhu kunjalo:

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

Ukudalwa Kwesitoreji

Imibiko yokuhlola izogcinwa ngendlela efanayo neseva yewebhu kanye jmeter-meter'Indawo - /jmeter/reports.

Kungcono ukudala ama-Storajs manje, ngoba ama-POD azoboshelwa kuwo jmeter-web и jmeter-master.

Uzothola ulwazi oluthe xaxa mayelana nesitoreji kumadokhumenti asemthethweni Isitoreji esiqhubekayo.

Masidale amafayela e-yaml 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

Asidale PV и PVC izungezwe yi-OpenShift:

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

Ihlola isimo se 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

Nakhu ukuthi izobukeka kanjani ku-GUI:

Ukudala isithombe se-JMeter Base

Asiqhubekele ekudaleni ImageStream и BuildConfig.

Ungathola lonke ulwazi oludingekayo kumadokhumenti - Yakha kanye Nokusakaza Kwezithombe.

Isu lokwakha isithombe lithi Docker emthonjeni wendawo.

Ake sakhe isithombe esiyisisekelo jmeter-base, okuzoba isisekelo jmeter-master.

I-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

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

Ake sakhe izinto IS и BC:

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

Manje ake sihlanganise isithombe esiyisisekelo jmeter-base:

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

I-JMeter WEB

jmeter-web Lena iseva yewebhu ye-Apache. Umsebenzi wawo ukuhlinzeka ngohla lwemibhalo olunemiphumela yokuhlolwa ukuze lubukwe.

Ilungiselelwe Dockerfile kanye nefayela lokumisa httpd.conf. Okokuqondisa DocumentRoot isethi yenani /jmeter/reports, i.e. uhla lwemibhalo lapho kugcinwa khona imiphumela yokuhlolwa.

I-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

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

Asidale ImageStream и BuildConfig izinto:

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

Iqoqa isithombe ku 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

Ake sakhe izinto Service и DeploymentConfig:

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

UJmeter Ungumbungazi ovelele

Ake siqale ukusebenzisa iseva yewebhu ye-Apache.

Le yi-Dockerfile jmeter-master'a, kusekelwe jmeter-base, ezosebenzisa izivivinyo futhi ilondoloze imiphumela endaweni yokugcina.

I-Dockerfile

Dockerfile ngoba jmeter-master, ngokusekelwe ku 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"]

run.sh

run.sh lesi iskripthi esisebenzisa i-JMeter futhi sigcina imiphumela ohlwini lwemibhalo files.

Ngaso sonke isikhathi uma umbhalo wethulwa, ususa izivivinyo zangaphambilini, ukuze ukwazi ukusebenza ngedatha yakamuva kuphela. Kodwa lokhu akuyona inkinga, ngoba ungayishintsha ukuze ihambisane nezidingo zakho.

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

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

Asidale IS и BC izinto:

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

Siqoqa jmeter-master isithombe:

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

UJobe

Jobzisetshenziswa ku OpenShift'e ukuze usebenzise eyodwa noma ngaphezulu PODfuthi siqinisekise ukuqedwa kwazo ngempumelelo ngemva kokwenza umyalo/iskripthi.

$ 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

Dala into Job:

$ oc create -f job.yaml -n perftest

Ake sihlole isimo somsebenzi:

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

Ukususa Job masisebenzise umyalo:

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

I-Jenkins Pipeline

Manje i-automation. Ake sidlule izinyathelo futhi:

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

Ngezansi kunepayipi lapho kwenziwa khona ukuhlanganisa kwekhosombe, ukususwa nokudalwa kwe-OpenShift 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}"
            }
        }

    }
}

Ngemuva kokuthi i-Pipeline iqede ukusebenza kwayo, sizothola isaziso nge-imeyili '[email protected] kusukela [email protected].

Ngokuchofoza isixhumanisi http://jmeter-web.127.0.0.1.nip.io/ sizobona uhla lwemibhalo files, egcina imibiko yokuhlolwa:

Okuqukethwe kwefayela 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

isiphetho

Lesi sihloko sibonise enye yezinketho zokuqalisa ukuhlolwa kwe-JMeter endaweni ye-OpenShift. Siqedele zonke izinyathelo mathupha, ngemuva kwalokho sakha i-Jenkins Pipeline ukuze senze inqubo yokuhlola isebenze ngokuzenzakalelayo.

Imithombo namadokhumenti

Source: www.habr.com

Ukuqalisa ukuhlolwa kwe-JMeter ku-OpenShift kusetshenziswa i-Jenkins Pipeline

Ukudala iphrojekthi ku-OpenShift

Ukudalwa Kwesitoreji

Ukudala isithombe se-JMeter Base

I-JMeter WEB

UJmeter Ungumbungazi ovelele

I-Jenkins Pipeline

isiphetho

Imithombo namadokhumenti

Engeza amazwana Отменить ответ