date:20181012

Re: [onap-discuss] [ONAP Helpdesk #62098] Issue on Failed to pull image from ONAP Nexus 3

2018-10-12 Thread Jennie Jia

Hi Jessica,

I was able to deploy SDC and portal yesterday.. thank you so much!

Jennie

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Friday, October 12, 2018 4:52 PM
Cc: Jennie Jia ; onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #62098] Issue on Failed to pull image from ONAP Nexus 3

Dear Jennie, 

Can you please check if you still have this issue?

We have restarted the server since and expecting things to be better. 

Thanks so much!
Jess

On Wed Oct 10 22:11:18 2018, jennie@amdocs.com wrote:
> Hi All,
> 
> This issue happened since yesterday. I have not seen a fix yet. I also 
> CC to helpdesk.
> 
> I cloned the latest oom,  and I am trying to deploy the SDC and SDC 
> UI.
> 
> root@jen-vm1:/home/ubuntu/oom/kubernetes/sdc# kubectl get pods --all- 
> namespaces
> NAMESPACE NAME READY
> STATUS RESTARTS   AGE
> kube-system   heapster-76b8cd7b5-hrd69 1/1
> Running2  111d
> kube-system   kube-dns-5d7b4487c9-dcng73/3
> Running6  111d
> kube-system   kubernetes-dashboard-f9577fffd-lz9lf 1/1
> Running3  111d
> kube-system   monitoring-grafana-997796fcf-ddmcp   1/1
> Running2  111d
> kube-system   monitoring-influxdb-56fdcd96b-648z4  1/1
> Running2  111d
> kube-system   tiller-deploy-7f7d4b5967-q5twt   1/1
> Running0  1d
> onap  dev-sdc-be-867985dddf-f44dn  0/2
> Init:0/2   0  1m
> onap  dev-sdc-be-config-backend-gc4dx  0/1
> Init:0/1   0  1m
> onap  dev-sdc-cs-5f8b655b4f-clsx6  0/1
> ImagePullBackOff   0  1m
> onap  dev-sdc-cs-config-cassandra-czdtl0/1
> Init:0/1   0  1m
> onap  dev-sdc-es-67bd554cc5-ttqqk  0/1
> ImagePullBackOff   0  1m
> onap  dev-sdc-es-config-elasticsearch-292vh0/1
> Init:0/1   0  1m
> onap  dev-sdc-fe-f7dbc6fb8-fn44r   0/2
> Init:0/2   0  1m
> onap  dev-sdc-kb-854f96658-9lp7l   0/1
> Init:0/1   0  1m
> onap  dev-sdc-onboarding-be-596c554bfd-4hh6f   0/2
> Init:0/1   0  1m
> onap  dev-sdc-onboarding-be-cassandra-init-c6czt   0/1
> Init:0/1   0  1m
> onap  dev-sdc-wfd-be-5b5c9fdf94-ph62l  0/1
> Init:0/1   0  1m
> onap  dev-sdc-wfd-be-workflow-init-znbg4   0/1
> Init:0/1   0  1m
> onap  dev-sdc-wfd-fe-55dc64bbc7-w756w  0/2
> Init:0/1   0  1m
> 
> # kubectl describe pods dev-sdc-cs-5f8b655b4f-clsx6 -n onap
> Name:   dev-sdc-cs-5f8b655b4f-clsx6
> Namespace:  onap
> Node:   jen-vm1/10.69.100.143
> Start Time: Thu, 11 Oct 2018 01:45:43 +
> Labels: app=sdc-cs
> pod-template-hash=1946211609
> release=dev
> Annotations:kubernetes.io/created-
> by={"kind":"SerializedReference","apiVersion":"v1","reference":{"kind"
> :"ReplicaSet","namespace":"onap","name":"dev-
> sdc-cs-5f8b655b4f","uid":"5d7773dc-ccf7-11e8-a3d1-021bcc6bfe00"...
> Status: Pending
> IP: 10.42.179.195
> Controlled By:  ReplicaSet/dev-sdc-cs-5f8b655b4f
> Containers:
>   sdc-cs:
> Container ID:
>Image:  nexus3.onap.org:10001/onap/sdc-cassandra:1.3-
> STAGING-latest
> Image ID:
> Ports:  9160/TCP, 9042/TCP
> Host Ports: 0/TCP, 0/TCP
> State:  Waiting
>   Reason:   ImagePullBackOff
> Ready:  False
> Restart Count:  0
> Limits:
>   cpu: 1
>   memory:  4Gi
> Requests:
>   cpu:  10m
>   memory:   1Gi
> Liveness:   tcp-socket :9160 delay=60s timeout=1s period=10s
> #success=1 #failure=3
> Readiness:  exec [/var/lib/ready-probe.sh] delay=60s timeout=1s 
> period=10s #success=1 #failure=3
> Environment:
>   ENVNAME:AUTO
>   RELEASE:latest
>   MAX_HEAP_SIZE:  1536M
>   HEAP_NEWSIZE:   512M
>   HOST_IP: (v1:status.podIP)
>   CS_PASSWORD: sdc-cs-secrets'>  Optional: false
> Mounts:
>   /etc/localtime from dev-sdc-cs-localtime (ro)
>   /root/chef-solo/environments/ from dev-sdc-cs-environments (rw)
>   /var/lib/cassandra/ from dev-sdc-cs-data (rw)
>   /var/run/secrets/kubernetes.io/serviceaccount from default- 
> token-wbz5r (ro)
> Conditions:
>   Type   Status
>   InitializedTrue
>   Ready  False
>   PodScheduled   True
> Volumes:
>   dev-sdc-cs-localtime:
> Type:  HostPath (bare host directory volume)
> Path:  /etc/localtime
> HostPathType:
>   dev-sdc-cs-data:
>

Re: [onap-discuss] [SO] Heat template from yaml string to json for SO multicloud adapter

2018-10-12 Thread Multanen, Eric W

Ok great – doesn’t look like I missed anything.  Thanks Steve!

From: SMOKOWSKI, STEVEN [mailto:ss8...@att.com]
Sent: Friday, October 12, 2018 12:57 PM
To: Multanen, Eric W ; onap-discuss@lists.onap.org
Subject: Re: [SO] Heat template from yaml string to json for SO multicloud 
adapter

Question 1:  Does the current SO Openstack adapter convert this Yaml  
“template” string to JSON at some point before it gets sent?  If it does, I 
haven’t been able to spot where that happens yet.
Nope

The second (related) issue is the “environment” attribute is also a string 
containing the contents of the heat env file.  I understand that multicloud 
would like to see this json attributes in the “parameters” list.
We would have to code that.

Question 2: Again, does the current SO Openstack adapter do any conversion on 
the “environment” attribute, or does it get sent ‘as is’?
Sent as is, best I can recall.

Questioin 3:  To summarize – is there current code in SO to do what I’m trying 
to do?  Or, does the current SO Openstack adapter just send the heat template 
and environment to Openstack as strings?
 I know we the intel folks are working on building in a multi-cloud plugin to 
the adapter.  Please reach out ot them, it looks like we will support it soon.

Thanks

-Steve

From: "Multanen, Eric W" 
mailto:eric.w.multa...@intel.com>>
Date: Friday, October 12, 2018 at 3:54 PM
To: "SMOKOWSKI, STEVEN" mailto:ss8...@att.com>>, 
"onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>
Subject: [SO] Heat template from yaml string to json for SO multicloud adapter

Hi SO experts,

For the Openstack multicloud adapter we’re working on in SO, a CreateStackParam 
object is
created from the inputs and included in the “template_data” part of the 
multicloud infra request body to create a vfModule.

That looks something like this:

   “template_data” : {
  “template”: “  “,
  “stack_name”: “vfw”,
  “parameters”: {
 “vnf_id”: “”
  },
  “environment”: “  
“,
   etc.

The issue right now is that the multicloud side would like to get the 
“template” attributes in JSON format – instead of as a Yaml string.
   E.g. something like:
"template": {
"heat_template_version": "2015-10-15",
“description": "Simple template to test heat commands",
"parameters": {

}
   Instead of:
"template": 
"##\n#\n#==LICENSE_START==\n#\n#\n#
 Copyright < rest of the heat template file > “,

Question 1:  Does the current SO Openstack adapter convert this Yaml  
“template” string to JSON at some point before it gets sent?  If it does, I 
haven’t been able to spot where that happens yet.

The second (related) issue is the “environment” attribute is also a string 
containing the contents of the heat env file.  I understand that multicloud 
would like to see this json attributes in the “parameters” list.

Question 2: Again, does the current SO Openstack adapter do any conversion on 
the “environment” attribute, or does it get sent ‘as is’?

Questioin 3:  To summarize – is there current code in SO to do what I’m trying 
to do?  Or, does the current SO Openstack adapter just send the heat template 
and environment to Openstack as strings?

Thanks,
Eric

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

View/Reply Online (#12994): https://lists.onap.org/g/onap-discuss/message/12994
Mute This Topic: https://lists.onap.org/mt/27276320/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] onap-sdnc-ansible-server cannot launch

2018-10-12 Thread Brian

The 1.4-STAGING-latest and update to the command line (ansible  moved from sdnc 
to ccsdk in Casablanca) worked for me in an Beijing instance as well.

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

View/Reply Online (#12993): https://lists.onap.org/g/onap-discuss/message/12993
Mute This Topic: https://lists.onap.org/mt/25510544/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [SO] Heat template from yaml string to json for SO multicloud adapter

2018-10-12 Thread Steve Smokowski

Question 1:  Does the current SO Openstack adapter convert this Yaml  
“template” string to JSON at some point before it gets sent?  If it does, I 
haven’t been able to spot where that happens yet.
Nope

The second (related) issue is the “environment” attribute is also a string 
containing the contents of the heat env file.  I understand that multicloud 
would like to see this json attributes in the “parameters” list.
We would have to code that.

Question 2: Again, does the current SO Openstack adapter do any conversion on 
the “environment” attribute, or does it get sent ‘as is’?
Sent as is, best I can recall.

Questioin 3:  To summarize – is there current code in SO to do what I’m trying 
to do?  Or, does the current SO Openstack adapter just send the heat template 
and environment to Openstack as strings?
 I know we the intel folks are working on building in a multi-cloud plugin to 
the adapter.  Please reach out ot them, it looks like we will support it soon.


Thanks

-Steve


From: "Multanen, Eric W" 
Date: Friday, October 12, 2018 at 3:54 PM
To: "SMOKOWSKI, STEVEN" , "onap-discuss@lists.onap.org" 

Subject: [SO] Heat template from yaml string to json for SO multicloud adapter

Hi SO experts,

For the Openstack multicloud adapter we’re working on in SO, a CreateStackParam 
object is
created from the inputs and included in the “template_data” part of the 
multicloud infra request body to create a vfModule.

That looks something like this:

   “template_data” : {
  “template”: “  “,
  “stack_name”: “vfw”,
  “parameters”: {
 “vnf_id”: “”
  },
  “environment”: “  
“,
   etc.

The issue right now is that the multicloud side would like to get the 
“template” attributes in JSON format – instead of as a Yaml string.
   E.g. something like:
"template": {
"heat_template_version": "2015-10-15",
“description": "Simple template to test heat commands",
"parameters": {

}
   Instead of:
"template": 
"##\n#\n#==LICENSE_START==\n#\n#\n#
 Copyright < rest of the heat template file > “,

Question 1:  Does the current SO Openstack adapter convert this Yaml  
“template” string to JSON at some point before it gets sent?  If it does, I 
haven’t been able to spot where that happens yet.

The second (related) issue is the “environment” attribute is also a string 
containing the contents of the heat env file.  I understand that multicloud 
would like to see this json attributes in the “parameters” list.

Question 2: Again, does the current SO Openstack adapter do any conversion on 
the “environment” attribute, or does it get sent ‘as is’?

Questioin 3:  To summarize – is there current code in SO to do what I’m trying 
to do?  Or, does the current SO Openstack adapter just send the heat template 
and environment to Openstack as strings?


Thanks,
Eric




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

View/Reply Online (#12992): https://lists.onap.org/g/onap-discuss/message/12992
Mute This Topic: https://lists.onap.org/mt/27276320/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-discuss] [SO] Heat template from yaml string to json for SO multicloud adapter

2018-10-12 Thread Multanen, Eric W

Hi SO experts,

For the Openstack multicloud adapter we're working on in SO, a CreateStackParam 
object is
created from the inputs and included in the "template_data" part of the 
multicloud infra request body to create a vfModule.

That looks something like this:

   "template_data" : {
  "template": "  ",
  "stack_name": "vfw",
  "parameters": {
 "vnf_id": ""
  },
  "environment": "  
",
   etc.

The issue right now is that the multicloud side would like to get the 
"template" attributes in JSON format - instead of as a Yaml string.
   E.g. something like:
"template": {
"heat_template_version": "2015-10-15",
"description": "Simple template to test heat commands",
"parameters": {

}
   Instead of:
"template": 
"##\n#\n#==LICENSE_START==\n#\n#\n#
 Copyright < rest of the heat template file > ",

Question 1:  Does the current SO Openstack adapter convert this Yaml  
"template" string to JSON at some point before it gets sent?  If it does, I 
haven't been able to spot where that happens yet.

The second (related) issue is the "environment" attribute is also a string 
containing the contents of the heat env file.  I understand that multicloud 
would like to see this json attributes in the "parameters" list.

Question 2: Again, does the current SO Openstack adapter do any conversion on 
the "environment" attribute, or does it get sent 'as is'?

Questioin 3:  To summarize - is there current code in SO to do what I'm trying 
to do?  Or, does the current SO Openstack adapter just send the heat template 
and environment to Openstack as strings?


Thanks,
Eric




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

View/Reply Online (#12991): https://lists.onap.org/g/onap-discuss/message/12991
Mute This Topic: https://lists.onap.org/mt/27276320/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [onap-tsc-vote] [onap-tsc] [TSC] Request API change waiver between SO and SDNC

2018-10-12 Thread Srini

+1 (on API change)

Thanks
Srini

From: onap-tsc-v...@lists.onap.org [mailto:onap-tsc-v...@lists.onap.org] On 
Behalf Of Catherine LEFEVRE
Sent: Friday, October 12, 2018 3:41 AM
To: onap-...@lists.onap.org; onap-tsc-v...@lists.onap.org
Cc: onap-discuss ; Seshu m 
; TIMONEY, DAN 
Subject: Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change waiver between 
SO and SDNC
Importance: High

Good morning Alexis,

Thank you for your leadership supporting the teams to progress quickly on this 
issue.
I am adding the TSC vote distro list in order to increase the visibility of 
this request.

TSC Members (or proxy)
Please vote (+1 waiver approved, 0-neutral, -1 waiver not approved) no later 
than Oct 13th End of your Day.
·Andreas Geissler (DT)
·Ranny Haiby, Nokia
·David Sauvageau, Bell Canada
·Chaker Al-Hakim, Huawei
·+1  Catherine Lefevre, AT&T
·Eric Debeau, Orange
·Jason Hunt, IBM
·Srinivasa Addepalli, Intel
·Murat Turpcu,turk telekom
·Ning So, Reliance Jio
·Lingli Deng, CMCC
·Alla Goldner, Amdocs
·Bin Yang, Wind River
·Milind Jalwadi,, TechMahindra
·Stephen Terrill, Ericsson
·Susana Sabater, Vodafone
·Viswa, Verizon
·Yan Chen, China Telecom
Many thanks & regards
Catherine

From: onap-...@lists.onap.org 
[mailto:onap-...@lists.onap.org] On Behalf Of Alexis de Talhouet
Sent: Friday, October 12, 2018 4:59 AM
To: onap-tsc; onap-discuss
Cc: Seshu m; TIMONEY, DAN
Subject: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

Hello TSC,

As discussed during today’s meeting, an issue has been identified in the new SO 
building block, introducing a regression in term of functionality from previous 
release.
PTLs from both projects acknowledge and agree with the required changes.

Expected behaviour:
Have the cloud owner / cloud region being retrievable from static configuration 
file.

Current behaviour:
Cloud owner is hardcoded in the code, with no way to change it using config 
file.

API change requested:
SDN-C: GENERIC-RESOURCE-API.yang

Impact:
This API change will allow SO to resolve the cloud owner from the config file 
(similar to what we had in previous release), and to be able to use it with the 
GR-API.

Patches:
SO:
1.  Use a property instead of hard coded value. (TBD)
2.  Push the changeset to allow it to be set on the north-bound 
api.  (TBD)
SDNC:
1 Add cloud-owner definition: 
.https://gerrit.onap.org/r/#/c/67413/

Regards,
Alexis

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

View/Reply Online (#12990): https://lists.onap.org/g/onap-discuss/message/12990
Mute This Topic: https://lists.onap.org/mt/27271290/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [appc] APPC CDT- Specifying Source as A&AI in Parameter Definition

2018-10-12 Thread Chandra

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 ; 
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 mailto:tc0...@att.com>>; 
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; 
Chandrashekhar Thakare 
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] On Behalf Of Chandra
Sent: Friday, October 12, 2018 6:55 AM
To: 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
 externally 
http://tim.techmahindra.com/tim/disclaimer.html
 internally within TechMahindra.

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

View/Reply Online (#12989): https://lists.onap.org/g/onap-discuss/message/12989
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]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [appc] APPC CDT- Specifying Source as A&AI in Parameter Definition

2018-10-12 Thread Chandra

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; Chandrashekhar Thakare 

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] On Behalf Of Chandra
Sent: Friday, October 12, 2018 6:55 AM
To: 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
 externally 
http://tim.techmahindra.com/tim/disclaimer.html
 internally within TechMahindra.

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

View/Reply Online (#12988): https://lists.onap.org/g/onap-discuss/message/12988
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]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [External]Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change waiver between SO and SDNC

2018-10-12 Thread Alexis de Talhouet

+1 from me, obviously :)  - Proxy for David Sauvageau

> On Oct 12, 2018, at 8:34 AM, Ning So  wrote:
> 
> ＋1.
> 
> Ning So
> 
> 
>  Original Message 
> Subject: [External]Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change 
> waiver between SO and SDNC
> From: Catherine LEFEVRE  >
> Date: Oct 12, 2018, 5:43 AM
> To: onap-...@lists.onap.org 
> ,onap-tsc-v...@lists.onap.org 
> 
> The e-mail below is from an external source. Please do not open attachments 
> or click links from an unknown or suspicious origin.
> 
> 
> Good morning Alexis,
>
> Thank you for your leadership supporting the teams to progress quickly on 
> this issue.
> I am adding the TSC vote distro list in order to increase the visibility of 
> this request.
>
> TSC Members (or proxy)
> Please vote (+1 waiver approved, 0-neutral, -1 waiver not approved) no later 
> than Oct 13th End of your Day.
> ·Andreas Geissler (DT)
> ·Ranny Haiby, Nokia
> ·David Sauvageau, Bell Canada
> ·Chaker Al-Hakim, Huawei
> ·+1  Catherine Lefevre, AT&T   
> ·Eric Debeau, Orange
> ·Jason Hunt, IBM
> ·Srinivasa Addepalli, Intel
> ·Murat Turpcu,turk telekom
> ·Ning So, Reliance Jio
> ·Lingli Deng, CMCC
> ·Alla Goldner, Amdocs
> ·Bin Yang, Wind River
> ·Milind Jalwadi,, TechMahindra
> ·Stephen Terrill, Ericsson
> ·Susana Sabater, Vodafone
> ·Viswa, Verizon
> ·Yan Chen, China Telecom
> Many thanks & regards
> Catherine
>
> From: onap-...@lists.onap.org  
> [mailto:onap-...@lists.onap.org ] On Behalf 
> Of Alexis de Talhouet
> Sent: Friday, October 12, 2018 4:59 AM
> To: onap-tsc; onap-discuss
> Cc: Seshu m; TIMONEY, DAN
> Subject: [onap-tsc] [TSC] Request API change waiver between SO and SDNC
>
> Hello TSC,
>
> As discussed during today’s meeting, an issue has been identified in the new 
> SO building block, introducing a regression in term of functionality from 
> previous release.
> PTLs from both projects acknowledge and agree with the required changes.
>
> Expected behaviour:
> Have the cloud owner / cloud region being retrievable from static 
> configuration file.
>
> Current behaviour:
> Cloud owner is hardcoded in the code, with no way to change it using config 
> file.
>
> API change requested:
> SDN-C: GENERIC-RESOURCE-API.yang
>
> Impact:
> This API change will allow SO to resolve the cloud owner from the config file 
> (similar to what we had in previous release), and to be able to use it with 
> the GR-API.
>
> Patches:
> SO:
> 1.  Use a property instead of hard coded value. (TBD)
> 2.  Push the changeset to allow it to be set on the north-bound 
> api.  (TBD)
> SDNC: 
> 1 Add cloud-owner definition: 
> .https://gerrit.onap.org/r/#/c/67413/ 
> 
>
> Regards,
> Alexis
> 
> "Confidentiality Warning: This message and any attachments are intended only 
> for the use of the intended recipient(s), are confidential and may be 
> privileged. If you are not the intended recipient, you are hereby notified 
> that any review, re-transmission, conversion to hard copy, copying, 
> circulation or other use of this message and any attachments is strictly 
> prohibited. If you are not the intended recipient, please notify the sender 
> immediately by return email and delete this message and any attachments from 
> your system.
> 
> Virus Warning: Although the company has taken reasonable precautions to 
> ensure no viruses are present in this email. The company cannot accept 
> responsibility for any loss or damage arising from the use of this email or 
> attachment."
> 
> 


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

View/Reply Online (#12987): https://lists.onap.org/g/onap-discuss/message/12987
Mute This Topic: https://lists.onap.org/mt/27269786/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] vFW demo-VES integration #integration

2018-10-12 Thread Jing Wang

Sure, thanks!

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

View/Reply Online (#12986): https://lists.onap.org/g/onap-discuss/message/12986
Mute This Topic: https://lists.onap.org/mt/27260346/21656
Mute #integration: https://lists.onap.org/mk?hashtag=integration&subid=2740164
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] vFW demo-VES integration #integration

2018-10-12 Thread Marco Platania

Thanks Jing,

I didn’t see that problem before, it seemed to run fine, but I’ll investigate 
more.

Marco

From:  on behalf of Jing Wang 

Reply-To: "onap-discuss@lists.onap.org" , 
"jing.wa...@huawei.com" 
Date: Friday, October 12, 2018 at 8:59 AM
To: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] vFW demo-VES integration #integration

Yes. The latest in the demo repo under VES5.0


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

View/Reply Online (#12985): https://lists.onap.org/g/onap-discuss/message/12985
Mute This Topic: https://lists.onap.org/mt/27260346/21656
Mute #integration: https://lists.onap.org/mk?hashtag=integration&subid=2740164
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] vFW demo-VES integration #integration

2018-10-12 Thread Jing Wang

Yes. The latest in the demo repo under VES5.0

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

View/Reply Online (#12984): https://lists.onap.org/g/onap-discuss/message/12984
Mute This Topic: https://lists.onap.org/mt/27260346/21656
Mute #integration: https://lists.onap.org/mk?hashtag=integration&subid=2740164
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [SO] Create/Activate BB NPE

2018-10-12 Thread Steve Smokowski

The current payload you have in yellow is correct.  Vid still states each 
resource, we can decide if that is worth tweaking and doing a look up in SO or 
not.

Thanks

-Steve


From: Alexis de Talhouët 
Date: Thursday, October 11, 2018 at 7:04 PM
To: "MALAKOV, YURIY" 
Cc: "onap-discuss@lists.onap.org" , "SMOKOWSKI, 
STEVEN" , "ZITELLA, MICHAEL V" , "DORKING, 
KEITH" 
Subject: Re: [onap-discuss] [SO] Create/Activate BB NPE

Steve, here is the bug 
https://jira.onap.org/browse/SO-1130
Yuriy, you have to empty all the userParams section. I tested this already, and 
it’s working. I mean I’m failing later in the game, but I’m passing that 
specific error.



On Oct 11, 2018, at 6:53 PM, MALAKOV, YURIY 
mailto:ym9...@att.com>> wrote:
Steve,
It may be an issue with the payload request for create and activate.

I’m not expecting the create-activate BB to have the user parameters being 
passed from VID b/c all the assignment are completed in previous flow.

Can you confirm if this is a valid payload request.

Request-activate---current

Should Be???

POST 
/onap/so/infra/serviceInstantiation/v7/serviceInstances/a644aad7-fbc3-4252-b732-bb2bcc86fde6/activate
 HTTP/1.1
Host: 10.195.197.73
Content-Type: application/json
Accept: application/json
X-FromAppId: Postman
X-TransactionId: postman-123
{
  "requestDetails": {
"subscriberInfo": {
  "globalSubscriberId": "Demonstration"
},
"requestInfo": {
  "suppressRollback": true,
  "productFamilyId": "a9a77d5a-123e-4ca2-9eb9-0b015d2ee0fb",
  "requestorId": "adt",
  "instanceName": "test-1234",
  "source": "VID"
},
"requestParameters": {
  "subscriptionServiceType": "vFW",
  "userParams": [
{
  "service": {
"instanceParams": [

],
"instanceName": "Service_E2E_vFW",
"resources": {
  "vnfs": [
{
  "modelInfo": {
"modelName": "d26a74bc-3fdb-4fd2-ad55",
"modelVersionId": "69a7d967-fe68-49d2-ad6b-fc40f5f5b31c",
"modelInvariantUuid": 
"c397d40f-cd2a-4b19-add6-e12ea9ecf4ab",
"modelVersion": "2.0",
"modelCustomizationId": 
"2cc242bc-ff38-4bac-9650-5fe1b54f5aeb",
"modelInstanceName": "d26a74bc-3fdb-4fd2-ad55 0"
  },
  "cloudConfiguration": {
"lcpCloudRegionId": "RegionOne",
"tenantId": "demo"
  },
  "platform": {
"platformName": "test"
  },
  "lineOfBusiness": {
"lineOfBusinessName": "someValue"
  },
  "productFamilyId": "a9a77d5a-123e-4ca2-9eb9-0b015d2ee0fb",
  "instanceName": "vFirewall 0",
  "instanceParams": [
  ],
  "vfModules": [
{
  "modelInfo": {
"modelName": 
"D26a74bc3fdb4fd2Ad55..base_template..module-0",
"modelVersionId": 
"e3c095c3-a620-4828-a689-7132936b90ff",
"modelInvariantUuid": 
"ac36a6de-0f92-4ee2-8b39-1b0dba0058f5",
"modelVersion": "1",
"modelCustomizationId": 
"1f8ff6cf-640b-432f-9dec-1352b7e1f862"
  },
  "instanceName": 
"vfirewall0..Vfirewall..base_template..module-0",
  "instanceParams": [
{

}
  ]
},
{
  "modelInfo": {
"modelName": "D26a74bc3fdb4fd2Ad55..vfw..module-3",
"modelVersionId": 
"086223d6-352c-47d3-abb4-213711fc5188",
"modelInvariantUuid": 
"d9e4a4e0-c0d3-4bd3-89cc-c6b95af29f6d",
"modelVersion": "1",
"modelCustomizationId": 
"a6751179-1762-4771-8ccb-541516c53cf2"
  },
  "instanceName": "vfirewall0..Vfirewall..vfw..module-0",
  "instanceParams": [
{

}
  ]
},
{
  "modelInfo": {
"modelName": "D26a74bc3fdb4fd2Ad55..vpg..module-2",
"modelVersionId": 
"6a18492b-4c9d-47a5-a8eb-34b085db0eb0",
"modelInvariantUuid": 
"74d0a390-c76f-42fd-ae5d-dc9bea9b79a5",
"modelVersion": "1",
"modelCustomizationId": 
"a505c501-0264-4835-8

Re: [onap-discuss] [External]Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change waiver between SO and SDNC

2018-10-12 Thread Ning So

＋1.

Ning So

 Original Message 
Subject: [External]Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change 
waiver between SO and SDNC
From: Catherine LEFEVRE 
Date: Oct 12, 2018, 5:43 AM
To: onap-...@lists.onap.org,onap-tsc-v...@lists.onap.org

The e-mail below is from an external source. Please do not open attachments or 
click links from an unknown or suspicious origin.

Good morning Alexis,

Thank you for your leadership supporting the teams to progress quickly on this 
issue.
I am adding the TSC vote distro list in order to increase the visibility of 
this request.

TSC Members (or proxy)
Please vote (+1 waiver approved, 0-neutral, -1 waiver not approved) no later 
than Oct 13th End of your Day.
*Andreas Geissler (DT)
*Ranny Haiby, Nokia
*David Sauvageau, Bell Canada
*Chaker Al-Hakim, Huawei
*+1  Catherine Lefevre, AT&T
*Eric Debeau, Orange
*Jason Hunt, IBM
*Srinivasa Addepalli, Intel
*Murat Turpcu,turk telekom
*Ning So, Reliance Jio
*Lingli Deng, CMCC
*Alla Goldner, Amdocs
*Bin Yang, Wind River
*Milind Jalwadi,, TechMahindra
*Stephen Terrill, Ericsson
*Susana Sabater, Vodafone
*Viswa, Verizon
*Yan Chen, China Telecom
Many thanks & regards
Catherine

From: onap-...@lists.onap.org 
[mailto:onap-...@lists.onap.org] On Behalf Of Alexis de Talhouet
Sent: Friday, October 12, 2018 4:59 AM
To: onap-tsc; onap-discuss
Cc: Seshu m; TIMONEY, DAN
Subject: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

Hello TSC,

As discussed during today’s meeting, an issue has been identified in the new SO 
building block, introducing a regression in term of functionality from previous 
release.
PTLs from both projects acknowledge and agree with the required changes.

Expected behaviour:
Have the cloud owner / cloud region being retrievable from static configuration 
file.

Current behaviour:
Cloud owner is hardcoded in the code, with no way to change it using config 
file.

API change requested:
SDN-C: GENERIC-RESOURCE-API.yang

Impact:
This API change will allow SO to resolve the cloud owner from the config file 
(similar to what we had in previous release), and to be able to use it with the 
GR-API.

Patches:
SO:
1.  Use a property instead of hard coded value. (TBD)
2.  Push the changeset to allow it to be set on the north-bound 
api.  (TBD)
SDNC:
1 Add cloud-owner definition: 
.https://gerrit.onap.org/r/#/c/67413/

Regards,
Alexis

"Confidentiality Warning: This message and any attachments are intended only 
for the use of the intended recipient(s). 
are confidential and may be privileged. If you are not the intended recipient. 
you are hereby notified that any 
review. re-transmission. conversion to hard copy. copying. circulation or other 
use of this message and any attachments is 
strictly prohibited. If you are not the intended recipient. please notify the 
sender immediately by return email. 
and delete this message and any attachments from your system.

Virus Warning: Although the company has taken reasonable precautions to ensure 
no viruses are present in this email. 
The company cannot accept responsibility for any loss or damage arising from 
the use of this email or attachment."

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

View/Reply Online (#12982): https://lists.onap.org/g/onap-discuss/message/12982
Mute This Topic: https://lists.onap.org/mt/27269786/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [E] Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change waiver between SO and SDNC

2018-10-12 Thread Viswanath Kumar Skand Priya via Lists.Onap.Org

+1 for API Waiver.



Viswanath Kumar Skand Priya
Senior Architect
Technology, Architecture & Planning



On Fri, Oct 12, 2018 at 4:10 PM Catherine LEFEVRE <
catherine.lefe...@intl.att.com> wrote:

> Good morning Alexis,
>
>
>
> Thank you for your leadership supporting the teams to progress quickly on
> this issue.
>
> I am adding the TSC vote distro list in order to increase the visibility
> of this request.
>
>
>
> TSC Members (or proxy)
>
> Please vote (+1 waiver approved, 0-neutral, -1 waiver not approved) no
> later than *Oct 13th End of your Day*.
>
> ·Andreas Geissler (DT)
>
> ·Ranny Haiby, Nokia
>
> ·David Sauvageau, Bell Canada
>
> ·Chaker Al-Hakim, Huawei
>
> ·+1  Catherine Lefevre, AT&T
>
> ·Eric Debeau, Orange
>
> ·Jason Hunt, IBM
>
> ·Srinivasa Addepalli, Intel
>
> ·Murat Turpcu,turk telekom
>
> ·Ning So, Reliance Jio
>
> ·Lingli Deng, CMCC
>
> ·Alla Goldner, Amdocs
>
> ·Bin Yang, Wind River
>
> ·Milind Jalwadi,, TechMahindra
>
> ·Stephen Terrill, Ericsson
>
> ·Susana Sabater, Vodafone
>
> ·Viswa, Verizon
>
> ·Yan Chen, China Telecom
>
> Many thanks & regards
>
> Catherine
>
>
>
> *From:* onap-...@lists.onap.org [mailto:onap-...@lists.onap.org
> ] *On Behalf Of *Alexis de Talhouet
> *Sent:* Friday, October 12, 2018 4:59 AM
> *To:* onap-tsc; onap-discuss
> *Cc:* Seshu m; TIMONEY, DAN
> *Subject:* [onap-tsc] [TSC] Request API change waiver between SO and SDNC
>
>
>
> Hello TSC,
>
>
>
> As discussed during today’s meeting, an issue has been identified in the
> new SO building block, introducing a regression in term of functionality
> from previous release.
>
> PTLs from both projects acknowledge and agree with the required changes.
>
>
>
> *Expected behaviour:*
>
> Have the cloud owner / cloud region being retrievable from static
> configuration file.
>
>
>
> *Current behaviour:*
>
> Cloud owner is hardcoded in the code, with no way to change it using
> config file.
>
>
>
> *API change requested:*
>
> SDN-C: GENERIC-RESOURCE-API.yang
>
>
>
> *Impact:*
>
> This API change will allow SO to resolve the cloud owner from the config
> file (similar to what we had in previous release), and to be able to use it
> with the GR-API.
>
>
>
> *Patches*:
>
> SO:
>
> 1.  Use a property instead of hard coded value. (TBD)
>
> 2.  Push the changeset to allow it to be set on the
> north-bound api.  (TBD)
>
> SDNC:
>
> 1 Add cloud-owner definition: .
> https://gerrit.onap.org/r/#/c/67413/
> 
>
>
>
> Regards,
>
> Alexis
>
> 
>

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

View/Reply Online (#12981): https://lists.onap.org/g/onap-discuss/message/12981
Mute This Topic: https://lists.onap.org/mt/27269171/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-discuss] [appc] APPC CDT- Specifying Source as A&AI in Parameter Definition

2018-10-12 Thread Chandra

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?

2.   Could you please confirm if this functionality included in Casablanca 
release?


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 
 externally 
http://tim.techmahindra.com/tim/disclaimer.html 
 internally within 
TechMahindra.



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

View/Reply Online (#12980): https://lists.onap.org/g/onap-discuss/message/12980
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]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [onap-tsc] [TSC] Request API change waiver between SO and SDNC

2018-10-12 Thread Catherine LEFEVRE

Good morning Alexis,

Thank you for your leadership supporting the teams to progress quickly on this 
issue.
I am adding the TSC vote distro list in order to increase the visibility of 
this request.

TSC Members (or proxy)
Please vote (+1 waiver approved, 0-neutral, -1 waiver not approved) no later 
than Oct 13th End of your Day.
·Andreas Geissler (DT)
·Ranny Haiby, Nokia
·David Sauvageau, Bell Canada
·Chaker Al-Hakim, Huawei
·+1  Catherine Lefevre, AT&T
·Eric Debeau, Orange
·Jason Hunt, IBM
·Srinivasa Addepalli, Intel
·Murat Turpcu,turk telekom
·Ning So, Reliance Jio
·Lingli Deng, CMCC
·Alla Goldner, Amdocs
·Bin Yang, Wind River
·Milind Jalwadi,, TechMahindra
·Stephen Terrill, Ericsson
·Susana Sabater, Vodafone
·Viswa, Verizon
·Yan Chen, China Telecom
Many thanks & regards
Catherine

From: onap-...@lists.onap.org 
[mailto:onap-...@lists.onap.org] On Behalf Of Alexis de Talhouet
Sent: Friday, October 12, 2018 4:59 AM
To: onap-tsc; onap-discuss
Cc: Seshu m; TIMONEY, DAN
Subject: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

Hello TSC,

As discussed during today’s meeting, an issue has been identified in the new SO 
building block, introducing a regression in term of functionality from previous 
release.
PTLs from both projects acknowledge and agree with the required changes.

Expected behaviour:
Have the cloud owner / cloud region being retrievable from static configuration 
file.

Current behaviour:
Cloud owner is hardcoded in the code, with no way to change it using config 
file.

API change requested:
SDN-C: GENERIC-RESOURCE-API.yang

Impact:
This API change will allow SO to resolve the cloud owner from the config file 
(similar to what we had in previous release), and to be able to use it with the 
GR-API.

Patches:
SO:
1.  Use a property instead of hard coded value. (TBD)
2.  Push the changeset to allow it to be set on the north-bound 
api.  (TBD)
SDNC:
1 Add cloud-owner definition: 
.https://gerrit.onap.org/r/#/c/67413/

Regards,
Alexis


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

View/Reply Online (#12979): https://lists.onap.org/g/onap-discuss/message/12979
Mute This Topic: https://lists.onap.org/mt/27261960/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [ONAP Helpdesk #62098] Issue on Failed to pull image from ONAP Nexus 3

Re: [onap-discuss] [SO] Heat template from yaml string to json for SO multicloud adapter

Re: [onap-discuss] onap-sdnc-ansible-server cannot launch

Re: [onap-discuss] [SO] Heat template from yaml string to json for SO multicloud adapter

[onap-discuss] [SO] Heat template from yaml string to json for SO multicloud adapter

Re: [onap-discuss] [onap-tsc-vote] [onap-tsc] [TSC] Request API change waiver between SO and SDNC

Re: [onap-discuss] [appc] APPC CDT- Specifying Source as A&AI in Parameter Definition

Re: [onap-discuss] [appc] APPC CDT- Specifying Source as A&AI in Parameter Definition

Re: [onap-discuss] [External]Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change waiver between SO and SDNC

Re: [onap-discuss] vFW demo-VES integration #integration

Re: [onap-discuss] vFW demo-VES integration #integration

Re: [onap-discuss] vFW demo-VES integration #integration

Re: [onap-discuss] [SO] Create/Activate BB NPE

Re: [onap-discuss] [External]Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change waiver between SO and SDNC

Re: [onap-discuss] [E] Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change waiver between SO and SDNC

[onap-discuss] [appc] APPC CDT- Specifying Source as A&AI in Parameter Definition

Re: [onap-discuss] [onap-tsc] [TSC] Request API change waiver between SO and SDNC

17 matches

Site Navigation

Mail list logo

Footer information