Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Page Under Construction

This page is a detailed user guide for a creating a very simple ONAP service that contains a valid monitoring configuration. This page covers the flow in SDC. The emphasis is on the flow through the various designers and other tools and none of these is explored in much detail except for the parts that are necessary for completion of this flow. Some caveats are highlighted though.

To some extent this aims to cover similar things as in DCAE-Design Studio but from a user perspective and in a more detailed level. This page also covers the full flow in SDC and does not restrict itself to steps in the overall flow that are not implemented by DCAE-DS. Another point of comparison is Onboarding steps for DCAE MS through SDC/Policy/CLAMP (Dublin) and can be considered to cover non-policy parts of its section "Load Policy Model and blueprint into SDC repo (Development phase)".

There are also instructions for doing partly the same kind of thing in "the old way" by using Cloudify blueprints directly in services in https://onap.readthedocs.io/en/latest/guides/onap-user/design/control-loop/index.html#. TODO: The relation of the procedure described in the above page to the procedure described in this page is not clear. Are both now supported? Or either one? Combination of both?

...

This has been tested with SDC/Dublin with software from around RC0 time. As the relevant parts were not really developed much during Dublin, these probably mostly apply to Casablanca as well. This has not been tested though. 



Terminology

AbbreviationLong FormDescription
MCMonitoring Configuration
VFCMTVirtual Function ? Monitoring TemplateTODO: What is the VFCMT really an abbreviation of?
SpecDCAE Micro service specification



...

This is a special case of VF Creation as described in https://onap.readthedocs.io/en/latest/guides/onap-user/design/vfcreation/index.html. Those instructions do not really apply much to this DCAE VF case on practical level, but conceptually fulfill the same part of the design process. Especially note that license model (VLM)  or vendor software product (VSP) concepts are not involved at all. 

...

SDC does not understand Spec file, so the first step is to translate the Spec file it to a set of TOSCA files. This can only be done using a special command line tool as detailed here: How to generate artefacts for SDC catalog using Tosca Lab Tool

...

The VF you added in the previous chapter is visible in the "Microservice" box on the right, but you need to click it to expand to show a list of VFs. The screenshot below shows it expanded . in a case of only one DCAE VF in SDC. If you have more VFs with type DCAE in SDC, they are visible here organized in a separate box by subcategory. If you have no DCAE VFs in SDC, no boxes are visible and you cannot effectively do anything here.

Last step to reach the state show shown in the screenshot below is to drag a VF from the box on the right to the central area. It visualizes the structure of the VF. In this case one container "tca-docker" subcribing to one DMaaP MR topic "topic0" and publishing to another "topic1".

...

SDC Catalogue has a DCAE VF in state "CertiffiedCertified" and DCAE-DS Catalogue has a VFCMT in state "NOT_CERTIFIED_CHECKIN".

...

A Monitoring Configuration currently requires a VF in the service. Usually for a useful service there would be a VF (VNF) implementing some actual network function, but for simplicity we will use the same DCAE VF created above for this. To use it in a service, open "Composition" from the menu on the left , and drag your VF from the "ELEMENTS" menu on the left to the central composition area. The DCAE VF is visible under "DCAE Component" heading in the "ELEMENTS" menu. 

To start Monitoring Configuration creation, click "Monitoring" on the left hand side menu. 

...

From user point of view this procedure is exactly the same as with SDC in general, like described here: https://onap.readthedocs.io/en/latest/guides/onap-user/design/service-distribution/index.html

 Some Some ONAP demo videos also show the step by step procedure from the user point of view.

...

A distribution of a CSAR created using the procedure of this page succeeds from the SDC point of view. However, CLAMP complains that the VF is not valid and seems to reject the service CSAR due to this. Clearly there are further requirements at least for the VF. This guide will be updated when this is resolved.

The problem seems to be related to VF TOSCA template generation in SDC (

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-2330
) which is still unresolved and at the moment does not seem to get fixed for Dublin. Unfortunately the resulting csar is not usable in runtime until this gets fixed some time in the El Alto timeframe. 

The distributed csar: 

View file
nameservice-Timoservice-csar.csar
height250

...