Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

AAI: Store orchestration-type parameter as part of model-ver:object

Description

SDC is currently using AAI to store the meta-data information about service models.
Essentially, this is done using model-ver:object (storing version-specific information about Service Models).

We need to extend the model-ver:object, to incorporate an additional parameter related to Service-Model - "orchestration-type".
The are 2 allowed names for orchestration-type:

  • "a-la-carte"

  • "macro"
    Default is "a-la-carte", and a Service Model needs to have always the orchestration-type assigned.
    Goal of this Story is to extend the existing object model, with this additional parameter.

Additionally:

Use AAI-ModelLoader component of AAI to store the value of service model`s orchestration-type in relevant AAI model-ver object field.

Proposal:

  • Extend the model-ver:object (orchestration-type is version-specific)

  • Add a field: orchestration-type

  • Field type: string

  • Required?: No

  • Extend the AAI-ML CSAR processor to fill-up the new field defined before

Activity

Show:

Former user September 17, 2019 at 1:19 PM

For testing purposes, adding it locally to v16 is OK, as it would not be contributed or backported to Dublin release.
But the actual contribution should be in v17 Frankfurt release.

I guess you do not want to be responsible for completing the additional work required to fully introduce a new schema version.

For the CCVPN SOTN NNI proposal , the plan is to wait for the full introduction of v17 before adding new schema changes on top of that.

Former user September 17, 2019 at 1:15 PM

ok, thank you. Btw which approach should we follow:

  • extending v16 with our change

  • add v17 (like I did here)  ? 

 

Former user September 17, 2019 at 1:10 PM
Edited

Please note that adding a new schema version to AAI requires more than one commit, e.g. see "Add v16" cases from Dublin release:
https://lf-onap.atlassian.net/issues/?jql=project%20%3D%20AAI%20AND%20text%20~%20%22add%20v16%22

Either it should all be done here or it should be delegated to

Former user September 4, 2019 at 2:20 PM

Ok, it`s the AAI-ModelLoader then. I believe the AAI-Model Loader deals with parsing distributed service model CSARs, and loads stuff to relevant AAI objects.
If that`s the case, then AAI-Model Loader is the one, which has to be modified/re-configured. We could look at the enhancement in there. Point taken.

Former user September 4, 2019 at 1:49 PM

There shall be a service model CSAR parser in AAI, which can be used to fill this parameter up based on the CSAR contents.
Is it feasible to follow this apporach?

 

I think A&AI model loader need enhancement to populate this service model property.

Done

Details

Assignee

Reporter

Fix versions

Priority

Parent

Created September 2, 2019 at 1:31 PM
Updated July 29, 2020 at 11:53 AM
Resolved February 13, 2020 at 4:05 PM