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
Project | StatusBuild artifacts | Produced docker images | CSIT jobs | CSIT job triggers | Tested docker images and repositories | Docker build jobs that create the tested images | CSIT Dependencies | Comments | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
aai | No 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 | ccsdk | Project-specific CSIT in use under ccsdk/distribution | Produced 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 jobs | mysql/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)improved | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ccsdk-oran | Project-specific CSIT in use under ccsdk/oran | a1onap/ccsdk-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.0oran-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 | review 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 | 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) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
cps | Project-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?)CSIT in use under cps repository | cps-and-nf-proxy:latest (+various other images on which this is dependent) | master branch: honolulu branch: | review 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-handler son-handler.jar with maven org.onap.dcaegen2.services.pm-mapper:latest ____________________ pmsh is python-based; no artifacts in Nexus? org.onap.dcaegen2.services.son-handler:latest ____________________ bbs-event-processor.jar with maven onap/org.onap.dcaegen2.services.pmsh:latest ____________________ dcaegen2/services/pm-mapper pm-mapper.jar with maven onap/org.onap.dcaegen2.services.components.bbs-event-processor:latest ____________________ VESCollector.jar with maven org.onap.dcaegen2.collectors.ves.vescollector:latest ______________________ org.onap.dcaegen2.services.prh.prh-app-server.jar with maven:latest ___________________ restconfcollector.jar with mavenorg.onap.dcaegen2.collectors.restconfcollector:latest ___________________ org.onap.dcaegen2.collectors.hv-ves.hv-collector-main:latest (and few other ones that are not being tested nor used in CSIT?)Some half a dozen different jars with maven ____________________ org.onap.dcaegen2.collectors.datafile.datafile-app-server.jar with maven Produced by docker-maven-plugin: org.onap.dcaegen2.services.son-handler:latest :latest ________________________ All produced by docker-maven-plugins | dcaegen2/services Produced by docker-build.sh from ci-management: onap/org.onap.dcaegen2.services.pmsh:latest -services-pm-mapper-review-verification-maven-master dcaegen2-services-pm-mapper-merge-verification-maven-master/ _____________________ dcaegen2/services Produced by dockerfile-maven-plugin: onap/org.onap.dcaegen2.services.components.bbs-event-processor:latest-services-son-handler-master-csit-testsuites _____________________ Produced by docker-maven-plugin: org.onap.dcaegen2.services.pm-mapper:latest _____________________ Produced by docker-maven-plugin: org.onap.dcaegen2.collectors.ves.vescollector:latest _ dcaegen2-services-bbs-event-processor-master-csit-bbs-testsuites ______________________ dcaegen2-master-csit-testsuites ______________________ 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 -restconf-master-csit-testsuites _____________________ 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/datafileorg.onap.dcaegen2.collectors.datafile.datafile-app-server:latest-datafile-master-csit-ManagementInterface-suite dcaegen2-servicescollectors-son-handlerdatafile-master-csit-testsuites___-Functional-suite | pmshcsittestsuite (does neither produce nor push docker image! Instead, it's produced by dcaegen2-services-son-handler-maven-docker-stage-master - ticket raised:
____ ____________________ __ _______________________ _______________________ ______________________ dcaegen2-master-csit-prh-testsuites (does neither produce nor push docker image! Instead, it's produced by dcaegen2-collectors-ves-maven-docker-stage-master - ticket raised:
_________________________ _____________________ dcaegen2-collectors-hv-ves-master-csit-testsuites (does neither produce nor push docker image! Instead, it's produced by dcaegen2-services-prh-maven-docker-stage-master - ticket raised:
_________________________ ( 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 by dcaegen2-servicescollectors-son-handlerrestconf-maven-docker-stage-master - ticket ticket raised:
_________________________ dcaegen2-servicescollectors-pmsh-docker-merge-master _________________________ dcaegen2-services-master-bbs-event-processor-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:
____________________________ pmmapper and files-processing-config-pmmapper Datafile CSITs have no trigger jobs____________ | onap/org.onap.dcaegen2.services.pm-mapper:latest _____________ |
Jira | ||||||
---|---|---|---|---|---|---|
|
_________________________
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 | ||||||
---|---|---|---|---|---|---|
|
nexus3.onap.org:10003/onap/org.onap.dcaegen2.services.son-handler:latest from dcaegen2/services/son-handler
____________________________
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 | ||||||
---|---|---|---|---|---|---|
|
__________
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 | ||||||
---|---|---|---|---|---|---|
|
_________________________
Datafile CSITs have no trigger jobs
nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.pmsh:latest
from dcaegen2/services
______________________________________
nexus3.onap.org:1000310001/onap/org.onap.dcaegen2.services.components.sonbbs-event-handlerprocessor:latest
from dcaegen2/services/son-handler
______________________________________
nexus3.onap.org:1000110003/onap/org.onap.dcaegen2.collectors.servicesves.pmshvescollector:latestfrom dcaegen2/services
______________________________________
nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.componentsprh.bbsprh-eventapp-processorserver:latestfrom dcaegen2/services
______________________________________
nexus3.onap.org:10001/onap/org.onap.dcaegen2.servicescollectors.pm-mapperrestconfcollector:latest
______________________________________
nexus3.onap.org:1000310001/onap/org.onap.dcaegen2.collectors.hv-ves.vescollectorhv-collector-main:latest
______________________________________
nexus3.onap.org:10001/onap/org.onap.dcaegen2.servicescollectors.prhdatafile.prhdatafile-app-server:latest
______________________________________
nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.restconfcollector:latest
________________(all hardcoded in various places in the tests)
Built locally within the verification jobs
___________________
nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.hv-ves.hv-collector-main:latest
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-collectors-ves-maven-docker-stage-master
(but :latest is also produced by two previous branch jobs)
____________________
dcaegen2-services-son-handlerprh-maven-docker-stage-master (but so do dcaegen2-services-son-handler-maven-docker-stage-honolulu and dcaegen2-services-son-handler-maven-docker-stage-guilin
(but :latest is also produced by two previous branch jobs)
____________________
dcaegen2-servicescollectors-pmshrestconf-maven-docker-mergestage-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 so do dcaegen2-services-pmsh-docker-merge-honolulu and dcaegen2-services-pmsh-docker-merge-guilin )
____________________
dcaegen2-servicescollectors-masterdatafile-bbsmaven-eventdocker-processorstage-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 branchesmaster
(but :latest is also produced by two previous branch jobs)
____________________
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)
Common ticket for all the DCAEGEN2 jobs regarding the use of "latest" raised:
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
onap/dmaap/buscontroller:latest
______________________
dcaegen2-services-prh-maven-docker-stage-master
(but :latest is also produced by two previous branch jobs)
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
______________________
dcaegen2-collectors-restconf-maven-docker-stage-master
(but :latest is also produced by two previous branch jobs)
_
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
_____________________
(but :latest is also produced by two previous branch jobs)
_____________________
(but :latest is also produced by two previous branch jobs)
Review and merge triggers
___________________
Common ticket for all the DCAEGEN2 jobs regarding the use of "latest" raised:
Jira | ||||||
---|---|---|---|---|---|---|
|
(not directly related to CSIT issues, but there also seem to be two separate jobs pushing release docker images for pm-mapper - dcaegen2-services-pm-mapper-release-merge and dcaegen2-services-pm-mapper-release-verify, VESCollector dcaegen2-collectors-ves-release-merge and dcaegen2-collectors-ves-release-verify,
prh and possibly several others? Maybe worth a ticket)
onap/dmaap/buscontroller
___
onap/dmaap/buscontroller:latest
______________________
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
dmaap-buscontroller-review-verification-maven-master
dmaap-buscontroller-merge-verification-maven-master
dmaap-buscontroller-review-verification-maven-honolulu
dmaap-buscontroller-merge-verification-maven-honolulu
(all hardcoded, version not given so latest by default)
Built locally within the verification jobs
_________________________________________
stage-master (same as job trigger)
_____________________
review and merge triggers
____________________
Latest version of dmaap-mr comes from dmaap
___________________
mrpubsub CSIT has no triggers
onap/dmaap/buscontroller
onap/modeling/etsicatalog
Built by shell script
________________________
nexus3.onap.org:10001/onap/dmaap/datarouter-proxvnexus3.onap.org:10001/onap/
modeling/etsicatalog (latest by default, ticket raised:
Jira | ||||||
---|---|---|---|---|---|---|
|
consul:0.9.3
nexus3.onap.org:10001/onap/
(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)
msb/msb_discovery
nexus3.onap.org:10001/onap/msb/msb_apigateway
nexus3.onap.org:10001/library/mariadb
onap/multicloud/openstack-fcaps:1.5.6
onap/multicloud/openstack-starlingx:1.5.6
onap/multicloud/vio:1.4.2
onap/multicloud/framework:1.6.0
All produced by maven-resources-plugin and maven-antrun-plugin
___________________
multicloud-master-csit-functionality1
___________________
___________________
No trigger jobs
nexus3.onap.org:10001/onap/multicloud/openstack-fcaps:1.5.6
___________________________________________________
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)
nexus3.onap.org:10001/onap/multicloud/vio:1.4.2
nexus3.onap.org:10001/onap/multicloud/framework:1.6.0
____________________________________________________
onap/modeling/etsicatalog
nexus3.onap.org:10001/onap/
multicloud/openstack-starlingx
(ticket raised on the use of "latest":
Jira | ||||||
---|---|---|---|---|---|---|
|
____________________________________________________
nexus3.onap.org:10001/onap/
multicloud/
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)
vio
(the use of "latest" mentioned in
Jira | ||||
---|---|---|---|---|
|
multicloud-master-csit-functionality1
Jira | ||||||
---|---|---|---|---|---|---|
|
Latest in Nexus3:
onap/multicloud/
openstack-fcaps:1.4.1 is from Sep 04 2019
multicloud-openstack-maven-docker-stage-elalto produces version 1 nexus3.onap.org:10001/onap/multicloud/framework: 1.4.13 of onap/multicloud/openstack-fcaps
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)fcaps:1.5.6 generated by multicloud-openstack-maven-docker-stage-master
__________________________
Latest in Nexus:
onap/multicloud/vio:1.4.1 is from Sep 12 2019
onapmulticloud-framework-maven-docker-stage-master produces version 1.6.0 (and also latest) of onap/multicloud/framework:1.4.1 is from Sep 06 2019
...these seem to be some early El-Alto versions?
Ticker raised: Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key MULTICLOUD-1229
multicloud-openstack-maven-docker-stage-master produces version 1.5.6 (and also latest) ofonap/multicloud/openstack-fcaps and https://jenkins.onap.org/view/multicloud/job/multicloud-openstack-maven-docker-stage-elalto produces version 1.4.3 of onap/multicloud/openstack-starlingxhttps://jenkins.onap.org/view/multicloud/job/multicloud-framework
multicloud-openstack-vmware-maven-docker-stage-master produces produces version 1.64.0 2 (and also latest) of onapof onap/multicloud/frameworkviomulticloud
multicloud-openstack-vmware-maven-docker-stage-master produces version 1.4.2 (and also latest) of onap/multicloud/vio
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-serviceoom-platform-cert-service-master-csit-certservice
____________________
oom-platform-cert-service-master-merge-java (triggers two CSITs but does not produce or trigger docker image? Ticket raised:
Jira | ||||||
---|---|---|---|---|---|---|
|
nexus3.onap.org:10001/onap/org.onap.oom.platform.cert-service.oom-certservice-api:latest
__________________________
nexus3.onap.org:10001/onapnexus3.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
Transition to project-specific CSIT in progress:
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
nexus3.onap.org:10003nexus3.onap.org:10001/onap/optf-cmso-service:latestnexus3.onap.org:10001/onap/optf-cmso-dbinit:latestosdf:latest
__________________________
nexus3.onap.org:1000110003/onap/optf-cmso-topologyhas:latest
_________________________
nexus3nexus3.onap.org:10001/onap/optf-cmso-ticketmgtservice:latest
nexus3.onap.org:10001/onap/optf-cmso-optimizerdbinit:latest
nexus3.onap.org:10001/onap/optf-cmso-robottopology: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-cmso-osdfticketmgt:2latest
nexus3.0.3-SNAPSHOT-onap.org:10001/onap/optf-cmso-optimizer:latest
nexus3.onap.org:10001/onap/optf-cmso-has:2.1.2-SNAPSHOT-latest
Repositories:
robot:latest
All generated by docker-maven-plugin
optf-osdf-review-verification-maven-master
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-mastermerge-osdfverification-mergemaven-javamaster
optf-hasosdf-masterreview-conductorverification-mergemaven-javahonolulu
policyoptf-masterosdf-csitmerge-apexverification-pdp
policy-master-csit-distribution
policy-master-csit-drools-applications
(+frankfurt branches for each)
________________
optf-has-review-verification-maven-master
optf-has-merge-verification-maven-master
optf-has-review-verification-maven-honolulu
optf-has-merge-verification-maven-honolulu
__________________
No trigger jobs
nexus3.onap.org:10003/onap/optf-osdf:latest
__________________________
nexus3.onap.org:10003/onap/optf-has:latest
_________________________
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 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-distribution-master-merge-java
policy-drools-applications-master-merge-java
policy-drools-pdp-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"
onap/sdnc-image
onap/sdnc-ansible-server-image
onap/sdnc-ueb-listener-image
onap/sdnc-dmaap-listener-image
All built with docker maven plugin
sdnc-oam-review-verification-maven-master
sdnc-oam-merge-verification-maven-master
Review and merge triggers
onap/sdnc-image
onap/sdnc-ansible-server-image
onap/ccsdk-dgbuilder-image
onap/sdnc-ueb-listener-image
onap/sdnc-dmaap-listener-image
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
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
(The jobs below - as well as their previous branches - has been disabled under
Jira | ||||||
---|---|---|---|---|---|---|
|
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
policy-apex-pdp-master-merge-java
policy-distribution-master-merge-java
policy-drools-applications-master-merge-java
policy-drools-pdp-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
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 | ||||||
---|---|---|---|---|---|---|
|
|
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 | ||||||
---|---|---|---|---|---|---|
|
nexus3.onap.org:10001/onap/sdnc-image/1.8-STAGING-latestnexus3.onap.org:10001/onap/sdnc-ansible-server-image/1.8/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
onap/so/sdc-controller:1.8.1-STAGING-latest
nexus3.onap.org:10001/onapso/admportal-sdnc-image/bpmn-infra:1.8.1-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
---_________________________
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/sdncbpmn-image/infra: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 server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CCSDK-2915
primekey/ejbca-ce:6.15.2.50
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/org.onap.aaf.certservice.aaf-certservice-api:latest/so/sdc-controller:1.8.0 ---
nexus3.onap.org:10001/mariadb:10.1.11
so-master-csit-integration-etsi-testing
so-master-csit-integration-testing
(and the same for frankfurt and elalto; see
Jira | ||||||
---|---|---|---|---|---|---|
|
/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)
________________________
Jira | ||||||
---|---|---|---|---|---|---|
|
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/integration/sosimulators/sdncnetconf-pnp-adaptersimulator:12.38.16
nexus3.onap.org:10001/onap/so/openstackccsdk-adapterblueprintsprocessor:1.3.1.0.3
mariadb:latest
onap/sdnc-image:latest
simulators/aai-simulator:latest
nexus3.onap.org:10001/onap/so/vfc-adapter::1.3.1nexus3.onap.org:10001/onap/so/sdc-mariadb:10.1.11
______________________________
mariadb:latest
mysql/mysql-server:5.6 controller:1.3.1
nexus3.onap.org:10001/onap/integration/sosimulators/bpmnnetconf-pnp-infrasimulator:12.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)
Jira | ||||||
---|---|---|---|---|---|---|
|
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
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?
onap/vfc/vnflcm-1.4.1-*-latest
_________________________
onap/vfc/vnfres-1.3.9-*-latest
__________________________
onap/vfc/gvnfmdriver-1.4.1-*-latest
__________________________
onap/vfc/nslcm-1.4.3-*-latest
__________________________
All images built with shell scripts
vfcvfc-gvnfm-vnflcm-master-csit-sanity-check
______________________
vfc-gvnfm-vnfres-master-csit-sanity-check-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-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/vnflcm10001/onap/vfc/vnfres
__________________________
nexus3.onap.org:10001/onap/vfc/vnfresnexus3.onap.org:10001/onap/vfc/gvnfmdrivergvnfmdriver
__________________________
nexus3.onap.org:10001/onap/vfc/nslcm
(all latest by default)
Source repositories:
__________________________
(all latest by default)vfc/nfvo/lcm
consul:0.9.3
nexus3.onap.org:10001/onap/msb/msb_discovery
nexus3.onap.org:10001/onap/msb/msb_a
pigatewayapigateway
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 dependenciesdependencies
- 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
onap/vid:7.0-STAGING-latest
generated with docker-maven-plugin
vidNo trigger jobs
nexus3.onap.org:10001/onap/vid:67.0-STAGING-latest
Source repo is vid
vid-maven-docker-stage-frankfurtvid-maven-docker-stage-master produces 78.0.0 2 versions except for STAGING-latest, which is somehow still 67.0 - however, this is problematic as Frankfurt Guilin also produces 67.0-STAGING-latest images. Ticket raised:
Jira | ||||||
---|---|---|---|---|---|---|
|
nexus3.onap.org:10001/library/mariadb:10
so-simulator (specific to this suite)
aai-simulator (specific to this suite)
(specific to this suite)
aai-simulator (specific to this suite)
- The CSITs have been failing for a while now:
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VID-923
onap/vnfsdk/refrepo/postgres:latest
onap/vnfsdk/refrepo:latest
generated with docker-maven-plugin
No trigger jobs
vnfsdk-refrepo-master-merge-java
(for both CSITs; however, this job does not produce or trigger any docker image? Ticket raised:Jira | ||||||
---|---|---|---|---|---|---|
|
nexus3.onap.org:10001/onap/vnfsdk/refrepo/postgres:latest
nexus3.onap.org:10001/onap/vnfsdk/refrepo:latestSource repo is vnfsdk/refrepo
onap/vnfsdk/refrepo/postgres
hasn't been produced since Jul 09 2019, ticket raised:
Jira | ||||||
---|---|---|---|---|---|---|
|
- 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?
Disabled projects
Projects with CSIT | Build ArtifactsDocker images | CSIT jobs | CSIT job triggers | Tested docker images and repositories | Docker build jobs that create the tested images | Dependencies | Comments | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
aaf (disabled) | TBD | TBDaaf-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 modeProject unmaintained, CSIT disabled:
| ||||||||||
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 Project unmaintained, CSIT disabled:
| |||||||||||
clamp (disabled) | Invalid trigger jobs removed in Jira | | |||||||||||||||
server | ONAP JIRA | ||||||||||||||||
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb | key | CLAMP-950nexus3.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 server | ONAP JIRA | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb | key | CLAMP-957 | mariadb:10.5.4 python:2-slim | In maintenance mode, CSIT Project unmaintained, CSIT disabled: | ||||||
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 Project unmaintained, CSIT disabled: |