Date   

SNMP experience with ONAP to configure PNF

Eric Debeau
 

Hello

 

In the context of PNF configuration, we would like to know is someone has some experience on using SNMP to configure PNF.

 

Best Regards

 

Eric

_________________________________________________________________________________________________________________________

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.


Re: [CLI] Latest version of CLI image

Kanagaraj Manickam
 

Hi Ryoyu,

 

For El Alto, the image is not released yet. So if you are looking for the latest CLI, please take it from the git master or nexus .

https://github.com/onap/cli/blob/master/deployment/zip/installer/install-latest.sh

NOTE: please use snapshot instead of release repo.

 

Regards

 

Kanagaraj Manickam

Senior System Architect

P&S ONAP

Huawei Technologies India Pvt. Ltd.

Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield

Bengaluru-560066, Karnataka

Tel: + 91-80-49160700 ext 72410 Mob: 9945602938

Company_logo

 


This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Ying, Ruoyu
Sent: 26 August 2019 06:40
To: Kanagaraj Manickam <kanagaraj.manickam@...>
Cc: onap-discuss@...
Subject: [onap-discuss][CLI] Latest version of CLI image

 

Hi Kanagaraj,

 

Do you know what’s the latest version for the CLI docker image that we could use for integration testing? Thanks.

 

Best Regards,

Ruoyu

 


[OOM] [CIA] [mariadb-galera]

Dmitry Puzikov <dmitry.puzikov@...>
 

Hi, OOM team,

While working on ONAP image optimization as a CIA team
we noticed that some amount of third party images are used.
One of them is adfinissygroup/k8s-mariadb-galera-centos
which is used across whole ONAP.
According to OOM Helm charts version v002 is used.
In depth checking of adfinissygroup GitHub repo (https://github.com/adfinis-sygroup/openshift-mariadb-galera)
shows that MariaDB 10.1 is under the hood and this DB version remains the same regardless of
image version v002 or v004.
There's an issue OOM-1720 (maybe there are more) concerning about outdated DB.
Adfinissygroup repo seems not to be active for a long time and becoming more and more outdated.

Taking all said in account we propose to take over building of MariaDB-galera images under the OOM umbrella.
Steps to make it done:
1. Fork adfinissygroup repo
2. Make required modification (update dockerfile, update DB version)
3. Push updated sources to the ONAP repo.
Similar to `common` helm charts, e.g. `docker-common` (sub)repo might be created to host
such images sources.
4. Create CI job to build and push updated MariaDB image to ONAP registry.
5. Update Helm charts to use ONAP maintained MariaDB-galera version.

We actually already did first two steps and eager to continue with the rest.
Currently multiarch PoC images are available on DockerHub personal repo (https://hub.docker.com/r/zhabba/k8s-mariadb-galera-ubuntu)
and sources are available on GitHub personal repo (https://github.com/zhabba/openshift-mariadb-galera).
New k8s-mariadb-galera is based on Ubuntu and offers MariaDB v10.3 and v10.4 with the pretty the same
functionality as adfinissygroup predecessor with as twice as smaller image size (591MB vs. 1.09GB) and multiarch support.
Images are tested as standalone 3 nodes cluster and currently we're testing them as part of ONAP installation.

If you have any thoughts, comments, ideas or may be some additional test requirements let's discuss it in details.

Thank you,

Best Regards,
Dmitry


AAF Agent helm OOM deploy fails #aaf #oom

Fiachra Corcoran
 

Hi AAF Team,

 

I am testing the new dynamic cert distribution flow for OOM deploy on one of our components. Was hoping to catch you at the AAF meeting but Sai explained you were busy.

 

I am deploying OOM using microk8s on my local machine.

 

I have updated the helm charts to include the Init container and configured it correctly. (I think!)

I am also mounting the relevant path to the /dockerdata-nfs (not sure if this is ok).

Attached are the updated charts for dmaap-dr-node.

 

When I deploy AAF OOM the dmaap-dr artifacts say that no X509's Creds instantiated. Is this OK?

I did try to run the agent.sh script but fails due to container linkage failure.

 

The dmaap-dr-node artifact is left as is:

 

When I deploy dmaap-dr, the init container runs but doesn't produce the jks file.

On my container the following are produced:

 

/opt $ ls -larth /opt/app/osaaf/local/
total 144
-rw-r--r--    1 root     root      115.2K Aug 13 16:27 truststoreONAPall.jks
-r--------    1 root     root        2.0K Aug 13 16:27 org.onap.dmaap-dr.keyfile
-rw-r--r--    1 root     root          16 Aug 13 16:27 VERSION
-rw-r--r--    1 root     root        1.3K Aug 13 16:27 org.onap.dmaap-dr.props
-rw-r--r--    1 root     root         285 Aug 13 16:27 org.onap.dmaap-dr.location.props
-rw-r--r--    1 root     root         548 Aug 13 16:27 org.onap.dmaap-dr.cred.props

 

 

The props file looks to have the correct data but no jks or p12.

 

/opt $ cat /opt/app/osaaf/local/org.onap.dmaap-dr.props
############################################################
# Properties Generated by AT&T Certificate Manager
#   by root
#   on 2019-08-13T15:27:48.120+0000
# @copyright 2019, AT&T
############################################################
aaf_env=DEV
aaf_id=dmaap-dr-node@...
aaf_locate_url=https://aaf-locate.onap:8095
aaf_locator_app_ns=org.onap.dmaap-dr
aaf_locator_container=oom
aaf_locator_container_ns=onap
aaf_locator_fqdn=dmaap-dr-node
aaf_oauth2_introspect_url=https://AAF_LOCATE_URL/%CNS.%AAF_NS.introspect:2.1/introspect
aaf_oauth2_token_url=https://AAF_LOCATE_URL/%CNS.%AAF_NS.token:2.1/token
aaf_url=https://AAF_LOCATE_URL/%CNS.%AAF_NS.service:2.1
aaf_url_cm=https://aaf-locate.onap:8095/locate/onap.org.onap.dmaap-dr.cm:2.1
aaf_url_fs=https://aaf-locate.onap:8095/locate/onap.org.osaaf.aaf.fs:2.1
aaf_url_gui=https://aaf-locate.onap:8095/locate/onap.org.osaaf.aaf.gui:2.1
aaf_url_hello=https://aaf-locate.onap:8095/locate/onap.org.osaaf.aaf.hello:2.1
aaf_url_oauth=https://aaf-locate.onap:8095/locate/onap.org.osaaf.aaf.oauth:2.1
cadi_prop_files=/opt/app/osaaf/local/org.onap.dmaap-dr.location.props:/opt/app/osaaf/local/org.onap.dmaap-dr.cred.props
cadi_protocols=TLSv1.1,TLSv1.2
cm_url=https://AAF_LOCATE_URL/%CNS.%AAF_NS.cm:2.1
fs_url=https://AAF_LOCATE_URL/%CNS.%AAF_NS.fs:2.1
gui_url=https://AAF_LOCATE_URL/%CNS.%AAF_NS.gui:2.1

My assumption was that the container would get the jks and p12 mounted to the relevant path and could be loaded into the server at deploy time.

 

Could you advise on what the issue might be?

 

Thanks,

Fiachra


Re: [SO][OOF][MultiCloud] error while instantiating VF module

thierry.hardy@...
 

Hi,

I’m going to check if Polipo filters DELETE actions.

For openstack version, we are on ROCKY version
Regards

Thierry

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Rene Robert via Lists.Onap.Org
Envoyé : samedi 24 août 2019 09:11
À : onap-discuss; HARDY Thierry TGI/OLN
Objet : Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

I think this is your Polipo local proxy that causes that error. Try the curl directly from the jumphost.

 

Envoyé depuis mon smartphone Xperia de Sony



---- thierry.hardy via Lists.Onap.Org a écrit ----

I tried this delete operation but it is not implemented

curl -X DELETE \

 http://msb.api.discovery.simpledemo.onap.org:30280/api/multicloud/v1/OPNFV/RegionOne \

  -H 'Accept: application/json' \

  -H 'Cache-Control: no-cache' \

  -H 'Content-Type: application/json' \

  -H 'Postman-Token: d3380ac7-205a-46d6-9ac3-ec1f929956a3' \

 

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

<html>

    <head>

        <title>Proxy error: 501 Method not implemented.</title>

    </head>

    <body>

       <h1>501 Method not implemented</h1>

        <p>The following error occurred:

            <br>

            <br>

            <strong>501 Method not implemented</strong>

        </p>

        <hr>Generated Fri, 23 Aug 2019 14:41:51 DST by Polipo on

        <em>WX-OR6178716.ad.francetelecom.fr:8185</em>.

    </body>

</html>

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Rene Robert via Lists.Onap.Org
Envoyé : vendredi 23 août 2019 14:25
À : Eric W <eric. w. multanen@intel. com> Multanen; sb00577584@...; Seshu m; Yang Bin <bin. yang@windriver. com>; onap-discuss; HARDY Thierry TGI/OLN
Objet : Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

maybe we should use the delete operation (see: unregister vim in  http://docs.onap.org/en/dublin/submodules/multicloud/framework.git/docs/MultiCloud-APIv1-Specification.html)

 

then the post operation to register the vim

 

Envoyé depuis mon smartphone Xperia de Sony



---- thierry.hardy via Lists.Onap.Org a écrit ----

Hi

I’m from Orange in the same team than René.

I have performed a modification of our installation project to integrate multicloud. And since this morning, the instantiation is successfull.

Yesterday, I met similar errors than yours due a wrong declaration of tenant via ESR. I forgot to indicate v3 in the service-url field.

 

So I changed yesterday this wrong configuration (via the right esr API) , but I was not able to overwrite the multicloud registration doing:

curl -X POST \

  http://msb.api.discovery.simpledemo.onap.org:30280/api/multicloud/v1/OPNFV/RegionOne/registry \

  -H 'Accept: application/json' \

  -H 'Cache-Control: no-cache' \

  -H 'Content-Type: application/json' \

  -H 'Postman-Token: 2b32db39-603b-4176-98f7-f1ee26675f48' \

  -H 'defaultTenant: onap-dublin-daily-vnfs-ci'

 

I don’t save the logs but the token error was still visible in logs of multicloud pike pod.

So I looked for an API request to delete registry action but without success. The one from ONAP documentation is not working.

 

As on this tenant, we perform a daily installation of ONAP, this morning, with the right configuration set in multicloud pods from the installation part (executed during the night), the instantiation was successful.

Regards

Thierry

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Multanen, Eric W
Envoyé : jeudi 22 août 2019 19:37
À : onap-discuss@...; sb00577584@...; seshu.kumar.m@...; ROBERT René TGI/OLN; bin.yang@...
Objet : Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

From the SO config side – looks like what you’ve configured is ok.

 

The multicloud logs – both on registration and vf module create indicate that multicloud is having trouble making requests to your cloud.

 

Do the user credentials you’re using for that cloud have the level of authorization to make these requests?  Have you verifying manually from a CLI perhaps?

 

It appears the main issue at the moment is the multicloud-ocata plugin talking to your Stein cloud.  First guess is something to do with the credentials.  

 

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Sunilkumar Shivangouda Biradar
Sent: Wednesday, August 21, 2019 10:44 PM
To: Multanen, Eric W <eric.w.multanen@...>; onap-discuss@...; seshu.kumar.m@...; rene.robert@...; bin.yang@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Seshu/Eric,

 

As per discussion we had during yesterday’s SO-Weekly call, sharing proper steps followed and fresh logs.

 

Steps followed:

  1. Cloud region created with these details. (Please refer to AAI_Cloud_Details.txt attached)   

 

Note: we are using Stein version (3.19.0) of openstack.

 

  1. Modified the identity_services table of catalogdb with Identity_url =”http://msb-iag.onap:80/api/multicloud/v0/CloudOwner_RegionOne/identity/v2.0”.
  2. Modified the cloud_sites table as shown below

 

 

  1. Did Setting of SO BPMN to use the VNF API v2 (post changing this, deleted the so-bpmn pod and the pod restarted successfully)

 

                    vnf:

                       endpoint: http://so-openstack-adapter.onap:8087/services/VnfAdapter

                       rest:

                         endpoint: http://so-openstack-adapter.onap:8087/services/rest/v2/vnfs

 

 

  1. Tried to register the cloud with multicloud using following API

curl -vvv -X POST http://10.211.1.20:30280/api/multicloud/v1/CloudOwner/RegionOne/registry -H 'Accept: application/json' -H 'Cache-Control: no-cache' -H 'Content-Type: application/json'

 

Note: did not understand why multicloud added "identity-url": "http://msb-iag.onap:80/api/multicloud-ocata/v0/CloudOwner_RegionOne/identity/v2.0"  to the AAI cloud region detail (we are using Stein version (3.19.0) of openstack)

 

I see errors in multicloud-ocata pod as shown below(full log file attached : multicloud-ocata_pod_logs.txt)

                2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_get_list_resources||DEBUG||making request with URI:projects,{'service_type': 'identity', 'interface': 'public'}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_discover_tenants||ERROR||HttpError: status:401, response:{u'error': {u'message': u'The request you have made requires authentication.', u'code': 401, u'title': u'Unauthorized'}}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_get_list_resources||DEBUG||making request with URI:/flavors/detail,{'service_type': 'compute', 'interface': 'public', 'region_name': u'RegionOne'}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_discover_flavors||ERROR||HttpError: status:401, response:{u'error': {u'message': u'The request you have made requires authentication.', u'code': 401, u'title': u'Unauthorized'}}||||requestID= invocationID= serviceName= serviceIP=

 

  1. Triggered VF Creation from VID portal (using VNF-API) with SNDC preload: VF Creation failed with error from multicloud.

Debug log file attached for SO-Openstack pod : VFCreation_SO_Openstack_pod_logs.txt

Log file attached from multicloud-ocata pod : VFCreation_Multicloud-ocata_pod_logs.txt

 

Snippet from SO-Openstack logs:

2019-08-22T04:23:20.279Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Making GET request to: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Request Headers: {Project=[c673af272d074170881559797f46b89d], Accept=[application/json], X-ONAP-RequestID=[5140aff8-5c26-4909-a443-84b8c36bff89], X-ONAP-InvocationID=[023572a9-79af-4802-9298-1265cff23e48], X-ONAP-PartnerName=[SO]}

2019-08-22T04:23:20.491Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Response from GET: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Response Headers: {Allow=[GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS], connection=[keep-alive], content-type=[text/html; charset=utf-8], Date=[Thu, 22 Aug 2019 04:23:20 GMT], Server=[openresty], transfer-encoding=[chunked], Vary=[Cookie], X-Frame-Options=[SAMEORIGIN]}<h1>Server Error (500)</h1>

 

Need your expertise in resolving this issue.

 

Thanks & Regards,

Sunil B

 

From: Multanen, Eric W <eric.w.multanen@...>
Sent: Wednesday, August 21, 2019 7:02 PM
To: onap-discuss@...; seshu.kumar.m@...; Sunilkumar Shivangouda Biradar <SB00577584@...>; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Per Seshu’s comment – yes, there is some apparent mismatch in the different log samples.

 

In the first log sample (down at the bottom) – it appears that configuration for using Multicloud via has been done (logs indicate usage of the Multicloud infrastructure workload API

http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

and messages are coming from org.onap.so.openstack.utils.MsoMulticloudUtils

 

In the more recent log sample, the logs coming from MsoHeatUtils show that the multicloud plugin in SO is not being used.

(ok – just spotted it – in the second case, the log indicates that the ‘orchestrator’ column for the cloud region is ‘null’ instead of ‘multicloud’)

 

 

The two key configs are:

  1. setting the SO BPMN to use the VNF API v2
  2. having ‘multicloud’ for the cloudregion in ‘orchestrator’ column of SO cloud_sites catalogdb table.

 

Sunil – to your recent question on the keystone url – when SO BPMN and the cloud region is configured as above, then the keystone url in SO is not used.   The authentication to the cloud region is

handled by the multicloud component – which goes back to the cloud registration process that includes the POST to /api/multicloud-titaniumcloud/v1/{{cloud-owner}}/{{cloud-region-id}}/registry

(and, the step of setting ‘multicloud’ in the ‘orchestrator’ column)

 

Eric

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of seshu kumar m
Sent: Wednesday, August 21, 2019 5:24 AM
To: onap-discuss@...; sb00577584@...; Multanen, Eric W <eric.w.multanen@...>; rene.robert@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Sunil

 

Did you change the orchestration type to Multicloud in SO, before trying this?

It seems there is some config mismatch issue with the intension and the actual execution from the logs.

 

Thanks and Regards,

M Seshu Kumar

Senior System Architect

Single OSS India Branch Department. S/W BU.

Huawei Technologies India Pvt. Ltd.

Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield

Bengaluru-560066, Karnataka.

Tel: + 91-80-49160700 , Mob: 9845355488

Company_logo

___________________________________________________________________________________________________

This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

-------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Sunilkumar Shivangouda Biradar
Sent: Wednesday, August 21, 2019 11:04 AM
To: Multanen, Eric W <eric.w.multanen@...>; onap-discuss@...; rene.robert@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Eric,

 

Thanks for reply, as mentioned in the second issue may I know the keystone url is proper  keystoneUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0

 

Because here I am getting responseCode as 401

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoCommonUtils - Config values RetryDelay:5 RetryCount:3  RetryCodes:504 ResponseCode:401

 

 

Thanks & Regards,

Sunil B

 

 

From: Multanen, Eric W <eric.w.multanen@...>
Sent: Tuesday, August 20, 2019 10:39 PM
To: Sunilkumar Shivangouda Biradar <SB00577584@...>; onap-discuss@...; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

This is what I’ve been using:  http://{{MSB_IP}}:{{MSB_PORT}}/api/multicloud-titaniumcloud/v1/{{cloud-owner}}/{{cloud-region-id}}/registry

 

From: Sunilkumar Shivangouda Biradar <SB00577584@...>
Sent: Tuesday, August 20, 2019 7:08 AM
To: onap-discuss@...; Multanen, Eric W <eric.w.multanen@...>; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Rene/Eric,

 

Thanks for reply, I followed the page which you suggested.

 

1.      Registering cloud site with multicloud as per document, but got 500 Internal server error.
               Found that there is different API “/api/multicloud/v1/MyCompanyName/INTEGRATION_CENTER/registry”, here I got 202 Unknown Status Code.
               Also tried with “/api/multicloud-titaniumcloud/v1/MyCompanyName/INTEGRATION_CENTER/registry, here I got 202 Accepted.
 
             May I know which API we need to use for registering? 

 

2.       In between I got to know that api changed from “MyCompanyName_INTEGRATION_CENTER/identity/v2.0” to “MyCompanyName/INTEGRATION_CENTER/identity/v2.0” for identity_url. 

                After this modification I got error as below

 

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - Found: CloudSite_.._jvsta6b_3c[regionId=RegionOne,identityServiceId=MC_KEYSTONE,cloudVersion=2.5,clli=RegionOne,cloudifyId=<null>,platform=<null>,orchestrator=<null>]

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - Found: CloudIdentity[id=MC_KEYSTONE,identityUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0,msoId=onap-tm5g-01,projectDomain=<null>,userDomain=<null>,adminTenant=service,memberRole=admin,tenantMetadata=true,identityServerType=KEYSTONE,identityAuthenticationType=USERNAME_PASSWORD]

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - keystoneUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoCommonUtils - Config values RetryDelay:5 RetryCount:3  RetryCodes:504 ResponseCode:401

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoHeatUtils - RA_CONNECTION_EXCEPTION 200 Openstack Exception on Token request:

org.onap.so.openstack.exceptions.MsoAdapterException: Authentication Failure: tenant=c673af272d074170881559797f46b89d,cloud=MC_KEYSTONE

        at org.onap.so.openstack.utils.MsoHeatUtils.getHeatClient(MsoHeatUtils.java:871)

        at org.onap.so.openstack.utils.MsoHeatUtils.queryStack(MsoHeatUtils.java:502)

        at org.onap.so.adapters.vnf.MsoVnfAdapterImpl.createVfModule(MsoVnfAdapterImpl.java:653)

 

 

Please suggest on this issue.

 

Thanks & Regards,

Sunil B

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Multanen, Eric W via Lists.Onap.Org
Sent: Monday, August 19, 2019 9:53 PM
To: onap-discuss@...; rene.robert@...; Sunilkumar Shivangouda Biradar <SB00577584@...>
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

I have the same suggestion – check that your cloud region has been setup and registered per the link.

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Rene Robert via Lists.Onap.Org
Sent: Monday, August 19, 2019 7:16 AM
To: onap-discuss@...; sb00577584@...; Multanen, Eric W <eric.w.multanen@...>
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

About cloud_site, there is that user-guide

 

https://onap.readthedocs.io/en/latest/guides/onap-user/cloud_site/index.html

 

maybe it could help

 

Best regards

 

 

Logo Orange

 

René Robert
«Open and Smart solutions for autOmating Network Services»
ORANGE/IMT/OLN/CNC/NARA/OSONS

 

Fixe : +33 2 96 07 39 29
Mobile : +33 6 74 78 68 43
rene.robert@...

 

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Sunilkumar Shivangouda Biradar
Envoyé : lundi 19 août 2019 12:38
À :
onap-discuss@...; eric.w.multanen@...
Objet : [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Team,

 

I am working on vFW usecase with HPA (ONAP version: Dublin)

 

Case 1:- Instantiated VM on openstack but not with specified flavors from OOF

 

I tried to create a VF module from VID using VNF-API and was able instantiate VM on openstack but not with the flavors which was suggested at oof_directives, instead it created the VM with the flavors provided in SDNC_preload and found from so-openstack log that SO was not calling multicloud  API “/api/multicloud/v1/CloudOwner/RegionOne/infra_workload”.

 

Case 2:- VM did not get instantiated, getting error.

 

https://wiki.onap.org/display/DW/Recap+of+Dublin+SO+Multicloud+Plugin+--%3E+Multicloud+Interactions

Got to know from wiki that for HPA we need not make any changes to cloud_site table of catalogdb. (which is leading to Case 1 above). Hence manually I modified orchestrator= “multicloud” for the region I’m using, as show in below table.

 

 

Post changing the cloud_site table I am able to see SO is calling the “/api/multicloud/v1/CloudOwner/RegionOne/infra_workload” API of multicloud.

But getting this below error from SO-openstack log(I made sure that no vf module with this name(vfwhpa_stack_test_24) exists in AAI before triggering vf module creation) :

 

2019-08-19T07:19:29.498Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Query multicloud HEAT stack: vfwhpa_stack_test_24 in tenant c673af272d074170881559797f46b89d

2019-08-19T07:19:29.499Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Multicloud Endpoint is: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

2019-08-19T07:19:29.505Z|| o.onap.so.logging.jaxrs.filter.JaxRsClientLogging - Could not Find Request ID Generating New One: /api/multicloud/v1/CloudOwner/RegionOne/infra_workload

2019-08-19T07:19:29.506Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Making GET request to: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Request Headers: {Project=[c673af272d074170881559797f46b89d], Accept=[application/json], X-ONAP-RequestID=[96718a17-4eeb-41db-b185-88f04799763e], X-ONAP-InvocationID=[bd58d3f1-ecc7-436f-88fb-378ed51a58e2], X-ONAP-PartnerName=[SO]}

2019-08-19T07:19:29.667Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Response from GET: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Response Headers: {Allow=[GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS], connection=[keep-alive], content-type=[text/html; charset=utf-8], Date=[Mon, 19 Aug 2019 07:19:29 GMT], Server=[openresty], transfer-encoding=[chunked], Vary=[Cookie], X-Frame-Options=[SAMEORIGIN]}{"template_type":"HEAT","workload_status_reason":"authenticate fails:CloudOwner, RegionOne, {\"error\":{\"message\":\"The request you have made requires authentication.\",\"code\":401,\"title\":\"Unauthorized\"}}","workload_status":"GET_FAILED","workload_id":""}

 

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Multicloud GET Response: org.apache.cxf.jaxrs.impl.ResponseImpl@6250c8cb

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - StackInfo to convert: {}

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - HeatStatus = FAILED msg = Internal Server Error

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Stack Status: FAILED

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Stack Status Message: Internal Server Error

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - Found Existing VDU, status=FAILED

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - RA_VNF_ALREADY_EXIST vfwhpa_stack_test_24 CloudOwner RegionOne c673af272d074170881559797f46b89d VDU queryVdu 300 VF Module vfwhpa_stack_test_24 already exists and is in FAILED state

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - Create VF: Deployment vfwhpa_stack_test_24 already exists and is in FAILED state in CloudOwner/RegionOne/c673af272d074170881559797f46b89d; requires manual intervention.

2019-08-19T07:19:29.679Z|| org.onap.so.adapters.vnf.BpelRestClient - Sending response to BPEL: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<vfModuleException>

    <messageId>dcfcc4e0-7723-473d-bfcb-dd8b9fe4ff2f-1566199169042</messageId>

    <category>INTERNAL</category>

    <message>Resource vfwhpa_stack_test_24 already exists in owner/cloud/tenant CloudOwner/RegionOne/c673af272d074170881559797f46b89d with ID </message>

   <rolledBack>true</rolledBack>

</vfModuleException>

 

 

Please suggest on this issue.

 

Thanks in advance.

 

Regards,

Sunil B

============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================

_________________________________________________________________________________________________________________________
 
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.

 

 

_________________________________________________________________________________________________________________________
 
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.
_________________________________________________________________________________________________________________________
 
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.
_________________________________________________________________________________________________________________________
 
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.
_________________________________________________________________________________________________________________________
 
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.

_________________________________________________________________________________________________________________________

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.


[CLI] Latest version of CLI image

Ying, Ruoyu
 

Hi Kanagaraj,

 

Do you know what’s the latest version for the CLI docker image that we could use for integration testing? Thanks.

 

Best Regards,

Ruoyu

 


Re: [SO][OOF][MultiCloud] error while instantiating VF module

Rene Robert <rene.robert@...>
 

I think this is your Polipo local proxy that causes that error. Try the curl directly from the jumphost.


Envoyé depuis mon smartphone Xperia de Sony



---- thierry.hardy via Lists.Onap.Org a écrit ----

I tried this delete operation but it is not implemented

curl -X DELETE \

 http://msb.api.discovery.simpledemo.onap.org:30280/api/multicloud/v1/OPNFV/RegionOne \

  -H 'Accept: application/json' \

  -H 'Cache-Control: no-cache' \

  -H 'Content-Type: application/json' \

  -H 'Postman-Token: d3380ac7-205a-46d6-9ac3-ec1f929956a3' \

 

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

<html>

    <head>

        <title>Proxy error: 501 Method not implemented.</title>

    </head>

    <body>

       <h1>501 Method not implemented</h1>

        <p>The following error occurred:

            <br>

            <br>

            <strong>501 Method not implemented</strong>

        </p>

        <hr>Generated Fri, 23 Aug 2019 14:41:51 DST by Polipo on

        <em>WX-OR6178716.ad.francetelecom.fr:8185</em>.

    </body>

</html>

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Rene Robert via Lists.Onap.Org
Envoyé : vendredi 23 août 2019 14:25
À : Eric W <eric. w. multanen@intel. com> Multanen; sb00577584@...; Seshu m; Yang Bin <bin. yang@windriver. com>; onap-discuss; HARDY Thierry TGI/OLN
Objet : Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

maybe we should use the delete operation (see: unregister vim in  http://docs.onap.org/en/dublin/submodules/multicloud/framework.git/docs/MultiCloud-APIv1-Specification.html)

 

then the post operation to register the vim

 

Envoyé depuis mon smartphone Xperia de Sony



---- thierry.hardy via Lists.Onap.Org a écrit ----

Hi

I’m from Orange in the same team than René.

I have performed a modification of our installation project to integrate multicloud. And since this morning, the instantiation is successfull.

Yesterday, I met similar errors than yours due a wrong declaration of tenant via ESR. I forgot to indicate v3 in the service-url field.

 

So I changed yesterday this wrong configuration (via the right esr API) , but I was not able to overwrite the multicloud registration doing:

curl -X POST \

  http://msb.api.discovery.simpledemo.onap.org:30280/api/multicloud/v1/OPNFV/RegionOne/registry \

  -H 'Accept: application/json' \

  -H 'Cache-Control: no-cache' \

  -H 'Content-Type: application/json' \

  -H 'Postman-Token: 2b32db39-603b-4176-98f7-f1ee26675f48' \

  -H 'defaultTenant: onap-dublin-daily-vnfs-ci'

 

I don’t save the logs but the token error was still visible in logs of multicloud pike pod.

So I looked for an API request to delete registry action but without success. The one from ONAP documentation is not working.

 

As on this tenant, we perform a daily installation of ONAP, this morning, with the right configuration set in multicloud pods from the installation part (executed during the night), the instantiation was successful.

Regards

Thierry

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Multanen, Eric W
Envoyé : jeudi 22 août 2019 19:37
À : onap-discuss@...; sb00577584@...; seshu.kumar.m@...; ROBERT René TGI/OLN; bin.yang@...
Objet : Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

From the SO config side – looks like what you’ve configured is ok.

 

The multicloud logs – both on registration and vf module create indicate that multicloud is having trouble making requests to your cloud.

 

Do the user credentials you’re using for that cloud have the level of authorization to make these requests?  Have you verifying manually from a CLI perhaps?

 

It appears the main issue at the moment is the multicloud-ocata plugin talking to your Stein cloud.  First guess is something to do with the credentials.  

 

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Sunilkumar Shivangouda Biradar
Sent: Wednesday, August 21, 2019 10:44 PM
To: Multanen, Eric W <eric.w.multanen@...>; onap-discuss@...; seshu.kumar.m@...; rene.robert@...; bin.yang@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Seshu/Eric,

 

As per discussion we had during yesterday’s SO-Weekly call, sharing proper steps followed and fresh logs.

 

Steps followed:

  1. Cloud region created with these details. (Please refer to AAI_Cloud_Details.txt attached)   

 

Note: we are using Stein version (3.19.0) of openstack.

 

  1. Modified the identity_services table of catalogdb with Identity_url =”http://msb-iag.onap:80/api/multicloud/v0/CloudOwner_RegionOne/identity/v2.0”.
  2. Modified the cloud_sites table as shown below

 

 

  1. Did Setting of SO BPMN to use the VNF API v2 (post changing this, deleted the so-bpmn pod and the pod restarted successfully)

 

                    vnf:

                       endpoint: http://so-openstack-adapter.onap:8087/services/VnfAdapter

                       rest:

                         endpoint: http://so-openstack-adapter.onap:8087/services/rest/v2/vnfs

 

 

  1. Tried to register the cloud with multicloud using following API

curl -vvv -X POST http://10.211.1.20:30280/api/multicloud/v1/CloudOwner/RegionOne/registry -H 'Accept: application/json' -H 'Cache-Control: no-cache' -H 'Content-Type: application/json'

 

Note: did not understand why multicloud added "identity-url": "http://msb-iag.onap:80/api/multicloud-ocata/v0/CloudOwner_RegionOne/identity/v2.0"  to the AAI cloud region detail (we are using Stein version (3.19.0) of openstack)

 

I see errors in multicloud-ocata pod as shown below(full log file attached : multicloud-ocata_pod_logs.txt)

                2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_get_list_resources||DEBUG||making request with URI:projects,{'service_type': 'identity', 'interface': 'public'}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_discover_tenants||ERROR||HttpError: status:401, response:{u'error': {u'message': u'The request you have made requires authentication.', u'code': 401, u'title': u'Unauthorized'}}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_get_list_resources||DEBUG||making request with URI:/flavors/detail,{'service_type': 'compute', 'interface': 'public', 'region_name': u'RegionOne'}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_discover_flavors||ERROR||HttpError: status:401, response:{u'error': {u'message': u'The request you have made requires authentication.', u'code': 401, u'title': u'Unauthorized'}}||||requestID= invocationID= serviceName= serviceIP=

 

  1. Triggered VF Creation from VID portal (using VNF-API) with SNDC preload: VF Creation failed with error from multicloud.

Debug log file attached for SO-Openstack pod : VFCreation_SO_Openstack_pod_logs.txt

Log file attached from multicloud-ocata pod : VFCreation_Multicloud-ocata_pod_logs.txt

 

Snippet from SO-Openstack logs:

2019-08-22T04:23:20.279Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Making GET request to: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Request Headers: {Project=[c673af272d074170881559797f46b89d], Accept=[application/json], X-ONAP-RequestID=[5140aff8-5c26-4909-a443-84b8c36bff89], X-ONAP-InvocationID=[023572a9-79af-4802-9298-1265cff23e48], X-ONAP-PartnerName=[SO]}

2019-08-22T04:23:20.491Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Response from GET: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Response Headers: {Allow=[GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS], connection=[keep-alive], content-type=[text/html; charset=utf-8], Date=[Thu, 22 Aug 2019 04:23:20 GMT], Server=[openresty], transfer-encoding=[chunked], Vary=[Cookie], X-Frame-Options=[SAMEORIGIN]}<h1>Server Error (500)</h1>

 

Need your expertise in resolving this issue.

 

Thanks & Regards,

Sunil B

 

From: Multanen, Eric W <eric.w.multanen@...>
Sent: Wednesday, August 21, 2019 7:02 PM
To: onap-discuss@...; seshu.kumar.m@...; Sunilkumar Shivangouda Biradar <SB00577584@...>; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Per Seshu’s comment – yes, there is some apparent mismatch in the different log samples.

 

In the first log sample (down at the bottom) – it appears that configuration for using Multicloud via has been done (logs indicate usage of the Multicloud infrastructure workload API

http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

and messages are coming from org.onap.so.openstack.utils.MsoMulticloudUtils

 

In the more recent log sample, the logs coming from MsoHeatUtils show that the multicloud plugin in SO is not being used.

(ok – just spotted it – in the second case, the log indicates that the ‘orchestrator’ column for the cloud region is ‘null’ instead of ‘multicloud’)

 

 

The two key configs are:

  1. setting the SO BPMN to use the VNF API v2
  2. having ‘multicloud’ for the cloudregion in ‘orchestrator’ column of SO cloud_sites catalogdb table.

 

Sunil – to your recent question on the keystone url – when SO BPMN and the cloud region is configured as above, then the keystone url in SO is not used.   The authentication to the cloud region is

handled by the multicloud component – which goes back to the cloud registration process that includes the POST to /api/multicloud-titaniumcloud/v1/{{cloud-owner}}/{{cloud-region-id}}/registry

(and, the step of setting ‘multicloud’ in the ‘orchestrator’ column)

 

Eric

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of seshu kumar m
Sent: Wednesday, August 21, 2019 5:24 AM
To: onap-discuss@...; sb00577584@...; Multanen, Eric W <eric.w.multanen@...>; rene.robert@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Sunil

 

Did you change the orchestration type to Multicloud in SO, before trying this?

It seems there is some config mismatch issue with the intension and the actual execution from the logs.

 

Thanks and Regards,

M Seshu Kumar

Senior System Architect

Single OSS India Branch Department. S/W BU.

Huawei Technologies India Pvt. Ltd.

Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield

Bengaluru-560066, Karnataka.

Tel: + 91-80-49160700 , Mob: 9845355488

Company_logo

___________________________________________________________________________________________________

This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

-------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Sunilkumar Shivangouda Biradar
Sent: Wednesday, August 21, 2019 11:04 AM
To: Multanen, Eric W <eric.w.multanen@...>; onap-discuss@...; rene.robert@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Eric,

 

Thanks for reply, as mentioned in the second issue may I know the keystone url is proper  keystoneUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0

 

Because here I am getting responseCode as 401

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoCommonUtils - Config values RetryDelay:5 RetryCount:3  RetryCodes:504 ResponseCode:401

 

 

Thanks & Regards,

Sunil B

 

 

From: Multanen, Eric W <eric.w.multanen@...>
Sent: Tuesday, August 20, 2019 10:39 PM
To: Sunilkumar Shivangouda Biradar <SB00577584@...>; onap-discuss@...; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

This is what I’ve been using:  http://{{MSB_IP}}:{{MSB_PORT}}/api/multicloud-titaniumcloud/v1/{{cloud-owner}}/{{cloud-region-id}}/registry

 

From: Sunilkumar Shivangouda Biradar <SB00577584@...>
Sent: Tuesday, August 20, 2019 7:08 AM
To: onap-discuss@...; Multanen, Eric W <eric.w.multanen@...>; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Rene/Eric,

 

Thanks for reply, I followed the page which you suggested.

 

1.      Registering cloud site with multicloud as per document, but got 500 Internal server error.
               Found that there is different API “/api/multicloud/v1/MyCompanyName/INTEGRATION_CENTER/registry”, here I got 202 Unknown Status Code.
               Also tried with “/api/multicloud-titaniumcloud/v1/MyCompanyName/INTEGRATION_CENTER/registry, here I got 202 Accepted.
 
             May I know which API we need to use for registering? 

 

2.       In between I got to know that api changed from “MyCompanyName_INTEGRATION_CENTER/identity/v2.0” to “MyCompanyName/INTEGRATION_CENTER/identity/v2.0” for identity_url. 

                After this modification I got error as below

 

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - Found: CloudSite_.._jvsta6b_3c[regionId=RegionOne,identityServiceId=MC_KEYSTONE,cloudVersion=2.5,clli=RegionOne,cloudifyId=<null>,platform=<null>,orchestrator=<null>]

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - Found: CloudIdentity[id=MC_KEYSTONE,identityUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0,msoId=onap-tm5g-01,projectDomain=<null>,userDomain=<null>,adminTenant=service,memberRole=admin,tenantMetadata=true,identityServerType=KEYSTONE,identityAuthenticationType=USERNAME_PASSWORD]

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - keystoneUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoCommonUtils - Config values RetryDelay:5 RetryCount:3  RetryCodes:504 ResponseCode:401

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoHeatUtils - RA_CONNECTION_EXCEPTION 200 Openstack Exception on Token request:

org.onap.so.openstack.exceptions.MsoAdapterException: Authentication Failure: tenant=c673af272d074170881559797f46b89d,cloud=MC_KEYSTONE

        at org.onap.so.openstack.utils.MsoHeatUtils.getHeatClient(MsoHeatUtils.java:871)

        at org.onap.so.openstack.utils.MsoHeatUtils.queryStack(MsoHeatUtils.java:502)

        at org.onap.so.adapters.vnf.MsoVnfAdapterImpl.createVfModule(MsoVnfAdapterImpl.java:653)

 

 

Please suggest on this issue.

 

Thanks & Regards,

Sunil B

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Multanen, Eric W via Lists.Onap.Org
Sent: Monday, August 19, 2019 9:53 PM
To: onap-discuss@...; rene.robert@...; Sunilkumar Shivangouda Biradar <SB00577584@...>
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

I have the same suggestion – check that your cloud region has been setup and registered per the link.

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Rene Robert via Lists.Onap.Org
Sent: Monday, August 19, 2019 7:16 AM
To: onap-discuss@...; sb00577584@...; Multanen, Eric W <eric.w.multanen@...>
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

About cloud_site, there is that user-guide

 

https://onap.readthedocs.io/en/latest/guides/onap-user/cloud_site/index.html

 

maybe it could help

 

Best regards

 

 

Logo Orange

 

René Robert
«Open and Smart solutions for autOmating Network Services»
ORANGE/IMT/OLN/CNC/NARA/OSONS

 

Fixe : +33 2 96 07 39 29
Mobile : +33 6 74 78 68 43
rene.robert@...

 

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Sunilkumar Shivangouda Biradar
Envoyé : lundi 19 août 2019 12:38
À :
onap-discuss@...; eric.w.multanen@...
Objet : [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Team,

 

I am working on vFW usecase with HPA (ONAP version: Dublin)

 

Case 1:- Instantiated VM on openstack but not with specified flavors from OOF

 

I tried to create a VF module from VID using VNF-API and was able instantiate VM on openstack but not with the flavors which was suggested at oof_directives, instead it created the VM with the flavors provided in SDNC_preload and found from so-openstack log that SO was not calling multicloud  API “/api/multicloud/v1/CloudOwner/RegionOne/infra_workload”.

 

Case 2:- VM did not get instantiated, getting error.

 

https://wiki.onap.org/display/DW/Recap+of+Dublin+SO+Multicloud+Plugin+--%3E+Multicloud+Interactions

Got to know from wiki that for HPA we need not make any changes to cloud_site table of catalogdb. (which is leading to Case 1 above). Hence manually I modified orchestrator= “multicloud” for the region I’m using, as show in below table.

 

 

Post changing the cloud_site table I am able to see SO is calling the “/api/multicloud/v1/CloudOwner/RegionOne/infra_workload” API of multicloud.

But getting this below error from SO-openstack log(I made sure that no vf module with this name(vfwhpa_stack_test_24) exists in AAI before triggering vf module creation) :

 

2019-08-19T07:19:29.498Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Query multicloud HEAT stack: vfwhpa_stack_test_24 in tenant c673af272d074170881559797f46b89d

2019-08-19T07:19:29.499Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Multicloud Endpoint is: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

2019-08-19T07:19:29.505Z|| o.onap.so.logging.jaxrs.filter.JaxRsClientLogging - Could not Find Request ID Generating New One: /api/multicloud/v1/CloudOwner/RegionOne/infra_workload

2019-08-19T07:19:29.506Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Making GET request to: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Request Headers: {Project=[c673af272d074170881559797f46b89d], Accept=[application/json], X-ONAP-RequestID=[96718a17-4eeb-41db-b185-88f04799763e], X-ONAP-InvocationID=[bd58d3f1-ecc7-436f-88fb-378ed51a58e2], X-ONAP-PartnerName=[SO]}

2019-08-19T07:19:29.667Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Response from GET: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Response Headers: {Allow=[GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS], connection=[keep-alive], content-type=[text/html; charset=utf-8], Date=[Mon, 19 Aug 2019 07:19:29 GMT], Server=[openresty], transfer-encoding=[chunked], Vary=[Cookie], X-Frame-Options=[SAMEORIGIN]}{"template_type":"HEAT","workload_status_reason":"authenticate fails:CloudOwner, RegionOne, {\"error\":{\"message\":\"The request you have made requires authentication.\",\"code\":401,\"title\":\"Unauthorized\"}}","workload_status":"GET_FAILED","workload_id":""}

 

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Multicloud GET Response: org.apache.cxf.jaxrs.impl.ResponseImpl@6250c8cb

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - StackInfo to convert: {}

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - HeatStatus = FAILED msg = Internal Server Error

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Stack Status: FAILED

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Stack Status Message: Internal Server Error

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - Found Existing VDU, status=FAILED

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - RA_VNF_ALREADY_EXIST vfwhpa_stack_test_24 CloudOwner RegionOne c673af272d074170881559797f46b89d VDU queryVdu 300 VF Module vfwhpa_stack_test_24 already exists and is in FAILED state

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - Create VF: Deployment vfwhpa_stack_test_24 already exists and is in FAILED state in CloudOwner/RegionOne/c673af272d074170881559797f46b89d; requires manual intervention.

2019-08-19T07:19:29.679Z|| org.onap.so.adapters.vnf.BpelRestClient - Sending response to BPEL: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<vfModuleException>

    <messageId>dcfcc4e0-7723-473d-bfcb-dd8b9fe4ff2f-1566199169042</messageId>

    <category>INTERNAL</category>

    <message>Resource vfwhpa_stack_test_24 already exists in owner/cloud/tenant CloudOwner/RegionOne/c673af272d074170881559797f46b89d with ID </message>

   <rolledBack>true</rolledBack>

</vfModuleException>

 

 

Please suggest on this issue.

 

Thanks in advance.

 

Regards,

Sunil B

============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================

_________________________________________________________________________________________________________________________
 
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.

 

 

_________________________________________________________________________________________________________________________
 
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.
_________________________________________________________________________________________________________________________
 
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.

_________________________________________________________________________________________________________________________

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.
_________________________________________________________________________________________________________________________

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.


Re: [SO][OOF][MultiCloud] error while instantiating VF module

Sunilkumar Shivangouda Biradar
 

Hi Bin,

Could you please have a quick look and give your valuable feedback on the issue we are facing here for cloud registration with Multicloud.

@Eric : Yes, the user which am using has the authorization to make these requests and i also checked this manually from command line interface(CLI).

@Thierry : May i know which openstack version you are using in your environment?

Thanks & Regards,
Sunil B


From: rene.robert@... <rene.robert@...>
Sent: 23 August 2019 17:55
To: Eric W <eric. w. multanen@intel. com> Multanen <eric.w.multanen@...>; Sunilkumar Shivangouda Biradar <SB00577584@...>; Seshu m <seshu.kumar.m@...>; Yang Bin <bin. yang@windriver. com> <bin.yang@...>; onap-discuss <onap-discuss@...>; HARDY Thierry TGI/OLN <thierry.hardy@...>
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module
 

maybe we should use the delete operation (see: unregister vim in  http://docs.onap.org/en/dublin/submodules/multicloud/framework.git/docs/MultiCloud-APIv1-Specification.html)


then the post operation to register the vim



Envoyé depuis mon smartphone Xperia de Sony



---- thierry.hardy via Lists.Onap.Org a écrit ----

Hi

I’m from Orange in the same team than René.

I have performed a modification of our installation project to integrate multicloud. And since this morning, the instantiation is successfull.

Yesterday, I met similar errors than yours due a wrong declaration of tenant via ESR. I forgot to indicate v3 in the service-url field.

 

So I changed yesterday this wrong configuration (via the right esr API) , but I was not able to overwrite the multicloud registration doing:

curl -X POST \

  http://msb.api.discovery.simpledemo.onap.org:30280/api/multicloud/v1/OPNFV/RegionOne/registry \

  -H 'Accept: application/json' \

  -H 'Cache-Control: no-cache' \

  -H 'Content-Type: application/json' \

  -H 'Postman-Token: 2b32db39-603b-4176-98f7-f1ee26675f48' \

  -H 'defaultTenant: onap-dublin-daily-vnfs-ci'

 

I don’t save the logs but the token error was still visible in logs of multicloud pike pod.

So I looked for an API request to delete registry action but without success. The one from ONAP documentation is not working.

 

As on this tenant, we perform a daily installation of ONAP, this morning, with the right configuration set in multicloud pods from the installation part (executed during the night), the instantiation was successful.

Regards

Thierry

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Multanen, Eric W
Envoyé : jeudi 22 août 2019 19:37
À : onap-discuss@...; sb00577584@...; seshu.kumar.m@...; ROBERT René TGI/OLN; bin.yang@...
Objet : Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

From the SO config side – looks like what you’ve configured is ok.

 

The multicloud logs – both on registration and vf module create indicate that multicloud is having trouble making requests to your cloud.

 

Do the user credentials you’re using for that cloud have the level of authorization to make these requests?  Have you verifying manually from a CLI perhaps?

 

It appears the main issue at the moment is the multicloud-ocata plugin talking to your Stein cloud.  First guess is something to do with the credentials.  

 

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Sunilkumar Shivangouda Biradar
Sent: Wednesday, August 21, 2019 10:44 PM
To: Multanen, Eric W <eric.w.multanen@...>; onap-discuss@...; seshu.kumar.m@...; rene.robert@...; bin.yang@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Seshu/Eric,

 

As per discussion we had during yesterday’s SO-Weekly call, sharing proper steps followed and fresh logs.

 

Steps followed:

  1. Cloud region created with these details. (Please refer to AAI_Cloud_Details.txt attached)   

 

Note: we are using Stein version (3.19.0) of openstack.

 

  1. Modified the identity_services table of catalogdb with Identity_url =”http://msb-iag.onap:80/api/multicloud/v0/CloudOwner_RegionOne/identity/v2.0”.
  2. Modified the cloud_sites table as shown below

 

 

  1. Did Setting of SO BPMN to use the VNF API v2 (post changing this, deleted the so-bpmn pod and the pod restarted successfully)

 

                    vnf:

                       endpoint: http://so-openstack-adapter.onap:8087/services/VnfAdapter

                       rest:

                         endpoint: http://so-openstack-adapter.onap:8087/services/rest/v2/vnfs

 

 

  1. Tried to register the cloud with multicloud using following API

curl -vvv -X POST http://10.211.1.20:30280/api/multicloud/v1/CloudOwner/RegionOne/registry -H 'Accept: application/json' -H 'Cache-Control: no-cache' -H 'Content-Type: application/json'

 

Note: did not understand why multicloud added "identity-url": "http://msb-iag.onap:80/api/multicloud-ocata/v0/CloudOwner_RegionOne/identity/v2.0"  to the AAI cloud region detail (we are using Stein version (3.19.0) of openstack)

 

I see errors in multicloud-ocata pod as shown below(full log file attached : multicloud-ocata_pod_logs.txt)

                2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_get_list_resources||DEBUG||making request with URI:projects,{'service_type': 'identity', 'interface': 'public'}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_discover_tenants||ERROR||HttpError: status:401, response:{u'error': {u'message': u'The request you have made requires authentication.', u'code': 401, u'title': u'Unauthorized'}}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_get_list_resources||DEBUG||making request with URI:/flavors/detail,{'service_type': 'compute', 'interface': 'public', 'region_name': u'RegionOne'}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_discover_flavors||ERROR||HttpError: status:401, response:{u'error': {u'message': u'The request you have made requires authentication.', u'code': 401, u'title': u'Unauthorized'}}||||requestID= invocationID= serviceName= serviceIP=

 

  1. Triggered VF Creation from VID portal (using VNF-API) with SNDC preload: VF Creation failed with error from multicloud.

Debug log file attached for SO-Openstack pod : VFCreation_SO_Openstack_pod_logs.txt

Log file attached from multicloud-ocata pod : VFCreation_Multicloud-ocata_pod_logs.txt

 

Snippet from SO-Openstack logs:

2019-08-22T04:23:20.279Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Making GET request to: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Request Headers: {Project=[c673af272d074170881559797f46b89d], Accept=[application/json], X-ONAP-RequestID=[5140aff8-5c26-4909-a443-84b8c36bff89], X-ONAP-InvocationID=[023572a9-79af-4802-9298-1265cff23e48], X-ONAP-PartnerName=[SO]}

2019-08-22T04:23:20.491Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Response from GET: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Response Headers: {Allow=[GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS], connection=[keep-alive], content-type=[text/html; charset=utf-8], Date=[Thu, 22 Aug 2019 04:23:20 GMT], Server=[openresty], transfer-encoding=[chunked], Vary=[Cookie], X-Frame-Options=[SAMEORIGIN]}<h1>Server Error (500)</h1>

 

Need your expertise in resolving this issue.

 

Thanks & Regards,

Sunil B

 

From: Multanen, Eric W <eric.w.multanen@...>
Sent: Wednesday, August 21, 2019 7:02 PM
To: onap-discuss@...; seshu.kumar.m@...; Sunilkumar Shivangouda Biradar <SB00577584@...>; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Per Seshu’s comment – yes, there is some apparent mismatch in the different log samples.

 

In the first log sample (down at the bottom) – it appears that configuration for using Multicloud via has been done (logs indicate usage of the Multicloud infrastructure workload API

http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

and messages are coming from org.onap.so.openstack.utils.MsoMulticloudUtils

 

In the more recent log sample, the logs coming from MsoHeatUtils show that the multicloud plugin in SO is not being used.

(ok – just spotted it – in the second case, the log indicates that the ‘orchestrator’ column for the cloud region is ‘null’ instead of ‘multicloud’)

 

 

The two key configs are:

  1. setting the SO BPMN to use the VNF API v2
  2. having ‘multicloud’ for the cloudregion in ‘orchestrator’ column of SO cloud_sites catalogdb table.

 

Sunil – to your recent question on the keystone url – when SO BPMN and the cloud region is configured as above, then the keystone url in SO is not used.   The authentication to the cloud region is

handled by the multicloud component – which goes back to the cloud registration process that includes the POST to /api/multicloud-titaniumcloud/v1/{{cloud-owner}}/{{cloud-region-id}}/registry

(and, the step of setting ‘multicloud’ in the ‘orchestrator’ column)

 

Eric

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of seshu kumar m
Sent: Wednesday, August 21, 2019 5:24 AM
To: onap-discuss@...; sb00577584@...; Multanen, Eric W <eric.w.multanen@...>; rene.robert@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Sunil

 

Did you change the orchestration type to Multicloud in SO, before trying this?

It seems there is some config mismatch issue with the intension and the actual execution from the logs.

 

Thanks and Regards,

M Seshu Kumar

Senior System Architect

Single OSS India Branch Department. S/W BU.

Huawei Technologies India Pvt. Ltd.

Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield

Bengaluru-560066, Karnataka.

Tel: + 91-80-49160700 , Mob: 9845355488

Company_logo

___________________________________________________________________________________________________

This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

-------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Sunilkumar Shivangouda Biradar
Sent: Wednesday, August 21, 2019 11:04 AM
To: Multanen, Eric W <eric.w.multanen@...>; onap-discuss@...; rene.robert@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Eric,

 

Thanks for reply, as mentioned in the second issue may I know the keystone url is proper  keystoneUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0

 

Because here I am getting responseCode as 401

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoCommonUtils - Config values RetryDelay:5 RetryCount:3  RetryCodes:504 ResponseCode:401

 

 

Thanks & Regards,

Sunil B

 

 

From: Multanen, Eric W <eric.w.multanen@...>
Sent: Tuesday, August 20, 2019 10:39 PM
To: Sunilkumar Shivangouda Biradar <SB00577584@...>; onap-discuss@...; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

This is what I’ve been using:  http://{{MSB_IP}}:{{MSB_PORT}}/api/multicloud-titaniumcloud/v1/{{cloud-owner}}/{{cloud-region-id}}/registry

 

From: Sunilkumar Shivangouda Biradar <SB00577584@...>
Sent: Tuesday, August 20, 2019 7:08 AM
To: onap-discuss@...; Multanen, Eric W <eric.w.multanen@...>; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Rene/Eric,

 

Thanks for reply, I followed the page which you suggested.

 

1.      Registering cloud site with multicloud as per document, but got 500 Internal server error.
               Found that there is different API “/api/multicloud/v1/MyCompanyName/INTEGRATION_CENTER/registry”, here I got 202 Unknown Status Code.
               Also tried with “/api/multicloud-titaniumcloud/v1/MyCompanyName/INTEGRATION_CENTER/registry, here I got 202 Accepted.
 
             May I know which API we need to use for registering? 

 

2.       In between I got to know that api changed from “MyCompanyName_INTEGRATION_CENTER/identity/v2.0” to “MyCompanyName/INTEGRATION_CENTER/identity/v2.0” for identity_url. 

                After this modification I got error as below

 

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - Found: CloudSite_.._jvsta6b_3c[regionId=RegionOne,identityServiceId=MC_KEYSTONE,cloudVersion=2.5,clli=RegionOne,cloudifyId=<null>,platform=<null>,orchestrator=<null>]

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - Found: CloudIdentity[id=MC_KEYSTONE,identityUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0,msoId=onap-tm5g-01,projectDomain=<null>,userDomain=<null>,adminTenant=service,memberRole=admin,tenantMetadata=true,identityServerType=KEYSTONE,identityAuthenticationType=USERNAME_PASSWORD]

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - keystoneUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoCommonUtils - Config values RetryDelay:5 RetryCount:3  RetryCodes:504 ResponseCode:401

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoHeatUtils - RA_CONNECTION_EXCEPTION 200 Openstack Exception on Token request:

org.onap.so.openstack.exceptions.MsoAdapterException: Authentication Failure: tenant=c673af272d074170881559797f46b89d,cloud=MC_KEYSTONE

        at org.onap.so.openstack.utils.MsoHeatUtils.getHeatClient(MsoHeatUtils.java:871)

        at org.onap.so.openstack.utils.MsoHeatUtils.queryStack(MsoHeatUtils.java:502)

        at org.onap.so.adapters.vnf.MsoVnfAdapterImpl.createVfModule(MsoVnfAdapterImpl.java:653)

 

 

Please suggest on this issue.

 

Thanks & Regards,

Sunil B

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Multanen, Eric W via Lists.Onap.Org
Sent: Monday, August 19, 2019 9:53 PM
To: onap-discuss@...; rene.robert@...; Sunilkumar Shivangouda Biradar <SB00577584@...>
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

I have the same suggestion – check that your cloud region has been setup and registered per the link.

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Rene Robert via Lists.Onap.Org
Sent: Monday, August 19, 2019 7:16 AM
To: onap-discuss@...; sb00577584@...; Multanen, Eric W <eric.w.multanen@...>
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

About cloud_site, there is that user-guide

 

https://onap.readthedocs.io/en/latest/guides/onap-user/cloud_site/index.html

 

maybe it could help

 

Best regards

 

 

Logo Orange

 

René Robert
«Open and Smart solutions for autOmating Network Services»
ORANGE/IMT/OLN/CNC/NARA/OSONS

 

Fixe : +33 2 96 07 39 29
Mobile : +33 6 74 78 68 43
rene.robert@...

 

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Sunilkumar Shivangouda Biradar
Envoyé : lundi 19 août 2019 12:38
À :
onap-discuss@...; eric.w.multanen@...
Objet : [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Team,

 

I am working on vFW usecase with HPA (ONAP version: Dublin)

 

Case 1:- Instantiated VM on openstack but not with specified flavors from OOF

 

I tried to create a VF module from VID using VNF-API and was able instantiate VM on openstack but not with the flavors which was suggested at oof_directives, instead it created the VM with the flavors provided in SDNC_preload and found from so-openstack log that SO was not calling multicloud  API “/api/multicloud/v1/CloudOwner/RegionOne/infra_workload”.

 

Case 2:- VM did not get instantiated, getting error.

 

https://wiki.onap.org/display/DW/Recap+of+Dublin+SO+Multicloud+Plugin+--%3E+Multicloud+Interactions

Got to know from wiki that for HPA we need not make any changes to cloud_site table of catalogdb. (which is leading to Case 1 above). Hence manually I modified orchestrator= “multicloud” for the region I’m using, as show in below table.

 

 

Post changing the cloud_site table I am able to see SO is calling the “/api/multicloud/v1/CloudOwner/RegionOne/infra_workload” API of multicloud.

But getting this below error from SO-openstack log(I made sure that no vf module with this name(vfwhpa_stack_test_24) exists in AAI before triggering vf module creation) :

 

2019-08-19T07:19:29.498Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Query multicloud HEAT stack: vfwhpa_stack_test_24 in tenant c673af272d074170881559797f46b89d

2019-08-19T07:19:29.499Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Multicloud Endpoint is: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

2019-08-19T07:19:29.505Z|| o.onap.so.logging.jaxrs.filter.JaxRsClientLogging - Could not Find Request ID Generating New One: /api/multicloud/v1/CloudOwner/RegionOne/infra_workload

2019-08-19T07:19:29.506Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Making GET request to: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Request Headers: {Project=[c673af272d074170881559797f46b89d], Accept=[application/json], X-ONAP-RequestID=[96718a17-4eeb-41db-b185-88f04799763e], X-ONAP-InvocationID=[bd58d3f1-ecc7-436f-88fb-378ed51a58e2], X-ONAP-PartnerName=[SO]}

2019-08-19T07:19:29.667Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Response from GET: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Response Headers: {Allow=[GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS], connection=[keep-alive], content-type=[text/html; charset=utf-8], Date=[Mon, 19 Aug 2019 07:19:29 GMT], Server=[openresty], transfer-encoding=[chunked], Vary=[Cookie], X-Frame-Options=[SAMEORIGIN]}{"template_type":"HEAT","workload_status_reason":"authenticate fails:CloudOwner, RegionOne, {\"error\":{\"message\":\"The request you have made requires authentication.\",\"code\":401,\"title\":\"Unauthorized\"}}","workload_status":"GET_FAILED","workload_id":""}

 

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Multicloud GET Response: org.apache.cxf.jaxrs.impl.ResponseImpl@6250c8cb

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - StackInfo to convert: {}

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - HeatStatus = FAILED msg = Internal Server Error

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Stack Status: FAILED

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Stack Status Message: Internal Server Error

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - Found Existing VDU, status=FAILED

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - RA_VNF_ALREADY_EXIST vfwhpa_stack_test_24 CloudOwner RegionOne c673af272d074170881559797f46b89d VDU queryVdu 300 VF Module vfwhpa_stack_test_24 already exists and is in FAILED state

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - Create VF: Deployment vfwhpa_stack_test_24 already exists and is in FAILED state in CloudOwner/RegionOne/c673af272d074170881559797f46b89d; requires manual intervention.

2019-08-19T07:19:29.679Z|| org.onap.so.adapters.vnf.BpelRestClient - Sending response to BPEL: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<vfModuleException>

    <messageId>dcfcc4e0-7723-473d-bfcb-dd8b9fe4ff2f-1566199169042</messageId>

    <category>INTERNAL</category>

    <message>Resource vfwhpa_stack_test_24 already exists in owner/cloud/tenant CloudOwner/RegionOne/c673af272d074170881559797f46b89d with ID </message>

   <rolledBack>true</rolledBack>

</vfModuleException>

 

 

Please suggest on this issue.

 

Thanks in advance.

 

Regards,

Sunil B

============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================

_________________________________________________________________________________________________________________________
 
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.

 

 

_________________________________________________________________________________________________________________________

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.
_________________________________________________________________________________________________________________________

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.


Re: [SO][OOF][MultiCloud] error while instantiating VF module

thierry.hardy@...
 

I tried this delete operation but it is not implemented

curl -X DELETE \

 http://msb.api.discovery.simpledemo.onap.org:30280/api/multicloud/v1/OPNFV/RegionOne \

  -H 'Accept: application/json' \

  -H 'Cache-Control: no-cache' \

  -H 'Content-Type: application/json' \

  -H 'Postman-Token: d3380ac7-205a-46d6-9ac3-ec1f929956a3' \

 

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

<html>

    <head>

        <title>Proxy error: 501 Method not implemented.</title>

    </head>

    <body>

       <h1>501 Method not implemented</h1>

        <p>The following error occurred:

            <br>

            <br>

            <strong>501 Method not implemented</strong>

        </p>

        <hr>Generated Fri, 23 Aug 2019 14:41:51 DST by Polipo on

        <em>WX-OR6178716.ad.francetelecom.fr:8185</em>.

    </body>

</html>

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Rene Robert via Lists.Onap.Org
Envoyé : vendredi 23 août 2019 14:25
À : Eric W <eric. w. multanen@intel. com> Multanen; sb00577584@...; Seshu m; Yang Bin <bin. yang@windriver. com>; onap-discuss; HARDY Thierry TGI/OLN
Objet : Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

maybe we should use the delete operation (see: unregister vim in  http://docs.onap.org/en/dublin/submodules/multicloud/framework.git/docs/MultiCloud-APIv1-Specification.html)

 

then the post operation to register the vim

 

Envoyé depuis mon smartphone Xperia de Sony



---- thierry.hardy via Lists.Onap.Org a écrit ----

Hi

I’m from Orange in the same team than René.

I have performed a modification of our installation project to integrate multicloud. And since this morning, the instantiation is successfull.

Yesterday, I met similar errors than yours due a wrong declaration of tenant via ESR. I forgot to indicate v3 in the service-url field.

 

So I changed yesterday this wrong configuration (via the right esr API) , but I was not able to overwrite the multicloud registration doing:

curl -X POST \

  http://msb.api.discovery.simpledemo.onap.org:30280/api/multicloud/v1/OPNFV/RegionOne/registry \

  -H 'Accept: application/json' \

  -H 'Cache-Control: no-cache' \

  -H 'Content-Type: application/json' \

  -H 'Postman-Token: 2b32db39-603b-4176-98f7-f1ee26675f48' \

  -H 'defaultTenant: onap-dublin-daily-vnfs-ci'

 

I don’t save the logs but the token error was still visible in logs of multicloud pike pod.

So I looked for an API request to delete registry action but without success. The one from ONAP documentation is not working.

 

As on this tenant, we perform a daily installation of ONAP, this morning, with the right configuration set in multicloud pods from the installation part (executed during the night), the instantiation was successful.

Regards

Thierry

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Multanen, Eric W
Envoyé : jeudi 22 août 2019 19:37
À : onap-discuss@...; sb00577584@...; seshu.kumar.m@...; ROBERT René TGI/OLN; bin.yang@...
Objet : Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

From the SO config side – looks like what you’ve configured is ok.

 

The multicloud logs – both on registration and vf module create indicate that multicloud is having trouble making requests to your cloud.

 

Do the user credentials you’re using for that cloud have the level of authorization to make these requests?  Have you verifying manually from a CLI perhaps?

 

It appears the main issue at the moment is the multicloud-ocata plugin talking to your Stein cloud.  First guess is something to do with the credentials.  

 

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Sunilkumar Shivangouda Biradar
Sent: Wednesday, August 21, 2019 10:44 PM
To: Multanen, Eric W <eric.w.multanen@...>; onap-discuss@...; seshu.kumar.m@...; rene.robert@...; bin.yang@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Seshu/Eric,

 

As per discussion we had during yesterday’s SO-Weekly call, sharing proper steps followed and fresh logs.

 

Steps followed:

  1. Cloud region created with these details. (Please refer to AAI_Cloud_Details.txt attached)   

 

Note: we are using Stein version (3.19.0) of openstack.

 

  1. Modified the identity_services table of catalogdb with Identity_url =”http://msb-iag.onap:80/api/multicloud/v0/CloudOwner_RegionOne/identity/v2.0”.
  2. Modified the cloud_sites table as shown below

 

 

  1. Did Setting of SO BPMN to use the VNF API v2 (post changing this, deleted the so-bpmn pod and the pod restarted successfully)

 

                    vnf:

                       endpoint: http://so-openstack-adapter.onap:8087/services/VnfAdapter

                       rest:

                         endpoint: http://so-openstack-adapter.onap:8087/services/rest/v2/vnfs

 

 

  1. Tried to register the cloud with multicloud using following API

curl -vvv -X POST http://10.211.1.20:30280/api/multicloud/v1/CloudOwner/RegionOne/registry -H 'Accept: application/json' -H 'Cache-Control: no-cache' -H 'Content-Type: application/json'

 

Note: did not understand why multicloud added "identity-url": "http://msb-iag.onap:80/api/multicloud-ocata/v0/CloudOwner_RegionOne/identity/v2.0"  to the AAI cloud region detail (we are using Stein version (3.19.0) of openstack)

 

I see errors in multicloud-ocata pod as shown below(full log file attached : multicloud-ocata_pod_logs.txt)

                2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_get_list_resources||DEBUG||making request with URI:projects,{'service_type': 'identity', 'interface': 'public'}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_discover_tenants||ERROR||HttpError: status:401, response:{u'error': {u'message': u'The request you have made requires authentication.', u'code': 401, u'title': u'Unauthorized'}}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_get_list_resources||DEBUG||making request with URI:/flavors/detail,{'service_type': 'compute', 'interface': 'public', 'region_name': u'RegionOne'}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_discover_flavors||ERROR||HttpError: status:401, response:{u'error': {u'message': u'The request you have made requires authentication.', u'code': 401, u'title': u'Unauthorized'}}||||requestID= invocationID= serviceName= serviceIP=

 

  1. Triggered VF Creation from VID portal (using VNF-API) with SNDC preload: VF Creation failed with error from multicloud.

Debug log file attached for SO-Openstack pod : VFCreation_SO_Openstack_pod_logs.txt

Log file attached from multicloud-ocata pod : VFCreation_Multicloud-ocata_pod_logs.txt

 

Snippet from SO-Openstack logs:

2019-08-22T04:23:20.279Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Making GET request to: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Request Headers: {Project=[c673af272d074170881559797f46b89d], Accept=[application/json], X-ONAP-RequestID=[5140aff8-5c26-4909-a443-84b8c36bff89], X-ONAP-InvocationID=[023572a9-79af-4802-9298-1265cff23e48], X-ONAP-PartnerName=[SO]}

2019-08-22T04:23:20.491Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Response from GET: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Response Headers: {Allow=[GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS], connection=[keep-alive], content-type=[text/html; charset=utf-8], Date=[Thu, 22 Aug 2019 04:23:20 GMT], Server=[openresty], transfer-encoding=[chunked], Vary=[Cookie], X-Frame-Options=[SAMEORIGIN]}<h1>Server Error (500)</h1>

 

Need your expertise in resolving this issue.

 

Thanks & Regards,

Sunil B

 

From: Multanen, Eric W <eric.w.multanen@...>
Sent: Wednesday, August 21, 2019 7:02 PM
To: onap-discuss@...; seshu.kumar.m@...; Sunilkumar Shivangouda Biradar <SB00577584@...>; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Per Seshu’s comment – yes, there is some apparent mismatch in the different log samples.

 

In the first log sample (down at the bottom) – it appears that configuration for using Multicloud via has been done (logs indicate usage of the Multicloud infrastructure workload API

http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

and messages are coming from org.onap.so.openstack.utils.MsoMulticloudUtils

 

In the more recent log sample, the logs coming from MsoHeatUtils show that the multicloud plugin in SO is not being used.

(ok – just spotted it – in the second case, the log indicates that the ‘orchestrator’ column for the cloud region is ‘null’ instead of ‘multicloud’)

 

 

The two key configs are:

  1. setting the SO BPMN to use the VNF API v2
  2. having ‘multicloud’ for the cloudregion in ‘orchestrator’ column of SO cloud_sites catalogdb table.

 

Sunil – to your recent question on the keystone url – when SO BPMN and the cloud region is configured as above, then the keystone url in SO is not used.   The authentication to the cloud region is

handled by the multicloud component – which goes back to the cloud registration process that includes the POST to /api/multicloud-titaniumcloud/v1/{{cloud-owner}}/{{cloud-region-id}}/registry

(and, the step of setting ‘multicloud’ in the ‘orchestrator’ column)

 

Eric

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of seshu kumar m
Sent: Wednesday, August 21, 2019 5:24 AM
To: onap-discuss@...; sb00577584@...; Multanen, Eric W <eric.w.multanen@...>; rene.robert@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Sunil

 

Did you change the orchestration type to Multicloud in SO, before trying this?

It seems there is some config mismatch issue with the intension and the actual execution from the logs.

 

Thanks and Regards,

M Seshu Kumar

Senior System Architect

Single OSS India Branch Department. S/W BU.

Huawei Technologies India Pvt. Ltd.

Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield

Bengaluru-560066, Karnataka.

Tel: + 91-80-49160700 , Mob: 9845355488

Company_logo

___________________________________________________________________________________________________

This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

-------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Sunilkumar Shivangouda Biradar
Sent: Wednesday, August 21, 2019 11:04 AM
To: Multanen, Eric W <eric.w.multanen@...>; onap-discuss@...; rene.robert@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Eric,

 

Thanks for reply, as mentioned in the second issue may I know the keystone url is proper  keystoneUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0

 

Because here I am getting responseCode as 401

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoCommonUtils - Config values RetryDelay:5 RetryCount:3  RetryCodes:504 ResponseCode:401

 

 

Thanks & Regards,

Sunil B

 

 

From: Multanen, Eric W <eric.w.multanen@...>
Sent: Tuesday, August 20, 2019 10:39 PM
To: Sunilkumar Shivangouda Biradar <SB00577584@...>; onap-discuss@...; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

This is what I’ve been using:  http://{{MSB_IP}}:{{MSB_PORT}}/api/multicloud-titaniumcloud/v1/{{cloud-owner}}/{{cloud-region-id}}/registry

 

From: Sunilkumar Shivangouda Biradar <SB00577584@...>
Sent: Tuesday, August 20, 2019 7:08 AM
To: onap-discuss@...; Multanen, Eric W <eric.w.multanen@...>; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Rene/Eric,

 

Thanks for reply, I followed the page which you suggested.

 

1.      Registering cloud site with multicloud as per document, but got 500 Internal server error.
               Found that there is different API “/api/multicloud/v1/MyCompanyName/INTEGRATION_CENTER/registry”, here I got 202 Unknown Status Code.
               Also tried with “/api/multicloud-titaniumcloud/v1/MyCompanyName/INTEGRATION_CENTER/registry, here I got 202 Accepted.
 
             May I know which API we need to use for registering? 

 

2.       In between I got to know that api changed from “MyCompanyName_INTEGRATION_CENTER/identity/v2.0” to “MyCompanyName/INTEGRATION_CENTER/identity/v2.0” for identity_url. 

                After this modification I got error as below

 

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - Found: CloudSite_.._jvsta6b_3c[regionId=RegionOne,identityServiceId=MC_KEYSTONE,cloudVersion=2.5,clli=RegionOne,cloudifyId=<null>,platform=<null>,orchestrator=<null>]

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - Found: CloudIdentity[id=MC_KEYSTONE,identityUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0,msoId=onap-tm5g-01,projectDomain=<null>,userDomain=<null>,adminTenant=service,memberRole=admin,tenantMetadata=true,identityServerType=KEYSTONE,identityAuthenticationType=USERNAME_PASSWORD]

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - keystoneUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoCommonUtils - Config values RetryDelay:5 RetryCount:3  RetryCodes:504 ResponseCode:401

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoHeatUtils - RA_CONNECTION_EXCEPTION 200 Openstack Exception on Token request:

org.onap.so.openstack.exceptions.MsoAdapterException: Authentication Failure: tenant=c673af272d074170881559797f46b89d,cloud=MC_KEYSTONE

        at org.onap.so.openstack.utils.MsoHeatUtils.getHeatClient(MsoHeatUtils.java:871)

        at org.onap.so.openstack.utils.MsoHeatUtils.queryStack(MsoHeatUtils.java:502)

        at org.onap.so.adapters.vnf.MsoVnfAdapterImpl.createVfModule(MsoVnfAdapterImpl.java:653)

 

 

Please suggest on this issue.

 

Thanks & Regards,

Sunil B

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Multanen, Eric W via Lists.Onap.Org
Sent: Monday, August 19, 2019 9:53 PM
To: onap-discuss@...; rene.robert@...; Sunilkumar Shivangouda Biradar <SB00577584@...>
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

I have the same suggestion – check that your cloud region has been setup and registered per the link.

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Rene Robert via Lists.Onap.Org
Sent: Monday, August 19, 2019 7:16 AM
To: onap-discuss@...; sb00577584@...; Multanen, Eric W <eric.w.multanen@...>
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

About cloud_site, there is that user-guide

 

https://onap.readthedocs.io/en/latest/guides/onap-user/cloud_site/index.html

 

maybe it could help

 

Best regards

 

 

Logo Orange

 

René Robert
«Open and Smart solutions for autOmating Network Services»
ORANGE/IMT/OLN/CNC/NARA/OSONS

 

Fixe : +33 2 96 07 39 29
Mobile : +33 6 74 78 68 43
rene.robert@...

 

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Sunilkumar Shivangouda Biradar
Envoyé : lundi 19 août 2019 12:38
À :
onap-discuss@...; eric.w.multanen@...
Objet : [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Team,

 

I am working on vFW usecase with HPA (ONAP version: Dublin)

 

Case 1:- Instantiated VM on openstack but not with specified flavors from OOF

 

I tried to create a VF module from VID using VNF-API and was able instantiate VM on openstack but not with the flavors which was suggested at oof_directives, instead it created the VM with the flavors provided in SDNC_preload and found from so-openstack log that SO was not calling multicloud  API “/api/multicloud/v1/CloudOwner/RegionOne/infra_workload”.

 

Case 2:- VM did not get instantiated, getting error.

 

https://wiki.onap.org/display/DW/Recap+of+Dublin+SO+Multicloud+Plugin+--%3E+Multicloud+Interactions

Got to know from wiki that for HPA we need not make any changes to cloud_site table of catalogdb. (which is leading to Case 1 above). Hence manually I modified orchestrator= “multicloud” for the region I’m using, as show in below table.

 

 

Post changing the cloud_site table I am able to see SO is calling the “/api/multicloud/v1/CloudOwner/RegionOne/infra_workload” API of multicloud.

But getting this below error from SO-openstack log(I made sure that no vf module with this name(vfwhpa_stack_test_24) exists in AAI before triggering vf module creation) :

 

2019-08-19T07:19:29.498Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Query multicloud HEAT stack: vfwhpa_stack_test_24 in tenant c673af272d074170881559797f46b89d

2019-08-19T07:19:29.499Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Multicloud Endpoint is: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

2019-08-19T07:19:29.505Z|| o.onap.so.logging.jaxrs.filter.JaxRsClientLogging - Could not Find Request ID Generating New One: /api/multicloud/v1/CloudOwner/RegionOne/infra_workload

2019-08-19T07:19:29.506Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Making GET request to: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Request Headers: {Project=[c673af272d074170881559797f46b89d], Accept=[application/json], X-ONAP-RequestID=[96718a17-4eeb-41db-b185-88f04799763e], X-ONAP-InvocationID=[bd58d3f1-ecc7-436f-88fb-378ed51a58e2], X-ONAP-PartnerName=[SO]}

2019-08-19T07:19:29.667Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Response from GET: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Response Headers: {Allow=[GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS], connection=[keep-alive], content-type=[text/html; charset=utf-8], Date=[Mon, 19 Aug 2019 07:19:29 GMT], Server=[openresty], transfer-encoding=[chunked], Vary=[Cookie], X-Frame-Options=[SAMEORIGIN]}{"template_type":"HEAT","workload_status_reason":"authenticate fails:CloudOwner, RegionOne, {\"error\":{\"message\":\"The request you have made requires authentication.\",\"code\":401,\"title\":\"Unauthorized\"}}","workload_status":"GET_FAILED","workload_id":""}

 

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Multicloud GET Response: org.apache.cxf.jaxrs.impl.ResponseImpl@6250c8cb

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - StackInfo to convert: {}

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - HeatStatus = FAILED msg = Internal Server Error

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Stack Status: FAILED

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Stack Status Message: Internal Server Error

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - Found Existing VDU, status=FAILED

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - RA_VNF_ALREADY_EXIST vfwhpa_stack_test_24 CloudOwner RegionOne c673af272d074170881559797f46b89d VDU queryVdu 300 VF Module vfwhpa_stack_test_24 already exists and is in FAILED state

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - Create VF: Deployment vfwhpa_stack_test_24 already exists and is in FAILED state in CloudOwner/RegionOne/c673af272d074170881559797f46b89d; requires manual intervention.

2019-08-19T07:19:29.679Z|| org.onap.so.adapters.vnf.BpelRestClient - Sending response to BPEL: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<vfModuleException>

    <messageId>dcfcc4e0-7723-473d-bfcb-dd8b9fe4ff2f-1566199169042</messageId>

    <category>INTERNAL</category>

    <message>Resource vfwhpa_stack_test_24 already exists in owner/cloud/tenant CloudOwner/RegionOne/c673af272d074170881559797f46b89d with ID </message>

   <rolledBack>true</rolledBack>

</vfModuleException>

 

 

Please suggest on this issue.

 

Thanks in advance.

 

Regards,

Sunil B

============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================

_________________________________________________________________________________________________________________________
 
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.

 

 

_________________________________________________________________________________________________________________________
 
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.
_________________________________________________________________________________________________________________________
 
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.

_________________________________________________________________________________________________________________________

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.


Re: [SO][OOF][MultiCloud] error while instantiating VF module

Rene Robert <rene.robert@...>
 

maybe we should use the delete operation (see: unregister vim in  http://docs.onap.org/en/dublin/submodules/multicloud/framework.git/docs/MultiCloud-APIv1-Specification.html)


then the post operation to register the vim



Envoyé depuis mon smartphone Xperia de Sony



---- thierry.hardy via Lists.Onap.Org a écrit ----

Hi

I’m from Orange in the same team than René.

I have performed a modification of our installation project to integrate multicloud. And since this morning, the instantiation is successfull.

Yesterday, I met similar errors than yours due a wrong declaration of tenant via ESR. I forgot to indicate v3 in the service-url field.

 

So I changed yesterday this wrong configuration (via the right esr API) , but I was not able to overwrite the multicloud registration doing:

curl -X POST \

  http://msb.api.discovery.simpledemo.onap.org:30280/api/multicloud/v1/OPNFV/RegionOne/registry \

  -H 'Accept: application/json' \

  -H 'Cache-Control: no-cache' \

  -H 'Content-Type: application/json' \

  -H 'Postman-Token: 2b32db39-603b-4176-98f7-f1ee26675f48' \

  -H 'defaultTenant: onap-dublin-daily-vnfs-ci'

 

I don’t save the logs but the token error was still visible in logs of multicloud pike pod.

So I looked for an API request to delete registry action but without success. The one from ONAP documentation is not working.

 

As on this tenant, we perform a daily installation of ONAP, this morning, with the right configuration set in multicloud pods from the installation part (executed during the night), the instantiation was successful.

Regards

Thierry

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Multanen, Eric W
Envoyé : jeudi 22 août 2019 19:37
À : onap-discuss@...; sb00577584@...; seshu.kumar.m@...; ROBERT René TGI/OLN; bin.yang@...
Objet : Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

From the SO config side – looks like what you’ve configured is ok.

 

The multicloud logs – both on registration and vf module create indicate that multicloud is having trouble making requests to your cloud.

 

Do the user credentials you’re using for that cloud have the level of authorization to make these requests?  Have you verifying manually from a CLI perhaps?

 

It appears the main issue at the moment is the multicloud-ocata plugin talking to your Stein cloud.  First guess is something to do with the credentials.  

 

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Sunilkumar Shivangouda Biradar
Sent: Wednesday, August 21, 2019 10:44 PM
To: Multanen, Eric W <eric.w.multanen@...>; onap-discuss@...; seshu.kumar.m@...; rene.robert@...; bin.yang@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Seshu/Eric,

 

As per discussion we had during yesterday’s SO-Weekly call, sharing proper steps followed and fresh logs.

 

Steps followed:

  1. Cloud region created with these details. (Please refer to AAI_Cloud_Details.txt attached)   

 

Note: we are using Stein version (3.19.0) of openstack.

 

  1. Modified the identity_services table of catalogdb with Identity_url =”http://msb-iag.onap:80/api/multicloud/v0/CloudOwner_RegionOne/identity/v2.0”.
  2. Modified the cloud_sites table as shown below

 

 

  1. Did Setting of SO BPMN to use the VNF API v2 (post changing this, deleted the so-bpmn pod and the pod restarted successfully)

 

                    vnf:

                       endpoint: http://so-openstack-adapter.onap:8087/services/VnfAdapter

                       rest:

                         endpoint: http://so-openstack-adapter.onap:8087/services/rest/v2/vnfs

 

 

  1. Tried to register the cloud with multicloud using following API

curl -vvv -X POST http://10.211.1.20:30280/api/multicloud/v1/CloudOwner/RegionOne/registry -H 'Accept: application/json' -H 'Cache-Control: no-cache' -H 'Content-Type: application/json'

 

Note: did not understand why multicloud added "identity-url": "http://msb-iag.onap:80/api/multicloud-ocata/v0/CloudOwner_RegionOne/identity/v2.0"  to the AAI cloud region detail (we are using Stein version (3.19.0) of openstack)

 

I see errors in multicloud-ocata pod as shown below(full log file attached : multicloud-ocata_pod_logs.txt)

                2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_get_list_resources||DEBUG||making request with URI:projects,{'service_type': 'identity', 'interface': 'public'}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_discover_tenants||ERROR||HttpError: status:401, response:{u'error': {u'message': u'The request you have made requires authentication.', u'code': 401, u'title': u'Unauthorized'}}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_get_list_resources||DEBUG||making request with URI:/flavors/detail,{'service_type': 'compute', 'interface': 'public', 'region_name': u'RegionOne'}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_discover_flavors||ERROR||HttpError: status:401, response:{u'error': {u'message': u'The request you have made requires authentication.', u'code': 401, u'title': u'Unauthorized'}}||||requestID= invocationID= serviceName= serviceIP=

 

  1. Triggered VF Creation from VID portal (using VNF-API) with SNDC preload: VF Creation failed with error from multicloud.

Debug log file attached for SO-Openstack pod : VFCreation_SO_Openstack_pod_logs.txt

Log file attached from multicloud-ocata pod : VFCreation_Multicloud-ocata_pod_logs.txt

 

Snippet from SO-Openstack logs:

2019-08-22T04:23:20.279Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Making GET request to: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Request Headers: {Project=[c673af272d074170881559797f46b89d], Accept=[application/json], X-ONAP-RequestID=[5140aff8-5c26-4909-a443-84b8c36bff89], X-ONAP-InvocationID=[023572a9-79af-4802-9298-1265cff23e48], X-ONAP-PartnerName=[SO]}

2019-08-22T04:23:20.491Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Response from GET: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Response Headers: {Allow=[GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS], connection=[keep-alive], content-type=[text/html; charset=utf-8], Date=[Thu, 22 Aug 2019 04:23:20 GMT], Server=[openresty], transfer-encoding=[chunked], Vary=[Cookie], X-Frame-Options=[SAMEORIGIN]}<h1>Server Error (500)</h1>

 

Need your expertise in resolving this issue.

 

Thanks & Regards,

Sunil B

 

From: Multanen, Eric W <eric.w.multanen@...>
Sent: Wednesday, August 21, 2019 7:02 PM
To: onap-discuss@...; seshu.kumar.m@...; Sunilkumar Shivangouda Biradar <SB00577584@...>; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Per Seshu’s comment – yes, there is some apparent mismatch in the different log samples.

 

In the first log sample (down at the bottom) – it appears that configuration for using Multicloud via has been done (logs indicate usage of the Multicloud infrastructure workload API

http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

and messages are coming from org.onap.so.openstack.utils.MsoMulticloudUtils

 

In the more recent log sample, the logs coming from MsoHeatUtils show that the multicloud plugin in SO is not being used.

(ok – just spotted it – in the second case, the log indicates that the ‘orchestrator’ column for the cloud region is ‘null’ instead of ‘multicloud’)

 

 

The two key configs are:

  1. setting the SO BPMN to use the VNF API v2
  2. having ‘multicloud’ for the cloudregion in ‘orchestrator’ column of SO cloud_sites catalogdb table.

 

Sunil – to your recent question on the keystone url – when SO BPMN and the cloud region is configured as above, then the keystone url in SO is not used.   The authentication to the cloud region is

handled by the multicloud component – which goes back to the cloud registration process that includes the POST to /api/multicloud-titaniumcloud/v1/{{cloud-owner}}/{{cloud-region-id}}/registry

(and, the step of setting ‘multicloud’ in the ‘orchestrator’ column)

 

Eric

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of seshu kumar m
Sent: Wednesday, August 21, 2019 5:24 AM
To: onap-discuss@...; sb00577584@...; Multanen, Eric W <eric.w.multanen@...>; rene.robert@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Sunil

 

Did you change the orchestration type to Multicloud in SO, before trying this?

It seems there is some config mismatch issue with the intension and the actual execution from the logs.

 

Thanks and Regards,

M Seshu Kumar

Senior System Architect

Single OSS India Branch Department. S/W BU.

Huawei Technologies India Pvt. Ltd.

Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield

Bengaluru-560066, Karnataka.

Tel: + 91-80-49160700 , Mob: 9845355488

Company_logo

___________________________________________________________________________________________________

This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

-------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Sunilkumar Shivangouda Biradar
Sent: Wednesday, August 21, 2019 11:04 AM
To: Multanen, Eric W <eric.w.multanen@...>; onap-discuss@...; rene.robert@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Eric,

 

Thanks for reply, as mentioned in the second issue may I know the keystone url is proper  keystoneUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0

 

Because here I am getting responseCode as 401

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoCommonUtils - Config values RetryDelay:5 RetryCount:3  RetryCodes:504 ResponseCode:401

 

 

Thanks & Regards,

Sunil B

 

 

From: Multanen, Eric W <eric.w.multanen@...>
Sent: Tuesday, August 20, 2019 10:39 PM
To: Sunilkumar Shivangouda Biradar <SB00577584@...>; onap-discuss@...; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

This is what I’ve been using:  http://{{MSB_IP}}:{{MSB_PORT}}/api/multicloud-titaniumcloud/v1/{{cloud-owner}}/{{cloud-region-id}}/registry

 

From: Sunilkumar Shivangouda Biradar <SB00577584@...>
Sent: Tuesday, August 20, 2019 7:08 AM
To: onap-discuss@...; Multanen, Eric W <eric.w.multanen@...>; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Rene/Eric,

 

Thanks for reply, I followed the page which you suggested.

 

1.      Registering cloud site with multicloud as per document, but got 500 Internal server error.
               Found that there is different API “/api/multicloud/v1/MyCompanyName/INTEGRATION_CENTER/registry”, here I got 202 Unknown Status Code.
               Also tried with “/api/multicloud-titaniumcloud/v1/MyCompanyName/INTEGRATION_CENTER/registry, here I got 202 Accepted.
 
             May I know which API we need to use for registering? 

 

2.       In between I got to know that api changed from “MyCompanyName_INTEGRATION_CENTER/identity/v2.0” to “MyCompanyName/INTEGRATION_CENTER/identity/v2.0” for identity_url. 

                After this modification I got error as below

 

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - Found: CloudSite_.._jvsta6b_3c[regionId=RegionOne,identityServiceId=MC_KEYSTONE,cloudVersion=2.5,clli=RegionOne,cloudifyId=<null>,platform=<null>,orchestrator=<null>]

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - Found: CloudIdentity[id=MC_KEYSTONE,identityUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0,msoId=onap-tm5g-01,projectDomain=<null>,userDomain=<null>,adminTenant=service,memberRole=admin,tenantMetadata=true,identityServerType=KEYSTONE,identityAuthenticationType=USERNAME_PASSWORD]

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - keystoneUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoCommonUtils - Config values RetryDelay:5 RetryCount:3  RetryCodes:504 ResponseCode:401

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoHeatUtils - RA_CONNECTION_EXCEPTION 200 Openstack Exception on Token request:

org.onap.so.openstack.exceptions.MsoAdapterException: Authentication Failure: tenant=c673af272d074170881559797f46b89d,cloud=MC_KEYSTONE

        at org.onap.so.openstack.utils.MsoHeatUtils.getHeatClient(MsoHeatUtils.java:871)

        at org.onap.so.openstack.utils.MsoHeatUtils.queryStack(MsoHeatUtils.java:502)

        at org.onap.so.adapters.vnf.MsoVnfAdapterImpl.createVfModule(MsoVnfAdapterImpl.java:653)

 

 

Please suggest on this issue.

 

Thanks & Regards,

Sunil B

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Multanen, Eric W via Lists.Onap.Org
Sent: Monday, August 19, 2019 9:53 PM
To: onap-discuss@...; rene.robert@...; Sunilkumar Shivangouda Biradar <SB00577584@...>
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

I have the same suggestion – check that your cloud region has been setup and registered per the link.

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Rene Robert via Lists.Onap.Org
Sent: Monday, August 19, 2019 7:16 AM
To: onap-discuss@...; sb00577584@...; Multanen, Eric W <eric.w.multanen@...>
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

About cloud_site, there is that user-guide

 

https://onap.readthedocs.io/en/latest/guides/onap-user/cloud_site/index.html

 

maybe it could help

 

Best regards

 

 

Logo Orange

 

René Robert
«Open and Smart solutions for autOmating Network Services»
ORANGE/IMT/OLN/CNC/NARA/OSONS

 

Fixe : +33 2 96 07 39 29
Mobile : +33 6 74 78 68 43
rene.robert@...

 

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Sunilkumar Shivangouda Biradar
Envoyé : lundi 19 août 2019 12:38
À :
onap-discuss@...; eric.w.multanen@...
Objet : [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Team,

 

I am working on vFW usecase with HPA (ONAP version: Dublin)

 

Case 1:- Instantiated VM on openstack but not with specified flavors from OOF

 

I tried to create a VF module from VID using VNF-API and was able instantiate VM on openstack but not with the flavors which was suggested at oof_directives, instead it created the VM with the flavors provided in SDNC_preload and found from so-openstack log that SO was not calling multicloud  API “/api/multicloud/v1/CloudOwner/RegionOne/infra_workload”.

 

Case 2:- VM did not get instantiated, getting error.

 

https://wiki.onap.org/display/DW/Recap+of+Dublin+SO+Multicloud+Plugin+--%3E+Multicloud+Interactions

Got to know from wiki that for HPA we need not make any changes to cloud_site table of catalogdb. (which is leading to Case 1 above). Hence manually I modified orchestrator= “multicloud” for the region I’m using, as show in below table.

 

 

Post changing the cloud_site table I am able to see SO is calling the “/api/multicloud/v1/CloudOwner/RegionOne/infra_workload” API of multicloud.

But getting this below error from SO-openstack log(I made sure that no vf module with this name(vfwhpa_stack_test_24) exists in AAI before triggering vf module creation) :

 

2019-08-19T07:19:29.498Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Query multicloud HEAT stack: vfwhpa_stack_test_24 in tenant c673af272d074170881559797f46b89d

2019-08-19T07:19:29.499Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Multicloud Endpoint is: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

2019-08-19T07:19:29.505Z|| o.onap.so.logging.jaxrs.filter.JaxRsClientLogging - Could not Find Request ID Generating New One: /api/multicloud/v1/CloudOwner/RegionOne/infra_workload

2019-08-19T07:19:29.506Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Making GET request to: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Request Headers: {Project=[c673af272d074170881559797f46b89d], Accept=[application/json], X-ONAP-RequestID=[96718a17-4eeb-41db-b185-88f04799763e], X-ONAP-InvocationID=[bd58d3f1-ecc7-436f-88fb-378ed51a58e2], X-ONAP-PartnerName=[SO]}

2019-08-19T07:19:29.667Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Response from GET: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Response Headers: {Allow=[GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS], connection=[keep-alive], content-type=[text/html; charset=utf-8], Date=[Mon, 19 Aug 2019 07:19:29 GMT], Server=[openresty], transfer-encoding=[chunked], Vary=[Cookie], X-Frame-Options=[SAMEORIGIN]}{"template_type":"HEAT","workload_status_reason":"authenticate fails:CloudOwner, RegionOne, {\"error\":{\"message\":\"The request you have made requires authentication.\",\"code\":401,\"title\":\"Unauthorized\"}}","workload_status":"GET_FAILED","workload_id":""}

 

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Multicloud GET Response: org.apache.cxf.jaxrs.impl.ResponseImpl@6250c8cb

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - StackInfo to convert: {}

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - HeatStatus = FAILED msg = Internal Server Error

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Stack Status: FAILED

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Stack Status Message: Internal Server Error

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - Found Existing VDU, status=FAILED

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - RA_VNF_ALREADY_EXIST vfwhpa_stack_test_24 CloudOwner RegionOne c673af272d074170881559797f46b89d VDU queryVdu 300 VF Module vfwhpa_stack_test_24 already exists and is in FAILED state

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - Create VF: Deployment vfwhpa_stack_test_24 already exists and is in FAILED state in CloudOwner/RegionOne/c673af272d074170881559797f46b89d; requires manual intervention.

2019-08-19T07:19:29.679Z|| org.onap.so.adapters.vnf.BpelRestClient - Sending response to BPEL: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<vfModuleException>

    <messageId>dcfcc4e0-7723-473d-bfcb-dd8b9fe4ff2f-1566199169042</messageId>

    <category>INTERNAL</category>

    <message>Resource vfwhpa_stack_test_24 already exists in owner/cloud/tenant CloudOwner/RegionOne/c673af272d074170881559797f46b89d with ID </message>

   <rolledBack>true</rolledBack>

</vfModuleException>

 

 

Please suggest on this issue.

 

Thanks in advance.

 

Regards,

Sunil B

============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================

_________________________________________________________________________________________________________________________
 
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.

 

 

_________________________________________________________________________________________________________________________

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.
_________________________________________________________________________________________________________________________

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.


Re: [dcaegen2] docker image dependency chart

Paul Vaduva
 

Kind reminder. Can someone from the DCAE team please check the dcaegen2 docker images dependencies list ?

 

Thanks you very much,

Paul Vaduva

 

From: Paul Vaduva
Sent: Monday, July 22, 2019 12:01 PM
To: onap-discuss@...
Cc: vv770d@...; 'Jessica Wagantall' <jwagantall@...>; 'Jim Baker' <jbaker@...>; 'Kenny Paul' <kpaul@...>; Cristina Pauna <Cristina.Pauna@...>
Subject: [onap-discuss][dcaegen2] docker image dependency chart

 

Hi dcaegen2 team

 

I am Paul Vaduva and I am part of the dockerhub migration effort together with Linux Foundation, as presented in various meetings at the DDF in June and anounced in multiple TSC meetings we need to create a dependency chart of docker images for every ONAP project before the migration happens in order for it to run smoothly according to Linux Foundation. As the team who is working on the dcaegen2 project you are the ones to ask about this docker images dependency list. However because your time is preciouse and there is a constant need of resources, I started this effort to create the dependency chart of all the docker images for all the project. Due to the multitude of docker iamges the manual process is tedious at best so I used an automated text parser to make a best effort list which is not complete and cannot be due to multiple inconsistent type of formated text output in docker build jobs logs. However it's a starting point and since each tech team should have the final work I invite you to have a look at the dependency list for dcaegen2 porject and give input in some form of your choosing (comments, edits, reply to this email, etc.) here:

https://wiki.onap.org/display/DW/Docker+images+dependency+list

You can see the list of docker images dependencies for each project in a roughly form like this:

1 --> 2 --> 3 ... --> n

where 1 is the dependency for the image (what you find in the FROM clause of a Dcokerfile), 2 is the dependent image (the name of the image that your project builds) and form 3 onward there are usually other tags of the same proejct image.

The previous wiki page is just a way to centralize the information regarding docker iamges dependency chart.

As Martial (PTL of clamp project) mentioned you can intruduce in the list the docker-compose dependencies (They are usually upstream project so already in dockerhub but better check them as well).

 

Thank you,

Paul


This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Enea may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, a mended, lost or destroyed, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Anyone who communicates with us by email accepts these risks.


Re: [logging] docker image dependency chart

Paul Vaduva
 

Kind reminder, Can someone from the logging team please check that the docker images dependencies are correct and complete ?

 

Thanks you very much,

Paul Vaduva

 

From: Paul Vaduva
Sent: Monday, July 22, 2019 11:58 AM
To: onap-discuss@...
Cc: frank.obrien@...; 'Jessica Wagantall' <jwagantall@...>; 'Jim Baker' <jbaker@...>; 'Kenny Paul' <kpaul@...>; Cristina Pauna <Cristina.Pauna@...>
Subject: [onap-discuss][logging] docker image dependency chart

 

Hi logging team

 

I am Paul Vaduva and I am part of the dockerhub migration effort together with Linux Foundation, as presented in various meetings at the DDF in June and anounced in multiple TSC meetings we need to create a dependency chart of docker images for every ONAP project before the migration happens in order for it to run smoothly according to Linux Foundation. As the team who is working on the logging project you are the ones to ask about this docker images dependency list. However because your time is preciouse and there is a constant need of resources, I started this effort to create the dependency chart of all the docker images for all the project. Due to the multitude of docker iamges the manual process is tedious at best so I used an automated text parser to make a best effort list which is not complete and cannot be due to multiple inconsistent type of formated text output in docker build jobs logs. However it's a starting point and since each tech team should have the final work I invite you to have a look at the dependency list for logging porject and give input in some form of your choosing (comments, edits, reply to this email, etc.) here:

https://wiki.onap.org/display/DW/Docker+images+dependency+list

You can see the list of docker images dependencies for each project in a roughly form like this:

1 --> 2 --> 3 ... --> n

where 1 is the dependency for the image (what you find in the FROM clause of a Dcokerfile), 2 is the dependent image (the name of the image that your project builds) and form 3 onward there are usually other tags of the same proejct image.

The previous wiki page is just a way to centralize the information regarding docker iamges dependency chart.

As Martial (PTL of clamp project) mentioned you can intruduce in the list the docker-compose dependencies (They are usually upstream project so already in dockerhub but better check them as well).

 

Thank you,

Paul


This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Enea may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, a mended, lost or destroyed, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Anyone who communicates with us by email accepts these risks.


Re: ONAP DCAE - VES - Java EVEL Library

Ramesh T
 

Just a followup.  Can anybody please tell me why the maven artifact for evel_javalib2 is not up to date ? Also can you through some clarity on the below questions?

 

Regards,

Ramesh

 

From: Thangamuthu, Ramesh
Sent: Thursday, August 8, 2019 4:46 PM
To: LOVETT, TREVOR J <tl2972@...>; onap-discuss@...; onap-arc@...
Cc: Maddipatla, Ramesh Babu <ramesh-babu.maddipatla@...>; BEJAWADA, VIJAYCHAND <vijaychand.bejawada@...>; Moosinada, Sarat <sarat.moosinada@...>; Rabertson Chikkala, Sunil <sunil.rabertson-chikkala@...>
Subject: RE: ONAP DCAE - VES - Java EVEL Library

 

Thanks Trevor. So we should refer https://github.com/onap/vnfsdk-ves-agent/tree/master/veslibrary/ves_javalibrary/evel_javalib2 for the latest code. Right? Couple of follow up questions if you (or someone in the community) can clarify.

 

1.       Is it an active open source project that VNF Providers can leverage to convert the logs/metrics into VES streams or is it used only for internal testing purposes of ONAP?

2.       Do you know what is the maven repo that has the latest maven artifact for this?

 

Regards,

Ramesh

 

From: LOVETT, TREVOR J [mailto:tl2972@...]
Sent: Wednesday, August 7, 2019 6:53 PM
To: onap-discuss@...; Thangamuthu, Ramesh <ramesh.thangamuthu@...>; onap-arc@...
Subject: RE: ONAP DCAE - VES - Java EVEL Library

 

I believe this is the current official version:  https://github.com/onap/vnfsdk-ves-agent/tree/master/veslibrary/ves_javalibrary/evel_javalib2

 

The VNFSDK compliance repository has been locked in the source ONAP Gerrit repository: https://gerrit.onap.org/r/admin/repos/q/filter:vnfsdk

 

Thanks,

 

Trevor Lovett

Lead Member of Technical Staff

AT&T Labs, Operational Automation and Program Management

 

AT&T Services, Inc.

Dallas, TX
m  314.401.8702  | 
trevor.lovett@...

 

This email and any attachments are confidential AT&T property intended solely for the recipients. If you received this message in error, please notify me and immediately delete this message from your computer.  Any retention, distribution, or other use of this email is strictly prohibited.

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Ramesh T
Sent: Wednesday, August 07, 2019 8:13 AM
To: onap-discuss@...; onap-arc@...
Subject: [onap-discuss] ONAP DCAE - VES - Java EVEL Library

 

Hello ONAP experts,

 

If this is not the right group to address the following question, please help me with the right mailing list. I also believe this is not a question to OPNFV com

 

munity. Please correct me.

 

Clarification Required:

To generate/convert observability data into VES streams in Java,  we have come across an open source library from ONAP community that helps us to generate VES format and stream it to collector. However we suspect that it may not be an active project (based on the snapshot below). Since this is outdated and not supporting the latest VES schema (v7), we would like to know from community that is it a test project or an active project meant to be used by VNF Providers? Could you please clarify?

 

Please take a look of the snapshots from Maven repo and Got Repo. No update for more than a year now.

 

https://mvnrepository.com/artifact/org.onap.vnfsdk.ves-agent/evel_javalib2

 

 

https://github.com/onap/vnfsdk-compliance/tree/master/veslibrary/ves_javalibrary

 

 

Regards,

Ramesh

 


Re: [SO][OOF][MultiCloud] error while instantiating VF module

thierry.hardy@...
 

Hi

I’m from Orange in the same team than René.

I have performed a modification of our installation project to integrate multicloud. And since this morning, the instantiation is successfull.

Yesterday, I met similar errors than yours due a wrong declaration of tenant via ESR. I forgot to indicate v3 in the service-url field.

 

So I changed yesterday this wrong configuration (via the right esr API) , but I was not able to overwrite the multicloud registration doing:

curl -X POST \

  http://msb.api.discovery.simpledemo.onap.org:30280/api/multicloud/v1/OPNFV/RegionOne/registry \

  -H 'Accept: application/json' \

  -H 'Cache-Control: no-cache' \

  -H 'Content-Type: application/json' \

  -H 'Postman-Token: 2b32db39-603b-4176-98f7-f1ee26675f48' \

  -H 'defaultTenant: onap-dublin-daily-vnfs-ci'

 

I don’t save the logs but the token error was still visible in logs of multicloud pike pod.

So I looked for an API request to delete registry action but without success. The one from ONAP documentation is not working.

 

As on this tenant, we perform a daily installation of ONAP, this morning, with the right configuration set in multicloud pods from the installation part (executed during the night), the instantiation was successful.

Regards

Thierry

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Multanen, Eric W
Envoyé : jeudi 22 août 2019 19:37
À : onap-discuss@...; sb00577584@...; seshu.kumar.m@...; ROBERT René TGI/OLN; bin.yang@...
Objet : Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

From the SO config side – looks like what you’ve configured is ok.

 

The multicloud logs – both on registration and vf module create indicate that multicloud is having trouble making requests to your cloud.

 

Do the user credentials you’re using for that cloud have the level of authorization to make these requests?  Have you verifying manually from a CLI perhaps?

 

It appears the main issue at the moment is the multicloud-ocata plugin talking to your Stein cloud.  First guess is something to do with the credentials.  

 

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Sunilkumar Shivangouda Biradar
Sent: Wednesday, August 21, 2019 10:44 PM
To: Multanen, Eric W <eric.w.multanen@...>; onap-discuss@...; seshu.kumar.m@...; rene.robert@...; bin.yang@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Seshu/Eric,

 

As per discussion we had during yesterday’s SO-Weekly call, sharing proper steps followed and fresh logs.

 

Steps followed:

  1. Cloud region created with these details. (Please refer to AAI_Cloud_Details.txt attached)   

 

Note: we are using Stein version (3.19.0) of openstack.

 

  1. Modified the identity_services table of catalogdb with Identity_url =”http://msb-iag.onap:80/api/multicloud/v0/CloudOwner_RegionOne/identity/v2.0”.
  2. Modified the cloud_sites table as shown below

 

 

  1. Did Setting of SO BPMN to use the VNF API v2 (post changing this, deleted the so-bpmn pod and the pod restarted successfully)

 

                    vnf:

                       endpoint: http://so-openstack-adapter.onap:8087/services/VnfAdapter

                       rest:

                         endpoint: http://so-openstack-adapter.onap:8087/services/rest/v2/vnfs

 

 

  1. Tried to register the cloud with multicloud using following API

curl -vvv -X POST http://10.211.1.20:30280/api/multicloud/v1/CloudOwner/RegionOne/registry -H 'Accept: application/json' -H 'Cache-Control: no-cache' -H 'Content-Type: application/json'

 

Note: did not understand why multicloud added "identity-url": "http://msb-iag.onap:80/api/multicloud-ocata/v0/CloudOwner_RegionOne/identity/v2.0"  to the AAI cloud region detail (we are using Stein version (3.19.0) of openstack)

 

I see errors in multicloud-ocata pod as shown below(full log file attached : multicloud-ocata_pod_logs.txt)

                2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_get_list_resources||DEBUG||making request with URI:projects,{'service_type': 'identity', 'interface': 'public'}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_discover_tenants||ERROR||HttpError: status:401, response:{u'error': {u'message': u'The request you have made requires authentication.', u'code': 401, u'title': u'Unauthorized'}}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_get_list_resources||DEBUG||making request with URI:/flavors/detail,{'service_type': 'compute', 'interface': 'public', 'region_name': u'RegionOne'}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_discover_flavors||ERROR||HttpError: status:401, response:{u'error': {u'message': u'The request you have made requires authentication.', u'code': 401, u'title': u'Unauthorized'}}||||requestID= invocationID= serviceName= serviceIP=

 

  1. Triggered VF Creation from VID portal (using VNF-API) with SNDC preload: VF Creation failed with error from multicloud.

Debug log file attached for SO-Openstack pod : VFCreation_SO_Openstack_pod_logs.txt

Log file attached from multicloud-ocata pod : VFCreation_Multicloud-ocata_pod_logs.txt

 

Snippet from SO-Openstack logs:

2019-08-22T04:23:20.279Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Making GET request to: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Request Headers: {Project=[c673af272d074170881559797f46b89d], Accept=[application/json], X-ONAP-RequestID=[5140aff8-5c26-4909-a443-84b8c36bff89], X-ONAP-InvocationID=[023572a9-79af-4802-9298-1265cff23e48], X-ONAP-PartnerName=[SO]}

2019-08-22T04:23:20.491Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Response from GET: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Response Headers: {Allow=[GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS], connection=[keep-alive], content-type=[text/html; charset=utf-8], Date=[Thu, 22 Aug 2019 04:23:20 GMT], Server=[openresty], transfer-encoding=[chunked], Vary=[Cookie], X-Frame-Options=[SAMEORIGIN]}<h1>Server Error (500)</h1>

 

Need your expertise in resolving this issue.

 

Thanks & Regards,

Sunil B

 

From: Multanen, Eric W <eric.w.multanen@...>
Sent: Wednesday, August 21, 2019 7:02 PM
To: onap-discuss@...; seshu.kumar.m@...; Sunilkumar Shivangouda Biradar <SB00577584@...>; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Per Seshu’s comment – yes, there is some apparent mismatch in the different log samples.

 

In the first log sample (down at the bottom) – it appears that configuration for using Multicloud via has been done (logs indicate usage of the Multicloud infrastructure workload API

http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

and messages are coming from org.onap.so.openstack.utils.MsoMulticloudUtils

 

In the more recent log sample, the logs coming from MsoHeatUtils show that the multicloud plugin in SO is not being used.

(ok – just spotted it – in the second case, the log indicates that the ‘orchestrator’ column for the cloud region is ‘null’ instead of ‘multicloud’)

 

 

The two key configs are:

  1. setting the SO BPMN to use the VNF API v2
  2. having ‘multicloud’ for the cloudregion in ‘orchestrator’ column of SO cloud_sites catalogdb table.

 

Sunil – to your recent question on the keystone url – when SO BPMN and the cloud region is configured as above, then the keystone url in SO is not used.   The authentication to the cloud region is

handled by the multicloud component – which goes back to the cloud registration process that includes the POST to /api/multicloud-titaniumcloud/v1/{{cloud-owner}}/{{cloud-region-id}}/registry

(and, the step of setting ‘multicloud’ in the ‘orchestrator’ column)

 

Eric

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of seshu kumar m
Sent: Wednesday, August 21, 2019 5:24 AM
To: onap-discuss@...; sb00577584@...; Multanen, Eric W <eric.w.multanen@...>; rene.robert@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Sunil

 

Did you change the orchestration type to Multicloud in SO, before trying this?

It seems there is some config mismatch issue with the intension and the actual execution from the logs.

 

Thanks and Regards,

M Seshu Kumar

Senior System Architect

Single OSS India Branch Department. S/W BU.

Huawei Technologies India Pvt. Ltd.

Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield

Bengaluru-560066, Karnataka.

Tel: + 91-80-49160700 , Mob: 9845355488

Company_logo

___________________________________________________________________________________________________

This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

-------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Sunilkumar Shivangouda Biradar
Sent: Wednesday, August 21, 2019 11:04 AM
To: Multanen, Eric W <eric.w.multanen@...>; onap-discuss@...; rene.robert@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Eric,

 

Thanks for reply, as mentioned in the second issue may I know the keystone url is proper  keystoneUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0

 

Because here I am getting responseCode as 401

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoCommonUtils - Config values RetryDelay:5 RetryCount:3  RetryCodes:504 ResponseCode:401

 

 

Thanks & Regards,

Sunil B

 

 

From: Multanen, Eric W <eric.w.multanen@...>
Sent: Tuesday, August 20, 2019 10:39 PM
To: Sunilkumar Shivangouda Biradar <SB00577584@...>; onap-discuss@...; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

This is what I’ve been using:  http://{{MSB_IP}}:{{MSB_PORT}}/api/multicloud-titaniumcloud/v1/{{cloud-owner}}/{{cloud-region-id}}/registry

 

From: Sunilkumar Shivangouda Biradar <SB00577584@...>
Sent: Tuesday, August 20, 2019 7:08 AM
To: onap-discuss@...; Multanen, Eric W <eric.w.multanen@...>; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Rene/Eric,

 

Thanks for reply, I followed the page which you suggested.

 

1.      Registering cloud site with multicloud as per document, but got 500 Internal server error.
               Found that there is different API “/api/multicloud/v1/MyCompanyName/INTEGRATION_CENTER/registry”, here I got 202 Unknown Status Code.
               Also tried with “/api/multicloud-titaniumcloud/v1/MyCompanyName/INTEGRATION_CENTER/registry, here I got 202 Accepted.
 
             May I know which API we need to use for registering? 

 

2.       In between I got to know that api changed from “MyCompanyName_INTEGRATION_CENTER/identity/v2.0” to “MyCompanyName/INTEGRATION_CENTER/identity/v2.0” for identity_url. 

                After this modification I got error as below

 

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - Found: CloudSite_.._jvsta6b_3c[regionId=RegionOne,identityServiceId=MC_KEYSTONE,cloudVersion=2.5,clli=RegionOne,cloudifyId=<null>,platform=<null>,orchestrator=<null>]

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - Found: CloudIdentity[id=MC_KEYSTONE,identityUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0,msoId=onap-tm5g-01,projectDomain=<null>,userDomain=<null>,adminTenant=service,memberRole=admin,tenantMetadata=true,identityServerType=KEYSTONE,identityAuthenticationType=USERNAME_PASSWORD]

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - keystoneUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoCommonUtils - Config values RetryDelay:5 RetryCount:3  RetryCodes:504 ResponseCode:401

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoHeatUtils - RA_CONNECTION_EXCEPTION 200 Openstack Exception on Token request:

org.onap.so.openstack.exceptions.MsoAdapterException: Authentication Failure: tenant=c673af272d074170881559797f46b89d,cloud=MC_KEYSTONE

        at org.onap.so.openstack.utils.MsoHeatUtils.getHeatClient(MsoHeatUtils.java:871)

        at org.onap.so.openstack.utils.MsoHeatUtils.queryStack(MsoHeatUtils.java:502)

        at org.onap.so.adapters.vnf.MsoVnfAdapterImpl.createVfModule(MsoVnfAdapterImpl.java:653)

 

 

Please suggest on this issue.

 

Thanks & Regards,

Sunil B

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Multanen, Eric W via Lists.Onap.Org
Sent: Monday, August 19, 2019 9:53 PM
To: onap-discuss@...; rene.robert@...; Sunilkumar Shivangouda Biradar <SB00577584@...>
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

I have the same suggestion – check that your cloud region has been setup and registered per the link.

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Rene Robert via Lists.Onap.Org
Sent: Monday, August 19, 2019 7:16 AM
To: onap-discuss@...; sb00577584@...; Multanen, Eric W <eric.w.multanen@...>
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

About cloud_site, there is that user-guide

 

https://onap.readthedocs.io/en/latest/guides/onap-user/cloud_site/index.html

 

maybe it could help

 

Best regards

 

 

Logo Orange

 

René Robert
«Open and Smart solutions for autOmating Network Services»
ORANGE/IMT/OLN/CNC/NARA/OSONS

 

Fixe : +33 2 96 07 39 29
Mobile : +33 6 74 78 68 43
rene.robert@...

 

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Sunilkumar Shivangouda Biradar
Envoyé : lundi 19 août 2019 12:38
À :
onap-discuss@...; eric.w.multanen@...
Objet : [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Team,

 

I am working on vFW usecase with HPA (ONAP version: Dublin)

 

Case 1:- Instantiated VM on openstack but not with specified flavors from OOF

 

I tried to create a VF module from VID using VNF-API and was able instantiate VM on openstack but not with the flavors which was suggested at oof_directives, instead it created the VM with the flavors provided in SDNC_preload and found from so-openstack log that SO was not calling multicloud  API “/api/multicloud/v1/CloudOwner/RegionOne/infra_workload”.

 

Case 2:- VM did not get instantiated, getting error.

 

https://wiki.onap.org/display/DW/Recap+of+Dublin+SO+Multicloud+Plugin+--%3E+Multicloud+Interactions

Got to know from wiki that for HPA we need not make any changes to cloud_site table of catalogdb. (which is leading to Case 1 above). Hence manually I modified orchestrator= “multicloud” for the region I’m using, as show in below table.

 

 

Post changing the cloud_site table I am able to see SO is calling the “/api/multicloud/v1/CloudOwner/RegionOne/infra_workload” API of multicloud.

But getting this below error from SO-openstack log(I made sure that no vf module with this name(vfwhpa_stack_test_24) exists in AAI before triggering vf module creation) :

 

2019-08-19T07:19:29.498Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Query multicloud HEAT stack: vfwhpa_stack_test_24 in tenant c673af272d074170881559797f46b89d

2019-08-19T07:19:29.499Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Multicloud Endpoint is: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

2019-08-19T07:19:29.505Z|| o.onap.so.logging.jaxrs.filter.JaxRsClientLogging - Could not Find Request ID Generating New One: /api/multicloud/v1/CloudOwner/RegionOne/infra_workload

2019-08-19T07:19:29.506Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Making GET request to: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Request Headers: {Project=[c673af272d074170881559797f46b89d], Accept=[application/json], X-ONAP-RequestID=[96718a17-4eeb-41db-b185-88f04799763e], X-ONAP-InvocationID=[bd58d3f1-ecc7-436f-88fb-378ed51a58e2], X-ONAP-PartnerName=[SO]}

2019-08-19T07:19:29.667Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Response from GET: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Response Headers: {Allow=[GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS], connection=[keep-alive], content-type=[text/html; charset=utf-8], Date=[Mon, 19 Aug 2019 07:19:29 GMT], Server=[openresty], transfer-encoding=[chunked], Vary=[Cookie], X-Frame-Options=[SAMEORIGIN]}{"template_type":"HEAT","workload_status_reason":"authenticate fails:CloudOwner, RegionOne, {\"error\":{\"message\":\"The request you have made requires authentication.\",\"code\":401,\"title\":\"Unauthorized\"}}","workload_status":"GET_FAILED","workload_id":""}

 

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Multicloud GET Response: org.apache.cxf.jaxrs.impl.ResponseImpl@6250c8cb

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - StackInfo to convert: {}

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - HeatStatus = FAILED msg = Internal Server Error

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Stack Status: FAILED

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Stack Status Message: Internal Server Error

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - Found Existing VDU, status=FAILED

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - RA_VNF_ALREADY_EXIST vfwhpa_stack_test_24 CloudOwner RegionOne c673af272d074170881559797f46b89d VDU queryVdu 300 VF Module vfwhpa_stack_test_24 already exists and is in FAILED state

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - Create VF: Deployment vfwhpa_stack_test_24 already exists and is in FAILED state in CloudOwner/RegionOne/c673af272d074170881559797f46b89d; requires manual intervention.

2019-08-19T07:19:29.679Z|| org.onap.so.adapters.vnf.BpelRestClient - Sending response to BPEL: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<vfModuleException>

    <messageId>dcfcc4e0-7723-473d-bfcb-dd8b9fe4ff2f-1566199169042</messageId>

    <category>INTERNAL</category>

    <message>Resource vfwhpa_stack_test_24 already exists in owner/cloud/tenant CloudOwner/RegionOne/c673af272d074170881559797f46b89d with ID </message>

   <rolledBack>true</rolledBack>

</vfModuleException>

 

 

Please suggest on this issue.

 

Thanks in advance.

 

Regards,

Sunil B

============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================

_________________________________________________________________________________________________________________________
 
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.

 

 

_________________________________________________________________________________________________________________________

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.


Re: [SO][OOF] error while instantiating service

Vamshi K Namilikonda
 

Thank you Ruoyu, sure.

 

 

 

Thanks & Regards,

 

Vamshi Krishna | Tech Mahindra

Sharda Centre, Off Karve Road, Erandwane, Pune 411 004, INDIA

Mobile: +91 9848639561, ext : 3492

Email Id – vn00480215@...

  

 

 

 

From: Ying, Ruoyu <ruoyu.ying@...>
Sent: Friday, August 23, 2019 5:50 AM
To: onap-discuss@...; Vamshi Namilikonda <VN00480215@...>
Subject: RE: [onap-discuss] [SO][OOF] error while instantiating service

 

Hi Vamshi,

 

Glad you make it. You may contact me if you have other issue within OOF.

 

Best Regards,

Ruoyu

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of vamshi
Sent: Thursday, August 22, 2019 11:00 PM
To: onap-discuss@...; Ying, Ruoyu <ruoyu.ying@...>
Subject: Re: [onap-discuss] [SO][OOF] error while instantiating service

 

That’s solved the issue Ruoyu. I could see Service Instance created now.  Thank you so much.

 

What I missed is : Matching between the following attributes as you suggested.

 

resources(Policy)  = resourceModuleName(SO)

policyScope (Policy) =  ServiceName(SO)

 

 

Thanks & Regards,

 

Vamshi Krishna | Tech Mahindra

Sharda Centre, Off Karve Road, Erandwane, Pune 411 004, INDIA

Mobile: +91 9848639561, ext : 3492

Email Id – vn00480215@...

  

 

 

 

From: Vamshi Namilikonda
Sent: Thursday, August 22, 2019 10:57 AM
To: onap-discuss@...; ruoyu.ying@...
Subject: RE: [onap-discuss] [SO][OOF] error while instantiating service

 

Hello Ruoyu,

 

Thank you so much, you are right. We’ve no right data in AAI compared to Policies pushed. I’m trying with right policy data. Many thanks for your continuous support.  

 

 

 

Thanks & Regards,

 

Vamshi Krishna | Tech Mahindra

Sharda Centre, Off Karve Road, Erandwane, Pune 411 004, INDIA

Mobile: +91 9848639561, ext : 3492

Email Id – vn00480215@...

  

 

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Ying, Ruoyu via Lists.Onap.Org
Sent: Saturday, August 17, 2019 12:27 PM
To: onap-discuss@...; Vamshi Namilikonda <VN00480215@...>
Subject: Re: [onap-discuss] [SO][OOF] error while instantiating service

 

Hi Vamshi,

 

I checked the logs you attached. It is showing that OOF cannot find an appropriate flavor inside AAI, so it is returning a ‘not found’ to SO which causes the results here. Can you check if you do have a candidate inside AAI matches all the requirement you specified in the HPA policies? Thanks.

 

Best Regards,

Ruoyu

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of vamshi
Sent: Friday, August 16, 2019 10:09 PM
To: Ying, Ruoyu <ruoyu.ying@...>; onap-discuss@...
Subject: Re: [onap-discuss] [SO][OOF] error while instantiating service

 

Hello Ruoyu,

 

Thank you very much.

 

I made changes to ensure following set match against each other.  There is some improvement as Payload to Conductor has picked more data, but issue is there still. Please take a look on logs attached. Thanks again

 

 

resources(Policy) = HpaVf51 ;       resourceModuleName(SO)  =  "HpaVf51"

policyScope (Policy) = vfw ;           ServiceName(SO) = "vfw"

 

 

2019-08-16T13:30:30,180+00:00||Thread-86||OOF_OSDF|a6ffc2dc-af83-11e9-a796-ce8f9b3345ee|DEBUG||10.42.4.26|dev-oof-oof-79f9f55959-fqgs4||||Payload to Conductor: {"name": "65487c09-d1ae-40f0-93ab-6be1fa8e365e", "files": {}, "num_solution": "1", "timeout": 600, "template": {"homing_template_version": "2017-10-10", "optimization": {"minimize": {"sum": [{"product": ["100", {"distance_between": ["customer_loc", "HpaVf51"]}]}, {"product": ["200", {"hpa_score": ["HpaVf51"]}]}]}}, "constraints": {"distance-vFW": {"properties": {"location": "customer_loc", "distance": "< 100 km"}, "demands": ["HpaVf51"], "type": "distance_to_location"}, "hpa-vFW": {"properties": {"evaluate": [{"directives": [{"attributes": [{"attribute_name": "firewall_flavor_name", "attribute_value": ""}], "type": "flavor_directives"}], "type": "vnfc", "id": "vfw", "flavorProperties": [{"hpa-feature": "basicCapabilities", "mandatory": "True", "architecture": "generic", "directives": [], "hpa-feature-attributes": [{"hpa-attribute-value": "2", "unit": "", "operator": "=", "hpa-attribute-key": "numVirtualCpu"}, {"hpa-attribute-value": "512", "unit": "MB", "operator": "=", "hpa-attribute-key": "virtualMemSize"}], "hpa-version": "v1"}, {"hpa-feature": "hugePages", "mandatory": "True", "architecture": "generic", "directives": [], "hpa-feature-attributes": [{"hpa-attribute-value": "2", "unit": "MB", "operator": "=", "hpa-attribute-key": "memoryPageSize"}], "hpa-version": "v1"}, {"hpa-feature": "localStorage", "mandatory": "True", "architecture": "generic", "directives": [], "hpa-feature-attributes": [{"hpa-attribute-value": "10", "unit": "GB", "hpa-attribute-key": "diskSize", "operator": ">="}], "hpa-version": "v1"}, {"hpa-feature": "cpuPinning", "mandatory": "False", "score": "100", "architecture": "generic", "directives": [], "hpa-feature-attributes": [{"hpa-attribute-value": "isolate", "unit": "", "operator": "=", "hpa-attribute-key": "logicalCpuThreadPinningPolicy"}, {"hpa-attribute-value": "dedicated", "unit": "", "operator": "=", "hpa-attribute-key": "logicalCpuPinningPolicy"}], "hpa-version": "v1"}]}, {"directives": [{"attributes": [{"attribute_name": "packetgen_flavor_name", "attribute_value": ""}], "type": "flavor_directives"}], "type": "vnfc", "id": "vgenerator", "flavorProperties": [{"hpa-feature": "basicCapabilities", "mandatory": "True", "architecture": "generic", "directives": [], "hpa-feature-attributes": [{"hpa-attribute-value": "1", "operator": ">=", "hpa-attribute-key": "numVirtualCpu"}, {"hpa-attribute-value": "7", "unit": "GB", "operator": ">=", "hpa-attribute-key": "virtualMemSize"}], "hpa-version": "v1"}, {"hpa-feature": "localStorage", "mandatory": "True", "architecture": "generic", "directives": [], "hpa-feature-attributes": [{"hpa-attribute-value": "10", "unit": "GB", "hpa-attribute-key": "diskSize", "operator": ">="}], "hpa-version": "v1"}]}, {"directives": [{"attributes": [{"attribute_name": "sink_flavor_name", "attribute_value": ""}], "type": "flavor_directives"}], "type": "vnfc", "id": "vsink", "flavorProperties": [{"hpa-feature": "basicCapabilities", "mandatory": "True", "architecture": "generic", "directives": [], "hpa-feature-attributes": [], "hpa-version": "v1"}]}]}, "demands": ["HpaVf51"], "type": "hpa"}}, "parameters": {"REQUIRED_DISK": "", "customer_lat": "32.89948", "REQUIRED_MEM": "", "customer_long": "97.045443", "service_name": "vfw", "service_id": "77534651-3d9e-4033-8378-0b31f1f9ca92"}, "locations": {"customer_loc": {"latitude": {"get_param": "customer_lat"}, "longitude": {"get_param": "customer_long"}}}, "demands": {"HpaVf51": [{"service_resource_id": "53a43a3a-2ad9-475e-860a-84e3329df186", "attributes": {"model-invariant-id": "b1b75792-65ac-4c48-b89a-192553eccc11", "model-version-id": "5540debe-28b1-4146-944c-309a95ea1de6"}, "service_type": "53a43a3a-2ad9-475e-860a-84e3329df186", "inventory_type": "cloud", "inventory_provider": "aai"}]}}}

 

Thanks & Regards,

 

Vamshi Krishna | Tech Mahindra

Sharda Centre, Off Karve Road, Erandwane, Pune 411 004, INDIA

Mobile: +91 9848639561, ext : 3492

Email Id – vn00480215@...

  

 

 

 

From: Ying, Ruoyu <ruoyu.ying@...>
Sent: Friday, August 16, 2019 6:52 AM
To: onap-discuss@...; Vamshi Namilikonda <VN00480215@...>
Subject: RE: [onap-discuss] [SO][OOF] error while instantiating service

 

Hi Vamshi,

 

I checked the logs here and I saw there’s something missing in your policy.

First, to apply the policies for a certain VNF included in a certain service, you need to make the two keys inside the policies(‘resources’ and ‘policyScope’) matching with the values you have in your SO request. You need to have your ‘ServiceName’ in the SO request available inside the ‘policyScope’ in the policy, and have your ‘resourceModuleName’ in the SO request available as part of ‘resources’ in the policies.

 

Take an example here. According to the pushed-policies.txt and the so-bpmn-log.txt you provided. We shall have a sample Distance policy being retrieved like this:

 

{

        "config": "{\"service\":\"distancePolicy\",\"guard\":\"False\",\"content\":{\"policyType\":\"distance_to_location\",\"applicableResources\":\"any\",\"identity\":\"distance-vFW\",\"policyScope\":[\"vfw\",\"us\",\"international\",\"ip\"],\"distanceProperties\":{\"distance\":{\"value\":\"100\",\"unit\":\"km\",\"operator\":\"<\"},\"locationInfo\":\"customer_loc\"},\"resources\":[\"vFW\",\"VfwHeatHpaV1\",\”HpaVf42\”]},\"priority\":\"3\",\"templateVersion\":\"OpenSource.version.1\",\"riskLevel\":\"2\",\"description\":\"Distance Policy for vFW\",\"policyName\":\"OSDF_DUBLIN.Distance_vFW_1\",\"version\":\"test1\",\"riskType\":\"test\"}",

        "matchingConditions": {

            "ECOMPName": "SampleDemo",

            "ONAPName": "SampleDemo",

            "policyScope": "vfw,us,international,ip",

            "policyType": "distance_to_location",

            "service": "distancePolicy"

        },

        "policyConfigMessage": "Config Retrieved! ",

        "policyConfigStatus": "CONFIG_RETRIEVED",

        "policyName": "OSDF_DUBLIN.Config_MS_Distance_vFW_1.1.xml",

        "policyType": "MicroService",

        "policyVersion": "1",

        "property": null,

        "responseAttributes": {},

        "type": "JSON"

}

 

So I think it is because of this, that a lot information are missing in the payload and cause the failure of placement.

Can you try updating the policies with the correct value and see if it can solve this problem?

Thanks.

 

Best Regards,

Ruoyu

 

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of vamshi
Sent: Wednesday, August 14, 2019 7:26 PM
To: Ying, Ruoyu <ruoyu.ying@...>; onap-discuss@...
Subject: Re: [onap-discuss] [SO][OOF] error while instantiating service

 

Hello Ruoyu,

 

Many thanks for your reply.

 

Here I pulled the logs need to understand the issue.  I’ve also attached logs from SO, OSDF and policies that are pushed. Thank you

 

 

OOF-OSDF – debug.log

------------------------------

2019-08-14T10:56:17,245+00:00||Thread-62||OOF_OSDF|a6ffc2dc-af83-11e9-a796-ce8f9b3345ee|DEBUG||10.42.4.26|dev-oof-oof-79f9f55959-fqgs4||||Sending first Conductor request for request_id 9f85f94d-52eb-4aba-a970-ebc3367052fa

2019-08-14T10:56:17,245+00:00||Thread-62||OOF_OSDF|a6ffc2dc-af83-11e9-a796-ce8f9b3345ee|DEBUG||10.42.4.26|dev-oof-oof-79f9f55959-fqgs4||||Payload to Conductor: {"name": "9f85f94d-52eb-4aba-a970-ebc3367052fa", "files": {}, "num_solution": "1", "timeout": 600, "template": {"homing_template_version": "2017-10-10", "optimization": {"minimize": {"sum": []}}, "constraints": {}, "parameters": {"REQUIRED_DISK": "", "customer_lat": "32.897480", "REQUIRED_MEM": "", "customer_long": "97.040443", "service_name": "vFW", "service_id": "e5bacb00-4e32-4e4b-811a-a327e2b00202"}, "locations": {"customer_loc": {"latitude": {"get_param": "customer_lat"}, "longitude": {"get_param": "customer_long"}}}, "demands": {}}}

2019-08-14T10:56:17,246+00:00||Thread-62||OOF_OSDF|a6ffc2dc-af83-11e9-a796-ce8f9b3345ee|DEBUG||10.42.4.26|dev-oof-oof-79f9f55959-fqgs4||||Requesting URL: https://oof-has-api:8091/v1/plans/

2019-08-14T10:56:19,954+00:00||Thread-62||OOF_OSDF|a6ffc2dc-af83-11e9-a796-ce8f9b3345ee|DEBUG||10.42.4.26|dev-oof-oof-79f9f55959-fqgs4||||Received response [code: 201, headers: {'X-LatestVersion': '1.3.1', 'Content-Type': 'application/json', 'Date': 'Wed, 14 Aug 2019 10:56:19 GMT', 'X-PatchVersion': '1', 'Server': 'nginx/1.14.2', 'Connection': 'keep-alive', 'Content-Length': '228', 'X-MinorVersion': '0'}, data: {'history': [], 'status_code': 201, '_next': None, 'request': <PreparedRequest [POST]>, 'reason': 'Created', 'connection': <requests.adapters.HTTPAdapter object at 0x7f56ebdd75c0>, '_content': b'{"status": "template", "name": "9f85f94d-52eb-4aba-a970-ebc3367052fa", "links": [[{"href": "https://oof-has-api:8091/v1/plans/f4c6f2c8-45a7-4a67-a9d5-52c8e1372d37", "rel": "self"}]], "id": "f4c6f2c8-45a7-4a67-a9d5-52c8e1372d37"}', 'headers': {'X-LatestVersion': '1.3.1', 'Content-Type': 'application/json', 'Date': 'Wed, 14 Aug 2019 10:56:19 GMT', 'X-PatchVersion': '1', 'Server': 'nginx/1.14.2', 'Connection': 'keep-alive', 'Content-Length': '228', 'X-MinorVersion': '0'}, '_content_consumed': True, 'cookies': <RequestsCookieJar[]>, 'elapsed': datetime.timedelta(0, 2, 687100), 'url': 'https://oof-has-api:8091/v1/plans/', 'raw': <urllib3.response.HTTPResponse object at 0x7f56ebde0438>, 'encoding': None}]

2019-08-14T10:56:29,965+00:00||Thread-62||OOF_OSDF|a6ffc2dc-af83-11e9-a796-ce8f9b3345ee|DEBUG||10.42.4.26|dev-oof-oof-79f9f55959-fqgs4||||Attempting to read the plan from the conductor provided url https://oof-has-api:8091/v1/plans/f4c6f2c8-45a7-4a67-a9d5-52c8e1372d37

2019-08-14T10:56:29,965+00:00||Thread-62||OOF_OSDF|a6ffc2dc-af83-11e9-a796-ce8f9b3345ee|DEBUG||10.42.4.26|dev-oof-oof-79f9f55959-fqgs4||||Requesting URL: https://oof-has-api:8091/v1/plans/f4c6f2c8-45a7-4a67-a9d5-52c8e1372d37

2019-08-14T10:56:31,497+00:00||Thread-62||OOF_OSDF|a6ffc2dc-af83-11e9-a796-ce8f9b3345ee|DEBUG||10.42.4.26|dev-oof-oof-79f9f55959-fqgs4||||Received response [code: 200, headers: {'X-LatestVersion': '1.3.1', 'Content-Type': 'application/json', 'Date': 'Wed, 14 Aug 2019 10:56:31 GMT', 'X-PatchVersion': '1', 'Server': 'nginx/1.14.2', 'Connection': 'keep-alive', 'Content-Length': '316', 'X-MinorVersion': '0'}, data: {'history': [], 'status_code': 200, '_next': None, 'request': <PreparedRequest [GET]>, 'reason': 'OK', 'connection': <requests.adapters.HTTPAdapter object at 0x7f56ebde0fd0>, '_content': b'{"plans": [{"status": "error", "message": "local variable \'triage_data_trans\' referenced before assignment", "name": "9f85f94d-52eb-4aba-a970-ebc3367052fa", "links": [[{"href": "https://oof-has-api:8091/v1/plans/f4c6f2c8-45a7-4a67-a9d5-52c8e1372d37", "rel": "self"}]], "id": "f4c6f2c8-45a7-4a67-a9d5-52c8e1372d37"}]}', 'headers': {'X-LatestVersion': '1.3.1', 'Content-Type': 'application/json', 'Date': 'Wed, 14 Aug 2019 10:56:31 GMT', 'X-PatchVersion': '1', 'Server': 'nginx/1.14.2', 'Connection': 'keep-alive', 'Content-Length': '316', 'X-MinorVersion': '0'}, '_content_consumed': True, 'cookies': <RequestsCookieJar[]>, 'elapsed': datetime.timedelta(0, 1, 509218), 'url': 'https://oof-has-api:8091/v1/plans/f4c6f2c8-45a7-4a67-a9d5-52c8e1372d37', 'raw': <urllib3.response.HTTPResponse object at 0x7f56ebdcf048>, 'encoding': None}]

2019-08-14T10:56:31,498+00:00||Thread-62||OOF_OSDF|a6ffc2dc-af83-11e9-a796-ce8f9b3345ee|DEBUG||10.42.4.26|dev-oof-oof-79f9f55959-fqgs4||||Requesting URL: http://so-bpmn-infra.onap:8081/mso/WorkflowMessage/oofResponse/9f85f94d-52eb-4aba-a970-ebc3367052fa

 

Thanks & Regards,

 

Vamshi Krishna | Tech Mahindra

Sharda Centre, Off Karve Road, Erandwane, Pune 411 004, INDIA

Mobile: +91 9848639561, ext : 3492

Email Id – vn00480215@...

  

 

 

 

From: Ying, Ruoyu <ruoyu.ying@...>
Sent: Wednesday, August 14, 2019 7:19 AM
To: onap-discuss@...; Vamshi Namilikonda <VN00480215@...>
Subject: RE: [onap-discuss] [SO][OOF] error while instantiating service

 

Hi Vamshi,

 

This error mainly happens when there’s something wrong with the optimization policy that is needed for placement. May you try login to the osdf pod and copy the debug log(especially the payload it send to conductor) here? That will help us to locate the root cause for the problem. Thanks.

 

Best Regards,

Ruoyu

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of vamshi
Sent: Tuesday, August 13, 2019 5:42 PM
To: onap-discuss@...
Subject: [onap-discuss] [SO][OOF] error while instantiating service

 

Hello SO/OOF team,

 

I’m trying vFW automation script for instantiating vFW use case. By following page https://github.com/onap/integration/tree/master/test/hpa_automation/heat

I was facing below issue in SO while it is trying to request OOF , have pulled log from - dev-so-so-bpmn-infra-5b4f566958-7jql6. The detailed log has attached to this mail. Could you please suggest any thoughts with your observations. Thank you

 

 

 

2019-08-13T06:49:14.926Z|5899cd91-80a9-4adc-9b09-40ce5340a0e0| org.onap.so.bpmn.common.scripts.OofHoming - OOF Async Callback Response is: "{\"externalApplicationDetails\": {\"httpMethod\": \"GET\", \"httpStatusCode\": 200, \"responseMessage\": {\"plans\": [{\"name\": \"c8fc2537-3080-4cc7-873e-82e1a404550d\", \"status\": \"error\", \"id\": \"375bcb8e-5ab8-403f-940f-306e5068363f\", \"links\": [[{\"rel\": \"self\", \"href\": \"https://oof-has-api:8091/v1/plans/375bcb8e-5ab8-403f-940f-306e5068363f\"}]], \"message\": \"local variable 'triage_data_trans' referenced before assignment\"}]}, \"url\": \"https://oof-has-api:8091/v1/plans/375bcb8e-5ab8-403f-940f-306e5068363f\"}, \"serviceException\": {\"text\": \"A request exception has occurred when contacting an external system\", \"errorType\": \"InterfaceError\"}}"

2019-08-13T06:49:14.932Z|5899cd91-80a9-4adc-9b09-40ce5340a0e0| org.onap.so.bpmn.core.json.JsonUtils - getJsonRawValue(): unable to parse json to retrieve value for field=solutions.placementSolutions. Exception was: org.json.JSONException: A JSONObject text must begin with '{' at 1 [character 2 line 1]

org.json.JSONException: A JSONObject text must begin with '{' at 1 [character 2 line 1]

        at org.json.JSONTokener.syntaxError(JSONTokener.java:433)

        at org.json.JSONObject.<init>(JSONObject.java:194)

        at org.json.JSONObject.<init>(JSONObject.java:321)

        at org.onap.so.bpmn.core.json.JsonUtils.getJsonRawValue(JsonUtils.java:775)

        at org.onap.so.bpmn.core.json.JsonUtils.getJsonRawValue(JsonUtils.java:757)

  

 

 

 

Thanks & Regards,

 

Vamshi Krishna | Tech Mahindra

Sharda Centre, Off Karve Road, Erandwane, Pune 411 004, INDIA

Mobile: +91 9848639561, ext : 3492

Email Id – vn00480215@...

  

 

 

 

============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================


Re: [SO][OOF] error while instantiating service

Ying, Ruoyu
 

Hi Vamshi,

 

Glad you make it. You may contact me if you have other issue within OOF.

 

Best Regards,

Ruoyu

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of vamshi
Sent: Thursday, August 22, 2019 11:00 PM
To: onap-discuss@...; Ying, Ruoyu <ruoyu.ying@...>
Subject: Re: [onap-discuss] [SO][OOF] error while instantiating service

 

That’s solved the issue Ruoyu. I could see Service Instance created now.  Thank you so much.

 

What I missed is : Matching between the following attributes as you suggested.

 

resources(Policy)  = resourceModuleName(SO)

policyScope (Policy) =  ServiceName(SO)

 

 

Thanks & Regards,

 

Vamshi Krishna | Tech Mahindra

Sharda Centre, Off Karve Road, Erandwane, Pune 411 004, INDIA

Mobile: +91 9848639561, ext : 3492

Email Id – vn00480215@...

  

 

 

 

From: Vamshi Namilikonda
Sent: Thursday, August 22, 2019 10:57 AM
To: onap-discuss@...; ruoyu.ying@...
Subject: RE: [onap-discuss] [SO][OOF] error while instantiating service

 

Hello Ruoyu,

 

Thank you so much, you are right. We’ve no right data in AAI compared to Policies pushed. I’m trying with right policy data. Many thanks for your continuous support.  

 

 

 

Thanks & Regards,

 

Vamshi Krishna | Tech Mahindra

Sharda Centre, Off Karve Road, Erandwane, Pune 411 004, INDIA

Mobile: +91 9848639561, ext : 3492

Email Id – vn00480215@...

  

 

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Ying, Ruoyu via Lists.Onap.Org
Sent: Saturday, August 17, 2019 12:27 PM
To: onap-discuss@...; Vamshi Namilikonda <VN00480215@...>
Subject: Re: [onap-discuss] [SO][OOF] error while instantiating service

 

Hi Vamshi,

 

I checked the logs you attached. It is showing that OOF cannot find an appropriate flavor inside AAI, so it is returning a ‘not found’ to SO which causes the results here. Can you check if you do have a candidate inside AAI matches all the requirement you specified in the HPA policies? Thanks.

 

Best Regards,

Ruoyu

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of vamshi
Sent: Friday, August 16, 2019 10:09 PM
To: Ying, Ruoyu <ruoyu.ying@...>; onap-discuss@...
Subject: Re: [onap-discuss] [SO][OOF] error while instantiating service

 

Hello Ruoyu,

 

Thank you very much.

 

I made changes to ensure following set match against each other.  There is some improvement as Payload to Conductor has picked more data, but issue is there still. Please take a look on logs attached. Thanks again

 

 

resources(Policy) = HpaVf51 ;       resourceModuleName(SO)  =  "HpaVf51"

policyScope (Policy) = vfw ;           ServiceName(SO) = "vfw"

 

 

2019-08-16T13:30:30,180+00:00||Thread-86||OOF_OSDF|a6ffc2dc-af83-11e9-a796-ce8f9b3345ee|DEBUG||10.42.4.26|dev-oof-oof-79f9f55959-fqgs4||||Payload to Conductor: {"name": "65487c09-d1ae-40f0-93ab-6be1fa8e365e", "files": {}, "num_solution": "1", "timeout": 600, "template": {"homing_template_version": "2017-10-10", "optimization": {"minimize": {"sum": [{"product": ["100", {"distance_between": ["customer_loc", "HpaVf51"]}]}, {"product": ["200", {"hpa_score": ["HpaVf51"]}]}]}}, "constraints": {"distance-vFW": {"properties": {"location": "customer_loc", "distance": "< 100 km"}, "demands": ["HpaVf51"], "type": "distance_to_location"}, "hpa-vFW": {"properties": {"evaluate": [{"directives": [{"attributes": [{"attribute_name": "firewall_flavor_name", "attribute_value": ""}], "type": "flavor_directives"}], "type": "vnfc", "id": "vfw", "flavorProperties": [{"hpa-feature": "basicCapabilities", "mandatory": "True", "architecture": "generic", "directives": [], "hpa-feature-attributes": [{"hpa-attribute-value": "2", "unit": "", "operator": "=", "hpa-attribute-key": "numVirtualCpu"}, {"hpa-attribute-value": "512", "unit": "MB", "operator": "=", "hpa-attribute-key": "virtualMemSize"}], "hpa-version": "v1"}, {"hpa-feature": "hugePages", "mandatory": "True", "architecture": "generic", "directives": [], "hpa-feature-attributes": [{"hpa-attribute-value": "2", "unit": "MB", "operator": "=", "hpa-attribute-key": "memoryPageSize"}], "hpa-version": "v1"}, {"hpa-feature": "localStorage", "mandatory": "True", "architecture": "generic", "directives": [], "hpa-feature-attributes": [{"hpa-attribute-value": "10", "unit": "GB", "hpa-attribute-key": "diskSize", "operator": ">="}], "hpa-version": "v1"}, {"hpa-feature": "cpuPinning", "mandatory": "False", "score": "100", "architecture": "generic", "directives": [], "hpa-feature-attributes": [{"hpa-attribute-value": "isolate", "unit": "", "operator": "=", "hpa-attribute-key": "logicalCpuThreadPinningPolicy"}, {"hpa-attribute-value": "dedicated", "unit": "", "operator": "=", "hpa-attribute-key": "logicalCpuPinningPolicy"}], "hpa-version": "v1"}]}, {"directives": [{"attributes": [{"attribute_name": "packetgen_flavor_name", "attribute_value": ""}], "type": "flavor_directives"}], "type": "vnfc", "id": "vgenerator", "flavorProperties": [{"hpa-feature": "basicCapabilities", "mandatory": "True", "architecture": "generic", "directives": [], "hpa-feature-attributes": [{"hpa-attribute-value": "1", "operator": ">=", "hpa-attribute-key": "numVirtualCpu"}, {"hpa-attribute-value": "7", "unit": "GB", "operator": ">=", "hpa-attribute-key": "virtualMemSize"}], "hpa-version": "v1"}, {"hpa-feature": "localStorage", "mandatory": "True", "architecture": "generic", "directives": [], "hpa-feature-attributes": [{"hpa-attribute-value": "10", "unit": "GB", "hpa-attribute-key": "diskSize", "operator": ">="}], "hpa-version": "v1"}]}, {"directives": [{"attributes": [{"attribute_name": "sink_flavor_name", "attribute_value": ""}], "type": "flavor_directives"}], "type": "vnfc", "id": "vsink", "flavorProperties": [{"hpa-feature": "basicCapabilities", "mandatory": "True", "architecture": "generic", "directives": [], "hpa-feature-attributes": [], "hpa-version": "v1"}]}]}, "demands": ["HpaVf51"], "type": "hpa"}}, "parameters": {"REQUIRED_DISK": "", "customer_lat": "32.89948", "REQUIRED_MEM": "", "customer_long": "97.045443", "service_name": "vfw", "service_id": "77534651-3d9e-4033-8378-0b31f1f9ca92"}, "locations": {"customer_loc": {"latitude": {"get_param": "customer_lat"}, "longitude": {"get_param": "customer_long"}}}, "demands": {"HpaVf51": [{"service_resource_id": "53a43a3a-2ad9-475e-860a-84e3329df186", "attributes": {"model-invariant-id": "b1b75792-65ac-4c48-b89a-192553eccc11", "model-version-id": "5540debe-28b1-4146-944c-309a95ea1de6"}, "service_type": "53a43a3a-2ad9-475e-860a-84e3329df186", "inventory_type": "cloud", "inventory_provider": "aai"}]}}}

 

Thanks & Regards,

 

Vamshi Krishna | Tech Mahindra

Sharda Centre, Off Karve Road, Erandwane, Pune 411 004, INDIA

Mobile: +91 9848639561, ext : 3492

Email Id – vn00480215@...

  

 

 

 

From: Ying, Ruoyu <ruoyu.ying@...>
Sent: Friday, August 16, 2019 6:52 AM
To: onap-discuss@...; Vamshi Namilikonda <VN00480215@...>
Subject: RE: [onap-discuss] [SO][OOF] error while instantiating service

 

Hi Vamshi,

 

I checked the logs here and I saw there’s something missing in your policy.

First, to apply the policies for a certain VNF included in a certain service, you need to make the two keys inside the policies(‘resources’ and ‘policyScope’) matching with the values you have in your SO request. You need to have your ‘ServiceName’ in the SO request available inside the ‘policyScope’ in the policy, and have your ‘resourceModuleName’ in the SO request available as part of ‘resources’ in the policies.

 

Take an example here. According to the pushed-policies.txt and the so-bpmn-log.txt you provided. We shall have a sample Distance policy being retrieved like this:

 

{

        "config": "{\"service\":\"distancePolicy\",\"guard\":\"False\",\"content\":{\"policyType\":\"distance_to_location\",\"applicableResources\":\"any\",\"identity\":\"distance-vFW\",\"policyScope\":[\"vfw\",\"us\",\"international\",\"ip\"],\"distanceProperties\":{\"distance\":{\"value\":\"100\",\"unit\":\"km\",\"operator\":\"<\"},\"locationInfo\":\"customer_loc\"},\"resources\":[\"vFW\",\"VfwHeatHpaV1\",\”HpaVf42\”]},\"priority\":\"3\",\"templateVersion\":\"OpenSource.version.1\",\"riskLevel\":\"2\",\"description\":\"Distance Policy for vFW\",\"policyName\":\"OSDF_DUBLIN.Distance_vFW_1\",\"version\":\"test1\",\"riskType\":\"test\"}",

        "matchingConditions": {

            "ECOMPName": "SampleDemo",

            "ONAPName": "SampleDemo",

            "policyScope": "vfw,us,international,ip",

            "policyType": "distance_to_location",

            "service": "distancePolicy"

        },

        "policyConfigMessage": "Config Retrieved! ",

        "policyConfigStatus": "CONFIG_RETRIEVED",

        "policyName": "OSDF_DUBLIN.Config_MS_Distance_vFW_1.1.xml",

        "policyType": "MicroService",

        "policyVersion": "1",

        "property": null,

        "responseAttributes": {},

        "type": "JSON"

}

 

So I think it is because of this, that a lot information are missing in the payload and cause the failure of placement.

Can you try updating the policies with the correct value and see if it can solve this problem?

Thanks.

 

Best Regards,

Ruoyu

 

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of vamshi
Sent: Wednesday, August 14, 2019 7:26 PM
To: Ying, Ruoyu <ruoyu.ying@...>; onap-discuss@...
Subject: Re: [onap-discuss] [SO][OOF] error while instantiating service

 

Hello Ruoyu,

 

Many thanks for your reply.

 

Here I pulled the logs need to understand the issue.  I’ve also attached logs from SO, OSDF and policies that are pushed. Thank you

 

 

OOF-OSDF – debug.log

------------------------------

2019-08-14T10:56:17,245+00:00||Thread-62||OOF_OSDF|a6ffc2dc-af83-11e9-a796-ce8f9b3345ee|DEBUG||10.42.4.26|dev-oof-oof-79f9f55959-fqgs4||||Sending first Conductor request for request_id 9f85f94d-52eb-4aba-a970-ebc3367052fa

2019-08-14T10:56:17,245+00:00||Thread-62||OOF_OSDF|a6ffc2dc-af83-11e9-a796-ce8f9b3345ee|DEBUG||10.42.4.26|dev-oof-oof-79f9f55959-fqgs4||||Payload to Conductor: {"name": "9f85f94d-52eb-4aba-a970-ebc3367052fa", "files": {}, "num_solution": "1", "timeout": 600, "template": {"homing_template_version": "2017-10-10", "optimization": {"minimize": {"sum": []}}, "constraints": {}, "parameters": {"REQUIRED_DISK": "", "customer_lat": "32.897480", "REQUIRED_MEM": "", "customer_long": "97.040443", "service_name": "vFW", "service_id": "e5bacb00-4e32-4e4b-811a-a327e2b00202"}, "locations": {"customer_loc": {"latitude": {"get_param": "customer_lat"}, "longitude": {"get_param": "customer_long"}}}, "demands": {}}}

2019-08-14T10:56:17,246+00:00||Thread-62||OOF_OSDF|a6ffc2dc-af83-11e9-a796-ce8f9b3345ee|DEBUG||10.42.4.26|dev-oof-oof-79f9f55959-fqgs4||||Requesting URL: https://oof-has-api:8091/v1/plans/

2019-08-14T10:56:19,954+00:00||Thread-62||OOF_OSDF|a6ffc2dc-af83-11e9-a796-ce8f9b3345ee|DEBUG||10.42.4.26|dev-oof-oof-79f9f55959-fqgs4||||Received response [code: 201, headers: {'X-LatestVersion': '1.3.1', 'Content-Type': 'application/json', 'Date': 'Wed, 14 Aug 2019 10:56:19 GMT', 'X-PatchVersion': '1', 'Server': 'nginx/1.14.2', 'Connection': 'keep-alive', 'Content-Length': '228', 'X-MinorVersion': '0'}, data: {'history': [], 'status_code': 201, '_next': None, 'request': <PreparedRequest [POST]>, 'reason': 'Created', 'connection': <requests.adapters.HTTPAdapter object at 0x7f56ebdd75c0>, '_content': b'{"status": "template", "name": "9f85f94d-52eb-4aba-a970-ebc3367052fa", "links": [[{"href": "https://oof-has-api:8091/v1/plans/f4c6f2c8-45a7-4a67-a9d5-52c8e1372d37", "rel": "self"}]], "id": "f4c6f2c8-45a7-4a67-a9d5-52c8e1372d37"}', 'headers': {'X-LatestVersion': '1.3.1', 'Content-Type': 'application/json', 'Date': 'Wed, 14 Aug 2019 10:56:19 GMT', 'X-PatchVersion': '1', 'Server': 'nginx/1.14.2', 'Connection': 'keep-alive', 'Content-Length': '228', 'X-MinorVersion': '0'}, '_content_consumed': True, 'cookies': <RequestsCookieJar[]>, 'elapsed': datetime.timedelta(0, 2, 687100), 'url': 'https://oof-has-api:8091/v1/plans/', 'raw': <urllib3.response.HTTPResponse object at 0x7f56ebde0438>, 'encoding': None}]

2019-08-14T10:56:29,965+00:00||Thread-62||OOF_OSDF|a6ffc2dc-af83-11e9-a796-ce8f9b3345ee|DEBUG||10.42.4.26|dev-oof-oof-79f9f55959-fqgs4||||Attempting to read the plan from the conductor provided url https://oof-has-api:8091/v1/plans/f4c6f2c8-45a7-4a67-a9d5-52c8e1372d37

2019-08-14T10:56:29,965+00:00||Thread-62||OOF_OSDF|a6ffc2dc-af83-11e9-a796-ce8f9b3345ee|DEBUG||10.42.4.26|dev-oof-oof-79f9f55959-fqgs4||||Requesting URL: https://oof-has-api:8091/v1/plans/f4c6f2c8-45a7-4a67-a9d5-52c8e1372d37

2019-08-14T10:56:31,497+00:00||Thread-62||OOF_OSDF|a6ffc2dc-af83-11e9-a796-ce8f9b3345ee|DEBUG||10.42.4.26|dev-oof-oof-79f9f55959-fqgs4||||Received response [code: 200, headers: {'X-LatestVersion': '1.3.1', 'Content-Type': 'application/json', 'Date': 'Wed, 14 Aug 2019 10:56:31 GMT', 'X-PatchVersion': '1', 'Server': 'nginx/1.14.2', 'Connection': 'keep-alive', 'Content-Length': '316', 'X-MinorVersion': '0'}, data: {'history': [], 'status_code': 200, '_next': None, 'request': <PreparedRequest [GET]>, 'reason': 'OK', 'connection': <requests.adapters.HTTPAdapter object at 0x7f56ebde0fd0>, '_content': b'{"plans": [{"status": "error", "message": "local variable \'triage_data_trans\' referenced before assignment", "name": "9f85f94d-52eb-4aba-a970-ebc3367052fa", "links": [[{"href": "https://oof-has-api:8091/v1/plans/f4c6f2c8-45a7-4a67-a9d5-52c8e1372d37", "rel": "self"}]], "id": "f4c6f2c8-45a7-4a67-a9d5-52c8e1372d37"}]}', 'headers': {'X-LatestVersion': '1.3.1', 'Content-Type': 'application/json', 'Date': 'Wed, 14 Aug 2019 10:56:31 GMT', 'X-PatchVersion': '1', 'Server': 'nginx/1.14.2', 'Connection': 'keep-alive', 'Content-Length': '316', 'X-MinorVersion': '0'}, '_content_consumed': True, 'cookies': <RequestsCookieJar[]>, 'elapsed': datetime.timedelta(0, 1, 509218), 'url': 'https://oof-has-api:8091/v1/plans/f4c6f2c8-45a7-4a67-a9d5-52c8e1372d37', 'raw': <urllib3.response.HTTPResponse object at 0x7f56ebdcf048>, 'encoding': None}]

2019-08-14T10:56:31,498+00:00||Thread-62||OOF_OSDF|a6ffc2dc-af83-11e9-a796-ce8f9b3345ee|DEBUG||10.42.4.26|dev-oof-oof-79f9f55959-fqgs4||||Requesting URL: http://so-bpmn-infra.onap:8081/mso/WorkflowMessage/oofResponse/9f85f94d-52eb-4aba-a970-ebc3367052fa

 

Thanks & Regards,

 

Vamshi Krishna | Tech Mahindra

Sharda Centre, Off Karve Road, Erandwane, Pune 411 004, INDIA

Mobile: +91 9848639561, ext : 3492

Email Id – vn00480215@...

  

 

 

 

From: Ying, Ruoyu <ruoyu.ying@...>
Sent: Wednesday, August 14, 2019 7:19 AM
To: onap-discuss@...; Vamshi Namilikonda <VN00480215@...>
Subject: RE: [onap-discuss] [SO][OOF] error while instantiating service

 

Hi Vamshi,

 

This error mainly happens when there’s something wrong with the optimization policy that is needed for placement. May you try login to the osdf pod and copy the debug log(especially the payload it send to conductor) here? That will help us to locate the root cause for the problem. Thanks.

 

Best Regards,

Ruoyu

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of vamshi
Sent: Tuesday, August 13, 2019 5:42 PM
To: onap-discuss@...
Subject: [onap-discuss] [SO][OOF] error while instantiating service

 

Hello SO/OOF team,

 

I’m trying vFW automation script for instantiating vFW use case. By following page https://github.com/onap/integration/tree/master/test/hpa_automation/heat

I was facing below issue in SO while it is trying to request OOF , have pulled log from - dev-so-so-bpmn-infra-5b4f566958-7jql6. The detailed log has attached to this mail. Could you please suggest any thoughts with your observations. Thank you

 

 

 

2019-08-13T06:49:14.926Z|5899cd91-80a9-4adc-9b09-40ce5340a0e0| org.onap.so.bpmn.common.scripts.OofHoming - OOF Async Callback Response is: "{\"externalApplicationDetails\": {\"httpMethod\": \"GET\", \"httpStatusCode\": 200, \"responseMessage\": {\"plans\": [{\"name\": \"c8fc2537-3080-4cc7-873e-82e1a404550d\", \"status\": \"error\", \"id\": \"375bcb8e-5ab8-403f-940f-306e5068363f\", \"links\": [[{\"rel\": \"self\", \"href\": \"https://oof-has-api:8091/v1/plans/375bcb8e-5ab8-403f-940f-306e5068363f\"}]], \"message\": \"local variable 'triage_data_trans' referenced before assignment\"}]}, \"url\": \"https://oof-has-api:8091/v1/plans/375bcb8e-5ab8-403f-940f-306e5068363f\"}, \"serviceException\": {\"text\": \"A request exception has occurred when contacting an external system\", \"errorType\": \"InterfaceError\"}}"

2019-08-13T06:49:14.932Z|5899cd91-80a9-4adc-9b09-40ce5340a0e0| org.onap.so.bpmn.core.json.JsonUtils - getJsonRawValue(): unable to parse json to retrieve value for field=solutions.placementSolutions. Exception was: org.json.JSONException: A JSONObject text must begin with '{' at 1 [character 2 line 1]

org.json.JSONException: A JSONObject text must begin with '{' at 1 [character 2 line 1]

        at org.json.JSONTokener.syntaxError(JSONTokener.java:433)

        at org.json.JSONObject.<init>(JSONObject.java:194)

        at org.json.JSONObject.<init>(JSONObject.java:321)

        at org.onap.so.bpmn.core.json.JsonUtils.getJsonRawValue(JsonUtils.java:775)

        at org.onap.so.bpmn.core.json.JsonUtils.getJsonRawValue(JsonUtils.java:757)

  

 

 

 

Thanks & Regards,

 

Vamshi Krishna | Tech Mahindra

Sharda Centre, Off Karve Road, Erandwane, Pune 411 004, INDIA

Mobile: +91 9848639561, ext : 3492

Email Id – vn00480215@...

  

 

 

 

============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================


Re: [SO][OOF][MultiCloud] error while instantiating VF module

Multanen, Eric W
 

From the SO config side – looks like what you’ve configured is ok.

 

The multicloud logs – both on registration and vf module create indicate that multicloud is having trouble making requests to your cloud.

 

Do the user credentials you’re using for that cloud have the level of authorization to make these requests?  Have you verifying manually from a CLI perhaps?

 

It appears the main issue at the moment is the multicloud-ocata plugin talking to your Stein cloud.  First guess is something to do with the credentials.  

 

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Sunilkumar Shivangouda Biradar
Sent: Wednesday, August 21, 2019 10:44 PM
To: Multanen, Eric W <eric.w.multanen@...>; onap-discuss@...; seshu.kumar.m@...; rene.robert@...; bin.yang@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Seshu/Eric,

 

As per discussion we had during yesterday’s SO-Weekly call, sharing proper steps followed and fresh logs.

 

Steps followed:

  1. Cloud region created with these details. (Please refer to AAI_Cloud_Details.txt attached)   

 

Note: we are using Stein version (3.19.0) of openstack.

 

  1. Modified the identity_services table of catalogdb with Identity_url =”http://msb-iag.onap:80/api/multicloud/v0/CloudOwner_RegionOne/identity/v2.0”.
  2. Modified the cloud_sites table as shown below

 

 

  1. Did Setting of SO BPMN to use the VNF API v2 (post changing this, deleted the so-bpmn pod and the pod restarted successfully)

 

                    vnf:

                       endpoint: http://so-openstack-adapter.onap:8087/services/VnfAdapter

                       rest:

                         endpoint: http://so-openstack-adapter.onap:8087/services/rest/v2/vnfs

 

 

  1. Tried to register the cloud with multicloud using following API

curl -vvv -X POST http://10.211.1.20:30280/api/multicloud/v1/CloudOwner/RegionOne/registry -H 'Accept: application/json' -H 'Cache-Control: no-cache' -H 'Content-Type: application/json'

 

Note: did not understand why multicloud added "identity-url": "http://msb-iag.onap:80/api/multicloud-ocata/v0/CloudOwner_RegionOne/identity/v2.0"  to the AAI cloud region detail (we are using Stein version (3.19.0) of openstack)

 

I see errors in multicloud-ocata pod as shown below(full log file attached : multicloud-ocata_pod_logs.txt)

                2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_get_list_resources||DEBUG||making request with URI:projects,{'service_type': 'identity', 'interface': 'public'}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_discover_tenants||ERROR||HttpError: status:401, response:{u'error': {u'message': u'The request you have made requires authentication.', u'code': 401, u'title': u'Unauthorized'}}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_get_list_resources||DEBUG||making request with URI:/flavors/detail,{'service_type': 'compute', 'interface': 'public', 'region_name': u'RegionOne'}||||requestID= invocationID= serviceName= serviceIP=

2019-08-22 03:40:46|||||common.msapi.helper||140461866624768||_discover_flavors||ERROR||HttpError: status:401, response:{u'error': {u'message': u'The request you have made requires authentication.', u'code': 401, u'title': u'Unauthorized'}}||||requestID= invocationID= serviceName= serviceIP=

 

  1. Triggered VF Creation from VID portal (using VNF-API) with SNDC preload: VF Creation failed with error from multicloud.

Debug log file attached for SO-Openstack pod : VFCreation_SO_Openstack_pod_logs.txt

Log file attached from multicloud-ocata pod : VFCreation_Multicloud-ocata_pod_logs.txt

 

Snippet from SO-Openstack logs:

2019-08-22T04:23:20.279Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Making GET request to: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Request Headers: {Project=[c673af272d074170881559797f46b89d], Accept=[application/json], X-ONAP-RequestID=[5140aff8-5c26-4909-a443-84b8c36bff89], X-ONAP-InvocationID=[023572a9-79af-4802-9298-1265cff23e48], X-ONAP-PartnerName=[SO]}

2019-08-22T04:23:20.491Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Response from GET: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Response Headers: {Allow=[GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS], connection=[keep-alive], content-type=[text/html; charset=utf-8], Date=[Thu, 22 Aug 2019 04:23:20 GMT], Server=[openresty], transfer-encoding=[chunked], Vary=[Cookie], X-Frame-Options=[SAMEORIGIN]}<h1>Server Error (500)</h1>

 

Need your expertise in resolving this issue.

 

Thanks & Regards,

Sunil B

 

From: Multanen, Eric W <eric.w.multanen@...>
Sent: Wednesday, August 21, 2019 7:02 PM
To: onap-discuss@...; seshu.kumar.m@...; Sunilkumar Shivangouda Biradar <SB00577584@...>; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Per Seshu’s comment – yes, there is some apparent mismatch in the different log samples.

 

In the first log sample (down at the bottom) – it appears that configuration for using Multicloud via has been done (logs indicate usage of the Multicloud infrastructure workload API

http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

and messages are coming from org.onap.so.openstack.utils.MsoMulticloudUtils

 

In the more recent log sample, the logs coming from MsoHeatUtils show that the multicloud plugin in SO is not being used.

(ok – just spotted it – in the second case, the log indicates that the ‘orchestrator’ column for the cloud region is ‘null’ instead of ‘multicloud’)

 

 

The two key configs are:

  1. setting the SO BPMN to use the VNF API v2
  2. having ‘multicloud’ for the cloudregion in ‘orchestrator’ column of SO cloud_sites catalogdb table.

 

Sunil – to your recent question on the keystone url – when SO BPMN and the cloud region is configured as above, then the keystone url in SO is not used.   The authentication to the cloud region is

handled by the multicloud component – which goes back to the cloud registration process that includes the POST to /api/multicloud-titaniumcloud/v1/{{cloud-owner}}/{{cloud-region-id}}/registry

(and, the step of setting ‘multicloud’ in the ‘orchestrator’ column)

 

Eric

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of seshu kumar m
Sent: Wednesday, August 21, 2019 5:24 AM
To: onap-discuss@...; sb00577584@...; Multanen, Eric W <eric.w.multanen@...>; rene.robert@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Sunil

 

Did you change the orchestration type to Multicloud in SO, before trying this?

It seems there is some config mismatch issue with the intension and the actual execution from the logs.

 

Thanks and Regards,

M Seshu Kumar

Senior System Architect

Single OSS India Branch Department. S/W BU.

Huawei Technologies India Pvt. Ltd.

Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield

Bengaluru-560066, Karnataka.

Tel: + 91-80-49160700 , Mob: 9845355488

Company_logo

___________________________________________________________________________________________________

This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

-------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Sunilkumar Shivangouda Biradar
Sent: Wednesday, August 21, 2019 11:04 AM
To: Multanen, Eric W <eric.w.multanen@...>; onap-discuss@...; rene.robert@...
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Eric,

 

Thanks for reply, as mentioned in the second issue may I know the keystone url is proper  keystoneUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0

 

Because here I am getting responseCode as 401

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoCommonUtils - Config values RetryDelay:5 RetryCount:3  RetryCodes:504 ResponseCode:401

 

 

Thanks & Regards,

Sunil B

 

 

From: Multanen, Eric W <eric.w.multanen@...>
Sent: Tuesday, August 20, 2019 10:39 PM
To: Sunilkumar Shivangouda Biradar <SB00577584@...>; onap-discuss@...; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

This is what I’ve been using:  http://{{MSB_IP}}:{{MSB_PORT}}/api/multicloud-titaniumcloud/v1/{{cloud-owner}}/{{cloud-region-id}}/registry

 

From: Sunilkumar Shivangouda Biradar <SB00577584@...>
Sent: Tuesday, August 20, 2019 7:08 AM
To: onap-discuss@...; Multanen, Eric W <eric.w.multanen@...>; rene.robert@...
Subject: RE: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Rene/Eric,

 

Thanks for reply, I followed the page which you suggested.

 

1.      Registering cloud site with multicloud as per document, but got 500 Internal server error.
               Found that there is different API “/api/multicloud/v1/MyCompanyName/INTEGRATION_CENTER/registry”, here I got 202 Unknown Status Code.
               Also tried with “/api/multicloud-titaniumcloud/v1/MyCompanyName/INTEGRATION_CENTER/registry, here I got 202 Accepted.
 
             May I know which API we need to use for registering? 

 

2.       In between I got to know that api changed from “MyCompanyName_INTEGRATION_CENTER/identity/v2.0” to “MyCompanyName/INTEGRATION_CENTER/identity/v2.0” for identity_url. 

                After this modification I got error as below

 

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - Found: CloudSite_.._jvsta6b_3c[regionId=RegionOne,identityServiceId=MC_KEYSTONE,cloudVersion=2.5,clli=RegionOne,cloudifyId=<null>,platform=<null>,orchestrator=<null>]

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - Found: CloudIdentity[id=MC_KEYSTONE,identityUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0,msoId=onap-tm5g-01,projectDomain=<null>,userDomain=<null>,adminTenant=service,memberRole=admin,tenantMetadata=true,identityServerType=KEYSTONE,identityAuthenticationType=USERNAME_PASSWORD]

2019-08-20T11:06:37.330Z|| org.onap.so.openstack.utils.MsoHeatUtils - keystoneUrl=http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/identity/v2.0

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoCommonUtils - Config values RetryDelay:5 RetryCount:3  RetryCodes:504 ResponseCode:401

2019-08-20T11:06:38.039Z|| org.onap.so.openstack.utils.MsoHeatUtils - RA_CONNECTION_EXCEPTION 200 Openstack Exception on Token request:

org.onap.so.openstack.exceptions.MsoAdapterException: Authentication Failure: tenant=c673af272d074170881559797f46b89d,cloud=MC_KEYSTONE

        at org.onap.so.openstack.utils.MsoHeatUtils.getHeatClient(MsoHeatUtils.java:871)

        at org.onap.so.openstack.utils.MsoHeatUtils.queryStack(MsoHeatUtils.java:502)

        at org.onap.so.adapters.vnf.MsoVnfAdapterImpl.createVfModule(MsoVnfAdapterImpl.java:653)

 

 

Please suggest on this issue.

 

Thanks & Regards,

Sunil B

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Multanen, Eric W via Lists.Onap.Org
Sent: Monday, August 19, 2019 9:53 PM
To: onap-discuss@...; rene.robert@...; Sunilkumar Shivangouda Biradar <SB00577584@...>
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

I have the same suggestion – check that your cloud region has been setup and registered per the link.

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Rene Robert via Lists.Onap.Org
Sent: Monday, August 19, 2019 7:16 AM
To: onap-discuss@...; sb00577584@...; Multanen, Eric W <eric.w.multanen@...>
Subject: Re: [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

About cloud_site, there is that user-guide

 

https://onap.readthedocs.io/en/latest/guides/onap-user/cloud_site/index.html

 

maybe it could help

 

Best regards

 

 

Logo Orange

 

René Robert
«Open and Smart solutions for autOmating Network Services»
ORANGE/IMT/OLN/CNC/NARA/OSONS

 

Fixe : +33 2 96 07 39 29
Mobile : +33 6 74 78 68 43
rene.robert@...

 

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Sunilkumar Shivangouda Biradar
Envoyé : lundi 19 août 2019 12:38
À :
onap-discuss@...; eric.w.multanen@...
Objet : [onap-discuss][SO][OOF][MultiCloud] error while instantiating VF module

 

Hi Team,

 

I am working on vFW usecase with HPA (ONAP version: Dublin)

 

Case 1:- Instantiated VM on openstack but not with specified flavors from OOF

 

I tried to create a VF module from VID using VNF-API and was able instantiate VM on openstack but not with the flavors which was suggested at oof_directives, instead it created the VM with the flavors provided in SDNC_preload and found from so-openstack log that SO was not calling multicloud  API “/api/multicloud/v1/CloudOwner/RegionOne/infra_workload”.

 

Case 2:- VM did not get instantiated, getting error.

 

https://wiki.onap.org/display/DW/Recap+of+Dublin+SO+Multicloud+Plugin+--%3E+Multicloud+Interactions

Got to know from wiki that for HPA we need not make any changes to cloud_site table of catalogdb. (which is leading to Case 1 above). Hence manually I modified orchestrator= “multicloud” for the region I’m using, as show in below table.

 

 

Post changing the cloud_site table I am able to see SO is calling the “/api/multicloud/v1/CloudOwner/RegionOne/infra_workload” API of multicloud.

But getting this below error from SO-openstack log(I made sure that no vf module with this name(vfwhpa_stack_test_24) exists in AAI before triggering vf module creation) :

 

2019-08-19T07:19:29.498Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Query multicloud HEAT stack: vfwhpa_stack_test_24 in tenant c673af272d074170881559797f46b89d

2019-08-19T07:19:29.499Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Multicloud Endpoint is: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

2019-08-19T07:19:29.505Z|| o.onap.so.logging.jaxrs.filter.JaxRsClientLogging - Could not Find Request ID Generating New One: /api/multicloud/v1/CloudOwner/RegionOne/infra_workload

2019-08-19T07:19:29.506Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Making GET request to: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Request Headers: {Project=[c673af272d074170881559797f46b89d], Accept=[application/json], X-ONAP-RequestID=[96718a17-4eeb-41db-b185-88f04799763e], X-ONAP-InvocationID=[bd58d3f1-ecc7-436f-88fb-378ed51a58e2], X-ONAP-PartnerName=[SO]}

2019-08-19T07:19:29.667Z|| o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Response from GET: http://msb-iag.onap:80/api/multicloud/v1/CloudOwner/RegionOne/infra_workload?name=vfwhpa_stack_test_24

Response Headers: {Allow=[GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS], connection=[keep-alive], content-type=[text/html; charset=utf-8], Date=[Mon, 19 Aug 2019 07:19:29 GMT], Server=[openresty], transfer-encoding=[chunked], Vary=[Cookie], X-Frame-Options=[SAMEORIGIN]}{"template_type":"HEAT","workload_status_reason":"authenticate fails:CloudOwner, RegionOne, {\"error\":{\"message\":\"The request you have made requires authentication.\",\"code\":401,\"title\":\"Unauthorized\"}}","workload_status":"GET_FAILED","workload_id":""}

 

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Multicloud GET Response: org.apache.cxf.jaxrs.impl.ResponseImpl@6250c8cb

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - StackInfo to convert: {}

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - HeatStatus = FAILED msg = Internal Server Error

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Stack Status: FAILED

2019-08-19T07:19:29.668Z|| org.onap.so.openstack.utils.MsoMulticloudUtils - Stack Status Message: Internal Server Error

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - Found Existing VDU, status=FAILED

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - RA_VNF_ALREADY_EXIST vfwhpa_stack_test_24 CloudOwner RegionOne c673af272d074170881559797f46b89d VDU queryVdu 300 VF Module vfwhpa_stack_test_24 already exists and is in FAILED state

2019-08-19T07:19:29.668Z|| org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - Create VF: Deployment vfwhpa_stack_test_24 already exists and is in FAILED state in CloudOwner/RegionOne/c673af272d074170881559797f46b89d; requires manual intervention.

2019-08-19T07:19:29.679Z|| org.onap.so.adapters.vnf.BpelRestClient - Sending response to BPEL: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<vfModuleException>

    <messageId>dcfcc4e0-7723-473d-bfcb-dd8b9fe4ff2f-1566199169042</messageId>

    <category>INTERNAL</category>

    <message>Resource vfwhpa_stack_test_24 already exists in owner/cloud/tenant CloudOwner/RegionOne/c673af272d074170881559797f46b89d with ID </message>

   <rolledBack>true</rolledBack>

</vfModuleException>

 

 

Please suggest on this issue.

 

Thanks in advance.

 

Regards,

Sunil B

============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================

_________________________________________________________________________________________________________________________
 
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.

 

 


Re: External DCAE Application (noob question) #dcaegen2 #question #noob

David Perez Caparros
 

Hi David,

we did something similar for the ONAP BBS use case. Perhaps you can start by having a look at the BBS event processor doc here: https://wiki.onap.org/pages/viewpage.action?pageId=60891185 
you can also find demo videos here: https://wiki.onap.org/display/DW/DEMOS+-+R4+Dublin+Demos 

BR,
David

On 22 Aug 2019, at 19:01, David Bainbridge <dbainbri@...> wrote:

Hello,

Is it possible, and what would be the process, to utilize an analytic component that deploys in a separate container, but processes events from the DCAE framework? Is it just a matter of connecting to the "common" message bus (kafka?) and processing the published topics as the data is in a defined format? I am assuming the external component is written in non-Java (C++, Go, Rust, Python ... it really doesn't matter).

avèk respè,
/david


External DCAE Application (noob question) #dcaegen2 #question #noob

David Bainbridge
 

Hello,

Is it possible, and what would be the process, to utilize an analytic component that deploys in a separate container, but processes events from the DCAE framework? Is it just a matter of connecting to the "common" message bus (kafka?) and processing the published topics as the data is in a defined format? I am assuming the external component is written in non-Java (C++, Go, Rust, Python ... it really doesn't matter).

avèk respè,
/david


Re: vDNS use case / issue with SO pub about APPC-READ

Marco Platania
 

Messages published in APPC-LCM-WRITE definitely come from APPC (unless you set the topics differently, which is not the common case). APPC reads from APP-LCM-READ (which is where clients like SO publish). Being APPC-LCM-WRITE a shared channel between APPC and possibly multiple clients, the originator ID is just to express which client sent the input message (in APP-LCM-READ). I believe this is why you see MSO as originator ID.

 

Regarding the actual error, I think your K8S cluster has some nodes out of sync. Try to see if the timestamps in the VMs (or physical hosts) are synchronized. I’m quite sure that’s not an ONAP-related issue.

 

Marco

 

From: D'Alessandro Alessandro Gerardo <alessandro.dalessandro@...>
Date: Thursday, August 22, 2019 at 11:42 AM
To: "PLATANIA, MARCO (MARCO)" <platania@...>, "VENKATESH KUMAR, VIJAY" <vv770d@...>, "onap-discuss@..." <onap-discuss@...>
Cc: "MALAKOV, YURIY" <ym9479@...>, Malinconico Aniello Paolo <a.malinconico@...>, Ferrero Marco Angelo <marco.ferrero@...>
Subject: vDNS use case / issue with SO pub about APPC-READ

 

Hi All,

we are continue working on vDNS use case (https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_scaleout.html ) primarily focusing on closed loop aspects


we successfully carried out the following steps related to the above guide

“PART 1 - Service Definition and Onboarding”

“PART 2 - Scale Out Use Case Instantiation”

“PART 3 - Post Instantiation Operations”

“3-1 Using the VNF : vLB Manual Configuration”… skipped because it was carried out automatically  

“3-2 Updating AAI with VNF resources”

 

After this steps we see vPKG does NOT generates packets. Anyway making that working is not our primary goal at this stage.

We changed the TCA rules as “if packets are LESS than 2000 than call policy operation” and this rules is always satisfied in our case. In fact we have seen MSO publishing a topic “APPC-LCM-READ” asking for "action":"HealthCheck". Refer to attached file “APPC_LCM_READ_messagerouter”

 

In the APP-C log you can also find “InvalidInputException : Input Timestamp is of future” associated to the messages related to the topic “APPC-LCM-READ”. Refer to attached file “appc_log_errortimestamp”

 

Afterwards we have noticed under topic “APPC-LCM-WRITE”  the following  "message":"INVALID INPUT PARAMETER - Input Timestamp is of future = Thu Aug 22 10:28:58 GMT 2019"           followed by  the          

"message":"UNEXPECTED ERROR - java.lang.IllegalStateException". Refer to attached file “APPC_LCM_WRITE_messagerouter”. Such messages are apparently published by MSO because that is the name associated to the field "originator-id" while we expected it was published by APPC as we understood from the  GET http://message-router.onap:3904/events/APPC-LCM-WRITE found in “bpmn_debug_cut.log”).

 

In the MSO log you can find the following error “Error Message: Unable to invoke action : HealthCheck”. Refer to attached file “bpmn_debug_cut.log”

 

 

Do you have any suggestion how to fix such issue?

Is there any document describing the semantic of messages published from both MSO and APPC?

 

Thanks in advance

 

Best regards,

Alessandro

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

Rispetta l'ambiente. Non stampare questa mail se non è necessario.

 

4461 - 4480 of 23111