Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 (+various other images on which this is dependent)

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 the verification jobs
CPS is the first project to adopt project-specific CSIT design from the beginning instead of porting their tests from integration/csit 
dcaegen2integration/csit in use, no current plans to move the tests to dcaegen2 repositories

dcaegen2/services/son-handler

son-handler.jar with maven

___________________

dcaegen2/services

pmsh is python-based; no artifacts in Nexus?

___________________

dcaegen2/services

bbs-event-processor.jar with maven

___________________

dcaegen2/services/pm-mapper

pm-mapper.jar with maven

___________________

dcaegen2/collectors/ves

VESCollector.jar with maven

___________________

dcaegen2/services/prh

prh-app-server.jar with maven

___________________

dcaegen2/collectors/restconf

restconfcollector.jar with maven

___________________

dcaegen2/collectors/hv-ves

Some half a dozen different jars with maven

___________________

dcaegen2/collectors/datafile

datafile-app-server.jar with maven


dcaegen2/services/son-handler

Produced by docker-maven-plugin:

org.onap.dcaegen2.services.son-handler:latest

____________________

dcaegen2/services

Produced by docker-build.sh from ci-management:

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

____________________

dcaegen2/services

Produced by dockerfile-maven-plugin:

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

____________________

dcaegen2/services/pm-mapper

Produced by docker-maven-plugin:

org.onap.dcaegen2.services.pm-mapper:latest

____________________

dcaegen2/collectors/ves

Produced by docker-maven-plugin:

org.onap.dcaegen2.collectors.ves.vescollector:latest

____________________

dcaegen2/services/prh

Produced by docker-maven-plugin:

org.onap.dcaegen2.services.prh.prh-app-server:latest

___________________

dcaegen2/collectors/restconf

org.onap.dcaegen2.collectors.restconfcollector:latest

___________________

dcaegen2/collectors/hv-ves

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

(and few other ones that are not being tested nor used in CSIT?)

____________________

dcaegen2/collectors/datafile

org.onap.dcaegen2.collectors.datafile.datafile-app-server:latest

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

dcaegen2-services-son-handler-master-merge-java

(does neither produce nor push docker image! Instead, it's produced by dcaegen2-services-son-handler-maven-docker-stage-master - ticket raised:

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-2741
)

________________________

dcaegen2-services-pmsh-docker-merge-master

_________________________

dcaegen2-services-master-bbs-event-processor-merge-java

_________________________

pmmapper and files-processing-config-pmmapper have no trigger jobs

_________________________

dcaegen2-collectors-ves-master-merge-java

(does neither produce nor push docker image! Instead, it's produced by dcaegen2-collectors-ves-maven-docker-stage-master - ticket raised:

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-2742
)

_________________________

dcaegen2-services-prh-master-merge-java

(does neither produce nor push docker image! Instead, it's produced by dcaegen2-services-prh-maven-docker-stage-master - ticket raised:

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-2743
)

_________________________

dcaegen2-collectors-restconf-master-merge-java

(does neither produce nor push docker image! Instead, it's produced by dcaegen2-collectors-restconf-maven-docker-stage-master - ticket raised:

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-2744
)

_________________________

dcaegen2-collectors-hv-ves-master-merge-java

(produces the docker image, but apparently does not push it? Instead, it - along with a few other images - is produced by dcaegen2-collectors-hv-ves-maven-docker-stage-master -  ticket raised:

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-2745
)

_________________________

Datafile CSITs have no trigger jobs

_________________________




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

______________________________________

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

from dcaegen2/services

______________________________________

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

from dcaegen2/services

______________________________________

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)


dcaegen2-services-son-handler-maven-docker-stage-master (but so do dcaegen2-services-son-handler-maven-docker-stage-honolulu and dcaegen2-services-son-handler-maven-docker-stage-guilin )

___________________

dcaegen2-services-pmsh-docker-merge-master

(but so do dcaegen2-services-pmsh-docker-merge-honolulu and dcaegen2-services-pmsh-docker-merge-guilin )

____________________

dcaegen2-services-master-bbs-event-processor-merge-java

(but then there's also dcaegen2-services-bbs-event-processor-maven-docker-stage-master and dcaegen2-services-master-bbs-event-processor-verify-java also doing this, as well as some of their previous branches)

____________________

dcaegen2-services-pm-mapper-maven-docker-stage-master 

____________________

dcaegen2-collectors-ves-maven-docker-stage-master

(but :latest is also produced by two previous branch jobs)

____________________

dcaegen2-services-prh-maven-docker-stage-master

(but :latest is also produced by two previous branch jobs)

____________________

dcaegen2-collectors-restconf-maven-docker-stage-master

(but :latest is also produced by two previous branch jobs)

____________________

dcaegen2-collectors-hv-ves-maven-docker-stage-master

(but :latest is also produced by two previous branch jobs)

____________________

dcaegen2-collectors-datafile-maven-docker-stage-master

(but :latest is also produced by two previous branch jobs)

____________________


Common ticket for all the DCAEGEN2 jobs regarding the use of "latest" raised: 

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-2746

A lot of simulators and other direct ambiguously referenced dependencies - TODO: raise a few tickets (this already caused an issue in pm-mapper that is using "latest" datarouter image)


dmaapTransition to project CSIT in progress - buscontroller tests are running under dmaap/buscontroller repository

dmaap/buscontroller

onap/dmaap/buscontroller:latest

______________________

dmaap/datarouter

nexus3.onap.org:10001/onap/dmaap/datarouter-proxv:latest

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

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

_______________________

dmaap/messagerouter/messageservice

dmaap-mr:1.2.20-STAGING-latest

dmaap-buscontroller-review-verification-maven-master

dmaap-buscontroller-merge-verification-maven-master


dmaap-buscontroller-review-verification-maven-honolulu

dmaap-buscontroller-merge-verification-maven-honolulu

_____________________

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

_____________________

dmaap-master-csit-mrpubsub


review and merge triggers

___________________


dmaap-datarouter-maven-docker-stage-master

___________________

mrpubsub CSIT has no triggers

dmaap/buscontroller

onap/dmaap/buscontroller

________________________

dmaap/datarouter

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

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)

_________________________

dmaap/messagerouter/messageservice

dmaap-mr:1.1.18 (hardcoded in docker-compose.yml checked out from the above repo


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

Built locally within the verification jobs

_________________________________________

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

_________________________________________

Latest version of dmaap-mr comes from dmaap-messagerouter-messageservice-java-11-maven-docker-stage-master, but this is 1.2.20-STAGING-latest. The tested 1.1.18 seems to come from some release job that no longer exists at all? (TODO: ticket)

TBD
modeling

modeling/etsicatalog

onap/modeling/etsicatalog

modeling-etsicatalog-master-csit-sanity-checkmodeling-etsicatalog-master-docker-java-version-shell-daily

modeling/etsicatalog

nexus3.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/library/mariadb

(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

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyMULTICLOUD-1231

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: 

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyMULTICLOUD-1229

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:

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOOM-2594
)

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: 

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOPTFRA-930



optf-cmso-master-csit-cmso

optf-osdf-master-csit-osdf

optf-has-master-csit-has

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOPTFRA-858

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)
sdcSDC has its legacy TestNG tests under sdc repo, incorporated into maven jobs

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-3302






sdnc


sdnc-master-csit-healthcheck

sdnc-master-csit-sdnc_netconf_tls_post_deploy



Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDNC-1381

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: 

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCCSDK-2915



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


TODO: macroflow



(The jobs below - as well as their previous branches - has been disabled under 

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-3632

so-master-csit-integration-etsi-testing

so-master-csit-integration-testing)











TBD - is distinction between images under test and image dependencies clear?
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


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVID-906

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: 

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVID-907

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:

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVNFSDK-701
)

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)?

...