Setting a relationship between ESR-SYSTEM-INFO and GENERIC-VNF for ETSI SOL003 SO VNFM Adapter in Dublin

I am working as a ONAP SO committer, working with Seshu. As you may know, for Dublin, Ericsson is contributing the ETSI SOL003 VNFM Adapter to ONAP Dublin release.
For that, we need to set a relationship between VNFM instance and GenericVNF instance to trace which VNFM instance manages which VNF instance.

Michael Morris from Ericsson investigated the relationship and proposed the following option. To me, this option has a very minor impact on A&AI.

• adding a rule in the AAI DbEdgeRule_vxx.json file (see the example below).

We are not sure the proper values for the remaining fields such as “contains-other-v”, “delete-other-v”, “prevent-delete”, “default” and “description”.
Your A&AI team needs to fill up the proper values. Based on the existing rules, most of the rules used the default values as below.

We’d like to put this relationship into the Dublin release. Could you please take a look at this option and advise us what would be the next step? Open a JIRA ticket?

e.g., aai-schema/src/main/resources/onap/dbedgerules/v15/DbEdgeRules_v15.json

<setting a relationship between generic-vnf to esr-system-info>

“rules”: [
…,
{
"from": "generic-vnf",
"to": "esr-system-info",
"label": "tosca.relationships.DependsOn",
"direction": "OUT",
"multiplicity": "MANY2ONE",
"contains-other-v": "NONE",
"delete-other-v": "NONE",
"prevent-delete": "NONE",
"default": "true",
"description":""
}
…
]