SDC Documentation
Administration
Administration Links
Here are some links to our administration pages found in the ONAP Service websites
SDC Architecture
Please refer to the SDC Kohn architecture description page, to get a full picture of SDC and its relationships within ONAP
Configuration
Global Configuration
SDC configuration is applied by several init containers running Chef recipes The files below describe the environment files that are applied on startup
environment.json
{
# Environment name
"name": "xxx",
# Environment description
"description": "OpenSource-xxx",
"json_class": "Chef::Environment",
"chef_type": "environment",
"default_attributes": {
"disableHttp": false,
# IPs used for docker configuration
"CS_VIP": "yyy",
"BE_VIP": "yyy",
"ONBOARDING_BE_VIP": "yyy",
"FE_VIP": "yyy",
"ES_VIP": "yyy",
"KB_VIP": "yyy",
"interfaces": {
"application": "eth0",
"private": "eth1"
},
# Configuration parameters used in portal properties
"ECompP": {
"ecomp_rest_url": "http://portal.api.simpledemo.onap.org:8989/ONAPPORTAL/auxapi",
"ecomp_redirect_url": "http://portal.api.simpledemo.openecomp.org:8989/ECOMPPORTAL/login.htm",
"cipher_key": "AGLDdG4D04BKm2IxIWEr8o==",
"portal_user": "Ipwxi2oLvDxctMA1royaRw1W0jhucLx+grHzci3ePIA=",
"portal_pass": "j85yNhyIs7zKYbR1VlwEfNhS6b7Om4l0Gx5O8931sCI="
},
# Configuration parameters used by SDC to work with Dmaap
"UEB": {
"PublicKey": "iPIxkpAMI8qTcQj8",
"SecretKey": "Ehq3WyT4bkif4zwgEbvshGal",
"fqdn": ["10.0.11.1", "10.0.11.1"]
},
# Kafka config
"Kafka": {
"bootstrap": "kafka-bootstrap:9092"
},
# Messaging topics to be used by clients
"DistributionTopics": {
"notificationTopicName": "SDC-DISTR-NOTIF-TOPIC",
"statusTopicName": "SDC-DISTR-STATUS-TOPIC"
},
# IPs used for docker configuration
"Nodes": {
"CS": ["yyy"],
"BE": "yyy",
"ONBOARDING_BE": "yyy",
"FE": "yyy",
"ES": ["yyy"],
"KB": "yyy"
},
"Plugins": {
"DCAE": {
"dcae_discovery_url": "yyy",
"dcae_source_url": "yyy"
},
"WORKFLOW": {
"workflow_discovery_url": "yyy",
"workflow_source_url": "yyy"
}
},
"VnfRepo": {
"vnfRepoPort": "8702",
"vnfRepoHost": "10.0.14.1"
},
"HelmValidator": {
"validator_enabled": true,
"helm_version": "3.5.2",
"deployable": true,
"lintable": false,
"strict_lintable": false,
"validator_url": "http://sdc-helm-validator:8080/validate"
}
},
"override_attributes": {
# FE and BE listening ports
"FE": {
"http_port": "8181",
"https_port": "9443"
},
"BE": {
"http_port": "8080",
"https_port": "8443"
},
"ONBOARDING_BE": {
"http_port": "8081",
"https_port": "8445"
},
# Cassandra configuration
"cassandra": {
"concurrent_reads": "32",
"num_tokens": "256",
"data_dir": "/var/lib/cassandra/data",
"hinted_handoff_enabled": "true",
"cassandra_user": "sdc_user",
"cassandra_password": "changeme",
"concurrent_writes": "32",
"cluster_name": "SDC-CS-",
"datacenter_name": "SDC-CS-",
"multithreaded_compaction": "false",
"cache_dir": "/var/lib/cassandra/saved_caches",
"log_file": "/var/lib/cassandra/log/system.log",
"phi_convict_threshold": "8",
"commitlog_dir": "/var/lib/cassandra/commitlog",
"socket_read_timeout": "20000",
"socket_connect_timeout": "20000",
"janusgraph_connection_timeout": "10000"
}
}
}
Backend Configurations
Catalog Configurations
BE-configuration.yaml
# Request headers for identification of the user that made the request
identificationHeaderFields:
- HTTP_IV_USER
- HTTP_CSP_FIRSTNAME
- HTTP_CSP_LASTNAME
- HTTP_IV_REMOTE_ADDRESS
- HTTP_CSP_WSTYPE
# Catalog backend hostname
beFqdn: <%= @catalog_ip %>
# Catalog backend http port
beHttpPort: <%= @catalog_port %>
# Catalog backend http context
beContext: /sdc/rest/config/get
# Catalog backend protocol
beProtocol: http
# Catalog backend ssl port
beSslPort: <%= @ssl_port %>
# Catalog backend configuration version
version: 1.1.0
# Catalog backend configuration release date
released: 2012-11-30
# Catalog tosca current conformance version
toscaConformanceLevel: 5.0
# Catalog minimum tosca conformance version
minToscaConformanceLevel: 3.0
# JanusGraph configuration file location
janusGraphCfgFile: /var/lib/jetty/config/catalog-be/janusgraph.properties
# Does JanusGraph hold the persistence data in memory
janusGraphInMemoryGraph: false
# The timeout for JanusGraph to lock on an object in a transaction
janusGraphLockTimeout: 1800
# The interval to try and reconnect to JanusGraph DB when it is down during SDC startup
janusGraphReconnectIntervalInSeconds: 3
# The read timeout towards JanusGraph DB when health check is invoked
janusGraphHealthCheckReadTimeout: 1
# The interval to try and reconnect to UEB health check when it is down during SDC startup
uebHealthCheckReconnectIntervalInSeconds: 15
# The read timeout towards UEB when health check is invoked
uebHealthCheckReadTimeout: 4
# Protocols being used in SDC
protocols:
- http
- https
# Default imports
# Under each import there is the file the data will be imported from
defaultImports:
- nodes:
file: nodes.yml
- datatypes:
file: data.yml
- capabilities:
file: capabilities.yml
- relationships:
file: relationships.yml
- groups:
file: groups.yml
- policies:
file: policies.yml
- annotations:
file: annotations.yml
# Users
# Deprecated. Will be removed in future releases
users:
tom: passwd
bob: passwd
cassandraConfig:
# Cassandra hostname
cassandraHosts: <%= @cassandra_ip %>
# Cassandra local data center name
localDataCenter: <%= @DC_NAME %>
# The read timeout towards Cassandra when health check is invoked
reconnectTimeout : 30000
# The amount of time the Cassandra client will wait for a socket
socketReadTimeout: <%= @socket_read_timeout %>
# The amount of time the Cassandra client will wait for a response
socketConnectTimeout: <%= @socket_connect_timeout %>
# Should authentication be used when accessing Cassandra
authenticate: true
# Username for accessing Cassandra
username: asdc_user
# Password for accessing Cassandra
password: {{cassandra_password}}
# Should ssl be used
ssl: false
# Location of .truststore file
truststorePath : /config/.truststore
# The .truststore file password
truststorePassword : changeme
# Keyspaces configuration for Cassandra
keySpaces:
- { name: dox, replicationStrategy: NetworkTopologyStrategy, replicationInfo: ['<%= @DC_NAME %>','<%= @rep_factor %>']}
- { name: sdcaudit, replicationStrategy: NetworkTopologyStrategy, replicationInfo: ['<%= @DC_NAME %>','<%= @rep_factor %>']}
- { name: sdcartifact, replicationStrategy: NetworkTopologyStrategy, replicationInfo: ['<%= @DC_NAME %>','<%= @rep_factor %>']}
- { name: sdccomponent, replicationStrategy: NetworkTopologyStrategy, replicationInfo: ['<%= @DC_NAME %>','<%= @rep_factor %>']}
- { name: sdcrepository, replicationStrategy: NetworkTopologyStrategy, replicationInfo: ['<%= @DC_NAME %>','<%= @rep_factor %>']}
# Artifact types placeholder
artifactTypes:
- CHEF
- PUPPET
- SHELL
- YANG
- YANG_XML
- HEAT
- BPEL
- DG_XML
- MURANO_PKG
- WORKFLOW
- NETWORK_CALL_FLOW
- TOSCA_TEMPLATE
- TOSCA_CSAR
- AAI_SERVICE_MODEL
- AAI_VF_MODEL
- AAI_VF_MODULE_MODEL
- AAI_VF_INSTANCE_MODEL
- OTHER
- SNMP_POLL
- SNMP_TRAP
- GUIDE
- PLAN
# License types placeholder
licenseTypes:
- User
- Installation
- CPU
# Resource types placeholder
resourceTypes: &allResourceTypes
- VFC
- CP
- VL
- VF
- CR
- VFCMT
- Abstract
- CVFC
#Deployment resource artifacts placeHolder
deploymentResourceArtifacts:
# Deployment resource instance artifact placeholders
# For each artifact the following properties exist:
#
# displayName - The display name of the artifact
# type - The type of the artifact
# description - The description of the artifact
# fileExtension - The file extension of the artifact file for uploading
deploymentResourceInstanceArtifacts:
heatEnv:
displayName: "HEAT ENV"
type: HEAT_ENV
description: "Auto-generated HEAT Environment deployment artifact"
fileExtension: "env"
VfHeatEnv:
displayName: "VF HEAT ENV"
type: HEAT_ENV
description: "VF Auto-generated HEAT Environment deployment artifact"
fileExtension: "env"
# Tosca artifacts placeholders
# For each artifact there is a template and a csar.
# For each one the following properties exists:
#
# artifactName - The suffix of the artifact file
# displayName - The display name of the artifact
# type - The type of the artifact
# description - The description of the artifact
toscaArtifacts:
assetToscaTemplate:
artifactName: -template.yml
displayName: Tosca Template
type: TOSCA_TEMPLATE
description: TOSCA representation of the asset
assetToscaCsar:
artifactName: -csar.csar
displayName: Tosca Model
type: TOSCA_CSAR
description: TOSCA definition package of the asset
# Resource category to exclude
excludeResourceCategory:
- Generic
# Resource type to exclude
excludeResourceType:
- PNF
- CR
# Informational resource artifacts placeHolder
# For each artifact the following properties exists:
#
# displayName - The display name of the artifact
# type - The type of the artifact
informationalResourceArtifacts:
features:
displayName: Features
type: OTHER
capacity:
displayName: Capacity
type: OTHER
vendorTestResult:
displayName: Vendor Test Result
type: OTHER
testScripts:
displayName: Test Scripts
type: OTHER
CloudQuestionnaire:
displayName: Cloud Questionnaire (completed)
type: OTHER
HEATTemplateFromVendor:
displayName: HEAT Template from Vendor
type: HEAT
resourceSecurityTemplate:
displayName: Resource Security Template
type: OTHER
# Service category to exclude
excludeServiceCategory:
# Informational service artifacts placeHolder
# For each artifact the following properties exists:
#
# displayName - The display name of the artifact
# type - The type of the artifact
informationalServiceArtifacts:
serviceArtifactPlan:
displayName: Service Artifact Plan
type: OTHER
summaryOfImpactsToECOMPElements:
displayName: Summary of impacts to ECOMP elements,OSSs, BSSs
type: OTHER
automationCompositionFunctions:
displayName: Automation Composition Functions
type: OTHER
dimensioningInfo:
displayName: Dimensioning Info
type: OTHER
affinityRules:
displayName: Affinity Rules
type: OTHER
operationalPolicies:
displayName: Operational Policies
type: OTHER
serviceSpecificPolicies:
displayName: Service-specific Policies
type: OTHER
engineeringRules:
displayName: Engineering Rules (ERD)
type: OTHER
distributionInstructions:
displayName: Distribution Instructions
type: OTHER
certificationTestResults:
displayName: TD Certification Test Results
type: OTHER
deploymentVotingRecord:
displayName: Deployment Voting Record
type: OTHER
serviceQuestionnaire:
displayName: Service Questionnaire
type: OTHER
serviceSecurityTemplate:
displayName: Service Security Template
type: OTHER
# Service api artifacts placeHolder
# For each artifact the following properties exists:
#
# displayName - The display name of the artifact
# type - The type of the artifact
serviceApiArtifacts:
configuration:
displayName: Configuration
type: OTHER
instantiation:
displayName: Instantiation
type: OTHER
monitoring:
displayName: Monitoring
type: OTHER
reporting:
displayName: Reporting
type: OTHER
logging:
displayName: Logging
type: OTHER
testing:
displayName: Testing
type: OTHER
# The maximum number of keys permitted for additional information on service
additionalInformationMaxNumberOfKeys: 50
# Collect process statistics
systemMonitoring:
# Should monitoring be enabled
enabled: false
# In case of going through the FE server proxy the information to the BE
isProxy: false
# What is the interval of the statistics collection
probeIntervalInSeconds: 15
defaultHeatArtifactTimeoutMinutes: 60
# Service deployment artifacts placeHolder
# For each artifact the following properties exists:
#
# acceptedTypes - File types that can be uploaded as each artifact
serviceDeploymentArtifacts:
YANG_XML:
acceptedTypes:
- xml
VNF_CATALOG:
acceptedTypes:
- xml
MODEL_INVENTORY_PROFILE:
acceptedTypes:
- xml
MODEL_QUERY_SPEC:
acceptedTypes:
- xml
UCPE_LAYER_2_CONFIGURATION:
acceptedTypes:
- xml
#AAI Artifacts
AAI_SERVICE_MODEL:
acceptedTypes:
- xml
AAI_VF_MODULE_MODEL:
acceptedTypes:
- xml
AAI_VF_INSTANCE_MODEL:
acceptedTypes:
- xml
UCPE_LAYER_2_CONFIGURATION:
acceptedTypes:
- xml
OTHER:
acceptedTypes:
#PLAN
PLAN:
acceptedTypes:
- xml
WORKFLOW:
acceptedTypes:
# Resource deployment artifacts placeHolder
# For each artifact the following properties exists:
#
# acceptedTypes - File types that can be uploaded as each artifact
# validForRespurceTypes - Resource types that support each artifact.
# If left empty it means all resource types are valid
resourceDeploymentArtifacts:
HEAT:
acceptedTypes:
- yaml
- yml
validForResourceTypes: *allResourceTypes
HEAT_VOL:
acceptedTypes:
- yaml
- yml
validForResourceTypes: *allResourceTypes
HEAT_NET:
acceptedTypes:
- yaml
- yml
validForResourceTypes: *allResourceTypes
HEAT_NESTED:
acceptedTypes:
- yaml
- yml
validForResourceTypes: *allResourceTypes
HEAT_ARTIFACT:
acceptedTypes:
validForResourceTypes: *allResourceTypes
YANG_XML:
acceptedTypes:
- xml
validForResourceTypes: *allResourceTypes
VNF_CATALOG:
acceptedTypes:
- xml
validForResourceTypes: *allResourceTypes
VF_LICENSE:
acceptedTypes:
- xml
validForResourceTypes: *allResourceTypes
VENDOR_LICENSE:
acceptedTypes:
- xml
validForResourceTypes: *allResourceTypes
MODEL_INVENTORY_PROFILE:
acceptedTypes:
- xml
validForResourceTypes: *allResourceTypes
MODEL_QUERY_SPEC:
acceptedTypes:
- xml
validForResourceTypes: *allResourceTypes
LIFECYCLE_OPERATIONS:
acceptedTypes:
- yaml
- yml
validForResourceTypes:
- VF
- VFC
VES_EVENTS:
acceptedTypes:
- yaml
- yml
validForResourceTypes: *allResourceTypes
PERFORMANCE_COUNTER:
acceptedTypes:
- csv
validForResourceTypes: *allResourceTypes
APPC_CONFIG:
acceptedTypes:
validForResourceTypes:
- VF
DCAE_TOSCA:
acceptedTypes:
- yml
- yaml
validForResourceTypes:
- VF
- VFCMT
DCAE_JSON:
acceptedTypes:
- json
validForResourceTypes:
- VF
- VFCMT
DCAE_POLICY:
acceptedTypes:
- emf
validForResourceTypes:
- VF
- VFCMT
DCAE_DOC:
acceptedTypes:
validForResourceTypes:
- VF
- VFCMT
DCAE_EVENT:
acceptedTypes:
validForResourceTypes:
- VF
- VFCMT
AAI_VF_MODEL:
acceptedTypes:
- xml
validForResourceTypes:
- VF
AAI_VF_MODULE_MODEL:
acceptedTypes:
- xml
validForResourceTypes:
- VF
OTHER:
acceptedTypes:
validForResourceTypes: *allResourceTypes
SNMP_POLL:
acceptedTypes:
validForResourceTypes: *allResourceTypes
SNMP_TRAP:
acceptedTypes:
validForResourceTypes: *allResourceTypes
#PLAN
PLAN:
acceptedTypes:
- xml
validForResourceTypes:
- VF
- VFC
WORKFLOW:
acceptedTypes:
# Resource instance deployment artifacts placeHolder
# For each artifact the following properties exists:
#
# acceptedTypes - File types that can be uploaded as each artifact
# validForRespurceTypes - Resource types that support each artifact.
# If left empty it means all resource types are valid
resourceInstanceDeploymentArtifacts:
HEAT_ENV:
acceptedTypes:
- env
VF_MODULES_METADATA:
acceptedTypes:
- json
VES_EVENTS:
acceptedTypes:
- yaml
- yml
PERFORMANCE_COUNTER:
acceptedTypes:
- csv
DCAE_INVENTORY_TOSCA:
acceptedTypes:
- yml
- yaml
DCAE_INVENTORY_JSON:
acceptedTypes:
- json
DCAE_INVENTORY_POLICY:
acceptedTypes:
- emf
DCAE_INVENTORY_DOC:
acceptedTypes:
DCAE_INVENTORY_BLUEPRINT:
acceptedTypes:
DCAE_INVENTORY_EVENT:
acceptedTypes:
SNMP_POLL:
acceptedTypes:
validForResourceTypes: *allResourceTypes
SNMP_TRAP:
acceptedTypes:
validForResourceTypes: *allResourceTypes
#PLAN
PLAN:
acceptedTypes:
- xml
# Resource informational artifacts placeHolder
# For each artifact the following properties exists:
#
# acceptedTypes - File types that can be uploaded as each artifact
# validForRespurceTypes - Resource types that support each artifact.
# If left empty it means all resource types are valid
resourceInformationalArtifacts:
CHEF:
acceptedTypes:
validForResourceTypes: *allResourceTypes
PUPPET:
acceptedTypes:
validForResourceTypes: *allResourceTypes
SHELL:
acceptedTypes:
validForResourceTypes: *allResourceTypes
YANG:
acceptedTypes:
validForResourceTypes: *allResourceTypes
YANG_XML:
acceptedTypes:
validForResourceTypes: *allResourceTypes
HEAT:
acceptedTypes:
validForResourceTypes: *allResourceTypes
BPEL:
acceptedTypes:
validForResourceTypes: *allResourceTypes
DG_XML:
acceptedTypes:
validForResourceTypes: *allResourceTypes
MURANO_PKG:
acceptedTypes:
validForResourceTypes: *allResourceTypes
OTHER:
acceptedTypes:
validForResourceTypes:
- VFC
- CVFC
- CP
- VL
- VF
- CR
- VFCMT
- Abstract
- PNF
SNMP_POLL:
acceptedTypes:
validForResourceTypes: *allResourceTypes
SNMP_TRAP:
acceptedTypes:
validForResourceTypes: *allResourceTypes
GUIDE:
acceptedTypes:
validForResourceTypes:
- VF
- VFC
- CVFC
# Requirements needed to be fulfilled before certification
requirementsToFulfillBeforeCert:
# Capabilities needed to be fulfilled before certification
capabilitiesToConsumeBeforeCert:
# Urls that should not be logged
unLoggedUrls:
- /sdc2/rest/healthCheck
# When component is being set as deleted those are the clean configurations
cleanComponentsConfiguration:
# The interval to check for deleted components to clean
cleanIntervalInMinutes: 1440
# The components types to delete
componentsToClean:
- Resource
- Service
# Deprecated. Will be removed in future releases
artifactsIndex: resources
# Used to add header and footer to heatENV files generated by SDC
heatEnvArtifactHeader: ""
heatEnvArtifactFooter: ""
onboarding:
# Onboarding protocol
protocol: http
# Onboarding backend hostname
host: <%= @host_ip %>
# Onboarding backend http port
port: <%= @catalog_port %>
# The url that being used when downloading CSARs
downloadCsarUri: "/onboarding-api/v1.0/vendor-software-products/packages"
# Url for onboarding health check
healthCheckUri: "/onboarding-api/v1.0/healthcheck"
#GSS IDNS
# Switchover configuration is used for Geo redundancy to provide automatic failovers
switchoverDetector:
gBeFqdn:
gFeFqdn:
beVip: 1.2.3.4
feVip: 1.2.3.4
beResolveAttempts: 3
feResolveAttempts: 3
enabled: false
interval: 60
changePriorityUser: onapsdc
changePriorityPassword: changeme
publishNetworkUrl:
publishNetworkBody: '{"note":"comment"}'
groups:
beSet: { changePriorityUrl: "", changePriorityBody: '{"name":"","uri":"","no_ad_redirection":false,"v4groups":{"failover_groups":["","","failover_policy":["FAILALL"]},"comment":"","intended_app_proto":"DNS"}'}
feSet: { changePriorityUrl: "", changePriorityBody: '{"name":"","uri":"","no_ad_redirection":false,"v4groups":{"failover_groups":["",""],"failover_policy":["FAILALL"]},"comment":"","intended_app_proto":"DNS"}'}
# Cache for datatypes. Improving run times for data type search
applicationL1Cache:
datatypes:
enabled: true
firstRunDelay: 10
pollIntervalInSec: 60
# Deprecated. Will be removed in future releases
applicationL2Cache:
enabled: false
catalogL1Cache:
enabled: false
resourcesSizeInCache: 300
servicesSizeInCache: 200
productsSizeInCache: 100
queue:
syncIntervalInSecondes: 43200
waitOnShutDownInMinutes: 10
numberOfCacheWorkers: 4
# Validators for Tosca properties
toscaValidators:
stringMaxLength: 2500
# Should audit be disabled
disableAudit: false
# VF module validations properties
vfModuleProperties:
min_vf_module_instances:
forBaseModule: 1
forNonBaseModule: 0
max_vf_module_instances:
forBaseModule: 1
forNonBaseModule:
initial_count:
forBaseModule: 1
forNonBaseModule: 0
vf_module_type:
forBaseModule: Base
forNonBaseModule: Expansion
# For each generic node type defining its corresponding class
genericAssetNodeTypes:
VFC: org.openecomp.resource.abstract.nodes.VFC
CVFC: org.openecomp.resource.abstract.nodes.VFC
VF : org.openecomp.resource.abstract.nodes.VF
PNF: org.openecomp.resource.abstract.nodes.PNF
Service: org.openecomp.resource.abstract.nodes.service
# tenant isolation configuration
workloadContext: Production
# tenant isolation configuration
environmentContext:
defaultValue: General_Revenue-Bearing
validValues:
- Critical_Revenue-Bearing
- Vital_Revenue-Bearing
- Essential_Revenue-Bearing
- Important_Revenue-Bearing
- Needed_Revenue-Bearing
- Useful_Revenue-Bearing
- General_Revenue-Bearing
- Critical_Non-Revenue
- Vital_Non-Revenue
- Essential_Non-Revenue
- Important_Non-Revenue
- Needed_Non-Revenue
- Useful_Non-Revenue
- General_Non-Revenue
# tenant isolation configuration
dmaapConsumerConfiguration:
hosts: localhost:3905
consumerGroup: sdc
consumerId: mama
timeoutMs: 15000
limit: 1
pollingInterval: 2
topic: topic
latitude: 32.109333
longitude: 34.855499
version: 1.0
serviceName: localhost/events
environment: TEST
partner: BOT_R
routeOffer: MR1
protocol: https
contenttype: application/json
dme2TraceOn: true
aftEnvironment: AFTUAT
aftDme2ConnectionTimeoutMs: 15000
aftDme2RoundtripTimeoutMs: 240000
aftDme2ReadTimeoutMs: 50000
dme2preferredRouterFilePath: DME2preferredRouter.txt
timeLimitForNotificationHandleMs: 120000
credential:
username: user
password:
# tenant isolation configuration
dmeConfiguration:
dme2Search: DME2SEARCH
dme2Resolve: DME2RESOLVE
# definition for policies types that cannot by created by api
excludedPolicyTypesMapping:
# VF:
# - a.b.c
# - c.d.e
#CR:
# - x.y.z
# definition for group types that cannot by created by api
excludedGroupTypesMapping:
CR:
- org.openecomp.groups.VfModule
- org.openecomp.groups.heat.HeatStack
- tosca.groups.Root
PNF:
- org.openecomp.groups.VfModule
- org.openecomp.groups.heat.HeatStack
- tosca.groups.Root
VF:
- org.openecomp.groups.VfModule
- org.openecomp.groups.heat.HeatStack
- tosca.groups.Root
Service:
- org.openecomp.groups.VfModule
- org.openecomp.groups.heat.HeatStack
- tosca.groups.Root
healthStatusExclude:
- DE
- DMAAP
- DCAE
# This configuration entry lists all node type names prefix that shall be allowed on SDC.
definedResourceNamespace:
- org.openecomp.resource.
# Comma separated list of excluded URLs by the DataValidatorFilter
dataValidatorFilterExcludedUrls: "/healthCheck,/followed,/authorize"
BE-distribution-engine-configuration.yaml
# UEB servers list
uebServers:
<% node['UEB']['fqdn'].each do |conn| -%>
- <%= conn %>
<% end -%>
# UEB public key
uebPublicKey: <%= node['UEB']['PublicKey'] %>
# UEB secret key
uebSecretKey: <%= node['UEB']['SecretKey'] %>
# Topic name for receiving distribution notification
distributionNotifTopicName: SDC-DISTR-NOTIF-TOPIC
# Topic name for distribution status
distributionStatusTopicName: SDC-DISTR-STATUS-TOPIC
# Distribution initialization retry interval time
initRetryIntervalSec: 5
# Distribution initialization maximum interval time
initMaxIntervalSec: 60
# Deprecated. Will be removed in future releases
distribNotifServiceArtifactTypes:
info:
- MURANO-PKG
# Deprecated. Will be removed in future releases
distribNotifResourceArtifactTypes:
lifecycle:
- HEAT
- DG-XML
# Distribution environments
environments:
- <%= node.chef_environment %>
distributionStatusTopic:
# Distribution status polling interval
pollingIntervalSec: 60
# Distribution status fetch time
fetchTimeSec: 15
# Distribution status consumer group
consumerGroup: sdc-<%= node.chef_environment %>
# Distribution status consumer id
consumerId: sdc-<%= node.chef_environment %>1
distributionNotificationTopic:
# Minimum pool size for distribution notifications
minThreadPoolSize: 0
# Maximum pool size for distribution notifications
maxThreadPoolSize: 10
# Maximum waiting time after sending a notification
maxWaitingAfterSendingSeconds: 5
# Deprecated. Will be removed in future releases
createTopic:
partitionCount: 1
replicationCount: 1
# STarting the distribution engine
startDistributionEngine: true
#This is false by default, since ONAP Dmaap currently doesn't support https
# Should https be used with Dmaap
useHttpsWithDmaap: false
opEnvRecoveryIntervalSec: 180
allowedTimeBeforeStaleSec: 300
# aai configuration for tenant isolation
aaiConfig:
httpRequestConfig:
serverRootUrl: https://aai.onap.org:8443
resourceNamespaces:
operationalEnvironments: /aai/v12/cloud-infrastructure/operational-environments
httpClientConfig:
timeouts:
readTimeoutMs: 5000
connectTimeoutMs: 1000
clientCertificate:
keyStore: /opt/app/jetty/base/be/etc/non-prod.jks
keyStorePassword: changeme
headers:
X-FromAppId: asdc
numOfRetries: 3
# mso configuration for tenant isolation
msoConfig:
httpRequestConfig:
serverRootUrl: http://127.0.0.1:8080/onap/mso/infra/modelDistributions/v1
resourceNamespaces:
distributions: /distributions
httpClientConfig:
timeouts:
readTimeoutMs: 2000
connectTimeoutMs: 500
basicAuthorization:
userName: sdc
password: changeme
numOfRetries: 3
currentArtifactInstallationTimeout: 120
BE-janusgraph.properties
# JanusGraph storage backend
storage.backend=cassandra
# JanusGraph storage hostname
storage.hostname=<%= @CASSANDRA_IP %>
# JanusGraph storage port
storage.port=9042
# JanusGraph storage username
storage.username=<%= @CASSANDRA_USR %>
# JanusGraph storage password
storage.password=<%= @CASSANDRA_PWD %>
# JanusGraph storage connection timeout
storage.connection-timeout=10000
# JanusGraph cassandra keyspace name
storage.cassandra.keyspace=sdctitan
# Is JanusGraph cassandra ssl is enabled
storage.cassandra.ssl.enabled=false
# JanusGraph cassandra ssl truststore file location
storage.cassandra.ssl.truststore.location=/var/lib/jetty/config/.truststore
# JanusGraph cassandra ssl truststore file password
storage.cassandra.ssl.truststore.password=changeme
# Should JanusGraph use cache
cache.db-cache = false
# How long in milliseconds should the cache keep entries before flushing them
cache.db-cache-clean-wait = 20
# Default expiration time in milliseconds for entries in the cache
cache.db-cache-time = 180000
# Size of JanusGraph database cache
cache.db-cache-size = 0.5
# JanusGraph cassandra read consistency level
storage.cassandra.read-consistency-level=LOCAL_QUORUM
# JanusGraph cassandra write consistency level
storage.cassandra.write-consistency-level=LOCAL_QUORUM
# JanusGraph cassandra replication strategy class name
storage.cassandra.replication-strategy-class=org.apache.cassandra.locator.NetworkTopologyStrategy
# JanusGraph cassandra replication startegy options
storage.cassandra.replication-strategy-options=<%= @DC_NAME %>,<%= @rep_factor %>
# JanusGraph cassandra local data center name
storage.cassandra.astyanax.local-datacenter=<%= @DC_NAME %>
# Number of times the system attempts to acquire a lock before giving up and throwing an exception
storage.lock.retries=5
# Number of milliseconds the system waits for a lock application to be acknowledged by the storage backend
storage.lock.wait-time=500
Onboarding configuration
BE-onboarding-configuration.yaml
notifications:
# Backend onboarding notifications polling interval in milliseconds
pollingIntervalMsec: 2000
# Backend onboarding notifications selection size
selectionSize: 100
# Backend onboarding notifications backend hostname
beHost: <%= @catalog_ip %>
# Backend onboarding notifications backend http port
beHttpPort: <%= @catalog_port %>
# Casandra configuration
cassandraConfig:
cassandraHosts: [<%= @cassandra_ip %>]
localDataCenter: <%= @DC_NAME %>
reconnectTimeout : 30000
socketReadTimeout: <%= @socket_read_timeout %>
socketConnectTimeout: <%= @socket_connect_timeout %>
authenticate: true
username: <%= @cassandra_usr %>
password: <%= @cassandra_pwd %>
ssl: <%= @cassandra_ssl_enabled %>
truststorePath: /config/truststore
truststorePassword: <%= @cassandra_truststore_password %>
externaltesting-configuration.yaml
# configuration to make available to the front end of this feature
client:
enabled: true
# array of endpoints that SDC-BE should connect with for external testing
# id,label,enabled,url[,scenariofilter][,apikey]
endpoints:
- vtp:VTP,true,http://<hostname>[:<port>]/onapapi/vnfsdk-marketplace,c.*
- repository:Repository,false,http://<ovphostname>[:<ovpport>]
vnfrepo-configuration.yaml
# The port on which the vnfsdk is licensing
vnfRepoPort: <port>
# The ip where vnfdk is deployed
vnfRepoHost: <ip>
# The url used for querying the vnf sdk for available CSARs
getVnfUri: /onapapi/vnfsdk-marketplace/v1/PackageResource/csars
# The url used for downloading the the CSAR from vnf sdk
downloadVnfUri: /onapapi/vnfsdk-marketplace/v1/PackageResource/csars/%s/files
Frontend Configuration
Catalog configuration
FE-configuration.yaml
# Catalog frontend hostname
feFqdn: <%= @fe_host_ip %>
# Catalog backend hostname
beHost: <%= @be_host_ip %>
# Catalog backend http port
beHttpPort: <%= @catalog_port %>
# Catalog backend http context
beContext: /sdc2/rest/v1/catalog/upload/resources
# Catalog backend protocol
beProtocol: http
# Catalog backend ssl port
beSslPort: <%= @ssl_port %>
# Threadpool size for handling requests
threadpoolSize: 50
# Request processing timeout (seconds)
requestTimeout: 10
# Health check timeout in milliseconds
healthCheckSocketTimeoutInMs: 5000
# Health check inteval in seconds
healthCheckIntervalInSeconds: 5
onboarding:
# Onboarding protocol
protocol: http
# Onboarding frontend hostname
host: <%= @fe_host_ip %>
# Onboarding frontend port
port: 8181
# Onboarding frontend health check url
healthCheckUri: "/onboarding/v1.0/healthcheck"
# Request headers for identification of the user that made the request
identificationHeaderFields:
-
- &HTTP_IV_USER HTTP_IV_USER
- &iv-user iv-user
-
- &HTTP_CSP_ATTUID HTTP_CSP_ATTUID
- &csp-attuid csp-attuid
-
- &HTTP_CSP_WSTYPE HTTP_CSP_WSTYPE
- &csp-wstype csp-wstype
# Optional request headers
optionalHeaderFields:
-
- &HTTP_CSP_FIRSTNAME HTTP_CSP_FIRSTNAME
- &csp-firstname csp-firstname
-
- &HTTP_CSP_LASTNAME HTTP_CSP_LASTNAME
- &csp-lastname csp-lastname
-
- &HTTP_IV_REMOTE_ADDRESS HTTP_IV_REMOTE_ADDRESS
- &iv-remote-address iv-remote-address
-
- &HTTP_CSP_EMAIL HTTP_CSP_EMAIL
- &csp-email csp-email
-
- &USER_ID USER_ID
- &user-id user-id
# Frontend configuration version
version: 1.0
# Frontend configuration release date
released: 2012-11-30
# Connection parameters
connection:
url: jdbc:mysql://localhost:3306/db
poolSize: 17
# Protocols being used in SDC
protocols:
- http
- https
# Collect process statistics
systemMonitoring:
# Should monitoring be enabled
enabled: false
# In case of going through the FE server proxy the information to the BE
isProxy: true
# What is the interval of the statistics collection
probeIntervalInSeconds: 15
# Comma separated list of excluded URLs by the DataValidatorFilter
dataValidatorFilterExcludedUrls: "/healthCheck,/followed,/authorize"
FE-plugins-configuration.yaml
# definition of the plugins that exist in sdc
# we have a pre-defined list of plugins that are connected to the system.
# the plugins define where they are shown, to whom and on what elements
pluginsList:
# the DCAE-DS is the SDC monitoring design studio this entry defines there use as part of the service level context
- pluginId: DCAED
# this defines from which url to chek that they are available
pluginDiscoveryUrl: <%= @dcae_discovery_url %>
# this defines from wht URL will ther you be served.
pluginSourceUrl: <%= @dcae_source_url %>
#thsi defines the plugin state name used by the UI for sending messages.
pluginStateUrl: "dcaed"
# the display options for the plugin
pluginDisplayOptions:
# the plugin will be displayed in the context of a catalog item
context:
# what will the option tag in the ui will be called
displayName: "Monitoring"
# under what catalog item to display it
displayContext: ["SERVICE"]
# what user roles will have the option to access the plugin
displayRoles: ["DESIGNER"]
# DCAE-DS as a tab
- pluginId: DCAE-DS
pluginDiscoveryUrl: <%= @dcae_dt_discovery_url %>
pluginSourceUrl: <%= @dcae_dt_source_url %>
pluginStateUrl: "dcae-ds"
pluginDisplayOptions:
tab:
displayName: "DCAE-DS"
displayRoles: ["DESIGNER"]
#work flow plugin
- pluginId: WORKFLOW
pluginDiscoveryUrl: <%= @workflow_discovery_url %>
pluginSourceUrl: <%= @workflow_source_url %>
pluginStateUrl: "workflowDesigner"
pluginDisplayOptions:
tab:
displayName: "WORKFLOW"
displayRoles: ["DESIGNER", "TESTER"]
# how long we will wait for the plugin to respond before cutting it.
connectionTimeout: 1000
FE-workspace-configuration.yaml
# this file contains the different configurable UI workspace items that can be set according to resource and service type.
# the workspaceMenuConfiguration entry defines the workspace menus that are displayed according to type/subtype of the component in the workspace
# in addition, they can also be disabled for specific roles. the key is the resource type or service type and it will return the list of the menu
# items that will be displayed.
#
# each key had a list of menu items with the following data:
# - text: display text,
# - state: the state for the screen
# - action: action associated
# - index: optional - an integer that will be used to decide on the order of appearance
# following are 2 example
workspaceMenuConfiguration:
VFC:
- text: General
action: onMenuItemPressed
state: workspace.general
- text: Deployment Artifact
action: onMenuItemPressed
state: workspace.deployment_artifacts
- text: Information Artifact
action: onMenuItemPressed
state: workspace.information_artifacts
- text: TOSCA Artifacts
action: onMenuItemPressed
state: workspace.tosca_artifacts
- text: Properties
action: onMenuItemPressed
state: workspace.properties
- text: Attributes
action: onMenuItemPressed
state: workspace.attributes
- text: Req. & Capabilities
action: onMenuItemPressed
state: workspace.reqAndCap
- text: Activity Log
action: onMenuItemPressed
state: workspace.activity_log
SERVICE:
- text: General
action: onMenuItemPressed
state: workspace.general
- text: TOSCA Artifacts
action: onMenuItemPressed
state: workspace.tosca_artifacts
- text: Composition
action: onMenuItemPressed
state: workspace.composition.details
- text: Operation
action: onMenuItemPressed
state: workspace.interface_operation
- text: Activity Log
action: onMenuItemPressed
state: workspace.activity_log
- text: Management Workflow
action: onMenuItemPressed
state: workspace.management_workflow
- text: 'Network Call Flow '
action: onMenuItemPressed
state: workspace.network_call_flow
- text: Distribution
action: onMenuItemPressed
state: workspace.distribution
disabledRoles:
- ADMIN
- TESTER
- GOVERNOR
- DESIGNER
- text: Deployment
action: onMenuItemPressed
state: workspace.deployment
- text: Properties Assignment
action: onMenuItemPressed
state: workspace.properties_assignment
- text: Outputs
action: onMenuItemPressed
state: workspace.outputs_assignment
- text: Req. & Capabilities
action: onMenuItemPressed
state: workspace.reqAndCapEditable
Onboarding configuration
FE-onboarding-configuration.yaml
notifications:
# Frontend onboarding notifications polling interval in milliseconds
pollingIntervalMsec: 2000
# Frontend onboarding notifications selection size
selectionSize: 100
# Frontend onboarding notifications backend hostname
beHost: <%= @catalog_ip %>
# Frontend onboarding notifications backend http port
beHttpPort: <%= @catalog_port %>
Consumed APIs
VNF-SDK
SDC allows the user to choose packages from VNF-SDK and start the onboarding from there instead of manually uploading a package.
URL |
Description |
|---|---|
/onapapi/vnfsdk-marketplace/v1/PackageResource/csars |
get all available csar package data |
/onapapi/vnfsdk-marketplace/v1/PackageResource/csars/{id}/files |
Download CSAR by id |
SDC invokes Compliance Checks via VNF Test Platform (VTP)
URL |
Description |
|---|---|
/vtp/scenarios |
retrieve list available test scenarios |
/vtp/scenarios/{scenario}/testsuites |
retrieve a list of available test suites in a given scenario |
/vtp/scenarios/{scenario}/testcases |
retrieve a list of available test cases in a given scenario |
/vtp/scenarios/{scenario}/testsuites/{testSuiteName}/testcases/{testCaseName} |
retrieve test case parameters such as inputs and outputs in a given scenario and test suite |
/vtp/executions |
execute a list of test cases |
SDC Offered APIs
The list of APIs that SDC offers can be found from the following table:
API name |
OpenAPI JSON |
OpenAPI YAML |
|---|---|---|
SDCE-1 |
||
SDCE-2 & SDCE-5 |
||
SDCE-4 |
||
SDCE-6 |
||
SDCE-7 |
Models
SDC supports the onboarding and design of resources and services that adhere to one of a number of models. The following models are included in the default deployment:
SDC AID
The ONAP SDC data model supported widely by ONAP components.
ETSI SOL001 v2.5.1
The data model for NFV descriptors standardised by ETSI, version 2.5.1. Limited support exists in ONAP components, but some support is provided in SO SOL003 and SOL005 adapters and ETSI Catalog Manager.
AUTOMATION COMPOSITION
The data model for designing automation compositions, see CLAMP Metadata Automation Composition Management using TOSCA for further details on Automation Composition Management.
Further models can be added through the Supported APIs at deployment or runtime. Model inheritance is supported though it is expected that the names of the types be unique across the inheritance tree. Resources that are imported or designed to adhere to a particular model can only be used in a service that adheres to the same model.
Delivery
SDC Dockers Images
Overview
Name |
Content of the image |
On Startup |
sdc-cassandra-init |
Logic for creating the schemas for SDC catalog server |
Creates the schemas |
sdc-onboard-cassandra-init |
Logic for creating the schemas for SDC onboarding server |
Creates the schemas |
sdc-cassandra |
Cassandra server, this is optional as SDC uses shared ONAP Cassandra by default |
Starts Cassandra |
sdc-onboard-backend |
Onboarding Backend Jetty server |
Starts Jetty with the application. |
sdc-backend-all-plugins |
Backend Jetty server |
Starts Jetty with the application. |
sdc-backend-init |
Logic for importing the SDC Tosca normative types Logic for configuring external users for SDC external api’s |
Executes the rest calls for the catalog server |
sdc-frontend |
SDC Frontend Jetty server |
Starts Jetty with our application. |
sdc-workflow-init |
Logic for configuring Workflow Designer |
Executes configuration tasks of the WFD |
sdc-workflow-backend |
SDC Workflow Backend Jetty server |
Starts Jetty with our application. |
sdc-workflow-frontend |
SDC Workflow Frontend Jetty server |
Starts Jetty with our application. |
sdc-helm-validator |
SDC container for Helm package validation |
Starts server with our application. |
Deployment dependency map
Connectivity Matrix
Name |
API purpose |
protocol |
port number / range |
TCP / UDP |
sdc-cassandra |
SDC backend uses the two protocols to access Cassandra |
trift/async |
9042 / 9160 |
TCP |
sdc-onboard-backend |
Access the onboarding functionality |
http(s) |
8081 / 8445 |
TCP |
sdc-backend |
Access the catalog functionality |
http(s) |
8080 / 8443 |
TCP |
sdc-frontend |
Access SDC UI and proxy requests to SDC backend |
http(s) |
8181 / 9443 |
TCP |
Offered APIs
container / vm name |
address |
API purpose |
protocol |
port number |
TCP / UDP |
sdc-frontend |
/sdc1/feproxy/* |
Proxy for all REST calls from SDC UI |
HTTP(S) |
8181 / 8443 |
TCP |
sdc-backend |
/sdc2/* |
Internal APIs used by the UI. Request is passed through front end proxy |
HTTP(S) |
8080 / 8443 |
TCP |
/sdc/* |
External APIs offered to the different components for retrieving info from SDC catalog. |
HTTP(S) |
8080 / 8443 |
TCP |
|
sdc-onboarding-be |
/onboarding/api/* |
Internal APIs used by the UI |
HTTP(S) |
8080 / 8443 |
TCP |
Structure
Below is a diagram of the SDC project docker containers and the connections between them.
Human Interfaces
User Guides In ONAP Confluence
These are links to the SDC user guides found in ONAP User Guides:
Generic Designer Integration
Pluggable Architecture
SDC has been working on opening the application to allow an easy integration for any designer explanations. The current definitions and explanations are located here:
Onboarding Package Types
Supported Package Types
SDC supports the following packages types
Heat Package
ONAP Tosca CSAR Package
ETSI SOL004 Tosca CSAR Package
Basic Helm package support for CNF
For an extensive guide on how to perform onboarding, please refer to the ONAP User guide
Heat Package
The heat package is a zip archive with a .zip extension. The package contains heat template yaml file(s), corresponding environment file(s) and a MANIFEST.json file. The MANIFEST.json file describes the contents of the package.
There must be at least one heat template yaml file in the package whose name starts with base_. The other heat templates in the package can have any name. All environment files that are included in the package must have the same name as its corresponding yaml file with a .env file extension.
An example of a simple heat package structure is a zip archive containing the following 3 files
base_vFW.yaml (heat template)
base_vFW.env (corresponding environment file)
MANIFEST.json (describes files included in the package)
Examples of heat packages are the packages with .zip extension available in SDC git repo
ONAP Tosca CSAR Package
The ONAP Tosca CSAR package is a zip archive with a .csar extension. The structure of the CSAR package is as described in ONAP wiki page
ASD CSAR Package
The Application Service Descriptor CSAR package is a zip archive with a .csar extension. The structure of the CSAR and the descriptor it shall contain is described in Application Service Descriptor (ASD) and packaging Proposals for CNF.
ETSI SOL004 Tosca CSAR Package
The ETSI SOL004 Tosca CSAR Package is a zip archive with a .csar extension. The structure necessary for the supported CSAR package depends on the model selected in onboarding as detailed below.
SDC AID
If the package is onboarded using the SDC AID model, the structure of the supported CSAR package is as described in ETSI NFV-SOL 004v2.6.1 csar structure option 1 i.e. CSAR containing a TOSCA-Metadata directory.
The supported descriptor included in the package is aligned to ETSI NFV-SOL 001v2.5.1. The descriptor is partially mapped into the SDC AID model. There is also limited support for v2.7.1 and 3.3.1
ETSI SOL001 v2.5.1
If the package is onboarded using the ETSI SOL001 v2.5.1 model, the structure of the supported CSAR package is as described in ETSI NFV-SOL 004v2.5.1 csar structure option 1 i.e. CSAR containing a TOSCA-Metadata directory.
The supported descriptor included in the package is aligned to ETSI NFV-SOL 001v2.5.1. The TOSCA types defined in this version of the ETSI NFV-SOL 001 are used in the created VF (rather than the types defined in the SDC AID model).
Note in relation to model selection:
More than one model can be selected during onboarding. In the subsequent VSP import one model from the list of models selected at onboarding time must be selected.
For a package to be used in service design it must be imported with the same model as is selected during service creation.
Other Points to note when onboarding this package are:
During onboarding the ETSI NFV-SOL004 CSAR structure is transformed to the internal ONAP CSAR structure.
The original input CSAR is maintained and stored as the SDC artifact ETSI_PACKAGE in the xNF internal model. For existing legacy xNF, it can be stored as ONBOARDED_PACKAGE instead.
The non-mano artifacts are mapped to the corresponding SDC Artifact Type in the xNF internal model.
Basic Helm package support for CNF
The helm package support is new since Guilin release, helm chart packaged as tgz file can be onboarded and distributed. The support is limited for this first release.
Since Istanbul release there is also an additional helm chart validation step during package onboarding process. More information: SDC Helm Validator.
Package Types applicable to Resource Types
VF
The 3 package types described in Supported Package Types are all applicable for a VF i.e. a VF can be onboarded using any of these package types.
PNF
Only the ETSI SOL004 Tosca CSAR Package is applicable for a PNF.
Note
The PNF is not explicitly mentioned in ETSI NFV-SOL 004v2.6.1. There is a CR pending on the SOL004 specification describing the PNFD archive. SDC supports and expects the metadata section in the PNFD archive manifest to be aligned with this CR i.e. the entries contain the following names (keys)
pnfd_provider
pnfd_name
pnfd_release_date_time
pnfd_archive_version
An example of valid manifest file metadata section
metadata:
pnfd_name: MRF
pnfd_provider: SunShineCompany
pnfd_archive_version: 1.0
pnfd_release_date_time: 2017-01-01T10:00:00+03:00
When the PNF package in onboarded, the PNFD (descriptor) is transformed from ETSI NFV-SOL 001 model to the internal ONAP model.
How does SDC determine which package type is being onboarded
SDC onboarding processes each of the package types differently. SDC determines which package type is being onboarded, and hence which logic to use.
If the ETSI SOL001 v2.5.1 model is selected during onboarding, SDC will always treat the package as an ETSI SOL004 Tosca CSAR Package.
If the SDC AID model is selected during onboarding, SDC will determine the package type based on the following.
First SDC checks the extension of the package. If the package extension is .zip then the package is treated as a Heat package or Basic Helm package support for CNF.
To determine whether the package is of type Helm, SDC looks into the package content and tries to find Helm base files if not found it will treat it as Heat.
If it determines that this is a Helm package, SDC will add dummy Heat descriptor files.
If the package extension is .csar and the following is true
CSAR package contains TOSCA-Metadata directory
The TOSCA.meta file exists within the TOSCA-Metadata directory
The TOSCA.meta file contains the following key names in block_0
Entry-Definitions
ETSI-Entry-Manifest
ETSI-Entry-Change-Log
then the package is treated as an ETSI SOL004 Tosca CSAR Package. Otherwise the package is treated as an ONAP Tosca CSAR Package.
Package Security
SDC validates the authenticity and integrity of onboarding packages that are secured according to Security option 2 described in ETSI NFV-SOL 004v2.6.1.
In this option the whole package is signed and delivered as part of a zip file. SDC supports both zip file structures specified in the standard i.e
Zip file containing 3 artifacts
Package
Signing Certificate File
Signature File
Zip file containing 2 artifacts
Package
Signature File containing signing certificate
SDC supports the signature in Cryptographic Message Syntax (CMS) format.
Note
For SDC to validate the authenticity and integrity of the onboarding package, the root certificate of the trusted CA needs to be pre-installed in SDC before onboarding is started.
Externalized Testing & VTP Certifications Query Feature
The Certifications Query and VTP (External to SDC) testing feature was added to Dublin to allow SDC onboarding to reach outside of SDC for testing of VSPs being onboarded.
These tests include queries for existing certification results for prior versions of the VSP and testing of CSAR or HEAT metadata via tests in or downstream of VTP. The design includes the ability to configure (see configuration below) multiple endpoints that SDC onboarding reaches out to for external testing.
This diagram presents the architecture to be achieved in Dublin or a future release given the resources available.
New and Impacted Code
The new code for this feature follows the software design of the existing onboarding BE. New code is isolated into two new subprojects contained within openecomp-be within minimal hooks elsewhere.
New code:
Code that creates an HTTP endpoint exposed to the SDC-FE for this feature is contained in this package:
package: api/openecomp-sdc-rest-webapp/externaltesting-rest/externaltesting-rest-services
Code to hold data types for the VTP API and the implementation of the interface to VTP is contained in these packages:
Provide the API and serialisation classes for the REST API to VTP
package: lib/openecomp-sdc-externaltesting-lib/openecomp-sdc-externaltesting-api
Implementation of the interface to VTP and Registry that are available for the HTTP endpoint above.
package: lib/openecomp-sdc-externaltesting-lib/openecomp-sdc-externaltesting-impl
Updated Code:
To hook this new code into the web app, these additional changes were made:
api/openecomp-sdc-rest-webapp/pom.xml - Updated pom to include new module to build.
api/openecomp-sdc-rest-webapp/onboarding-rest-war/pom.xml - Update pom to include externaltesting libraries.
api/openecomp-sdc-rest-webapp/onboarding-rest-war - Update src/main/webapp/WEB-INF/beans-services.xml so that the external testing service beans are instantiated.
Configuration
Configuration was added to the onboarding backend yaml in order to know the URLs to reach VTP and external testing sources. The full configuration is documented in the configuration section of this manual. For details, see the BE-onboarding-configuration.yaml section. Here is an example of the yaml.
# External Testing Configuration
externalTestingConfig:
#array of endpoints that SDC-BE should connect with for external testing
endpoints:
// ID for endpoint
- id: vtp
// what format of post request does the endpoint accept for runs - json or multi-part form
postStyle: application/json
// is this enpoint enabled or disabled.
enabled: false
// base URL for the endpoint
url: http://ec2-34-237-35-152.compute-1.amazonaws.com:9090
// optional api key to pass in header to endpoint
apiKey: blahblahblah
- id: certifications repository
postStyle: application/json
url: http://ec2-34-237-35-152.compute-1.amazonaws.com:9090
enabled: true
apiKey: blahblahblah2
Installation
Installation Guides
In Guilin SDC is deployed through OOM based deployment. more information is available in the OOM and in the demo projects.
For local deployment SDC offers specific Maven Profiles (START-SDC and STOP-SDC)
Collection of commands used in deploying and monitoring sdc in OOM - SDC on OOM
SDC troubleshooting:
Kafka
- As of London release, SDC distribution can be configured to use Kakfa as an alternative to DMaaP message Router (MR) for publishing and consuming distribution events. This is controlled via the global SDC helm chart value:
- kafka:
useKafka: true/false
Logging
Where to Access Information
The logs for the application are available in the docker itself at /var/lib/jetty/logs/ In Heat deployment the dockers are mapped into /data/logs on the vm where the application is running. In OOM you can use the logging project to access the logs collected from the applications.
In the OOM deployment the log location in the docker is /var/log/onap
Server |
Location |
Type |
Description |
Rolling |
|---|---|---|---|---|
BE catalog and onboarding |
/data/logs/BE/2017_03_10.stderrout.log |
Jetty server log |
The log describes info regarding Jetty startup and execution |
the log rolls daily |
/data/logs/BE/SDC/SDC-BE/audit.log |
application audit |
An audit record is created for each operation in SDC |
rolls at 20 MB |
|
/data/logs/BE/SDC/SDC-BE/debug.log |
application logging |
We can enable higher logging on demand by editing the logback.xml inside the server docker. The file is located under: config/catalog-be/logback.xml. This log holds the debug and trace level output of the application. |
rolls at 20 MB |
|
/data/logs/BE/SDC/SDC-BE/error.log |
application logging |
This log holds the info and error level output of the application. |
rolls at 20 MB |
|
/data/logs/BE/SDC/SDC-BE/transaction.log |
application logging |
Not currently in use, will be used in future releases. |
rolls at 20 MB |
|
/data/logs/BE/SDC/SDC-BE/all.log |
application logging |
On demand, we can enable log aggregation into one file for easier debugging. This is done by editing the logback.xml inside the server docker. The file is located under: config/catalog-be/logback.xml. To allow this logger, set the value for this property to true This log holds all logging output of the application. |
rolls at 20 MB |
|
FE |
/data/logs/FE/2017_03_10.stderrout.log |
Jetty server log |
The log describes info regarding the Jetty startup and execution |
the log rolls daily |
/data/logs/FE/SDC/SDC-FE/debug.log |
application logging |
We can enable higher logging on demand by editing the logback.xml inside the server docker. The file is located,under: config/catalog-fe/logback.xml. This log holds the debug and trace level output of the application. |
rolls at 20 MB |
|
/data/logs/FE/SDC/SDC-FE/error.log |
application logging |
This log holds the Info and Error level output of the application. |
rolls at 20 MB |
|
/data/logs/FE/SDC/SDC-FE/all.log |
application logging |
On demand we can enable log aggregation into one file for easier debugging, by editing the logback.xml inside the server docker.The file is located under: config/catalog-fe/logback.xml. To allow this logger set this property to true This log holds all the logging output of the application. |
rolls |
Changing log level
SDC uses logback for logging. In order to change the level you will need to access the docker. Update the logback.xml inside the docker according to your need - the change does not require a restart of the docker.
To change the level for all logs, change the following value:
<root level="INFO">
To change the level for logs of some specific packages, change the following value:
<logger level="INFO" name="org.openecomp.sdc" />
To aggregate all the logs from all levels into a single log file called all.log change the following property to true:
<property name="enable-all-log" scope="context" value="false" />
Error / Warning Messages
Response Types
OK: {
code: 200,
message: "OK"
}
CREATED: {
code: 201,
message: "OK"
}
NO_CONTENT: {
code: 204,
message: "No Content"
}
——–POL4050—————————–
NOT_ALLOWED: {
code: 405,
message: "Error: Method not allowed.",
messageId: "POL4050"
}
——–POL5000—————————–
GENERAL_ERROR: {
code: 500,
message: "Error: Internal Server Error. Please try again later.",
messageId: "POL5000"
}
———POL5001—————————-
MISSING_X_ECOMP_INSTANCE_ID: {
code: 400 ,
message: "Error: Missing 'X-ECOMP-InstanceID' HTTP header.",
messageId: "POL5001"
}
———POL5002——————————
AUTH_REQUIRED: {
code: 401 ,
message: "Error: Authentication is required to use the API.",
messageId: "POL5002"
}
———POL5003——————————
AUTH_FAILED: {
code: 403 ,
message: "Error: Not authorized to use the API.",
messageId: "POL5003"
}
———POL5004——————————
MISSING\_USER\_ID: {
code: 400 ,
message: "Error: Missing 'USER\_ID' HTTP header.",
messageId: "POL5004"
}
———SVC4000—————————–
INVALID_CONTENT: {
code: 400,
message: "Error: Invalid content.",
messageId: "SVC4000"
}
———SVC4002—————————–
MISSING_INFORMATION: {
code: 403,
message: "Error: Missing information.",
messageId: "SVC4002"
}
———SVC4003——————————
%1 - User’s ID
USER_NOT_FOUND: {
code: 404,
message: "Error: User '%1' was not found.",
messageId: "SVC4003"
}
———SVC4004—————————–
%1 - User’s email address
INVALID_EMAIL_DDRESS: {
code: 400,
message: "Error: Invalid email address '%1'.",
messageId: "SVC4004"
}
———SVC4005——————————
%1 - role
INVALID_ROLE: {
code: 400,
message: "Error: Invalid role '%1'.",
messageId: "SVC4005"
}
———SVC4006——————————
%1 - User’s USER_ID
USER_ALREADY_EXIST: {
code: 409,
message: "Error: User with '%1' ID already exists.",
messageId: "SVC4006"
}
———SVC4007——————————
DELETE_USER_ADMIN_CONFLICT: {
code: 409,
message: "Error: An administrator can only be deleted by another administrator.",
messageId: "SVC4007"
}
———SVC4008—————————–
%1 - User’s USER_ID
INVALID_USER_ID: {
code: 400,
message: "Error: Invalid userId '%1'.",
messageId: "SVC4008"
}
———SVC4049——————————
%1 - Service/Resource
COMPONENT_MISSING_CONTACT: {
code: 400,
message: "Error: Invalid Content. Missing %1 contact.",
messageId: "SVC4049"
}
———SVC4050—————————–
%1 - Service/Resource/Additional parameter
%2 - Service/Resource/Label name
COMPONENT_NAME_ALREADY_EXIST: {
code: 409,
message: "Error: %1 with name '%2' already exists.",
messageId: "SVC4050"
}
———SVC4051——————————
%1 - Resource/Service
COMPONENT_MISSING_CATEGORY: {
code: 400,
message: "Error: Invalid Content. Missing %1 category.",
messageId: "SVC4051"
}
———SVC4052——————————
COMPONENT_MISSING_TAGS: {
code: 400,
message: "Error: Invalid Content. At least one tag has to be specified.",
messageId: "SVC4052"
}
———SVC4053——————————
%1 - service/resource
COMPONENT_MISSING_DESCRIPTION: {
code: 400,
message: "Error: Invalid Content. Missing %1 description.",
messageId: "SVC4053"
}
———SVC4054——————————
%1 - service/resource
COMPONENT_INVALID_CATEGORY: {
code: 400,
message: "Error: Invalid Content. Invalid %1 category.",
messageId: "SVC4054"
}
———SVC4055——————————
MISSING_VENDOR_NAME: {
code: 400,
message: "Error: Invalid Content. Missing vendor name.",
messageId: "SVC4055"
}
———SVC4056——————————
MISSING_VENDOR_RELEASE: {
code: 400,
message: "Error: Invalid Content. Missing vendor release.",
messageId: "SVC4056"
}
———SVC4057——————————
MISSING_DERIVED_FROM_TEMPLATE: {
code: 400,
message: "Error: Invalid Content. Missing derived from template specification.",
messageId: "SVC4057"
}
———SVC4058——————————
%1 - service/resource
COMPONENT_MISSING_ICON: {
code: 400,
message: "Error: Invalid Content. Missing %1 icon.",
messageId: "SVC4058"
}
———SVC4059——————————
%1 - service/resource
COMPONENT_INVALID_ICON: {
code: 400,
message: "Error: Invalid Content. Invalid %1 icon.",
messageId: "SVC4059"
}
———SVC4060——————————
PARENT_RESOURCE_NOT_FOUND: {
code: 400,
message: "Error: Invalid Content. Derived from resource template was not found.",
messageId: "SVC4060"
}
———SVC4061——————————
MULTIPLE_PARENT_RESOURCE_FOUND: {
code: 400,
message: "Error: Invalid Content. Multiple derived from resource template is not allowed.",
messageId: "SVC4061"
}
———SVC4062——————————
%1 - service/resource
MISSING_COMPONENT_NAME: {
code: 400,
message: "Error: Invalid Content. Missing %1 name.",
messageId: "SVC4062"
}
———SVC4063——————————
%1 - service/resource
RESOURCE_NOT_FOUND: {
code: 404,
message: "Error: Requested '%1' resource was not found.",
messageId: "SVC4063"
}
———SVC4064——————————
%1 - Service/Resource/Property
COMPONENT_INVALID_DESCRIPTION: {
code: 400,
message: "Error: Invalid Content. %1 description contains non-english characters.",
messageId: "SVC4064"
}
———SVC4065——————————
%1 - Service/Resource/Property
%2 - max resource/service name length
COMPONENT_DESCRIPTION_EXCEEDS_LIMIT: {
code: 400,
message: "Error: Invalid Content. %1 description exceeds limit of %2 characters.",
messageId: "SVC4065"
}
———SVC4066——————————
%1 - max length
COMPONENT_TAGS_EXCEED_LIMIT: {
code: 400,
message: "Error: Invalid Content. Tags overall length exceeds limit of %1 characters.",
messageId: "SVC4066"
}
———SVC4067——————————
%1 - max length
VENDOR_NAME_EXCEEDS_LIMIT: {
code: 400,
message: "Error: Invalid Content. Vendor name exceeds limit of %1 characters.",
messageId: "SVC4067"
}
———SVC4068——————————
%1 - max length
VENDOR_RELEASE_EXCEEDS_LIMIT: {
code: 400,
message: "Error: Invalid Content. Vendor release exceeds limit of %1 characters.",
messageId: "SVC4068"
}
———SVC4069——————————
%1 - Service/Resource/Product
COMPONENT_INVALID_CONTACT: {
code: 400,
message: "Error: Invalid Content. %1 Contact Id should be in format 'mnnnnnn' or 'aannna' or 'aannnn', where m=m ,a=a-zA-Z and n=0-9",
messageId: "SVC4069"
}
———SVC4070——————————
%1 - Service/Resource
INVALID_COMPONENT_NAME: {
code: 400,
message: 'Error: Invalid Content. %1 name is not allowed to contain characters like <>:"\/|?* and space characters other than regular space.',
messageId: "SVC4070"
}
———SVC4071——————————
INVALID_VENDOR_NAME: {
code: 400,
message: 'Error: Invalid Content. Vendor name is not allowed to contain characters like <>:"\/|?* and space characters other than regular space.',
messageId: "SVC4071"
}
———SVC4072——————————
INVALID_VENDOR_RELEASE: {
code: 400,
message: 'Error: Invalid Content. Vendor release is not allowed to contain characters like <>:"\/|?* and space characters other than regular space.',
messageId: "SVC4072"
}
———SVC4073——————————
%1 - Service/Resource
%2 - max resource/service name
COMPONENT_NAME_EXCEEDS_LIMIT: {
code: 400,
message: "Error: Invalid Content. %1 name exceeds limit of %2 characters.",
messageId: "SVC4073"
}
———SVC4080——————————
%1 - Service/Resource name
%2 - Service/Resource
%3 - First name of last modifier
%4 - Last name of last modifier
%5 - USER_ID of last modifier
COMPONENT_IN_CHECKOUT_STATE: {
code: 403,
message: "Error: Requested '%1' %2 is locked for modification by %3 %4(%5).",
messageId: "SVC4080"
}
———SVC4081—————————–
%1 - Service/Resource name
%2 - Service/Resource
%3 - First name of last modifier
%4 - Last name of last modifier
%5 - USER_ID of last modifier
COMPONENT_IN_CERT_IN_PROGRESS_STATE: {
code: 403,
message: "Error: Requested '%1' %2 is locked for certification by %3 %4(%5).",
messageId: "SVC4081"
}
———–SVC4082—————————
%1 - Service/Resource name
%2 - Service/Resource
%3 - First name of last modifier
%4 - Last name of last modifier
%5 - USER_ID of last modifier
COMPONENT_SENT_FOR_CERTIFICATION: {
code: 403,
message: "Error: Requested '%1' %2 is sent for certification by %3 %4(%5).",
messageId: "SVC4082"
}
———–SVC4083—————————
%1 - Service/Resource name
COMPONENT_VERSION_ALREADY_EXIST: {
code: 409,
message: "Error: Version of this %1 was already promoted.",
messageId: "SVC4083"
}
———–SVC4084—————————
%1 - Service/Resource/Product name
%2 - Service/Resource/Product
%3 - First name of last modifier
%4 - Last name of last modifier
%5 - USER_ID of last modifier
COMPONENT_ALREADY_CHECKED_IN: {
code: 409,
message: "Error: The current version of '%1' %2 was already checked-in by %3 %4(%5).",
messageId: "SVC4084"
}
———–SVC4085—————————
%1 - Service/Resource/Product name
%2 - Service/Resource/Product
%3 - First name of last modifier
%4 - Last name of last modifier
%5 - USER_ID of last modifier
COMPONENT_CHECKOUT_BY_ANOTHER_USER: {
code: 403,
message: "Error: %1 %2 has already been checked out by %3 %4(%5).",
messageId: "SVC4085"
}
———–SVC4086—————————
%1 - Service/Resource name
%2 - Service/Resource
COMPONENT_IN_USE: {
code: 403,
message: "Error: Requested '%1' %2 is in use by another user.",
messageId: "SVC4086"
}
———–SVC4087—————————
%1 - Component name
%2 - Service/Resource/Product
COMPONENT_HAS_NEWER_VERSION: {
code: 409,
message: "Error: Checking out of the requested version of the '%1' %2 is not allowed as a newer version exists.",
messageId: "SVC4087"
}
———–SVC4088—————————
%1 - Service/Resource name
%2 - Service/Resource
%3 - First name of last modifier
%4 - Last name of last modifier
%5 - USER_ID of last modifier
COMPONENT_ALREADY_CERTIFIED: {
code: 403,
message: "Error: Requested %1 %2 has already been certified by %3 %4(%5).",
messageId: "SVC4088"
}
———–SVC4089—————————
%1 - Service/Resource name
%2 - Service/Resource
COMPONENT_NOT_READY_FOR_CERTIFICATION: {
code: 403,
message: "Error: Requested '%1' %2 is not ready for certification.",
messageId: "SVC4089"
}
———–SVC4100—————————
%1 - property name
PROPERTY_NOT_FOUND: {
code: 404,
message: "Error: Requested '%1' property was not found.",
messageId: "SVC4100"
}
———–SVC4101—————————
%1 - property name
PROPERTY_ALREADY_EXIST: {
code: 409,
message: "Error: Property with '%1' name already exists.",
messageId: "SVC4101"
}
———–SVC4102—————————
%1 - capability type name
CAPABILITY_TYPE_ALREADY_EXIST: {
code: 409,
message: "Error: Capability Type with name '%1' already exists.",
messageId: "SVC4102"
}
———–SVC4114—————————
AUTH_FAILED_INVALIDE_HEADER: {
code: 400,
message: "Error: Invalid Authorization header.",
messageId: "SVC4114"
}
———–SVC4115—————————
%1 - capability type name
MISSING_CAPABILITY_TYPE: {
code: 400,
message: "Error: Invalid Content. Missing Capability Type '%1'.",
messageId: "SVC4115"
}
———–SVC4116—————————
RESOURCE_INSTANCE_BAD_REQUEST: {
code: 400,
message: "Error: Invalid Content.",
messageId: "SVC4116"
}
———–SVC4117—————————
%1 - resource instance name
%2 - resource instance name
%3 - requirement name
RESOURCE_INSTANCE_MATCH_NOT_FOUND: {
code: 404,
message: "Error: Match not found between resource instance '%1' and resource instance '%2' for requirement '%3'.",
messageId: "SVC4117"
}
———–SVC4118—————————
%1 - resource instance name
%2 - resource instance name
%3 - requirement name
RESOURCE_INSTANCE_ALREADY_EXIST: {
code: 409,
message: "Error: Resource instances '%1' and '%2' are already associated with requirement '%3'.",
messageId: "SVC4118"
}
———–SVC4119—————————
%1 - resource instance name
%2 - resource instance name
%3 - requirement name
RESOURCE_INSTANCE_RELATION_NOT_FOUND: {
code: 404,
message: "Error: No relation found between resource instances '%1' and '%2' for requirement '%3'.",
messageId: "SVC4119"
}
———–SVC4120—————————
%1 - User’s USER_ID
USER_INACTIVE: {
code: 404,
message: "Error: User %1 was not found.",
messageId: "SVC4120"
}
———–SVC4121—————————
%1 - User’s USER_ID
USER_HAS_ACTIVE_ELEMENTS: {
code: 403,
message: "Error: User with %1 ID can not be deleted since it has active elements(resources/services/artifacts).",
messageId: "SVC4121"
}
———–SVC4122—————————
%1 - artifact type
ARTIFACT_TYPE_NOT_SUPPORTED: {
code: 400,
message: "Error: Invalid artifact type '%1'.",
messageId: "SVC4122"
}
———–SVC4123—————————
ARTIFACT_LOGICAL_NAME_CANNOT_BE_CHANGED: {
code: 400,
message: "Error: Artifact logical name cannot be changed.",
messageId: "SVC4123"
}
———–SVC4124—————————
MISSING_ARTIFACT_TYPE: {
code: 400,
message: "Error: Missing artifact type.",
messageId: "SVC4124"
}
———–SVC4125—————————
%1 - artifact name
ARTIFACT_EXIST: {
code: 400,
message: "Error: Artifact '%1' already exists.",
messageId: "SVC4125"
}
———SVC4126——————————
%1 - Resource/Service/Product/…
%2 - field (tag, vendor name…)
INVALID_FIELD_FORMAT: {
code: 400,
message: "Error: Invalid %1 %2 format.",
messageId: "SVC4126"
}
———–SVC4127—————————
ARTIFACT_INVALID_MD5: {
code: 400,
message: "Error: Invalid artifact checksum.",
messageId: "SVC4127"
}
———–SVC4128—————————
MISSING_ARTIFACT_NAME: {
code: 400,
message: "Error: Invalid content. Missing artifact name.",
messageId: "SVC4128"
}
———–SVC4129—————————
MISSING_PROJECT_CODE: {
code: 400,
message: "Error: Invalid Content. Missing PROJECT_CODE number.",
messageId: "SVC4129"
}
———–SVC4130—————————
INVALID_PROJECT_CODE: {
code: 400,
message: "Error: Invalid Content. PROJECT_CODE must be from 3 up to 50 characters.",
messageId: "SVC4130"
}
———–SVC4131—————————
%1-resource/service
%2-artifact/artifacts
%3-semicolon separated list of artifact
COMPONENT_MISSING_MANDATORY_ARTIFACTS: {
code: 403,
message: "Error: Missing mandatory informational %1 %2: [%3].",
messageId: "SVC4131"
}
———–SVC4132—————————
%1 - lifecycle type name
LIFECYCLE_TYPE_ALREADY_EXIST: {
code: 409,
message: "Error: Lifecycle Type with name '%1' already exists.",
messageId: "SVC4132"
}
———–SVC4133—————————
%1 - service version
%2 - service name
SERVICE_NOT_AVAILABLE_FOR_DISTRIBUTION: {
code: 403,
message: "Error: Version %1 of '%2' service is not available for distribution.",
messageId: "SVC4133"
}
———–SVC4134—————————
MISSING_LIFECYCLE_TYPE: {
code: 400,
message: "Error: Invalid Content. Missing interface life-cycle type.",
messageId: "SVC4134"
}
———SVC4135——————————
SERVICE_CATEGORY_CANNOT_BE_CHANGED: {
code: 400,
message: "Error: Service category cannot be changed once the service is certified.",
messageId: "SVC4135"
}
———SVC4136——————————
%1 - distribution environment name
DISTRIBUTION_ENVIRONMENT_NOT_AVAILABLE: {
code: 500,
message: "Error: Requested distribution environment '%1' is not available.",
messageId: "SVC4136"
}
———SVC4137——————————
%1 - distribution environment name
DISTRIBUTION_ENVIRONMENT_NOT_FOUND: {
code: 400,
message: "Error: Requested distribution environment '%1' was not found.",
messageId: "SVC4137"
}
———SVC4138——————————
DISTRIBUTION_ENVIRONMENT_INVALID: {
code: 400,
message: "Error: Invalid distribution environment.",
messageId: "SVC4138"
}
———SVC4139——————————
%1 - service name
DISTRIBUTION_ARTIFACT_NOT_FOUND: {
code: 409,
message: "Error: Service '%1' cannot be distributed due to missing deployment artifacts.",
messageId: "SVC4139"
}
———SVC4200——————————
%1 - Service/Resource
%2 - max icon name length
COMPONENT_ICON_EXCEEDS_LIMIT: {
code: 400,
message: "Error: Invalid Content. %1 icon name exceeds limit of %2 characters.",
messageId: "SVC4200"
}
———SVC4300——————————
RESTRICTED_ACCESS: {
code: 403,
message: "Error: Restricted access.",
messageId: "SVC4300"
}
———SVC4301——————————
RESTRICTED_OPERATION: {
code: 409,
message: "Error: Restricted operation.",
messageId: "SVC4301"
}
———SVC4500——————————
MISSING_BODY: {
code: 400 ,
message: "Error: Missing request body.",
messageId: "SVC4500"
}
———SVC4501——————————
MISSING_PUBLIC_KEY: {
code: 400 ,
message: "Error: Invalid Content. Missing mandatory parameter 'apiPublicKey'." ,
messageId: "SVC4501"
}
———SVC4502——————————
DISTRIBUTION_ENV_DOES_NOT_EXIST: {
code: 400 ,
message: "Error: Invalid Body : Missing mandatory parameter 'distrEnvName'." ,
messageId: "SVC4502"
}
———–SVC4503—————————
%1 - service name
SERVICE_NOT_FOUND: {
code: 404,
message: "Error: Requested '%1' service was not found.",
messageId: "SVC4503"
}
———SVC4504——————————
%1 - Service/Resource
%2 - service/resource version
COMPONENT_VERSION_NOT_FOUND: {
code: 404,
message: "Error: %1 version %2 was not found.",
messageId: "SVC4504"
}
———–SVC4505—————————
%1 - artifact name
ARTIFACT_NOT_FOUND: {
code: 404,
message: "Error: Artifact '%1' was not found.",
messageId: "SVC4505"
}
———SVC4506——————————
MISSING_ENV_NAME: {
code: 400 ,
message: "Error: Invalid Content. Missing mandatory parameter 'distrEnvName'.",
messageId: "SVC4506"
}
———SVC4507——————————
COMPONENT_INVALID_TAGS_NO_COMP_NAME: {
code: 400,
message: "Error: Invalid Content. One of the tags should be the component name.",
messageId: "SVC4507"
}
———SVC4508——————————
SERVICE_NAME_CANNOT_BE_CHANGED: {
code: 400,
message: "Error: Service name cannot be changed once the service is certified.",
messageId: "SVC4508"
}
———SVC4509——————————
SERVICE_ICON_CANNOT_BE_CHANGED: {
code: 400,
message: "Error: Icon cannot be changed once the service is certified.",
messageId: "SVC4509"
}
———SVC4510——————————
%1 - icon name max length
SERVICE_ICON_EXCEEDS_LIMIT: {
code: 400,
message: "Error: Invalid Content. Icon name exceeds limit of %1 characters.",
messageId: "SVC4510"
}
———SVC4511——————————
DISTRIBUTION_REQUESTED_NOT_FOUND: {
code: 404,
message: "Error: Requested distribution was not found.",
messageId: "SVC4511"
}
———SVC4512——————————
%1 - Distribution ID
DISTRIBUTION_REQUESTED_FAILED: {
code: 403,
message: "Error: Requested distribution '%1' failed.",
messageId: "SVC4512"
}
———SVC4513——————————
RESOURCE_CATEGORY_CANNOT_BE_CHANGED: {
code: 400,
message: "Error: Resource category cannot be changed once the resource is certified.",
messageId: "SVC4513"
}
———SVC4514——————————
RESOURCE_NAME_CANNOT_BE_CHANGED: {
code: 400,
message: "Error: Resource name cannot be changed once the resource is certified.",
messageId: "SVC4514"
}
———SVC4515——————————
RESOURCE_ICON_CANNOT_BE_CHANGED: {
code: 400,
message: "Error: Icon cannot be changed once the resource is certified.",
messageId: "SVC4515"
}
———SVC4516——————————
RESOURCE_VENDOR_NAME_CANNOT_BE_CHANGED: {
code: 400,
message: "Error: Vendor name cannot be changed once the resource is certified.",
messageId: "SVC4516"
}
———SVC4517——————————
RESOURCE_DERIVED_FROM_CANNOT_BE_CHANGED: {
code: 400,
message: "Error: Derived from resource template cannot be changed once the resource is certified.",
messageId: "SVC4517"
}
———SVC4518——————————
%1 - max length
COMPONENT_SINGLE_TAG_EXCEED_LIMIT: {
code: 400,
message: "Error: Invalid Content. Single tag exceeds limit of %1 characters.",
messageId: "SVC4518"
}
———SVC4519——————————
INVALID_DEFAULT_VALUE: {
code: 400,
message: "Error: mismatch in data-type occurred for property %1. data type is %2 and default value found is %3.",
messageId: "SVC4519"
}
———SVC4520——————————
%1 - serviceresource
ADDITIONAL_INFORMATION_MAX_NUMBER_REACHED: {
code: 409,
message: "Error: Maximal number of additional %1 parameters was reached.",
messageId: "SVC4520"
}
———SVC4521——————————
ADDITIONAL_INFORMATION_EMPTY_STRING_NOT_ALLOWED: {
code: 400,
message: "Error: Invalid Content. The Additional information label and value cannot be empty.",
messageId: "SVC4521"
}
———SVC4522——————————
%1 - label/value
%2 - Maximal length of %1
ADDITIONAL_INFORMATION_EXCEEDS_LIMIT: {
code: 400,
message: "Error: Invalid Content. Additional information %1 exceeds limit of %2 characters.",
messageId: "SVC4522"
}
———SVC4523——————————
ADDITIONAL_INFORMATION_KEY_NOT_ALLOWED_CHARACTERS: {
code: 400,
message: 'Error: Invalid Content. Additional information label is not allowed to contain characters like <>:"\/|?* and space characters other than regular space.',
messageId: "SVC4523"
}
———SVC4524——————————
ADDITIONAL_INFORMATION_NOT_FOUND: {
code: 409,
message: "Error: Requested additional information was not found.",
messageId: "SVC4524"
}
———SVC4525——————————
ADDITIONAL_INFORMATION_VALUE_NOT_ALLOWED_CHARACTERS: {
code: 400,
message: 'Error: Invalid Content. Additional information contains non-English characters.',
messageId: "SVC4525"
}
———SVC4526——————————
RESOURCE_INSTANCE_NOT_FOUND: {
code: 404,
message: "Error: Requested '%1' resource instance was not found.",
messageId: "SVC4526"
}
———SVC4527——————————
ASDC_VERSION_NOT_FOUND: {
code: 500,
message: 'Error: ASDC version cannot be displayed.',
messageId: "SVC4527"
}
———SVC4528——————————
%1-artifact url/artifact label/artifact description/VNF Service Indicator
MISSING_DATA: {
code: 400,
message: "Error: Invalid content. Missing %1.",
messageId: "SVC4528"
}
———SVC4529——————————
%1-artifact url/artifact label/artifact description/artifact name
%2 - Maximal length of %1
EXCEEDS_LIMIT: {
code: 400,
message: "Error: Invalid Content. %1 exceeds limit of %2 characters.",
messageId: "SVC4529"
}
———SVC4530——————————
ARTIFACT_INVALID_TIMEOUT: {
code: 400,
message: "Error: Invalid Content. Artifact Timeout should be set to valid positive non-zero number of minutes.",
messageId: "SVC4530"
}
———SVC4531——————————
SERVICE_IS_VNF_CANNOT_BE_CHANGED: {
code: 400,
message: "Error: VNF Indicator cannot be updated for certified service.",
messageId: "SVC4531"
}
———SVC4532——————————
RESOURCE_INSTANCE_NOT_FOUND_ON_SERVICE: {
code: 404,
message: "Error: Requested '%1' resource instance was not found on the service '%2.",
messageId: "SVC4532"
}
———SVC4533——————————
%1 - artifact name(“HEAT”/”HEAT_ENV”/”MURANO_PKG”/”YANG_XML”)
WRONG_ARTIFACT_FILE_EXTENSION: {
code: 400,
message: "Error: Invalid file extension for %1 artifact type.",
messageId: "SVC4533"
}
———SVC4534——————————
%1 - “HEAT”/”HEAT_ENV”
INVALID_YAML: {
code: 400,
message: "Error: Uploaded YAML file for %1 artifact is invalid.",
messageId: "SVC4534"
}
———SVC4535——————————
%1 - “HEAT”
INVALID_DEPLOYMENT_ARTIFACT_HEAT: {
code: 400,
message: "Error: Invalid %1 artifact.",
messageId: "SVC4535"
}
———SVC4536——————————
%1 - Resource/Service
%2 - Resource/Service name
%3 - “HEAT”/”HEAT_ENV”/”MURANO_PKG”
%4 - “HEAT”/”HEAT_ENV”/”MURANO_PKG
DEPLOYMENT_ARTIFACT_OF_TYPE_ALREADY_EXISTS: {
code: 400,
message: "Error: %1 '%2' already has a deployment artifact of %3 type .Please delete or update an existing %4 artifact.",
messageId: "SVC4536"
}
———SVC4537——————————
MISSING_HEAT: {
code: 400,
message: "Error: Missing HEAT artifact. HEAT_ENV artifact cannot be uploaded without corresponding HEAT template.",
messageId: "SVC4537"
}
———SVC4538——————————
MISMATCH_HEAT_VS_HEAT_ENV: {
code: 400,
message: "Error: Invalid artifact content. Parameter's set in HEAT_ENV '%1' artifact doesn't match the parameters in HEAT '%2' artifact.",
messageId: "SVC4538"
}
———SVC4539——————————
INVALID_RESOURCE_PAYLOAD: {
code: 400,
message: "Error: Invalid resource payload.",
messageId: "SVC4539"
}
———SVC4540——————————
INVALID_TOSCA_FILE_EXTENSION: {
code: 400,
message: "Error: Invalid file extension for TOSCA template.",
messageId: "SVC4540"
}
———SVC4541——————————
INVALID_YAML_FILE: {
code: 400,
message: "Error: Invalid YAML file.",
messageId: "SVC4541"
}
———SVC4542——————————
INVALID_TOSCA_TEMPLATE: {
code: 400,
message: "Error: Invalid TOSCA template.",
messageId: "SVC4542"
}
———SVC4543——————————
NOT_RESOURCE_TOSCA_TEMPLATE: {
code: 400,
message: "Error: Imported Service TOSCA template.",
messageId: "SVC4543"
}
———SVC4544——————————
NOT_SINGLE_RESOURCE: {
code: 400,
message: "Error: Imported TOSCA template should contain one resource definition.",
messageId: "SVC4544"
}
———SVC4545——————————
INVALID_RESOURCE_NAMESPACE: {
code: 400,
message: "Error: Invalid resource namespace.",
messageId: "SVC4545"
}
———SVC4546——————————
RESOURCE_ALREADY_EXISTS: {
code: 400,
message: "Error: Imported resource already exists in ASDC Catalog.",
messageId: "SVC4546"
}
———SVC4549——————————
INVALID_RESOURCE_CHECKSUM: {
code: 400,
message: "Error: Invalid resource checksum.",
messageId: "SVC4549"
}
———SVC4550——————————
%1 - Consumer salt
INVALID_LENGTH: {
code: 400,
message: "Error: Invalid %1 length.",
messageId: "SVC4550"
}
———SVC4551——————————
%1 - ECOMP User name
ECOMP_USER_NOT_FOUND: {
code: 404,
message: "Error: ECOMP User '%1' was not found.",
messageId: "SVC4551"
}
———SVC4552——————————
CONSUMER_ALREADY_EXISTS: {
code: 409,
message: "Error: ECOMP User already exists.",
messageId: "SVC4552"
}
———SVC4553—————————–
%1 - Consumer name / Consumer password/ Consumer salt
INVALID_CONTENT_PARAM: {
code: 400,
message: "Error: %1 is invalid.",
messageId: "SVC4553"
}
———SVC4554——————————
%1 - “Resource”/”Service”
COMPONENT_ARTIFACT_NOT_FOUND: {
code: 404,
message: "Error: Requested artifact doesn't belong to specified %1.",
messageId: "SVC4554"
}
———SVC4554——————————
%1 - “Service name”
SERVICE_DEPLOYMENT_ARTIFACT_NOT_FOUND: {
code: 403,
message: "Error: Requested '%1' service is not ready for certification. Service has to have at least one deployment artifact.",
messageId: "SVC4554"
}
———SVC4555——————————
%1 - Resource/Service/Product
%2 - Category”
COMPONENT_ELEMENT_INVALID_NAME_LENGTH: {
code: 400,
message: "Error: Invalid %1 %2 name length.",
messageId: "SVC4555"
}
———SVC4556——————————
%1 - Resource/Service/Product %2 - Category”
COMPONENT_ELEMENT_INVALID_NAME_FORMAT: {
code: 400,
message: "Error: Invalid %1 %2 name format.",
messageId: "SVC4556"
}
———SVC4557——————————
%1 - Resource/Service/Product
%2 - Category name”
COMPONENT_CATEGORY_ALREADY_EXISTS: {
code: 409,
message: "Error: %1 category name '%2' already exists.",
messageId: "SVC4557"
}
———SVC4558——————————
%1 - service/VF
%2 - Resource name
VALIDATED_RESOURCE_NOT_FOUND: {
code: 403,
message: "Error: Submit for Testing is not permitted as your '%1' includes non-validated '%2' resource.",
messageId: "SVC4558"
}
———SVC4559——————————
%1 - Service/VF
%2 - Resource name
FOUND_ALREADY_VALIDATED_RESOURCE: {
code: 403,
message: "Error: Submit for Testing is not permitted as your '%1' includes non-validated '%2' resource. Please use already available validated resource version.",
messageId: "SVC4559"
}
———SVC4560——————————
%1 - Service/VF
%2 - Resource name
FOUND_LIST_VALIDATED_RESOURCES: {
code: 403,
message: "Error: Submit for Testing is not permitted as your '%1' includes non-validated '%2' resource. Please use one of available validated resource versions.",
messageId: "SVC4560"
}
———SVC4561——————————
%1 - Resource/Product
%2 - Category
%3 - Category name
COMPONENT_CATEGORY_NOT_FOUND: {
code: 404,
message: "Error: Requested %1 %2 '%3' was not found.",
messageId: "SVC4561"
}
———SVC4562——————————
%1 - Resource/Product
%2 - Sub-Category name
%3 - Category name
COMPONENT_SUB_CATEGORY_EXISTS_FOR_CATEGORY: {
code: 409,
message: "Error: %1 sub-category '%2' already exists under '%3' category.",
messageId: "SVC4562"
}
———SVC4563——————————
%1 - Product
%2 - Grouping name
%3 - Sub-Category name
COMPONENT_GROUPING_EXISTS_FOR_SUB_CATEGORY: {
code: 409,
message: "Error: %1 grouping '%2' already exists under '%3' sub-category.",
messageId: "SVC4563"
}
———SVC4564——————————
%1 - Product name
PRODUCT_NOT_FOUND: {
code: 404,
message: "Error: Requested '%1' product was not found.",
messageId: "SVC4564"
}
———SVC4565——————————
%1 - “HEAT”
%2 - Parameter type (“string” , “boolean” , “number”)
%3 - Parameter name
INVALID_HEAT_PARAMETER_VALUE: {
code: 400,
message: "Error: Invalid %1 artifact. Invalid %2 value set for '%3' parameter.",
messageId: "SVC4565"
}
———SVC4566——————————
%1 - “HEAT”
%2 - Parameter type (“string” , “boolean” , “number”)
INVALID_HEAT_PARAMETER_TYPE: {
code: 400,
message: "Error: Invalid %1 artifact. Unsupported '%2' parameter type.",
messageId: "SVC4566"
}
———SVC4567——————————
%1 - “YANG_XML”
INVALID_XML: {
code: 400,
message: "Error: Uploaded XML file for %1 artifact is invalid.",
messageId: "SVC4567"
}
———SVC4567——————————
%1 - User Name and UserId
%2 - Checked-out/In-certification
CANNOT_DELETE_USER_WITH_ACTIVE_ELEMENTS: {
code: 409,
message: "Error: User cannot be deleted. User '%1' has %2 projects.",
messageId: "SVC4567"
}
———SVC4568——————————
%1 - User Name and UserId
%2 - Checked-out/In-certification
CANNOT_UPDATE_USER_WITH_ACTIVE_ELEMENTS: {
code: 409,
message: "Error: Role cannot be changed. User '%1' has %2 projects.",
messageId: "SVC4568"
}
———SVC4570——————————
UPDATE_USER_ADMIN_CONFLICT: {
code: 409,
message: "Error: An administrator is not allowed to change his/her role.",
messageId: "SVC4570"
}
———SVC4571——————————
SERVICE_CANNOT_CONTAIN_SUBCATEGORY: {
code: 400,
message: "Error: Sub category cannot be defined for service",
messageId: "SVC4571"
}
———SVC4572——————————
%1 - Resource/Service
COMPONENT_TOO_MUCH_CATEGORIES: {
code: 400,
message: "Error: %1 must have only 1 category",
messageId: "SVC4572"
}
———SVC4574——————————
RESOURCE_TOO_MUCH_SUBCATEGORIES: {
code: 400,
message: "Error: Resource must have only 1 sub category",
messageId: "SVC4574"
}
———SVC4575——————————
COMPONENT_MISSING_SUBCATEGORY: {
code: 400,
message: "Error: Missing sub category",
messageId: "SVC4575"
}
———SVC4576——————————
%1 - Component type
UNSUPPORTED_ERROR: {
code: 400,
message: "Error : Requested component type %1 is unsupported.",
messageId: "SVC4576"
}
———SVC4577——————————
%1 - Resource type
RESOURCE_CANNOT_CONTAIN_RESOURCE_INSTANCES: {
code: 409,
message: "Error : Resource of type %1 cannot contain resource instances.",
messageId: "SVC4577"
}
———SVC4578——————————
%1 - Resource/Service
%2 - Resource/Service name
%3 - Artifact name
DEPLOYMENT_ARTIFACT_NAME_ALREADY_EXISTS: {
code: 400,
message: "Error: %1 '%2' already has a deployment artifact named '%3'.",
messageId: "SVC4578"
}
———SVC4579——————————
%1 - “Category/Sub-Category/Group”
%2 - Category/Sub-Category/Grouping name.
INVALID_GROUP_ASSOCIATION: {
code: 400,
message: "Error: Invalid group association. %1 '%2' was not found.",
messageId: "SVC4579"
}
———SVC4580——————————
EMPTY_PRODUCT_CONTACTS_LIST: {
code: 400,
message: "Error: Invalid content. At least one Product Contact has to be specified.",
messageId: "SVC4580"
}
———SVC4581——————————
%1 - UserId
INVALID_PRODUCT_CONTACT: {
code: 400,
message: "Error: Invalid content. User '%1' cannot be set as Product Contact.",
messageId: "SVC4581"
}
———SVC4582——————————
%1 - Product
%2 - Abbreviated/Full”
MISSING_ONE_OF_COMPONENT_NAMES: {
code: 400,
message: "Error: Invalid content. Missing %1 %2 name.",
messageId: "SVC4582"
}
———SVC4583——————————
%1 - Icon
%2 - Resource/Service/Product
COMPONENT_PARAMETER_CANNOT_BE_CHANGED: {
code: 400,
message: "Error: %1 cannot be changed once the %2 is certified.",
messageId: "SVC4583"
}
———SVC4584——————————
%1 - Service/VF name
%2 - Service/VF
%3 - Resource instance origin type
%4 - Resource instance name
%5 - Requirement/Capability
%6 - Requirement/Capability name
%7 - Fulfilled” (for req)/Consumed (forcap)
REQ_CAP_NOT_SATISFIED_BEFORE_CERTIFICATION: {
code: 403,
message: "Error: Requested '%1' %2 is not ready for certification. %3'%4' has to have %5 '%6' %7.",
messageId: "SVC4584"
}
———SVC4585——————————
INVALID\_OCCURRENCES: {
code: 400,
message: "Error: Invalid occurrences format.",
messageId: "SVC4585"
}
———SVC4586——————————
INVALID_SERVICE_API_URL:{
code: 400,
message: 'Error: Invalid Service API URL. Please check whether your URL has a valid domain extension
'and does not contain the following characters - #?&@%+;,=$<>~^\`[]{}\|"\*!',
messageId: "SVC4586"
}
———SVC4587——————————
%1 - Data type name
DATA_TYPE_ALREADY_EXIST: {
code: 409,
message: 'Error: Data type %1 already exists.',
messageId: "SVC4587"
}
———SVC4588——————————
%1 - Data type name
DATA_TYPE_NOR_PROPERTIES_NEITHER_DERIVED_FROM: {
code: 400,
message: 'Error: Invalid Data type %1. Data type must have either a valid derived from declaration or at least one valid property',
messageId: "SVC4588"
}
———SVC4589——————————
%1 - Data type name
DATA_TYPE_PROPERTIES_CANNOT_BE_EMPTY: {
code: 400,
message: "Error: Invalid Data type %1. 'properties' parameter cannot be empty if provided.",
messageId: "SVC4589"
}
———SVC4590——————————
%1 - Property type name
%2 - Property name
INVALID_PROPERTY_TYPE: {
code: 400,
message: "Error: Invalid Property type %1 in property %2.",
messageId: "SVC4590"
}
———SVC4591——————————
%1 - Property inner type
%2 - Property name
INVALID_PROPERTY_INNER_TYPE: {
code: 400,
message: "Error: Invalid property inner type %1, in property %2",
messageId: "SVC4591"
}
———SVC4592——————————
%1 - Component instance name
%2 - Resource instance/Service instance
COMPONENT_INSTANCE_NOT_FOUND: {
code: 404,
message: "Error: Requested '%1' %2 was not found.",
messageId: "SVC4592"
}
———SVC4593——————————
%1 - Component instance name
%2 - Resource instance/Service instance
%3 - Resource/Service/Product
%4 - Container name
COMPONENT_INSTANCE_NOT_FOUND_ON_CONTAINER: {
code: 404,
message: "Error: Requested '%1' %2 was not found on the %3 '%4'.",
messageId: "SVC4593"
}
———SVC4594——————————
%1 - Requirement/Capability
%2 - Requirement name
IMPORT_DUPLICATE_REQ_CAP_NAME: {
code: 400,
message: "Error: Imported TOSCA template contains more than one %1 named '%2'.",
messageId: "SVC4594"
}
———SVC4595——————————
%1 - Requirement/Capability
%2 - Requirement name
%3 - Parent containing the requirement
IMPORT_REQ_CAP_NAME_EXISTS_IN_DERIVED: {
code: 400,
message: "Error: Imported TOSCA template contains %1 '%2' that is already defined by derived template %3.",
messageId: "SVC4595"
}
———SVC4596——————————
%1 - Data type name
DATA_TYPE_DERIVED_IS_MISSING: {
code: 400,
message: "Error: Invalid Content. The ancestor data type %1 cannot be found in the system.",
messageId: "SVC4596"
}
———SVC4597——————————
%1 - Data type name
%2 - Property names
DATA_TYPE_PROPERTY_ALREADY_DEFINED_IN_ANCESTOR: {
code: 400,
message: "Error: Invalid Content. The data type %1 contains properties named %2 which are already defined in one of its ancestors.",
messageId: "SVC4597"
}
———SVC4598——————————
%1 - Data type name
DATA_TYPE_DUPLICATE_PROPERTY: {
code: 400,
message: "Error: Invalid Content. The data type %1 contains duplicate property.",
messageId: "SVC4598"
}
———SVC4599——————————
%1 - Data type name
%2 - Property names
DATA_TYPE_PROEPRTY_CANNOT_HAVE_SAME_TYPE_OF_DATA_TYPE: {
code: 400,
message: "Error: Invalid Content. The data type %1 contains properties %2 which their type is this data type.",
messageId: "SVC4599"
}
———SVC4600——————————
%1 - Data type name
DATA_TYPE_CANNOT_HAVE_PROPERTIES: {
code: 400,
message: "Error: Invalid Content. The data type %1 cannot have properties since it is of type scalar",
messageId: "SVC4600"
}
———SVC4601——————————
NOT_TOPOLOGY_TOSCA_TEMPLATE: {
code: 400,
message: "Error: TOSCA yaml file %1 cannot be modeled to VF as it does not contain 'topology_template.",
messageId: "SVC4601"
}
———SVC4602——————————–
%1 - YAML file name
%2 - Node_Template label
%3 - Node_Template type
INVALID_NODE_TEMPLATE: {
code: 400,
message: "Error: TOSCA yaml file '%1' contains node_template '%2' of type '%3' that does not represent existing VFC/CP/VL",
messageId: "SVC4602"
}
———SVC4603——————————
%1 - Component type
%2 - Component name
%3 - State
ILLEGAL_COMPONENT_STATE: {
code: 403,
message: "Error: Component instance of %1 can not be created because the component '%2' is in an illegal state %3.",
messageId: "SVC4603"
}
———SVC4604——————————
%1 - CSAR file name
CSAR_INVALID: {
code: 400,
message: "Error: TOSCA CSAR '%1' is invalid. 'TOSCA-Metadata/Tosca.meta' file must be provided.",
messageId: "SVC4604"
}
———SVC4605——————————
%1 - CSAR file name
CSAR_INVALID_FORMAT: {
code: 400,
message: "Error: TOSCA CSAR '%1' is invalid. Invalid 'TOSCA-Metadata/Tosca.meta' file format.",
messageId: "SVC4605"
}
———SVC4606——————————
%1 - Property name
%2 - Property type
%3 - Property innerType
%4 - Default value
INVALID_COMPLEX_DEFAULT_VALUE: {
code: 400,
message: "Error: Invalid default value of property %1. Data type is %2 with inner type %3 and default value found is %4.",
messageId: "SVC4606"
}
———SVC4607——————————
%1 - csar file name
CSAR_NOT_FOUND: {
code: 400,
message: "Error: TOSCA CSAR '%1' is not found.",
messageId: "SVC4607"
}
———SVC4608——————————
%1 - Artifact name
%2 - Component type
%3 - Actual component type
MISMATCH_BETWEEN_ARTIFACT_TYPE_AND_COMPONENT_TYPE: {
code: 400,
message: "Error: Artifact %1 is only compatible with component of type %2, but component type is %3.",
messageId: "SVC4608"
}
———SVC4609——————————
%1 - INVALID_JSON
INVALID_JSON: {
code: 400,
message: "Error: Uploaded JSON file for %1 artifact is invalid.",
messageId: "SVC4609"
}
———SVC4610——————————
%1 - CSAR file name
%2 - Missing file name
YAML_NOT_FOUND_IN_CSAR: {
code: 400,
message: "Error - TOSCA CSAR %1 is invalid. TOSCA-Metadata/Tosca.meta refers to file %2 that is not provided.",
messageId: "SVC4610"
}
———SVC4611——————————
%1 - Group name
GROUP_MEMBER_EMPTY: {
code: 400,
message: "Error: Invalid Content. Group %1 member list was provided but does not have values",
messageId: "SVC4611"
}
———SVC4612——————————
%1 - Group name
GROUP_TYPE_ALREADY_EXIST: {
code: 409,
message: 'Error: Group type %1 already exists.',
messageId: "SVC4612"
}
———SVC4613——————————
%1 - Group name
%2 - VF name(component name)
%3 - Actual component type [VF]
GROUP_ALREADY_EXIST: {
code: 409,
message: "Error: Group with name '%1' already exists in %2 %3.",
messageId: "SVC4613"
}
———SVC4614——————————
%1 - Group type
GROUP_TYPE_IS_INVALID: {
code: 400,
message: "Error: Invalid content. Group type %1 does not exist",
messageId: "SVC4614"
}
———SVC4615——————————
%1 - group name
GROUP_MISSING_GROUP_TYPE: {
code: 400,
message: "Error: Invalid Content. Missing Group Type for group '%1'",
messageId: "SVC4615"
}
———SVC4616——————————
%1 - Member name
%2 - Group name
%3 - VF name
%4 - Component type [VF ]
GROUP_INVALID_COMPONENT_INSTANCE: {
code: 400,
message: "Error: Member '%1' listed in group '%2' is not part of '%3' %4.",
messageId: "SVC4616"
}
———SVC4617——————————
%1 - Member name
%2 - Group name
%3 - Group type
GROUP_INVALID_TOSCA_NAME_OF_COMPONENT_INSTANCE: {
code: 400,
message: "Error: member %1 listed in group %2 is not part of allowed members of group type %3.",
messageId: "SVC4617"
}
———SVC4618——————————
%1 - Missing file name
%2 - CSAR file name
ARTIFACT_NOT_FOUND_IN_CSAR: {
code: 400,
message: "Error: artifact %1 is defined in CSAR %2 manifest but is not provided",
messageId: "SVC4618"
}
———SVC4619——————————
%1 - Artifact name
%2 - Artifact type
%3 - Existing artifact type
ARTIFACT_ALREADY_EXIST_IN_DIFFERENT_TYPE_IN_CSAR: {
code: 400,
message: "Error: artifact %1 in type %2 already exists in type %3.",
messageId: "SVC4619"
}
———SVC4620——————————
FAILED_RETRIVE_ARTIFACTS_TYPES: {
code: 400,
message: "Error: Failed to retrieve list of supported artifact types.",
messageId: "SVC4620"
}
———SVC4621——————————
%1 - Artifact name
%2 - Master
ARTIFACT_ALRADY_EXIST_IN_MASTER_IN_CSAR: {
code: 400,
message: "Error: artifact %1 already exists in master %2 .",
messageId: "SVC4621"
}
———SVC4622——————————
%1 - Artifact name
%2 - Artifact type
%3 - Master name
%4 - Master type
ARTIFACT_NOT_VALID_IN_MASTER: {
code: 400,
message: "Error: artifact %1 in type %2 can not be exists under master %3 in type %4.",
messageId: "SVC4622"
}
———SVC4623——————————
%1 - Artifact name
%2 - Artifact type
%3 - Env name
%4 - Existing env
ARTIFACT_NOT_VALID_ENV: {
code: 400,
message: "Error: Artifact %1 in type %2 with env %3 already exists with another env %4",
messageId: "SVC4623"
}
———SVC4624——————————
%1 - Groups names
%2 - VF name
%3 - Component type [VF ]
GROUP_IS_MISSING: {
code: 400,
message: "Error: Invalid Content. The groups '%1' cannot be found under %2 %3.",
messageId: "SVC4624"
}
———SVC4625——————————
%1 - Groups name
GROUP_ARTIFACT_ALREADY_ASSOCIATED: {
code: 400,
message: "Error: Invalid Content. Artifact already associated to group '%1'.",
messageId: "SVC4625"
}
———SVC4626——————————
%1 - Groups name
GROUP_ARTIFACT_ALREADY_DISSOCIATED: {
code: 400,
message: "Error: Invalid Content. Artifact already dissociated from group '%1'.",
messageId: "SVC4626"
}
———SVC4627——————————
%1 - Property name
%2 - Group name
%3 - Group type name
GROUP_PROPERTY_NOT_FOUND: {
code: 400,
message: "Error: property %1 listed in group %2 is not exist in group type %3.",
messageId: "SVC4627"
}
———SVC4628——————————
%1 - CSAR UUID
%2 - VF name
VSP_ALREADY_EXISTS: {
code: 400,
message: "Error: The VSP with UUID %1 was already imported for VF %2. Please select another or update the existing VF.",
messageId: "SVC4628"
}
———SVC4629——————————
%1 - VF name
MISSING_CSAR_UUID: {
code: 400,
message: "Error: The Csar UUID or payload name is missing for VF %1.",
messageId: "SVC4629"
}
———SVC4630——————————
%1 - VF name
%2 - New CSAR UUID
%3 - Old CSAR UUID
RESOURCE_LINKED_TO_DIFFERENT_VSP: {
code: 400,
message: "Error: Resource %1 cannot be updated using CsarUUID %2 since the resource is linked to a different VSP with csarUUID %3.",
messageId: "SVC4630"
}
———SVC4631——————————
%1 - Policy name
POLICY_TYPE_ALREADY_EXIST: {
code: 409,
message: "Error: Policy type %1 already exists.",
messageId: "SVC4631"
}
———SVC4632——————————
%1 - Target name
%2 - Policy type name
TARGETS_NON_VALID: {
code: 400,
message: "Error: target %1 listed in policy type %2 is not a group or resource.",
messageId: "SVC4632"
}
———SVC4633——————————
%1 - Policy name
TARGETS_EMPTY: {
code: 400,
message: "Error: Invalid Content. Policy %1 target list was provided but does not have values",
messageId: "SVC4633"
}
———SVC4634——————————
DATA_TYPE_CANNOT_BE_EMPTY: {
code: 500,
message: "Error: Data types are empty. Please import the data types.",
messageId: "SVC4634"
}
———SVC4635——————————
%1 - CSAR UUID
RESOURCE_FROM_CSAR_NOT_FOUND: {
code: 400,
message: "Error: resource from csar uuid %1 not found",
messageId: "SVC4635"
}
———SVC4636——————————
%1 - Data type name
DATA_TYPE_CANNOT_BE_UPDATED_BAD_REQUEST: {
code: 400,
message: 'Error: Data type %1 cannot be upgraded. The new data type does not contain old properties or the type of one of the properties has been changed.',
messageId: "SVC4636"
}
———–SVC4637—————————
%1 - Attribute name
ATTRIBUTE_NOT_FOUND: {
code: 404,
message: "Error: Requested '%1' attribute was not found.",
messageId: "SVC4637"
}
———–SVC4638—————————
%1 - Attribute name
ATTRIBUTE_ALREADY_EXIST: {
code: 409,
message: "Error: Attribute with '%1' name already exists.",
messageId: "SVC4638"
}
———–SVC4639—————————
%1 - Property name
PROPERTY_NAME_ALREADY_EXISTS: {
code: 409,
message: "Error: Property with '%1' name and different type already exists.",
messageId: "SVC4639"
}
———–SVC4640—————————
%1 - Property name
INVALID_PROPERTY: {
code: 409,
message: "Error: Invalid property received.",
messageId: "SVC4640"
}
———SVC4641—————————–
%1 - Invalid filter
%2 - Valid filters
INVALID_FILTER_KEY: {
code: 400,
message: "Error: The filter %1 is not applicable. Please use one of the following filters: %2",
messageId: "SVC4641"
}
———SVC4642—————————–
%1 - Asset type
%2 - Filter
NO_ASSETS_FOUND: {
code: 404,
message: "No %1 were found to match criteria %2",
messageId: "SVC4642"
}
———SVC4643——————————
%1 - Resource”/”Product
%2 - Sub-Category name
%3 - Category name
COMPONENT_SUB_CATEGORY_NOT_FOUND_FOR_CATEGORY: {
code: 404,
message: "Error: %1 sub-category '%2' not found under category '%3'.",
messageId: "SVC4643"
}
———SVC4644——————————
%1 - Format
CORRUPTED_FORMAT: {
code: 400,
message: "Error: %1 format is corrupted.",
messageId: "SVC4644"
}
———SVC4645——————————
%1 - GroupType
INVALID_VF_MODULE_TYPE: {
code: 400,
message: "Error: Invalid group type '%1' (should be VfModule).",
messageId: "SVC4645"
}
———SVC4646——————————
%1 - GroupName
INVALID_VF_MODULE_NAME: {
code: 400,
message: "Error: Invalid Content. VF Module name '%1' contains invalid characters",
messageId: "SVC4646"
}
———SVC4647——————————
%1 - ModifiedName
INVALID_VF_MODULE_NAME_MODIFICATION: {
code: 400,
message: "Error: Invalid VF Module name modification, can not modify '%1'",
messageId: "SVC4647"
}
———SVC4648——————————
%1 - InputId
%2 - ComponentId
INPUT_IS_NOT_CHILD_OF_COMPONENT: {
code: 400,
message: "Error: Input id: '%1' is not child of component id: '%2'",
messageId: "SVC4648"
}
———SVC4649——————————
%1 - GroupName
GROUP_HAS_CYCLIC_DEPENDENCY: {
code: 400,
message: "Error: The group '%1' has cyclic dependency",
messageId: "SVC4649"
}
———SVC4650——————————
%1 - Component Type
%2 - Service Name
%3 - Error description
AAI_ARTIFACT_GENERATION_FAILED: {
code: 500,
message: "Error: %1 %2 automatic generation of artifacts failed. Description: %3",
messageId: "SVC4650"
}
———SVC4651——————————
PARENT_RESOURCE_DOES_NOT_EXTEND: {
code: 400,
message: "Error: Once resource is certified, derived_from can be changed only to a sibling",
messageId: "SVC4651"
}
———SVC4652——————————
%1 - Resource/Service
COMPONENT_INVALID_SUBCATEGORY: {
code: 400,
message: "Error: Invalid Content. Invalid %1 sub category.",
messageId: "SVC4652"
}
———SVC4653——————————
%1 - Group instance uniqueId
%2 - Service uniqueId
GROUP_INSTANCE_NOT_FOUND_ON_COMPONENT_INSTANCE: {
code: 404,
message: "Error: Requested group instance %1 was not found on component %2.",
messageId: "SVC4653"
}
———SVC4654——————————
%1 - Group property name
%2 - Valid min limit value
%3 - Valid max limit value
INVALID_GROUP_MIN_MAX_INSTANCES_PROPERTY_VALUE: {
code: 400,
message: "Error: Value of %1 must be not higher than %2, and not lower than %3.",
messageId: "SVC4654"
}
———SVC4655——————————
%1 - Group property name
%2 - Valid min limit value
%3 - Valid max limit value
INVALID_GROUP_INITIAL_COUNT_PROPERTY_VALUE: {
code: 400,
message: "Error: Value of %1 must be between %2 and %3.",
messageId: "SVC4655"
}
———SVC4656——————————
%1 - Group property name
%2 - Lower/Higher
%3 - Valid max/min value
INVALID_GROUP_PROPERTY_VALUE_LOWER_HIGHER: {
code: 400,
message: "Error: Value of %1 must be %2 or equals to %3.",
messageId: "SVC4656"
}
———SVC4657——————————
%1 - CertificationRequest/StartTesting
RESOURCE_VFCMT_LIFECYCLE_STATE_NOT_VALID: {
code: 400,
message: "Error - Lifecycle state %1 is not valid for resource of type VFCMT",
messageId: "SVC4657"
}
———SVC4658——————————
%1 – Asset type [Service/Resource]
%2 – Main asset uuid
%3 – Not found asset type [Service/Resource]
%4 – Not found asset name
ASSET_NOT_FOUND_DURING_CSAR_CREATION: {
code: 400,
message: "Error: CSAR packaging failed for %1 %2. %3 %4 was not found",
messageId: "SVC4658"
}
———SVC4659——————————
%1 – asset type [Service/Resource]
%2 – Main asset UUID
%3 – Artifact name
%4 – Artifact uuid
ARTIFACT_PAYLOAD_NOT_FOUND_DURING_CSAR_CREATION: {
code: 400,
message: "Error: CSAR packaging failed for %1 %2. Artifact %3 [%4] was not found",
messageId: "SVC4659"
}
———SVC4660——————————
%1 - Asset type
%2 - Matching generic node type name
GENERIC_TYPE_NOT_FOUND: {
code: 404,
message: "Creation of %1 failed. Generic type %2 was not found",
messageId: "SVC4660"
}
———SVC4661——————————
%1 - Asset type
%2 - Matching generic node type name
TOSCA_SCHEMA_FILES_NOT_FOUND: {
code: 400,
message: "Error: CSAR packaging failed. TOSCA schema files for SDC-Version: %1 and Conformance-Level %2 were not found",
messageId: "SVC4661"
}
———SVC4662——————————
%1 - File name
%2 - Parser error
TOSCA_PARSE_ERROR: {
code: 400,
message: "Error: Invalid TOSCA template in file %1. %2",
messageId: "SVC4662"
}
———SVC4663——————————
%1 - Max length
RESOURCE_VENDOR_MODEL_NUMBER_EXCEEDS_LIMIT: {
code: 400,
message: "Error: Invalid Content. Resource vendor model number exceeds limit of %1 characters.",
messageId: "SVC4663"
}
———SVC4664——————————
INVALID_RESOURCE_VENDOR_MODEL_NUMBER: {
code: 400,
message: 'Error: Invalid Content. Resource vendor model number is not allowed to contain characters like <>:"\/|?* and space characters other than regular space.',
messageId: "SVC4664"
}
———SVC4665——————————
%1 - Max length
SERVICE_TYPE_EXCEEDS_LIMIT: {
code: 400,
message: "Error: Invalid Content. Service type exceeds limit of %1 characters.",
messageId: "SVC4665"
}
———SVC4666——————————
INVALID_SERVICE_TYPE: {
code: 400,
message: 'Error: Invalid Content. Service type is not allowed to contain characters like <>:"\/|?* and space characters other than regular space.',
messageId: "SVC4666"
}
———SVC4667——————————
%1 - Max length
SERVICE_ROLE_EXCEEDS_LIMIT: {
code: 400,
message: "Error: Invalid Content. Service role exceeds limit of %1 characters.",
messageId: "SVC4667"
}
———SVC4668——————————
INVALID_SERVICE_ROLE: {
code: 400,
message: 'Error: Invalid Content. Service role is not allowed to contain characters like <>:"\/|?* and space characters other than regular space.',
messageId: "SVC4668"
}
———SVC4669—————————–
INVALID_RESOURCE_TYPE: {
code: 400,
message: "Error: Invalid resource type.",
messageId: "SVC4669"
}
———SVC4670——————————
ARTIFACT_NAME_INVALID: {
code: 400,
message: "Error: Artifact name is invalid.",
messageId: "SVC4670"
}
———SVC4671——————————
%1 - VSP name
%2 - VFC name
CFVC_LOOP_DETECTED: {
code: 400,
message: 'Error: VSP %1 cannot be imported. The VSP contains internal loop in VFC %2',
messageId: "SVC4671"
}
———SVC4672——————————
%1 - capability uniqueId
%2 - instance uniqueId
%3 - container uniqueId
CAPABILITY_OF_INSTANCE_NOT_FOUND_ON_CONTAINER: {
code: 404,
message: "Error: Requested capability %1 of instance %2 was not found on the container %3.",
messageId: "SVC4672"
}
———SVC4673——————————
%1 - requirement uniqueId
%2 - instance uniqueId
%3 - container uniqueId
REQUIREMENT_OF_INSTANCE_NOT_FOUND_ON_CONTAINER: {
code: 404,
message: "Error: Requested requirement %1 of instance %2 was not found on the container %3.",
messageId: "SVC4673"
}
———SVC4674—————————–
%1 - relation Id
%2 - container uniqueId
RELATION_NOT_FOUND: {
code: 404,
message: "Error: Requested relation %1 was not found on the container %2.",
messageId: "SVC4674"
}
———SVC4675——————————
INVALID_SERVICE_STATE: {
code: 409,
message: "Service state is invalid for this action",
messageId: "SVC4675"
}
———SVC4676——————————
INVALID_RESPONSE_FROM_PROXY: {
code: 502,
message: "Error: The server was acting as a gateway or proxy and received an invalid response from the upstream server",
messageId: "SVC4676"
}
———SVC4677——————————
API_RESOURCE_NOT_FOUND: {
code: 404,
message: "Error: Requested '%1' was not found.",
messageId: "SVC4677"
}
———SVC4678——————————
BAD_REQUEST_MISSING_RESOURCE: {
code: 400,
message: "Error: The required resource name/id is missing in the request",
messageId: "SVC4678"
}
———SVC4679——————————
%1 forwarding path name maximum length
FORWARDING_PATH_NAME_MAXIMUM_LENGTH: {
code: 400,
message: "Forwarding path name too long, , maximum allowed 200 characters : '%1'.",
messageId: "SVC4679"
}
———SVC4680——————————
%1 Forwarding path name already in use
FORWARDING_PATH_NAME_ALREADY_IN_USE: {
code: 400,
message: "Forwarding path name already in use : '%1'.",
messageId: "SVC4680"
}
———SVC4681——————————
%1 Forwarding path name empty
FORWARDING_PATH_NAME_EMPTY: {
code: 400,
message: "Forwarding Path Name can't be empty .",
messageId: "SVC4681"
}
———SVC4682——————————
%1 - resource uniqueId
%2 - resource component type
RESOURCE_CANNOT_CONTAIN_POLICIES: {
code: 400,
message: "Error: The resource %1 type of %2 cannot contain policies.",
messageId: "SVC4682"
}
———SVC4683——————————
%1 - policy uniqueId
%2 - component uniqueId
POLICY_NOT_FOUND_ON_CONTAINER: {
code: 404,
message: "Error: Requested policy %1 was not found on the container %2.",
messageId: "SVC4683"
}
———SVC4684——————————
%1 - policy name
INVALID_POLICY_NAME: {
code: 400,
message: "Error: Invalid policy name %1 received.",
messageId: "SVC4684"
}
———SVC4685——————————
%1 - policy name
POLICY_NAME_ALREADY_EXIST: {
code: 409,
message: "Error: The policy with the name %1 already exists.",
messageId: "SVC4685"
}
———SVC4686——————————
%1 - policy name
POLICY_TARGET_DOES_NOT_EXIST: {
code: 400,
message: "Error: The targets %1 are not valid, all targets have to be on the topologyTemplate.",
messageId: "SVC4686"
}
———SVC4687——————————
%1 - policy type
%2 - component type
EXCLUDED_POLICY_TYPE: {
code: 400,
message: "Error: The policy of the type %1 excluded to add to a component of the type %2.",
messageId: "SVC4687"
}
———SVC4688——————————
%1 - group type
%2 - component type
GROUP_TYPE_ILLEGAL_PER_COMPONENT: {
code: 400,
message: "Error: group type %1 not permitted in component of type %2",
messageId: "SVC4688"
}
———SVC4689——————————
%1 - group type
%2 - component type
POLICY_TARGET_TYPE_DOES_NOT_EXIST: {
code: 400,
message: "Error: The target types %1 are not valid.",
messageId: "SVC4689"
}
———SVC4690——————————
%1 forwarding path protocol maximum length
FORWARDING_PATH_PROTOCOL_MAXIMUM_LENGTH: {
code: 400,
message: "Forwarding path protocol too long, , maximum allowed 200 characters : '%1'.",
messageId: "SVC4690"
}
———SVC4691——————————
%1 forwarding path destination port maximum length
FORWARDING_PATH_DESTINATION_PORT_MAXIMUM_LENGTH: {
code: 400,
message: "Forwarding path destination port too long, , maximum allowed 200 characters : '%1'.",
messageId: "SVC4691"
}
———POL4692——————————
MISSING_OLD_COMPONENT_INSTANCE: {
code: 400 ,
message: "Error: Missing 'componentInstanceId' HTTP param.",
messageId: "POL4692"
}
———POL4693——————————
MISSING_NEW_COMPONENT_INSTANCE: {
code: 400 ,
message: "Error: Missing 'newComponentInstanceId' HTTP param.",
messageId: "POL4693"
}
———SVC4694——————————
%1 External Reference Value
EXT_REF_NOT_FOUND: {
code: 404,
message: "Error: External Reference '%1' was not found.",
messageId: "SVC4694"
}
———SVC4695—————————–
%1 - Interface operation type
INTERFACE_OPERATION_TYPE_ALREADY_IN_USE: {
code: 400,
message: "Error: Interface Operation type %1 already in use",
messageId: "SVC4695"
}
———SVC4696—————————–
%1 - workflow operation type
INTERFACE_OPERATION_TYPE_INVALID: {
code: 400,
message: "Error: Interface Operation type %1 is Invalid, Operation type should not contain
special character, space, numbers and should not be greater than 200 characters ",
messageId: "SVC4696"
}
———SVC4697—————————–
INTERFACE_OPERATION_TYPE_MANDATORY: {
code: 404,
message: "Error: Interface Operation type is mandatory, Operation type can't be empty",
messageId: "SVC4697"
}
———SVC4698—————————–
%1 - workflow operation description
INTERFACE_OPERATION_DESCRIPTION_MAX_LENGTH: {
code: 400,
message: "Error: Interface Operation description %1 is invalid, maximum 200 characters allowed",
messageId: "SVC4698"
}
———SVC4699—————————–
INTERFACE_OPERATION_INPUT_NAME_ALREADY_IN_USE: {
code: 400,
message: "Error: Interface Operation input parameter names %1 already in use",
messageId: "SVC4699"
}
———SVC4700—————————–
INTERFACE_OPERATION_OUTPUT_NAME_INVALID: {
code: 400,
message: "Error: Interface Operation output parameters invalid, should be unique and mandatory",
messageId: "SVC4700"
}
———SVC4701—————————–
%1 - resource Id
INTERFACE_OPERATION_NOT_FOUND: {
code: 404,
message: "Error: Interface operations not found in the resource %1",
messageId: "SVC4701"
}
———SVC46702—————————–
INTERFACE_OPERATION_NOT_DELETED: {
code: 404,
message: "Error: Failed to delete interface operation.",
messageId: "SVC4702"
}
———SVC4703—————————–
%1 – asset type [service / resource ]
%2 – main asset uuid
ERROR_DURING_CSAR_CREATION: {
code: 404,
message: "Error: CSAR packaging failed for %1 %2.",
messageId: "SVC4702"
}
———SVC46703—————————–
INTERFACE_OPERATION_INPUT_NAME_MANDATORY: {
code: 404,
message: "Error: Interface operation input parameter name should not be empty",
messageId: "SVC46703"
}
———SVC4750—————————–
MISSING_TENANT_NAME: {
code: 400,
message: "Error: Missing Tenant name.",
messageId: "SVC4750"
}
Release Notes
Version: 1.13.6
- Release Date:
2023-10-27
SDC SDKs Versions
sdc-distribution-client (Kafka)
- Version:
2.1.1
sdc-distribution-client (DMaap MR - deprecated)
- Version:
1.4.5
sdc-tosca
- Version:
1.9.0
Release Purpose
SDC Montreal release
Epics
N/A
Stories
SDC-4637 - TLS sdc-be: Truststore & keystore handling for cassandra
SDC-4642 - Add support for TLS to sdc-FE
SDC-4639 - Add support for TLS to sdc-BE
SDC-4654 - Increase unit test coverage
Bug Fixes
SDC-4674 - Exception thrown from sdc-FE healthcheck when using http
SDC-4650 - JUEL expression syntax prevents download
SDC-4667 - service role and service function metadata not imported
SDC-4668 - Schema being added to non list properties
SDC-4665 - service role metadata cleared after service creation
SDC-4661 - Unable to import service template with interface
SDC-4664 - Null value in model node type properties after VFC update
SDC-4663 - Null value in model node type properties
SDC-4662 - Certifying mechanism changing structure of csar
SDC-4607 - No properties found when trying to add a node filter to a component instance
SDC-4649 - Declare Output button disabled after saving a default value
Tasks
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.13.5
- Release Date:
2023-10-09
SDC SDKs Versions
sdc-distribution-client (Kafka)
- Version:
2.0.1
sdc-distribution-client (DMaap MR - deprecated)
- Version:
1.4.5
sdc-tosca
- Version:
1.8.0
Release Purpose
SDC Montreal early release
Epics
N/A
Stories
SDC-4647 - Import service with milestones on instance operations
SDC-4635 - Persisting of map entry property values
SDC-4646 - Import VFC with operation milestones
SDC-4636 - Hide or disable milestone filters
SDC-4621 - TLS support in sdc-BE (partially)
SDC-4620 - Support setting interfaces on instances
SDC-4601 - UI Support for operation milestones
SDC-4590 - Backend support for operation milestone filters
SDC-4582 - Backend support for operation milestones with activity inputs
SDC-4577 - Backend support for operation milestones with activities
SDC-4622 - Provide the ability to add user defined values to Service Role / Function metadata
Bug Fixes
SDC-4648 - Error updating milestone in operation on instance in service
SDC-4628 - Fail to import service with node filter using ‘in_range’
SDC-4645 - Missing Substitution Map Node after update Service
SDC-4644 - Issues found when trying to create activities in interface operations
SDC-4643 - missing properties after service import
SDC-4638 - CSAR contains duplicate syntax
SDC-4634 - NPE on service import
SDC-4633 - Substitution Node not updated during import
SDC-4632 - Outputs - default values / template attributes
SDC-4627 - Order of TOSCA.meta field is hardcoded
SDC-4626 - TOSCA-Meta-File-Version and CSAR-Version accept only following format X.Y
SDC-4629 - Unable to import service with missing ‘ecompGeneratedNaming’ in metadata
SDC-4630 - Output names are changed after import
SDC-4625 - Changing VFC version wipes List type property values
Tasks
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.13.4
- Release Date:
2023-09-15
SDC SDKs Versions
sdc-distribution-client (Kafka)
- Version:
2.0.1
sdc-distribution-client (DMaap MR - deprecated)
- Version:
1.4.5
sdc-tosca
- Version:
1.8.0
Release Purpose
SDC Montreal early release
Epics
N/A
Stories
SDC-4623 - Improved error handling on service import
SDC-4605 - UI support for service update via csar import
SDC-4578 - Create plugin point for csar generation
SDC-4579 - Add endpoint to update service by csar import
SDC-4616 - User specified output name
SDC-4614 - Support for the policy type definition upgrade
SDC-4602 - UI support for interface definitions on VFC instances
SDC-4613 - Import service with outputs mapped to implicit attributes
SDC-4612 - Implicit attributes in get_attribute list
SDC-4611 - Declare implicit attributes as outputs
SDC-4604 - UI support for service update via tosca template import
SDC-4588 - Import VFC with timeout in interface operation implementation
SDC-4593 - System should validate JSON anywhere it is added as property value
SDC-4575 - UI support for timeout in interface operation implementation
SDC-4576 - Add endpoint to update service by tosca template import
SDC-4580 - Add backend support for timeout in interface operation implementation
SDC-4562 - Support TOSCA functions of complex list/map entries in composition view
Bug Fixes
SDC-4618 - Error when importing output with common name in attributes and properties
SDC-4615 - Stringbuilder UI - two scroll bars overlapping
SDC-4603 - Unable to add metadata on inputs
SDC-4610 - Surrounding a value in quotes can lead to failure to parse the value
SDC-4606 - Error thrown from Jsoup validation for < char
SDC-4599 - Fail to import service with CP
SDC-4554 - Custom tosca functions with valid_values and in_range operators not showing properly
SDC-4586 - Changing VFC version on template wipes previously assigned property values based on get_input
SDC-4598 - ‘Tosca Function’ get_input in Properties Assignment error
SDC-4591 - Import use case fails when interfaces in template do not exist in system
SDC-4596 - Fail to import service with get_property of map-of-string
SDC-4587 - Creation date only works with requests that return 1 service (API)
SDC-4583 - Unable to drag a VFC on to composition if an existing VFC instance has the same name
SDC-4581 - Unable to save yaml content in node filter
SDC-4556 - Upgrading a node does not bring its new capabilities
Tasks
SDC-4608 - Improve handling ‘empty’/null string in Service fields
SDC-4563 - Remove unused code
SDC-4600 - Replace deprecated maven parameters
SDC-4597 - Add DOT to property’s name permitted chars
SDC-4592 - Update error message for missing sub mapping properties
SDC-4589 - Introduce error message for missing properties during the service import
SDC-4585 - Rollback nested transaction
SDC-4569 - Replace/remove outdated dependencies
SDC-4565 - Improvement to maven multi-thread run
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.13.3
- Release Date:
2023-07-14
SDC SDKs Versions
sdc-distribution-client (Kafka)
- Version:
2.0.1
sdc-distribution-client (DMaap MR - deprecated)
- Version:
1.4.5
sdc-tosca
- Version:
1.8.0
Release Purpose
SDC London release
Epics
N/A
Stories
N/A
Bug Fixes
SDC-4573 - Import service with JUEL-function produces wrong UI representation
SDC-4572 - Error displaying node filters
SDC-4571 - Issue import node filters
Tasks
N/A
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.13.2
- Release Date:
2023-07-13
SDC SDKs Versions
sdc-distribution-client (Kafka)
- Version:
2.0.1
sdc-distribution-client (DMaap MR - deprecated)
- Version:
1.4.5
sdc-tosca
- Version:
1.8.0
Release Purpose
SDC London release
Epics
N/A
Stories
SDC-4561 - UI support for metadata when editing properties of VFCs
SDC-4558 - Include version in metadata
SDC-4528 - Support TOSCA functions of complex types in composition view
SDC-4555 - Do not collapse complex property when setting element value
SDC-4471 - Create test model
SDC-4537 - Validation of datatype YAML prior to import
Bug Fixes
SDC-4568 - Service import issues
SDC-4564 - JUEL function not displayed correctly in UI (ok in template)
SDC-4566 - Occurrences and instance count do not survive import
SDC-4527 - Unable to set tosca function on complex type on input operation
SDC-4551 - Validation problems when trying to set an operation input of complex type
SDC-4529 - Certifying a template with two connected services results in error (using service proxy in the relationship)
Tasks
SDC-4569 - Replace outdated dependencies
SDC-4567 - Fix missing logs SDC-BE
SDC-4560 - Update outdated/vulnerable dependencies
SDC-4559 - Remove unused ‘org.springframework.boot’ dependency
SDC-4553 - Separate execution of UI and API integration tests to speed up verify feedback
SDC-4557 - Update SDC openapi files
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.13.1
- Release Date:
2023-06-23
SDC SDKs Versions
sdc-distribution-client (Kafka)
- Version:
2.0.1
sdc-distribution-client (DMaap MR - deprecated)
- Version:
1.4.5
sdc-tosca
- Version:
1.8.0
Release Purpose
SDC London release
Epics
N/A
Stories
SDC-4545 - Support custom tosca functions in operation input values
SDC-4521 - Order response from external assets API
SDC-4520 - Additional metadata in external assets api
SDC-4540 - Enable setting of sasl.mechanism for Kafka communincation
SDC-4409 - Update external query api with new query params
Bug Fixes
SDC-4543 - Cannot set instance property
SDC-4498 - Python Code Updates: Service Design and Creation (SDC)
SDC-4539 - Substitution Mapping node properties not updated
SDC-4541 - Fix normative VFCs being set to non normative during service import
SDC-4538 - Cannot set TOSCA function value using nested values for get_input
SDC-4535 - Node filter boolean values output as strings
SDC-4522 - Fix different issues when adding properties
SDC-4530 - NPE in ServiceImportBusinessLogic
Tasks
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.13.0
- Release Date:
2023-06-02
SDC SDKs Versions
sdc-distribution-client (Kafka)
- Version:
2.0.1
sdc-distribution-client (DMaap MR - deprecated)
- Version:
1.4.5
sdc-tosca
- Version:
1.8.0
Release Purpose
SDC London release
Epics
N/A
Stories
SDC-4517 - Support INDEX in node filter tosca functions
SDC-4442 - Support TOSCA functions in operation inputs
SDC-4506 - Support import of service with no substitution mapping node type
SDC-4505 - Support index in tosca functions (nested lists)
SDC-4493 - UI support for default custom function names with get_input structure
SDC-4497 - Disabling archive functionality for normatives
SDC-4395 - Support additional operands for node filters
SDC-4435 - Enable using substitution mapping type directly
SDC-4472 - Stringbuilder support for INDEX token on all functions
SDC-4473 - UI support for default custom function names
SDC-4479 - Support service import with custom tosca functions
SDC-4469 - Support definition of custom tosca function names through configuration
SDC-4477 - VFC Property default value enforced forced to comply with restraints
SDC-4474 - Sort data type drop down lists in add property
SDC-4466 - UI support for custom functions
SDC-4455 - Backend support for custom functions
Bug Fixes
SDC-4518 - Actual sub mapping node not used during import
SDC-4515 - Error when adding valid_values constraint to int property
SDC-4523 - Formatting error for operation input of complex type
SDC-4475 - Adding certain characters into property default value causes VFC to break
SDC-4510 - Bug fixes on tosca function
SDC-4512 - Various bugs related to custom tosca functions
SDC-4511 - Not possible to edit property following import service with custom tosca function
SDC-4508 - Remove need for USER_ID header
SDC-4503 - Invalid json being set on propertyConstraints
SDC-4509 - NPE when using concat TOSCA function
SDC-4507 - Service with custom functions not importing correctly
SDC-4500 - Error in console when no default custom tosca functions
SDC-4502 - Error in handling of operation input of complex type
SDC-4468 - SVC4301 RESTRICTED_OPERATION on service composition
SDC-4482 - Fix complex list/map entries in composition view
SDC-4481 - Fix constraints on custom datatype not formatted correctly in CSAR
Tasks
SDC-4525 - Exclude outdated transitive dependencies com.fasterxml.jackson.
SDC-4519 - Update vulnerable dependencies
SDC-4504 - Update vulnerable dependencies
SDC-4496 - Update outdated gecko.driver
SDC-4495 - Add retry option to wget commands
SDC-4494 - Update Cassandra to 3.11.15
SDC-4467 - Preparation for JDK17
SDC-4470 - Upgrade vulnerable dependency
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.12.5
- Release Date:
2023-05-29
SDC SDKs Versions
sdc-distribution-client (Kafka)
- Version:
2.0.1
sdc-distribution-client (DMaap MR - deprecated)
- Version:
1.4.5
sdc-tosca
- Version:
1.8.0
Release Purpose
SDC London release
Epics
N/A
Stories
N/A
Bug Fixes
SDC-4508 - Remove need for USER_ID header
SDC-4468 - SVC4301 RESTRICTED_OPERATION on service composition
Tasks
N/A
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.12.4
- Release Date:
2023-04-03
SDC SDKs Versions
sdc-distribution-client (Kafka)
- Version:
2.0.1
sdc-distribution-client (DMaap MR - deprecated)
- Version:
1.4.5
sdc-tosca
- Version:
1.8.0
Release Purpose
SDC London release
Epics
N/A
Stories
SDC-4452 - Add robustness to type creation on service import
SDC-4445 - Stringbuilder support for child elements of type list
SDC-4439 - Support to change substitution mapping node or version after service creation
SDC-4430 - Check for service property usage in sub mapping node change
SDC-4451 - No rollback on import fail
Bug Fixes
N/A
Tasks
SDC-4456 - Upgrade docker images to use Python 3
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.12.3
- Release Date:
2023-03-24
SDC SDKs Versions
sdc-distribution-client (Kafka)
- Version:
2.0.1
sdc-distribution-client (DMaap MR - deprecated)
- Version:
1.4.5
sdc-tosca
- Version:
1.8.0
Release Purpose
SDC London early release
Epics
N/A
Stories
SDC-4438 - Allign properties import during service import
SDC-4441 - Order targets in policy target modal
SDC-4423 - Support for delete of non normative interface types
SDC-4427 - Provide input name suggestion
SDC-4385 - Provide input name when declaring service property as input
SDC-4429 - Sort drop down lists in VFC requirements and capabilities
SDC-4424 - VFC property metadata backend support
SDC-4422 - Sort properties in node filter modal
SDC-4316 - Add validation for int and float constraints
Bug Fixes
SDC-4437 - Certifying a template with two connected services results in error
SDC-4434 - Error thrown when setting default value for list of floats property in VFC
SDC-4432 - Valid values constraints not showing for lists
SDC-4431 - Property with ‘::’ in name produces wrong Input
SDC-4405 - Setting Tosca Function on top of unsaved value causes problems
SDC-4404 - Error opening list property for editing
SDC-4410 - Fix instance declared inputs mapped to substitution mapping
SDC-4428 - Fix undeclarePropertiesAsInput in UI after Service Import
SDC-4425 - Unable to use stringbuilder to for simple list/map items
SDC-4420 - VFC interface operation not clearing artifact details when unchecked
SDC-4421 - Operation implementation name not formatting correctly
Tasks
SDC-4287 - PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR LONDON RELEASE
SDC-4446 - Fix missing default no-args constructor
SDC-4425 - Update vulnerable dependency - javax.servlet:javax.servlet-api
SDC-4415 - PortalRestApiCentralServiceImpl- Add null test before using nullable values
SDC-4372 - Remove ‘Security Hotspot - Weak Cryptography’ reported by Sonar
SDC-4414 - TranslationService- Add null test before using nullable values
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.12.2
- Release Date:
2023-02-24
SDC SDKs Versions
sdc-distribution-client (Kafka)
- Version:
2.0.0
sdc-distribution-client (DMaap MR - deprecated)
- Version:
1.4.5
sdc-tosca
- Version:
1.7.0
Release Purpose
SDC London early release
Epics
N/A
Stories
SDC-4411 - Delete non-normative data types
SDC-4365 - Show boolean-type constraint as drop-down list
SDC-4379 - Support TOSCA functions for list of map entries in property assignment view
SDC-4371 - Service Import - general page validation
SDC-4383 - Implement option to choose ‘None’ for not mandatory drop-box field
SDC-4378 - Support for delete property from non-normative data type
SDC-4373 - Edit properties of non-normative data types
SDC-4331 - Constraints in data type view
SDC-4360 - Enable UI component to display property constraints
SDC-4366 - Validate service input default values against constraints
SDC-4361 - Stop auto-generation of inputs from substitution mapping node
Bug Fixes
SDC-4418 - Type list of floats not generated correctly in tosca
SDC-4375 - Fix handling of default values for VFC properties
SDC-4412 - Constraint validation failure for list or map with valid values
SDC-4416 - Cannot view archived components on UI
SDC-4413 - Compilation error when building
SDC-4399 - Error validating list property with equals constraint
SDC-4401 - Constraint validation failure for yaml value
SDC-4398 - Incorrect behaviour for list valid values
SDC-3384 - Wrong behavior for ‘edit’ attribute
SDC-4400 - Issues adding values to complex properties in Property Assignment
SDC-4403 - NPE when setting value of complex property
SDC-4396 - AttributeServlet- Add null test before using nullable values
SDC-4394 - Support for copy/paste tosca functions into operation inputs
SDC-4392 - Issues adding values to map in Property Assignment
SDC-4380 - Fix ng lint command missing configuration
SDC-4384 - Omit tenant metadata when not set
SDC-4382 - Cannot set value to a instance property with valid values constraint
SDC-4377 - Inconsistent behaviour for interface properties removal
SDC-3794 - Incorrect substitution type being set in Services/VFs
SDC-4374 - Setting input value destroys constraints
SDC-4376 - Unable to discard service input changes
SDC-4369 - Import failures added to additional_types
SDC-4364 - NPE when deleting interface operation from VFC
SDC-4357 - in_range constraints missing from TOSCA template
SDC-3863 - Composition window category name shows instead of displayName
SDC-4352 - Unable to set values on properties of VFC instances in a service
SDC-4362 - Fix tiles on Home page always show model as SDC AID
SDC-4354 - Unable to edit VFC property after checkout
Tasks
SDC-4408 - NotificationWebsocketHandler- Add null test before using nullable values
SDC-4406 - Update INFO.yaml
SDC-4402 - ConfigurationImpl- Add null test before using nullable values
SDC-4397 - AbstractTemplateServlet- Add null test before using nullable values
SDC-4381 - Fix major bug reported by Sonar
SDC-4358 - Improve getting Service with specific version
SDC-4370 - Fix broken ‘start-sdc’ profile
SDC-4112 - Skip swagger to improve build time
SDC-4359 - Fix Blocker Bug reported by Sonar
SDC-3529 - Fix Sonar CRITICAL BUGs
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.12.1
- Release Date:
2023-01-27
SDC SDKs Versions
sdc-distribution-client (Kafka)
- Version:
2.0.0
sdc-distribution-client (DMaap MR - deprecated)
- Version:
1.4.5
sdc-tosca
- Version:
1.7.0
Release Purpose
SDC London early release
Epics
N/A
Stories
SDC-4346 - Property Constraints on Service inputs
SDC-4279 - Import data type in UI
SDC-4344 - Implement hiding mechanism
SDC-4341 - Disable editing of normative data types
SDC-4330 - Improve composition view filtering
SDC-4333 - Support TOSCA functions of primitive list entries in composition view
SDC-4332 - Download data type from UI
SDC-4320 - Constraint validation - Policy Properties in a Service
SDC-4319 - Support TOSCA functions of primitive map entries in composition view
SDC-4311 - Update needed to allow assignment of TOSCA functions to List/Map/Custom datatypes
SDC-4305 - Add support for comparable type constraints for scalar values
SDC-4288 - Support TOSCA functions in list entries
SDC-4299 - Add support for comparable type constraints for strings
SDC-4283 - Node filter/Substitution filter: type validation just works during edit
SDC-4264 - Support TOSCA functions for map values
DMAAP-1787 - [SDC] Migrate SDC to use kafka native messaging
SDC-4221 - Open Data type from Catalog
SDC-4260 - Update UI Constraints component to support addition of pattern constraints
SDC-4220 - View data types in UI catalog
SDC-4223 - Update UI Constraints component to support addition of scalar type constraints
SDC-4258 - Addition of Properties to a Data type in UI
SDC-4219 - Create UI Component for viewing property constraints
SDC-4170 - Support TOSCA functions in operation implementation properties
Bug Fixes
SDC-4318 - Fix constraints saving as strings
SDC-4351 - Error importing data type in the UI
SDC-4352 - Unable to set values on properties of VFC instances in a service
SDC-4349 - Added datatype property not include in model definitions
SDC-4343 - Invalid property values provided: Unsupported value provided for is_default property supported value type is boolean.
SDC-4348 - Frontend cache causing data types not found
SDC-4345 - Property Constraint error when uprading VFC instance version in service
SDC-4334 - Error creating in_range constraint for non integer properties
SDC-4339 - Possible to add property to data type with type belonging to other model
SDC-4342 - Constraint not added when creating property
SDC-3505 - SDC be API returns HTTP 200 response code on error
SDC-4338 - Primitive types should not be shown under data types in catalog
SDC-4337 - Data type cache not updated when data type updated
SDC-4335 - Datatype workspace opens up from wrong menuItem
SDC-4290 - Resource property constraint values mutable in Service design
SDC-4315 - Not possible to add value to list of map property
SDC-4312 - NPE thrown in editing constraints
SDC-3216 - Artifact type “CONTROLLER_BLUEPRINT_ARCHIVE” is not recognized based on its type.
SDC-2851 - Tosca List Entry Schema failed to be recoginized with creating VSP
SDC-4310 - Adding property to VF/Service throws js-exception
SDC-4292 - Swagger UI fails to load
SDC-4307 - Not possible to set value on a VFC property with constraint
SDC-4294 - Pattern constraint validation failure
SDC-4306 - Some default responses in the generated openapi files are missing descriptions
SDC-4302 - Fix docker build issue
SDC-4291 - Import VFC with constraint PATTERN ignores constraint
SDC-4303 - NPE thrown when checking out Service
SDC-4293 - in_range constraint validation gives unhelpful error message
SDC-4286 - Constraint not displayed when cycling through properties
SDC-4274 - Numeric constraint values generated as strings
SDC-4281 - Empty interfaces and operations in generated tosca
SDC-4271 - SDC-simulator not logging to STDOUT
SDC-3536 - SDC-ONBOARDING-BE log does not use stdout
SDC-4266 - Error while importing a Service: icon cannot be changed once the resource is certified
SDC-4267 - EcompIntImpl - And null test before using nullable value
SDC-4253 - Changing property in a node filter causes several issues
SDC-4222 - Fix behaviour when validation of property constraints
SDC-4269 - ExternalTestingManagerImpl - Add null test before using nullable value
SDC-3535 - SDC-FE log does not use STDOUT
SDC-3534 - SDC-BE log does not use STDOUT
SDC-4268 - Model for “SOL001” shows incorrectly in GUI
SDC-4265 - DefaultPropertyDeclarator - Add null test before using nullable value
SDC-4259 - Interfaces in VNFD in ETSI NSD
SDC-4242 - fix doc config files in master and kohn branch
SDC-4255 - Interface is formatted using extended notation when no implementation added at VFC level
SDC-4237 - Tosca Export: a boolean, from a default complex type value, is being exported as string
Tasks
SDC-4347 - Improve test coverage for Constraints
SDC-4317 - Improve test coverage
SDC-4308 - Update openapi files in the docs
SDC-4313 - Upgrade testing frameworks to latest not-vulnerable versions
SDC-4314 - Fix broken build
SDC-4215 - Multitenancy feature in SDC
SDC-4304 - Update INFO.yaml
SDC-4300 - Add missing ‘scalar-unit.bitrate’ data type
SDC-4289 - Fix broken build
SDC-4275 - Add SonarCloud badges to README
DOC-798 - Create docs for ‘Kohn’ main release
SDC-4243 - Issues with ‘range’ data type detected
SDC-4261 - Fix Readme formatting for Catalog-UI
SDC-4254 - Remove ‘Powered by Jetty’ from default jetty response
SDC-4256 - Improve error reporting when onboarding a VSP and storage is full
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.12.0
- Release Date:
2022-10-28
SDC SDKs Versions
sdc-distribution-client (Kafka)
- Version:
2.0.0
sdc-distribution-client (DMaap MR - deprecated)
- Version:
1.4.5
sdc-tosca
- Version:
1.7.0
Release Purpose
SDC London early release
Epics
N/A
Stories
SDC-4207 - Constraint validation - Node Template Interfaces
SDC-4229 - Default Substitution Mapping
DMAAP-1787 - [SDC] Migrate SDC to use kafka native messaging
SDC-4216 - Support import of VFCs with property constraints
SDC-4209 - Constraint validation - Instance Attributes in a Service
SDC-4210 - VFC properties - Increase character limit to 100 and allow use of @ character
SDC-4214 - View Data type properties in UI
SDC-4142 - Service import - Import updated node types with new attributes
SDC-4208 - Enable viewing of VFC property details when checked in
SDC-4190 - Constraint validation - Instance Properties in a Service
SDC-4193 - View data type in UI
SDC-4184 - API for fetching single data type
DMAAP-1744 - Move SDC and clients to use Strimzi Kafka
Bug Fixes
SDC-4224 - Import service with policy error
SDC-4225 - Import of service with concat property value issue
SDC-4227 - Error importing service with instance interfaces
SDC-4189 - security risk: Improper Input Validation
SDC-4217 - Setting value on interface operation property with constraint throws exception
SDC-4218 - Fix cant set properties on an instance in the composition view
SDC-4211 - Fetch data type endpoint is returning Optional instead of the requested Data Type
SDC-4213 - Onboard-ui build started to fail with problems in ./node_modules/react-show-more-text/lib/ShowMoreText.css
SDC-4196 - Empty interface operation definitions throw exception
SDC-4192 - X-Frame-Options not configured: Lack of clickjacking protection
SDC-4185 - Composition Window doesnot allow to update new version of VFC
Tasks
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.11.9
- Release Date:
2022-09-28
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.5
sdc-tosca
- Version:
1.7.0
Release Purpose
SDC Kohn M4 release
Epics
SDC-4034 - Service Import
SDC-4037 - Additional TOSCA constructs support Kohn
SDC-4035 - Deletion of archived assets
SDC-4037 - Additional TOSCA constructs support Kohn
SDC-4036 - Enable application metrics
Stories
SDC-4186 - Service import - Import unknown interface types
SDC-4187 - Service import - Import unknown capability types
SDC-4176 - Service import - Import unknown group types
SDC-4173 - Support tosca functions for node capability filters
SDC-4153 - Service import - Import necessary artifact types
SDC-4162 - Service Import - yaml error
Bug Fixes
SDC-4125 - Error thrown when setting policy property with get_property
SDC-4188 - Fix show add button for Req and Capabilities in VF
SDC-4181 - Simulator showing server exception when no content type is provided
SDC-4179 - maven-resources-plugin filtering problem with plugins-configuration.yaml
SDC-4175 - Capablity Types not refreshing after model change
Tasks
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.11.8
- Release Date:
2022-09-09
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.5
sdc-tosca
- Version:
1.7.0
Release Purpose
SDC Kohn early release
Epics
N/A
Stories
SDC-4168 - Support import of service with TOSCA functions in sub properties
SDC-4171 - Relax checking on operation property values
SDC-4128 - Support TOSCA functions for node filters
SDC-4151 - Support TOSCA functions in sub properties in properties assignment
SDC-4131 - Service import - Import updated node types
SDC-4149 - Allow to select properties in the get_attribute function
SDC-4140 - Service import - Import updated data types
SDC-4137 - Service Import - general page validation
SDC-4082 - Service Import - Inputs
SDC-4136 - Allow ETSI VNF without other node template
Bug Fixes
SDC-4174 - New node filter API does not accept legacy payload
SDC-4166 - Importing service with TOSCA function yaml value
SDC-4169 - application exposed to path traversal attack
SDC-4134 - Import VFC not importing interfaces
SDC-4145 - NPE thrown for interface operation template with no inputs
SDC-4150 - Import service - sub import files are not loading
SDC-4097 - Wrong Inputs creation on ‘Add Service’
SDC-4144 - SDC Jakarta release: “create service” does not work when new category added
SDC-4141 - Encrypted user not being handled correctly in SDC-BE
SDC-4130 - Fix Wrongly generated tosca implementation
SDC-4132 - Fix error handling for instances with no properties
SDC-4133 - ClassCastException thrown for artifact primary string value
Tasks
SDC-4167 - Update/remove vulnerable dependencies
SDC-4165 - Update SDC with new ‘security-util-lib’ version
DOC-782 - Create docs for ‘Jakarta’ main release
SDC-4143 - Improve error’s message readability
SDC-4017 - Remove/update vulnerable dependency
SDC-4139 - Fix broken build
SDC-4133 - ClassCastException thrown for artifact primary string value
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.11.7
- Release Date:
2022-08-15
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.5
sdc-tosca
- Version:
1.7.0
Release Purpose
SDC Kohn early release
Epics
N/A
Stories
SDC-4113 - Service Import - Node Template Interface Definitions
SDC-4118 - Service import - Import unknown node types
SDC-4119 - Service import - Import unknown data types
SDC-4123 - Support property get_input value in deprecated format
SDC-4122 - Support tosca functions for policy instance properties in property assignment view
SDC-4120 - Support for TOSCA functions for Service Import
SDC-4083 - Service Import - Node Template Relationship Template
SDC-4109 - Enable configuration of instance name
SDC-4099 - Set property to yaml string in TOSCA functions modal
Bug Fixes
SDC-4129 - Newly imported data types not found in UI
SDC-4126 - Properties of the previous instance is loading in the Hierarchical panel
SDC-4127 - Fix unable to delete default value for a complex property
SDC-4124 - Empty node filter in template when directives added with no filter
SDC-4117 - Error Importing node filter with multiple capability properties
SDC-4125 - Error thrown when setting policy property with get_property
SDC-4098 - Error adding capability with properties to VFC
SDC-4121 - Fix outputs of complex type display and delete
SDC-4114 - Fix Tosca Function Validation for Group and Policy properties
SDC-4116 - UI shows text overlay on value field
SDC-4115 - Fix functionaljava dependency for onboarding
SDC-4084 - Group Property value display not easily readable
SDC-4110 - Save button disabled in update property in composition view
Tasks
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.11.6
- Release Date:
2022-07-21
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.5
sdc-tosca
- Version:
1.7.0
Release Purpose
SDC Kohn early release
Epics
N/A
Stories
SDC-4078 - Support tosca functions for group instances in composition view
SDC-4060 - Service Import - Policies
SDC-4051 - Service Import - Outputs
SDC-4080 - Allow set values in properties of type timestamp
SDC-4095 - Support concat for string property values
SDC-4090 - Support tosca functions for group instances
Bug Fixes
SDC-4048 - VFC properties of type timestamp not visible in property assignment
SDC-4063 - Directives drop down list cut short
SDC-4087 - Node Filters displayed incorrectly
SDC-4088 - Save/discard button not showing for an instance attributes
SDC-4081 - Fail to declare Input for duplicated name of property
SDC-4089 - Fix upgrade failure
SDC-4079 - Service Import - Input appearing as a property
SDC-4091 - Fix clear value for group instances toscaGetFunction
SDC-4085 - Unable to create a property on SELF of type List <Map>
SDC-4096 - Changing VFC version on composition page results in error
SDC-4101 - Fix incorrect dependency scope change
Tasks
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.11.5
- Release Date:
2022-06-24
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.5
sdc-tosca
- Version:
1.7.0
Release Purpose
SDC Kohn early release
Epics
N/A
Stories
SDC-3982 - Rearrange Interface Operation Implementation
SDC-4055 - Delete interface operation from VFC
SDC-4052 - Service Import - Input Metadata
SDC-4049 - Service Import - Node Template Node Filter
SDC-4053 - Support get_attribute in Property Assignment TOSCA functions
SDC-4054 - Service Import - Groups
SDC-4044 - Service Import - Read metadata from csar
SDC-4065 - Make instance count optional
Bug Fixes
SDC-4041 - Fix broken build
SDC-4042 - TOSCA function modal input/property not found message does not disappear
SDC-4046 - After a checkout in the VFC Properties page, can’t edit a property
SDC-4043 - Load inputs/properties in Tosca Get Function dialog considering the selected property schema
SDC-4047 - Disable the save button in Property assignment TOSCA Function Modal for invalid values
SDC-4039 - Fix getToscaFunction validation for property value
SDC-4038 - Fix loading issue and double errors in properties assignment
SDC-4050 - Update a list of map in VFC Properties - error while adding a new entry
SDC-4057 - get_input not working for complex properties
SDC-4059 - Fix interface name and operation not being disabled on edit
SDC-4058 - VFC interface operation can be edited even when checked in
SDC-4061 - Fix Interface Operation mandatory fields
SDC-4045 - Fix interface operation implementation not being updated on version change
Tasks
SDC-4056 - Remove unused maven properties in main pom
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.11.4
- Release Date:
2022-06-09
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.5
sdc-tosca
- Version:
1.7.0
Release Purpose
SDC Kohn early release
Epics
N/A
Stories
SDC-4031 - get_property support in Update Property modal from Composition page
SDC-4028 - Allow to edit a TOSCA get function value in the Properties Assignment
SDC-4025 - Maintain VFC instance attribute outputs on instance version change
SDC-4018 - Maintain VFC UI added interface operations after an upgrade
SDC-4012 - Maintain VFC UI added properties after an upgrade
SDC-4016 - Maintain VFC external capabilities and requirements on instance version change
SDC-4026 - Component Instance property selection in Property Assignment get property
SDC-4009 - Maintain VFC instance interface operation details on instance version change
SDC-4023 - Delete VSP - Ensure complete deletion of VSP from DB
SDC-4014 - Support get_property in Property Assignment TOSCA functions
SDC-4015 - Maintain VFC instance occurrences values on instance version change
Bug Fixes
SDC-4032 - sdc-be-init fails intermittently
SDC-4030 - Fix Component Instance requirements and capabilities not updating
SDC-4024 - Interface Operation Implementation artifact file name incorrect for extended notation
SDC-4027 - Error when restoring VLM: Unable to restore partially deleted VSP, re-try VSP deletion
SDC-4022 - Inconsistent behavior adding a CONCAT string to VFC property and node filter property
SDC-4021 - Fix Component Instance versions not updating
SDC-4013 - Exception thrown when accessing a VF General page
SDC-3987 - Node Filter string property value displayed as object
Tasks
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.11.3
- Release Date:
2022-05-17
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.5
sdc-tosca
- Version:
1.7.0
Release Purpose
SDC Kohn early release
Epics
N/A
Stories
SDC-3999 - Import VFC with interface operation implementation extended notataion
SDC-4001 - Support list<map<string, string>> properties in composition screen dialog
SDC-3996 - Generalise Select Input button in Properties Assignment view
SDC-4003 - Onboarded ASD csar included in VF csar
Bug Fixes
SDC-3989 - additional_type_definition file missing in the csar package
SDC-3990 - Custom datatype error when creating new property/input
SDC-3983 - Fix inputs/policy tabs view for self and instances
SDC-3991 - VLM duplicate name gives generic error
SDC-4000 - Edit Operation modal does not offer correct artifact types and data types
SDC-3997 - Interface panel is blank when switch to a different version of a VFC
SDC-3998 - Datatypes for a property are not specific to the VFC model
SDC-4007 - Unable to delete Map from List<Maps> property type
SDC-4010 - Fix UI not displaying directives list correctly
Tasks
N/A
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.11.2
- Release Date:
2022-04-23
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.5
sdc-tosca
- Version:
1.7.0
Release Purpose
SDC Kohn early release
Epics
N/A
Stories
SDC-3964 - Onboarding UI support for VLM deletion
SDC-3957 - Add application metrics in the catalog backend
SDC-3956 - Add application metrics in the onboarding backend
SDC-3966 - Restrict deletion of a VLM that is in use by any VSP
SDC-3968 - Delete VLM - Support deletion of archived VLMs in onboarding BE
SDC-3972 - Delete VFC - distinguish between system deployed or user deployed VFCs
SDC-3981 - Delete VFC - restrict deletion of system deployed VFCs
SDC-3936 - Delete Service - Support deletion of archived services in SDC BE
SDC-3962 - Delete service - UI support for deleting services
SDC-3969 - Add an UI feedback when saving a interface operation
SDC-3973 - Delete Service - Support deletion of archived VFs in SDC BE
Bug Fixes
SDC-3960 - Adjust onboarding UI min node npm version
SDC-3957 - Add application metrics in the catalog backend
SDC-3967 - Failed to launch to SDC from Portal
SDC-3971 - Fix incorrect version in metrics-rest
SDC-3975 - Unit tests with conflicting output folder, resulting in intermittent build errors
SDC-3974 - NPE thrown when adding ASD VF to a service
SDC-3985 - Edit/Delete options for directives are not disabled when service is checked in / certified
SDC-3986 - Fix check to restrict deletion for system deployed VFCs
Tasks
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.11.1
- Release Date:
2022-04-08
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.5
sdc-tosca
- Version:
1.6.6
Release Purpose
SDC Kohn early release
Epics
N/A
Stories
SDC-3938 - Add ASD node and data types to SDC AID model
SDC-3952 - Delete VSP - Onboarding UI support for VSP deletion
Bug Fixes
SDC-3953 - Fix error handling for VSP usage check in VF
Tasks
N/A
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.11.0
- Release Date:
2022-04-05
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.5
sdc-tosca
- Version:
1.6.6
Release Purpose
SDC Kohn early release
Epics
N/A
Stories
SDC-3893 - UI support for editing interfaces on a node type
SDC-3931 - Delete VSP - Handling partial delete failure
SDC-3935 - Delete VSP - Restore of partially deleted VSP
SDC-3948 - Add ASD artifact type to SDC AID model
SDC-3893 - UI support for editing interfaces on a node type
SDC-3894 - Delete VSP - Restrict deletion of archived VSPs if used in VF
SDC-3884 - Copy entry_defintion_type to TOSCA.meta
SDC-3890 - Delete VSP - Support deletion of archived VSPs in onboarding BE
Bug Fixes
SDC-3939 - NPE thrown in service import
SDC-3934 - Package storage and reducer config are not reloading when there is a config change
SDC-3937 - PM_DICTIONARY check is causing nullpointer
SDC-3926 - Setting value of list or map property with complex type results in single value
SDC-3928 - Fix unable to update ‘Interface Name’ in VF
Tasks
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.10.3
- Release Date:
2022-03-22
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.5
sdc-tosca
- Version:
1.6.6
Release Purpose
SDC Jakarta
- Epics
N/A
- Stories
N/A
Bug Fixes
SDC-3921 - Map entry deletion not showing for inputs of type map<a complex type> in interface operation
SDC-3922 - Node filters not loading while editing the select directive list
SDC-3919 - Instance count not being added correctly to node template
SDC-3918 - Interface operation artifact implementation is being persisted even if not selected
SDC-3920 - Default value for inputs of complex type (in a instance interface operation) not being saved as JSON string
SDC-3916 - Error assigning substitution filter property to service property
Tasks
SDC-3923 - Implement redirecting root url to sdc1
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.10.2
- Release Date:
2022-03-15
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.5
sdc-tosca
- Version:
1.6.6
Release Purpose
SDC Jakarta
- Epics
N/A
Stories
SDC-3885 - Remove single request bottleneck from the simulator
SDC-3886 - Implement improved MinIo client
SDC-3861 - Support for multiple directives
SDC-3898 - Support properties of type List<Map<String, String>>
SDC-3891 - Update SDC for rename of TOSCA CL to ACM
SDC-3882 - Support occurrences on node templates
SDC-3897 - Support complex types in interface operation inputs
SDC-3899 - Support complex types for artifact properties in interface operation implementation
SDC-3887 - Support instance count on node template
Bug Fixes
SDC-3881 - Fix NSD plugin to find version by model and category metadata
SDC-3892 - SDC build failing
SDC-3889 - Error when no derived from exists
SDC-3888 - VSP upload with large files can handle the upload status incorrectly
SDC-3901 - Cannot create node filter capability if capability has different type properties
SDC-3907 - Exception when mouse over and out the node pallet in the composition screen
SDC-3905 - Error updating node filter capability
SDC-3904 - Error creating node filter capability using get_property
Tasks
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.10.1
- Release Date:
2022-02-02
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.5
sdc-tosca
- Version:
1.6.6
Release Purpose
SDC Jakarta
- Epics
N/A
Stories
SDC-3867 - Improve service import support
SDC-3842 - Add Controlloop design-time components to SDC
SDC-3862 - Obtain and control VSP package upload status
SDC-3855 - Add artifact types to ETSI SOL001 v2.5.1 model
SDC-3858 - Add a display name for the category
SDC-3850 - Add Interface support to VFC for viewing an interface definition
SDC-3848 - Update VSP upload status during backend processing
SDC-3856 - Issues creating control loop model
SDC-3847 - Support node template artifact properties
SDC-3846 - Add support for update to artifact types endpoint
SDC-3827 - Create endpoint to check status of the VSP package upload
SDC-3826 - Create endpoint to acquire a VSP package upload lock
SDC-3845 - Add sdc-be-init support for artifact types
Bug Fixes
SDC-3866 - Fix VFC being removed from the list of allowable types
SDC-3864 - UI hangs if drag/and drop policy in composition view
SDC-3860 - Error in artifact update
SDC-3851 - Decrypt errors in sdc-be logs
SDC-3852 - Cassandra init dockers not working with latest version of cqlsh
SDC-2902 - Make sure Optionals values are defined before calling their get method
SDC-3840 - Remove test-jar generation
Tasks
Security Notes
Fixed Security Issues
N/A
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.10.0
- Release Date:
2022-01-07
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.5
sdc-tosca
- Version:
1.6.6
Release Purpose
SDC Jakarta first release
- Epics
N/A
Stories
SDC-3837 - Update property to identify SOL004 packages
SDC-3819 - Solution for identifying SOL004 packages
SDC-3805 - Allows custom property type names
SDC-3803 - Enable VF to be nested in a VF
SDC-3802 - Allow space and single quote in prop names
SDC-3774 - Update service import to import substitution filters
SDC-3775 - Update service import to import node filters
SDC-3793 - Node filter property value equals input value
SDC-3764 - Update service import to import service properties
SDC-3754 - Large csar handling - object store
SDC-3768 - UI support for adding artifacts to an interface operation implementation
SDC-3763 - Support for adding artifact types
SDC-3735 - Integration Tests - Import tosca types for a model
SDC-3715 - Import VSP with non-standard policy types
SDC-3759 - Allow Service base type to be optional
SDC-3760 - Support get_input for complex data types
SDC-3752 - Import multiple node_types in a single endpoint during the initialization
SDC-3737 - Add a display name for the category metadataKeys entries
SDC-3751 - Allow importing service with no instances
SDC-3725 - Type safety in node filters
SDC-3706 - Filter categories by model
SDC-3727 - Allow multiple base types for a service
SDC-3736 - Display model in UI tiles
SDC-3729 - Expand allowed chars in property names to include colon
Bug Fixes
SDC-2921 - ToscaElementLifecycleOperation - Add null test before using nullable values
SDC-3018 - Fix import service to persist its model name
SDC-3822 - Topology template inputs created for interface inputs
SDC-3800 - Unable to set interface opertion for custom interface type
SDC-3799 - Not possible to set value of custom data type
SDC-3796 - Fix Incorrect properties entry on the interface operation definition and Required fields validation
SDC-3798 - Node Filter UI faults
SDC-3801 - Fix import service to persist its model name
SDC-3792 - VNFD not added to NSD when using S3 storage
SDC-3791 - Base type not set when not provided in the Service creation API
SDC-3757 - Test cases failing incorrectly on Jenkins
SDC-3784 - Not possible to restore an archived component
SDC-3607 - fix CRITICAL xss (cross site scripting) issues identified in sonarcloud
SDC-3770 - unable to run TCs separately (ImportVfcUiTest)
SDC-3765 - Changing the model during the service creation can cause invalid category and base type state
SDC-3734 - Fix child model being shown in UI
Tasks
SDC-3824 - Make configurable UI version
SDC-3823 - Update Catalog-model set skip deploy to false
SDC-3816 - Fix MongoSocketOpenException-issue
SDC-3804 - Improve fast-build profile
SDC-3790 - Upgrade VSP is using the wrong VSP version id
SDC-3785 - Fix potential NPE
SDC-3771 - Fix CSV’s generation on wrong folder
SDC-3776 - Fix broken TC (ExternalRefsServletTest)
SDC-3783 - Use base image user on sdc-backend-all-plugins docker image descriptor
SDC-3782 - Remove unnecessary maven resource filtering in asdctool
SDC-3772 - Fix discrepancy in IT between Intellij and maven
SDC-3753 - Skip UI tests during fast build
SDC-3761 - Define encoding while reading files in python init scripts
SDC-3741 - Clean sdctool.tar during build
Security Notes
Fixed Security Issues
SDC-3820 - Fix potential Log4Shell Security Vulnerability
SDC-3795 - Analyse vulnerable dependency versions in SDC
Known Security Issues
OJSI-94 - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.9.3
- Release Date:
2021-09-30
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.5
sdc-tosca
- Version:
1.6.6
Release Purpose
SDC Istanbul Release
Epics
Stories
The full list of implemented stories is available on JIRA ISTANBUL STORIES
Tasks
The full list of implemented tasks is available on JIRA ISTANBUL TASKS
Bug Fixes
The full list of fixed bugs is available on JIRA ISTANBUL BUGS
Security Notes
Fixed Security Issues
[SDC-3634] - Fix security vulnerabilities
[SDC-3572] - Update Vulnerable package dependencies for I release
Known Security Issues
[OJSI-94] - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.8.5
- Release Date:
2021-04-22
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.2
sdc-tosca
- Version:
1.6.5
Release Purpose
SDC Honolulu Release
Epics
SDC-3338 - Design ETSI SOL007 compliant Network Service Descriptor packages
SDC-3279 - SDC Enhancements for ETSI-Alignment for Honolulu
SDC-2813 - Support additional package artifact Indicators for ETSI packages and Non-ETSI packages
SDC-2613 - SDC supports ETSI 3.3.1 Package security and validation for SOL007 and SOL004 packages
SDC-2610 - Support Onboard ETSI 3.3.1 SOL004 compliant VNF / CNF packages
Stories
SDC-3491 - Update guava version
SDC-3484 - Increase SDC unit test coverage
SDC-3471 - Creation of Vendor Licensing Model is an optional step in VSP onboarding
SDC-3470 - Update node and data types in ONAP for ETSI SOL001 3.3.1 + minimum CNF enhancements
SDC-3466 - Improve import and export VFC TOSCA attributes
SDC-3447 - Handle ETSI versions in NSD Plugin
SDC-3446 - Support for updating interface operations in component instances
SDC-3435 - Initial support for relationship_templates
SDC-3432 - Enable updating of existing categories
SDC-3417 - SDC Distribution Client - enable test pipeline and add artifact consumption tests
SDC-3412 - Support for category specific metadata
SDC-3404 - Set directives and node_filters in any node type
SDC-3402 - Adapt SDC-BE to support new SDC Distribution Client notifications format
SDC-3401 - Adapt SDC FE Distribution Status to support new notifications format
SDC-3400 - SDC Distribution Client - Migrate to Java 11
SDC-3399 - Support for metadata in topology inputs
SDC-3380 - Support the SOL001 vnf_profile properties
SDC-3373 - Allow to set directives and node_filters in any node type
SDC-3372 - Support for interface input during import VFC
SDC-3352 - Support for mapping of ETSI v3.3.1 SOL001 VNF Descriptor with minimum CNF enhancements from 4.1.1 into SDC AID Data Model
SDC-3351 - Support for onboarding ETSI v3.3.1 SOL001 VNF Descriptors with minimum CNF enhancements from 4.1.1
SDC-3342 - Support for mapping of ETSI v3.3.1 SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model
SDC-3341 - Support for using VNFs with CNF enhancements
SDC-3340 - Compose of one or more VNFs and the Virtual Links that connect them
SDC-3339 - Support for designing an ETSI SOL001 v3.3.1 compliant Network Service that can be deployed with an ETSI compliant NFVO
SDC-3337 - Support for onboarding ETSI v3.3.1 SOL004 VNF CSAR Packages with minimum CNF enhancements from 4.1.1
SDC-3335 - Fix Node Filter for capabilities
SDC-3303 - Allow hot reloading of specific config properties
SDC-3103 - Change creation of VLM to be optional
SDC-2815 - SDC client supports additional filtering on the artifact types for distinguishing between ETSI packages and Non-ETSI packages
SDC-2814 - SDC Notification supports additional package artifact types to split ETSI package from other non-ETSI TOSCA packages
SDC-2614 - SDC supports SOL007 NS Package security
SDC-2611 - Support for onboarding ETSI v3.3.1 SOL001 VNF Descriptors
Tasks
The full list of implemented tasks is available on JIRA HONOLULU TASKS
Bug Fixes
The full list of fixed bugs is available on JIRA HONOLULU BUGS
Security Notes
Fixed Security Issues
[OJSI-90] - SDC exposes unprotected API for user creation
Known Security Issues
[OJSI-94] - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
Uploading and on-boarding several VSP in parallel can cause SDC exceptions, a user should retry failed operations which typically succeed on second try.
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.7.3
- Release Date:
2020-11-19
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.1
sdc-tosca
- Version:
1.6.5
Release Purpose
SDC Guilin Release
Epics
SDC-3085 - Test Topology Auto Design （NFV Testing Automatic Platform）
SDC-2802 - Design ETSI SOL007 compliant Network Service Descriptor packages
Stories
SDC-3275 - Make directives options configurable
SDC-3262 - Support for node_filters - capabilities
SDC-3257 - Enable node_filter update action
SDC-3254 - Map topology inputs to properties in substitution mapping
SDC-3249 - ETSI Network Service Descriptor CSAR plugin
SDC-3244 - Change the ONBOARDED_PACKAGE directory to the ETSI_PACKAGE directory
SDC-3195 - Add UI support for substitution_filter
SDC-3184 - Distribute HELM package artifact as a part of VF
SDC-3183 - Create VF model from VSP with HELM type inside
SDC-3182 - SDC should support CNF Orchestration
SDC-3180 - Support for Test Topology Auto Design- Abstract Service Template
SDC-3179 - Support for Test Topology Auto Design- Service Import
SDC-3177 - Config instances types allowed to be used in the component composition
SDC-3173 - SDC must not use root access to DB
SDC-3172 - SDC to support automatic retrieval of certificates
SDC-3167 - Create VSP with HELM as a native artifact type
SDC-3147 - Add back-end support for substitution_filter
SDC-3131 - Improve Utils coverage and improve Sonar score
SDC-3095 - Add support for node_filter on VFC
SDC-3094 - Migrate any Python code to version 3.8
SDC-3087 - E2E Network Slicing: KPI Monitoring
SDC-3086 - E2E Network Slicing: subnet slicing
SDC-3084 - Initial support for TOSCA property constraints in ToscaProperty class and constraint valid_values
SDC-3079 - Make Directive values Tosca compliant
SDC-3075 - Allow TOSCA Entity Type Schema and specific Interface Type entries in an Interface Type
SDC-3074 - Add support for directives on VFC
SDC-3062 - Plugable entry to customize properties during Service creation
SDC-3061 - Expose generic Service properties as properties, not only as inputs
SDC-3060 - Update a resource template from a new onboarding package
SDC-3051 - Upgrade Vulnerable Direct Dependencies
SDC-3021 - Enable by configuration which global type file should be added to the generated CSAR
SDC-3020 - Adjust docker-compose and SSL config in Workflow plugin
SDC-2997 - HEAT to TOSCA VM Consolidation
SDC-2984 - Remove powermock dependency
SDC-2957 - Support the substitution_mappings in the VNFD
SDC-2883 - Support design of Service templates, including NSDs
SDC-2877 - Support for configuring base tosca type on a category basis
SDC-2854 - Support 50 characters for VSP name in OnBoarding
SDC-2820 - Create / Update Entitlement Pool - Support Type Field
SDC-2810 - Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using an external NFVO
SDC-2809 - Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using VF-C as the NFVO
SDC-2808 - Design ETSI SOL001 NSD and generate ETSI SOL001 compliant Network Service descriptor and package
SDC-2804 - SDC supports onboarding of the SOL007 NS package for an External NFVO
SDC-2781 - Allow other entries for SOL004 Tosca.meta
SDC-2775 - Include derived_from types in generated csar
SDC-2772 - Import of VFC interface implementation
SDC-2771 - Unassigned requirements in topology template substitution mapping
SDC-2768 - Support Tosca DependsOn root node relationship
SDC-2754 - Allow SDC component artifact types to be configurable
SDC-2688 - Upgrade Selenium
SDC-2659 - Support setting custom properties required true/false in UI
SDC-2642 - Archive DCAE-DS project
SDC-2618 - Mapping between SOL001 NSD and SDC AID DM/SDC Internal TOSCA
SDC-2612 - SDC supports onboarding of the SOL007 NS package for VFC as the NFVO
SDC-2590 - Upgrade To Cassandra 3
Tasks
The full list of implemented tasks is available on JIRA GUILIN TASKS
Bug Fixes
The full list of fixed bugs is available on JIRA GUILIN BUGS
Security Notes
Fixed Security Issues
Known Security Issues
[OJSI-90] - SDC exposes unprotected API for user creation
[OJSI-94] - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
N/A
Upgrade Notes
N/A
Deprecation Notes
SDC DCAE-DS plugin is now deprecated (replaced by DCAE-MOD)
Other
N/A
Version: 1.6.7
- Release Date:
2020-07-23
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.1
sdc-tosca
- Version:
1.6.2
Release Purpose
Frankfurt maintenance release : fix high severity bugs identified post Frankfurt
Stories/Bug fixes/Tasks implemented
Security Notes
Fixed Security Issues
Known Security Issues
[OJSI-90] - SDC exposes unprotected API for user creation
[OJSI-94] - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
N/A
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.6.6
- Release Date:
2020-06-04
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.1
sdc-tosca
- Version:
1.6.2
Release Purpose
Epics
SDC-1607 - Logging alignemnet to 1.2 logging spec
SDC-1970 - Supporting PNF package onboarding
SDC-2011 - Design Studio (DCAE-DS) support for 3GPP PM Mapper
SDC-2378 - ONAP as Third Party Domain Manager - Import Third Party Catalog in SDC
SDC-2415 - AAF integration of HTTPS certificates
SDC-2482 - Add VSP Compliance and Verification Check feature Phase 2
SDC-2555 - SDC support of Network Slicing Demo in Frankfurt
SDC-2598 - Frankfurt release planning milestone
SDC-2643 - Collapsing Roles / Role consolidation
SDC-2683 - Functionality and API Freeze
SDC-2742 - Code Freeze
SDC-2787 - Release Candidate 0 Integration and Test
Stories
SDC-1952 - 9 artifacts 9 definition is missing in the exported csar 9 s VDU node
SDC-2095 - R6 5G U/C SDC: PM Dictionary GUI Display from PNF Onboarded Package
SDC-2138 - SDC docker runs as non root
SDC-2216 - Security improvements
SDC-2382 - Introduce a new category for the 3rd party Service
SDC-2383 - Expose the API for service creation as an External API
SDC-2385 - Introduce property mapping rules to define parent-child mapping for properties added in service definition
SDC-2393 - CBA association enhancement in PNFD to support API decision
SDC-2394 - Support custom PNF workflow design
SDC-2405 - Add workflow-designer secure frontend-backend communication
SDC-2417 - SDC must work in HTTPS mode in all interfaces
SDC-2456 - Optimize usage of repositories
SDC-2559 - Need a getter method to return Input list from getEntity API
SDC-2561 - Transformation of customized Node Types for PNFD
SDC-2562 - Package Security - support signing of individual artifacts
SDC-2582 - CBA association enhancement in VNFD to support API decision
SDC-2584 - SDC-BE - create unique identifier for each execution of test cases.
SDC-2585 - Refresh option in the onboarding validation page
SDC-2589 - Onboard PNF software version
SDC-2590 - Upgrade To Cassandra 3
SDC-2629 - SDC UI button for user to request VTP to create & upload a OVP tar.gz file to OVP Portal
SDC-2631 - SDC Meta Data for CDS Integration
SDC-2638 - Upgrade Portal SDK to latest (2.6.0)
SDC-2639 - Align logging to Onap-ELS 2019.11
SDC-2640 - Handle onboard ALTER tables to support upgrade
SDC-2644 - Collapsing Roles - UI changes
SDC-2645 - From Certified to Distributed - BE
SDC-2650 - Perform Software Composition Analysis - Vulnerability tables
SDC-2651 - Tosca Parser - getVFModule - new API
SDC-2652 - Document current upgrade component Strategy
SDC-2656 - add securityUtil code to Onap
SDC-2685 - Upgrade Node & npm version
SDC-2686 - add common-app-logging module
SDC-2687 - Upgrade sdc-tosca version in main SDC pom
SDC-2691 - Enhance catalog FE proxy to be able to proxy to any defined plugin
SDC-2692 - Fix sonar issues
SDC-2696 - Release sdc-be-common 1.6.0
SDC-2699 - Increase SDC Code Coverage
SDC-2703 - Upgrade Node/npm/yarn version for WF-D
SDC-2724 - Catalog alignment
SDC-2732 - fix CSIT
SDC-2733 - remove unnecessary dependencies from pom
SDC-2758 - Backend configuration file runtime reload
SDC-2760 - Support import of custom node type name
SDC-2761 - Backend extensibility
Security Notes
Fixed Security Issues
[OJSI-102] - sdc-fe exposes plain text HTTP endpoint using port 30206
[OJSI-126] - sdc-wfd-fe exposes plain text HTTP endpoint using port 30256
[OJSI-127] - sdc-wfd-be exposes plain text HTTP endpoint using port 30257
Known Security Issues
[OJSI-90] - SDC exposes unprotected API for user creation
[OJSI-94] - sdc-wfd-fe allows to impersonate any user by setting USER_ID
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
N/A
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.5.2
- Release Date:
2019-10-10
SDC SDKs Versions
sdc-distribution-client
- Version:
1.4.0
sdc-tosca
- Version:
1.6.2
Release Purpose
Epics
[SDC-1425] - SDC documentation improvement
[SDC-2461] - El Alto release planning milestone
[SDC-2487] - Functionality and API Freeze
[SDC-2523] - Code Freeze
[SDC-2566] - Release Candidate 0 Integration and Test
Stories
[SDC-1894] - Enable Certificate for SDC
[SDC-1961] - Purge APIs for Service and Resource
[SDC-2072] - Create VSP from VNF csar
[SDC-2101] - RestConf - Policy model support
[SDC-2102] - DFC - Policy model support
[SDC-2104] - PM-Mapper Policy Model support
[SDC-2142] - Enhance Service/VF/PNF to support Req & Cap
[SDC-2166] - Enable transport level encryption on all interfaces and the option to turn it off
[SDC-2294] - Support Capability Properties
[SDC-2296] - Upgrade SDC from Titan to Janus Graph
[SDC-2313] - Fix Service Proxy Node Type
[SDC-2359] - Fix Service Proxy Node Template
[SDC-2397] - SDC Constructor injection - better practice
[SDC-2416] - Embed AAF generated certificate in SDC
[SDC-2419] - Migrate all SDC projects to O-Parent
[SDC-2475] - Package Handling - Validate PM Dictionary and VES Events YAML Files in SOL004 package
[SDC-2478] - Update SDC versions
[SDC-2509] - Descriptor Handling - Model-driven mapping from SOL001 to internal model
[SDC-2510] - Package Handling - Store the original onboarded package, whether it’s a CSAR or a ZIP
[SDC-2540] - Package Handling - Fix artifacts references in main TOSCA descriptor while converting packages
[SDC-2560] - Update SDC versions
Security Notes
Fixed Security Issues
[OJSI-31] - Unsecured Swagger UI Interface in sdc-wfd-be
CVE-2019-12115 [OJSI-76] - demo-sdc-sdc-be exposes JDWP on port 4000 which allows for arbitrary code execution
CVE-2019-12116 [OJSI-77] - demo-sdc-sdc-fe exposes JDWP on port 6000 which allows for arbitrary code execution
CVE-2019-12117 [OJSI-78] - demo-sdc-sdc-onboarding-be exposes JDWP on port 4001 which allows for arbitrary code execution
CVE-2019-12118 [OJSI-79] - demo-sdc-sdc-wfd-be exposes JDWP on port 7001 which allows for arbitrary code execution
CVE-2019-12119 [OJSI-80] - demo-sdc-sdc-wfd-fe exposes JDWP on port 7000 which allows for arbitrary code execution
Known Security Issues
[OJSI-90] - SDC exposes unprotected API for user creation
[OJSI-94] - sdc-wfd-fe allows to impersonate any user by setting USER_ID
[OJSI-126] - In default deployment SDC (sdc-wfd-fe) exposes HTTP port 30256 outside of cluster.
[OJSI-127] - In default deployment SDC (sdc-wfd-be) exposes HTTP port 30257 outside of cluster.
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
[SDC-2541] - Custom WF not present in the CSAR package
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.4.1
- Release Date:
2019-06-06
SDC SDKs Versions
sdc-distribution-client
- Version:
1.3.0
sdc-tosca
- Version:
1.5.1
Release Purpose
New Features
- The main goal of the Dublin release was to:
Support PNF onboarding
SOL 001 v2.5.1 support
VSP compliance check feature
SDC and CDS integration
improve code coverage of the SDC code.
Epics
[SDC-1937] - Service Workflow - Assigned Workflow and Complex Types in Operation
[SDC-1956] - Add VSP Compliance Check feature
[SDC-1970] - Supporting PNF package onboarding
[SDC-1987] - Add dependent child service to service
[SDC-1988] - Add property to service
[SDC-1990] - Service Consumption
[SDC-1991] - Service Consumption - Input Data and Validations
[SDC-1992] - Service dependency - Rainy Day Validations
[SDC-1993] - Service dependency - Input Data and Validations
[SDC-1994] - Add property to VNF and PNF
[SDC-1999] - Operation interfaces
[SDC-2170] - updating the VNFD (SOL001) type based on SOL001 v2.5.1
Stories
[SDC-1000] - SDC Parser is throwing exception on critical issues
[SDC-1392] - Write Unit test for Compile-Helper-Plugin
[SDC-1399] - Change the plugins load to be parallel
[SDC-1426] - catalog documentation
[SDC-1427] - Onboarding documentation
[SDC-1429] - WORKFLOW documentation
[SDC-1489] - multiple cloud technology artifact support
[SDC-1568] - Health check integration for designers
[SDC-1569] - Enable a secuirity solution for the designers in sdc TBD
[SDC-1743] - Add support for work flow deployment on heat
[SDC-1744] - Add support for different locations of Main service template WIP
[SDC-1925] - Resolve SONAR issues in SDC BE
[SDC-1941] - SDC refactoring and code smells
[SDC-1946] - Code quality improvements
[SDC-1948] - Solve BE issues from sonar
[SDC-1950] - asdctool code quality improvements
[SDC-1973] - Create VSP package from PNF onboarding package
[SDC-1974] - Supporting PNF manifest file in the onboarding package
[SDC-1975] - Design time catalog to associate artifacts with PNF (Test)
[SDC-1976] - Supporting PNFD (SOL001) mapping to AID model
[SDC-1977] - Display VSP Resource Type (VF/PNF) in Import VSP UI
[SDC-1978] - Ensure descriptor name matches name used in generated TOSCA.meta in VSP
[SDC-1979] - Allowing the dedicated artifact folder with Entry-point in TOSCA.meta
[SDC-1980] - Supporting onboarding packaging security
[SDC-2022] - Allow custom plugins in SDC
[SDC-2067] - SDC and CDS Integration to enable E2E Automation
[SDC-2085] - Outputs on operations - Operation screen BE
[SDC-2090] - update the normative type of onboarding DM
[SDC-2094] - R4 5G U/C SDC: FM Meta Data GUI Display from PNF Onboarded Package
[SDC-2108] - Import VSP and Create PNF internal csar
[SDC-2109] - Adding additional artifacts
[SDC-2110] - Add PNF manually (without using vsp)
[SDC-2112] - Add a copy of the onboarded package under artifact folder
[SDC-2113] - copy the on boarding artifacts into the right SDC artifact type
[SDC-2136] - HTTPS support on workflow application backend
[SDC-2168] - M2/3/4 findings
[SDC-2194] - Enhance SDC Workflow designer BE to connect to secure Cassandra
[SDC-2199] - Migrate SDC to use Common Cassandra Cluster
[SDC-2226] - Create Internal BE API for artifact Upload
[SDC-2233] - Support workflow artifact in Service Distribution Notification
[SDC-2280] - achieve CII Badging passing level for Dublin
[SDC-2313] - Fix Service Proxy Node Type
Known Issues
Security Notes
Fixed Security Issues
Known Security Issues
[OJSI-31] - Unsecured Swagger UI Interface in sdc-wfd-be
CVE-2019-12115 [OJSI-76] - demo-sdc-sdc-be exposes JDWP on port 4000 which allows for arbitrary code execution
CVE-2019-12116 [OJSI-77] - demo-sdc-sdc-fe exposes JDWP on port 6000 which allows for arbitrary code execution
CVE-2019-12117 [OJSI-78] - demo-sdc-sdc-onboarding-be exposes JDWP on port 4001 which allows for arbitrary code execution
CVE-2019-12118 [OJSI-79] - demo-sdc-sdc-wfd-be exposes JDWP on port 7001 which allows for arbitrary code execution
CVE-2019-12119 [OJSI-80] - demo-sdc-sdc-wfd-fe exposes JDWP on port 7000 which allows for arbitrary code execution
[OJSI-90] - SDC exposes unprotected API for user creation
[OJSI-94] - sdc-wfd-fe allows to impersonate any user by setting USER_ID
[OJSI-101] - In default deployment SDC (sdc-be) exposes HTTP port 30205 outside of cluster.
[OJSI-102] - In default deployment SDC (sdc-fe) exposes HTTP port 30206 outside of cluster.
[OJSI-126] - In default deployment SDC (sdc-wfd-fe) exposes HTTP port 30256 outside of cluster.
[OJSI-127] - In default deployment SDC (sdc-wfd-be) exposes HTTP port 30257 outside of cluster.
[OJSI-132] - In default deployment SDC (sdc-dcae-fe) exposes HTTP port 30263 outside of cluster.
[OJSI-133] - In default deployment SDC (sdc-dcae-dt) exposes HTTP port 30265 outside of cluster.
Known Vulnerabilities in Used Modules
Quick Links:
Known Issues
N/A
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.3.7
- Release Date:
2019-01-31
SDC SDKs Versions
- sdc-distribution-client
- Version:
1.3.0
- sdc-tosca
- Version:
1.4.63
Release Purpose
The Casablanca Maintenance release was focused on fixing high priority defects discovered in Casablanca release.
Bugs
[SDC-1447] - [SDC] SDC create csar with many warnnings
[SDC-1955] - SDC distribution failed
[SDC-1958] - SDC Parser can not be used for CCVPN Templates
[SDC-1971] - Change version failure
[SDC-2014] - Documentation figure not readable
[SDC-2053] - SDC fails healthcheck
[SDC-2077] - SDC-BE and SDC-FE missing log files
Version: 1.3.5
- Release Date:
2018-11-30
SDC SDKs Versions
- sdc-distribution-client
- Version:
1.3.0
- sdc-tosca
- Version:
1.4.7
Release Purpose
The Casablanca release was focused on improving platform stability and resiliency and introducing new platform capabilities.
New Features
The Casablanca release is the third release of the Service Design and Creation (SDC).
- The main goal of the Casablanca release was to:
Improve code coverage of the SDC code.
Complete E2E workflow design and distribution.
Finalize DCAE-DS and integrate it with OOM
Support HPA
Enhance security
Security Notes
SDC code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, items that remain open have been assessed for risk and determined to be false positive. The SDC open Critical security vulnerabilities and their risk assessment have been documented as part of the project.
Quick Links:
Known Issues
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.2.0
- Release Date:
2018-06-07
SDC SDKs Versions
sdc-distribution-client
- Version:
1.3.0
sdc-tosca
- Version:
1.3.5
Release Purpose
The Beijing release was focused on improving platform stability and resiliency.
New Features
The Beijing release is the second release of the Service Design and Creation (SDC).
- The main goal of the Beijing release was to:
Enhance Platform maturity by improving SDC maturity matrix see Wiki.
SDC made improvements to the deployment to allow an easy and stable integration with OOM.
SDC change the docker structure to allow easier and the beginning of breaking the application into Micro Services.
SDC introduced a generic framework to allow different Modeling plugins to be easily integrated with SDC.
improve code coverage of the SDC code.
SDC introduced two new experimental projects the DCAE-D and WorkFlow which enhance the modeling capabilities of SDC.
DCAE-D information is available here: DCAE-DS Workflow information is available in readthedocs
Epics
[SDC-77] - Designer issues
[SDC-126] - Holmes Designer
[SDC-180] - This epic is for modeling placements and homing rules for VNF placements
[SDC-181] - This epic is for modeling relationship in TOSCA between nodes (VNFs)
[SDC-220] - integrate VNF onboarding using VNF-SDK
[SDC-326] - Support work flows in SDC
[SDC-383] - sdc will enhance our testing to provide better testing coverage
[SDC-647] - process build and deploy process optimization
[SDC-659] - SDC deploy and build optimization
[SDC-731] - sdc designer integration
[SDC-778] - Non-Functional requirements - Resiliency
[SDC-812] - Non-Functional requirements - Performance
[SDC-813] - Non-Functional requirements - Stability
[SDC-814] - Tenant Isolation - Context Distribution - [e1802 - TDP Epic 316628]
[SDC-815] - Tenant Isolation - Context Definition - [e1802 - TDP Epic 316484]
[SDC-816] - SDC Pause Instantiation - [e1802 - TDP Epic 330782]
[SDC-817] - Service Model Design to support Complex Services
[SDC-819] - Change namespace from openECOMP to org.onap
[SDC-820] - SDC Enhance Connect Behavior - [1802 TDP Epic 332501]
[SDC-823] - Non-Functional requirements - Security
[SDC-825] - Non-Functional requirements - Manageability
[SDC-826] - Non-Functional requirements - Usability
[SDC-828] - OOM integration
[SDC-831] - Support life cycle artifacts in model
[SDC-936] - SDC parser configuration improvements
[SDC-976] - Manual Scale Out use case support
[SDC-978] - Adapter of WF Designer for SDC
[SDC-980] - Extend Activities for Workflow Designer
[SDC-985] - Hardware Platform Enablement(HPA) modeling design
[SDC-986] - Hardware Platform Enablement(HPA) use case support
[SDC-1053] - PNF use case support
Stories
[SDC-10] - Deploy a SDC high availability environment
[SDC-51] - vCPE_UC: Add Close-Loop (CL) Blueprint Monitoring-Template (MT) to a VNF-I
[SDC-73] - Import WorkFlow
[SDC-82] - support adding artifact type for node template
[SDC-118] - support sub process
[SDC-124] - support insert a sub process which is already defined
[SDC-143] - create local DEV environment based on onap vagrant
[SDC-242] - TDP 325252 - resolve get_input values
[SDC-243] - TDP 319197 - tosca parser port mirroring
[SDC-259] - TDP 316633 - TenantIsolation ContextDistribution
[SDC-277] - docker enhancements
[SDC-343] - Fixing SONAR Qube Issues
[SDC-364] - workflow designer backend init code
[SDC-365] - support load data from config file
[SDC-366] - convert workflow json to bpmn file
[SDC-384] - Add UI testing capabilities to the SDC sanity docker
[SDC-398] - write data to workflow template
[SDC-403] - add unit test for config class
[SDC-404] - add unit test for bpmn file convert
[SDC-408] - integrate back end service
[SDC-572] - HEAT Validations Error codes
[SDC-586] - Support and align CSAR’s for VOLTE
[SDC-608] - CSIT and sanity stabilization
[SDC-615] - add new artifact type to SDC
[SDC-619] - ONAP support
[SDC-627] - Collaboration - BE - Healing - new healing table
[SDC-650] - review docker memory assignment
[SDC-652] - K8/OOM adoption - Research
[SDC-655] - Fixing update HEAT
[SDC-660] - docker image size optimization
[SDC-679] - Generate bpmn files that can be executed on activity engine
[SDC-683] - sync release-1.1-0 with master
[SDC-685] - create unit tests for jtosca
[SDC-686] - code sync
[SDC-687] - sdc designer integration part 1
[SDC-712] - import normative superation
[SDC-713] - amsterdam branch
[SDC-728] - sdc designer integration part 2
[SDC-732] - sdc designer integration part 3
[SDC-740] - converter support IntermediateCatchEvent
[SDC-741] - support script task
[SDC-742] - converter supports gateway elements
[SDC-744] - TDP 344203 - Distribution-client Tenant Isolation
[SDC-745] - Converter support service task
[SDC-746] - Converter supports error events
[SDC-747] - Converter support rest task
[SDC-749] - Update Global Types for TOSCA Import
[SDC-753] - converter code style change
[SDC-755] - ONAP support
[SDC-781] - Create on boarding docker
[SDC-782] - OOM/HEAT integration
[SDC-788] - support Cassandra schema creation - work in progress
[SDC-821] - Sanity alignment after merge
[SDC-834] - Log management
[SDC-840] - sync 1802p to ONAP
[SDC-842] - down stream source
[SDC-863] - onboarding workspace - selecting item with 1 draft version skips versions page
[SDC-865] - refactor error codes in JTOSCA
[SDC-868] - UI - Remove restful-js and jquery dependency
[SDC-887] - UI -change variable names to catalog
[SDC-889] - remove plan name from plan definition
[SDC-891] - fix workflow is empty error
[SDC-899] - update microservice config info
[SDC-901] - add internationalization
[SDC-902] - add exclusive gateway
[SDC-903] - sdc designer integration part 5 bus and event resource and definition
[SDC-905] - add backend service
[SDC-906] - Deploy K8 on Vagrant
[SDC-907] - Cassandra OOM Alignment - update OOM deployment
[SDC-908] - ElasticSearch OOM Alignment
[SDC-910] - file encoding change
[SDC-911] - Cassandra OOM Alignment - create init docker
[SDC-912] - ES OOM alignment - create init docker
[SDC-913] - ES OOM Alignment - update OOM deployment
[SDC-914] - Cassandra OOM Alignment - Chef clean up
[SDC-915] - ES OOM Alignment - Chef clean up
[SDC-916] - BE OOM Alignment - create init docker
[SDC-917] - BE OOM alignment - update OOM deployment
[SDC-918] - BE OOM Alignment - Chef clean up
[SDC-919] - FE OOM alignment - update OOM deployment
[SDC-920] - FE OOM Alignment - Chef clean up
[SDC-921] - Kibana OOM Alignment - Chef clean up
[SDC-922] - Kibana OOM alignment - update OOM deployment
[SDC-923] - Cassandra OOM Alignment - create C* docker
[SDC-924] - ONAP support
[SDC-925] - ES OOM alignment - update ES docker
[SDC-950] - update JTOSCA packages
[SDC-951] - update SDC-TOSCA packages
[SDC-952] - update SDC-DISTRIBUTION-CLIENT packages
[SDC-953] - update SDC-DOCKER-BASE packages
[SDC-955] - configuration ovriding capabilities.
[SDC-957] - add ignore conformance level option
[SDC-969] - sync1802E to ONAP part 1
[SDC-972] - sdc designer integration part 4 design alignment
[SDC-977] - sdc designer integration part 6 bus implementation
[SDC-981] - Setup Micro-Service for WF Designer SDC Adapter
[SDC-987] - Update Dropwizard to the Latest Version
[SDC-990] - Add BDD Testing for onboarding
[SDC-994] - VirtualMachineInterface validation + flow tests
[SDC-995] - scan the TOSCA parser components code using fosologe
[SDC-997] - Import Jersey to implement the Rest APIs
[SDC-998] - VLAN tagging - Support pattern 1A
[SDC-999] - Initialize metaProperties in JTosca to enable SDC Parser to parse individual Yamls
[SDC-1002] - Import swagger to build up the api-doc
[SDC-1003] - sdc designer integration 7 error handling
[SDC-1011] - Package UI Resources for Integration with Server
[SDC-1012] - Modify Base Url of WF Designer for Integrating with SDC
[SDC-1015] - BE OOM Alignment - create server docker
[SDC-1018] - FE OOM Alignment - create server docker
[SDC-1019] - Kibana OOM Alignment - create server docker
[SDC-1020] - Sync SDC with OOM deployment
[SDC-1025] - Sync Integ to ONAP
[SDC-1036] - VLAN tagging - Support pattern 1C1
[SDC-1038] - Provide sample data for WF Designer Adapter
[SDC-1044] - Update JTosca dependency version in SDC-Tosca
[SDC-1055] - Update version in JTOSCA POM
[SDC-1061] - ONAP Support
[SDC-1073] - Support VFC Instance Group per networkrole
[SDC-1080] - Close the ‘DirectoryStream’ after its be used.
[SDC-1104] - Normative alignment
[SDC-1117] - achieve the 50% unit test coverage
[SDC-1130] - Display Extend Activities on WF Designer UI
[SDC-1131] - Use Extend Activities to Design Workflow and Save
[SDC-1164] - SDC designer Integration part 8 - Add promise logic to the SDC pub-sub notify
[SDC-1165] - SDC designer Integration part 9 - Create component that disables selected layouts
[SDC-1169] - CII passing badge
[SDC-1172] - reach 50% unit test coverage sdc workflow
[SDC-1174] - Support unified Tosca pattern 1C2 for vlan subinterface
[SDC-1197] - Enhance SDC Parser to support Interface and Operations
[SDC-1221] - Fix library CVEs in sdc-cassandra
[SDC-1310] - Fix additional library CVEs in sdc-docker-base
Bugs
[SDC-176] - Cannot access Kibana dashboard after logged into SDC as an Admin user.
[SDC-249] - Temporary files and directories not completely removed during execution
[SDC-250] - CSAR files are decompressed twice in the same thread
[SDC-251] - TOSCA does not attempt to delete decompressed folders in certain conditions
[SDC-265] - Some important information lost while upload a VF’s TOSCA model using REST API in SDC 1.1
[SDC-272] - The problem in the substitution_mappings of a service.
[SDC-291] - Resources not closed in onboarding code in multiple places
[SDC-311] - nfc_naming_code and nfc_function at VSP level not populated at VF level
[SDC-312] - Can’t assign a value for a capability’s property of a node.
[SDC-314] - Can’t assign a value for a relationship’s property.
[SDC-328] - The default values of the properties of the ‘org.openecomp.resource.vl.extVL’ exported are incorrect.
[SDC-341] - Deploy Error on Service Distribution
[SDC-346] - Very long descriptions are not displayed correctly
[SDC-386] - add license header for class
[SDC-393] - Build stuck at org.openecomp.sdc.tosca.services.impl.ToscaAnalyzerServiceImplTest
[SDC-402] - TDP 335705 - get_input of list of wrong format
[SDC-412] - fix file already exists error
[SDC-425] - change nested compute node type prefix
[SDC-427] - fix group members ids
[SDC-434] - Healing should be added to the resubmitAll utility REST
[SDC-438] - Unable to Access SDC from Portal
[SDC-440] - When creating a new VSP “HSS_FE_test_100617”, HEAT validation failed with 2 errors
[SDC-458] - Onboard questionaire-component missing enum AIC
[SDC-459] - Month navigation does not work in firefox
[SDC-466] - Submit failed for existing VSP “Nimbus 3.1 PCRF 0717”
[SDC-468] - add check for flat node type, in case of port mirroring
[SDC-473] - healing does not work on submitted vsps
[SDC-479] - Fix the sdc vagrant-onap to work as a local deployment vagrant
[SDC-480] - fix failing healers during resubmit
[SDC-484] - Deleting a connection between VNF resources causes 500 error code on SDC Composition GUI
[SDC-485] - Limits - issue in display
[SDC-488] - parse error message
[SDC-489] - error when moving to previous version using the version drop down
[SDC-490] - Onboarding undo checkout wrong implementation
[SDC-492] - need to add support for dynamic port
[SDC-494] - Readonly does not work for VLM limits
[SDC-526] - need to enable upload of files with zip or csar extensions in uppercase
[SDC-529] - VendorSoftwareProductManager->healAndAdvanceFinalVersion heal Submit VSPs
[SDC-534] - Fix swagger basepath
[SDC-535] - Incorrect UI files information during onboarding.
[SDC-540] - confirmation msg for delete FG doesn’t appear
[SDC-541] - delete confirmation modals - styles alignment
[SDC-549] - add property to fixed_ips global type
[SDC-550] - Creating users using the webseal-simulator returns 404
[SDC-552] - VLM overview - refactor of edit description input
[SDC-554] - zip with duplicate ids in different files is not throwing an exception
[SDC-555] - Unable to populate network_resource table
[SDC-559] - update component prefix
[SDC-565] - Extension loading is not working when the module is being used as a dependent library.
[SDC-566] - YAML syntax errors are not being sent in Validation Issue List against error code JE1002
[SDC-567] - Recursive Imports are not needed when individual Yamls are being validated
[SDC-568] - NodeType/EntityType capabilities import failing with Class Cast Exception
[SDC-573] - Sev 1 - Property assignments on SDC UI is not grouped by VM/VNFC type(s), instead it lists ALL VMs/VNFCs.
[SDC-574] - ignore node templates that point to substitution ST without topology template
[SDC-576] - support dynamic ports
[SDC-578] - Revert a checked out version causes data loss
[SDC-580] - Error in Jetty logs
[SDC-581] - Error in Jetty logs
[SDC-583] - sdc/sdc-docker-base fails to build
[SDC-637] - VLM Overview - Connection list/ Orphans list - tabs behavior
[SDC-639] - Unexpected response while creating VSP with onboarding method as NULL/Invalid
[SDC-640] - update fabric8 docker-maven-plugin version
[SDC-641] - hardcoded version for restful-js
[SDC-642] - sdc build is failing on onboarding UI
[SDC-646] - can’t convert parameters when importing tosca
[SDC-653] - implement forwarder capability
[SDC-657] - Error message is not reported to calling functions
[SDC-661] - need to throw an exception in case that substitution mappings is not correct
[SDC-664] - JTOSCA Library is missing case insensitive check for status attribute value : “supported” vs “SUPPORTED”
[SDC-666] - Library Import feature is ignoring multiple imports in a file and loading only the last one in sequence
[SDC-667] - Validate and Create capabilities APIs are throwing class cast exception
[SDC-668] - Imports loading is running in to Stack overflow error for CSARs generated via SDC on-boarding process
[SDC-669] - Add SDC Global Types as a dependency in JTOSCA library implementation
[SDC-670] - fix nova validator
[SDC-671] - changing replication factory
[SDC-682] - Tosca parser fails to parse csar with get_attributes
[SDC-690] - SDC portal does not come up on latest master of ONAP demo
[SDC-692] - Update VSP by resetting the VLM, and uploading new Heat. Could not submit
[SDC-693] - throw yaml exception when retrieving service templates
[SDC-694] - fix NPE in when extracting components
[SDC-698] - Webseal simulator Docker image cannot be built on Linux
[SDC-700] - Wrong check for file extension in HeatValidator
[SDC-703] - Duplicate logging frameworks in SDC onboarding repository
[SDC-704] - SDC External API : Swagger Errors
[SDC-705] - SDC Sanity Docker exits
[SDC-715] - SDC-CS docker container sporadically gets errors during startup
[SDC-716] - Make SDC splash screen statefull - only show once for repeated distribution flows
[SDC-737] - catalog-be unit tests fail on different build systems
[SDC-739] - CD healthcheck of SDC failing periodically 35% of the time (since Feb 75%)
[SDC-748] - Build failure due to translator core tests getting stuck
[SDC-765] - Error 500 when trying to edit a connection
[SDC-770] - SDC openecomp-be build failure on missing build-tools-1.2.0-SNAPSHOT.jar
[SDC-773] - SDC Import Export Executors should be supported.
[SDC-774] - fix parameter value check in vm grouping
[SDC-776] - Sonar coverage drop onboarding
[SDC-777] - sonar scan alignement
[SDC-792] - Add a private constructor to hide the implicit public one to ConfigurationUtils
[SDC-811] - Assign Mib to Component
[SDC-830] - Broken mapping of ChoiceOrOther because of missing default constructor
[SDC-835] - Sonar issue fix - remove unused exception handling.
[SDC-843] - response code is not validate in C* chef
[SDC-861] - Error while importing VF (CSAR onboarded)
[SDC-872] - Collaboration : Dependencies are getting deleted after same HEAT is uploaded to VSP
[SDC-874] - fix upload csar unit tests
[SDC-876] - Null pointer exception while creating Deployment flavor
[SDC-879] - Improve ConfigurationUtils class
[SDC-881] - Toggle support for UI
[SDC-886] - ZipOutputStream need to be closed
[SDC-888] - sonar fix - Stack
[SDC-892] - Fail to Export VLM
[SDC-894] - Upgrade React version to 15.6
[SDC-896] - Lifecycle Operations artifact is not reflecting in CSAR for VSP Processes Type is Lifecycle_Operations
[SDC-898] - Update the snapshot in test-config for v1.1.1-SNAPSHOT
[SDC-904] - ToscaFileOutputServiceCsarImplTest has tests with shared state
[SDC-909] - Unit Test of sdc-workflow-designer-server project failed.
[SDC-931] - Contributor can also submit fix
[SDC-932] - Dropdown text is cut off
[SDC-935] - Incorrect FG version “0.0” appears in “vf-license-model.xml” file in csar
[SDC-940] - NPE during submit of VSP
[SDC-941] - Fix zusammen Import
[SDC-943] - React version downgrade
[SDC-944] - dox-sequence-diagram-ui render fix
[SDC-963] - Fix broken npm packages
[SDC-989] - SDC healthcheck fails with message DCAE is Down
[SDC-992] - SDC-FE container fails to start because of missing chef parameters
[SDC-993] - SDC simulator compilation issues
[SDC-996] - SRIOV - add annotations
[SDC-1010] - Extending the value list of the RAM memory in the compute
[SDC-1016] - ASDC is not associating get_file with a VF module, causing MSO not deploy get_file ( E2E - 405397, IST - 404072
[SDC-1050] - Allow set Toggle feature ON on Flow - Test
[SDC-1051] - Catalog Profile Is Broken
[SDC-1054] - SDC-Cassandra fails in starting up on Heat
[SDC-1062] - Failure to submit NFoD when backup NIC is set (Onboarding manual flow)
[SDC-1064] - EP UUIDs in the vendor license model are not the same
[SDC-1071] - Create properly session context in zusammen tools
[SDC-1077] - Left panel buttons are enabled before creating a component
[SDC-1083] - Problem with radio button in onboarding UI
[SDC-1084] - ui heat validation tabs fixes
[SDC-1089] - fix build for onboarding
[SDC-1090] - Error-code POL5000 Internal Server Error.
[SDC-1092] - SDC-CS memory leak?
[SDC-1093] - Validation of VSP fails with error null
[SDC-1095] - Jenkins build does not execute unit tests.
[SDC-1096] - E2E Defect 430981 - ip_requirments for multiple ports with difference version
[SDC-1103] - onap normatives are imported always
[SDC-1105] - ForwardingPathBussinessLogicTest fails
[SDC-1107] - E2E Defect 427115 - Port Mirroring: Incorrect Interfaces list - not correct Port Type
[SDC-1108] - Scripts are using deprecated API
[SDC-1110] - Fix BDD Test failure
[SDC-1113] - E2E/Internal Defect - multiple ports (extCP) with wrong network-role
[SDC-1120] - Empty error message during Proceed To Validation
[SDC-1123] - The csar packages not passing onboarding during SDC sanity
[SDC-1124] - Bug - The csar packages not passing onboarding during SDC sanity
[SDC-1126] - Fixed merge issues regarding the plugins development
[SDC-1134] - healed version of VSP is missing a Description
[SDC-1143] - SDC docs: fix a typo in release notes
[SDC-1144] - Fix SDC Sonar bugs
[SDC-1145] - fix a SDC sonar NullPointer bug
[SDC-1146] - fix sonar NullPointer bugs in SDC
[SDC-1150] - Json Serialization of collections should hide empty attribute.
[SDC-1184] - Unable to create VF after creating component dependency in VSP due to error
[SDC-1188] - User Permission items
[SDC-1190] - Java proxy classname in audit logs instead of resource name
[SDC-1192] - ValidationVsp Cannot support multiple sessions
[SDC-1200] - SDC tab shows “HTTP Error 305” after login and accessing from the portal
[SDC-1204] - maven clean leaves files in target
[SDC-1206] - Create VF fails with 404 error message for subinterface_indicator property
[SDC-1207] - Distribution cannot create “UEB keys”
[SDC-1208] - Missing heat script for deploying sdc-workflow designer
[SDC-1209] - Missing uuid & operationId while navigate from sdc to wf-designer
[SDC-1210] - Format Issue in the Example Resource File
[SDC-1211] - Issues from Nexus-IQ
[SDC-1212] - Issues of the BPMN Converter
[SDC-1214] - Fix for healing of vlan tagging and annotations
[SDC-1215] - Errors in Retrieving Data From SDC
[SDC-1222] - base_sdc-python docker image build failure
[SDC-1234] - Vsp certified version which gets healed - remains draft
[SDC-1235] - Extend Service Task Miss ‘class’ Information
[SDC-1236] - Null Fields Should not Be Find in the Extend Servcie Task
[SDC-1237] - ui-styling-fixes
[SDC-1239] - ui-attachments-page-bug-fix
[SDC-1241] - SDC-BE pod started but it’s responding with 503 HTTP code
[SDC-1244] - Issue in healing zusammen MainTool
[SDC-1245] - jenkins release jobs are failing
[SDC-1247] - SDC tester page hangs when clicking on Accept button
[SDC-1248] - support 5 digit port number
[SDC-1249] - not able to get the value fromProperty node
[SDC-1250] - Not Possible to accept “VF” in test
[SDC-1251] - Catalog UI - Plugin Loader doesn’t finish even though the plugin is already loaded
[SDC-1255] - Create VF fails for heats “vOTA123.zip” and “2016-144_vmstore_30_1702.zip”
[SDC-1256] - change the order of items in version page according to version number
[SDC-1261] - Unable to create more than one component dependency for VSP
[SDC-1262] - Add multiple servers for BDD testing
[SDC-1265] - SDC OOM Install elastic search in crashbackloop
[SDC-1267] - service submit for testing fails
[SDC-1268] - Submit for testing fails
[SDC-1269] - Error message appear twice
[SDC-1271] - Incorrect message when not choosing commit
[SDC-1273] - Unable to submit the NS to testing
[SDC-1274] - NFOD - Error when adding nic to component
[SDC-1275] - Logging core tests fail on Linux without hostname
[SDC-1279] - fix marge job
[SDC-1280] - ‘Model Schema’ is not available for any API in onboarding Swagger
[SDC-1281] - TOSCA Analyzer - null point exception
[SDC-1283] - Onboarding filter archive to active changes when pressing on workspace button
[SDC-1284] - fix catalog-be start
[SDC-1292] - Service Distribution is not happening under Operator role
[SDC-1293] - Facing issues while onboarding
[SDC-1295] - work flow release jobs are failing
[SDC-1303] - Certified activity spec status fetched as ‘draft’ right after attribute action not at all specified in the body
[SDC-1304] - Sorting version lists
[SDC-1305] - VSP Component Function input validation should be removed
[SDC-1308] - SDC fails health check in OOM deployment
[SDC-1309] - SDC fails health check on HEAT deployment
[SDC-1315] - Nested Dependency Issue
[SDC-1321] - Catalog Docker swagger not loading
[SDC-1328] - plug-in Iframe changes size on WINDOW_OUT event to composition page
[SDC-1329] - Warning in generated CSAR
[SDC-1332] - Enable VNF market place in sdc deployment
[SDC-1336] - SDC service category missing Network Service and E2E Service types
[SDC-1337] - Unexpected entry for interfaces + interface_types when no operation is defined
[SDC-1341] - SDC-DMAAP connection fails in multi-node cluster
[SDC-1347] - Wrap plug-ins API call in a promise to prevent loading issues of SDC UI
[SDC-1349] - Filter By vendor view - list of vsp is not closed
[SDC-1351] - Viewer can archive and restore
[SDC-1352] - SDC service design Properties Assignment page doesn’t function properly
[SDC-1354] - DCAE wrong jetty truststore file name
[SDC-1355] - Onborading permissions: change items’ owner works partially
[SDC-1356] - Wrong FE version name
[SDC-1366] - New version created based on old-unhealed version is not getting healed
[SDC-1376] - dcae_fe: Update context path to dcaed
[SDC-1382] - “Property Assignment” does not show the list of properties in OOM-deployed env
Security Notes
SDC code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, items that remain open have been assessed for risk and determined to be false positive. The SDC open Critical security vulnerabilities and their risk assessment have been documented as part of the project.
Quick Links:
Known Issues
[SDC-1380] - Missing Inheritance of VduCp in SDC distributed CSAR package
[SDC-1182] - SDC must no log serviceInstanceID and SERVICE_INSTANCE_ID
Upgrade Notes
N/A
Deprecation Notes
N/A
Other
N/A
Version: 1.1.0
- Release Date:
2017-11-15
SDC SDKs Versions
sdc-distribution-client
- Version:
1.1.32
sdc-tosca
- Version:
1.1.32
Release Purpose
The Amsterdam release is the first ONAP release. This release is focused on creating a merged architecture between the OpenECOMP and OpenO components. In addition, the release enhances the list of supported use cases to support the VoLTE and vCPE use cases.
New Features
Full and comprehensive VNF/Software Application(VF) and service design
Collaborative design
VNF/VF/SERVICE testing and certification
Distribution to ONAP
External API- for VNF/VF and service
Integration with BSS / Customer ordering.
Epics
[SDC-52] - SDC Opensource tech gaps
[SDC-53] - F28350/302244 [MVP] SDC 1710 - Increment Conformance Level
[SDC-54] - F36419/299760 [EPIC] - [MVP] SDC 1710 - Introduce a new Asset Type: PNF
[SDC-55] - F34117/305092 [EPIC] - [MVP] SDC 1710 - Enhance the CP
[SDC-56] - F36795/298830 [EPIC] - Provide a new Capability to Onboard non-HEAT VNFs based on a Questionnaire.
[SDC-57] - F36795/150093 [EPIC] - Enhance the VNF Model to include VNFC (VFC)
[SDC-58] - F36795/291353 EPIC] - [MVP] ASDC 1710 -TOSCA Parser - Stand alone
[SDC-59] - F36795/296771 [EPIC] - [MVP] SDC 1710 - TOSCA Parser - Support Complex Inputs
[SDC-60] - F36795/309319 EPIC] - Provide Additional Artifact type relevant for VNF Onboarding.
[SDC-61] - F36797/291413 [EPIC] - Enhance the VFC Model with additional Properties for VFC characterization
[SDC-62] - F36801/152151 [EPIC] - [MVP] ASDC 1707 - Tosca Schema files
[SDC-63] - F36257/292814 EPIC] - [MVP] SDC 1710 NFR - Enhance the System Health Check API
[SDC-64] - 306915 EPIC: [DevOps] - SSL Certificates separation of certificates for the deployment code
[SDC-66] - Workflow Designer
[SDC-71] - Workflow Management
[SDC-99] - Onbording Tosca VNF
[SDC-111] - swagger restful interface support
[SDC-116] - bpmn workflow modeler
[SDC-218] - support integration with VFC
[SDC-219] - Support for uCPE usecase
[SDC-287] - catalog support TOSCA CSAR import and distribution
[SDC-326] - Support work flows in SDC
Stories
[SDC-28] - TDP 291354 - JTOSCA repo initial commit
[SDC-67] - Workflow designer support json object type
[SDC-68] - Workflow designer support Swagger definition
[SDC-69] - WorkFlow Input Parameter Designer
[SDC-70] - WorkFlow Diagram Editor
[SDC-72] - Export WorkFlow
[SDC-74] - Delete WorkFlow
[SDC-75] - Modify WorkFlow
[SDC-76] - Add WorkFlow
[SDC-81] - Support VNF Package Specification
[SDC-92] - Topology Diagram Editor
[SDC-94] - Support Package draft
[SDC-95] - Support Package draft
[SDC-96] - Package multiple-versions support
[SDC-97] - CLI Package Validation and Packaging tool
[SDC-98] - Template management
[SDC-112] - support swagger specification interface definition
[SDC-113] - support set swagger info by swagger string
[SDC-114] - support set swagger info by url
[SDC-115] - support invoke restful interfaces defined by swagger specification
[SDC-117] - support bpmn workflow nodes(start, end, exclusive gateway, parallel gateway)
[SDC-119] - support set conditoin for gateway
[SDC-120] - support set input and output params for start event and end event
[SDC-121] - support quote output of previous workflow node for params
[SDC-122] - support quote input of start event for params
[SDC-161] - Remove MojoHaus Maven plug-in from pom file
[SDC-223] - Attachment display changes - UI
[SDC-224] - Tosca based onbaording enrichment - BE
[SDC-225] - Tosca validation in the attachment - BE
[SDC-226] - Support TOSCA CSAR attachments and validation in overview display - BE
[SDC-227] - Create new VSP, onboard from TOSCA file - BE
[SDC-228] - Tosca based onbaording enrichment - UI
[SDC-229] - Support TOSCA attachments in overview display - UI
[SDC-230] - Create new VSP, onboard from TOSCA file - UI
[SDC-231] - VNF package manifest file parsing - BE
[SDC-232] - Import TOSCA YAML CSAR - BE
[SDC-240] - WorkFlow Deisigner seed code
[SDC-248] - add verify job for workflow-designer in ci-manager
[SDC-255] - support add workflow node
[SDC-257] - save and query workflow definition data from catalog
[SDC-269] - support set microservice info
[SDC-276] - add dynamic dox scheme creation
[SDC-282] - support rest task node
[SDC-288] - Independent Versioning and Release Process
[SDC-294] - support bpmn timer element
[SDC-295] - delete node or connection by keyboard
[SDC-299] - Port mirroring
[SDC-306] - Replace Dockefiles with new baselines
[SDC-318] - Provide preset definitions for the enitity types standardized by the tosca-nfv specification.
[SDC-325] - Add “Network Service” and “E2E Service” to the predefined list of SDC categories.
[SDC-327] - add new artifact type to SDC
[SDC-329] - add categories to define SDC service
[SDC-339] - project package and create dockfile
[SDC-355] - support set value for branch node
[SDC-360] - Import New VF vCSCF
[SDC-370] - sdc documentation
[SDC-379] - Write functional test cases based on the functionality tested by sanity docker
[SDC-476] - add sonar branch to sdc project pom
[SDC-481] - update swagger
[SDC-498] - Support and align CSAR’s for VOLTE
[SDC-506] - Fill SDC read the docs sections
[SDC-517] - ONAP support
[SDC-521] - CSIT and sanity stabilization
[SDC-522] - sync 1710 defects into ONAP
[SDC-586] - Support and align CSAR’s for VOLTE
[SDC-594] - Fill SDC read the docs sections
[SDC-608] - CSIT and sanity stabilization
[SDC-615] - add new artifact type to SDC
[SDC-619] - ONAP support
[SDC-623] - Independent Versioning and Release Process
Bug Fixes
[SDC-160] - substitution mapping problem
[SDC-256] - modify workflow version in package.json
[SDC-263] - Exception is not showing the correct error
[SDC-270] - The node template name in the capability/requirement mapping map is not synchronized while modify a node template’ name.
[SDC-273] - Error: Internal Server Error. Please try again later
[SDC-280] - SDC healthcheck 500 on Rackspace deployment
[SDC-283] - jjb daily build fail
[SDC-289] - UI shows {length} and {maxLength} instead of actual limit values
[SDC-290] - discrepancy between the BE and FE on the “Create New License Agreement” Wizard
[SDC-296] - The default value of the VF input parameter is incorrect.
[SDC-297] - adjust textarea component style
[SDC-298] - The exported CSAR package of VFC lacks the definition of capability types standardized in the tosca-nfv specification.
[SDC-300] - GET query to metadata fails requested service not found
[SDC-307] - add sequence flow after refresh
[SDC-308] - save new position after node dragged
[SDC-309] - The exported CSAR package of VF lacks the definition of relationship types standardized in the tosca-nfv specification.
[SDC-310] - The exported CSAR package of VFC lacks the definition of data types standardized in the tosca-nfv specification.
[SDC-313] - requirement id is not correct
[SDC-323] - The scalar unit type value is in correctly created
[SDC-335] - swagger convert error
[SDC-337] - add missing global type
[SDC-338] - submit fails when uploading CSAR file
[SDC-344] - move jtosca version to main pom
[SDC-349] - add global type for import tosca
[SDC-351] - enable port mirroring
[SDC-353] - ONAP 1.1.0 SDC distributions failing in ORD - Add Software Product - Status 500
[SDC-363] - data convert error for tree node
[SDC-369] - invalid tag defined for docker
[SDC-375] - Onboarding build time
[SDC-381] - VLM update with EP/LKG - null error
[SDC-389] - Default value of properties do not match
[SDC-390] - fix docker file script error
[SDC-407] - VLM Refresh issue in orphans list on added agreement
[SDC-410] - Import normatives not running + Upgrade normatives not imports the onap types
[SDC-431] - Artifacts not generated for PNF Resource and hence not enabling model distribution to A&AI
[SDC-435] - sdc staging job is failing
[SDC-436] - sdc release stagging is failing on release 1.1.0
[SDC-441] - module-0 with version 1.0 not found in MSO Catalog DB
[SDC-443] - Fix SDC inter-DC overlay configuration model to support multiple networks
[SDC-444] - sdc-sdc-workflow-designer-master-stage-site-java Jenkins job failed
[SDC-448] - Onboarding of VNF Base_VLB failed
[SDC-452] - Workflow designer UI doesn’t show up
[SDC-454] - vMME CSAR from vendor failed SDC onboarding
[SDC-457] - artifacts are not copied to CSAR
[SDC-460] - vCSCF_aligned.csar Tosca.meta Entry definition file is missing
[SDC-461] - sidebar element background color changed
[SDC-471] - Predefined Network Service is missing in Generic Service Category
[SDC-474] - Issue in Onboarding converting occurrences in node_types section
[SDC-477] - SDC-base-docker jetty base failed to run apt-get
[SDC-483] - Zip file stored under vendor CSAR Artifacts directory is not included in CSAR created by SDC after VSP import
[SDC-491] - Artifact are incorrectly passed
[SDC-495] - artifacts are not packed correctly when uploading csar
[SDC-525] - Docker RUN chmod fails
[SDC-528] - SDC Backend/frontend not starting
[SDC-533] - Fail to get correct labels of requirements of nodes in service template
[SDC-537] - Backend doesn’t respond on port 8181 after heat deployment
[SDC-544] - Should not be validating message router certificate
[SDC-546] - Fix SCH to properly set “useHttpsWithDmaap”
[SDC-547] - SDC server error when registering for distribution
[SDC-548] - Distribution failing to SO in SDC client tosca parser null pointer
[SDC-561] - SDC version 1.1.32 is not available in nexus, blocking SO docker build
Known Issues
N/A
Upgrade Notes
Beijing backward compatibility to Amsterdam is not supported.
Deprecation Notes
N/A
Other
N/A
End of Release Notes
SDC SDKs
SDC SDKs List
The sdc project consists of a few additional sub projects listed below:
sdc-tosca
sdc-jtosca
sdc-distribution-client
SDC SDKs Explanations
SDC-TOSCA and SDC-DISTRIBUTION-CLIENT
DCAE-Designer
DCAE Designer is deprecated and replaced by DCAE-MOD, it is no longer deployed with SDC.
SDC Workflow Designer
README
The readme file for the workflow is available here
Documentation
Architecture and User guides are available here
SDC Helm Validator
General information
This application can be used to validate CNF Helm charts using a Helm Client. It allows to select Helm version, which will be used to execute validation.
More information could be found in project repository, see Project repository.
Offered API
Latest Open API model: OpenAPI.yaml
Validation
Application executes two types of validation:
Deployable (basic validation) - verify correct chart rendering.
Lint (optional) - verify syntax of charts, it can be turned on/off by request parameter.
Request parameters:
versionDesired - Helm Client version, which will be used to validation (list of supported versions can be received /versions endpoint), available formats:
Semantic version [X.Y.Z] e.g 3.5.2
Major version [vX] - uses latest of available major version, e.g: v3 uses latest 3.Y.Z version.
isLinted - turn on/off lint validation
isStrictLinted - turn on/off strict lint - if lint validation detects any warning, it marks chart as invalid.
Example usage
Supported versions (/versions) Request:
curl -X 'GET' \
'http://<host>:<port>/versions' \
-H 'accept: */*'
E.g:
curl -X 'GET' \
'http://localhost:8080/versions' \
-H 'accept: */*'
Sample response:
{"versions":
["3.5.2",
"3.4.1",
"3.3.4"]}
Validation (/validate)
Request:
curl -X 'POST' \
'http://<HOST>:<PORT>/validate' \
-H 'accept: application/json' \
-H 'Content-Type: multipart/form-data' \
-F 'versionDesired=<Helm client version>' \
-F 'file=@<path to file in .tgz format>;type=application/x-compressed-tar' \
-F 'isLinted=true' \
-F 'isStrictLinted=true'
E.g:
curl -X 'POST' \
'http://localhost:8080/validate' \
-H 'accept: application/json' \
-H 'Content-Type: multipart/form-data' \
-F 'versionDesired=3.5.2' \
-F 'file=@correct-apiVersion-v2.tgz;type=application/x-compressed-tar' \
-F 'isLinted=true' \
-F 'isStrictLinted=true'
Sample response:
{
"renderErrors": [],
"lintWarning": [],
"lintError": [],
"versionUsed": "3.5.2",
"valid": true,
"deployable": true
}
Usage within SDC
The Helm validator is triggered by the SDC onboarding BE in CNF package onboarding use-cases.
Project repository
User Administration
Initial User Creation
During initial install following users are created:
{
{
"userId": "demo",
"firstName": "demo",
"lastName": "demo",
"role": "ADMIN",
"email": "demo@openecomp.org"
},
{
"userId": "jh0003",
"firstName": "Jimmy",
"lastName": "Hendrix",
"role": "Admin",
"email": "jh0003@openecomp.org"
},
{
"userId": "jm0007",
"firstName": "Joni",
"lastName": "Mitchell",
"role": "TESTER",
"email": "jm0007@openecomp.org"
},
{
"userId": "cs0008",
"firstName": "Carlos",
"lastName": "Santana",
"role": "DESIGNER",
"email": "cs0008r@openecomp.org"
}
}
Default User
By default, SDC UI is launched with default user ‘cs0008’. To override see section Using Cookies to set User.