...
The Amsterdam release had certain limitations due to which fixes/workarounds have been provided to execute the demos. The document contains the details of the fixes/workarounds and the steps to deploy them. TODO: reference workarounds, scripts and ONAP content from this wiki - do not duplicate inside Amdocs
Current Limitations of Amsterdam Release and Workarounds
| S.No. | Component | Issue detail | Current Status | Further Actions |
|---|---|---|---|---|
| 1 | SDC | The VNFs are onboarded using TOSCA. However, SDC does not support the 'Group' construct (aka VFModule) which is required when the TOSCA is ingested in SO after distribution. | A partial fix has been provided to overcome this issue | A proposal to include the fix and enhance SDC to support TOSCA 'Groups' construct has been submitted to the SDC PTL. Expected to discuss this and include in the Casablanca release |
| 2 | VID | VID is unable to show the 'VFModule' of a TOSCA service definition. This is linked to the above issue in SDC. | Fix has been provided | The fix will be submitted along with the SDC Group fix for Casablanca release |
| 3 | Multivim Broker | MultiVim broker does not support http request that have content-type as 'multipart/form-data' | Fixed in Beijing release | NA |
| 4 | SDC | The SDC UI displays the service distribution is not successful even though the TOSCA was successfully deployed in SO. | Fixed in Beijing release | NA |
| 5 | SO | VFModule not available in TOSCA definitions due to which SO does not consume the service properly | Fix has been provided in the 'ASDC Controller' module so that the VFModule tables in the Catalog schema can be populated | A proper solution for this depends on the SDC fix explained above. The changes to support 'Groups'/'VFModule' are part of the SDC client library provided by SDC. In addition, the ASDC controller would also need fixes to handle the SDC client library changes. Expected to be fixed in the Casablanca release. |
High level Solution Architecture
...
The High level solution architecture can be found here
| Note |
|---|
| Not all ONAP components have been shown in the high level solution. Only the new component/modules that are introduced in the solution are shown. Rest all remains the same. |
...
The detailed list of changes is given below:
| S.No | Project Name | Docker Image (Pull from dockerhub repo) | Remarks |
|---|---|---|---|
| 1 | OOM | elhaydox/oom | Contains the latest values.yaml files along with certain fixes needed in Amsterdam release. That include:
|
| 2 | OOM Config | elhaydox/oomconfig | Contains the configuration files. |
| 3 | SO | elhaydox/mso | Contains the VFModule fix along with the newly developed BPMN and Multi VIM adapter |
| 4 | multicloud-azure | elhaydox/multicloud-azure | Aria plugin to interface with Azure and instantiate VNFs |
| 5 | SDC | elhaydox/sdc-backend | Contains the partial fix to support Group construct |
| 6 | VID | elhaydox/vid | Contains the partial fix to support Group construct so that VF-Module can be instantiated from VID |
Deploying ONAP on a Single VM
...