diff options
Diffstat (limited to 'docs')
31 files changed, 207 insertions, 85 deletions
diff --git a/docs/guides/onap-developer/apiref/index.rst b/docs/guides/onap-developer/apiref/index.rst index db4cd6a51..f3ff54348 100644 --- a/docs/guides/onap-developer/apiref/index.rst +++ b/docs/guides/onap-developer/apiref/index.rst @@ -51,6 +51,7 @@ Common Services Modeling Parsers <../../../submodules/modeling/toscaparsers.git/docs/offeredapis.rst> MSB - Micro Services Bus <../../../submodules/msb/apigateway.git/docs/platform/offeredapis.rst> MultiVIM Cloud <../../../submodules/multicloud/framework.git/docs/MultiCloud-API-Specification-V1.rst> + Music <../../../submodules/music.git/docs/offeredapis.rst> SDK --- diff --git a/docs/guides/onap-developer/developing/index.rst b/docs/guides/onap-developer/developing/index.rst index b92541769..e335649ea 100644 --- a/docs/guides/onap-developer/developing/index.rst +++ b/docs/guides/onap-developer/developing/index.rst @@ -152,6 +152,15 @@ MultiVIM Cloud ../../../submodules/multicloud/framework.git/docs/index +Music +----- + +.. toctree:: + :maxdepth: 2 + :titlesonly: + + ../../../submodules/music.git/docs/index + Nokia SVNFM driver ------------------ diff --git a/docs/guides/onap-developer/settingup/fullonap.rst b/docs/guides/onap-developer/settingup/fullonap.rst index 0ae6646a0..d8529ef97 100644 --- a/docs/guides/onap-developer/settingup/fullonap.rst +++ b/docs/guides/onap-developer/settingup/fullonap.rst @@ -1,6 +1,7 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. This work is licensed under a Creative Commons Attribution 4.0 + International License. http://creativecommons.org/licenses/by/4.0 - Copyright 2017 ONAP + Copyright 2017-2018 ONAP .. contents:: @@ -18,13 +19,21 @@ **Context** =========== -ONAP may be deployed in different contexts depending on your requirements. The recommended installation for Amsterdam Release is currently based on OpenStack HEAT Template. +ONAP may be deployed in different contexts depending on your requirements. +The recommended installation for Beijng Release over virtual machines is based +on OpenStack HEAT Template. -Using the Amsterdam HEAT Template installer, ONAP can be deployed in a single tenant or multiple tenants. One tenant for all the components except DCAE, and another tenant dedicated to the DCAE components. +Using the Beijing HEAT Template installer, ONAP can be deployed in a single +tenant or multiple tenants. One tenant for all the components except DCAE, and +another tenant dedicated to the DCAE components. -The VNFs managed by ONAP may be deployed in different OpenStack tenants or based on top of VMware based infrastructure. For details, refer :ref:`to MultiCloud project<index-multicloud>`. +The VNFs managed by ONAP may be deployed in different OpenStack tenants or +based on top of VMware based infrastructure. For details, refer +:ref:`to MultiCloud project<index-multicloud>`. -The current installation is based on the single tenant deployment (all the ONAP components will be hosted in a unique tenant) with DCAE components deployed in High Availability mode. +The current installation is based on the single tenant deployment (all the ONAP +components will be hosted in a unique tenant) with DCAE components deployed in +High Availability mode. The installation requires some manual tasks to setup the DCAE components. @@ -35,9 +44,12 @@ The installation requires some manual tasks to setup the DCAE components. OpenStack --------- -ONAP installation is validated on `OpenStack Ocata <https://releases.openstack.org/ocata/>`_ or latter release. +ONAP installation is validated on +`OpenStack Ocata <https://releases.openstack.org/ocata/>`_ or latter release. -You can use various Cloud providers offering OpenStack based solutions. A list of available Cloud providers on the `OpenStack marketplace <https://www.openstack.org/marketplace/public-clouds/>`_. +You can use various Cloud providers offering OpenStack based solutions. +A list of available Cloud providers on the +`OpenStack marketplace <https://www.openstack.org/marketplace/public-clouds/>`_. You can use your private Cloud infrastructure. @@ -57,11 +69,13 @@ To deploy OpenStack, you can use various solutions: - `OpenStack Ocata installation guide <https://docs.openstack.org/ocata/install/>`_ .. tip:: - - Notice the documentation version mentioned in the URL, e.g. ocata/, pike/, latest/ ... - - The installation is pretty huge, some automated scripts have been created by the community: + - Notice the documentation version mentioned in the URL, e.g. ocata/, pike/, + latest/ ... + - The installation is pretty huge, some automated scripts have been created by + the community: - `OpenStack installation with Ansible (All openstack services) <https://docs.openstack.org/openstack-ansible/latest/>`_ - - `OpenStack Ocata installation scripts for testing environment (DO NOT install Heat, Designate and Cinder Volume services) <https://github.com/reachsrirams/openstack-scripts>`_ + - `OpenStack Ocata installation scripts for testing environment(DO NOT install Heat, Designate and Cinder Volume services) <https://github.com/reachsrirams/openstack-scripts>`_ Use the procedure below to deploy and configure *Designate* manually @@ -71,12 +85,14 @@ Use the procedure below to deploy and configure *Designate* manually install-designate.rst -The OpenStack infrastructure must enable internet access and you need to have an "External network" already configured properly. +The OpenStack infrastructure must enable internet access and you need to have +an "External network" already configured properly. The External network ID will have to be provided in the Heat environment file. ONAP components --------------- -The following table presents the mapping between the created VM and the ONAP components, and provides VM information (flavor and image): +The following table presents the mapping between the created VM and the ONAP +components, and provides VM information (flavor and image): =================== ================= ======= ============ VM name ONAP project(s) Flavor Image @@ -121,7 +137,8 @@ The ONAP installation requires the following footprint: - 3 TB Storage - 29 floating IP addresses -.. Note: The default flavor size may be optimized. The ONAP community is working to update flavors of basic ONAP installation. +.. Note: The default flavor size may be optimized. The ONAP community is + working to update flavors of basic ONAP installation. .. Note: You should also reserve some resources for the VNFs to be deployed. @@ -137,15 +154,21 @@ The following artifacts must be deployed on the OpenStack infrastructure: .. Note: The floating IP may be private IP. -.. Note: Basic flavors can reuse the default flavors as defined by `OpenStack <https://docs.openstack.org/horizon/latest/admin/manage-flavors.html>`_ - The xxlarge flavor should be configured using the following values: 12 vCPU, 64 GB RAM and 120 GB storage. +.. Note: Basic flavors can reuse the default flavors as defined by + OpenStack + <https://docs.openstack.org/horizon/latest/admin/manage-flavors.html>`_ + The xxlarge flavor should be configured using the following values: + 12 vCPU, 64 GB RAM and 120 GB storage. Security -------- -The default installation assumes that the Default security group is configured to enable full access between the ONAP components. -Depending on your environment, we may need to open some security groups (eg when using the portal from your desktop). +The default installation assumes that the Default security group is configured +to enable full access between the ONAP components. +Depending on your environment, we may need to open some security groups +(eg when using the portal from your desktop). -The list of various services and ports used can be found on the `ONAP wiki <https://wiki.onap.org/display/DW/ONAP+Services+List#ONAPServicesList-ONAPServices>`_. +The list of various services and ports used can be found on the +`ONAP wiki - ports <https://wiki.onap.org/display/DW/ONAP+Services+List#ONAPServicesList-ONAPServices>`_. **Deployment** ============== @@ -153,20 +176,23 @@ The list of various services and ports used can be found on the `ONAP wiki <http Source files ------------ -Both following files must be downloaded and configured to match your configuration: +Both following files must be downloaded and configured to match your +configuration: -- Template file: https://git.onap.org/demo/plain/heat/ONAP/onap_openstack.yaml -- Environment file: https://git.onap.org/demo/plain/heat/ONAP/onap_openstack.env +- Template file: + https://git.onap.org/demo/plain/heat/ONAP/onap_openstack.yaml +- Environment file: + https://git.onap.org/demo/plain/heat/ONAP/onap_openstack.env The environment file must be customized as described in the following sections. -.. Note Amsterdam release files +.. Note Beijing release files Description ----------- -The ONAP HEAT template spins up all the components expect the DCAE. The template, -onap_openstack.yaml, comes with an environment file, +The ONAP HEAT template spins up all the components expect the DCAE. +The template, onap_openstack.yaml, comes with an environment file, onap_openstack.env, in which all the default values are defined. The HEAT template is composed of two sections: (i) parameters, and (ii) @@ -179,7 +205,8 @@ file. The resource section contains the definition of: -- ONAP Private Management Network, which ONAP components use to communicate with each other and with VNFs +- ONAP Private Management Network, which ONAP components use to communicate + with each other and with VNFs - ONAP Virtual Machines (VMs) - Public/private key pair used to access ONAP VMs - Virtual interfaces towards the ONAP Private Management Network @@ -258,8 +285,8 @@ OpenStack-based cloud. :: - ubuntu_1404_image: PUT THE UBUNTU 14.04 IMAGE NAME HERE - ubuntu_1604_image: PUT THE UBUNTU 16.04 IMAGE NAME HERE + ubuntu_1404_image: PUT THE UBUNTU 14.04 IMAGE NAME HERE + ubuntu_1604_image: PUT THE UBUNTU 16.04 IMAGE NAME HERE flavor_small: PUT THE SMALL FLAVOR NAME HERE flavor_medium: PUT THE MEDIUM FLAVOR NAME HERE flavor_large: PUT THE LARGE FLAVOR NAME HERE @@ -284,38 +311,70 @@ following OpenStack CLI command: :: - dns_list: PUT THE ADDRESS OFTHE EXTERNAL DNS HERE (e.g. a comma-separated list of IP addresses in your /etc/resolv.conf in UNIX-based Operating Systems). THIS LIST MUST INCLUDE THE DNS SERVER THAT OFFERS DNS AS AS SERVICE (see DCAE section below for more details) - external_dns: PUT THE FIRST ADDRESS OF THE EXTERNAL DNS LIST HERE oam_network_cidr: 10.0.0.0/16 + dns_list: PUT THE ADDRESS OFTHE EXTERNAL DNS HERE (e.g. a comma-separated list + of IP addresses in your /etc/resolv.conf in UNIX-based Operating Systems). + THIS LIST MUST INCLUDE THE DNS SERVER THAT OFFERS DNS AS AS SERVICE + see DCAE section below for more details) + external_dns: PUT THE FIRST ADDRESS OF THE EXTERNAL DNS LIST HERE + oam_network_cidr: 10.0.0.0/16 dns_forwarder: PUT THE IP OF DNS FORWARDER FOR ONAP DEPLOYMENT'S OWN DNS SERVER oam_network_cidr: 10.0.0.0/16 -You can use the Google Public DNS 8.8.8.8 and 4.4.4.4 address or your internal DNS servers. - -ONAP installs a DNS server used to resolve IP addresses in the ONAP OAM private network. -ONAP Amsterdam Release also requires OpenStack Designate DNS support for the DCAE platform, so as to allow IP address discovery and communication among DCAE elements. -This is required because the ONAP HEAT template only installs the DCAE bootstrap container, which will in turn install the entire DCAE platform. -As such, at installation time, the IP addresses of the DCAE components are unknown. - -The DNS server that ONAP installs needs to be connected to the Designate DNS to allow communication between the DCAE elements and the other ONAP components. -To this end, dns\_list, external\_dns, and dns\_forwarder should all have the IP address of the Designate DNS. -These three parameters are redundant, but still required for Amsterdam Release. Originally, dns\_list and external\_dns were both used to circumvent some limitations of older OpenStack versions. -In future releases, the DNS settings and parameters in HEAT will be consolidated. +You can use the Google Public DNS 8.8.8.8 and 4.4.4.4 address or your internal +DNS servers. + +ONAP installs a DNS server used to resolve IP addresses in the ONAP OAM private +network. +ONAP Beijing Release also requires OpenStack Designate DNS support for the +DCAE platform, so as to allow IP address discovery and communication among +DCAE elements. +This is required because the ONAP HEAT template only installs the DCAE +bootstrap container, which will in turn install the entire DCAE platform. +As such, at installation time, the IP addresses of the DCAE components are +unknown. + +The DNS server that ONAP installs needs to be connected to the Designate DNS to +allow communication between the DCAE elements and the other ONAP components. +To this end, dns\_list, external\_dns, and dns\_forwarder should all have the +IP address of the Designate DNS. +These three parameters are redundant, but still required for Beijing Release. +Originally, dns\_list and external\_dns were both used to circumvent some +limitations of older OpenStack versions. +In future releases, the DNS settings and parameters in HEAT will be +consolidated. The Designate DNS is configured to access the external DNS. -As such, the ONAP DNS will forward to the Designate DNS the queries from ONAP components to the external world. +As such, the ONAP DNS will forward to the Designate DNS the queries from ONAP +components to the external world. The Designate DNS will then forward those queries to the external DNS. **DCAE Parameters** DCAE spins up ONAP's data collection and analytics system in two phases. -The first phase consists of launching a bootstrap VM that is specified in the ONAP HEAT template, as described above. This VM requires a number of deployment-specific configuration parameters being provided so that it can subsequently bring up the DCAE system. +The first phase consists of launching a bootstrap VM that is specified in the +ONAP HEAT template, as described above. This VM requires a number of +deployment-specific configuration parameters being provided so that it can +subsequently bring up the DCAE system. There are two groups of parameters: -- The first group relates to the launching of DCAE VMs, including parameters such as the keystone URL and additional VM image IDs/names. Hence these parameters need to be provided to DCAE. Note that although DCAE VMs will be launched in the same tenant as the rest of ONAP, because DCAE may use MultiCloud node as the agent for interfacing with the underlying cloud, it needs a separate keystone URL (which points to MultiCloud node instead of the underlying cloud). +- The first group relates to the launching of DCAE VMs, including parameters + such as the keystone URL and additional VM image IDs/names. Hence these + parameters need to be provided to DCAE. Note that although DCAE VMs will be + launched in the same tenant as the rest of ONAP, because DCAE may use + MultiCloud node as the agent for interfacing with the underlying cloud, it + needs a separate keystone URL (which points to MultiCloud node instead of + the underlying cloud). -- The second group of configuration parameters relate to DNS As A Service support (DNSaaS). DCAE requires DNSaaS for registering its VMs into organization-wide DNS service. For OpenStack, DNSaaS is provided by Designate, as mentioned above. Designate support can be provided via an integrated service endpoint listed under the service catalog of the OpenStack installation; or proxyed by the ONAP MultiCloud service. For the latter case, a number of parameters are needed to configure MultiCloud to use the correct Designate service. +- The second group of configuration parameters relate to DNS As A Service + support(DNSaaS). DCAE requires DNSaaS for registering its VMs into + organization-wide DNS service. For OpenStack, DNSaaS is provided by + Designate, as mentioned above. + Designate support can be provided via an integrated service endpoint listed + under the service catalog of the OpenStack installation; or proxyed by the + ONAP MultiCloud service. For the latter case, a number of parameters are + needed to configure MultiCloud to use the correct Designate service. These parameters are described below: @@ -345,8 +404,10 @@ or Command Line. - Login to Horizon URL with your personal credentials - Click "Stacks" from the "Orchestration" menu - Click "Launch Stack" -- Paste or manually upload the HEAT template file (onap_openstack.yaml) in the "Template Source" form -- Paste or manually upload the HEAT environment file (onap_openstack.env) in the "Environment Source" form +- Paste or manually upload the HEAT template file (onap_openstack.yaml) in the + "Template Source" form +- Paste or manually upload the HEAT environment file (onap_openstack.env) in + the "Environment Source" form - Click "Next" - Specify a name in the "Stack Name" form - Provide the password in the "Password" form - Click "Launch" @@ -379,15 +440,18 @@ or Command Line. :: # Old HEAT client - heat stack-create STACK_NAME -f PATH_TO_HEAT_TEMPLATE(YAML FILE) -e PATH_TO_ENV_FILE + heat stack-create STACK_NAME -f PATH_TO_HEAT_TEMPLATE(YAML FILE) + -e PATH_TO_ENV_FILE OR # New OpenStack client - openstack stack create -t PATH_TO_HEAT_TEMPLATE(YAML FILE) -e PATH_TO_ENV_FILE STACK_NAME + openstack stack create -t PATH_TO_HEAT_TEMPLATE(YAML FILE) + -e PATH_TO_ENV_FILE STACK_NAME -.. Note The HEAT template deployment may take time (up to one hour) depending on your hardware environment. +.. Note The HEAT template deployment may take time (up to one hour) + depending on your hardware environment. Deploy DCAE ----------- @@ -398,16 +462,23 @@ The HEAT template deployed the onap-dcae-bootstrap virtual machine. Test the installation --------------------- -Every ONAP component offers a HealthCheck REST API. The Robot Virtual Machine (*onap-robot*) can be used to test that every components run smoothly. +Every ONAP component offers a HealthCheck REST API. The Robot Virtual Machine +(*onap-robot*) can be used to test that every components run smoothly. Run the following command to perform the HealthCheck: .. code-block:: bash - docker exec -it openecompete_container /var/opt/OpenECOMP_ETE/runTags.sh -i health h -d ./html -V /share/config/integration_robot_properties.py -V /share/config/integration_preload_parameters.py -V /share/config/vm_properties.py + docker exec -it openecompete_container /var/opt/OpenECOMP_ETE/runTags.sh + -i health + -d ./html + -V /share/config/integration_robot_properties.py + -V /share/config/integration_preload_parameters.py + -V /share/config/vm_properties.py This test suite will execute 30 tests towards the various ONAP components. -After the installation, it is possible to deploy the various use-cases described in `ONAP wiki <https://wiki.onap.org/display/DW/Running+the+ONAP+Demos>`_. +After the installation, it is possible to deploy the various use-cases +described in `ONAP wiki - demos <https://wiki.onap.org/display/DW/Running+the+ONAP+Demos>`_. Detect problems --------------- @@ -415,10 +486,12 @@ If all the tests are not OK, many causes are possible. Here is a simple procedure to detect where the problem occurs: * Check the OpenStack Virtual Machine logs -* Connect to the Virtual Machine and check that the various containers are running. +* Connect to the Virtual Machine and check that the various containers are + running. -The list of containers are described on the `ONAP wiki <https://wiki.onap.org/display/DW/ONAP+Services+List#ONAPServicesList-ONAPServices>`_ -. In case some containers are missing, check the Docker logs using the following command: +The list of containers are described on the `ONAP wiki - containers <https://wiki.onap.org/display/DW/ONAP+Services+List#ONAPServicesList-ONAPServices>`_. +In case some containers are missing, check the Docker logs using the following +command: .. code-block:: bash @@ -428,7 +501,9 @@ The list of containers are described on the `ONAP wiki <https://wiki.onap.org/di **Portal configuration** ======================== The current ONAP installation is using the *onap.org* domain. -To use the portal on your desktop, you must configure the following information in your *host* file (located in /etc/host for Linux or /windows/system32/drivers/etc/hosts for Windows): +To use the portal on your desktop, you must configure the following information +in your *host* file (located in /etc/host for Linux or +/windows/system32/drivers/etc/hosts for Windows): .. code-block:: bash @@ -440,13 +515,15 @@ To use the portal on your desktop, you must configure the following information <onap-aai-inst2_ip> aai.ui.simpledemo.onap.org -You can use the Horizon dashboard to get the IP addresses associated with the Virtual Machines or use the following command line: +You can use the Horizon dashboard to get the IP addresses associated with the +Virtual Machines or use the following command line: .. code-block:: bash openstack server list -Launch the portal on the http://portal.api.simpledemo.onap.org:8989/ONAPPORTAL/login.htm +Launch the portal on the +http://portal.api.simpledemo.onap.org:8989/ONAPPORTAL/login.htm Various users are predefined as presented in the following table: @@ -462,7 +539,8 @@ Various users are predefined as presented in the following table: The password is *demo123456!* -Go to the `Portal component user guide <http://onap.readthedocs.io/en/latest/submodules/portal.git/docs/index.html>`_ +Go to the `Portal component user guide +<http://onap.readthedocs.io/en/latest/submodules/portal.git/docs/index.html>`_ Other UI documentation: - `CLAMP <http://onap.readthedocs.io/en/latest/submodules/clamp.git/docs/index.html>`_ @@ -473,7 +551,8 @@ Other UI documentation: **Components** ============== -The list of various services and ports used can be found on the `ONAP wiki <https://wiki.onap.org/display/DW/ONAP+Services+List#ONAPServicesList-ONAPServices>`_ +The list of various services and ports used can be found on the +`ONAP wiki - services <https://wiki.onap.org/display/DW/ONAP+Services+List#ONAPServicesList-ONAPServices>`_ .. This work is licensed under a Creative Commons Attribution 4.0 International License. http://creativecommons.org/licenses/by/4.0 diff --git a/docs/guides/onap-developer/settingup/install-designate.rst b/docs/guides/onap-developer/settingup/install-designate.rst index 9f9dde3d9..42000a43d 100644 --- a/docs/guides/onap-developer/settingup/install-designate.rst +++ b/docs/guides/onap-developer/settingup/install-designate.rst @@ -53,7 +53,28 @@ The current design of kubernetes deployment installs DCAE into any openstack ins Few steps have to be performed. The detail of each steps are in `the config guide of Openstack Designate <https://docs.openstack.org/designate/latest/install/index.html>`: 1. Install bind9 nameserver -2. Configure it to accept dns updates and forward to your master DNS Server +2. Configure it to accept dns updates and forward to your master DNS Server. Example configuration is below: + .. code:: bash + root@designate:~# cat /etc/bind/named.conf.options + include "/etc/bind/rndc.key"; + options { + directory "/var/cache/bind"; + allow-new-zones yes; + dnssec-validation auto; + listen-on port 53 { 10.203.157.79; }; + forwarders { + 8.8.8.8; + 8.8.4.4; + }; + forward only; + allow-query { any; }; + recursion yes; + minimal-responses yes; + }; + controls { + inet 10.203.157.79 port 953 allow { 10.203.157.79; } keys { "rndc-key"; }; + }; + root@designate:~# 3. Configure Designate in openstack. Please see `this guide <https://docs.openstack.org/mitaka/networking-guide/config-dns-int.html>` for more details. 4. Create a pool pointing to your nameserver diff --git a/docs/guides/onap-developer/tutorials/index.rst b/docs/guides/onap-developer/tutorials/index.rst index 2365efd10..b128224c7 100644 --- a/docs/guides/onap-developer/tutorials/index.rst +++ b/docs/guides/onap-developer/tutorials/index.rst @@ -1,4 +1,5 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. This work is licensed under a Creative Commons Attribution 4.0 +.. International License. Tutorials ========= @@ -8,7 +9,7 @@ Tutorials .. caution:: The tutorials may refer to earlier versions of software - and have not been certified on the latest Amsterdam Release. + and have not been certified on the latest Beijing Release. * `Automatically Creating a Netconf Mount in APPC from SDNC <https://wiki.onap.org/x/JYUx>`_ diff --git a/docs/release/releaserepos.rst b/docs/release/releaserepos.rst index 2b0d5c607..c8f4c83f3 100644 --- a/docs/release/releaserepos.rst +++ b/docs/release/releaserepos.rst @@ -127,6 +127,16 @@ MultiVIM Cloud multicloud/framework<../submodules/multicloud/framework.git/docs/Release Notes.rst> +Music +----- + +.. toctree:: + :maxdepth: 1 + :titlesonly: + + music<../submodules/music.git/docs/release-notes.rst> + + ONAP Operations Manager (experimental) -------------------------------------- diff --git a/docs/release/repolist.rst b/docs/release/repolist.rst index d29aa8354..148c1dd88 100644 --- a/docs/release/repolist.rst +++ b/docs/release/repolist.rst @@ -16,40 +16,34 @@ Project/Components aaf/authz <../submodules/aaf/authz.git/docs/index> AAI - Active & Available Inventory <../submodules/aai/aai-common.git/docs/index> - AAI External System Registration UI <../submodules/aai/esr-gui.git/docs/index> + aai/event-client <../submodules/aai/event-client.git/docs/index> AAI External System Registration Server <../submodules/aai/esr-server.git/docs/index> + AAI External System Registration UI <../submodules/aai/esr-gui.git/docs/index> AAI Sparky Inventory UI <../submodules/aai/sparky-be.git/docs/index> - ../submodules/appc/deployment.git/docs/index - ../submodules/appc.git/docs/index CCSDK Dashboard <../submodules/ccsdk/dashboard.git/docs/index> ccsdk/distribution <../submodules/ccsdk/distribution.git/docs/index> + CCSDK Orchestrator Plugins <../submodules/ccsdk/platform/plugins.git/docs/index> ccsdk/parent <../submodules/ccsdk/parent.git/docs/index> ccsdk/platform/blueprints <../submodules/ccsdk/platform/blueprints.git/docs/index> ccsdk/platform/nbapi <../submodules/ccsdk/platform/nbapi.git/docs/index> - CCSDK Orchestrator Plugins <../submodules/ccsdk/platform/plugins.git/docs/index> ccsdk/storage/esaas <../submodules/ccsdk/storage/esaas.git/docs/index> ccsdk/storage/pgaas <../submodules/ccsdk/storage/pgaas.git/docs/index> ccsdk/utils <../submodules/ccsdk/utils.git/docs/index> - ../submodules/clamp.git/docs/index - ../submodules/cli.git/docs/index - ../submodules/dcaegen2.git/docs/index - ../submodules/dmaap/messagerouter/messageservice.git/docs/index + dmaap/datarouter <../submodules/dmaap/datarouter.git/docs/index> + dmaap/dbcapi <../submodules/dmaap/dbcapi.git/docs/index> HOLMES - Alarm Correlation and Analysis <../submodules/holmes/engine-management.git/docs/index> HOLMES - Architecuture and APIs <../submodules/holmes/rule-management.git/docs/index> integration <../submodules/integration.git/docs/index> logging-analytics <../submodules/logging-analytics.git/docs/index> - ../submodules/modeling/modelspec.git/docs/index modeling/toscaparsers <../submodules/modeling/toscaparsers.git/docs/index> - MSB - Microservice Bus <../submodules/msb/apigateway.git/docs/index> msb/discovery <../submodules/msb/discovery.git/docs/index> msb/java-sdk <../submodules/msb/java-sdk.git/docs/index> + MSB - Microservice Bus <../submodules/msb/apigateway.git/docs/index> msb/swagger-sdk <../submodules/msb/swagger-sdk.git/docs/index> MultiCloud Framework <../submodules/multicloud/framework.git/docs/index> + music <../submodules/music.git/docs/index> ONAP Operations Manager <../submodules/oom.git/docs/index> - ../submodules/optf/has.git/docs/index - ../submodules/policy/engine.git/docs/index - ../submodules/portal.git/docs/index - Service Design and Creation <../submodules/sdc.git/docs/index> + optf/osdf <../submodules/optf/osdf.git/docs/index> sdc/jtosca <../submodules/sdc/jtosca.git/docs/index> sdc/sdc-distribution-client <../submodules/sdc/sdc-distribution-client.git/docs/index> sdc/sdc-docker-base <../submodules/sdc/sdc-docker-base.git/docs/index> @@ -57,17 +51,24 @@ Project/Components sdc/sdc-tosca <../submodules/sdc/sdc-tosca.git/docs/index> sdc/sdc-workflow-designer <../submodules/sdc/sdc-workflow-designer.git/docs/index> sdnc/oam <../submodules/sdnc/oam.git/docs/index> + Service Design and Creation <../submodules/sdc.git/docs/index> Service Orchestrator <../submodules/so.git/docs/index> so/libs <../submodules/so/libs.git/docs/index> + ../submodules/appc/deployment.git/docs/index + ../submodules/appc.git/docs/index + ../submodules/clamp.git/docs/index + ../submodules/cli.git/docs/index + ../submodules/dcaegen2.git/docs/index + ../submodules/dmaap/messagerouter/messageservice.git/docs/index + ../submodules/modeling/modelspec.git/docs/index + ../submodules/optf/has.git/docs/index + ../submodules/policy/engine.git/docs/index + ../submodules/portal.git/docs/index + ../submodules/vnfrqts/guidelines.git/docs/index + ../submodules/vnfrqts/requirements.git/docs/index Use Case User Interface <../submodules/usecase-ui.git/docs/index> VFC - Virtual Function Controller <../submodules/vfc/nfvo/lcm.git/docs/index> - VID - Virtual Infrastructure Deployment <../submodules/vid.git/docs/index> vid/asdcclient <../submodules/vid/asdcclient.git/docs/index> - ../submodules/vnfrqts/guidelines.git/docs/index - ../submodules/vnfrqts/requirements.git/docs/index + VID - Virtual Infrastructure Deployment <../submodules/vid.git/docs/index> VNF Software Development Kit <../submodules/vnfsdk/model.git/docs/index> vvp/documentation <../submodules/vvp/documentation.git/docs/index> - aai/event-client <../submodules/aai/event-client.git/docs/index> - optf/osdf <../submodules/optf/osdf.git/docs/index> - dmaap/datarouter <../submodules/dmaap/datarouter.git/docs/index> - dmaap/dbcapi <../submodules/dmaap/dbcapi.git/docs/index> diff --git a/docs/submodules/aai/aai-common.git b/docs/submodules/aai/aai-common.git -Subproject ea404c2e3dd25ae283345065b9956656306d70d +Subproject f104828c79f132688ee05555c309730e6ffc418 diff --git a/docs/submodules/appc.git b/docs/submodules/appc.git -Subproject e551a81ab48b77b5be881699b4176bbc337bbbc +Subproject 2c73e06f03d6b3d83ead42b4eec3cd40c81865e diff --git a/docs/submodules/ccsdk/parent.git b/docs/submodules/ccsdk/parent.git -Subproject eb6e45dd148db099d132ae8b9cfba5cc187a28f +Subproject ebc00be5b7a3b37569f465fcdd3c9d0b3eba913 diff --git a/docs/submodules/clamp.git b/docs/submodules/clamp.git -Subproject 3dc5f2a4a5c066a57ef0ce346be884b045ae73c +Subproject f7e5aab99d6c2a0a9d5e56b561ba0513aafd504 diff --git a/docs/submodules/cli.git b/docs/submodules/cli.git -Subproject 5d2f93c6fb594fb0197a082a4cf1ba6aea0ead0 +Subproject 8f21819de7f63856f087ad40ac0f36c644781e5 diff --git a/docs/submodules/dcaegen2.git b/docs/submodules/dcaegen2.git -Subproject ef55ef2163dee32905bd10b0a0b3ea0f6a76332 +Subproject 13de8870c542c1cd87d24f1bdde5878c82276c8 diff --git a/docs/submodules/holmes/engine-management.git b/docs/submodules/holmes/engine-management.git -Subproject 56acc55bf479d8b7a635fc91cecc9bcc9775bc5 +Subproject 4417b8ab450c39ccfa357d1314c5e7e31454e07 diff --git a/docs/submodules/holmes/rule-management.git b/docs/submodules/holmes/rule-management.git -Subproject 9d61ac9a63eb763ee5c11993a82e2dcfd6dbafc +Subproject 9b19d379b3f9ea0f1f31202b8c175f8e55fc9b0 diff --git a/docs/submodules/msb/apigateway.git b/docs/submodules/msb/apigateway.git -Subproject ae1f91f7459163a6ae5c7b902379cce7513e1f9 +Subproject b6e4ff577fcbbca210e8c57d477d637c1560191 diff --git a/docs/submodules/msb/java-sdk.git b/docs/submodules/msb/java-sdk.git -Subproject b0fd041c7ec97e762109c1a0700400bb2f3aef1 +Subproject 01b109873fa129319830a4619a01c503c139cd2 diff --git a/docs/submodules/multicloud/framework.git b/docs/submodules/multicloud/framework.git -Subproject 9a0d43b54519c8e08683e522255370ccba13790 +Subproject 9a8d0bfd808e4a3dd0f9e6a5753c89460ca7154 diff --git a/docs/submodules/music.git b/docs/submodules/music.git new file mode 160000 +Subproject 6cfe365f5e342df9d29935df15a83fee40289c5 diff --git a/docs/submodules/policy/engine.git b/docs/submodules/policy/engine.git -Subproject 82b62ca5dd3ae30aab7999b5959e1c07eb1d3d1 +Subproject 4938fc8ff0a231e26d63c06016365bea5c021c3 diff --git a/docs/submodules/sdc.git b/docs/submodules/sdc.git -Subproject 6f578c479c73c2f5989e383355c28cf1c7a01c6 +Subproject 84f69f366eef1a33472145db98e0e2983d3503f diff --git a/docs/submodules/sdc/jtosca.git b/docs/submodules/sdc/jtosca.git -Subproject 05d9b88fd55c81ffce49f8e764a05af195cc24f +Subproject 6263a57c5bb2da0f89292313927cac3e83157a8 diff --git a/docs/submodules/sdc/sdc-distribution-client.git b/docs/submodules/sdc/sdc-distribution-client.git -Subproject e8d8a37da95c6fea435e0b3e93a477b5aa45b9b +Subproject 5729888c9dc75c75ff62bce68a4690275ac0b8e diff --git a/docs/submodules/sdc/sdc-titan-cassandra.git b/docs/submodules/sdc/sdc-titan-cassandra.git -Subproject 83a4e4067fd50cec9bdfbacf18f953cef62b52e +Subproject a9dba442b6acb1347a208825528374a157e45f8 diff --git a/docs/submodules/sdc/sdc-tosca.git b/docs/submodules/sdc/sdc-tosca.git -Subproject f524d3ccf7e3ede73c740830a7ffb0c7820fcc4 +Subproject b0ed12f587f7f87dedb0b838664800662bc4ca8 diff --git a/docs/submodules/sdc/sdc-workflow-designer.git b/docs/submodules/sdc/sdc-workflow-designer.git -Subproject 43bed0e28512332aecc3b70f9e24840682c59e9 +Subproject bbc0b40602f42a6aac5e04fa6cea8507f7ae8f6 diff --git a/docs/submodules/sdnc/oam.git b/docs/submodules/sdnc/oam.git -Subproject f62137b244e64bfaf0d9aa9b606597e59774ea2 +Subproject d21a1b3a5e05b5466c792d5ee7298df5ab714a5 diff --git a/docs/submodules/so.git b/docs/submodules/so.git -Subproject 8ff992a2c526c3b652586fe21216de118294c5b +Subproject 558a73181640d0d19f7f05cab6e0b8568574b50 diff --git a/docs/submodules/so/libs.git b/docs/submodules/so/libs.git -Subproject f0261ef5d032d604cc553593ce694b73f6f179b +Subproject d413cf3266aa38b3a9c5bf37ce30c3de68b3ad5 diff --git a/docs/submodules/vfc/nfvo/driver/vnfm/svnfm.git b/docs/submodules/vfc/nfvo/driver/vnfm/svnfm.git -Subproject eabd611557229b92fdf0f84da9628e5a72801dc +Subproject 16352314819e03143e91d76b3157a125d3e49f8 diff --git a/docs/submodules/vfc/nfvo/lcm.git b/docs/submodules/vfc/nfvo/lcm.git -Subproject 07163fee37f72a64c0ea6cfa94b7cd61a08c7a0 +Subproject e12434fe867b9e53555525c2548ee0200886a6d |