Versions Compared

Key

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

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

...

SDNC-1533



ProjectStatusProduced docker imagesCSIT jobs CSIT job triggersTested docker images and repositoriesDocker build jobs that create the tested imagesCSIT DependenciesComments
aaiNo existing CSITs in Jenkins (even though there are some under integration/csit)------Existing Scala + Gatling-based tests are to be incorporated into maven builds for multi-tenancy verification

ccsdk

Project-specific CSIT in use under ccsdk/distribution

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 

ccsdk-oranProject-specific CSIT in use under ccsdk/oranonap/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

cpsProject-specific CSIT in use under cps repository

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 
dcaegen2

Transition to project CSIT has started - PM-Mapper CSITs are being moved under dcaegen2/services/pm-mapper, everything else is still running from integration/csit

 in use, no current plans to move the tests to dcaegen2 repositories

dcaegen2/services/sonpm-handlermapper

org.onap.dcaegen2.services.sonpm-handlermapper:latest

____________________

dcaegen2/services/son-handler

onap/org.onap.dcaegen2.services.pmshson-handler:latest

____________________

dcaegen2/services

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

____________________

dcaegen2/services

onap/pm-mapperorg.onap.dcaegen2.services.components.pmbbs-event-mapperprocessor:latest

____________________

dcaegen2/collectors/ves

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

____________________

dcaegen2/services/prh

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

________________________

All produced by docker-maven-plugins

dcaegen2-services-son-handler-pm-mapper-review-verification-maven-master-csit-testsuites

dcaegen2-services-pm-mapper-merge-verification-maven-master/

_____________________

dcaegen2-services-son-pmshhandler-master-csit-testsuitetestsuites

______________________

dcaegen2-services-bbspmsh-event-processor-master-csit-bbs-testsuitestestsuite

______________________

dcaegen2-pmmapper-services-bbs-event-processor-master-csit-bbs-pmmappertestsuites

______________________

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

Review and merge triggers

__________________

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 Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
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 Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
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 Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
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 Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
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 Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-2745
)

_________________________

Datafile CSITs have no trigger jobs



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

______________________________________

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

______________________________________

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

from dcaegen2/services

______________________________________

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

from dcaegen2/services

______________________________________

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-Built locally within the verification jobs

___________________

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 Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-2746

A lot of simulators and other direct ambiguously referenced dependencies 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-2792
 


dmaapTransition to project CSIT in progress - buscontroller tests are already running under dmaap/buscontroller repository and the rest planned

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

_________________________

dmaap/messagerouter/messageservice

dmaap-mr


(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

kafka111, zookeeper, mariadb - some of these referred to just as "latest"
modelingintegration/csit in use, no current plans to move the tests to modeling/etsicatalog

modeling/etsicatalog

onap/modeling/etsicatalog

Built by shell script

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, ticket raised:

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMODELING-518
)

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



multicloudintegration/csit in use, no current plans to move the tests to multicloud repositories

multicloud/openstack

onap/multicloud/openstack-fcaps:1.5.6

onap/multicloud/openstack-starlingx:1.5.6

multicloud/openstack/vmware

onap/multicloud/vio:1.4.2

multicloud/framework

onap/multicloud/framework:1.6.0


All produced by maven-resources-plugin and maven-antrun-plugin

multicloud-fcaps-master-csit-functionality1

___________________

multicloud-master-csit-functionality1

___________________

multicloud-starlingx-master-csit-functionality1

___________________

multicloud-vmware-master-csit-functionality1

No trigger jobs

nexus3.onap.org:10001/onap/multicloud/openstack-fcaps:1.5.6

___________________________________________________


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

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

____________________________________________________

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

(ticket raised on the use of "latest": 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMULTICLOUD-1349
)

____________________________________________________

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

(all hardcoded, default latest for those that do not define version explicitly - TODO: raise a ticket)

Latest in Nexus3:

onap/multicloud/openstack-fcaps:1.the use of "latest" mentioned in 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMULTICLOUD-1349
, but there is no risk of conflict here as there's no El-Alto branch for the docker job)


Latest in Nexus3:

onap/multicloud/openstack-fcaps:1.4.1 is from Sep 04 2019

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

nexus3.onap.org:10001/onap/multicloud/openstack-fcaps:1.5.6 generated by multicloud-openstack-maven-docker-stage-master 

__________________________

Latest in Nexus:

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) ofonap/multicloud/openstack-fcaps and onap/multicloud/openstack-starlingx

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

Why are there jobs only for el-Alto and master? Worth a ticket?


-
oom-platform-cert-serviceintegration/csit in use, no current plans to move the tests to oom/platform/cert-service repository

oom/platform/cert-service

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

onap/org.onap.oom.platform.cert-service.oom-certservice-post-processor:latest

generated by docker-maven-plugin

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

____________________

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

No trigger jobs

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


  • Images from guilin are tagged with "guilin-latest", so the risk of conflicts is significantly reduced - TODO: discuss whether this should be taken as a best practice 
optf

Transition to project-specific CSIT in progress: 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOPTFRA-930

Already done for optf/osdf and optf/has while optf/cmso is still pending

optf/osdf

nexus3.onap.org:10003/onap/optf-osdf:latest

__________________________

 optf/has

nexus3.onap.org:10003/onap/optf-has:latest

_________________________

optf/cmso

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

All generated by docker-maven-plugin


optf-osdf-review-verification-maven-master

optf-osdf-merge-verification-maven-master


optf-osdf-review-verification-maven-honolulu

optf-osdf-merge-verification-maven-honolulu

________________

optf-has-review-verification-maven-master

optf-has-merge-verification-maven-master


optf-has-review-verification-maven-honolulu

optf-has-merge-verification-maven-honolulu

__________________

optf-cmso-master-csit-cmso


No trigger jobs

optf/osdf

nexus3.onap.org:10003/onap/optf-osdf:latest

__________________________

 optf/has

nexus3.onap.org:10003/onap/optf-has:latest

_________________________

optf/cmso

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)


optf-osdf and optf-has images built locally within the verification jobs

__________________________

optf-cmso-maven-docker-stage-master

(the frankfurt versions of the above jobs are also  pushing the same images with "latest" - waiving a ticket for now since the cmso is to be moved under project)

nexus3.onap.org:10001/onap/aaf/sms

(this was produced by some aaf-sms job that no longer even exists - is this safe?)


policy

Policy projects have somewhat of a hybrid model; all the policy CSITs have been moved to project repositories, but they are using custom templates for separate CSIT jobs that are still executed after reviews and merges

Also, guilin and frankfurt branches are still running maintenance CSITs from integration/csit


policy-apex-pdp-master-project-csit-apex-pdp

policy-api-master-project-csit-api

policy-distribution-master-project-csit-distribution

policy-drools-applications-master-project-csit-drools-applications

policy-drools-pdp-master-project-csit-drools-pdp

policy-pap-master-project-csit-pap

policy-xacml-pdp-master-project-csit-xacml-pdp


policy-apex-pdp-honolulu-project-csit-apex-pdp

policy-api-honolulu-project-csit-api

policy-distribution-honolulu-project-csit-distribution

policy-drools-applications-honolulu-project-csit-drools-applications

policy-drools-pdp-honolulu-project-csit-drools-pdp

policy-pap-honolulu-project-csit-pap

policy-xacml-pdp-honolulu-project-csit-xacml-pdp


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


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

Same as triggersPolicy components have a lot of dependencies between each other and the CSITs are currently working more like integration tests rather than proper project-specific functional testsPolicy 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







sdncintegration/csit in use, move to Project-specific CSIT in use under sdnc/oam repository in progress

sdnc/oam

onap/sdnc-image/2.2-STAGING-latest

onap/sdnc-ansible-server-image/2.2-STAGING-latest

onap/sdnc-ueb-listener-image/2.2-STAGING-latestnexus3.

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

All built with docker maven plugin

sdnc-oam-review-masterverification-csitmaven-healthcheckmaster

sdnc-oam-mastermerge-verification-csit-sdnc_netconf_tls_post_deploy

No trigger jobs

maven-master



Review and merge triggers

sdnc/oam

nexus3.onap.org:10001//sdnc-image

onap/sdnc-ansible-server-image

onap/2.1ccsdk-STAGING-latest

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

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

nexus3.onap.org:10001/onap/dgbuilder-image

onap/sdnc-ueb-listener-image/2.1-STAGING-latestnexus3.onap.org:

10001/onap/sdnc-dmaap-listener-image/2.1-STAGING-latest

___________________________

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

2.1-STAGING-latest images are coming from sdnc-oam-maven-docker-stage-honolulu, while the 2.2-STAGING-latest versions that sdnc-oam-maven-docker-stage-master -ticket raised: 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDNC-1541

The latest onap/ccsdk-dgbuilder-image/1.1-STAGING-latest in Nexus3 is from Fri Sep 01 2017 (?!), and the closest to that is https://jenkins.onap.org/view/ccsdk/job/ccsdk-distribution-maven-docker-stage-honolulu producing 1.1-SNAPSHOT-latest images (which are neither the latest - master is producing 1.2-SNAPSHOT-latest images - nor actually used in CSIT) - ticket raised: 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
key

Built locally within the verification jobs


mariadb:10.5

_______________

wurstmeister/zookeeper

wurstmeister/kafka:1.1.0

onap/org.onap.integration.simulators.netconfsimulator

onap/org.onap.integration.simulators.netopeer

atmoz/sftp:alpine

stilliard/pure-ftpd:latest





sointegration/csit in use, no current plans to move the tests to so repository

so

onap/so/catalog-db-adapter:1.8.1-STAGING-latest
onap/so/request-db-adapter:1.8.1-STAGING-latest
onap/so/sdnc-adapter:1.8.1-STAGING-latest
onap/so/openstack-adapter:1.8.1-STAGING-latest
onap/so/sdc-controller:1.8.1-STAGING-latest
onap/so/bpmn-infra:1.8.1-STAGING-latest
onap/so/api-handler-infra:1.8.1-STAGING-latest

all generated with docker-maven-plugin


so-master-csit-macroflow

so-honolulu-csit-macroflow

so-guilin-csit-macroflow


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

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-3632

so-master-csit-integration-etsi-testing

so-master-csit-integration-testing)


No trigger jobs

nexus3.onap.org:10001/onap/so/catalog-db-adapter:1.8.0-STAGING-latest
nexus3.onap.org:10001/onap/so/request-db-adapter:1.8.0-STAGING-latest
nexus3.onap.org:10001/onap/so/sdnc-adapter:1.8.0-STAGING-latest
nexus3.onap.org:10001/onap/so/openstack-adapter:1.8.0-STAGING-latest
nexus3.onap.org:10001/onap/so/sdc-controller:1.8.0-STAGING-latest
nexus3.onap.org:10001/onap/so/bpmn-infra:1.8.0-STAGING-latest
nexus3.onap.org:10001/onap/so/api-handler-infra:1.8.0-STAGING-latest


Both https://jenkins.onap.org/view/so/job/so-maven-docker-stage-master and https://jenkins.onap.org/view/so/job/so-maven-docker-stage-honolulu generate versions 1.8.1-STAGING-latest - however, the Macroflow CSIT does not pass with these. Ticket raised: 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-3633

Also, https://jenkins.onap.org/view/so/job/so-maven-docker-stage-guilin/ is generating 1.7.8-STAGING-latest even when version 1.7.12 is already released? Ticket raised: 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-3634


nexus3.onap.org:10001/mariadb:10.5.8

(simulators below are specific to SO CSIT suites)

simulators/sdc-simulator:latest
simulators/aai-simulator:latest
jobs/workaround-job-container:latest
simulators/sdnc-simulator:latest
simulators/multicloud-simulator:latest


usecasesintegration/csit in use

so

onap/so/sdc-controller:1.8.1-STAGING-latest
onap/so/bpmn-infra:1.8.1-STAGING-latest

_________________________

 sdnc/oam ?

usecases-pnf-sw-upgrade-master-csit-pnf-sw-upgrade

_______________

usecases-config-over-netconf-master-csit-config-over-netconf

No trigger jobs

nexus3.onap.org:10001/onap/so/bpmn-infra:1.8.0
nexus3.onap.org:10001/onap/so/sdnc-adapter:1.8.0
nexus3.onap.org:10001/onap/so/api-handler-infra:1.8.0
nexus3.onap.org:10001/onap/so/request-db-adapter:1.8.0

nexus3.onap.org:10001/onap/so/sdc-controller:1.8.0
nexus3.onap.org:10001/onap/so/catalog-db-adapter:1.8.0

____________________________________

onap/ccsdk-blueprintsprocessor:latest ?
onap/sdnc-image:latest ?
onap/sdnc-ansible-server-image:latest ?

which of these are the primary images under test? SDNC?

so-release-merge (but this is wrong, makes no sense to test released images in CSIT)

________________________

 sdnc-oam-maven-docker-stage-master ?

nexus3.onap.org:10001/onap/integration/simulators/netconf-pnp-simulator:2.8.6
nexus3.onap.org:10001/onap/ccsdk-blueprintsprocessor:1.0.3
mariadb:latest
onap/sdnc-image:latest
simulators/aai-simulator:latest
nexus3.onap.org:10001/mariadb:10.1.11

______________________________

mariadb:latest
mysql/mysql-server:5.6
nexus3.onap.org:10001/onap/integration/simulators/netconf-pnp-simulator:2.8.6

  • It's unclear if these are appropriate functional tests at all; they do not belong clearly to any single repository and refer to fixed, released image versions?
vfcintegration/csit in use, no current plans to move the tests to vfc repositories

vfc/gvnfm/vnflcm

onap/vfc/vnflcm-1.4.1-*-latest

_________________________

vfc/gvnfm/vnfres

onap/vfc/vnfres-1.3.9-*-latest

__________________________

vfc/nfvo/driver/vnfm/gvnfm

onap/vfc/gvnfmdriver-1.4.1-*-latest

__________________________

vfc/nfvo/lcm

onap/vfc/nslcm-1.4.3-*-latest

__________________________

All images built with shell scripts


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


vfc/gvnfm/vnflcm

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

_________________________

vfc/gvnfm/vnfres

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

__________________________

vfc/nfvo/driver/vnfm/gvnfm

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

__________________________

vfc/nfvo/lcm

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

__________________________

(all latest by default)


Same as triggers

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

redis (!?)

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



  • All jobs are for master, no maintenance releases?
  • All images are tagged with SNAPSHOT and STAGING at the same time?
  • CSITs are using default latest for everything 
vidintegration/csit in use, no current plans to move the tests to vid repository

vid

onap/vid:7.0-STAGING-latest

generated with docker-maven-plugin


vid-master-csit-healthCheck


No trigger jobs

vid

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

vid-maven-docker-stage-master produces 8.0.2 versions except for STAGING-latest, which is still 7.0 - however, this is problematic as Guilin also produces 7.0-STAGING-latest images. Ticket raised: 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVID-984

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

so-simulator (specific to this suite)

aai-simulator (specific to this suite)


  • The CSITs have been failing for a while now: 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyVID-923
vfsdkintegration/csit in use, no current plans to move the tests to vnfsdk/refrepo repository

vnfsdk/refrepo

onap/vnfsdk/refrepo/postgres:latest

onap/vnfsdk/refrepo:latest

generated with docker-maven-plugin


vnfsdk-marketplace-master-csit-testsuites

vnfsdk-refrepo-master-csit-testsuites

No trigger jobs

vnfsdk/refrepo

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

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




vnfsdk-refrepo-maven-docker-stage-master

 onap/vnfsdk/refrepo/postgres hasn't been produced since Jul 09 2019, ticket raised: 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVNFSDK-768




  • The CSITs are testing "latest" images, which is ambiguous - however, the frankfurt branch does not push "latest" so there is no concrete risk of conflict
  • Frankfurt branch is the last release branch, no Guilin or Honolulu? Is this project still maintained?

...