Hi Taka, Thanks for reply. I have tried with below PD file. Still error persists. PFA the files for reference.
It seems technical issue related to json--> java object parsing.
name: vnf_name
type: null
description: null
required: null
default: null
source: "A&AI"
rule-type: vnf-name
request-keys: null
response-keys:
- unique-key-name: parent-name
unique-key-value: vnf
field-key-name: vnf-name
_________________
Thanks & Regards
Viresh N
From: CHO, TAKAMUNE [mailto:tc0...@att.com]
Sent: Saturday, October 20, 2018 01:59 AM
To: Viresh R Navalli <vn00569...@techmahindra.com>
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [appc] APPC CDT- Specifying Source as A&AI in
Parameter Definition
See below:
Taka
From: Viresh R Navalli [mailto:vn00569...@techmahindra.com]
Sent: Friday, October 19, 2018 4:21 AM
To: CHO, TAKAMUNE <tc0...@att.com<mailto:tc0...@att.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-discuss] [appc] APPC CDT- Specifying Source as A&AI in Parameter
Definition
Hi Taka,
Thanks for reply.
1. What is the expected request-key here? Is it the name of parameter we
are providing? In our case would it be like below?
request-keys:
- key-name: vnf_name
- key-value: vnf_name
We tried with this and it's same error.
Please see below correct PD file data for rule-type as vnf-name with source as
A&AI.
-
name: vnf_name
type: null
description: null
required: null
default: null
source: "A&AI"
rule-type: vnf-name
request-keys: null
response-keys:
- unique-key-name: parent-name
unique-key-value: vnf
field-key-name: vnf-name
2. We have tried to change eth source as A&AI and other ruletype it seems
that by default the request-keys are fetched as null.
Yes it will be null However the keyword "request-keys " should be present in
the PD file as shown in above example.
3. How this rule type really works? Is this rule-type represents the AAI
object and field key-name represents the actuals field name?
Yes
4. How can we specify the new ruletype and new field-key-name? Do we need
to add the data in any of the properties file or table?
We do not have to add the data in any properties file. Any other rule type
apart from the one listed below will not work
If the source = A&AI, then the following rule-types should be displayed in a
drop-down:
* vnf-name
* vm-name-list
* vnfc-name-list
* vnf-oam-ipv4-address
* vnfc-oam-ipv4-address-list
_________________
Thanks & Regards
Viresh N
From: CHO, TAKAMUNE [mailto:tc0...@att.com]
Sent: Wednesday, October 17, 2018 09:50 PM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; Viresh R
Navalli <vn00569...@techmahindra.com<mailto:vn00569...@techmahindra.com>>
Subject: RE: [onap-discuss] [appc] APPC CDT- Specifying Source as A&AI in
Parameter Definition
Viresh,
In your PD file, the request-key is missing.
-Taka
PD file:
kind: 'Property Definition'
version: V1
vnf-parameter-list:
-
name: vnf_name
type: null
description: null
required: null
default: null
source: A&AI
rule-type: vnf-name
request-keys: null
response-keys:
- unique-key-name: parent-name
unique-key-value: vnf
field-key-name: vnf-name
Taka
From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
[mailto:onap-discuss@lists.onap.org] On Behalf Of Viresh R Navalli
Sent: Wednesday, October 17, 2018 5:52 AM
To: CHO, TAKAMUNE <tc0...@att.com<mailto:tc0...@att.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-discuss] [appc] APPC CDT- Specifying Source as A&AI in Parameter
Definition
Hi Taka,
On further investigation of specifying Source as A&AI in Parameter Definition,
we observed below result while running configure action from appc swagger. We
tried to use the rule-type as 'vnf-name' and response-keys (unique-key-name:
parent-name, unique-key-value: vnf, field-key-name: vnf-name)
Please find attached PD file, payload and logs-
2018-10-17 08:20:36,981 | ERROR | ppc-dispatcher-7 | InstarClientNode
| 409 - appc-common - 1.3.0 - SvcLogicGraph [module=APPC,
rpc=ProcessParameterDefinition, mode=sync, version=4.0.0,
md5sum=fc75493451a1d5a7e9b3eece1dfa19eb] - 1 (block) | Failed processing AAI
data
com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized
field "rule-type" (class org.onap.sdnc.config.params.data.Parameter), not
marked as ignorable (9 known properties: "requestKeys", "name", "defaultValue",
"responseKeys", "ruleType", "type", "source", "description", "required"])
at [Source:
java.io.StringReader@450691af<mailto:java.io.StringReader@450691af>; line: 1,
column: 105] (through reference chain:
org.onap.sdnc.config.params.data.Parameter["rule-type"])
Queries are-
1. Do we need to upload the key file for parameters with A&AI as source?
From wiki it seems that it is only required if the source is other than A&AI.
2. How this rule type really works? Is this rule-type represents the AAI
object and field key-name represents the actuals field name?
3. How can we specify the new ruletype and new field-key-name? Do we need
to add the data in any of the properties file or table?
4. Can someone validate if the attached PD file in the right format or
any missing attributes?
_________________
Thanks & Regards
Viresh N
From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
[mailto:onap-discuss@lists.onap.org] On Behalf Of Chandra
Sent: Friday, October 12, 2018 07:55 PM
To: CHO, TAKAMUNE <tc0...@att.com<mailto:tc0...@att.com>>;
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] [appc] APPC CDT- Specifying Source as A&AI in
Parameter Definition
Thanks Taka for your response. We will investigate the error again and if
needed we will post it in community.
From: CHO, TAKAMUNE [mailto:tc0...@att.com]
Sent: 12 October 2018 19:49
To: Chandrashekhar Thakare
<ct00548...@techmahindra.com<mailto:ct00548...@techmahindra.com>>;
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: [appc] APPC CDT- Specifying Source as A&AI in Parameter Definition
Yes. Those Configure actions are nothing changing in Casablanca. Thus should be
in Beijing.
Taka
From: Chandrashekhar Thakare [mailto:ct00548...@techmahindra.com]
Sent: Friday, October 12, 2018 10:16 AM
To: CHO, TAKAMUNE <tc0...@att.com<mailto:tc0...@att.com>>;
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: [appc] APPC CDT- Specifying Source as A&AI in Parameter Definition
Hi Taka,
Do you mean that source as A&AI is supported in Beijing?
From: CHO, TAKAMUNE [mailto:tc0...@att.com]
Sent: 12 October 2018 19:42
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>;
Chandrashekhar Thakare
<ct00548...@techmahindra.com<mailto:ct00548...@techmahindra.com>>
Subject: RE: [appc] APPC CDT- Specifying Source as A&AI in Parameter Definition
Hi
Please see my answer below.
Taka
From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
[mailto:onap-discuss@lists.onap.org] On Behalf Of Chandra
Sent: Friday, October 12, 2018 6:55 AM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-discuss] [appc] APPC CDT- Specifying Source as A&AI in Parameter
Definition
Hi,
We are trying to upload the parameter definitions from CDT and trying to
specify the source as A&AI. If we specify the source as A&AI; the values
should be fetched from A&AI while preparing the config templates and APPC does
not expect these values in the Configure/ConfigScaleout request. However we
are getting errors while executing the configure request.
I was checking demo Videos of CDT and it seems that specifying source as A&AI
,not available in Beijing and APPC always expects these values from SO. Queries
are-
1. Can you please confirm if source as A&AI is not supported for
Configure, ConfigScaleout, ModifyConfig? Or specifically it is not supported
only for ConfigScaleout?
[Taka] Source as A&AI is supported for all Configure related actions
2. Could you please confirm if this functionality included in Casablanca
release?
[Taka] Yes
Regards
Chandrashekhar
============================================================================================================================
Disclaimer: This message and the information contained herein is proprietary
and confidential and subject to the Tech Mahindra policy statement, you may
review the policy at
http://www.techmahindra.com/Disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_Disclaimer.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2SpRaOlaUglzr4dgoYaSsJQHU3X5g6PDPy8-4kdLndM&m=-CdBI-vpdx07W7pwvm_wE4dXY5cERPVfc0kUc3DJM5Q&s=9yRRwSWqGI24M9VrzcwmHFApHDFTcbTOzJHziuiRiz4&e=>
externally
http://tim.techmahindra.com/tim/disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__tim.techmahindra.com_tim_disclaimer.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2SpRaOlaUglzr4dgoYaSsJQHU3X5g6PDPy8-4kdLndM&m=-CdBI-vpdx07W7pwvm_wE4dXY5cERPVfc0kUc3DJM5Q&s=-c6DtM23ABCVeL_byUHZqjSwECvkR2bBqU7nO7cEeD4&e=>
internally within TechMahindra.
============================================================================================================================
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13166): https://lists.onap.org/g/onap-discuss/message/13166
Mute This Topic: https://lists.onap.org/mt/27268933/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
reference_AllAction_vLoadBalancer_vLoadBalancer-test0_0.0.1V.JSON
Description: reference_AllAction_vLoadBalancer_vLoadBalancer-test0_0.0.1V.JSON
pd_Configure_vLoadBalancer_vLoadBalancer-test0_0.0.1V.YAML
Description: pd_Configure_vLoadBalancer_vLoadBalancer-test0_0.0.1V.YAML
template_Configure_vLoadBalancer_vLoadBalancer-test0_0.0.1V.JSON
Description: template_Configure_vLoadBalancer_vLoadBalancer-test0_0.0.1V.JSON
{
"appc-provider-lcm:input": {
"appc-provider-lcm:common-header": {
"appc-provider-lcm:timestamp": "2018-10-22T07:22:05.97Z" ,
"appc-provider-lcm:api-ver": "2.00",
"appc-provider-lcm:originator-id": "VyOS_22102018_06",
"appc-provider-lcm:request-id": "VyOS_request-id_22102018_06",
"appc-provider-lcm:sub-request-id": "VyOS_subrequest-id_22102018_06",
"appc-provider-lcm:flags": {
"appc-provider-lcm:mode": "EXCLUSIVE",
"appc-provider-lcm:force": "TRUE",
"appc-provider-lcm:ttl": "0"
}
},
"appc-provider-lcm:action": "Configure",
"appc-provider-lcm:action-identifiers": {
"appc-provider-lcm:vnf-id": "APPC-test-vLB"
},
"appc-provider-lcm:payload":
"{\"request-parameters\":{\"vnf-id\":\"APPC-test-vLB\"},\"configuration-parameters\":{\"intr_name\":\"eth0\"}}"
}
}
