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


Anumaneni, Venkataramana (Nokia - US/Irving)
 

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

 

 

 

 

Join onap-discuss@lists.onap.org to automatically receive all group messages.