You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Next »

This is an overview of the state of readiness for moving to project-specific CSIT per project at the end of Honolulu release


TBD: The aspects to be considered:

  • produced artifacts and method of production
  • produced docker images and method of production
  • cross-project dependencies
  • execution time (including artifact and docker builds)
  • use of Nexus in various phases

Active projects

ProjectStatusBuild artifactsProduced docker imagesCSIT jobs CSIT job triggersTested docker images and repositoriesDocker build jobs that create the tested imagesCSIT DependenciesComments

ccsdk

Project-specific CSIT in use under ccsdk/distributionProduced by maven-assembly-plugin from various repo zips that are in onap.nexus.org (to where they get by ccsdk-sli-maven-stage-master that is triggered from gerrit by 'stage-release' command) 

Produced by docker-maven-plugin

ccsdk-odlsli-alpine-image:latest

ccsdk-dgbuilder-image:latest

(+ many others that are not separately tested)





ccsdk-distribution-review-verification-maven-master

ccsdk-distribution-merge-verification-maven-master


Review and merge triggers

ccsdk-odlsli-alpine-image:latest

ccsdk-dgbuilder-image:latest

Technically the source repository for the above images is ccsdk/distribution, but in reality their contents are collected from various other ccsdk repositories via repository zip maven dependencies

Built locally within the verification jobsmysql/mysql-server:5.6

The tested images have some tricky build-time dependencies to other docker images that are also built on the fly - their tagging and references should be improved (TODO: create Jira)

ccsdk-oranProject-specific CSIT in use under ccsdk/oran

a1-policy-management-service.jar, produced by fabric8 maven plugin locally

(which raises the question of the purpose of  published artifacts in ccsdk-oran-maven-stage-master since ccsdk-oran-maven-docker-stage-master also builds the artifacts on the fly instead of pulling them from Nexus)

onap/ccsdk-oran-a1policymanagementservice (1.2.0-SNAPSHOT for master, 1.1.3-SNAPSHOT for Honolulu, 1.0.3-SNAPSHOT for Guilin)

ccsdk-oran-review-verification-maven-master

ccsdk-oran-merge-verification-maven-master


ccsdk-oran-review-verification-maven-honolulu

ccsdk-oran-merge-verification-maven-honolulu


ccsdk-oran-review-verification-maven-guilin

ccsdk-oran-merge-verification-maven-guilin

review and merge triggers

onap/ccsdk-oran-a1policymanagementservice (1.2.0-SNAPSHOT for master, 1.1.3-SNAPSHOT for Honolulu, 1.0.3-SNAPSHOT for Guilin)

The source repository is ccsdk/oran

Built locally within the verification jobs

nexus3.onap.org:10003/onap/sdnc-image (2.1.0-STAGING-latest for master, nexus3.onap.org:10003/onap/sdnc-image:2.0.1-STAGING-latest for Guilin)

nexus3.o-ran-sc.org:10004/o-ran-sc/nonrtric-controlpanel:2.0.0
mysql/mysql-server:5.6
nexus3.o-ran-sc.org:10004/o-ran-sc/a1-simulator:2.0.0
consul:1.7.2
nexus3.onap.org:10001/onap/org.onap.dcaegen2.platform.configbinding.app-app:2.3.0
mrstub:latest
callback-receiver:latest

These tests are currently cloned from ORAN repository and they are essentially plain shell scripts that are just wrapped into Robot

Note that the Robot wrapper could be removed if more flexible project-specific CSIT JJB template was created for that (TODO: create Jira if needed)

cpsProject-specific CSIT  using cps repositoryA number of jars created with maven (docker builds always do this on the fly so what purpose do the artifacts pushed to Nexus serve?)cps-and-nf-proxy:latest

master branch:
cps-review-verification-maven-master
cps-merge-verification-maven-master

honolulu branch:
cps-review-verification-maven-honolulu
cps-merge-verification-maven-honolulu

review and merge triggers

cps-and-nf-proxy:latest

The source repository is  cps

built locally within Jenkins jobs
CPS is the first project to adopt project-specific CSIT design from the beginning instead of porting their tests from integration/csit 
dcaegen2


dcaegen2-services-son-handler-master-csit-testsuites

dcaegen2-services-pmsh-master-csit-testsuite

dcaegen2-services-bbs-event-processor-master-csit-bbs-testsuites

dcaegen2-pmmapper-master-csit-pmmapper

dcaegen2-master-csit-testsuites

dcaegen2-master-csit-prh-testsuites

dcaegen2-collectors-restconf-master-csit-testsuites

dcaegen2-collectors-hv-ves-master-csit-testsuites

dcaegen2-collectors-datafile-master-csit-ManagementInterface-suite

dcaegen2-collectors-datafile-master-csit-Functional-suite

nexus3.onap.org:10003/onap/org.onap.dcaegen2.services.son-handler:latest

nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.pmsh:latest

nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.components.bbs-event-processor:latest

nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.pm-mapper:latest

nexus3.onap.org:10003/onap/org.onap.dcaegen2.collectors.ves.vescollector:latest

nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.prh.prh-app-server:latest

nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.restconfcollector:latest

nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.hv-ves.hv-collector-main:latest

nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.datafile.datafile-app-server:latest

(all hardcoded in various places in the tests)

TBD: most or all of these are in their own dedicated repositories, TBD: are the repo-image-CSIT relations straightforward 1:1 in all cases (or any case)?

Some of the triggering jobs produce the tested images, others do not produce any  image; requires a deeper lookA lot of simulators used, TBD
dmaap


dmaap-buscontroller-master-csit-ssl

dmaap-buscontroller-master-csit-with_dr

dmaap-buscontroller-master-csit-with_mr

dmaap-datarouter-master-csit-ssl-dr-suite

dmaap-master-csit-mrpubsub


dmaap-datarouter-maven-docker-stage-master

  DMAAP-1501 - Getting issue details... STATUS

nexus3.onap.org:10001/onap/dmaap/buscontroller


nexus3.onap.org:10001/onap/dmaap/datarouter-prov

nexus3.onap.org:10001/onap/dmaap/datarouter-node

nexus3.onap.org:10001/onap/dmaap/datarouter-subscriber


(all hardcoded, version not given so latest by default)

At least three different source repositories:

dmaap/buscontroller

dmaap/datarouter

dmaap/messagerouter/messageservice


There are no jobs producing onap/dmaap/buscontroller - the latest image in Nexus has been updated Thu Feb 21 2019 and belongs to Casablanca (?!) - ticket raised:

DMAAP-1502 - Getting issue details... STATUS


dmaap-datarouter-maven-docker-stage-master (same as job trigger)

TBDIt's unclear in some of these suites if  datarouter and messagerouter are dependencies for buscontroller or components under test? We seem to have multi-repository problem here that needs to be solved somehow
modeling


modeling-etsicatalog-master-csit-sanity-checkmodeling-etsicatalog-master-docker-java-version-shell-dailynexus3.onap.org:10001/onap/modeling/etsicatalog (latest by default)

modeling-etsicatalog-master-docker-java-version-shell-daily

consul:0.9.3

nexus3.onap.org:10001/onap/msb/msb_discovery

nexus3.onap.org:10001/onap/msb/msb_apigateway

nexus3.onap.org:10001/onap/msb/msb_apigateway

(all latest by default - this is dangerous, fixed dependency versions should be defined as latest can be anything)

Default latest is used both for image to be tested and for dependency images. Both should be improved (TBD: ticket to be created)
multicloud


multicloud-master-csit-functionality1

multicloud-starlingx-master-csit-functionality1

multicloud-vmware-master-csit-functionality1

MULTICLOUD-1231 - Getting issue details... STATUS

nexus3.onap.org:10001/onap/multicloud/vio:1.4.1 

nexus3.onap.org:10001/onap/multicloud/framework:1.4.1


nexus3.onap.org:10001/onap/multicloud/openstack-starlingx


nexus3.onap.org:10001/onap/multicloud/vio

(all hardcoded, default latest for those that do not define version explicitly)


Latest in Nexus:

onap/multicloud/vio:1.4.1 is from Sep 12 2019

onap/multicloud/framework:1.4.1 is from Sep 06 2019

...these seem to be some early El-Alto versions?

Ticker raised:  MULTICLOUD-1229 - Getting issue details... STATUS

https://jenkins.onap.org/view/multicloud/job/multicloud-openstack-maven-docker-stage-elalto produces version 1.4.3 of onap/multicloud/openstack-starlingx

https://jenkins.onap.org/view/multicloud/job/multicloud-framework-maven-docker-stage-master produces version 1.6.0 (and also latest) of onap/multicloud/framework

multicloud-openstack-maven-docker-stage-master produces version 1.5.6 (and also latest) of onap/multicloud/openstack-starlingx

multicloud-openstack-vmware-maven-docker-stage-master produces version 1.4.2 (and also latest) of onap/multicloud/vio

-
oom-platform-cert-service


oom-platform-cert-service-master-csit-certservice

oom-platform-cert-service-master-csit-postprocessor

oom-platform-cert-service-master-merge-java (triggers two CSITs but does not produce or trigger docker image? Ticket raised: OOM-2594 - Getting issue details... STATUS )

nexus3.onap.org:10001/onap/org.onap.oom.platform.cert-service.oom-certservice-api:latest

nexus3.onap.org:10001/onap/org.onap.oom.platform.cert-service.oom-certservice-post-processor:latest (but started in Robot test and defined in Robot variable so it would be theoretically overridable)

oom-platform-cert-service-maven-docker-stage-master (for both)


primekey/ejbca-ce:6.15.2.5



optf

Transition to project-specific CSIT in progress:  OPTFRA-930 - Getting issue details... STATUS



optf-cmso-master-csit-cmso

optf-osdf-master-csit-osdf

optf-has-master-csit-has

OPTFRA-858 - Getting issue details... STATUS

nexus3.onap.org:10001/onap/optf-cmso-service:latest

nexus3.onap.org:10001/onap/optf-cmso-dbinit:latest

nexus3.onap.org:10001/onap/optf-cmso-topology:latest

nexus3.onap.org:10001/onap/optf-cmso-ticketmgt:latest

nexus3.onap.org:10001/onap/optf-cmso-optimizer:latest

nexus3.onap.org:10001/onap/optf-cmso-robot:latest (!! The actual Robot tests run here in setup phase instead of as separate Robot tests from CSIT repo)


nexus3.onap.org:10001/onap/optf-osdf:2.0.3-SNAPSHOT-latest


nexus3.onap.org:10001/onap/optf-has:2.1.2-SNAPSHOT-latest




Repositories:

optf/cmso

optf/osdf

optf/has


optf-cmso-maven-docker-stage-master

(word of warning: the frankfurt versions of the above jobs are also  pushing the same images with "latest"! Probably worth a ticket)

optf-osdf-master-osdf-merge-java

optf-has-master-conductor-merge-java



policy


policy-master-csit-apex-pdp

policy-master-csit-api

policy-master-csit-distribution

policy-master-csit-drools-applications

policy-master-csit-drools-pdp

policy-master-csit-pap

policy-master-csit-xacml-pdp

(+frankfurt branches for each)


policy-apex-pdp-master-merge-java

policy-api-master-merge-java

policy-distribution-master-merge-java

policy-drools-applications-master-merge-java

policy-drools-pdp-master-merge-java

policy-pap-master-merge-java

policy-xacml-pdp-master-merge-java

(+frankfurt branches for each - note that these also produce the same images with latest tag; this is not critical though since CSITs do not refer to those)

Dynamic image version resolution based on GERRIT_BRANCH and pom.xmls in the referred branches of the related repositories amended with "SNAPSHOT-latest"

  • The distinction between images under test and dependent images is blurred -any policy component change can cause any other's CSIT to fail
Same as triggersPolicy components have a lot of dependencies between each other and distinction between what's under test and what's just required is not clearPolicy CSITs and their triggers and image references are currently almost as valid as they can be under current circumstances (the only uncertainty is related to the distinction between images under test and dependency images)
sdc (CSIT disabled)


SDC-3302 - Getting issue details... STATUS





SDC has moved its legacy TestNG tests under SDC repo already and incorporated them into maven jobs. (where they test the docker image(s) generated in the same build) This needs to be evaluated in Honolulu.
sdnc


sdnc-master-csit-healthcheck

sdnc-master-csit-sdnc_netconf_tls_post_deploy



SDNC-1381 - Getting issue details... STATUS

nexus3.onap.org:10001/onap/sdnc-image/1.8-STAGING-latest

nexus3.onap.org:10001/onap/sdnc-ansible-server-image/1.8-STAGING-latest

nexus3.onap.org:10001/onap/admportal-sdnc-image/1.8-STAGING-latest

nexus3.onap.org:10001/onap/sdnc-ueb-listener-image/1.8-STAGING-latest

nexus3.onap.org:10001/onap/sdnc-dmaap-listener-image/1.8-STAGING-latest

nexus3.onap.org:10001/onap/ccsdk-dgbuilder-image/0.7-STAGING-latest

---

nexus3.onap.org:10001/onap/sdnc-image/1.8.3-STAGING-latest

The source repo is sdnc/oam

SDNC images are going at version 2.1 in master )sdnc-oam-maven-docker-stage-master) and at 2.0 in Guilin (https://jenkins.onap.org/view/sdnc/job/sdnc-oam-maven-docker-stage-guilin)

Latest 1.8-STAGING-latest images are from Aug 31 2020 and 1.8.3-STAGING-latest from Jun 07 2020. These images are from Frankfurt and have no longer any jobs to generate them.

Ticket created:  CCSDK-2915 - Getting issue details... STATUS



primekey/ejbca-ce:6.15.2.5

nexus3.onap.org:10001/onap/org.onap.aaf.certservice.aaf-certservice-api:latest

---

nexus3.onap.org:10001/mariadb:10.1.11





so


so-master-csit-integration-etsi-testing

so-master-csit-integration-testing

(and the same for frankfurt and elalto; see SO-3307 - Getting issue details... STATUS  for the latter)


SO-3305 - Getting issue details... STATUS

nexus3.onap.org:10001/onap/so/catalog-db-adapter:1.3.1

nexus3.onap.org:10001/onap/so/request-db-adapter:1.3.1

nexus3.onap.org:10001/onap/so/sdnc-adapter:1.3.1

nexus3.onap.org:10001/onap/so/openstack-adapter:1.3.1

nexus3.onap.org:10001/onap/so/vfc-adapter::1.3.1

nexus3.onap.org:10001/onap/so/sdc-controller:1.3.1

nexus3.onap.org:10001/onap/so/bpmn-infra:1.3.1

nexus3.onap.org:10001/onap/so/api-handler-infra:1.3.1

---

1.6.0 tag for integration-etsi-testing (TBD: images to be added)

Source repo seems to be so for all of these (to be verified)



1.3.1 goes all the way back to early Casablanca - these have not been updated since Nov 16 2018

1.6.0 are early Frankfurt versions (no updates since April 2020)

SO-3306 - Getting issue details... STATUS

so-maven-docker-stage-master is at 1.7.3

so-maven-docker-stage-frankfurt is at 1.6.4

so-maven-docker-stage-elalto is at 1.5.4






TBD - is distinction between images under test and image dependencies clear?integration-testing suite hasn't been relevant for two years
vfc


vfc-gvnfm-vnflcm-master-csit-sanity-check

vfc-gvnfm-vnfres-master-csit-sanity-check

vfc-nfvo-driver-vnfm-gvnfm-master-csit-sanity-check

vfc-nfvo-lcm-master-csit-sanity-check



vfc-gvnfm-vnflcm-master-docker-java-version-shell-daily

vfc-gvnfm-vnfres-master-docker-java-version-shell-daily

vfc-nfvo-driver-vnfm-gvnfm-master-docker-java-version-shell-daily

vfc-nfvo-lcm-master-docker-java-version-shell-daily

nexus3.onap.org:10001/onap/vfc/vnflcm

nexus3.onap.org:10001/onap/vfc/vnfres

nexus3.onap.org:10001/onap/vfc/gvnfmdriver

nexus3.onap.org:10001/onap/vfc/nslcm

(all latest by default)

Source repositories:

vfc/gvnfm/vnflcm

vfc/gvnfm/vnfres

vfc/nfvo/driver/vnfm/gvnfm

vfc/nfvo/lcm


Same as triggers

consul:0.9.3

nexus3.onap.org:10001/onap/msb/msb_discovery

nexus3.onap.org:10001/onap/msb/msb_a
pigateway

nexus3.onap.org:10001/library/mariadb

redis (!?)

It's not clear in all cases which VFC images are under test and which are just necessary dependencies




vid


vid-master-csit-healthCheck


VID-906 - Getting issue details... STATUS

nexus3.onap.org:10001/onap/vid:6.0-STAGING-latest

Source repo is vid


vid-maven-docker-stage-frankfurt

vid-maven-docker-stage-master produces 7.0.0 versions except for STAGING-latest, which is somehow still 6.0 - however, this is problematic as Frankfurt also produces 6.0-STAGING-latest images. Ticket raised:  VID-907 - Getting issue details... STATUS

nexus3.onap.org:10001/library/mariadb:10

so-simulator (specific to this suite)

aai-simulator (specific to this suite)



vfsdk


vnfsdk-marketplace-master-csit-testsuites

vnfsdk-refrepo-master-csit-testsuites

vnfsdk-refrepo-master-merge-java

(for both CSITs; however, this job does not produce or trigger any docker image? Ticket raised: VNFSDK-701 - Getting issue details... STATUS )

nexus3.onap.org:10001/onap/vnfsdk/refrepo/postgres:latest

nexus3.onap.org:10001/onap/vnfsdk/refrepo:latest

Source repo is vnfsdk/refrepo



vnfsdk-refrepo-maven-docker-stage-master

Where is onap/vnfsdk/refrepo/postgres coming from? It hasn't been produced since Jul 09 2019?




What's the relevance of the marketplace CSIT now (given that it's testing postgres image that hasn't been built for over a year)?



Disabled projects

Projects with CSITBuild ArtifactsDocker imagesCSIT jobs CSIT job triggersTested docker images and repositoriesDocker build jobs that create the tested imagesDependenciesComments
aaf (disabled)TBDTBD

aaf-frankfurt-csit-certservice

Frankfurt branch only? The tests triggered from here do not even exist in master (on the other hand, there are no Jenkins jobs for still remaining aafapi and sms-test-plan?)

aaf-certservice-frankfurt-merge-java - this job neither builds a docker image nor triggers another job that does it, so why trigger CSIT?

nexus3.onap.org:10001/onap/ org.onap.aaf.certservice.aaf-certservice-api:frankfurt-latest

(hardcoded)

The source repository is aaf/certservice

aaf-certservice-maven-docker-stage-frankfurt

(note that aaf-certservice-release-verify and aaf-certservice-release-merge also build aaf-certservice-api image, but not with frankfurt-latest tag)

primekey/ejbca-ce:6.15.2.5 (hardcoded, real image used)


In maintenance mode, CSIT disabled:  AAF-1208 - Getting issue details... STATUS

appc (disabled)

appc-master-csit-healthcheck

-

nexus3.onap.org:10001/onap/appc-image:1.7.2-SNAPSHOT-latest

nexus3.onap.org:10001/onap/appc-cdt-image:1.7.2-SNAPSHOT-latest

(hardcoded)

docker-compose.yml as well as appc-image and appc-cdt-image come from appc/deployment


No job is producing these images at the moment! 

appc-deployment-master-docker-java-daily produces 1.8.0-SNAPSHOT-latest and 

appc-deployment-frankfurt-docker-java-daily is producing 1.7.3-SNAPSHOT-latest

1.7.2-SNAPSHOT-latest images have not been created since May 27


mariadb:10.4.3

nexus3.onap.org:10001/onap/ccsdk-dgbuilder-image:0.6.0 (no longer produced, last update to Nexus on Aug 30 2019)

nexus3.onap.org:10001/onap/ccsdk-ansible-server-image:0.4.4 (no longer produced, last update to Nexus on Jun 06 2019)

(hardcoded, real images used)

In maintenance mode, CSIT disabled:  APPC-1910 - Getting issue details... STATUS


clamp (disabled)



clamp-master-csit-APIs

clamp-master-csit-UIs


Invalid trigger jobs removed in  CLAMP-950 - Getting issue details... STATUS

nexus3.onap.org:10001/onap/clamp-backend:4.1-STAGING-latest

(hardcoded)

The docker-compose.yml and source of the images is clamp

clamp-maven-docker-stage-elalto

CLAMP-957 - Getting issue details... STATUS

mariadb:10.5.4

python:2-slim

In maintenance mode, CSIT disabled:  CLAMP-952 - Getting issue details... STATUS

music (disabled)

music-master-verify-csit-music-distributed-kv-store-test-plan


music-distributed-kv-store-master-docker-golang-shell-daily

nexus3.onap.org:10001/onap/music/distributed-kv-store (hardcoded, latest by default)


music-distributed-kv-store-master-docker-golang-shell-daily-

In maintenance mode, CSIT disabled:  MUSIC-613 - Getting issue details... STATUS  

usecases (disabled? but how?)








  • No labels