[app-c] Ansible Server details in appc.properties file


Anumaneni, Venkataramana (Nokia - US/Irving)
 

Hello Taka,

 

Sorry for late response. Yes, I have used “changeit” in all steps below. I will check below links and see if I can solve this issue.

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Friday, June 08, 2018 8:08 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkata,

 

Your steps sounds ok.  I think you are using the password: “changeit” not “change it” for the all steps below.

 

One more thing you could try is verifying the https connectivity with your jks and your ansible server without APPC. I found one link it may help you: https://confluence.atlassian.com/kb/unable-to-connect-to-ssl-services-due-to-pkix-path-building-failed-779355358.html

 

Is your ansible server using your own RESTful script or using the scripts in ONAP repo: https://gerrit.onap.org/r/gitweb?p=appc.git;a=tree;f=appc-adapters/appc-ansible-adapter/appc-ansible-example-server;h=90fa259c3905d1c5f25b9668a6e537a7c1f1a8e4;hb=refs/heads/master?  

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, June 06, 2018 2:45 PM
To: CHO, TAKAMUNE <tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

I have received certificate from Ansible server team in PEM file. I have used below command to create Java truststore from PEM file.

 

oot@nokonap-appc:/home/ubuntu# keytool -import -file taco_cert.pem -alias tacoCA -keystore mykeystore.js

Enter keystore password: <I have entered changeit here>

Re-enter new password: <I have entered changeit here>

Owner: CN=phonehome, EMAILADDRESS=dane.dwyer@..., OU=SI, O=Nokia, L=Murray Hill, ST=New Jersey, C=US

Issuer: CN=phonehome, EMAILADDRESS=dane.dwyer@..., OU=SI, O=Nokia, L=Murray Hill, ST=New Jersey, C=US

Serial number: 9fdeec1c775fa125

Valid from: Thu Mar 15 17:50:20 UTC 2018 until: Sun Mar 12 17:50:20 UTC 2028

Certificate fingerprints:

         MD5:  F0:99:DA:DA:5E:5D:84:C5:16:3E:80:6F:C4:F2:15:xx

         SHA1: 98:A6:BB:67:C9:4B:58:33:9A:DB:FB:CC:01:60:43:A4:D7:53:E5:xx

         SHA256: AF:2C:26:98:53:E5:82:A6:7B:2C:D7:3F:F8:3D:xx:A7:1E:39:C0:B7:C6:8C:93:B7:4F:F1:27:34:F6:83:11:xx

         Signature algorithm name: SHA256withRSA

         Version: 3

 

Extensions:

 

#1: ObjectId: 2.5.29.17 Criticality=false

SubjectAlternativeName [

  DNSName: 135.104.207.168

]

 

Trust this certificate? [no]:  yes

Certificate was added to keystore

root@nokonap-appc:/home/ubuntu# keytool -list -keystore mykeystore.js

Enter keystore password: < I have entered change it here>

 

Keystore type: JKS

Keystore provider: SUN

 

Your keystore contains 1 entry

 

tacoca, Jun 6, 2018, trustedCertEntry,

Certificate fingerprint (SHA1): 98:A6:BB:67:C9:4B:58:33:9A:DB:FB:CC:01:60:43:A4:D7:53:E5:xx

root@nokonap-appc:/home/ubuntu#

 

copy this file to opendaylight directory.

 

root@nokonap-appc:/home/ubuntu# cp /home/ubuntu/mykeystore.js /var/lib/docker/aufs/mnt/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/opendaylight/tls-client/

root@nokonap-appc:/home/ubuntu# ls -lrt /var/lib/docker/aufs/mnt/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/opendaylight/tls-client/

total 4

-rw-rw-r-- 1 root root 1538 Jun  6 18:42 mykeystore.js

root@nokonap-appc:/home/ubuntu#

 

Username is cman and password is “password”.

 

I have restarted all containers and tested it.

 

Please let me know if this helps to find root cause.

 

Regards

Venkat

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Wednesday, June 06, 2018 8:22 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Venkata,

 

Please provide the details step by step of how you generate the keystore file and password for https connection  between APPC and Ansible server and the console log that you did. Without that, I am not able to tell what went wrong in your setting.

 

Thanks

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Tuesday, June 05, 2018 1:33 PM
To: CHO, TAKAMUNE <tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

I have tried with below changes.

 

data/log# locate mykeystore.js

/home/ubuntu/mykeystore.js

/var/lib/docker/aufs/diff/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/opendaylight/tls-client/mykeystore.js

/var/lib/docker/aufs/mnt/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/opendaylight/tls-client/mykeystore.js

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Tuesday, June 05, 2018 11:04 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Venkata,

 

The default.properties is built on /opt/opendaylight/current/system/org/onap/appc/appc-ansible-adapter-bundle/1.3.0-SNAPSHOT/appc-ansible-adapter-bundle-1.3.0-SNAPSHOT.jar.

 

remove those values in appc.properties.

 

use and regenerate the truststore file with the default values of the default.properties in Repo below:

 

  org.onap.appc.adapter.ansible.trustStore=/opt/opendaylight/tls-client/mykeystore.js

  org.onap.appc.adapter.ansible.trustStore.trustPasswd=changeit

org.onap.appc.adapter.ansible.clientType=DEFAULT

 

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Monday, June 04, 2018 5:22 PM
To: CHO, TAKAMUNE <tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

We don’t have this file on APP-C.

 

root@nokonap-appc:~# locate default.properties

root@nokonap-appc:~#

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Monday, June 04, 2018 3:54 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkata,

 

As I stated before. You need to put those properties in

 

/appc-ansible-adapter-bundle/src/main/resources/org/onap/appc/default.properties.

 

Not in appc.properties.

 

Please try that. And let me know the result.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Monday, June 04, 2018 3:12 PM
To: CHO, TAKAMUNE <tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

I am still facing same issue even after doing lot of configuration changes. Below are the issues.

 

APPC Ansible Adapter is not taking configuration parameter from appc.properties file.

 

My appc.properties contains below parameters. I have restarted APPC with TRUST_all parameters also.

 

org.onap.appc.adapter.ansible.clientType=TRUST_CERT

org.onap.appc.adapter.ansible.trustStore=/opt/openecomp/appc/data/stores/truststore.openecomp.taco.jks

org.onap.appc.adapter.ansible.trustStore.trustPasswd=adminadmin

 

2018-06-04 18:53:21,305 | INFO  | Event Dispatcher | AnsibleAdapterImpl               | 402 - appc-ansible-adapter - 1.2.0 | Creating http client with default behaviour

 

I have followed steps mentioned at below link to create trust store.

 

https://docs.oracle.com/cd/E19509-01/820-3503/6nf1il6er/index.html

 

I am still facing same issue when I send request.

 

2018-06-04 18:08:34,091 | ERROR | ppc-dispatcher-1 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Ansible Adapter Error = Error posting request. Reason = sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

        at org.openecomp.appc.adapter.ansible.impl.AnsibleAdapterImpl.doFailure(AnsibleAdapterImpl.java:207)

        at org.openecomp.appc.adapter.ansible.impl.AnsibleAdapterImpl.reqExec(AnsibleAdapterImpl.java:325)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.CallNodeExecutor.execute(CallNodeExecutor.java:127)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.CallNodeExecutor.execute(CallNodeExecutor.java:127)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

 

If I use http it works but APPC doesn’t send authentication parameters in request whereas Ansible Server expects authentication parameters.

 

Please help me to solve this issue.

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 31, 2018 3:06 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkat,

 

TRUST_ALL value should be fine.

 

From the error you got (I excerpted)

 

Error posting request. Reason = sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

 

It sounds like your trusted keysore js file is not correct when you generated. Did you try to verify your js file from other CLI tools like open_ssl etc?

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, May 30, 2018 6:09 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

Thanks. I have actually added below parameter in appc.properties file to trust all Ansible Servers. But, It still expects certificate to be available in store.

 

root@nokonap-appc:~# grep org.onap.appc.adapter.ansible.clientType /opt/appc/installation/src/main/properties/appc.propertiesorg.onap.appc.adapter.ansible.clientType=TRUST_ALL

 

 

Regards

Venkat

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Wednesday, May 30, 2018 3:36 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

HI Venkata.

 

The path for the keystore key is defined on /appc-ansible-adapter-bundle/src/main/resources/org/onap/appc/default.properties

Which is https://gerrit.onap.org/r/gitweb?p=appc.git;a=blob;f=appc-adapters/appc-ansible-adapter/appc-ansible-adapter-bundle/src/main/resources/org/onap/appc/default.properties;h=d49c0396c5984fb8d46b2b3cf1f572223c8d5c6c;hb=refs/heads/master

 

I assume you know how to generate the trusted keystore file.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, May 30, 2018 3:12 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

We could pass “Unable decrypt the password”  error. Now, we are facing an issue with SSL certification.

Could you please help us to find the path to store certificates and other settings to solve this error?

 

2018-05-29 18:50:05,809 | ERROR | ppc-dispatcher-6 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Error posting request. Reason = sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

        at Proxye981c0ea_91ea_409d_8ef6_23c4fb2c32b1.execute(Unknown Source)

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.SVCLogicServiceExecute(WorkFlowManagerImpl.java:251)[384:appc-workflow-management-core:1.2.0]

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.executeWorkflow(WorkFlowManagerImpl.java:154)[384:appc-workflow-management-core:1.2.0]

        at Proxy405593b3_30f4_4ec4_83f6_6bbd2a7cb808.executeWorkflow(Unknown Source)

        at Proxy03b18168_8c75_4e04_8865_048a156628fb.executeWorkflow(Unknown Source)

        at org.openecomp.appc.executor.impl.CommandTask.execute(CommandTask.java:79)

        at org.openecomp.appc.executor.impl.LCMCommandTask.run(LCMCommandTask.java:175)

        at org.openecomp.appc.executionqueue.impl.QueueManager.lambda$enqueueTask$0(QueueManager.java:118)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_151]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_151]

        at java.lang.Thread.run(Thread.java:748)[:1.8.0_151]

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Friday, May 18, 2018 1:44 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkat,

 

I think there is something wrong when you are doing encrypt password.

 

There is the java code here: https://gerrit.onap.org/r/gitweb?p=appc.git;a=blob;f=appc-config/appc-encryption-tool/provider/src/main/java/org/onap/appc/encryptiontool/wrapper/WrapperEncryptionTool.java;h=6091e4cf275eb217f5fe2f230a425c95e2159904;hb=refs/heads/master

 

That can help you generate encrypted password for appc_southbound properties.

 

There is a wrapper script for this WrapperEncryptionTool.class in the attachment. You may need to change some lines for your env. I will add this script in APPC Repo for R3 later…

 

Hope that would help

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Friday, May 18, 2018 9:52 AM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

I have tried without username and password and facing same issue.

 

Below is the appc_southbound.properties file.

 

Also, Attached is the log file.

 

root@nokonap-appc:/# more ./var/lib/docker/aufs/mnt/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/app/bvc/properties/appc_southbound.properties

mrf2\/MRF\ 0.ANSIBLE.Configure.user=cman

mrf2\/MRF\ 0.ANSIBLE.Configure.port=8084

mrf2\/MRF\ 0.ANSIBLE.Configure.password=313DECE408AF7759D442D7B06DD9A6AA

mrf2\/MRF\ 0.ANSIBLE.Configure.url=https://10.203.134.105:8084/api/v1/ansibleserver

root@nokonap-appc:/#

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 17, 2018 3:46 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkat,

 

Can you try the payload without user and password?

 

And attach the appc_southbount.properties and full log?

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Thursday, May 17, 2018 3:33 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

Payload didn’t have username and password earlier and I was still facing same issue. So, I thought, I will give try with including password.

 

Also, appc_southbound.properties file has username and password(encrypted).

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 17, 2018 1:06 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

HI Venkat,

 

The log  says “error-message -- Unable to decrypt the password”. The user name and password should not be in the payload.

Those are supposed to update it in properties file which is appc southbound properties I mentioned before . Code will not read user id and password from payload.

 

From their payload

   "appc-provider-lcm:payload": "{\"Id\": \"$requestID\",\"PlaybookName\": \"vmmsc@playbook_linux@...\",\"NodeList\": [\"CMAN-TACO-MMSC1\" ],\"password\": \"313DECE408AF7759D442D7B06DD9A6AA\", \"Timeout\": 600, \"EnvParameters\": { \"working_dir\": \"/var/log\",\"command\": \"ls\", \"user_name\": \"root\",\"host_name\": \"mmsc\" }}"

 

From log

NodeList[0] -- CMAN-TACO-MMSC1

2018-05-16 20:13:18,925 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  template-name --

2018-05-16 20:13:18,925 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-message -- Unable to decrypt the password.

2018-05-16 20:13:18,925 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  input.common-header.sub-request-id -- 1-1

2018-05-16 20:13:18,925 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  SvcLogic.status -- failure

2018-05-16 20:13:18,926 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  input.common-header.request-id -- 10

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, May 16, 2018 4:31 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

Attached is log. Below is the request sent to configure. Please let me know if I am missing any thing.

 

{

"appc-provider-lcm:input": {

"appc-provider-lcm:action":"Configure",   

 "appc-provider-lcm:action-identifiers": {

"appc-provider-lcm:vnf-id": "d9d69025-0852-49a9-8982-d71553a557e4"

},

"appc-provider-lcm:common-header": {

      "appc-provider-lcm:request-id": "9",

      "appc-provider-lcm:originator-id": "venkat",

      "appc-provider-lcm:api-ver": "2.43",

      "appc-provider-lcm:timestamp": "2018-05-16T20:11:55.55Z",

      "appc-provider-lcm:sub-request-id": "1-1",

      "appc-provider-lcm:flags": {

        "appc-provider-lcm:ttl": "0",

        "appc-provider-lcm:force": "TRUE",

        "appc-provider-lcm:mode": "NORMAL"

}

},

   "appc-provider-lcm:payload": "{\"Id\": \"$requestID\",\"PlaybookName\": \"vmmsc@playbook_linux@...\",\"NodeList\": [\"CMAN-TACO-MMSC1\" ],\"password\": \"313DECE408AF7759D442D7B06DD9A6AA\", \"Timeout\": 600, \"EnvParameters\": { \"working_dir\": \"/var/log\",\"command\": \"ls\", \"user_name\": \"root\",\"host_name\": \"mmsc\" }}"

}

}

 

Regards

Venkat

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Monday, May 14, 2018 1:04 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkat,

 

Yes. User would provide their own credentials for Ansible Server RESTful API.

 

Maybe you missed my previous email, I assume you followed this : https://gerrit.onap.org/r/gitweb?p=appc.git;a=tree;f=appc-adapters/appc-ansible-adapter/appc-ansible-example-server;h=90fa259c3905d1c5f25b9668a6e537a7c1f1a8e4;hb=refs/heads/master for setting up RESTful API in Ansible server.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Monday, May 14, 2018 11:05 AM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

Sorry I missed your email.

 

My question, Do we need provider credentials as Ansible Server REST API shouldn’t be configured with credentials as per ONAP documentation.

 

mrf2\/MRF\ 0.ANSIBLE.Configure.user=<username>

mrf2\/MRF\ 0.ANSIBLE.Configure.port=8084

mrf2\/MRF\ 0.ANSIBLE.Configure.password=<encrypted password>

mrf2\/MRF\ 0.ANSIBLE.Configure.url=https://<IP>:8084/ui

                                  

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Monday, May 14, 2018 9:25 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hi Venkat,

 

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-code -- 401

 

So you got 401 error back. Did you try to use other cli tools like openssl or curl command to test the connection with the password that you used?

 

Also Can you attach the appc_southbound.properties file?

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Friday, May 11, 2018 5:33 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

Below is the latest status.

 

It was looking for “appc_southbound.properties” file at /opt/app/bvc/properties/. I have created this file.

 

2018-05-11 20:08:30,490 | ERROR | ppc-dispatcher-5 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Cannot locate configuration source /opt/app/bvc/properties/appc_southbound.properties

 

After this, It says that It is “Unable to decrypt the password”. I tried to encrypt the password using “so” VM but it still fails at the same place.

 

Any help to fix this issue would be appreciated.

 

2018-05-11 21:24:52,271 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  password -- password

2018-05-11 21:24:52,271 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  request-action -- Configure

2018-05-11 21:24:52,271 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  configurationblock --

2018-05-11 21:24:52,271 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  EnvParameters --

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  EnvParameters.host_name -- mmsc

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  VNFCNAME0 --

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  api-ver --

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  EnvParameters.working_dir -- /var/log

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-code -- 401

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  vnfc-type --

2018-05-11 21:24:52,273 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  EnvParameters.user_name -- root

2018-05-11 21:24:52,273 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  vf-module-id --

2018-05-11 21:24:52,273 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  tmp.vnfInfo.vm-count -- 0

2018-05-11 21:24:52,273 | INFO  | ppc-dispatcher-1 | FlowControlNode                  | 360 - appc-common - 1.2.0 | Handling Response for transaction Id 1

2018-05-11 21:24:52,274 | INFO  | ppc-dispatcher-1 | DefaultResponseHandler           | 360 - appc-common - 1.2.0 | Transaction Input params Transaction [transactionId=1, action=Configure, actionLevel=vnf, actionIdentifier=null, parameters=null, executionType=graph, uId=null, statusCode=401, pswd=null, executionEndPoint=null, executionModule=APPC, executionRPC=Generic_AnsibleDG, state=null, precheck=null, payload={"Id": "$requestID","PlaybookName": "vmmsc@playbook_linux@...","NodeList": ["CMAN-TACO-MMSC1" ],"Timeout": 600, "EnvParameters": { "working_dir": "/var/log","command": "ls", "user_name": "root","host_name": "mmsc" }}, responses=[Response [responseCode=null, responseMessage=null, responseAction=ResponseAction [wait=null, retry=null, jump=null, ignore=false, stop=true, intermediateMessage=false], responseActionHanlder=null]], status=failure]

2018-05-11 21:24:52,274 | INFO  | ppc-dispatcher-1 | FlowControlNode                  | 360 - appc-common - 1.2.0 | Executed all the transacstion successfully

2018-05-11 21:24:52,275 | ERROR | ppc-dispatcher-1 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Unable to decrypt the password.

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

 

Regards

Venkat

 

 

From: Anumaneni, Venkataramana (Nokia - US/Irving)
Sent: Friday, May 11, 2018 3:11 PM
To: 'CHO, TAKAMUNE' <
tc012c@...>; 'onap-discuss@...' <onap-discuss@...>
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

I have found this issue. I think, EXECUTION_RPC should be “Generic_AnsibleDG” when PROTOCOL is “Ansible”.

Please correct me if I am wrong.

 

 

mysql> select * from PROCESS_FLOW_REFERENCE where ACTION="Configure" and ACTION_LEVEL="vnf" and PROTOCOL="Ansible";

+---------------------------+-----------+--------------+----------+----------------+------------------+-------------------+---------------------+--------------------+

| PROCESS_FLOW_REFERENCE_ID | ACTION    | ACTION_LEVEL | PROTOCOL | EXECUTION_TYPE | EXECUTION_MODULE | EXECUTION_RPC     | UPDATED_DATE        | GET_RUNNING_CONFIG |

+---------------------------+-----------+--------------+----------+----------------+------------------+-------------------+---------------------+--------------------+

|                        24 | Configure | vnf          | Ansible  | graph          | APPC             | Generic_Configure | 2017-08-25 19:40:05 | NULL               |

|                        52 | Configure | vnf          | Ansible  | graph          | APPC             | Generic_Configure | 2017-09-12 16:49:54 | NULL               |

+---------------------------+-----------+--------------+----------+----------------+------------------+-------------------+---------------------+--------------------+

2 rows in set (0.00 sec)

 

 

Regards

Venkat

 

 

From: Anumaneni, Venkataramana (Nokia - US/Irving)
Sent: Friday, May 11, 2018 2:27 PM
To: 'CHO, TAKAMUNE' <
tc012c@...>; 'onap-discuss@...' <onap-discuss@...>
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

After further analysis, APPC should search with “APPC,ansible-adapter-1.0,2.0.1,sync “ instead of “APPC,Generic_Configure,null,sync”.

 

How does APPC gets these parmeters?

 

Regards

Venkat

 

 

From: Anumaneni, Venkataramana (Nokia - US/Irving)
Sent: Friday, May 11, 2018 2:12 PM
To: 'CHO, TAKAMUNE' <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

I have found the root cause of the below error. There were no entries in PROTOCOL_REFERENCE table for this vnf type. After adding entry and make it Ansible, it went further and now it failed while fetching sevice logic.

 

Do I have to add any entry in Service logic table manually?

 

2018-05-11 18:53:54,950 | INFO  | ppc-dispatcher-3 | SvcLogicServiceImpl              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Fetching service logic from data store

2018-05-11 18:53:54,952 | INFO  | ppc-dispatcher-3 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-message -- No service logic found for [APPC,Generic_Configure,null,sync]

2018-05-11 18:53:54,955 | INFO  | ppc-dispatcher-3 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-code -- 401

2018-05-11 18:53:54,955 | INFO  | ppc-dispatcher-3 | FlowControlNode                  | 360 - appc-common - 1.2.0 | Handling Response for transaction Id 1

2018-05-11 18:53:54,956 | INFO  | ppc-dispatcher-3 | DefaultResponseHandler           | 360 - appc-common - 1.2.0 | Transaction Input params Transaction [transactionId=1, action=Configure, actionLevel=vnf, actionIdentifier=null, parameters=null, executionType=graph, uId=null, statusCode=401, pswd=null, executionEndPoint=null, executionModule=APPC, executionRPC=Generic_Configure, state=null, precheck=null, payload={"Id": "$requestID","PlaybookName": "vmmsc@playbook_linux@...","NodeList": ["CMAN-TACO-MMSC1" ],"Timeout": 600, "EnvParameters": { "working_dir": "/var/log","command": "ls", "user_name": "root","host_name": "mmsc" }}, responses=[Response [responseCode=null, responseMessage=null, responseAction=ResponseAction [wait=null, retry=null, jump=null, ignore=false, stop=true, intermediateMessage=false], responseActionHanlder=null]], status=Others]

2018-05-11 18:53:54,956 | INFO  | ppc-dispatcher-3 | FlowControlNode                  | 360 - appc-common - 1.2.0 | Executed all the transacstion successfully

2018-05-11 18:53:54,957 | ERROR | ppc-dispatcher-3 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: No service logic found for [APPC,Generic_Configure,null,sync]

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

        at Proxy3dac49de_249e_44ea_9178_3251aea35ebb.execute(Unknown Source)

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.SVCLogicServiceExecute(WorkFlowManagerImpl.java:251)[384:appc-workflow-management-core:1.2.0]

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.executeWorkflow(WorkFlowManagerImpl.java:154)[384:appc-workflow-management-core:1.2.0]

        at Proxy01e5329d_f310_47f5_a8dc_16266785b6dd.executeWorkflow(Unknown Source)

        at Proxy6b0c2d51_9818_434e_8f3f_6d2dfbedb96b.executeWorkflow(Unknown Source)

        at org.openecomp.appc.executor.impl.CommandTask.execute(CommandTask.java:79)

        at org.openecomp.appc.executor.impl.LCMCommandTask.run(LCMCommandTask.java:175)

        at org.openecomp.appc.executionqueue.impl.QueueManager.lambda$enqueueTask$0(QueueManager.java:118)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_151]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_151]

        at java.lang.Thread.run(Thread.java:748)[:1.8.0_151]

2018-05-11 18:53:54,966 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (401) not found, keys are { (400) (Other)}

2018-05-11 18:53:54,997 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (success) not found, keys are { (failure)}

2018-05-11 18:53:54,997 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (failure)}

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Friday, May 11, 2018 1:28 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hi Vankat,

 

Can you attach your full log? The part of the log below does not help not much to check further.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Friday, May 11, 2018 12:02 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

I am able to add those entries. It is able to get capabilities. However, I am facing below error now.

 

2018-05-11 15:21:22,698 | INFO  | ppc-dispatcher-1 | ConfigResourceNode               | 360 - appc-common - 1.2.0 | getCapability Successful

2018-05-11 15:21:22,699 | INFO  | ppc-dispatcher-1 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome ("") not found, keys are { (Not-Supported) (Supported) (Other)}

2018-05-11 15:21:22,815 | ERROR | ppc-dispatcher-1 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Don't know how to execute transaction ID 1

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

        at Proxy3dac49de_249e_44ea_9178_3251aea35ebb.execute(Unknown Source)

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.SVCLogicServiceExecute(WorkFlowManagerImpl.java:251)[384:appc-workflow-management-core:1.2.0]

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.executeWorkflow(WorkFlowManagerImpl.java:154)[384:appc-workflow-management-core:1.2.0]

        at Proxy01e5329d_f310_47f5_a8dc_16266785b6dd.executeWorkflow(Unknown Source)

        at Proxy6b0c2d51_9818_434e_8f3f_6d2dfbedb96b.executeWorkflow(Unknown Source)

        at org.openecomp.appc.executor.impl.CommandTask.execute(CommandTask.java:79)

        at org.openecomp.appc.executor.impl.LCMCommandTask.run(LCMCommandTask.java:175)

        at org.openecomp.appc.executionqueue.impl.QueueManager.lambda$enqueueTask$0(QueueManager.java:118)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_151]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_151]

        at java.lang.Thread.run(Thread.java:748)[:1.8.0_151]

 

My entries are below;

 

mysql> SELECT * FROM ASDC_REFERENCE;

+-------------------+------------+-----------+---------------+--------+---------------+--------------------------------------+

| ASDC_REFERENCE_ID | VNF_TYPE   | VNFC_TYPE | FILE_CATEGORY | ACTION | ARTIFACT_TYPE | ARTIFACT_NAME                        |

+-------------------+------------+-----------+---------------+--------+---------------+--------------------------------------+

|                 1 | mrf2/MRF 0 | NULL      | capability    | NULL   | NULL          | capability_AllAction_vMRF_0.01v.json |

+-------------------+------------+-----------+---------------+--------+---------------+--------------------------------------+

1 row in set (0.00 sec)

 

mysql> SELECT * FROM ASDC_ARTIFACTS;

+-------------------+--------------------------------------+-----------------+--------------+---------------------+-------------------------------------+------------------------+---------------+------------------+---------------+---------------+---------------+------------------+----------------------+------------------+---------------------+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

| ASDC_ARTIFACTS_ID | SERVICE_UUID                         | DISTRIBUTION_ID | SERVICE_NAME | SERVICE_DESCRIPTION | RESOURCE_UUID                       | RESOURCE_INSTANCE_NAME | RESOURCE_NAME | RESOURCE_VERSION | RESOURCE_TYPE | ARTIFACT_UUID | ARTIFACT_TYPE | ARTIFACT_VERSION | ARTIFACT_DESCRIPTION | INTERNAL_VERSION | CREATION_DATE       | ARTIFACT_NAME                        | ARTIFACT_CONTENT                                                                                                                                                                                                                                                                                                                                                          |

+-------------------+--------------------------------------+-----------------+--------------+---------------------+-------------------------------------+------------------------+---------------+------------------+---------------+---------------+---------------+------------------+----------------------+------------------+---------------------+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

|                 1 | 6a000b37-1b4d-4ceb-b5d1-14722f2484f3 | 1               | mrf          | mrfconfigure        | d9d69025-0852-49a9-8982-d71553a557e | mrf                    | m2            | 1525955128862    | mrf2/MRF 0    | 1             | NULL          | NULL             | configure            |                1 | 2018-05-11 14:44:31 | capability_AllAction_vMRF_0.01v.json | {"capabilities":{"vnfc":[],"vm":[{"AttachVolume":[]},{"DetachVolume":[]},{"Evacuate":["pld","ssc"]},{"Migrate":["pld","ssc"]},{"Reboot":["pld","ssc"]},{"Rebuild":["pld","ssc"]},{"Restart":["pld","ssc"]},{"Snapshot":["pld","ssc"]},{"Start":["pld","ssc"]},{"Stop":["pld","ssc"]}],"vf-module":[],"vnf":["Configure","ConfigModify","OpenStack Actions","AllAction"]}} |

+-------------------+--------------------------------------+-----------------+--------------+---------------------+-------------------------------------+------------------------+---------------+------------------+---------------+---------------+---------------+------------------+----------------------+------------------+---------------------+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

1 row in set (0.00 sec)

 

 

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 10, 2018 10:36 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

HI Venkat,

 

I assume you followed the instruction to have APPC in your local env: https://wiki.onap.org/display/DW/Building+and+Running+APPC+Docker+Images.

 

Then you should have mysql container running in your local. The how-to login to mysql container is on the wiki page. And the source script for  creating tables for mysql is at: https://gerrit.onap.org/r/gitweb?p=appc/deployment.git;a=blob;f=installation/appc/src/main/scripts/installAppcDb.sh;h=fc5ae53caafec9a95a5c63e3061510de59a14c60;hb=refs/heads/master

 

Which is triggered from startODL.sh https://gerrit.onap.org/r/gitweb?p=appc/deployment.git;a=blob;f=installation/appc/src/main/scripts/startODL.sh;h=f58db40df0f031ee40d8df3b1c6019c1e5e817fe;hb=refs/heads/master

 

Taka

 

 

 

From: ANUMANENI, VENKATA RAMANA
Sent: Thursday, May 10, 2018 9:59 AM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

I am looking for mysql credentials to add these entries in those tables.

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 10, 2018 8:22 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

HI Venkat,

 

From error in your log, yes. This has to be done.

 

Sorry, What do you mean by “default credentials”?

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, May 09, 2018 6:11 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

Thank you for this. Is this has to be done on APPC?

 

What are the default credentials?

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Wednesday, May 09, 2018 1:55 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hi Venkat,

 

The Configure action is not in the reference file.

 

You would need to insert the capacity plan which has Configure action in two tables in mysql DB:

 

Here is the one sample:

 

On ASDC_ARTIFACTS table:

 

TLSUUID836241290926

TLDID95681

TLServiceName

Template Loader Test

TLRUID95681

TLRIName

null

TLResourceVersion

TLResourceType

TLAUUID95681

null

0.1

SdcTestDescription

41

2018-05-09 11:41:31

capability_AllAction_vUSP-MetaswitchvSBC_0.0.1V.json

{"capabilities":{"vnfc":[],"vm":[{"AttachVolume":[]},{"DetachVolume":[]},{"Evacuate":["pld","ssc"]},{"Migrate":["pld","ssc"]},{"Reboot":["pld","ssc"]},{"Rebuild":["pld","ssc"]},{"Restart":["pld","ssc"]},{"Snapshot":["pld","ssc"]},{"Start":["pld","ssc"]},{"Stop":["pld","ssc"]}],"vf-module":[],"vnf":["Configure","ConfigModify","OpenStack Actions","AllAction"]}}

 

On ASDC_REFERENCE table:

 

1899

vUSP-Metaswitch vSBC

null

capability

null

null

capability_AllAction_vUSP-MetaswitchvSBC_0.0.1V.json

 

Taka

 

 

From: ANUMANENI, VENKATA RAMANA
Sent: Tuesday, May 08, 2018 5:39 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Takamune,

 

Thanks for your support.

 

We have tried changes suggested by you. I sent LCM action configure command through APPC LCM API. Action was accepted but it has failed in service logic at below step.

 

At this moment, LCM API to sent Service Logic and it has queried A&AI successfully. But, Service Logic is not able find any further step.

 

Is there anything I am mssing?

 

 

2018-05-08 15:29:53,286 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (not-found) (failure)}

2018-05-08 15:29:53,289 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (not-found) not found, keys are { (failure)}

2018-05-08 15:29:53,289 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (failure)}

2018-05-08 15:29:53,290 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome ("") not found, keys are { (YES) (Other)}

2018-05-08 15:29:53,343 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (success) not found, keys are { (failure)}

2018-05-08 15:29:53,344 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (failure)}

2018-05-08 15:29:53,344 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (vnf) not found, keys are { (vm) (Other)}

2018-05-08 15:29:53,345 | INFO  | ppc-dispatcher-3 | ConfigResourceNode               | 360 - appc-common - 1.2.0 | Received getCapability call with params : {caplevel=vnf, checkCapability=Configure, vnf-type=MRF/MRF 0}

2018-05-08 15:29:53,346 | INFO  | ppc-dispatcher-3 | DGGeneralDBService               | 360 - appc-common - 1.2.0 | getCapability Query String : select max(internal_version) as maxInternalVersion, artifact_name as artifactName from ASDC_ARTIFACTS  where artifact_name in (select artifact_name from ASDC_REFERENCE  where vnf_type= $vnf-type  and file_category = 'capability' )

2018-05-08 15:29:53,352 | INFO  | ppc-dispatcher-3 | ConfigResourceNode               | 360 - appc-common - 1.2.0 | getCapability::returned from DB::+cap

2018-05-08 15:29:53,353 | INFO  | ppc-dispatcher-3 | ConfigResourceNode               | 360 - appc-common - 1.2.0 | getCapability Successful - No capability blocks found

2018-05-08 15:29:53,353 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome ("") not found, keys are { (Not-Supported) (Supported) (Other)}

2018-05-08 15:29:53,422 | ERROR | ppc-dispatcher-3 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Don't know how to execute transaction ID 1

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

        at Proxycfa15bb4_f80e_4ec0_a4a5_05840b27df19.execute(Unknown Source)

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.SVCLogicServiceExecute(WorkFlowManagerImpl.java:251)[384:appc-workflow-management-core:1.2.0]

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.executeWorkflow(WorkFlowManagerImpl.java:154)[384:appc-workflow-management-core:1.2.0]

        at Proxy811d5c86_04fa_4eb0_bac4_b322573a1a43.executeWorkflow(Unknown Source)

        at Proxy9777da8e_409e_4a97_8a9e_3f9c94b8ff99.executeWorkflow(Unknown Source)

        at org.openecomp.appc.executor.impl.CommandTask.execute(CommandTask.java:79)

        at org.openecomp.appc.executor.impl.LCMCommandTask.run(LCMCommandTask.java:175)

        at org.openecomp.appc.executionqueue.impl.QueueManager.lambda$enqueueTask$0(QueueManager.java:118)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_151]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_151]

        at java.lang.Thread.run(Thread.java:748)[:1.8.0_151]

2018-05-08 15:29:53,428 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (401) not found, keys are { (400) (Other)}

2018-05-08 15:29:53,460 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (success) not found, keys are { (failure)}

2018-05-08 15:29:53,461 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (failure)}

@                                                                                                                                                                                                                                                                                            

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Friday, May 04, 2018 2:21 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>; onap-discuss@...
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

On the same directory in APPC docker. You would see the appc_southbound.properties file instead. The format for ansible server in southbound properties is below:

 

<vnf-type>.ANSIBLE.<action_name>.user

<vnf-type>.ANSIBLE.<action_name>.port

<vnf-type>.ANSIBLE.<action_name>.password

<vnf-type>.ANSIBLE.<action_name>.url

 

<vnf-type> has to be matched with vnf-type in A&AI.

 

For example:

 

vUSP-vCOM.ANSIBLE.HealthCheck.user = XXX

vUSP-vCOM.ANSIBLE.HealthCheck.port = 5000

vUSP-vCOM.ANSIBLE.HealthCheck.password = ABCDEF

vUSP-vCOM.ANSIBLE.HealthCheck.url = https://<url>:5000

 

In Casablanca release, these ansible server configures will be moving to device_authentication table in  maria (now is mysql) db.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Friday, May 04, 2018 1:28 PM
To: CHO, TAKAMUNE <
tc012c@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>; onap-discuss@...
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello APPC team,

 

I am trying to update Ansible Server details in APPC properties file. But, we couldn’t find exact parameter to be updated. Could you please provide sample appc.properties file which has Ansible Server details?

 

ariable Name

Description

Type

Comments

User

Username to logon to Ansible Server

Mandatory

Should be provided by APPC.

Password

Password to logon to Ansible Server

Mandatory

Should be provided by APPC.

AgentUrl

The complete URL of the Ansible Server to post the request for execution and retrieve results (if in synchronous mode)

 

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Wednesday, April 04, 2018 3:56 PM
To: Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <
ramanjaneyul_reddy.akula@...>; onap-discuss@...
Cc: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>
Subject: RE: [onap-discuss] [app-c] appc client library location

 

HI Ramu,

 

Thanks for interested on APPC.

 

It sounds like your local_setting.xml for mvn build has an issue, can you attach your local_setting to me, I can take a look.

 

Thanks

 

Taka

 

From: onap-discuss-bounces@... [mailto:onap-discuss-bounces@...] On Behalf Of Akula, Ramanjaneyul Reddy (Nokia - US/Irving)
Sent: Wednesday, April 04, 2018 3:27 PM
To:
onap-discuss@...
Cc: ANUMANENI, VENKATA RAMANA <
venkataramana.a@...>
Subject: [onap-discuss] [app-c] appc client library location

 

Hi APPC Team,

We are planning to do some VNF configuration using APP-C. For the same, learned that we can use the APP-C client libraries (org.onap.appc.client:client-kit, org.onap.appc.client:client-lib) to send the LCM request to DMaaP topic (http://onap.readthedocs.io/en/latest/submodules/appc.git/docs/APPC%20Client%20Library%20Guide/APPC%20Client%20Library%20Guide.html#appc-client-library

 

However, we failed to located the needed jars.

Then tried to compile the code using the instructions @ “https://wiki.onap.org/display/DW/Building+Entire+ONAP

 

While comping the APP-C code, getting below error:

 

[FATAL] Non-resolvable parent POM for org.onap.appc:appc:1.3.0-SNAPSHOT: Failure to find org.onap.ccsdk.parent:odlparent-carbon-sr1:pom:0.1.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 25, column 13

@

 

Can someone help me on how to get around this problem.

 

 

Thanks & best regards,

Ramu

 

 

 

 


Taka Cho
 

Hi Venkata,

 

Your steps sounds ok.  I think you are using the password: “changeit” not “change it” for the all steps below.

 

One more thing you could try is verifying the https connectivity with your jks and your ansible server without APPC. I found one link it may help you: https://confluence.atlassian.com/kb/unable-to-connect-to-ssl-services-due-to-pkix-path-building-failed-779355358.html

 

Is your ansible server using your own RESTful script or using the scripts in ONAP repo: https://gerrit.onap.org/r/gitweb?p=appc.git;a=tree;f=appc-adapters/appc-ansible-adapter/appc-ansible-example-server;h=90fa259c3905d1c5f25b9668a6e537a7c1f1a8e4;hb=refs/heads/master?  

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, June 06, 2018 2:45 PM
To: CHO, TAKAMUNE <tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

I have received certificate from Ansible server team in PEM file. I have used below command to create Java truststore from PEM file.

 

oot@nokonap-appc:/home/ubuntu# keytool -import -file taco_cert.pem -alias tacoCA -keystore mykeystore.js

Enter keystore password: <I have entered changeit here>

Re-enter new password: <I have entered changeit here>

Owner: CN=phonehome, EMAILADDRESS=dane.dwyer@..., OU=SI, O=Nokia, L=Murray Hill, ST=New Jersey, C=US

Issuer: CN=phonehome, EMAILADDRESS=dane.dwyer@..., OU=SI, O=Nokia, L=Murray Hill, ST=New Jersey, C=US

Serial number: 9fdeec1c775fa125

Valid from: Thu Mar 15 17:50:20 UTC 2018 until: Sun Mar 12 17:50:20 UTC 2028

Certificate fingerprints:

         MD5:  F0:99:DA:DA:5E:5D:84:C5:16:3E:80:6F:C4:F2:15:xx

         SHA1: 98:A6:BB:67:C9:4B:58:33:9A:DB:FB:CC:01:60:43:A4:D7:53:E5:xx

         SHA256: AF:2C:26:98:53:E5:82:A6:7B:2C:D7:3F:F8:3D:xx:A7:1E:39:C0:B7:C6:8C:93:B7:4F:F1:27:34:F6:83:11:xx

         Signature algorithm name: SHA256withRSA

         Version: 3

 

Extensions:

 

#1: ObjectId: 2.5.29.17 Criticality=false

SubjectAlternativeName [

  DNSName: 135.104.207.168

]

 

Trust this certificate? [no]:  yes

Certificate was added to keystore

root@nokonap-appc:/home/ubuntu# keytool -list -keystore mykeystore.js

Enter keystore password: < I have entered change it here>

 

Keystore type: JKS

Keystore provider: SUN

 

Your keystore contains 1 entry

 

tacoca, Jun 6, 2018, trustedCertEntry,

Certificate fingerprint (SHA1): 98:A6:BB:67:C9:4B:58:33:9A:DB:FB:CC:01:60:43:A4:D7:53:E5:xx

root@nokonap-appc:/home/ubuntu#

 

copy this file to opendaylight directory.

 

root@nokonap-appc:/home/ubuntu# cp /home/ubuntu/mykeystore.js /var/lib/docker/aufs/mnt/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/opendaylight/tls-client/

root@nokonap-appc:/home/ubuntu# ls -lrt /var/lib/docker/aufs/mnt/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/opendaylight/tls-client/

total 4

-rw-rw-r-- 1 root root 1538 Jun  6 18:42 mykeystore.js

root@nokonap-appc:/home/ubuntu#

 

Username is cman and password is “password”.

 

I have restarted all containers and tested it.

 

Please let me know if this helps to find root cause.

 

Regards

Venkat

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Wednesday, June 06, 2018 8:22 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Venkata,

 

Please provide the details step by step of how you generate the keystore file and password for https connection  between APPC and Ansible server and the console log that you did. Without that, I am not able to tell what went wrong in your setting.

 

Thanks

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Tuesday, June 05, 2018 1:33 PM
To: CHO, TAKAMUNE <tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

I have tried with below changes.

 

data/log# locate mykeystore.js

/home/ubuntu/mykeystore.js

/var/lib/docker/aufs/diff/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/opendaylight/tls-client/mykeystore.js

/var/lib/docker/aufs/mnt/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/opendaylight/tls-client/mykeystore.js

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Tuesday, June 05, 2018 11:04 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Venkata,

 

The default.properties is built on /opt/opendaylight/current/system/org/onap/appc/appc-ansible-adapter-bundle/1.3.0-SNAPSHOT/appc-ansible-adapter-bundle-1.3.0-SNAPSHOT.jar.

 

remove those values in appc.properties.

 

use and regenerate the truststore file with the default values of the default.properties in Repo below:

 

  org.onap.appc.adapter.ansible.trustStore=/opt/opendaylight/tls-client/mykeystore.js

  org.onap.appc.adapter.ansible.trustStore.trustPasswd=changeit

org.onap.appc.adapter.ansible.clientType=DEFAULT

 

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Monday, June 04, 2018 5:22 PM
To: CHO, TAKAMUNE <tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

We don’t have this file on APP-C.

 

root@nokonap-appc:~# locate default.properties

root@nokonap-appc:~#

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Monday, June 04, 2018 3:54 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkata,

 

As I stated before. You need to put those properties in

 

/appc-ansible-adapter-bundle/src/main/resources/org/onap/appc/default.properties.

 

Not in appc.properties.

 

Please try that. And let me know the result.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Monday, June 04, 2018 3:12 PM
To: CHO, TAKAMUNE <tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

I am still facing same issue even after doing lot of configuration changes. Below are the issues.

 

APPC Ansible Adapter is not taking configuration parameter from appc.properties file.

 

My appc.properties contains below parameters. I have restarted APPC with TRUST_all parameters also.

 

org.onap.appc.adapter.ansible.clientType=TRUST_CERT

org.onap.appc.adapter.ansible.trustStore=/opt/openecomp/appc/data/stores/truststore.openecomp.taco.jks

org.onap.appc.adapter.ansible.trustStore.trustPasswd=adminadmin

 

2018-06-04 18:53:21,305 | INFO  | Event Dispatcher | AnsibleAdapterImpl               | 402 - appc-ansible-adapter - 1.2.0 | Creating http client with default behaviour

 

I have followed steps mentioned at below link to create trust store.

 

https://docs.oracle.com/cd/E19509-01/820-3503/6nf1il6er/index.html

 

I am still facing same issue when I send request.

 

2018-06-04 18:08:34,091 | ERROR | ppc-dispatcher-1 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Ansible Adapter Error = Error posting request. Reason = sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

        at org.openecomp.appc.adapter.ansible.impl.AnsibleAdapterImpl.doFailure(AnsibleAdapterImpl.java:207)

        at org.openecomp.appc.adapter.ansible.impl.AnsibleAdapterImpl.reqExec(AnsibleAdapterImpl.java:325)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.CallNodeExecutor.execute(CallNodeExecutor.java:127)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.CallNodeExecutor.execute(CallNodeExecutor.java:127)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

 

If I use http it works but APPC doesn’t send authentication parameters in request whereas Ansible Server expects authentication parameters.

 

Please help me to solve this issue.

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 31, 2018 3:06 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkat,

 

TRUST_ALL value should be fine.

 

From the error you got (I excerpted)

 

Error posting request. Reason = sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

 

It sounds like your trusted keysore js file is not correct when you generated. Did you try to verify your js file from other CLI tools like open_ssl etc?

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, May 30, 2018 6:09 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

Thanks. I have actually added below parameter in appc.properties file to trust all Ansible Servers. But, It still expects certificate to be available in store.

 

root@nokonap-appc:~# grep org.onap.appc.adapter.ansible.clientType /opt/appc/installation/src/main/properties/appc.propertiesorg.onap.appc.adapter.ansible.clientType=TRUST_ALL

 

 

Regards

Venkat

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Wednesday, May 30, 2018 3:36 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

HI Venkata.

 

The path for the keystore key is defined on /appc-ansible-adapter-bundle/src/main/resources/org/onap/appc/default.properties

Which is https://gerrit.onap.org/r/gitweb?p=appc.git;a=blob;f=appc-adapters/appc-ansible-adapter/appc-ansible-adapter-bundle/src/main/resources/org/onap/appc/default.properties;h=d49c0396c5984fb8d46b2b3cf1f572223c8d5c6c;hb=refs/heads/master

 

I assume you know how to generate the trusted keystore file.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, May 30, 2018 3:12 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

We could pass “Unable decrypt the password”  error. Now, we are facing an issue with SSL certification.

Could you please help us to find the path to store certificates and other settings to solve this error?

 

2018-05-29 18:50:05,809 | ERROR | ppc-dispatcher-6 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Error posting request. Reason = sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

        at Proxye981c0ea_91ea_409d_8ef6_23c4fb2c32b1.execute(Unknown Source)

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.SVCLogicServiceExecute(WorkFlowManagerImpl.java:251)[384:appc-workflow-management-core:1.2.0]

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.executeWorkflow(WorkFlowManagerImpl.java:154)[384:appc-workflow-management-core:1.2.0]

        at Proxy405593b3_30f4_4ec4_83f6_6bbd2a7cb808.executeWorkflow(Unknown Source)

        at Proxy03b18168_8c75_4e04_8865_048a156628fb.executeWorkflow(Unknown Source)

        at org.openecomp.appc.executor.impl.CommandTask.execute(CommandTask.java:79)

        at org.openecomp.appc.executor.impl.LCMCommandTask.run(LCMCommandTask.java:175)

        at org.openecomp.appc.executionqueue.impl.QueueManager.lambda$enqueueTask$0(QueueManager.java:118)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_151]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_151]

        at java.lang.Thread.run(Thread.java:748)[:1.8.0_151]

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Friday, May 18, 2018 1:44 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkat,

 

I think there is something wrong when you are doing encrypt password.

 

There is the java code here: https://gerrit.onap.org/r/gitweb?p=appc.git;a=blob;f=appc-config/appc-encryption-tool/provider/src/main/java/org/onap/appc/encryptiontool/wrapper/WrapperEncryptionTool.java;h=6091e4cf275eb217f5fe2f230a425c95e2159904;hb=refs/heads/master

 

That can help you generate encrypted password for appc_southbound properties.

 

There is a wrapper script for this WrapperEncryptionTool.class in the attachment. You may need to change some lines for your env. I will add this script in APPC Repo for R3 later…

 

Hope that would help

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Friday, May 18, 2018 9:52 AM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

I have tried without username and password and facing same issue.

 

Below is the appc_southbound.properties file.

 

Also, Attached is the log file.

 

root@nokonap-appc:/# more ./var/lib/docker/aufs/mnt/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/app/bvc/properties/appc_southbound.properties

mrf2\/MRF\ 0.ANSIBLE.Configure.user=cman

mrf2\/MRF\ 0.ANSIBLE.Configure.port=8084

mrf2\/MRF\ 0.ANSIBLE.Configure.password=313DECE408AF7759D442D7B06DD9A6AA

mrf2\/MRF\ 0.ANSIBLE.Configure.url=https://10.203.134.105:8084/api/v1/ansibleserver

root@nokonap-appc:/#

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 17, 2018 3:46 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkat,

 

Can you try the payload without user and password?

 

And attach the appc_southbount.properties and full log?

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Thursday, May 17, 2018 3:33 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

Payload didn’t have username and password earlier and I was still facing same issue. So, I thought, I will give try with including password.

 

Also, appc_southbound.properties file has username and password(encrypted).

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 17, 2018 1:06 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

HI Venkat,

 

The log  says “error-message -- Unable to decrypt the password”. The user name and password should not be in the payload.

Those are supposed to update it in properties file which is appc southbound properties I mentioned before . Code will not read user id and password from payload.

 

From their payload

   "appc-provider-lcm:payload": "{\"Id\": \"$requestID\",\"PlaybookName\": \"vmmsc@playbook_linux@...\",\"NodeList\": [\"CMAN-TACO-MMSC1\" ],\"password\": \"313DECE408AF7759D442D7B06DD9A6AA\", \"Timeout\": 600, \"EnvParameters\": { \"working_dir\": \"/var/log\",\"command\": \"ls\", \"user_name\": \"root\",\"host_name\": \"mmsc\" }}"

 

From log

NodeList[0] -- CMAN-TACO-MMSC1

2018-05-16 20:13:18,925 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  template-name --

2018-05-16 20:13:18,925 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-message -- Unable to decrypt the password.

2018-05-16 20:13:18,925 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  input.common-header.sub-request-id -- 1-1

2018-05-16 20:13:18,925 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  SvcLogic.status -- failure

2018-05-16 20:13:18,926 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  input.common-header.request-id -- 10

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, May 16, 2018 4:31 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

Attached is log. Below is the request sent to configure. Please let me know if I am missing any thing.

 

{

"appc-provider-lcm:input": {

"appc-provider-lcm:action":"Configure",   

 "appc-provider-lcm:action-identifiers": {

"appc-provider-lcm:vnf-id": "d9d69025-0852-49a9-8982-d71553a557e4"

},

"appc-provider-lcm:common-header": {

      "appc-provider-lcm:request-id": "9",

      "appc-provider-lcm:originator-id": "venkat",

      "appc-provider-lcm:api-ver": "2.43",

      "appc-provider-lcm:timestamp": "2018-05-16T20:11:55.55Z",

      "appc-provider-lcm:sub-request-id": "1-1",

      "appc-provider-lcm:flags": {

        "appc-provider-lcm:ttl": "0",

        "appc-provider-lcm:force": "TRUE",

        "appc-provider-lcm:mode": "NORMAL"

}

},

   "appc-provider-lcm:payload": "{\"Id\": \"$requestID\",\"PlaybookName\": \"vmmsc@playbook_linux@...\",\"NodeList\": [\"CMAN-TACO-MMSC1\" ],\"password\": \"313DECE408AF7759D442D7B06DD9A6AA\", \"Timeout\": 600, \"EnvParameters\": { \"working_dir\": \"/var/log\",\"command\": \"ls\", \"user_name\": \"root\",\"host_name\": \"mmsc\" }}"

}

}

 

Regards

Venkat

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Monday, May 14, 2018 1:04 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkat,

 

Yes. User would provide their own credentials for Ansible Server RESTful API.

 

Maybe you missed my previous email, I assume you followed this : https://gerrit.onap.org/r/gitweb?p=appc.git;a=tree;f=appc-adapters/appc-ansible-adapter/appc-ansible-example-server;h=90fa259c3905d1c5f25b9668a6e537a7c1f1a8e4;hb=refs/heads/master for setting up RESTful API in Ansible server.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Monday, May 14, 2018 11:05 AM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

Sorry I missed your email.

 

My question, Do we need provider credentials as Ansible Server REST API shouldn’t be configured with credentials as per ONAP documentation.

 

mrf2\/MRF\ 0.ANSIBLE.Configure.user=<username>

mrf2\/MRF\ 0.ANSIBLE.Configure.port=8084

mrf2\/MRF\ 0.ANSIBLE.Configure.password=<encrypted password>

mrf2\/MRF\ 0.ANSIBLE.Configure.url=https://<IP>:8084/ui

                                  

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Monday, May 14, 2018 9:25 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hi Venkat,

 

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-code -- 401

 

So you got 401 error back. Did you try to use other cli tools like openssl or curl command to test the connection with the password that you used?

 

Also Can you attach the appc_southbound.properties file?

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Friday, May 11, 2018 5:33 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

Below is the latest status.

 

It was looking for “appc_southbound.properties” file at /opt/app/bvc/properties/. I have created this file.

 

2018-05-11 20:08:30,490 | ERROR | ppc-dispatcher-5 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Cannot locate configuration source /opt/app/bvc/properties/appc_southbound.properties

 

After this, It says that It is “Unable to decrypt the password”. I tried to encrypt the password using “so” VM but it still fails at the same place.

 

Any help to fix this issue would be appreciated.

 

2018-05-11 21:24:52,271 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  password -- password

2018-05-11 21:24:52,271 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  request-action -- Configure

2018-05-11 21:24:52,271 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  configurationblock --

2018-05-11 21:24:52,271 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  EnvParameters --

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  EnvParameters.host_name -- mmsc

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  VNFCNAME0 --

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  api-ver --

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  EnvParameters.working_dir -- /var/log

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-code -- 401

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  vnfc-type --

2018-05-11 21:24:52,273 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  EnvParameters.user_name -- root

2018-05-11 21:24:52,273 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  vf-module-id --

2018-05-11 21:24:52,273 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  tmp.vnfInfo.vm-count -- 0

2018-05-11 21:24:52,273 | INFO  | ppc-dispatcher-1 | FlowControlNode                  | 360 - appc-common - 1.2.0 | Handling Response for transaction Id 1

2018-05-11 21:24:52,274 | INFO  | ppc-dispatcher-1 | DefaultResponseHandler           | 360 - appc-common - 1.2.0 | Transaction Input params Transaction [transactionId=1, action=Configure, actionLevel=vnf, actionIdentifier=null, parameters=null, executionType=graph, uId=null, statusCode=401, pswd=null, executionEndPoint=null, executionModule=APPC, executionRPC=Generic_AnsibleDG, state=null, precheck=null, payload={"Id": "$requestID","PlaybookName": "vmmsc@playbook_linux@...","NodeList": ["CMAN-TACO-MMSC1" ],"Timeout": 600, "EnvParameters": { "working_dir": "/var/log","command": "ls", "user_name": "root","host_name": "mmsc" }}, responses=[Response [responseCode=null, responseMessage=null, responseAction=ResponseAction [wait=null, retry=null, jump=null, ignore=false, stop=true, intermediateMessage=false], responseActionHanlder=null]], status=failure]

2018-05-11 21:24:52,274 | INFO  | ppc-dispatcher-1 | FlowControlNode                  | 360 - appc-common - 1.2.0 | Executed all the transacstion successfully

2018-05-11 21:24:52,275 | ERROR | ppc-dispatcher-1 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Unable to decrypt the password.

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

 

Regards

Venkat

 

 

From: Anumaneni, Venkataramana (Nokia - US/Irving)
Sent: Friday, May 11, 2018 3:11 PM
To: 'CHO, TAKAMUNE' <
tc012c@...>; 'onap-discuss@...' <onap-discuss@...>
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

I have found this issue. I think, EXECUTION_RPC should be “Generic_AnsibleDG” when PROTOCOL is “Ansible”.

Please correct me if I am wrong.

 

 

mysql> select * from PROCESS_FLOW_REFERENCE where ACTION="Configure" and ACTION_LEVEL="vnf" and PROTOCOL="Ansible";

+---------------------------+-----------+--------------+----------+----------------+------------------+-------------------+---------------------+--------------------+

| PROCESS_FLOW_REFERENCE_ID | ACTION    | ACTION_LEVEL | PROTOCOL | EXECUTION_TYPE | EXECUTION_MODULE | EXECUTION_RPC     | UPDATED_DATE        | GET_RUNNING_CONFIG |

+---------------------------+-----------+--------------+----------+----------------+------------------+-------------------+---------------------+--------------------+

|                        24 | Configure | vnf          | Ansible  | graph          | APPC             | Generic_Configure | 2017-08-25 19:40:05 | NULL               |

|                        52 | Configure | vnf          | Ansible  | graph          | APPC             | Generic_Configure | 2017-09-12 16:49:54 | NULL               |

+---------------------------+-----------+--------------+----------+----------------+------------------+-------------------+---------------------+--------------------+

2 rows in set (0.00 sec)

 

 

Regards

Venkat

 

 

From: Anumaneni, Venkataramana (Nokia - US/Irving)
Sent: Friday, May 11, 2018 2:27 PM
To: 'CHO, TAKAMUNE' <
tc012c@...>; 'onap-discuss@...' <onap-discuss@...>
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

After further analysis, APPC should search with “APPC,ansible-adapter-1.0,2.0.1,sync “ instead of “APPC,Generic_Configure,null,sync”.

 

How does APPC gets these parmeters?

 

Regards

Venkat

 

 

From: Anumaneni, Venkataramana (Nokia - US/Irving)
Sent: Friday, May 11, 2018 2:12 PM
To: 'CHO, TAKAMUNE' <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

I have found the root cause of the below error. There were no entries in PROTOCOL_REFERENCE table for this vnf type. After adding entry and make it Ansible, it went further and now it failed while fetching sevice logic.

 

Do I have to add any entry in Service logic table manually?

 

2018-05-11 18:53:54,950 | INFO  | ppc-dispatcher-3 | SvcLogicServiceImpl              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Fetching service logic from data store

2018-05-11 18:53:54,952 | INFO  | ppc-dispatcher-3 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-message -- No service logic found for [APPC,Generic_Configure,null,sync]

2018-05-11 18:53:54,955 | INFO  | ppc-dispatcher-3 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-code -- 401

2018-05-11 18:53:54,955 | INFO  | ppc-dispatcher-3 | FlowControlNode                  | 360 - appc-common - 1.2.0 | Handling Response for transaction Id 1

2018-05-11 18:53:54,956 | INFO  | ppc-dispatcher-3 | DefaultResponseHandler           | 360 - appc-common - 1.2.0 | Transaction Input params Transaction [transactionId=1, action=Configure, actionLevel=vnf, actionIdentifier=null, parameters=null, executionType=graph, uId=null, statusCode=401, pswd=null, executionEndPoint=null, executionModule=APPC, executionRPC=Generic_Configure, state=null, precheck=null, payload={"Id": "$requestID","PlaybookName": "vmmsc@playbook_linux@...","NodeList": ["CMAN-TACO-MMSC1" ],"Timeout": 600, "EnvParameters": { "working_dir": "/var/log","command": "ls", "user_name": "root","host_name": "mmsc" }}, responses=[Response [responseCode=null, responseMessage=null, responseAction=ResponseAction [wait=null, retry=null, jump=null, ignore=false, stop=true, intermediateMessage=false], responseActionHanlder=null]], status=Others]

2018-05-11 18:53:54,956 | INFO  | ppc-dispatcher-3 | FlowControlNode                  | 360 - appc-common - 1.2.0 | Executed all the transacstion successfully

2018-05-11 18:53:54,957 | ERROR | ppc-dispatcher-3 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: No service logic found for [APPC,Generic_Configure,null,sync]

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

        at Proxy3dac49de_249e_44ea_9178_3251aea35ebb.execute(Unknown Source)

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.SVCLogicServiceExecute(WorkFlowManagerImpl.java:251)[384:appc-workflow-management-core:1.2.0]

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.executeWorkflow(WorkFlowManagerImpl.java:154)[384:appc-workflow-management-core:1.2.0]

        at Proxy01e5329d_f310_47f5_a8dc_16266785b6dd.executeWorkflow(Unknown Source)

        at Proxy6b0c2d51_9818_434e_8f3f_6d2dfbedb96b.executeWorkflow(Unknown Source)

        at org.openecomp.appc.executor.impl.CommandTask.execute(CommandTask.java:79)

        at org.openecomp.appc.executor.impl.LCMCommandTask.run(LCMCommandTask.java:175)

        at org.openecomp.appc.executionqueue.impl.QueueManager.lambda$enqueueTask$0(QueueManager.java:118)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_151]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_151]

        at java.lang.Thread.run(Thread.java:748)[:1.8.0_151]

2018-05-11 18:53:54,966 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (401) not found, keys are { (400) (Other)}

2018-05-11 18:53:54,997 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (success) not found, keys are { (failure)}

2018-05-11 18:53:54,997 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (failure)}

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Friday, May 11, 2018 1:28 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hi Vankat,

 

Can you attach your full log? The part of the log below does not help not much to check further.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Friday, May 11, 2018 12:02 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

I am able to add those entries. It is able to get capabilities. However, I am facing below error now.

 

2018-05-11 15:21:22,698 | INFO  | ppc-dispatcher-1 | ConfigResourceNode               | 360 - appc-common - 1.2.0 | getCapability Successful

2018-05-11 15:21:22,699 | INFO  | ppc-dispatcher-1 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome ("") not found, keys are { (Not-Supported) (Supported) (Other)}

2018-05-11 15:21:22,815 | ERROR | ppc-dispatcher-1 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Don't know how to execute transaction ID 1

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

        at Proxy3dac49de_249e_44ea_9178_3251aea35ebb.execute(Unknown Source)

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.SVCLogicServiceExecute(WorkFlowManagerImpl.java:251)[384:appc-workflow-management-core:1.2.0]

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.executeWorkflow(WorkFlowManagerImpl.java:154)[384:appc-workflow-management-core:1.2.0]

        at Proxy01e5329d_f310_47f5_a8dc_16266785b6dd.executeWorkflow(Unknown Source)

        at Proxy6b0c2d51_9818_434e_8f3f_6d2dfbedb96b.executeWorkflow(Unknown Source)

        at org.openecomp.appc.executor.impl.CommandTask.execute(CommandTask.java:79)

        at org.openecomp.appc.executor.impl.LCMCommandTask.run(LCMCommandTask.java:175)

        at org.openecomp.appc.executionqueue.impl.QueueManager.lambda$enqueueTask$0(QueueManager.java:118)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_151]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_151]

        at java.lang.Thread.run(Thread.java:748)[:1.8.0_151]

 

My entries are below;

 

mysql> SELECT * FROM ASDC_REFERENCE;

+-------------------+------------+-----------+---------------+--------+---------------+--------------------------------------+

| ASDC_REFERENCE_ID | VNF_TYPE   | VNFC_TYPE | FILE_CATEGORY | ACTION | ARTIFACT_TYPE | ARTIFACT_NAME                        |

+-------------------+------------+-----------+---------------+--------+---------------+--------------------------------------+

|                 1 | mrf2/MRF 0 | NULL      | capability    | NULL   | NULL          | capability_AllAction_vMRF_0.01v.json |

+-------------------+------------+-----------+---------------+--------+---------------+--------------------------------------+

1 row in set (0.00 sec)

 

mysql> SELECT * FROM ASDC_ARTIFACTS;

+-------------------+--------------------------------------+-----------------+--------------+---------------------+-------------------------------------+------------------------+---------------+------------------+---------------+---------------+---------------+------------------+----------------------+------------------+---------------------+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

| ASDC_ARTIFACTS_ID | SERVICE_UUID                         | DISTRIBUTION_ID | SERVICE_NAME | SERVICE_DESCRIPTION | RESOURCE_UUID                       | RESOURCE_INSTANCE_NAME | RESOURCE_NAME | RESOURCE_VERSION | RESOURCE_TYPE | ARTIFACT_UUID | ARTIFACT_TYPE | ARTIFACT_VERSION | ARTIFACT_DESCRIPTION | INTERNAL_VERSION | CREATION_DATE       | ARTIFACT_NAME                        | ARTIFACT_CONTENT                                                                                                                                                                                                                                                                                                                                                          |

+-------------------+--------------------------------------+-----------------+--------------+---------------------+-------------------------------------+------------------------+---------------+------------------+---------------+---------------+---------------+------------------+----------------------+------------------+---------------------+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

|                 1 | 6a000b37-1b4d-4ceb-b5d1-14722f2484f3 | 1               | mrf          | mrfconfigure        | d9d69025-0852-49a9-8982-d71553a557e | mrf                    | m2            | 1525955128862    | mrf2/MRF 0    | 1             | NULL          | NULL             | configure            |                1 | 2018-05-11 14:44:31 | capability_AllAction_vMRF_0.01v.json | {"capabilities":{"vnfc":[],"vm":[{"AttachVolume":[]},{"DetachVolume":[]},{"Evacuate":["pld","ssc"]},{"Migrate":["pld","ssc"]},{"Reboot":["pld","ssc"]},{"Rebuild":["pld","ssc"]},{"Restart":["pld","ssc"]},{"Snapshot":["pld","ssc"]},{"Start":["pld","ssc"]},{"Stop":["pld","ssc"]}],"vf-module":[],"vnf":["Configure","ConfigModify","OpenStack Actions","AllAction"]}} |

+-------------------+--------------------------------------+-----------------+--------------+---------------------+-------------------------------------+------------------------+---------------+------------------+---------------+---------------+---------------+------------------+----------------------+------------------+---------------------+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

1 row in set (0.00 sec)

 

 

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 10, 2018 10:36 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

HI Venkat,

 

I assume you followed the instruction to have APPC in your local env: https://wiki.onap.org/display/DW/Building+and+Running+APPC+Docker+Images.

 

Then you should have mysql container running in your local. The how-to login to mysql container is on the wiki page. And the source script for  creating tables for mysql is at: https://gerrit.onap.org/r/gitweb?p=appc/deployment.git;a=blob;f=installation/appc/src/main/scripts/installAppcDb.sh;h=fc5ae53caafec9a95a5c63e3061510de59a14c60;hb=refs/heads/master

 

Which is triggered from startODL.sh https://gerrit.onap.org/r/gitweb?p=appc/deployment.git;a=blob;f=installation/appc/src/main/scripts/startODL.sh;h=f58db40df0f031ee40d8df3b1c6019c1e5e817fe;hb=refs/heads/master

 

Taka

 

 

 

From: ANUMANENI, VENKATA RAMANA
Sent: Thursday, May 10, 2018 9:59 AM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

I am looking for mysql credentials to add these entries in those tables.

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 10, 2018 8:22 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

HI Venkat,

 

From error in your log, yes. This has to be done.

 

Sorry, What do you mean by “default credentials”?

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, May 09, 2018 6:11 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

Thank you for this. Is this has to be done on APPC?

 

What are the default credentials?

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Wednesday, May 09, 2018 1:55 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hi Venkat,

 

The Configure action is not in the reference file.

 

You would need to insert the capacity plan which has Configure action in two tables in mysql DB:

 

Here is the one sample:

 

On ASDC_ARTIFACTS table:

 

TLSUUID836241290926

TLDID95681

TLServiceName

Template Loader Test

TLRUID95681

TLRIName

null

TLResourceVersion

TLResourceType

TLAUUID95681

null

0.1

SdcTestDescription

41

2018-05-09 11:41:31

capability_AllAction_vUSP-MetaswitchvSBC_0.0.1V.json

{"capabilities":{"vnfc":[],"vm":[{"AttachVolume":[]},{"DetachVolume":[]},{"Evacuate":["pld","ssc"]},{"Migrate":["pld","ssc"]},{"Reboot":["pld","ssc"]},{"Rebuild":["pld","ssc"]},{"Restart":["pld","ssc"]},{"Snapshot":["pld","ssc"]},{"Start":["pld","ssc"]},{"Stop":["pld","ssc"]}],"vf-module":[],"vnf":["Configure","ConfigModify","OpenStack Actions","AllAction"]}}

 

On ASDC_REFERENCE table:

 

1899

vUSP-Metaswitch vSBC

null

capability

null

null

capability_AllAction_vUSP-MetaswitchvSBC_0.0.1V.json

 

Taka

 

 

From: ANUMANENI, VENKATA RAMANA
Sent: Tuesday, May 08, 2018 5:39 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Takamune,

 

Thanks for your support.

 

We have tried changes suggested by you. I sent LCM action configure command through APPC LCM API. Action was accepted but it has failed in service logic at below step.

 

At this moment, LCM API to sent Service Logic and it has queried A&AI successfully. But, Service Logic is not able find any further step.

 

Is there anything I am mssing?

 

 

2018-05-08 15:29:53,286 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (not-found) (failure)}

2018-05-08 15:29:53,289 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (not-found) not found, keys are { (failure)}

2018-05-08 15:29:53,289 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (failure)}

2018-05-08 15:29:53,290 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome ("") not found, keys are { (YES) (Other)}

2018-05-08 15:29:53,343 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (success) not found, keys are { (failure)}

2018-05-08 15:29:53,344 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (failure)}

2018-05-08 15:29:53,344 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (vnf) not found, keys are { (vm) (Other)}

2018-05-08 15:29:53,345 | INFO  | ppc-dispatcher-3 | ConfigResourceNode               | 360 - appc-common - 1.2.0 | Received getCapability call with params : {caplevel=vnf, checkCapability=Configure, vnf-type=MRF/MRF 0}

2018-05-08 15:29:53,346 | INFO  | ppc-dispatcher-3 | DGGeneralDBService               | 360 - appc-common - 1.2.0 | getCapability Query String : select max(internal_version) as maxInternalVersion, artifact_name as artifactName from ASDC_ARTIFACTS  where artifact_name in (select artifact_name from ASDC_REFERENCE  where vnf_type= $vnf-type  and file_category = 'capability' )

2018-05-08 15:29:53,352 | INFO  | ppc-dispatcher-3 | ConfigResourceNode               | 360 - appc-common - 1.2.0 | getCapability::returned from DB::+cap

2018-05-08 15:29:53,353 | INFO  | ppc-dispatcher-3 | ConfigResourceNode               | 360 - appc-common - 1.2.0 | getCapability Successful - No capability blocks found

2018-05-08 15:29:53,353 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome ("") not found, keys are { (Not-Supported) (Supported) (Other)}

2018-05-08 15:29:53,422 | ERROR | ppc-dispatcher-3 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Don't know how to execute transaction ID 1

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

        at Proxycfa15bb4_f80e_4ec0_a4a5_05840b27df19.execute(Unknown Source)

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.SVCLogicServiceExecute(WorkFlowManagerImpl.java:251)[384:appc-workflow-management-core:1.2.0]

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.executeWorkflow(WorkFlowManagerImpl.java:154)[384:appc-workflow-management-core:1.2.0]

        at Proxy811d5c86_04fa_4eb0_bac4_b322573a1a43.executeWorkflow(Unknown Source)

        at Proxy9777da8e_409e_4a97_8a9e_3f9c94b8ff99.executeWorkflow(Unknown Source)

        at org.openecomp.appc.executor.impl.CommandTask.execute(CommandTask.java:79)

        at org.openecomp.appc.executor.impl.LCMCommandTask.run(LCMCommandTask.java:175)

        at org.openecomp.appc.executionqueue.impl.QueueManager.lambda$enqueueTask$0(QueueManager.java:118)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_151]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_151]

        at java.lang.Thread.run(Thread.java:748)[:1.8.0_151]

2018-05-08 15:29:53,428 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (401) not found, keys are { (400) (Other)}

2018-05-08 15:29:53,460 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (success) not found, keys are { (failure)}

2018-05-08 15:29:53,461 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (failure)}

@                                                                                                                                                                                                                                                                                            

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Friday, May 04, 2018 2:21 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>; onap-discuss@...
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

On the same directory in APPC docker. You would see the appc_southbound.properties file instead. The format for ansible server in southbound properties is below:

 

<vnf-type>.ANSIBLE.<action_name>.user

<vnf-type>.ANSIBLE.<action_name>.port

<vnf-type>.ANSIBLE.<action_name>.password

<vnf-type>.ANSIBLE.<action_name>.url

 

<vnf-type> has to be matched with vnf-type in A&AI.

 

For example:

 

vUSP-vCOM.ANSIBLE.HealthCheck.user = XXX

vUSP-vCOM.ANSIBLE.HealthCheck.port = 5000

vUSP-vCOM.ANSIBLE.HealthCheck.password = ABCDEF

vUSP-vCOM.ANSIBLE.HealthCheck.url = https://<url>:5000

 

In Casablanca release, these ansible server configures will be moving to device_authentication table in  maria (now is mysql) db.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Friday, May 04, 2018 1:28 PM
To: CHO, TAKAMUNE <
tc012c@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>; onap-discuss@...
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello APPC team,

 

I am trying to update Ansible Server details in APPC properties file. But, we couldn’t find exact parameter to be updated. Could you please provide sample appc.properties file which has Ansible Server details?

 

ariable Name

Description

Type

Comments

User

Username to logon to Ansible Server

Mandatory

Should be provided by APPC.

Password

Password to logon to Ansible Server

Mandatory

Should be provided by APPC.

AgentUrl

The complete URL of the Ansible Server to post the request for execution and retrieve results (if in synchronous mode)

 

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Wednesday, April 04, 2018 3:56 PM
To: Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <
ramanjaneyul_reddy.akula@...>; onap-discuss@...
Cc: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>
Subject: RE: [onap-discuss] [app-c] appc client library location

 

HI Ramu,

 

Thanks for interested on APPC.

 

It sounds like your local_setting.xml for mvn build has an issue, can you attach your local_setting to me, I can take a look.

 

Thanks

 

Taka

 

From: onap-discuss-bounces@... [mailto:onap-discuss-bounces@...] On Behalf Of Akula, Ramanjaneyul Reddy (Nokia - US/Irving)
Sent: Wednesday, April 04, 2018 3:27 PM
To:
onap-discuss@...
Cc: ANUMANENI, VENKATA RAMANA <
venkataramana.a@...>
Subject: [onap-discuss] [app-c] appc client library location

 

Hi APPC Team,

We are planning to do some VNF configuration using APP-C. For the same, learned that we can use the APP-C client libraries (org.onap.appc.client:client-kit, org.onap.appc.client:client-lib) to send the LCM request to DMaaP topic (http://onap.readthedocs.io/en/latest/submodules/appc.git/docs/APPC%20Client%20Library%20Guide/APPC%20Client%20Library%20Guide.html#appc-client-library

 

However, we failed to located the needed jars.

Then tried to compile the code using the instructions @ “https://wiki.onap.org/display/DW/Building+Entire+ONAP

 

While comping the APP-C code, getting below error:

 

[FATAL] Non-resolvable parent POM for org.onap.appc:appc:1.3.0-SNAPSHOT: Failure to find org.onap.ccsdk.parent:odlparent-carbon-sr1:pom:0.1.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 25, column 13

@

 

Can someone help me on how to get around this problem.

 

 

Thanks & best regards,

Ramu

 

 

 

 


Anumaneni, Venkataramana (Nokia - US/Irving)
 

Hello Taka,

 

I have received certificate from Ansible server team in PEM file. I have used below command to create Java truststore from PEM file.

 

oot@nokonap-appc:/home/ubuntu# keytool -import -file taco_cert.pem -alias tacoCA -keystore mykeystore.js

Enter keystore password: <I have entered changeit here>

Re-enter new password: <I have entered changeit here>

Owner: CN=phonehome, EMAILADDRESS=dane.dwyer@..., OU=SI, O=Nokia, L=Murray Hill, ST=New Jersey, C=US

Issuer: CN=phonehome, EMAILADDRESS=dane.dwyer@..., OU=SI, O=Nokia, L=Murray Hill, ST=New Jersey, C=US

Serial number: 9fdeec1c775fa125

Valid from: Thu Mar 15 17:50:20 UTC 2018 until: Sun Mar 12 17:50:20 UTC 2028

Certificate fingerprints:

         MD5:  F0:99:DA:DA:5E:5D:84:C5:16:3E:80:6F:C4:F2:15:xx

         SHA1: 98:A6:BB:67:C9:4B:58:33:9A:DB:FB:CC:01:60:43:A4:D7:53:E5:xx

         SHA256: AF:2C:26:98:53:E5:82:A6:7B:2C:D7:3F:F8:3D:xx:A7:1E:39:C0:B7:C6:8C:93:B7:4F:F1:27:34:F6:83:11:xx

         Signature algorithm name: SHA256withRSA

         Version: 3

 

Extensions:

 

#1: ObjectId: 2.5.29.17 Criticality=false

SubjectAlternativeName [

  DNSName: 135.104.207.168

]

 

Trust this certificate? [no]:  yes

Certificate was added to keystore

root@nokonap-appc:/home/ubuntu# keytool -list -keystore mykeystore.js

Enter keystore password: < I have entered change it here>

 

Keystore type: JKS

Keystore provider: SUN

 

Your keystore contains 1 entry

 

tacoca, Jun 6, 2018, trustedCertEntry,

Certificate fingerprint (SHA1): 98:A6:BB:67:C9:4B:58:33:9A:DB:FB:CC:01:60:43:A4:D7:53:E5:xx

root@nokonap-appc:/home/ubuntu#

 

copy this file to opendaylight directory.

 

root@nokonap-appc:/home/ubuntu# cp /home/ubuntu/mykeystore.js /var/lib/docker/aufs/mnt/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/opendaylight/tls-client/

root@nokonap-appc:/home/ubuntu# ls -lrt /var/lib/docker/aufs/mnt/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/opendaylight/tls-client/

total 4

-rw-rw-r-- 1 root root 1538 Jun  6 18:42 mykeystore.js

root@nokonap-appc:/home/ubuntu#

 

Username is cman and password is “password”.

 

I have restarted all containers and tested it.

 

Please let me know if this helps to find root cause.

 

Regards

Venkat

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Wednesday, June 06, 2018 8:22 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Venkata,

 

Please provide the details step by step of how you generate the keystore file and password for https connection  between APPC and Ansible server and the console log that you did. Without that, I am not able to tell what went wrong in your setting.

 

Thanks

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Tuesday, June 05, 2018 1:33 PM
To: CHO, TAKAMUNE <tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

I have tried with below changes.

 

data/log# locate mykeystore.js

/home/ubuntu/mykeystore.js

/var/lib/docker/aufs/diff/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/opendaylight/tls-client/mykeystore.js

/var/lib/docker/aufs/mnt/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/opendaylight/tls-client/mykeystore.js

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Tuesday, June 05, 2018 11:04 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Venkata,

 

The default.properties is built on /opt/opendaylight/current/system/org/onap/appc/appc-ansible-adapter-bundle/1.3.0-SNAPSHOT/appc-ansible-adapter-bundle-1.3.0-SNAPSHOT.jar.

 

remove those values in appc.properties.

 

use and regenerate the truststore file with the default values of the default.properties in Repo below:

 

  org.onap.appc.adapter.ansible.trustStore=/opt/opendaylight/tls-client/mykeystore.js

  org.onap.appc.adapter.ansible.trustStore.trustPasswd=changeit

org.onap.appc.adapter.ansible.clientType=DEFAULT

 

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Monday, June 04, 2018 5:22 PM
To: CHO, TAKAMUNE <tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

We don’t have this file on APP-C.

 

root@nokonap-appc:~# locate default.properties

root@nokonap-appc:~#

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Monday, June 04, 2018 3:54 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkata,

 

As I stated before. You need to put those properties in

 

/appc-ansible-adapter-bundle/src/main/resources/org/onap/appc/default.properties.

 

Not in appc.properties.

 

Please try that. And let me know the result.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Monday, June 04, 2018 3:12 PM
To: CHO, TAKAMUNE <tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

I am still facing same issue even after doing lot of configuration changes. Below are the issues.

 

APPC Ansible Adapter is not taking configuration parameter from appc.properties file.

 

My appc.properties contains below parameters. I have restarted APPC with TRUST_all parameters also.

 

org.onap.appc.adapter.ansible.clientType=TRUST_CERT

org.onap.appc.adapter.ansible.trustStore=/opt/openecomp/appc/data/stores/truststore.openecomp.taco.jks

org.onap.appc.adapter.ansible.trustStore.trustPasswd=adminadmin

 

2018-06-04 18:53:21,305 | INFO  | Event Dispatcher | AnsibleAdapterImpl               | 402 - appc-ansible-adapter - 1.2.0 | Creating http client with default behaviour

 

I have followed steps mentioned at below link to create trust store.

 

https://docs.oracle.com/cd/E19509-01/820-3503/6nf1il6er/index.html

 

I am still facing same issue when I send request.

 

2018-06-04 18:08:34,091 | ERROR | ppc-dispatcher-1 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Ansible Adapter Error = Error posting request. Reason = sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

        at org.openecomp.appc.adapter.ansible.impl.AnsibleAdapterImpl.doFailure(AnsibleAdapterImpl.java:207)

        at org.openecomp.appc.adapter.ansible.impl.AnsibleAdapterImpl.reqExec(AnsibleAdapterImpl.java:325)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.CallNodeExecutor.execute(CallNodeExecutor.java:127)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.CallNodeExecutor.execute(CallNodeExecutor.java:127)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

 

If I use http it works but APPC doesn’t send authentication parameters in request whereas Ansible Server expects authentication parameters.

 

Please help me to solve this issue.

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 31, 2018 3:06 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkat,

 

TRUST_ALL value should be fine.

 

From the error you got (I excerpted)

 

Error posting request. Reason = sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

 

It sounds like your trusted keysore js file is not correct when you generated. Did you try to verify your js file from other CLI tools like open_ssl etc?

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, May 30, 2018 6:09 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

Thanks. I have actually added below parameter in appc.properties file to trust all Ansible Servers. But, It still expects certificate to be available in store.

 

root@nokonap-appc:~# grep org.onap.appc.adapter.ansible.clientType /opt/appc/installation/src/main/properties/appc.propertiesorg.onap.appc.adapter.ansible.clientType=TRUST_ALL

 

 

Regards

Venkat

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Wednesday, May 30, 2018 3:36 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

HI Venkata.

 

The path for the keystore key is defined on /appc-ansible-adapter-bundle/src/main/resources/org/onap/appc/default.properties

Which is https://gerrit.onap.org/r/gitweb?p=appc.git;a=blob;f=appc-adapters/appc-ansible-adapter/appc-ansible-adapter-bundle/src/main/resources/org/onap/appc/default.properties;h=d49c0396c5984fb8d46b2b3cf1f572223c8d5c6c;hb=refs/heads/master

 

I assume you know how to generate the trusted keystore file.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, May 30, 2018 3:12 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

We could pass “Unable decrypt the password”  error. Now, we are facing an issue with SSL certification.

Could you please help us to find the path to store certificates and other settings to solve this error?

 

2018-05-29 18:50:05,809 | ERROR | ppc-dispatcher-6 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Error posting request. Reason = sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

        at Proxye981c0ea_91ea_409d_8ef6_23c4fb2c32b1.execute(Unknown Source)

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.SVCLogicServiceExecute(WorkFlowManagerImpl.java:251)[384:appc-workflow-management-core:1.2.0]

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.executeWorkflow(WorkFlowManagerImpl.java:154)[384:appc-workflow-management-core:1.2.0]

        at Proxy405593b3_30f4_4ec4_83f6_6bbd2a7cb808.executeWorkflow(Unknown Source)

        at Proxy03b18168_8c75_4e04_8865_048a156628fb.executeWorkflow(Unknown Source)

        at org.openecomp.appc.executor.impl.CommandTask.execute(CommandTask.java:79)

        at org.openecomp.appc.executor.impl.LCMCommandTask.run(LCMCommandTask.java:175)

        at org.openecomp.appc.executionqueue.impl.QueueManager.lambda$enqueueTask$0(QueueManager.java:118)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_151]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_151]

        at java.lang.Thread.run(Thread.java:748)[:1.8.0_151]

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Friday, May 18, 2018 1:44 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkat,

 

I think there is something wrong when you are doing encrypt password.

 

There is the java code here: https://gerrit.onap.org/r/gitweb?p=appc.git;a=blob;f=appc-config/appc-encryption-tool/provider/src/main/java/org/onap/appc/encryptiontool/wrapper/WrapperEncryptionTool.java;h=6091e4cf275eb217f5fe2f230a425c95e2159904;hb=refs/heads/master

 

That can help you generate encrypted password for appc_southbound properties.

 

There is a wrapper script for this WrapperEncryptionTool.class in the attachment. You may need to change some lines for your env. I will add this script in APPC Repo for R3 later…

 

Hope that would help

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Friday, May 18, 2018 9:52 AM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

I have tried without username and password and facing same issue.

 

Below is the appc_southbound.properties file.

 

Also, Attached is the log file.

 

root@nokonap-appc:/# more ./var/lib/docker/aufs/mnt/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/app/bvc/properties/appc_southbound.properties

mrf2\/MRF\ 0.ANSIBLE.Configure.user=cman

mrf2\/MRF\ 0.ANSIBLE.Configure.port=8084

mrf2\/MRF\ 0.ANSIBLE.Configure.password=313DECE408AF7759D442D7B06DD9A6AA

mrf2\/MRF\ 0.ANSIBLE.Configure.url=https://10.203.134.105:8084/api/v1/ansibleserver

root@nokonap-appc:/#

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 17, 2018 3:46 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkat,

 

Can you try the payload without user and password?

 

And attach the appc_southbount.properties and full log?

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Thursday, May 17, 2018 3:33 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

Payload didn’t have username and password earlier and I was still facing same issue. So, I thought, I will give try with including password.

 

Also, appc_southbound.properties file has username and password(encrypted).

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 17, 2018 1:06 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

HI Venkat,

 

The log  says “error-message -- Unable to decrypt the password”. The user name and password should not be in the payload.

Those are supposed to update it in properties file which is appc southbound properties I mentioned before . Code will not read user id and password from payload.

 

From their payload

   "appc-provider-lcm:payload": "{\"Id\": \"$requestID\",\"PlaybookName\": \"vmmsc@playbook_linux@...\",\"NodeList\": [\"CMAN-TACO-MMSC1\" ],\"password\": \"313DECE408AF7759D442D7B06DD9A6AA\", \"Timeout\": 600, \"EnvParameters\": { \"working_dir\": \"/var/log\",\"command\": \"ls\", \"user_name\": \"root\",\"host_name\": \"mmsc\" }}"

 

From log

NodeList[0] -- CMAN-TACO-MMSC1

2018-05-16 20:13:18,925 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  template-name --

2018-05-16 20:13:18,925 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-message -- Unable to decrypt the password.

2018-05-16 20:13:18,925 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  input.common-header.sub-request-id -- 1-1

2018-05-16 20:13:18,925 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  SvcLogic.status -- failure

2018-05-16 20:13:18,926 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  input.common-header.request-id -- 10

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, May 16, 2018 4:31 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

Attached is log. Below is the request sent to configure. Please let me know if I am missing any thing.

 

{

"appc-provider-lcm:input": {

"appc-provider-lcm:action":"Configure",   

 "appc-provider-lcm:action-identifiers": {

"appc-provider-lcm:vnf-id": "d9d69025-0852-49a9-8982-d71553a557e4"

},

"appc-provider-lcm:common-header": {

      "appc-provider-lcm:request-id": "9",

      "appc-provider-lcm:originator-id": "venkat",

      "appc-provider-lcm:api-ver": "2.43",

      "appc-provider-lcm:timestamp": "2018-05-16T20:11:55.55Z",

      "appc-provider-lcm:sub-request-id": "1-1",

      "appc-provider-lcm:flags": {

        "appc-provider-lcm:ttl": "0",

        "appc-provider-lcm:force": "TRUE",

        "appc-provider-lcm:mode": "NORMAL"

}

},

   "appc-provider-lcm:payload": "{\"Id\": \"$requestID\",\"PlaybookName\": \"vmmsc@playbook_linux@...\",\"NodeList\": [\"CMAN-TACO-MMSC1\" ],\"password\": \"313DECE408AF7759D442D7B06DD9A6AA\", \"Timeout\": 600, \"EnvParameters\": { \"working_dir\": \"/var/log\",\"command\": \"ls\", \"user_name\": \"root\",\"host_name\": \"mmsc\" }}"

}

}

 

Regards

Venkat

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Monday, May 14, 2018 1:04 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkat,

 

Yes. User would provide their own credentials for Ansible Server RESTful API.

 

Maybe you missed my previous email, I assume you followed this : https://gerrit.onap.org/r/gitweb?p=appc.git;a=tree;f=appc-adapters/appc-ansible-adapter/appc-ansible-example-server;h=90fa259c3905d1c5f25b9668a6e537a7c1f1a8e4;hb=refs/heads/master for setting up RESTful API in Ansible server.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Monday, May 14, 2018 11:05 AM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

Sorry I missed your email.

 

My question, Do we need provider credentials as Ansible Server REST API shouldn’t be configured with credentials as per ONAP documentation.

 

mrf2\/MRF\ 0.ANSIBLE.Configure.user=<username>

mrf2\/MRF\ 0.ANSIBLE.Configure.port=8084

mrf2\/MRF\ 0.ANSIBLE.Configure.password=<encrypted password>

mrf2\/MRF\ 0.ANSIBLE.Configure.url=https://<IP>:8084/ui

                                  

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Monday, May 14, 2018 9:25 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hi Venkat,

 

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-code -- 401

 

So you got 401 error back. Did you try to use other cli tools like openssl or curl command to test the connection with the password that you used?

 

Also Can you attach the appc_southbound.properties file?

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Friday, May 11, 2018 5:33 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

Below is the latest status.

 

It was looking for “appc_southbound.properties” file at /opt/app/bvc/properties/. I have created this file.

 

2018-05-11 20:08:30,490 | ERROR | ppc-dispatcher-5 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Cannot locate configuration source /opt/app/bvc/properties/appc_southbound.properties

 

After this, It says that It is “Unable to decrypt the password”. I tried to encrypt the password using “so” VM but it still fails at the same place.

 

Any help to fix this issue would be appreciated.

 

2018-05-11 21:24:52,271 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  password -- password

2018-05-11 21:24:52,271 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  request-action -- Configure

2018-05-11 21:24:52,271 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  configurationblock --

2018-05-11 21:24:52,271 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  EnvParameters --

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  EnvParameters.host_name -- mmsc

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  VNFCNAME0 --

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  api-ver --

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  EnvParameters.working_dir -- /var/log

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-code -- 401

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  vnfc-type --

2018-05-11 21:24:52,273 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  EnvParameters.user_name -- root

2018-05-11 21:24:52,273 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  vf-module-id --

2018-05-11 21:24:52,273 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  tmp.vnfInfo.vm-count -- 0

2018-05-11 21:24:52,273 | INFO  | ppc-dispatcher-1 | FlowControlNode                  | 360 - appc-common - 1.2.0 | Handling Response for transaction Id 1

2018-05-11 21:24:52,274 | INFO  | ppc-dispatcher-1 | DefaultResponseHandler           | 360 - appc-common - 1.2.0 | Transaction Input params Transaction [transactionId=1, action=Configure, actionLevel=vnf, actionIdentifier=null, parameters=null, executionType=graph, uId=null, statusCode=401, pswd=null, executionEndPoint=null, executionModule=APPC, executionRPC=Generic_AnsibleDG, state=null, precheck=null, payload={"Id": "$requestID","PlaybookName": "vmmsc@playbook_linux@...","NodeList": ["CMAN-TACO-MMSC1" ],"Timeout": 600, "EnvParameters": { "working_dir": "/var/log","command": "ls", "user_name": "root","host_name": "mmsc" }}, responses=[Response [responseCode=null, responseMessage=null, responseAction=ResponseAction [wait=null, retry=null, jump=null, ignore=false, stop=true, intermediateMessage=false], responseActionHanlder=null]], status=failure]

2018-05-11 21:24:52,274 | INFO  | ppc-dispatcher-1 | FlowControlNode                  | 360 - appc-common - 1.2.0 | Executed all the transacstion successfully

2018-05-11 21:24:52,275 | ERROR | ppc-dispatcher-1 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Unable to decrypt the password.

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

 

Regards

Venkat

 

 

From: Anumaneni, Venkataramana (Nokia - US/Irving)
Sent: Friday, May 11, 2018 3:11 PM
To: 'CHO, TAKAMUNE' <
tc012c@...>; 'onap-discuss@...' <onap-discuss@...>
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

I have found this issue. I think, EXECUTION_RPC should be “Generic_AnsibleDG” when PROTOCOL is “Ansible”.

Please correct me if I am wrong.

 

 

mysql> select * from PROCESS_FLOW_REFERENCE where ACTION="Configure" and ACTION_LEVEL="vnf" and PROTOCOL="Ansible";

+---------------------------+-----------+--------------+----------+----------------+------------------+-------------------+---------------------+--------------------+

| PROCESS_FLOW_REFERENCE_ID | ACTION    | ACTION_LEVEL | PROTOCOL | EXECUTION_TYPE | EXECUTION_MODULE | EXECUTION_RPC     | UPDATED_DATE        | GET_RUNNING_CONFIG |

+---------------------------+-----------+--------------+----------+----------------+------------------+-------------------+---------------------+--------------------+

|                        24 | Configure | vnf          | Ansible  | graph          | APPC             | Generic_Configure | 2017-08-25 19:40:05 | NULL               |

|                        52 | Configure | vnf          | Ansible  | graph          | APPC             | Generic_Configure | 2017-09-12 16:49:54 | NULL               |

+---------------------------+-----------+--------------+----------+----------------+------------------+-------------------+---------------------+--------------------+

2 rows in set (0.00 sec)

 

 

Regards

Venkat

 

 

From: Anumaneni, Venkataramana (Nokia - US/Irving)
Sent: Friday, May 11, 2018 2:27 PM
To: 'CHO, TAKAMUNE' <
tc012c@...>; 'onap-discuss@...' <onap-discuss@...>
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

After further analysis, APPC should search with “APPC,ansible-adapter-1.0,2.0.1,sync “ instead of “APPC,Generic_Configure,null,sync”.

 

How does APPC gets these parmeters?

 

Regards

Venkat

 

 

From: Anumaneni, Venkataramana (Nokia - US/Irving)
Sent: Friday, May 11, 2018 2:12 PM
To: 'CHO, TAKAMUNE' <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

I have found the root cause of the below error. There were no entries in PROTOCOL_REFERENCE table for this vnf type. After adding entry and make it Ansible, it went further and now it failed while fetching sevice logic.

 

Do I have to add any entry in Service logic table manually?

 

2018-05-11 18:53:54,950 | INFO  | ppc-dispatcher-3 | SvcLogicServiceImpl              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Fetching service logic from data store

2018-05-11 18:53:54,952 | INFO  | ppc-dispatcher-3 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-message -- No service logic found for [APPC,Generic_Configure,null,sync]

2018-05-11 18:53:54,955 | INFO  | ppc-dispatcher-3 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-code -- 401

2018-05-11 18:53:54,955 | INFO  | ppc-dispatcher-3 | FlowControlNode                  | 360 - appc-common - 1.2.0 | Handling Response for transaction Id 1

2018-05-11 18:53:54,956 | INFO  | ppc-dispatcher-3 | DefaultResponseHandler           | 360 - appc-common - 1.2.0 | Transaction Input params Transaction [transactionId=1, action=Configure, actionLevel=vnf, actionIdentifier=null, parameters=null, executionType=graph, uId=null, statusCode=401, pswd=null, executionEndPoint=null, executionModule=APPC, executionRPC=Generic_Configure, state=null, precheck=null, payload={"Id": "$requestID","PlaybookName": "vmmsc@playbook_linux@...","NodeList": ["CMAN-TACO-MMSC1" ],"Timeout": 600, "EnvParameters": { "working_dir": "/var/log","command": "ls", "user_name": "root","host_name": "mmsc" }}, responses=[Response [responseCode=null, responseMessage=null, responseAction=ResponseAction [wait=null, retry=null, jump=null, ignore=false, stop=true, intermediateMessage=false], responseActionHanlder=null]], status=Others]

2018-05-11 18:53:54,956 | INFO  | ppc-dispatcher-3 | FlowControlNode                  | 360 - appc-common - 1.2.0 | Executed all the transacstion successfully

2018-05-11 18:53:54,957 | ERROR | ppc-dispatcher-3 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: No service logic found for [APPC,Generic_Configure,null,sync]

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

        at Proxy3dac49de_249e_44ea_9178_3251aea35ebb.execute(Unknown Source)

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.SVCLogicServiceExecute(WorkFlowManagerImpl.java:251)[384:appc-workflow-management-core:1.2.0]

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.executeWorkflow(WorkFlowManagerImpl.java:154)[384:appc-workflow-management-core:1.2.0]

        at Proxy01e5329d_f310_47f5_a8dc_16266785b6dd.executeWorkflow(Unknown Source)

        at Proxy6b0c2d51_9818_434e_8f3f_6d2dfbedb96b.executeWorkflow(Unknown Source)

        at org.openecomp.appc.executor.impl.CommandTask.execute(CommandTask.java:79)

        at org.openecomp.appc.executor.impl.LCMCommandTask.run(LCMCommandTask.java:175)

        at org.openecomp.appc.executionqueue.impl.QueueManager.lambda$enqueueTask$0(QueueManager.java:118)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_151]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_151]

        at java.lang.Thread.run(Thread.java:748)[:1.8.0_151]

2018-05-11 18:53:54,966 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (401) not found, keys are { (400) (Other)}

2018-05-11 18:53:54,997 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (success) not found, keys are { (failure)}

2018-05-11 18:53:54,997 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (failure)}

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Friday, May 11, 2018 1:28 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hi Vankat,

 

Can you attach your full log? The part of the log below does not help not much to check further.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Friday, May 11, 2018 12:02 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

I am able to add those entries. It is able to get capabilities. However, I am facing below error now.

 

2018-05-11 15:21:22,698 | INFO  | ppc-dispatcher-1 | ConfigResourceNode               | 360 - appc-common - 1.2.0 | getCapability Successful

2018-05-11 15:21:22,699 | INFO  | ppc-dispatcher-1 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome ("") not found, keys are { (Not-Supported) (Supported) (Other)}

2018-05-11 15:21:22,815 | ERROR | ppc-dispatcher-1 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Don't know how to execute transaction ID 1

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

        at Proxy3dac49de_249e_44ea_9178_3251aea35ebb.execute(Unknown Source)

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.SVCLogicServiceExecute(WorkFlowManagerImpl.java:251)[384:appc-workflow-management-core:1.2.0]

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.executeWorkflow(WorkFlowManagerImpl.java:154)[384:appc-workflow-management-core:1.2.0]

        at Proxy01e5329d_f310_47f5_a8dc_16266785b6dd.executeWorkflow(Unknown Source)

        at Proxy6b0c2d51_9818_434e_8f3f_6d2dfbedb96b.executeWorkflow(Unknown Source)

        at org.openecomp.appc.executor.impl.CommandTask.execute(CommandTask.java:79)

        at org.openecomp.appc.executor.impl.LCMCommandTask.run(LCMCommandTask.java:175)

        at org.openecomp.appc.executionqueue.impl.QueueManager.lambda$enqueueTask$0(QueueManager.java:118)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_151]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_151]

        at java.lang.Thread.run(Thread.java:748)[:1.8.0_151]

 

My entries are below;

 

mysql> SELECT * FROM ASDC_REFERENCE;

+-------------------+------------+-----------+---------------+--------+---------------+--------------------------------------+

| ASDC_REFERENCE_ID | VNF_TYPE   | VNFC_TYPE | FILE_CATEGORY | ACTION | ARTIFACT_TYPE | ARTIFACT_NAME                        |

+-------------------+------------+-----------+---------------+--------+---------------+--------------------------------------+

|                 1 | mrf2/MRF 0 | NULL      | capability    | NULL   | NULL          | capability_AllAction_vMRF_0.01v.json |

+-------------------+------------+-----------+---------------+--------+---------------+--------------------------------------+

1 row in set (0.00 sec)

 

mysql> SELECT * FROM ASDC_ARTIFACTS;

+-------------------+--------------------------------------+-----------------+--------------+---------------------+-------------------------------------+------------------------+---------------+------------------+---------------+---------------+---------------+------------------+----------------------+------------------+---------------------+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

| ASDC_ARTIFACTS_ID | SERVICE_UUID                         | DISTRIBUTION_ID | SERVICE_NAME | SERVICE_DESCRIPTION | RESOURCE_UUID                       | RESOURCE_INSTANCE_NAME | RESOURCE_NAME | RESOURCE_VERSION | RESOURCE_TYPE | ARTIFACT_UUID | ARTIFACT_TYPE | ARTIFACT_VERSION | ARTIFACT_DESCRIPTION | INTERNAL_VERSION | CREATION_DATE       | ARTIFACT_NAME                        | ARTIFACT_CONTENT                                                                                                                                                                                                                                                                                                                                                          |

+-------------------+--------------------------------------+-----------------+--------------+---------------------+-------------------------------------+------------------------+---------------+------------------+---------------+---------------+---------------+------------------+----------------------+------------------+---------------------+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

|                 1 | 6a000b37-1b4d-4ceb-b5d1-14722f2484f3 | 1               | mrf          | mrfconfigure        | d9d69025-0852-49a9-8982-d71553a557e | mrf                    | m2            | 1525955128862    | mrf2/MRF 0    | 1             | NULL          | NULL             | configure            |                1 | 2018-05-11 14:44:31 | capability_AllAction_vMRF_0.01v.json | {"capabilities":{"vnfc":[],"vm":[{"AttachVolume":[]},{"DetachVolume":[]},{"Evacuate":["pld","ssc"]},{"Migrate":["pld","ssc"]},{"Reboot":["pld","ssc"]},{"Rebuild":["pld","ssc"]},{"Restart":["pld","ssc"]},{"Snapshot":["pld","ssc"]},{"Start":["pld","ssc"]},{"Stop":["pld","ssc"]}],"vf-module":[],"vnf":["Configure","ConfigModify","OpenStack Actions","AllAction"]}} |

+-------------------+--------------------------------------+-----------------+--------------+---------------------+-------------------------------------+------------------------+---------------+------------------+---------------+---------------+---------------+------------------+----------------------+------------------+---------------------+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

1 row in set (0.00 sec)

 

 

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 10, 2018 10:36 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

HI Venkat,

 

I assume you followed the instruction to have APPC in your local env: https://wiki.onap.org/display/DW/Building+and+Running+APPC+Docker+Images.

 

Then you should have mysql container running in your local. The how-to login to mysql container is on the wiki page. And the source script for  creating tables for mysql is at: https://gerrit.onap.org/r/gitweb?p=appc/deployment.git;a=blob;f=installation/appc/src/main/scripts/installAppcDb.sh;h=fc5ae53caafec9a95a5c63e3061510de59a14c60;hb=refs/heads/master

 

Which is triggered from startODL.sh https://gerrit.onap.org/r/gitweb?p=appc/deployment.git;a=blob;f=installation/appc/src/main/scripts/startODL.sh;h=f58db40df0f031ee40d8df3b1c6019c1e5e817fe;hb=refs/heads/master

 

Taka

 

 

 

From: ANUMANENI, VENKATA RAMANA
Sent: Thursday, May 10, 2018 9:59 AM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

I am looking for mysql credentials to add these entries in those tables.

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 10, 2018 8:22 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

HI Venkat,

 

From error in your log, yes. This has to be done.

 

Sorry, What do you mean by “default credentials”?

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, May 09, 2018 6:11 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

Thank you for this. Is this has to be done on APPC?

 

What are the default credentials?

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Wednesday, May 09, 2018 1:55 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hi Venkat,

 

The Configure action is not in the reference file.

 

You would need to insert the capacity plan which has Configure action in two tables in mysql DB:

 

Here is the one sample:

 

On ASDC_ARTIFACTS table:

 

TLSUUID836241290926

TLDID95681

TLServiceName

Template Loader Test

TLRUID95681

TLRIName

null

TLResourceVersion

TLResourceType

TLAUUID95681

null

0.1

SdcTestDescription

41

2018-05-09 11:41:31

capability_AllAction_vUSP-MetaswitchvSBC_0.0.1V.json

{"capabilities":{"vnfc":[],"vm":[{"AttachVolume":[]},{"DetachVolume":[]},{"Evacuate":["pld","ssc"]},{"Migrate":["pld","ssc"]},{"Reboot":["pld","ssc"]},{"Rebuild":["pld","ssc"]},{"Restart":["pld","ssc"]},{"Snapshot":["pld","ssc"]},{"Start":["pld","ssc"]},{"Stop":["pld","ssc"]}],"vf-module":[],"vnf":["Configure","ConfigModify","OpenStack Actions","AllAction"]}}

 

On ASDC_REFERENCE table:

 

1899

vUSP-Metaswitch vSBC

null

capability

null

null

capability_AllAction_vUSP-MetaswitchvSBC_0.0.1V.json

 

Taka

 

 

From: ANUMANENI, VENKATA RAMANA
Sent: Tuesday, May 08, 2018 5:39 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Takamune,

 

Thanks for your support.

 

We have tried changes suggested by you. I sent LCM action configure command through APPC LCM API. Action was accepted but it has failed in service logic at below step.

 

At this moment, LCM API to sent Service Logic and it has queried A&AI successfully. But, Service Logic is not able find any further step.

 

Is there anything I am mssing?

 

 

2018-05-08 15:29:53,286 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (not-found) (failure)}

2018-05-08 15:29:53,289 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (not-found) not found, keys are { (failure)}

2018-05-08 15:29:53,289 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (failure)}

2018-05-08 15:29:53,290 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome ("") not found, keys are { (YES) (Other)}

2018-05-08 15:29:53,343 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (success) not found, keys are { (failure)}

2018-05-08 15:29:53,344 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (failure)}

2018-05-08 15:29:53,344 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (vnf) not found, keys are { (vm) (Other)}

2018-05-08 15:29:53,345 | INFO  | ppc-dispatcher-3 | ConfigResourceNode               | 360 - appc-common - 1.2.0 | Received getCapability call with params : {caplevel=vnf, checkCapability=Configure, vnf-type=MRF/MRF 0}

2018-05-08 15:29:53,346 | INFO  | ppc-dispatcher-3 | DGGeneralDBService               | 360 - appc-common - 1.2.0 | getCapability Query String : select max(internal_version) as maxInternalVersion, artifact_name as artifactName from ASDC_ARTIFACTS  where artifact_name in (select artifact_name from ASDC_REFERENCE  where vnf_type= $vnf-type  and file_category = 'capability' )

2018-05-08 15:29:53,352 | INFO  | ppc-dispatcher-3 | ConfigResourceNode               | 360 - appc-common - 1.2.0 | getCapability::returned from DB::+cap

2018-05-08 15:29:53,353 | INFO  | ppc-dispatcher-3 | ConfigResourceNode               | 360 - appc-common - 1.2.0 | getCapability Successful - No capability blocks found

2018-05-08 15:29:53,353 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome ("") not found, keys are { (Not-Supported) (Supported) (Other)}

2018-05-08 15:29:53,422 | ERROR | ppc-dispatcher-3 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Don't know how to execute transaction ID 1

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

        at Proxycfa15bb4_f80e_4ec0_a4a5_05840b27df19.execute(Unknown Source)

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.SVCLogicServiceExecute(WorkFlowManagerImpl.java:251)[384:appc-workflow-management-core:1.2.0]

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.executeWorkflow(WorkFlowManagerImpl.java:154)[384:appc-workflow-management-core:1.2.0]

        at Proxy811d5c86_04fa_4eb0_bac4_b322573a1a43.executeWorkflow(Unknown Source)

        at Proxy9777da8e_409e_4a97_8a9e_3f9c94b8ff99.executeWorkflow(Unknown Source)

        at org.openecomp.appc.executor.impl.CommandTask.execute(CommandTask.java:79)

        at org.openecomp.appc.executor.impl.LCMCommandTask.run(LCMCommandTask.java:175)

        at org.openecomp.appc.executionqueue.impl.QueueManager.lambda$enqueueTask$0(QueueManager.java:118)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_151]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_151]

        at java.lang.Thread.run(Thread.java:748)[:1.8.0_151]

2018-05-08 15:29:53,428 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (401) not found, keys are { (400) (Other)}

2018-05-08 15:29:53,460 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (success) not found, keys are { (failure)}

2018-05-08 15:29:53,461 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (failure)}

@                                                                                                                                                                                                                                                                                            

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Friday, May 04, 2018 2:21 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>; onap-discuss@...
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

On the same directory in APPC docker. You would see the appc_southbound.properties file instead. The format for ansible server in southbound properties is below:

 

<vnf-type>.ANSIBLE.<action_name>.user

<vnf-type>.ANSIBLE.<action_name>.port

<vnf-type>.ANSIBLE.<action_name>.password

<vnf-type>.ANSIBLE.<action_name>.url

 

<vnf-type> has to be matched with vnf-type in A&AI.

 

For example:

 

vUSP-vCOM.ANSIBLE.HealthCheck.user = XXX

vUSP-vCOM.ANSIBLE.HealthCheck.port = 5000

vUSP-vCOM.ANSIBLE.HealthCheck.password = ABCDEF

vUSP-vCOM.ANSIBLE.HealthCheck.url = https://<url>:5000

 

In Casablanca release, these ansible server configures will be moving to device_authentication table in  maria (now is mysql) db.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Friday, May 04, 2018 1:28 PM
To: CHO, TAKAMUNE <
tc012c@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>; onap-discuss@...
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello APPC team,

 

I am trying to update Ansible Server details in APPC properties file. But, we couldn’t find exact parameter to be updated. Could you please provide sample appc.properties file which has Ansible Server details?

 

ariable Name

Description

Type

Comments

User

Username to logon to Ansible Server

Mandatory

Should be provided by APPC.

Password

Password to logon to Ansible Server

Mandatory

Should be provided by APPC.

AgentUrl

The complete URL of the Ansible Server to post the request for execution and retrieve results (if in synchronous mode)

 

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Wednesday, April 04, 2018 3:56 PM
To: Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <
ramanjaneyul_reddy.akula@...>; onap-discuss@...
Cc: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>
Subject: RE: [onap-discuss] [app-c] appc client library location

 

HI Ramu,

 

Thanks for interested on APPC.

 

It sounds like your local_setting.xml for mvn build has an issue, can you attach your local_setting to me, I can take a look.

 

Thanks

 

Taka

 

From: onap-discuss-bounces@... [mailto:onap-discuss-bounces@...] On Behalf Of Akula, Ramanjaneyul Reddy (Nokia - US/Irving)
Sent: Wednesday, April 04, 2018 3:27 PM
To:
onap-discuss@...
Cc: ANUMANENI, VENKATA RAMANA <
venkataramana.a@...>
Subject: [onap-discuss] [app-c] appc client library location

 

Hi APPC Team,

We are planning to do some VNF configuration using APP-C. For the same, learned that we can use the APP-C client libraries (org.onap.appc.client:client-kit, org.onap.appc.client:client-lib) to send the LCM request to DMaaP topic (http://onap.readthedocs.io/en/latest/submodules/appc.git/docs/APPC%20Client%20Library%20Guide/APPC%20Client%20Library%20Guide.html#appc-client-library

 

However, we failed to located the needed jars.

Then tried to compile the code using the instructions @ “https://wiki.onap.org/display/DW/Building+Entire+ONAP

 

While comping the APP-C code, getting below error:

 

[FATAL] Non-resolvable parent POM for org.onap.appc:appc:1.3.0-SNAPSHOT: Failure to find org.onap.ccsdk.parent:odlparent-carbon-sr1:pom:0.1.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 25, column 13

@

 

Can someone help me on how to get around this problem.

 

 

Thanks & best regards,

Ramu

 

 

 

 


Taka Cho
 

Venkata,

 

Please provide the details step by step of how you generate the keystore file and password for https connection  between APPC and Ansible server and the console log that you did. Without that, I am not able to tell what went wrong in your setting.

 

Thanks

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Tuesday, June 05, 2018 1:33 PM
To: CHO, TAKAMUNE <tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

I have tried with below changes.

 

data/log# locate mykeystore.js

/home/ubuntu/mykeystore.js

/var/lib/docker/aufs/diff/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/opendaylight/tls-client/mykeystore.js

/var/lib/docker/aufs/mnt/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/opendaylight/tls-client/mykeystore.js

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Tuesday, June 05, 2018 11:04 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Venkata,

 

The default.properties is built on /opt/opendaylight/current/system/org/onap/appc/appc-ansible-adapter-bundle/1.3.0-SNAPSHOT/appc-ansible-adapter-bundle-1.3.0-SNAPSHOT.jar.

 

remove those values in appc.properties.

 

use and regenerate the truststore file with the default values of the default.properties in Repo below:

 

  org.onap.appc.adapter.ansible.trustStore=/opt/opendaylight/tls-client/mykeystore.js

  org.onap.appc.adapter.ansible.trustStore.trustPasswd=changeit

org.onap.appc.adapter.ansible.clientType=DEFAULT

 

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Monday, June 04, 2018 5:22 PM
To: CHO, TAKAMUNE <tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

We don’t have this file on APP-C.

 

root@nokonap-appc:~# locate default.properties

root@nokonap-appc:~#

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Monday, June 04, 2018 3:54 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkata,

 

As I stated before. You need to put those properties in

 

/appc-ansible-adapter-bundle/src/main/resources/org/onap/appc/default.properties.

 

Not in appc.properties.

 

Please try that. And let me know the result.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Monday, June 04, 2018 3:12 PM
To: CHO, TAKAMUNE <tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

I am still facing same issue even after doing lot of configuration changes. Below are the issues.

 

APPC Ansible Adapter is not taking configuration parameter from appc.properties file.

 

My appc.properties contains below parameters. I have restarted APPC with TRUST_all parameters also.

 

org.onap.appc.adapter.ansible.clientType=TRUST_CERT

org.onap.appc.adapter.ansible.trustStore=/opt/openecomp/appc/data/stores/truststore.openecomp.taco.jks

org.onap.appc.adapter.ansible.trustStore.trustPasswd=adminadmin

 

2018-06-04 18:53:21,305 | INFO  | Event Dispatcher | AnsibleAdapterImpl               | 402 - appc-ansible-adapter - 1.2.0 | Creating http client with default behaviour

 

I have followed steps mentioned at below link to create trust store.

 

https://docs.oracle.com/cd/E19509-01/820-3503/6nf1il6er/index.html

 

I am still facing same issue when I send request.

 

2018-06-04 18:08:34,091 | ERROR | ppc-dispatcher-1 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Ansible Adapter Error = Error posting request. Reason = sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

        at org.openecomp.appc.adapter.ansible.impl.AnsibleAdapterImpl.doFailure(AnsibleAdapterImpl.java:207)

        at org.openecomp.appc.adapter.ansible.impl.AnsibleAdapterImpl.reqExec(AnsibleAdapterImpl.java:325)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.CallNodeExecutor.execute(CallNodeExecutor.java:127)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.CallNodeExecutor.execute(CallNodeExecutor.java:127)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

 

If I use http it works but APPC doesn’t send authentication parameters in request whereas Ansible Server expects authentication parameters.

 

Please help me to solve this issue.

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 31, 2018 3:06 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkat,

 

TRUST_ALL value should be fine.

 

From the error you got (I excerpted)

 

Error posting request. Reason = sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

 

It sounds like your trusted keysore js file is not correct when you generated. Did you try to verify your js file from other CLI tools like open_ssl etc?

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, May 30, 2018 6:09 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

Thanks. I have actually added below parameter in appc.properties file to trust all Ansible Servers. But, It still expects certificate to be available in store.

 

root@nokonap-appc:~# grep org.onap.appc.adapter.ansible.clientType /opt/appc/installation/src/main/properties/appc.propertiesorg.onap.appc.adapter.ansible.clientType=TRUST_ALL

 

 

Regards

Venkat

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Wednesday, May 30, 2018 3:36 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

HI Venkata.

 

The path for the keystore key is defined on /appc-ansible-adapter-bundle/src/main/resources/org/onap/appc/default.properties

Which is https://gerrit.onap.org/r/gitweb?p=appc.git;a=blob;f=appc-adapters/appc-ansible-adapter/appc-ansible-adapter-bundle/src/main/resources/org/onap/appc/default.properties;h=d49c0396c5984fb8d46b2b3cf1f572223c8d5c6c;hb=refs/heads/master

 

I assume you know how to generate the trusted keystore file.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, May 30, 2018 3:12 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

We could pass “Unable decrypt the password”  error. Now, we are facing an issue with SSL certification.

Could you please help us to find the path to store certificates and other settings to solve this error?

 

2018-05-29 18:50:05,809 | ERROR | ppc-dispatcher-6 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Error posting request. Reason = sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

        at Proxye981c0ea_91ea_409d_8ef6_23c4fb2c32b1.execute(Unknown Source)

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.SVCLogicServiceExecute(WorkFlowManagerImpl.java:251)[384:appc-workflow-management-core:1.2.0]

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.executeWorkflow(WorkFlowManagerImpl.java:154)[384:appc-workflow-management-core:1.2.0]

        at Proxy405593b3_30f4_4ec4_83f6_6bbd2a7cb808.executeWorkflow(Unknown Source)

        at Proxy03b18168_8c75_4e04_8865_048a156628fb.executeWorkflow(Unknown Source)

        at org.openecomp.appc.executor.impl.CommandTask.execute(CommandTask.java:79)

        at org.openecomp.appc.executor.impl.LCMCommandTask.run(LCMCommandTask.java:175)

        at org.openecomp.appc.executionqueue.impl.QueueManager.lambda$enqueueTask$0(QueueManager.java:118)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_151]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_151]

        at java.lang.Thread.run(Thread.java:748)[:1.8.0_151]

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Friday, May 18, 2018 1:44 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkat,

 

I think there is something wrong when you are doing encrypt password.

 

There is the java code here: https://gerrit.onap.org/r/gitweb?p=appc.git;a=blob;f=appc-config/appc-encryption-tool/provider/src/main/java/org/onap/appc/encryptiontool/wrapper/WrapperEncryptionTool.java;h=6091e4cf275eb217f5fe2f230a425c95e2159904;hb=refs/heads/master

 

That can help you generate encrypted password for appc_southbound properties.

 

There is a wrapper script for this WrapperEncryptionTool.class in the attachment. You may need to change some lines for your env. I will add this script in APPC Repo for R3 later…

 

Hope that would help

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Friday, May 18, 2018 9:52 AM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

I have tried without username and password and facing same issue.

 

Below is the appc_southbound.properties file.

 

Also, Attached is the log file.

 

root@nokonap-appc:/# more ./var/lib/docker/aufs/mnt/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/app/bvc/properties/appc_southbound.properties

mrf2\/MRF\ 0.ANSIBLE.Configure.user=cman

mrf2\/MRF\ 0.ANSIBLE.Configure.port=8084

mrf2\/MRF\ 0.ANSIBLE.Configure.password=313DECE408AF7759D442D7B06DD9A6AA

mrf2\/MRF\ 0.ANSIBLE.Configure.url=https://10.203.134.105:8084/api/v1/ansibleserver

root@nokonap-appc:/#

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 17, 2018 3:46 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkat,

 

Can you try the payload without user and password?

 

And attach the appc_southbount.properties and full log?

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Thursday, May 17, 2018 3:33 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

Payload didn’t have username and password earlier and I was still facing same issue. So, I thought, I will give try with including password.

 

Also, appc_southbound.properties file has username and password(encrypted).

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 17, 2018 1:06 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

HI Venkat,

 

The log  says “error-message -- Unable to decrypt the password”. The user name and password should not be in the payload.

Those are supposed to update it in properties file which is appc southbound properties I mentioned before . Code will not read user id and password from payload.

 

From their payload

   "appc-provider-lcm:payload": "{\"Id\": \"$requestID\",\"PlaybookName\": \"vmmsc@playbook_linux@...\",\"NodeList\": [\"CMAN-TACO-MMSC1\" ],\"password\": \"313DECE408AF7759D442D7B06DD9A6AA\", \"Timeout\": 600, \"EnvParameters\": { \"working_dir\": \"/var/log\",\"command\": \"ls\", \"user_name\": \"root\",\"host_name\": \"mmsc\" }}"

 

From log

NodeList[0] -- CMAN-TACO-MMSC1

2018-05-16 20:13:18,925 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  template-name --

2018-05-16 20:13:18,925 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-message -- Unable to decrypt the password.

2018-05-16 20:13:18,925 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  input.common-header.sub-request-id -- 1-1

2018-05-16 20:13:18,925 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  SvcLogic.status -- failure

2018-05-16 20:13:18,926 | INFO  | ppc-dispatcher-7 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  input.common-header.request-id -- 10

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, May 16, 2018 4:31 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

Attached is log. Below is the request sent to configure. Please let me know if I am missing any thing.

 

{

"appc-provider-lcm:input": {

"appc-provider-lcm:action":"Configure",   

 "appc-provider-lcm:action-identifiers": {

"appc-provider-lcm:vnf-id": "d9d69025-0852-49a9-8982-d71553a557e4"

},

"appc-provider-lcm:common-header": {

      "appc-provider-lcm:request-id": "9",

      "appc-provider-lcm:originator-id": "venkat",

      "appc-provider-lcm:api-ver": "2.43",

      "appc-provider-lcm:timestamp": "2018-05-16T20:11:55.55Z",

      "appc-provider-lcm:sub-request-id": "1-1",

      "appc-provider-lcm:flags": {

        "appc-provider-lcm:ttl": "0",

        "appc-provider-lcm:force": "TRUE",

        "appc-provider-lcm:mode": "NORMAL"

}

},

   "appc-provider-lcm:payload": "{\"Id\": \"$requestID\",\"PlaybookName\": \"vmmsc@playbook_linux@...\",\"NodeList\": [\"CMAN-TACO-MMSC1\" ],\"password\": \"313DECE408AF7759D442D7B06DD9A6AA\", \"Timeout\": 600, \"EnvParameters\": { \"working_dir\": \"/var/log\",\"command\": \"ls\", \"user_name\": \"root\",\"host_name\": \"mmsc\" }}"

}

}

 

Regards

Venkat

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Monday, May 14, 2018 1:04 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkat,

 

Yes. User would provide their own credentials for Ansible Server RESTful API.

 

Maybe you missed my previous email, I assume you followed this : https://gerrit.onap.org/r/gitweb?p=appc.git;a=tree;f=appc-adapters/appc-ansible-adapter/appc-ansible-example-server;h=90fa259c3905d1c5f25b9668a6e537a7c1f1a8e4;hb=refs/heads/master for setting up RESTful API in Ansible server.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Monday, May 14, 2018 11:05 AM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

Sorry I missed your email.

 

My question, Do we need provider credentials as Ansible Server REST API shouldn’t be configured with credentials as per ONAP documentation.

 

mrf2\/MRF\ 0.ANSIBLE.Configure.user=<username>

mrf2\/MRF\ 0.ANSIBLE.Configure.port=8084

mrf2\/MRF\ 0.ANSIBLE.Configure.password=<encrypted password>

mrf2\/MRF\ 0.ANSIBLE.Configure.url=https://<IP>:8084/ui

                                  

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Monday, May 14, 2018 9:25 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hi Venkat,

 

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-code -- 401

 

So you got 401 error back. Did you try to use other cli tools like openssl or curl command to test the connection with the password that you used?

 

Also Can you attach the appc_southbound.properties file?

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Friday, May 11, 2018 5:33 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

Below is the latest status.

 

It was looking for “appc_southbound.properties” file at /opt/app/bvc/properties/. I have created this file.

 

2018-05-11 20:08:30,490 | ERROR | ppc-dispatcher-5 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Cannot locate configuration source /opt/app/bvc/properties/appc_southbound.properties

 

After this, It says that It is “Unable to decrypt the password”. I tried to encrypt the password using “so” VM but it still fails at the same place.

 

Any help to fix this issue would be appreciated.

 

2018-05-11 21:24:52,271 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  password -- password

2018-05-11 21:24:52,271 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  request-action -- Configure

2018-05-11 21:24:52,271 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  configurationblock --

2018-05-11 21:24:52,271 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  EnvParameters --

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  EnvParameters.host_name -- mmsc

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  VNFCNAME0 --

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  api-ver --

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  EnvParameters.working_dir -- /var/log

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-code -- 401

2018-05-11 21:24:52,272 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  vnfc-type --

2018-05-11 21:24:52,273 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  EnvParameters.user_name -- root

2018-05-11 21:24:52,273 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  vf-module-id --

2018-05-11 21:24:52,273 | INFO  | ppc-dispatcher-1 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  tmp.vnfInfo.vm-count -- 0

2018-05-11 21:24:52,273 | INFO  | ppc-dispatcher-1 | FlowControlNode                  | 360 - appc-common - 1.2.0 | Handling Response for transaction Id 1

2018-05-11 21:24:52,274 | INFO  | ppc-dispatcher-1 | DefaultResponseHandler           | 360 - appc-common - 1.2.0 | Transaction Input params Transaction [transactionId=1, action=Configure, actionLevel=vnf, actionIdentifier=null, parameters=null, executionType=graph, uId=null, statusCode=401, pswd=null, executionEndPoint=null, executionModule=APPC, executionRPC=Generic_AnsibleDG, state=null, precheck=null, payload={"Id": "$requestID","PlaybookName": "vmmsc@playbook_linux@...","NodeList": ["CMAN-TACO-MMSC1" ],"Timeout": 600, "EnvParameters": { "working_dir": "/var/log","command": "ls", "user_name": "root","host_name": "mmsc" }}, responses=[Response [responseCode=null, responseMessage=null, responseAction=ResponseAction [wait=null, retry=null, jump=null, ignore=false, stop=true, intermediateMessage=false], responseActionHanlder=null]], status=failure]

2018-05-11 21:24:52,274 | INFO  | ppc-dispatcher-1 | FlowControlNode                  | 360 - appc-common - 1.2.0 | Executed all the transacstion successfully

2018-05-11 21:24:52,275 | ERROR | ppc-dispatcher-1 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Unable to decrypt the password.

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

 

Regards

Venkat

 

 

From: Anumaneni, Venkataramana (Nokia - US/Irving)
Sent: Friday, May 11, 2018 3:11 PM
To: 'CHO, TAKAMUNE' <
tc012c@...>; 'onap-discuss@...' <onap-discuss@...>
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

I have found this issue. I think, EXECUTION_RPC should be “Generic_AnsibleDG” when PROTOCOL is “Ansible”.

Please correct me if I am wrong.

 

 

mysql> select * from PROCESS_FLOW_REFERENCE where ACTION="Configure" and ACTION_LEVEL="vnf" and PROTOCOL="Ansible";

+---------------------------+-----------+--------------+----------+----------------+------------------+-------------------+---------------------+--------------------+

| PROCESS_FLOW_REFERENCE_ID | ACTION    | ACTION_LEVEL | PROTOCOL | EXECUTION_TYPE | EXECUTION_MODULE | EXECUTION_RPC     | UPDATED_DATE        | GET_RUNNING_CONFIG |

+---------------------------+-----------+--------------+----------+----------------+------------------+-------------------+---------------------+--------------------+

|                        24 | Configure | vnf          | Ansible  | graph          | APPC             | Generic_Configure | 2017-08-25 19:40:05 | NULL               |

|                        52 | Configure | vnf          | Ansible  | graph          | APPC             | Generic_Configure | 2017-09-12 16:49:54 | NULL               |

+---------------------------+-----------+--------------+----------+----------------+------------------+-------------------+---------------------+--------------------+

2 rows in set (0.00 sec)

 

 

Regards

Venkat

 

 

From: Anumaneni, Venkataramana (Nokia - US/Irving)
Sent: Friday, May 11, 2018 2:27 PM
To: 'CHO, TAKAMUNE' <
tc012c@...>; 'onap-discuss@...' <onap-discuss@...>
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

After further analysis, APPC should search with “APPC,ansible-adapter-1.0,2.0.1,sync “ instead of “APPC,Generic_Configure,null,sync”.

 

How does APPC gets these parmeters?

 

Regards

Venkat

 

 

From: Anumaneni, Venkataramana (Nokia - US/Irving)
Sent: Friday, May 11, 2018 2:12 PM
To: 'CHO, TAKAMUNE' <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

I have found the root cause of the below error. There were no entries in PROTOCOL_REFERENCE table for this vnf type. After adding entry and make it Ansible, it went further and now it failed while fetching sevice logic.

 

Do I have to add any entry in Service logic table manually?

 

2018-05-11 18:53:54,950 | INFO  | ppc-dispatcher-3 | SvcLogicServiceImpl              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Fetching service logic from data store

2018-05-11 18:53:54,952 | INFO  | ppc-dispatcher-3 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-message -- No service logic found for [APPC,Generic_Configure,null,sync]

2018-05-11 18:53:54,955 | INFO  | ppc-dispatcher-3 | GraphExecutor                    | 360 - appc-common - 1.2.0 | NEW KEY =  error-code -- 401

2018-05-11 18:53:54,955 | INFO  | ppc-dispatcher-3 | FlowControlNode                  | 360 - appc-common - 1.2.0 | Handling Response for transaction Id 1

2018-05-11 18:53:54,956 | INFO  | ppc-dispatcher-3 | DefaultResponseHandler           | 360 - appc-common - 1.2.0 | Transaction Input params Transaction [transactionId=1, action=Configure, actionLevel=vnf, actionIdentifier=null, parameters=null, executionType=graph, uId=null, statusCode=401, pswd=null, executionEndPoint=null, executionModule=APPC, executionRPC=Generic_Configure, state=null, precheck=null, payload={"Id": "$requestID","PlaybookName": "vmmsc@playbook_linux@...","NodeList": ["CMAN-TACO-MMSC1" ],"Timeout": 600, "EnvParameters": { "working_dir": "/var/log","command": "ls", "user_name": "root","host_name": "mmsc" }}, responses=[Response [responseCode=null, responseMessage=null, responseAction=ResponseAction [wait=null, retry=null, jump=null, ignore=false, stop=true, intermediateMessage=false], responseActionHanlder=null]], status=Others]

2018-05-11 18:53:54,956 | INFO  | ppc-dispatcher-3 | FlowControlNode                  | 360 - appc-common - 1.2.0 | Executed all the transacstion successfully

2018-05-11 18:53:54,957 | ERROR | ppc-dispatcher-3 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: No service logic found for [APPC,Generic_Configure,null,sync]

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

        at Proxy3dac49de_249e_44ea_9178_3251aea35ebb.execute(Unknown Source)

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.SVCLogicServiceExecute(WorkFlowManagerImpl.java:251)[384:appc-workflow-management-core:1.2.0]

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.executeWorkflow(WorkFlowManagerImpl.java:154)[384:appc-workflow-management-core:1.2.0]

        at Proxy01e5329d_f310_47f5_a8dc_16266785b6dd.executeWorkflow(Unknown Source)

        at Proxy6b0c2d51_9818_434e_8f3f_6d2dfbedb96b.executeWorkflow(Unknown Source)

        at org.openecomp.appc.executor.impl.CommandTask.execute(CommandTask.java:79)

        at org.openecomp.appc.executor.impl.LCMCommandTask.run(LCMCommandTask.java:175)

        at org.openecomp.appc.executionqueue.impl.QueueManager.lambda$enqueueTask$0(QueueManager.java:118)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_151]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_151]

        at java.lang.Thread.run(Thread.java:748)[:1.8.0_151]

2018-05-11 18:53:54,966 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (401) not found, keys are { (400) (Other)}

2018-05-11 18:53:54,997 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (success) not found, keys are { (failure)}

2018-05-11 18:53:54,997 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (failure)}

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Friday, May 11, 2018 1:28 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hi Vankat,

 

Can you attach your full log? The part of the log below does not help not much to check further.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Friday, May 11, 2018 12:02 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

I am able to add those entries. It is able to get capabilities. However, I am facing below error now.

 

2018-05-11 15:21:22,698 | INFO  | ppc-dispatcher-1 | ConfigResourceNode               | 360 - appc-common - 1.2.0 | getCapability Successful

2018-05-11 15:21:22,699 | INFO  | ppc-dispatcher-1 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome ("") not found, keys are { (Not-Supported) (Supported) (Other)}

2018-05-11 15:21:22,815 | ERROR | ppc-dispatcher-1 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Don't know how to execute transaction ID 1

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

        at Proxy3dac49de_249e_44ea_9178_3251aea35ebb.execute(Unknown Source)

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.SVCLogicServiceExecute(WorkFlowManagerImpl.java:251)[384:appc-workflow-management-core:1.2.0]

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.executeWorkflow(WorkFlowManagerImpl.java:154)[384:appc-workflow-management-core:1.2.0]

        at Proxy01e5329d_f310_47f5_a8dc_16266785b6dd.executeWorkflow(Unknown Source)

        at Proxy6b0c2d51_9818_434e_8f3f_6d2dfbedb96b.executeWorkflow(Unknown Source)

        at org.openecomp.appc.executor.impl.CommandTask.execute(CommandTask.java:79)

        at org.openecomp.appc.executor.impl.LCMCommandTask.run(LCMCommandTask.java:175)

        at org.openecomp.appc.executionqueue.impl.QueueManager.lambda$enqueueTask$0(QueueManager.java:118)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_151]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_151]

        at java.lang.Thread.run(Thread.java:748)[:1.8.0_151]

 

My entries are below;

 

mysql> SELECT * FROM ASDC_REFERENCE;

+-------------------+------------+-----------+---------------+--------+---------------+--------------------------------------+

| ASDC_REFERENCE_ID | VNF_TYPE   | VNFC_TYPE | FILE_CATEGORY | ACTION | ARTIFACT_TYPE | ARTIFACT_NAME                        |

+-------------------+------------+-----------+---------------+--------+---------------+--------------------------------------+

|                 1 | mrf2/MRF 0 | NULL      | capability    | NULL   | NULL          | capability_AllAction_vMRF_0.01v.json |

+-------------------+------------+-----------+---------------+--------+---------------+--------------------------------------+

1 row in set (0.00 sec)

 

mysql> SELECT * FROM ASDC_ARTIFACTS;

+-------------------+--------------------------------------+-----------------+--------------+---------------------+-------------------------------------+------------------------+---------------+------------------+---------------+---------------+---------------+------------------+----------------------+------------------+---------------------+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

| ASDC_ARTIFACTS_ID | SERVICE_UUID                         | DISTRIBUTION_ID | SERVICE_NAME | SERVICE_DESCRIPTION | RESOURCE_UUID                       | RESOURCE_INSTANCE_NAME | RESOURCE_NAME | RESOURCE_VERSION | RESOURCE_TYPE | ARTIFACT_UUID | ARTIFACT_TYPE | ARTIFACT_VERSION | ARTIFACT_DESCRIPTION | INTERNAL_VERSION | CREATION_DATE       | ARTIFACT_NAME                        | ARTIFACT_CONTENT                                                                                                                                                                                                                                                                                                                                                          |

+-------------------+--------------------------------------+-----------------+--------------+---------------------+-------------------------------------+------------------------+---------------+------------------+---------------+---------------+---------------+------------------+----------------------+------------------+---------------------+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

|                 1 | 6a000b37-1b4d-4ceb-b5d1-14722f2484f3 | 1               | mrf          | mrfconfigure        | d9d69025-0852-49a9-8982-d71553a557e | mrf                    | m2            | 1525955128862    | mrf2/MRF 0    | 1             | NULL          | NULL             | configure            |                1 | 2018-05-11 14:44:31 | capability_AllAction_vMRF_0.01v.json | {"capabilities":{"vnfc":[],"vm":[{"AttachVolume":[]},{"DetachVolume":[]},{"Evacuate":["pld","ssc"]},{"Migrate":["pld","ssc"]},{"Reboot":["pld","ssc"]},{"Rebuild":["pld","ssc"]},{"Restart":["pld","ssc"]},{"Snapshot":["pld","ssc"]},{"Start":["pld","ssc"]},{"Stop":["pld","ssc"]}],"vf-module":[],"vnf":["Configure","ConfigModify","OpenStack Actions","AllAction"]}} |

+-------------------+--------------------------------------+-----------------+--------------+---------------------+-------------------------------------+------------------------+---------------+------------------+---------------+---------------+---------------+------------------+----------------------+------------------+---------------------+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

1 row in set (0.00 sec)

 

 

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 10, 2018 10:36 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

HI Venkat,

 

I assume you followed the instruction to have APPC in your local env: https://wiki.onap.org/display/DW/Building+and+Running+APPC+Docker+Images.

 

Then you should have mysql container running in your local. The how-to login to mysql container is on the wiki page. And the source script for  creating tables for mysql is at: https://gerrit.onap.org/r/gitweb?p=appc/deployment.git;a=blob;f=installation/appc/src/main/scripts/installAppcDb.sh;h=fc5ae53caafec9a95a5c63e3061510de59a14c60;hb=refs/heads/master

 

Which is triggered from startODL.sh https://gerrit.onap.org/r/gitweb?p=appc/deployment.git;a=blob;f=installation/appc/src/main/scripts/startODL.sh;h=f58db40df0f031ee40d8df3b1c6019c1e5e817fe;hb=refs/heads/master

 

Taka

 

 

 

From: ANUMANENI, VENKATA RAMANA
Sent: Thursday, May 10, 2018 9:59 AM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

I am looking for mysql credentials to add these entries in those tables.

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 10, 2018 8:22 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

HI Venkat,

 

From error in your log, yes. This has to be done.

 

Sorry, What do you mean by “default credentials”?

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, May 09, 2018 6:11 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Taka,

 

Thank you for this. Is this has to be done on APPC?

 

What are the default credentials?

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Wednesday, May 09, 2018 1:55 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hi Venkat,

 

The Configure action is not in the reference file.

 

You would need to insert the capacity plan which has Configure action in two tables in mysql DB:

 

Here is the one sample:

 

On ASDC_ARTIFACTS table:

 

TLSUUID836241290926

TLDID95681

TLServiceName

Template Loader Test

TLRUID95681

TLRIName

null

TLResourceVersion

TLResourceType

TLAUUID95681

null

0.1

SdcTestDescription

41

2018-05-09 11:41:31

capability_AllAction_vUSP-MetaswitchvSBC_0.0.1V.json

{"capabilities":{"vnfc":[],"vm":[{"AttachVolume":[]},{"DetachVolume":[]},{"Evacuate":["pld","ssc"]},{"Migrate":["pld","ssc"]},{"Reboot":["pld","ssc"]},{"Rebuild":["pld","ssc"]},{"Restart":["pld","ssc"]},{"Snapshot":["pld","ssc"]},{"Start":["pld","ssc"]},{"Stop":["pld","ssc"]}],"vf-module":[],"vnf":["Configure","ConfigModify","OpenStack Actions","AllAction"]}}

 

On ASDC_REFERENCE table:

 

1899

vUSP-Metaswitch vSBC

null

capability

null

null

capability_AllAction_vUSP-MetaswitchvSBC_0.0.1V.json

 

Taka

 

 

From: ANUMANENI, VENKATA RAMANA
Sent: Tuesday, May 08, 2018 5:39 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello Takamune,

 

Thanks for your support.

 

We have tried changes suggested by you. I sent LCM action configure command through APPC LCM API. Action was accepted but it has failed in service logic at below step.

 

At this moment, LCM API to sent Service Logic and it has queried A&AI successfully. But, Service Logic is not able find any further step.

 

Is there anything I am mssing?

 

 

2018-05-08 15:29:53,286 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (not-found) (failure)}

2018-05-08 15:29:53,289 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (not-found) not found, keys are { (failure)}

2018-05-08 15:29:53,289 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (failure)}

2018-05-08 15:29:53,290 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome ("") not found, keys are { (YES) (Other)}

2018-05-08 15:29:53,343 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (success) not found, keys are { (failure)}

2018-05-08 15:29:53,344 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (failure)}

2018-05-08 15:29:53,344 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (vnf) not found, keys are { (vm) (Other)}

2018-05-08 15:29:53,345 | INFO  | ppc-dispatcher-3 | ConfigResourceNode               | 360 - appc-common - 1.2.0 | Received getCapability call with params : {caplevel=vnf, checkCapability=Configure, vnf-type=MRF/MRF 0}

2018-05-08 15:29:53,346 | INFO  | ppc-dispatcher-3 | DGGeneralDBService               | 360 - appc-common - 1.2.0 | getCapability Query String : select max(internal_version) as maxInternalVersion, artifact_name as artifactName from ASDC_ARTIFACTS  where artifact_name in (select artifact_name from ASDC_REFERENCE  where vnf_type= $vnf-type  and file_category = 'capability' )

2018-05-08 15:29:53,352 | INFO  | ppc-dispatcher-3 | ConfigResourceNode               | 360 - appc-common - 1.2.0 | getCapability::returned from DB::+cap

2018-05-08 15:29:53,353 | INFO  | ppc-dispatcher-3 | ConfigResourceNode               | 360 - appc-common - 1.2.0 | getCapability Successful - No capability blocks found

2018-05-08 15:29:53,353 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome ("") not found, keys are { (Not-Supported) (Supported) (Other)}

2018-05-08 15:29:53,422 | ERROR | ppc-dispatcher-3 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Don't know how to execute transaction ID 1

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

        at Proxycfa15bb4_f80e_4ec0_a4a5_05840b27df19.execute(Unknown Source)

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.SVCLogicServiceExecute(WorkFlowManagerImpl.java:251)[384:appc-workflow-management-core:1.2.0]

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.executeWorkflow(WorkFlowManagerImpl.java:154)[384:appc-workflow-management-core:1.2.0]

        at Proxy811d5c86_04fa_4eb0_bac4_b322573a1a43.executeWorkflow(Unknown Source)

        at Proxy9777da8e_409e_4a97_8a9e_3f9c94b8ff99.executeWorkflow(Unknown Source)

        at org.openecomp.appc.executor.impl.CommandTask.execute(CommandTask.java:79)

        at org.openecomp.appc.executor.impl.LCMCommandTask.run(LCMCommandTask.java:175)

        at org.openecomp.appc.executionqueue.impl.QueueManager.lambda$enqueueTask$0(QueueManager.java:118)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_151]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_151]

        at java.lang.Thread.run(Thread.java:748)[:1.8.0_151]

2018-05-08 15:29:53,428 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (401) not found, keys are { (400) (Other)}

2018-05-08 15:29:53,460 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (success) not found, keys are { (failure)}

2018-05-08 15:29:53,461 | INFO  | ppc-dispatcher-3 | SvcLogicExprListener             | 294 - org.onap.ccsdk.sli.core.sli-common - 0.1.2 | Outcome (Other) not found, keys are { (failure)}

@                                                                                                                                                                                                                                                                                            

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Friday, May 04, 2018 2:21 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>; onap-discuss@...
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

On the same directory in APPC docker. You would see the appc_southbound.properties file instead. The format for ansible server in southbound properties is below:

 

<vnf-type>.ANSIBLE.<action_name>.user

<vnf-type>.ANSIBLE.<action_name>.port

<vnf-type>.ANSIBLE.<action_name>.password

<vnf-type>.ANSIBLE.<action_name>.url

 

<vnf-type> has to be matched with vnf-type in A&AI.

 

For example:

 

vUSP-vCOM.ANSIBLE.HealthCheck.user = XXX

vUSP-vCOM.ANSIBLE.HealthCheck.port = 5000

vUSP-vCOM.ANSIBLE.HealthCheck.password = ABCDEF

vUSP-vCOM.ANSIBLE.HealthCheck.url = https://<url>:5000

 

In Casablanca release, these ansible server configures will be moving to device_authentication table in  maria (now is mysql) db.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Friday, May 04, 2018 1:28 PM
To: CHO, TAKAMUNE <
tc012c@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>; onap-discuss@...
Subject: RE: [onap-discuss] [app-c] Ansible Server details in
appc.properties file

 

Hello APPC team,

 

I am trying to update Ansible Server details in APPC properties file. But, we couldn’t find exact parameter to be updated. Could you please provide sample appc.properties file which has Ansible Server details?

 

ariable Name

Description

Type

Comments

User

Username to logon to Ansible Server

Mandatory

Should be provided by APPC.

Password

Password to logon to Ansible Server

Mandatory

Should be provided by APPC.

AgentUrl

The complete URL of the Ansible Server to post the request for execution and retrieve results (if in synchronous mode)

 

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Wednesday, April 04, 2018 3:56 PM
To: Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <
ramanjaneyul_reddy.akula@...>; onap-discuss@...
Cc: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>
Subject: RE: [onap-discuss] [app-c] appc client library location

 

HI Ramu,

 

Thanks for interested on APPC.

 

It sounds like your local_setting.xml for mvn build has an issue, can you attach your local_setting to me, I can take a look.

 

Thanks

 

Taka

 

From: onap-discuss-bounces@... [mailto:onap-discuss-bounces@...] On Behalf Of Akula, Ramanjaneyul Reddy (Nokia - US/Irving)
Sent: Wednesday, April 04, 2018 3:27 PM
To:
onap-discuss@...
Cc: ANUMANENI, VENKATA RAMANA <
venkataramana.a@...>
Subject: [onap-discuss] [app-c] appc client library location

 

Hi APPC Team,

We are planning to do some VNF configuration using APP-C. For the same, learned that we can use the APP-C client libraries (org.onap.appc.client:client-kit, org.onap.appc.client:client-lib) to send the LCM request to DMaaP topic (http://onap.readthedocs.io/en/latest/submodules/appc.git/docs/APPC%20Client%20Library%20Guide/APPC%20Client%20Library%20Guide.html#appc-client-library

 

However, we failed to located the needed jars.

Then tried to compile the code using the instructions @ “https://wiki.onap.org/display/DW/Building+Entire+ONAP

 

While comping the APP-C code, getting below error:

 

[FATAL] Non-resolvable parent POM for org.onap.appc:appc:1.3.0-SNAPSHOT: Failure to find org.onap.ccsdk.parent:odlparent-carbon-sr1:pom:0.1.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 25, column 13

@

 

Can someone help me on how to get around this problem.

 

 

Thanks & best regards,

Ramu

 

 

 

 


Anumaneni, Venkataramana (Nokia - US/Irving)
 

Hello Taka,

 

I have tried with below changes.

 

data/log# locate mykeystore.js

/home/ubuntu/mykeystore.js

/var/lib/docker/aufs/diff/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/opendaylight/tls-client/mykeystore.js

/var/lib/docker/aufs/mnt/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/opendaylight/tls-client/mykeystore.js

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Tuesday, June 05, 2018 11:04 AM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Venkata,

 

The default.properties is built on /opt/opendaylight/current/system/org/onap/appc/appc-ansible-adapter-bundle/1.3.0-SNAPSHOT/appc-ansible-adapter-bundle-1.3.0-SNAPSHOT.jar.

 

remove those values in appc.properties.

 

use and regenerate the truststore file with the default values of the default.properties in Repo below:

 

  org.onap.appc.adapter.ansible.trustStore=/opt/opendaylight/tls-client/mykeystore.js

  org.onap.appc.adapter.ansible.trustStore.trustPasswd=changeit

org.onap.appc.adapter.ansible.clientType=DEFAULT

 

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Monday, June 04, 2018 5:22 PM
To: CHO, TAKAMUNE <tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

We don’t have this file on APP-C.

 

root@nokonap-appc:~# locate default.properties

root@nokonap-appc:~#

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Monday, June 04, 2018 3:54 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkata,

 

As I stated before. You need to put those properties in

 

/appc-ansible-adapter-bundle/src/main/resources/org/onap/appc/default.properties.

 

Not in appc.properties.

 

Please try that. And let me know the result.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Monday, June 04, 2018 3:12 PM
To: CHO, TAKAMUNE <tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

I am still facing same issue even after doing lot of configuration changes. Below are the issues.

 

APPC Ansible Adapter is not taking configuration parameter from appc.properties file.

 

My appc.properties contains below parameters. I have restarted APPC with TRUST_all parameters also.

 

org.onap.appc.adapter.ansible.clientType=TRUST_CERT

org.onap.appc.adapter.ansible.trustStore=/opt/openecomp/appc/data/stores/truststore.openecomp.taco.jks

org.onap.appc.adapter.ansible.trustStore.trustPasswd=adminadmin

 

2018-06-04 18:53:21,305 | INFO  | Event Dispatcher | AnsibleAdapterImpl               | 402 - appc-ansible-adapter - 1.2.0 | Creating http client with default behaviour

 

I have followed steps mentioned at below link to create trust store.

 

https://docs.oracle.com/cd/E19509-01/820-3503/6nf1il6er/index.html

 

I am still facing same issue when I send request.

 

2018-06-04 18:08:34,091 | ERROR | ppc-dispatcher-1 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Ansible Adapter Error = Error posting request. Reason = sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

        at org.openecomp.appc.adapter.ansible.impl.AnsibleAdapterImpl.doFailure(AnsibleAdapterImpl.java:207)

        at org.openecomp.appc.adapter.ansible.impl.AnsibleAdapterImpl.reqExec(AnsibleAdapterImpl.java:325)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.CallNodeExecutor.execute(CallNodeExecutor.java:127)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.CallNodeExecutor.execute(CallNodeExecutor.java:127)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

 

If I use http it works but APPC doesn’t send authentication parameters in request whereas Ansible Server expects authentication parameters.

 

Please help me to solve this issue.

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 31, 2018 3:06 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkat,

 

TRUST_ALL value should be fine.

 

From the error you got (I excerpted)

 

Error posting request. Reason = sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

 

It sounds like your trusted keysore js file is not correct when you generated. Did you try to verify your js file from other CLI tools like open_ssl etc?

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, May 30, 2018 6:09 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

Thanks. I have actually added below parameter in appc.properties file to trust all Ansible Servers. But, It still expects certificate to be available in store.

 

root@nokonap-appc:~# grep org.onap.appc.adapter.ansible.clientType /opt/appc/installation/src/main/properties/appc.propertiesorg.onap.appc.adapter.ansible.clientType=TRUST_ALL

 

 

Regards

Venkat

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Wednesday, May 30, 2018 3:36 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

HI Venkata.

 

The path for the keystore key is defined on /appc-ansible-adapter-bundle/src/main/resources/org/onap/appc/default.properties

Which is https://gerrit.onap.org/r/gitweb?p=appc.git;a=blob;f=appc-adapters/appc-ansible-adapter/appc-ansible-adapter-bundle/src/main/resources/org/onap/appc/default.properties;h=d49c0396c5984fb8d46b2b3cf1f572223c8d5c6c;hb=refs/heads/master

 

I assume you know how to generate the trusted keystore file.

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Wednesday, May 30, 2018 3:12 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

We could pass “Unable decrypt the password”  error. Now, we are facing an issue with SSL certification.

Could you please help us to find the path to store certificates and other settings to solve this error?

 

2018-05-29 18:50:05,809 | ERROR | ppc-dispatcher-6 | ExecuteNodeExecutor              | 295 - org.onap.ccsdk.sli.core.sli-provider - 0.1.2 | Could not execute plugin. SvcLogic status will be set to failure.

org.onap.ccsdk.sli.core.sli.SvcLogicException: Error posting request. Reason = sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

        at org.openecomp.appc.flow.controller.node.FlowControlNode.processFlow(FlowControlNode.java:107)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_151]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_151]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_151]

        at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_151]

        at org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor.execute(ExecuteNodeExecutor.java:96)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.BlockNodeExecutor.execute(BlockNodeExecutor.java:62)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.executeNode(SvcLogicServiceImpl.java:182)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:159)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:248)

        at org.onap.ccsdk.sli.core.sli.provider.SvcLogicServiceImpl.execute(SvcLogicServiceImpl.java:221)

        at Proxye981c0ea_91ea_409d_8ef6_23c4fb2c32b1.execute(Unknown Source)

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.SVCLogicServiceExecute(WorkFlowManagerImpl.java:251)[384:appc-workflow-management-core:1.2.0]

        at org.openecomp.appc.workflow.impl.WorkFlowManagerImpl.executeWorkflow(WorkFlowManagerImpl.java:154)[384:appc-workflow-management-core:1.2.0]

        at Proxy405593b3_30f4_4ec4_83f6_6bbd2a7cb808.executeWorkflow(Unknown Source)

        at Proxy03b18168_8c75_4e04_8865_048a156628fb.executeWorkflow(Unknown Source)

        at org.openecomp.appc.executor.impl.CommandTask.execute(CommandTask.java:79)

        at org.openecomp.appc.executor.impl.LCMCommandTask.run(LCMCommandTask.java:175)

        at org.openecomp.appc.executionqueue.impl.QueueManager.lambda$enqueueTask$0(QueueManager.java:118)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_151]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_151]

        at java.lang.Thread.run(Thread.java:748)[:1.8.0_151]

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Friday, May 18, 2018 1:44 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkat,

 

I think there is something wrong when you are doing encrypt password.

 

There is the java code here: https://gerrit.onap.org/r/gitweb?p=appc.git;a=blob;f=appc-config/appc-encryption-tool/provider/src/main/java/org/onap/appc/encryptiontool/wrapper/WrapperEncryptionTool.java;h=6091e4cf275eb217f5fe2f230a425c95e2159904;hb=refs/heads/master

 

That can help you generate encrypted password for appc_southbound properties.

 

There is a wrapper script for this WrapperEncryptionTool.class in the attachment. You may need to change some lines for your env. I will add this script in APPC Repo for R3 later…

 

Hope that would help

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Friday, May 18, 2018 9:52 AM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

I have tried without username and password and facing same issue.

 

Below is the appc_southbound.properties file.

 

Also, Attached is the log file.

 

root@nokonap-appc:/# more ./var/lib/docker/aufs/mnt/49d7a48097f9b186c62e4a30931c6748578492e1e5a22d73daff5b4d1b718225/opt/app/bvc/properties/appc_southbound.properties

mrf2\/MRF\ 0.ANSIBLE.Configure.user=cman

mrf2\/MRF\ 0.ANSIBLE.Configure.port=8084

mrf2\/MRF\ 0.ANSIBLE.Configure.password=313DECE408AF7759D442D7B06DD9A6AA

mrf2\/MRF\ 0.ANSIBLE.Configure.url=https://10.203.134.105:8084/api/v1/ansibleserver

root@nokonap-appc:/#

 

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 17, 2018 3:46 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hi Venkat,

 

Can you try the payload without user and password?

 

And attach the appc_southbount.properties and full log?

 

Taka

 

From: ANUMANENI, VENKATA RAMANA
Sent: Thursday, May 17, 2018 3:33 PM
To: CHO, TAKAMUNE <
tc012c@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

Hello Taka,

 

Payload didn’t have username and password earlier and I was still facing same issue. So, I thought, I will give try with including password.

 

Also, appc_southbound.properties file has username and password(encrypted).

 

Regards

Venkat

 

 

From: CHO, TAKAMUNE [mailto:tc012c@...]
Sent: Thursday, May 17, 2018 1:06 PM
To: Anumaneni, Venkataramana (Nokia - US/Irving) <
venkataramana.a@...>; onap-discuss@...
Cc: Talari Nehemiah Vara, Vara (Nokia - US/Irving) <
vara.talari_nehemiah_vara@...>; Akula, Ramanjaneyul Reddy (Nokia - US/Irving) <ramanjaneyul_reddy.akula@...>
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties file

 

HI Venkat,

 

The log  says “error-message -- Unable to decrypt the password”. The user name and password should not be in the payload.

Those are supposed to update it in properties file which is appc southbound properties I mentioned before . Code will not read user id and password from payload.

 

From their payload

   "appc-provider-lcm:payload": "{\"Id\": \"$requestID\",\"PlaybookName\": \"vmmsc@playbook_linux@...\",\"NodeList\": [\"CMAN-TACO-MMSC1\" ],\"password\": \"313DECE408AF7759D442D7B06DD9A6AA\", \"Timeout\": 600, \"EnvParameters\": { \"working_dir\": \"/var/log\",\"command\": \"ls\", \"user_name\": \"root\",\"host_name\": \"mmsc\" }}"