Cynnal profion JMeter yn OpenShift gan ddefnyddio Piblinell Jenkins

Helo bawb!

Yn yr erthygl hon rwyf am rannu un o'r ffyrdd o redeg profion perfformiad JMeter yn OpenShift gan ddefnyddio Jenkins fel awtomeiddio. Yn gyntaf byddwn yn gwneud yr holl gamau angenrheidiol (creu ImageStreams, BuildConfig, Job ac ati) yn y modd llaw. Ar ôl hynny, gadewch i ni ysgrifennu Jenkins Pipeline.

Fel man cychwyn dylem gael:

  1. rhedeg clwstwr OpenShift (v3.11).
  2. Gweinydd Jenkins gyda manylion wedi'u ffurfweddu i weithio yn OpenShift
  3. файл apache-jmeter-5.2.tgz

Fel profion bydd yn syml HTTP Request ar ya.ru mewn un ffrwd.

Creu prosiect yn OpenShift

Gadewch i ni ddechrau trwy greu amgylchedd newydd. Gadewch i ni greu perftest wedi'i amgylchynu gan dîm:

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

Byddwn yn cael ein trosglwyddo'n awtomatig i'r amgylchedd newydd perftest, gadewch i ni wirio bod hyn felly:

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

Creu Storio

Bydd adroddiadau prawf yn cael eu storio yn gyffredin â'r gweinydd gwe a jmeter-meter'lle - /jmeter/reports.

Mae'n well creu Storajs nawr, oherwydd bydd PODs yn gysylltiedig â nhw jmeter-web и jmeter-master.

Fe welwch wybodaeth fanylach am storio yn y dogfennau swyddogol Storio parhaus.

Gadewch i ni greu ffeiliau yaml ar gyfer 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

Gadewch i ni greu PV и PVC wedi'i amgylchynu gan OpenShift:

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

Wrthi'n gwirio'r statws ar gyfer 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

Dyma sut olwg fydd arno yn y GUI:

Cynnal profion JMeter yn OpenShift gan ddefnyddio Piblinell Jenkins

Creu Delwedd Sylfaen JMeter

Gadewch i ni symud ymlaen i greu ImageStream и BuildConfig.

Gallwch ddod o hyd i'r holl wybodaeth angenrheidiol yn y ddogfennaeth - Adeiladu a Ffrydiau Delwedd.

Mae'r strategaeth adeiladu delweddau Docker o ffynhonnell leol.

Gadewch i ni greu delwedd sylfaenol jmeter-base, a fydd yn sail i 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

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

Gadewch i ni greu gwrthrychau IS и BC:

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

Nawr gadewch i ni gydosod y ddelwedd sylfaenol jmeter-base:

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

JMeter WE

jmeter-web Gweinydd gwe Apache yw hwn. Ei dasg yw darparu cyfeiriadur gyda chanlyniadau profion i'w gweld.

Parod Dockerfile a ffeil ffurfweddu httpd.conf. Am gyfarwyddeb DocumentRoot set gwerth /jmeter/reports, h.y. y cyfeiriadur lle mae canlyniadau profion yn cael eu cadw.

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

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

Gadewch i ni greu ImageStream и BuildConfig gwrthrychau:

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

Casglu delwedd o 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

Gadewch i ni greu gwrthrychau Service и DeploymentConfig:

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

Jmeter-meistr

Gadewch i ni ddechrau defnyddio gweinydd gwe Apache.

Dyma'r Dockerfile jmeter-master'a, yn seiliedig ar jmeter-base, a fydd yn rhedeg profion ac yn arbed y canlyniadau i storio.

Dockerfile

Dockerfile gyfer jmeter-master, yn seiliedig ar 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"]

rhedeg.sh

run.sh dyma sgript sy'n rhedeg JMeter ac yn cadw'r canlyniadau i gyfeiriadur files.

Bob tro y caiff y sgript ei lansio, mae'n dileu profion blaenorol, felly dim ond gyda'r data diweddaraf y gallwch chi weithio. Ond nid yw hyn yn broblem, oherwydd gallwch ei newid i weddu i'ch anghenion.

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

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

Gadewch i ni greu IS и BC gwrthrychau:

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

Rydyn ni'n casglu jmeter-master delwedd:

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

Swyddi

Job's yn cael eu defnyddio yn OpenShift'e er mwyn rhedeg un neu fwy PODs ac yn gwarantu eu cwblhau'n llwyddiannus ar ôl gweithredu'r gorchymyn/sgript.

$ 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

Creu gwrthrych Job:

$ oc create -f job.yaml -n perftest

Gadewch i ni wirio statws y swydd:

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

I ddileu Job gadewch i ni ddefnyddio'r gorchymyn:

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

Jenkins Piblinell

Nawr awtomeiddio. Gadewch i ni fynd dros y camau eto:

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

Isod mae piblinell lle mae clonio ystorfa, dileu a chreu OpenShift yn cael eu perfformio 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}"
            }
        }

    }
}

Ar ôl i Pipeline gwblhau ei weithrediad, byddwn yn derbyn hysbysiad trwy e-bost '[email protected] o [email protected].

Trwy glicio ar y ddolen http://jmeter-web.127.0.0.1.nip.io/ cawn weld y cyfeiriadur files, sy'n storio adroddiadau prawf:

Cynnal profion JMeter yn OpenShift gan ddefnyddio Piblinell Jenkins

Cynnwys y ffeil 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

Casgliad

Roedd yr erthygl hon yn dangos un o'r opsiynau ar gyfer rhedeg profion JMeter yn amgylchedd OpenShift. Cwblhawyd yr holl gamau â llaw, ac ar ôl hynny fe wnaethom greu Piblinell Jenkins i awtomeiddio'r broses o redeg profion.

Ffynonellau a dogfennaeth

Ffynhonnell: hab.com

Ychwanegu sylw