# ONAP SDC [](https://sonarcloud.io/summary/new_code?id=onap_sdc) [](https://sonarcloud.io/summary/new_code?id=onap_sdc) [](https://sonarcloud.io/summary/new_code?id=onap_sdc) [](https://sonarcloud.io/summary/new_code?id=onap_sdc) [](https://sonarcloud.io/summary/new_code?id=onap_sdc) [](https://sonarcloud.io/summary/new_code?id=onap_sdc) [](https://sonarcloud.io/summary/new_code?id=onap_sdc) [](https://sonarcloud.io/summary/new_code?id=onap_sdc) [](https://sonarcloud.io/summary/new_code?id=onap_sdc) [](https://sonarcloud.io/summary/new_code?id=onap_sdc) [](https://sonarcloud.io/summary/new_code?id=onap_sdc) ## Introduction SDC is the ONAP visual modeling and design tool. It creates internal metadata that describes assets used by all ONAP components, both at design time and run time. The SDC manages the content of a catalog and logical assemblies of selected catalog items to completely define how and when VNFs are realized in a target environment. A complete virtual assembly of specific catalog items, together with selected workflows and instance configuration data, completely defines how the deployment, activation, and life-cycle management of VNFs are accomplished. SDC manages four levels of assets: * Resource - A fundamental capability, implemented either entirely in software, or as software that interacts with a hardware device. Each Resource is a combination of one or more Virtual Function Components (VFCs), along with all the information necessary to instantiate, update, delete and manage the Resource. * Service - A well-formed object comprising one or more Resources. Service Designers create Services from Resources, and include all of the information about the Service needed to instantiate, update, delete and manage the Service. The key output of SDC is a set of models containing descriptions of asset capabilities and instructions to manage them. These models are stored in the SDC Master Reference Catalog for the entire enterprise to use. There are four major components of SDC: * Catalog - The repository for assets at the Resource, Service and Product levels. Assets are added to the Catalog using the Design Studio. * Design Studio - Used to create, modify and add Resource, Service and Product definitions in the Catalog. * Certification Studio - Available in a future release, is used to test new assets at all levels. It will be used for sandbox experimentation, and will include support for automated testing. * Distribution Studio - Used to deploy certified assets. From the Distribution studio, new Product assets, including their underlying Resources and Services, are deployed into lab environments for testing purposes, and into production after certification is complete. In a future release, there will be a way to export Product information to external Business Support Systems for customer ordering and billing. ## Git Configuration Note that if you're working on Windows, it's important to enable long paths for your machine; otherwise git won't be able to handle some files. In order to do so just add this section to your global git.config file under the `[core]` key
*.class
*.jar
*.war
*.log
*.log.zip
cps-ncmp-rest-stub/dependency-reduced-pom.xml
cps-application/archunit_store
cps-ri/src/main/resources/changelog/db/changes/data/dmi/generated-csv/generated_yang_resource_*
target/
log/
.idea/
.idea_modules/
*.iml
*.ipr
*.iws
*.DS_Store
.settings/
bin/
tmp/
.metadata
.classpath
.project
*.tmp
.checkstyle
/.tox
/__pycache__/*
/docs/docs/
/docs/.vscode/
/docs/_build/*
/test-tools/metrics-reports/
csit/env.properties
csit/archives/