Hello

Working with ONAP Dublin

I managed to instantiate Service/VNF/VF module using the "old VNF_API".

I wanted to try the new "GR_API" option that is available on VID to instantiate 
the same service, on the same cloud region/tenant.

Service Instantiation was OK

VNF instantiation was NOK :

"requestId": "d985ce11-cb1e-4fd8-bfa0-7c039afaa470",
"requestType": "createInstance",
"timestamp": "Tue, 20 Aug 2019 09:42:37",
"requestState": "FAILED",
"requestStatus": "STATUS: Error from SDNC: No availability zones found in AAI 
for cloud region RegionOne FLOW STATUS: All Rollback flows have completed 
successfully ROLLBACK STATUS: Rollback has been completed successfully.",
"percent-progress": "100"


Here is what existed in AAI about "RegionOne"

Request :

curl -X GET \
  
https://aai.api.sparky.simpledemo.onap.org:30233/aai/v16/cloud-infrastructure/cloud-regions
 \
  -H 'Accept: application/json' \
  -H 'Authorization: Basic QUFJOkFBSQ==' \
  -H 'X-FromAppId: AAI' \
  -H 'X-TransactionId: 808b54e3-e563-4144-a1b9-e24e2ed93d4f' \
  -H 'cache-control: no-cache'

Response:

{
    "cloud-region": [
        {
            "cloud-owner": "CloudOwner",
            "cloud-region-id": "RegionOne",
            "cloud-type": "openstack",
            "owner-defined-type": "",
            "cloud-region-version": "",
            "identity-url": "WillBeUpdatedByMultiCloud",
            "cloud-zone": "brittany",
            "complex-name": "Cruguil",
            "sriov-automation": "false",
            "cloud-extra-info": "{\"openstack-region-id\":\"RegionOne\"}",
            "orchestration-disabled": false,
            "in-maint": false,
            "resource-version": "1566227459913"
        },
        {
            "cloud-owner": "OPNFV",
            "cloud-region-id": "RegionOne",
            "cloud-type": "openstack",
            "owner-defined-type": "N/A",
            "cloud-region-version": "pike",
            "identity-url": 
"http://msb-iag.onap:80/api/multicloud-pike/v0/OPNFV_RegionOne/identity/v2.0";,
            "cloud-zone": "OPNFV LaaS",
            "complex-name": "Cruguil",
            "orchestration-disabled": false,
            "in-maint": false,
            "resource-version": "1565190842653",
            "relationship-list": {
                "relationship": [
                    {
                        "related-to": "complex",
                        "relationship-label": 
"org.onap.relationships.inventory.LocatedIn",
                        "related-link": 
"/aai/v16/cloud-infrastructure/complexes/complex/cruguil",
                        "relationship-data": [
                            {
                                "relationship-key": 
"complex.physical-location-id",
                                "relationship-value": "cruguil"
                            }
                        ]
                    }
                ]
            }
        }
    ]
}


In AAI API documentation 
(https://onap.readthedocs.io/en/latest/submodules/aai/aai-common.git/docs/platform/offeredapis.html),
 I see that it is possible to declare an "availability-zone"

PUT 
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}

I need to provide an "availability-zone-name" and "hypervisor-type"

Question1 : is there a relation between "cloud-zone" parameter and the 
"availability-zone-name" ?
Question2 : what are the typical values for "hypervisor-type"


I made a try, creating an "availability-zone" associated to my cloud region 
OPNV/RegionOne.
PUT request:

curl -X PUT \
  
https://aai.api.sparky.simpledemo.onap.org:30233/aai/v16/cloud-infrastructure/cloud-regions/cloud-region/OPNFV/RegionOne/availability-zones/availability-zone/brittany
 \
  -H 'Accept: application/json' \
  -H 'Authorization: Basic QUFJOkFBSQ==' \
  -H 'Content-Type: application/json' \
  -H 'X-FromAppId: AAI' \
  -H 'X-TransactionId: get_aai_subscr' \
  -H 'cache-control: no-cache' \
  -d '{
    "availability-zone-name": "brittany",
    "hypervisor-type": "undefined"
}'

Get request:

curl -X GET \
  
https://aai.api.sparky.simpledemo.onap.org:30233/aai/v16/cloud-infrastructure/cloud-regions/cloud-region/OPNFV/RegionOne/availability-zones
 \
  -H 'Accept: application/json' \
  -H 'Authorization: Basic QUFJOkFBSQ==' \
  -H 'Content-Type: application/json' \
  -H 'X-FromAppId: AAI' \
  -H 'X-TransactionId: 808b54e3-e563-4144-a1b9-e24e2ed93d4f' \
  -H 'cache-control: no-cache'

Response :
{
    "availability-zone": [
        {
            "availability-zone-name": "brittany",
            "hypervisor-type": "undefined",
            "resource-version": "1566289319135"
        }
    ]
}


Then I tried to instantiate the VNF:  Success !

Then I tried to instantiate the VF module : Failed !

"requestId": "ff65a3af-18bd-4c0b-bb5e-b9d161d23798",
"requestType": "createInstance",
"timestamp": "Tue, 20 Aug 2019 10:35:27",
"requestState": "FAILED",
"requestStatus": "STATUS: Error from SDNC: Unable to generate VM name: 
naming-policy-generate-name: input.policy-instance-name is not set and 
input.policy is ASSIGN FLOW STATUS: All Rollback flows have completed 
successfully ROLLBACK STATUS: Rollback has been completed successfully."

I imagined that I should have declare something during service design in SDC 
about using naming policy...
Question3: where can I find the procedure ?

Best regards

René


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.


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

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

Reply via email to