🥇 Ku socodsiinta tijaabooyinka JMeter ee OpenShift iyadoo la adeegsanayo Jenkins Pipeline

Hello qof walba!

Maqaalkan waxaan rabaa in aan la wadaago mid ka mid ah siyaabaha loo socodsiiyo imtixaanada waxqabadka JMeter ee OpenShift anigoo isticmaalaya Jenkins si toos ah. Marka hore waxaan samayn doonaa dhammaan tallaabooyinka lagama maarmaanka ah (abuurista ImageStreams, BuildConfig, Job iwm) habka gacanta. Intaa ka dib, aan qorno Jenkins Pipeline.

Bar bilow ahaan waa in aan yeelano:

Kutlada OpenShift (v3.11).
Server Jenkins oo wata shahaadooyin la habeeyey si uu uga shaqeeyo OpenShift
faylka apache-jmeter-5.2.tgz

Sida imtixaanada waxay noqon doontaa mid fudud HTTP Request on ya.ru hal durdur ah.

Abuuritaanka mashruuc OpenShift

Aan ku bilowno abuurista jawi cusub. Aan abuurno perftest koox ay ku hareeraysan yihiin:

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

Waxa si toos ah naloogu wareejin doonaa deegaanka cusub ee la abuuray perftest, aynu eegno in tani ay tahay:

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

Abuuritaanka Kaydinta

Warbixinaha tijaabada waxaa lagu kaydin doonaa si wadajir ah server-ka iyo jmeter-meter'goob - /jmeter/reports.

Way fiicantahay in hadda la abuuro Storajs, sababtoo ah POD-yada ayaa lagu xidhi doonaa iyaga jmeter-web и jmeter-master.

Waxaad ka heli doontaa macluumaad faahfaahsan oo ku saabsan kaydinta dukumeentiyada rasmiga ah Kaydinta joogtada ah.

Aan u abuurno yaml files 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

Aan abuurno PV и PVC waxaa ku hareeraysan OpenShift:

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

Hubinta xaalada 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

Waa kan sida ay ugu ekaan doonto GUI:

Abuuritaanka Sawirka Saldhigga JMeter

Aan u gudubno abuurista ImageStream и BuildConfig.

Waxaad ka heli kartaa dhammaan macluumaadka lagama maarmaanka ah dukumentiyada - Dhisidda iyo Sawirrada durdurrada.

Istaraatiijiyada dhismaha sawirka waa Docker ilo maxalli ah.

Aynu abuurno sawir sal ah jmeter-base, taasoo saldhig u noqon doonta 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

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

Aan abuurno walxo IS и BC:

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

Hadda aynu soo ururino sawirka salka jmeter-base:

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

JMeter WEB

jmeter-web Kani waa server-ka Apache Shaqadeedu waa inay bixiso hage leh natiijooyin imtixaan si loo daawado.

La diyaariyay Dockerfile iyo faylka qaabeynta httpd.conf. Dardaaran DocumentRoot qiimaha go'an /jmeter/reports, i.e. tusaha lagu kaydiyo natiijooyinka imtixaanka.

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

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

Aan abuurno ImageStream и BuildConfig walxaha:

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

Ka soo ururinta sawir 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

Aan abuurno walxo Service и DeploymentConfig:

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

Jmeter-master

Aynu bilowno geynta serverka shabakadda Apache.

Kani waa Dockerfile-ka jmeter-master'a, ku salaysan jmeter-base, kaas oo samayn doona imtixaano oo ku badbaadin doona natiijooyinka kaydinta.

Dockerfile

Dockerfile si ay u jmeter-master, ku salaysan 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"]

orod.sh

run.sh kani waa qoraal shaqaynaya JMeter oo natiijada ku kaydiya hagaha files.

Mar kasta oo qoraalka la bilaabo, wuxuu tirtiraa imtixaanadii hore, si aad kaliya ugu shaqeyso xogta ugu dambeysa. Laakiin tani dhib ma aha, sababtoo ah waxaad u beddeli kartaa si ay ugu habboonaato baahiyahaaga.

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

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

Aan abuurno IS и BC walxaha:

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

Waxaan soo aruurinaa jmeter-master sawirka:

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

Job

Jobwaxaa loo isticmaalaa in OpenShift'e si loo ordo mid ama ka badan POD's oo dammaanad qaadaya dhammaystirkooda guusha leh ka dib fulinta amarka/script.

$ 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

Abuur shay Job:

$ oc create -f job.yaml -n perftest

Aan hubino heerka shaqada:

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

Si aad u tirtirto Job aan isticmaalno amarka:

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

Jenkins Pipeline

Hadda automation. Aan mar kale dulmarno tillaabooyinka:

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

Hoos waxaa ah dhuumo kaas oo kaydinta kaydinta, tirtirka iyo abuurista OpenShift lagu sameeyay Jobs

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

    }
}

Ka dib markii Pipeline ay dhameysato hawsheeda, waxaan ku heli doonaa ogeysiis iimayl ahaan '[email protected] ka [email protected].

Adigoo gujinaya xiriirka http://jmeter-web.127.0.0.1.nip.io/ waan arki doonaa hagaha files, kaas oo kaydiya warbixinnada tijaabada:

Waxa ku jira faylka 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

gunaanad

Maqaalkani wuxuu muujiyay mid ka mid ah fursadaha lagu socodsiiyo imtixaannada JMeter ee jawiga OpenShift. Dhammaan tillaabooyinka gacanta ayaanu ku dhammaystirnay, ka dib waxaan abuurnay Jenkins Pipeline si ay otomaatig ugu noqoto hannaanka socodsiinta imtixaannada.

Ilaha iyo dukumentiyada

Source: www.habr.com

Ku socodsiinta imtixaanada JMeter gudaha OpenShift iyadoo la isticmaalayo Jenkins Pipeline

Abuuritaanka mashruuc OpenShift

Abuuritaanka Kaydinta

Abuuritaanka Sawirka Saldhigga JMeter

JMeter WEB

Jmeter-master

Jenkins Pipeline

gunaanad

Ilaha iyo dukumentiyada

Add a comment cancel reply