Currently, the one piece of data that will link you to the workload in KUD is 
the ‘heat-stack-id’ value in AAI.

E.g.  (

        "vf-module": [
            {
                "vf-module-id": "f7e90e21-9474-4889-9dd3-959231197514",
                "vf-module-name": "vfwk8s_vfm2",
                "heat-stack-id": "vfwk8s_vfm2/nervous_pascal",
                "orchestration-status": "active",
                "is-base-vf-module": true,
                "automated-assignment": false,
                "resource-version": "1569628892420",
                "model-invariant-id": "688f8159-2e75-4a1f-8926-f95ac03e4c33",
                "model-version-id": "c7df9bb9-7af2-4057-8770-b12c84038549",
                "model-customization-id": 
"46eaced0-c81a-4e86-8f7c-b2ed7eed3cbf",
                "module-index": 0
            }
        ]


In this example, ‘nervous_pascal’ is id that the multicloud-k8s plugin uses to 
identify the instance.  E.g. if you were to use curl/postman to query 
multicloud directly - 
https://wiki.onap.org/display/DW/MultiCloud+K8s-Plugin-service+API#MultiCloudK8s-Plugin-serviceAPI-InstantiationAPI

There is also some work in progress to provide additional information in AAI 
about the workload.
Some discussions on the wiki around here:  
https://wiki.onap.org/display/DW/Updating+AAI+upon+successful+instantiation+of+resource+bundle?src=contextnavpagetreemode
gerrit:  https://gerrit.onap.org/r/c/multicloud/k8s/+/96063

Eric

From: [email protected] <[email protected]> On Behalf Of 
Aniello Paolo Malinconico
Sent: Monday, December 16, 2019 7:33 AM
To: [email protected]
Subject: [onap-discuss] [Dublin] Generic Service deployed on KUD (Kubernetes 
enviroment) not described into AAI

Hi all,
I have created a service composed by a VNF (dummy vnf (dummy heat and env file) 
plus a tar.gz file contening all YAMLs files to deploy the vnf on kubernetes).
I successfully deployed it on a KUD . In fact a new pod,service and deployment 
is created on Kubernetes.
However, If I search my Service on ONAP AAI, I see:

  1.   At the service level, the service is described properly
  2.  At VNF level, the service describes the VNF dummy (and I can see that It 
has a file xxxx.tar.gz as CLOUD_TECNOLOGY_.....)
  3.  But I have no description about the Kubernetes service (no reference to 
the k8s tar.gz content files)
In this way, ONAP knows nothing about the services(vnf) deployed on Kubernetes.
For ONAP AAI, my service is composed only by a VNF dummy contening the tar.gz 
and nothing else.

Can anyone confirm it?

Thanks,
Aniello Paolo Malinconico


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#19666): https://lists.onap.org/g/onap-discuss/message/19666
Mute This Topic: https://lists.onap.org/mt/68730385/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to