date:20180503

Re: [onap-discuss] [Onap-usecasesub] Usecase subcommittee meeting of 30/4/2018 - the summary

2018-05-03 Thread Vladimir Yanover (vyanover)

Tracy, Steve and Vimal
I have to admit that I am confused as well and need your help.
Which categories of parameters will be supported by the SDN-R?
Which categories of "the parameters needed for DU & CUs" cannot be supported by 
the SDN-R (why?) and will be supported by the APP-C?
Thanks
Vladimir


From: onap-usecasesub-boun...@lists.onap.org 
 On Behalf Of VAN BRAKLE, TRACY L
Sent: Thursday, May 3, 2018 12:04 AM
To: BEGWANI, VIMAL ; Stephen Terrill 
; Alla Goldner ; 
onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: Re: [Onap-usecasesub] [onap-discuss] Usecase subcommittee meeting of 
30/4/2018 - the summary

Whatever we elect to call it, "SDN-R" in Casablanca is evolving to include all 
(or most) logic + features/functionality derived from CC-SDK, whether 
considered "SDN-C" or "APP-C."  This will include Ansible and Chef interfaces 
as well as the additional parameters that may be defined/documented within ONAP 
or within a related open source project.

Refer to the "ONAP OAM Controller" slides on SDN-R wiki page 
(https://wiki.onap.org/display/DW/SDN-R+Documents) that were reviewed with you 
and with others last month.

The seed code is already packaged and will be uploaded to the repository as 
soon as it becomes available.


From: 
onap-discuss-boun...@lists.onap.org 
mailto:onap-discuss-boun...@lists.onap.org>>
 On Behalf Of BEGWANI, VIMAL
Sent: Wednesday, May 02, 2018 4:30 PM
To: Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>; Alla 
Goldner mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; 
onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: Re: [onap-discuss] [Onap-usecasesub] Usecase subcommittee meeting of 
30/4/2018 - the summary

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Steve,
  We have a SDN-C sub-project called SND-R, that focuses on radio configuration 
using NetConf Yang, but it did not cover all the parameters needed for DU & CUs 
(and UPF) and need support Ansible.  We also realized that all mobility network 
elements should be managed by the same controllers (as we might combine CU-UP, 
a RAN element, with UPF, a core elements).  Hence, we need some of the 
capabilities from SDN-C  and some from App-C.  Therefore, we decided this 
controller persona should be created from CCSDK, taking required modules from 
SDN-C and App-C (we can give a short presentation either during 5G Use case 
call or use case subcommittee call).  This could be a starting point for 
generic NF 4-7 Controller.

Hope that helps.

Regards,
Vimal

From: 
onap-usecasesub-boun...@lists.onap.org
 
mailto:onap-usecasesub-boun...@lists.onap.org>>
 On Behalf Of Stephen Terrill
Sent: Wednesday, May 02, 2018 4:13 PM
To: Alla Goldner mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; 
onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: Re: [Onap-usecasesub] Usecase subcommittee meeting of 30/4/2018 - the 
summary

Hi Alla, All,

I had one question for clarification - in the 5G use case work there is the 
statement "Support full application level configuration (+ansible), allow 
various mobile network elements to be controlled from the same controller 
persona created from CC-SDK"

Today in the architecture we have the APP-C, VFC and SDNC.  I was wondering 
whether there was clarification on how the statement relates to the existing 
controllers, and the motivation for the "same" controller".

BR,

Steve.

From: onap-arc-boun...@lists.onap.org 
[mailto:onap-arc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Tuesday, May 01, 2018 3:46 PM
To: onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; 
onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: [Onap-arc] Usecase subcommittee meeting of 30/4/2018 - the summary

Hi all,

Thanks to all meeting attendants!

Here is the summary:

1. We reviewed Edge automation presentation by Ramki and, specifically, what is 
planned for Casablanca
2. We reviewed EUAG feedback (Vodafone, Verizon, AT&T, Bell, Orange) regarding 
their priorities for Casablanca. I put those requirements under 
https://wiki.onap.org/display/DW/Casablanca+goals

[onap-discuss] Is Nexus2 legacy?

2018-05-03 Thread Jaroslav Safka




Hi all,
I have a question regarding nexus 2 and nexus 3. Is the nexus 2 still required, when we have the nexus 3?
Are there any missing features in nexus 3?
Thanks and have a nice day :)
 
Best regards
Jarek
 
  

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ONAP][SO] Unable to login : Camunda portal

2018-05-03 Thread Karthik

Hi Everyone,

I am able to access the camunda UI with  admin/
Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U
Thanks.


Regards,
Karthik



On Wed, May 2, 2018 at 9:10 PM, Karthik  wrote:

> Hi Team , Good day !
>
> I am able to build and run the SO docker images  [dockerconfig_mso_1, 
> dockerconfig_mariadb_1]
> .  But I could not login to Camunda admin portal.
> In Wiki page it is mentioned that "The user is "admin" and the password
> is the same as the jboss admin password," .
> - As per my search , I found that jboss admin password is admin. But it
> did not work. Please correct me if I am wrong.
> - I followed the instructions to add a new user in Jboss using add-user.sh
> script, I am able to access MSO UI [http://ip:9990/console/App.html#home]
> with new user, But could not access Camunda UI [
> http://ip:8080/camunda/app/admin/default/#/login].
> - I changed the password for admin user also, still no use.
>
> It would be great if you could  give me some suggesstions on this problem.
> Thanks a lot!
>
>
> Regards,
> Karthik
>
>
>
>
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Weekly Service IM Discussion Call

2018-05-03 Thread Lingli Deng

Thank you Pascal for the introduction.

Nice to meet you Bithika, and welcome on board.

 

Lingli

 

From: Pascal Menezes  
Sent: 2018年5月2日 19:31
To: Lingli Deng ; 'BEGWANI, VIMAL' 
; 'BULLARD, GIL' ; Chris Purdy 
; 'Davis, Nigel' ; 'ESHET, ITAMAR' 
; huang.zhuo...@zte.com.cn; 'John Strassner' 
; jwil...@tmforum.org; 'KATZMAN, ANATOLY' 
; 'KLUGER, YOAV' ; 'LEFEVRE, 
CATHERINE' ; 'MAYER, ANDREW J' ; 
meili...@huawei.com; 'NG, JOHN' ; Pascal Menezes 
; 'Rittwik Jana' ; 'SCAGGS, KEVIN' 
; 'SHADMI, DAVID' ; 'Vul, Alex' 
; yuan@zte.com.cn; 'Zengjianguo (OSS Design' 
; zhang.maope...@zte.com.cn; 
onap-discuss@lists.onap.org; Bithika Khargharia 
Cc: Pascal Menezes 
Subject: Re: Weekly Service IM Discussion Call

 

Hi Lingli,

 

I am adding and have forward to  Bithika  this weekly conf call series.   
Bithika is with the Office of the CTO in MEF.  She will attend the conf calls 
on my behalf as she is working with our MEF modelling teams on this subject.

 

Thanks for the invite and you are in good hands with Bithika 

 

Thanks


Pascal

 

 

 

 

 

 

From: Lingli Deng mailto:denglin...@chinamobile.com> >
Date: Tuesday, 1 May 2018 at 21:07
To: "'BEGWANI, VIMAL'" mailto:vb1...@att.com> >, "'BULLARD, 
GIL'" mailto:wb5...@att.com> >, 'Chris Purdy' 
mailto:chris.pu...@mef.net> >, "'Davis, Nigel'" 
mailto:nda...@ciena.com> >, "'ESHET, ITAMAR'" 
mailto:ie2...@intl.att.com> >, "huang.zhuo...@zte.com.cn 
 " mailto:huang.zhuo...@zte.com.cn> >, 'John Strassner' mailto:straz...@gmail.com> >, "jwil...@tmforum.org 
 " mailto:jwil...@tmforum.org> >, "'KATZMAN, ANATOLY'" mailto:ak4...@intl.att.com> >, "'KLUGER, YOAV'" mailto:yoav.klu...@amdocs.com> >, "'LEFEVRE, CATHERINE'" mailto:cl6...@intl.att.com> >, "'MAYER, ANDREW J'" mailto:am8...@att.com> >, "meili...@huawei.com  " 
mailto:meili...@huawei.com> >, "'NG, JOHN'" 
mailto:jn1...@att.com> >, Pascal Menezes 
mailto:pas...@tscmtechnology.com> >, 'Pascal 
Menezes' mailto:pas...@mef.net> >, 'Rittwik Jana' 
mailto:rittwik.j...@gmail.com> >, "'SCAGGS, KEVIN'" 
mailto:ks0...@att.com> >, "'SHADMI, DAVID'" mailto:ds2...@att.com> >, "'Vul, Alex'" mailto:alex@intel.com> >, "yuan@zte.com.cn 
 " mailto:yuan@zte.com.cn> >, "'Zengjianguo (OSS Design'" 
mailto:zengjian...@huawei.com> >, 
"zhang.maope...@zte.com.cn  " 
mailto:zhang.maope...@zte.com.cn> >, 
"onap-discuss@lists.onap.org  " 
mailto:onap-discuss@lists.onap.org> >
Subject: RE: Weekly Service IM Discussion Call

 

I am receiving bounce-back notifications from several recipients, hence 
resending the invite.

Sorry for the inconvenience.

 

Lingli

 

-Original Appointment-
From: Lingli Deng <  
denglin...@chinamobile.com> 
Sent: 2018年5月2日 11:35
To: 'BEGWANI, VIMAL'; 'BULLARD, GIL'; 'Chris Purdy'; 'Davis, Nigel'; 'ESHET, 
ITAMAR'; 'huang.zhuo...@zte.com.cn'; 'John Strassner'; 'jwil...@tmforum.org'; 
'KATZMAN, ANATOLY'; 'KLUGER, YOAV'; 'LEFEVRE, CATHERINE'; 'MAYER, ANDREW J'; 
'meili...@huawei.com'; 'NG, JOHN'; 'Pascal Menezes'; 'Pascal Menezes'; 'Rittwik 
Jana'; 'SCAGGS, KEVIN'; 'SHADMI, DAVID'; 'Vul, Alex'; 'yuan@zte.com.cn'; 
'Zengjianguo (OSS Design'; 'zhang.maope...@zte.com.cn';  
 denglin...@chinamobile.com;  
 onap-discuss@lists.onap.org
Subject: FW: Weekly Service IM Discussion Call
When: Occurs every 星期三 effective 2018/5/2 from 8:00 to 9:00 (GMT-08:00) 
America/Los_Angeles.
Where:   https://zoom.us/j/ 9117271979

 

Hi guys,

 

Welcome to join our weekly discussion call for ONAP service modeling.

 

Thanks,

Lingli

 

-Original Appointment-
From: Google Calendar <  
calendar-notificat...@google.com> On Behalf Of ONAP Meetings and Events
Sent: 2018年4月26日 3:20
To: ONAP Meetings and Events;   
denglin...@chinamobile.com;   
onap-discuss@lists.onap.org
Subject: Weekly Service IM Discussion Call
When: Occurs every 星期三 effective 2018/5/2 from 8:00 to 9:00 (GMT-08:00) 
America/Los_Angeles.
Where:   https://zoom.us/j/ 9117271979

 


 

 more details »


Weekly Service IM Discussion Call



When

Weekly from 8am to 9am on Wednesday Pacific Time


Where

  https://zoom.us/j/ 9117271979 ( 
 map)


Calendar

  d

[onap-discuss] SDC deployment on heat and OOM

2018-05-03 Thread Lando,Michael

Hi,

After Gary explained to me how I can login into the external labs I started 
checking our deployment there.

Heat:

It looks like on the last heat deployment execution 
https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-heat-deploy/259/consoleFull

The SDC was not even started I logged into the VM that was assigned to SDC 
10.12.5.83 and our docker startup script was not even executed as far as I can 
see since :
root@onap-sdc:~# docker ps -a
CONTAINER IDIMAGE   COMMAND CREATED 
STATUS  PORTS   NAMES
root@onap-sdc:~#

as a result our health check is shown as failing which is not the case.
What is the cause? What failed?

OOM:

https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-oom-deploy/339/console

from what I see the job and the health check was completed at 8:30 utc when I 
logged into the Machin I can see that it took SDC started successful with no 
intervention (Thank you OOM team) and that last docker came up at 09:14:09 utc.
As a result our health check is marked as failed which is not the case since I 
was able to log into the sdc fe docker and validate the health check is passing.

How can this be addressed can we prolong the job execution or the number of 
retries for the health check? I am more than sure the SDC is not the only 
application that fails because of this.

Side note:
I tried executing the health check from out side the docker but probably I am 
missing something in connection to the K8 networking since I was unable to 
connect.
I tried curl http://sdc-fe.onap:8181/sdc1/rest/healthCheck as the health check 
does.













BR,

[Michael Lando]

AT&T Network Application Development * NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
***
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: michael.la...@intl.att.com

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] SDC deployment on heat and OOM

2018-05-03 Thread Roger Maitland

Hi Michael,

When I look at the logs from Gary’s system I see that the SDC health check was 
run 8 times, failing the 1st time and passing all of the rest:
08:29:50 Basic SDC Health Check
| FAIL |
08:29:50 Basic SDC Health Check
| PASS |
08:29:51 Basic SDC Health Check
| PASS |
08:29:51 Basic SDC Health Check
| PASS |
08:29:51 Basic SDC Health Check
| PASS |
08:29:51 Basic SDC Health Check
| PASS |
08:29:51 Basic SDC Health Check
| PASS |
08:29:51 Basic SDC Health Check
| PASS |
However, the times are different than what you saw at the end of the same URL 
which I can’t explain. Given that Robot doesn’t really know the state of the 
system when it runs the health check this behavior seems reasonable to me (I 
wish I could say this about all the components).

Is there really a problem here?

Cheers,
Roger

From: "Lando,Michael" 
Date: Thursday, May 3, 2018 at 5:56 AM
To: 'Yunxia Chen' , Gary Wu , 
Michael O'Brien , "PLATANIA, MARCO" 
, Mike Elliott , Roger 
Maitland 
Cc: "FREEMAN, BRIAN D" , "Nachmias, Lior" 
, "'onap-discuss@lists.onap.org'" 
, "Ratz, Yaki" , "Fuss, 
Areli" 
Subject: SDC deployment on heat and OOM

Hi,

After Gary explained to me how I can login into the external labs I started 
checking our deployment there.

Heat:

It looks like on the last heat deployment execution 
https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-heat-deploy/259/consoleFull

The SDC was not even started I logged into the VM that was assigned to SDC 
10.12.5.83 and our docker startup script was not even executed as far as I can 
see since :
root@onap-sdc:~# docker ps -a
CONTAINER IDIMAGE   COMMAND CREATED 
STATUS  PORTS   NAMES
root@onap-sdc:~#

as a result our health check is shown as failing which is not the case.
What is the cause? What failed?

OOM:

https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-oom-deploy/339/console

from what I see the job and the health check was completed at 8:30 utc when I 
logged into the Machin I can see that it took SDC started successful with no 
intervention (Thank you OOM team) and that last docker came up at 09:14:09 utc.
As a result our health check is marked as failed which is not the case since I 
was able to log into the sdc fe docker and validate the health check is passing.

How can this be addressed can we prolong the job execution or the number of 
retries for the health check? I am more than sure the SDC is not the only 
application that fails because of this.

Side note:
I tried executing the health check from out side the docker but probably I am 
missing something in connection to the K8 networking since I was unable to 
connect.
I tried curl http://sdc-fe.onap:8181/sdc1/rest/healthCheck as the health check 
does.













BR,

[Michael Lando]

AT&T Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: michael.la...@intl.att.com

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] AAI R2 Vulnerability report

2018-05-03 Thread FORSYTH, JAMES

Hi, Stephen,

The AAI team has made great strides in reducing the number of vulnerabilities 
across our many repositories.  I have updated the AAI Vulnerability report here:
https://wiki.onap.org/x/ZzSEAQ

The last item shows champ as “in progress” with a link to 2 jira stories – the 
team is actively working these right now.  We did a commit on Champ last night 
which will remove multiple vulnerabilities; hopefully Jenkins will be back up 
soon so we can re-run the clm job and get a new report.

There is also one other commit pending from the Champ team which I am hopeful 
will address most of the remaining items.

I’ll keep you posted on our progress and update the set of champ items once I 
have a better report - thanks for your patience.

-jimmy
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] OOM deployment error

2018-05-03 Thread VENKATESH KUMAR, VIJAY

OOM Team,
While deploying the latest (master) OOM charts, running into below error.

ubuntu@vv-k8-2:~/oom/kubernetes$  helm install local/onap -n dev --namespace 
onap
2018/05/03 02:36:05 warning: skipped value for image: Not a table.
Error: error validating "": error validating data: found invalid field 
annotations for v1.PersistentVolumeClaim


Any suggestions please?

Regards,
Vijay
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Onap-usecasesub] Usecase subcommittee meeting of 30/4/2018 - the summary

2018-05-03 Thread VAN BRAKLE, TRACY L

Vladimir,

As of now, the expectation is that all categories of parameters would be 
supported by the ONAP controller derived from CC-SDK for Mobility Wireless.

We have dubbed this controller "SDN-R," as you know, because this particular 
label has meaning (traction, actually) within both ONAP and ONF.

SDN-R = SDN-C + APP-C for Mobility Wireless, in other words.

What we do not yet know is what will be configured via Netconf/YANG versus what 
will be configured via Ansible, but I believe the community will have this 
question answered fairly early within the Casblanca release timeframe.

Tracy

From: Vladimir Yanover (vyanover) 
Sent: Thursday, May 03, 2018 4:09 AM
To: VAN BRAKLE, TRACY L ; BEGWANI, VIMAL ; 
Stephen Terrill ; Alla Goldner 
; onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: RE: [Onap-usecasesub] [onap-discuss] Usecase subcommittee meeting of 
30/4/2018 - the summary

Tracy, Steve and Vimal
I have to admit that I am confused as well and need your help.
Which categories of parameters will be supported by the SDN-R?
Which categories of "the parameters needed for DU & CUs" cannot be supported by 
the SDN-R (why?) and will be supported by the APP-C?
Thanks
Vladimir


From: 
onap-usecasesub-boun...@lists.onap.org
 
mailto:onap-usecasesub-boun...@lists.onap.org>>
 On Behalf Of VAN BRAKLE, TRACY L
Sent: Thursday, May 3, 2018 12:04 AM
To: BEGWANI, VIMAL mailto:vb1...@att.com>>; Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>; Alla 
Goldner mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; 
onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: Re: [Onap-usecasesub] [onap-discuss] Usecase subcommittee meeting of 
30/4/2018 - the summary

Whatever we elect to call it, "SDN-R" in Casablanca is evolving to include all 
(or most) logic + features/functionality derived from CC-SDK, whether 
considered "SDN-C" or "APP-C."  This will include Ansible and Chef interfaces 
as well as the additional parameters that may be defined/documented within ONAP 
or within a related open source project.

Refer to the "ONAP OAM Controller" slides on SDN-R wiki page 
(https://wiki.onap.org/display/DW/SDN-R+Documents)
 that were reviewed with you and with others last month.

The seed code is already packaged and will be uploaded to the repository as 
soon as it becomes available.


From: 
onap-discuss-boun...@lists.onap.org 
mailto:onap-discuss-boun...@lists.onap.org>>
 On Behalf Of BEGWANI, VIMAL
Sent: Wednesday, May 02, 2018 4:30 PM
To: Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>; Alla 
Goldner mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; 
onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: Re: [onap-discuss] [Onap-usecasesub] Usecase subcommittee meeting of 
30/4/2018 - the summary

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Steve,
  We have a SDN-C sub-project called SND-R, that focuses on radio configuration 
using NetConf Yang, but it did not cover all the parameters needed for DU & CUs 
(and UPF) and need support Ansible.  We also realized that all mobility network 
elements should be managed by the same controllers (as we might combine CU-UP, 
a RAN element, with UPF, a core elements).  Hence, we need some of the 
capabilities from SDN-C  and some from App-C.  Therefore, we decided this 
controller persona should be created from CCSDK, taking required modules from 
SDN-C and App-C (we can give a short presentation either during 5G Use case 
call or use case subcommittee call).  This could be a starting point for 
generic NF 4-7 Controller.

Hope that helps.

Regards,
Vimal

From: 
onap-usecasesub-boun...@lists.onap.org
 
mailto:onap-usecasesub-boun...@lists.onap.org>>
 On Behalf Of Stephen Terrill
Sent: Wednesday, May 02, 2018 4:13 PM
To: Alla Goldner mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; 
onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: Re: [Onap-usecas

Re: [onap-discuss] [Onap-usecasesub] Usecase subcommittee meeting of 30/4/2018 - the summary

2018-05-03 Thread Andrej Záň

Hello there,


I have one question (possibly stupid one, sorry for that).

You wrote that SDN-R will be SDN-C + APP-C functionality but for Mobility 
Wireless. Does that mean, that these functions can't be provided by some 
combination/cooperation of SDN-C and APP-C themselves?


Regards

Andrej Záň


Od: VAN BRAKLE, TRACY L 
Odoslané: štvrtok, 3. mája 2018 15:07
Komu: Vladimir Yanover (vyanover); BEGWANI, VIMAL; Stephen Terrill; Alla 
Goldner; onap-usecase...@lists.onap.org
Kópia: onap-...@lists.onap.org; onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Predmet: Re: [Onap-usecasesub] [onap-discuss] Usecase subcommittee meeting of 
30/4/2018 - the summary


Vladimir,



As of now, the expectation is that all categories of parameters would be 
supported by the ONAP controller derived from CC-SDK for Mobility Wireless.



We have dubbed this controller “SDN-R,” as you know, because this particular 
label has meaning (traction, actually) within both ONAP and ONF.



SDN-R = SDN-C + APP-C for Mobility Wireless, in other words.



What we do not yet know is what will be configured via Netconf/YANG versus what 
will be configured via Ansible, but I believe the community will have this 
question answered fairly early within the Casblanca release timeframe.



Tracy



From: Vladimir Yanover (vyanover) 
Sent: Thursday, May 03, 2018 4:09 AM
To: VAN BRAKLE, TRACY L ; BEGWANI, VIMAL ; 
Stephen Terrill ; Alla Goldner 
; onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: RE: [Onap-usecasesub] [onap-discuss] Usecase subcommittee meeting of 
30/4/2018 - the summary



Tracy, Steve and Vimal

I have to admit that I am confused as well and need your help.

Which categories of parameters will be supported by the SDN-R?

Which categories of “the parameters needed for DU & CUs” cannot be supported by 
the SDN-R (why?) and will be supported by the APP-C?

Thanks

Vladimir





From: 
onap-usecasesub-boun...@lists.onap.org
 
mailto:onap-usecasesub-boun...@lists.onap.org>>
 On Behalf Of VAN BRAKLE, TRACY L
Sent: Thursday, May 3, 2018 12:04 AM
To: BEGWANI, VIMAL mailto:vb1...@att.com>>; Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>; Alla 
Goldner mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; 
onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: Re: [Onap-usecasesub] [onap-discuss] Usecase subcommittee meeting of 
30/4/2018 - the summary



Whatever we elect to call it, “SDN-R” in Casablanca is evolving to include all 
(or most) logic + features/functionality derived from CC-SDK, whether 
considered “SDN-C” or “APP-C.”  This will include Ansible and Chef interfaces 
as well as the additional parameters that may be defined/documented within ONAP 
or within a related open source project.



Refer to the “ONAP OAM Controller” slides on SDN-R wiki page 
(https://wiki.onap.org/display/DW/SDN-R+Documents)
 that were reviewed with you and with others last month.



The seed code is already packaged and will be uploaded to the repository as 
soon as it becomes available.





From: 
onap-discuss-boun...@lists.onap.org 
mailto:onap-discuss-boun...@lists.onap.org>>
 On Behalf Of BEGWANI, VIMAL
Sent: Wednesday, May 02, 2018 4:30 PM
To: Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>; Alla 
Goldner mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; 
onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: Re: [onap-discuss] [Onap-usecasesub] Usecase subcommittee meeting of 
30/4/2018 - the summary



***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.

Steve,

  We have a SDN-C sub-project called SND-R, that focuses on radio configuration 
using NetConf Yang, but it did not cover all the parameters needed for DU & CUs 
(and UPF) and need support Ansible.  We also realized that all mobility network 
elements should be managed by the same controllers (as we might combine CU-UP, 
a RAN element, with UPF, a core elements).  Hence, we need some of the 
capabilities from SDN-C  and some from App-C.  Therefore, we decided this 
controller persona should be created from CCSDK, taking required modules from 
SDN-C and App-C (

Re: [onap-discuss] [Onap-usecasesub] Usecase subcommittee meeting of 30/4/2018 - the summary

2018-05-03 Thread VAN BRAKLE, TRACY L

Andrej,

I suppose there are a variety of ways this could be implemented, as all three 
derive from CC-SDK.

SDN-R = CC-SDK + Mobility Wireless "artifacts"

Tracy

From: Andrej Záň 
Sent: Thursday, May 03, 2018 9:21 AM
To: VAN BRAKLE, TRACY L ; Vladimir Yanover (vyanover) 
; BEGWANI, VIMAL ; Stephen Terrill 
; Alla Goldner ; 
onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: Re: [Onap-usecasesub] [onap-discuss] Usecase subcommittee meeting of 
30/4/2018 - the summary


Hello there,



I have one question (possibly stupid one, sorry for that).

You wrote that SDN-R will be SDN-C + APP-C functionality but for Mobility 
Wireless. Does that mean, that these functions can't be provided by some 
combination/cooperation of SDN-C and APP-C themselves?


Regards

Andrej Záň


Od: VAN BRAKLE, TRACY L mailto:tv8...@att.com>>
Odoslané: štvrtok, 3. mája 2018 15:07
Komu: Vladimir Yanover (vyanover); BEGWANI, VIMAL; Stephen Terrill; Alla 
Goldner; onap-usecase...@lists.onap.org
Kópia: onap-...@lists.onap.org; 
onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Predmet: Re: [Onap-usecasesub] [onap-discuss] Usecase subcommittee meeting of 
30/4/2018 - the summary


Vladimir,



As of now, the expectation is that all categories of parameters would be 
supported by the ONAP controller derived from CC-SDK for Mobility Wireless.



We have dubbed this controller "SDN-R," as you know, because this particular 
label has meaning (traction, actually) within both ONAP and ONF.



SDN-R = SDN-C + APP-C for Mobility Wireless, in other words.



What we do not yet know is what will be configured via Netconf/YANG versus what 
will be configured via Ansible, but I believe the community will have this 
question answered fairly early within the Casblanca release timeframe.



Tracy



From: Vladimir Yanover (vyanover) 
mailto:vyano...@cisco.com>>
Sent: Thursday, May 03, 2018 4:09 AM
To: VAN BRAKLE, TRACY L mailto:tv8...@att.com>>; BEGWANI, VIMAL 
mailto:vb1...@att.com>>; Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>; Alla 
Goldner mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; 
onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: RE: [Onap-usecasesub] [onap-discuss] Usecase subcommittee meeting of 
30/4/2018 - the summary



Tracy, Steve and Vimal

I have to admit that I am confused as well and need your help.

Which categories of parameters will be supported by the SDN-R?

Which categories of "the parameters needed for DU & CUs" cannot be supported by 
the SDN-R (why?) and will be supported by the APP-C?

Thanks

Vladimir





From: 
onap-usecasesub-boun...@lists.onap.org
 
mailto:onap-usecasesub-boun...@lists.onap.org>>
 On Behalf Of VAN BRAKLE, TRACY L
Sent: Thursday, May 3, 2018 12:04 AM
To: BEGWANI, VIMAL mailto:vb1...@att.com>>; Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>; Alla 
Goldner mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; 
onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: Re: [Onap-usecasesub] [onap-discuss] Usecase subcommittee meeting of 
30/4/2018 - the summary



Whatever we elect to call it, "SDN-R" in Casablanca is evolving to include all 
(or most) logic + features/functionality derived from CC-SDK, whether 
considered "SDN-C" or "APP-C."  This will include Ansible and Chef interfaces 
as well as the additional parameters that may be defined/documented within ONAP 
or within a related open source project.



Refer to the "ONAP OAM Controller" slides on SDN-R wiki page 
(https://wiki.onap.org/display/DW/SDN-R+Documents)
 that were reviewed with you and with others last month.



The seed code is already packaged and will be uploaded to the repository as 
soon as it becomes available.





From: 
onap-discuss-boun...@lists.onap.org 
mailto:onap-discuss-boun...@lists.onap.org>>
 On Behalf Of BEGWANI, VIMAL
Sent: Wednesday, May 02, 2018 4:30 PM
To: Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>; Alla 
Goldner mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-.

Re: [onap-discuss] SDC deployment on heat and OOM

2018-05-03 Thread PLATANIA, MARCO (MARCO)

Michael,

The issue with the Heat deployment is that connection to Gerrit timed out, so 
the SDC repo hasn’t been cloned:

fatal: unable to access 'http://gerrit.onap.org/r/sdc.git/': Failed to connect 
to gerrit.onap.org port 80: Connection timed out

As a consequence, sdc_vm_init.sh couldn’t find deploy.sh. I just cloned it 
manually and redeployed SDC. Yesterday, we experienced network instability. 
Consider that the clone operation this morning succeeded after a few failed 
attempts. I’m not sure whether the network has healed completely.

Marco

From: "LANDO, MICHAEL" 
Date: Thursday, May 3, 2018 at 5:55 AM
To: 'Yunxia Chen' , Gary Wu , 
"OBRIEN, FRANK MICHAEL" , "PLATANIA, MARCO (MARCO)" 
, Mike Elliott , 'Roger 
Maitland' 
Cc: BRIAN FREEMAN , "NACHMIAS, LIOR" , 
"'onap-discuss@lists.onap.org'" , "RATZ, YAKI" 
, "FUSS, ARELI" 
Subject: SDC deployment on heat and OOM

Hi,

After Gary explained to me how I can login into the external labs I started 
checking our deployment there.

Heat:

It looks like on the last heat deployment execution 
https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-heat-deploy/259/consoleFull

The SDC was not even started I logged into the VM that was assigned to SDC 
10.12.5.83 and our docker startup script was not even executed as far as I can 
see since :
root@onap-sdc:~# docker ps -a
CONTAINER IDIMAGE   COMMAND CREATED 
STATUS  PORTS   NAMES
root@onap-sdc:~#

as a result our health check is shown as failing which is not the case.
What is the cause? What failed?

OOM:

https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-oom-deploy/339/console

from what I see the job and the health check was completed at 8:30 utc when I 
logged into the Machin I can see that it took SDC started successful with no 
intervention (Thank you OOM team) and that last docker came up at 09:14:09 utc.
As a result our health check is marked as failed which is not the case since I 
was able to log into the sdc fe docker and validate the health check is passing.

How can this be addressed can we prolong the job execution or the number of 
retries for the health check? I am more than sure the SDC is not the only 
application that fails because of this.

Side note:
I tried executing the health check from out side the docker but probably I am 
missing something in connection to the K8 networking since I was unable to 
connect.
I tried curl http://sdc-fe.onap:8181/sdc1/rest/healthCheck as the health check 
does.













BR,

[ichael Lando]

AT&T Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: michael.la...@intl.att.com

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Regarding DCAE on OOM

2018-05-03 Thread Michael O'Brien

Mandeep,
   Hi, forwarding to community.
   Welcome - Accenture is an excellent and very efficient organization from my 
experience.
   From the pod names and namespace below - it looks like a pre-amsterdam 
deployment - before last Sept 2017 - you do not want to be running that old 
release.
   You have an Amsterdam branch option - not recommended - there is a 
heatbridge component to DCAE VMs running there - it works on the intel openlab 
as designate is setup there.
   Recommend you move to Beijing/master where DCAEGEN2 is fully containerized 
via OOM/K8S deployment (no openstack) - all kubernetes pods - this is what we 
are supporting.
   Thank you
   /michael


From: Singh Kalra, Mandeep [mailto:mandeep.singh.ka...@accenture.com]
Sent: Thursday, May 3, 2018 3:35 AM
To: Michael O'Brien 
Subject: RE: Regarding DCAE on OOM

Hi Michael,

 Greetings!!

 I am using the Amsterdam release of ONAP deployed 
all major components except DCAE on it using OOM.
 I heard that DCAE requires openstack to come up. 
If I am not wrong then dcaeGen2 uses HEAT, and just tried to run dcae ( not 
gen2) on oom, I could see all pods running:

   onap-dcae 
cdap0-4078069992-jp1vr 1/1   Running   0  
40m
onap-dcae cdap1-4039904165-nnmxn 1/1   
Running   0  40m
onap-dcae cdap2-422364317-nnngx  1/1   
Running   0  40m
onap-dcae dcae-collector-common-event-1149898616-njmd0   1/1   
Running   0  40m
onap-dcae dcae-collector-dmaapbc-1520987080-lcn901/1   
Running   0  40m
onap-dcae dcae-controller-2121147148-qlhbh   1/1   
Running   0  40m
onap-dcae dcae-pgaas-2006588677-s0tbs1/1   
Running   0  40m
onap-dcae dmaap-1927146826-c0svz 1/1   
Running   0  40m
onap-dcae kafka-2590900334-00fgk 1/1   
Running   0  40m
onap-dcae zookeeper-2166102094-qsvkz 1/1   
Running   0  40m


  So just confused whether DCAE actually runs on kubernetes as PODs 
apart from openstack VMs ?




Regards
Mandeep



This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise confidential information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the e-mail by you is prohibited. Where allowed by local law, electronic 
communications with Accenture and its affiliates, including e-mail and instant 
messaging (including content), may be scanned by our systems for the purposes 
of information security and assessment of internal compliance with Accenture 
policy. Your privacy is important to us. Accenture uses your personal data only 
in compliance with data protection laws. For further information on how 
Accenture processes your personal data, please see our privacy statement at 
https://www.accenture.com/us-en/privacy-policy.
__

www.accenture.com
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] OOM deployment error - use HELM 2.8.2 up from 2.7.2 after OOM-779

2018-05-03 Thread Michael O'Brien

Vijaj,
   Hi, I was worried about this.  There was a change put in for APPC where a 
helm upgrade to 2.8.2 was required.
   We already were prototyping the 2.7.2 to 2.8.2 was beneficial for onap 
upgrades being run by Mike E. but those were in progress and did not require 
2.8.2 yet.
   Because of the commit below we now require 2.8.2 on all onap deployments

https://gerrit.onap.org/r/#/c/43005/3

https://jira.onap.org/browse/OOM-1036
https://jira.onap.org/browse/OOM-1033
https://jira.onap.org/browse/OOM-779

Also for everyone - this is a red herring - this other table error has been in 
since the helm install switch a month ago - looking into it
2018/05/03 02:36:05 warning: skipped value for image: Not a table.

Thank you
/michael

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of VENKATESH KUMAR, VIJAY
Sent: Thursday, May 3, 2018 9:05 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] OOM deployment error

OOM Team,
While deploying the latest (master) OOM charts, running into below error.

ubuntu@vv-k8-2:~/oom/kubernetes$  helm install local/onap -n dev --namespace 
onap
2018/05/03 02:36:05 warning: skipped value for image: Not a table.
Error: error validating "": error validating data: found invalid field 
annotations for v1.PersistentVolumeClaim


Any suggestions please?

Regards,
Vijay
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] OOM deployment error - use HELM 2.8.2 up from 2.7.2 after OOM-779

2018-05-03 Thread VENKATESH KUMAR, VIJAY

Hi Michael (and Josef)
Thank you for the update!

I will try switching to newer helm and check. The other warning reported was 
indeed noticed before (that dint really interfere with the deployment).

Regards
-Vijay

From: OBRIEN, FRANK MICHAEL
Sent: Thursday, May 03, 2018 10:52 AM
To: VENKATESH KUMAR, VIJAY ; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] OOM deployment error - use HELM 2.8.2 up from 2.7.2 
after OOM-779

Vijaj,
   Hi, I was worried about this.  There was a change put in for APPC where a 
helm upgrade to 2.8.2 was required.
   We already were prototyping the 2.7.2 to 2.8.2 was beneficial for onap 
upgrades being run by Mike E. but those were in progress and did not require 
2.8.2 yet.
   Because of the commit below we now require 2.8.2 on all onap deployments

https://gerrit.onap.org/r/#/c/43005/3

https://jira.onap.org/browse/OOM-1036
https://jira.onap.org/browse/OOM-1033
https://jira.onap.org/browse/OOM-779

Also for everyone - this is a red herring - this other table error has been in 
since the helm install switch a month ago - looking into it
2018/05/03 02:36:05 warning: skipped value for image: Not a table.

Thank you
/michael

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of VENKATESH KUMAR, VIJAY
Sent: Thursday, May 3, 2018 9:05 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] OOM deployment error

OOM Team,
While deploying the latest (master) OOM charts, running into below error.

ubuntu@vv-k8-2:~/oom/kubernetes$  helm install local/onap -n dev --namespace 
onap
2018/05/03 02:36:05 warning: skipped value for image: Not a table.
Error: error validating "": error validating data: found invalid field 
annotations for v1.PersistentVolumeClaim


Any suggestions please?

Regards,
Vijay
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Is Nexus2 legacy?

2018-05-03 Thread Andrew Grimberg

On 05/03/2018 01:52 AM, Jaroslav Safka wrote:
> Hi all,
> 
> I have a question regarding nexus 2 and nexus 3. Is the nexus 2 still
> required, when we have the nexus 3?
> 
> Are there any missing features in nexus 3?
> 
> Thanks and have a nice day :)

Greetings Jaroslav,

Nexus 2 is still required by our environment. The reason being that
Nexus 3 still does not provide any staging capabilities for Maven artifacts.

Additionally, we heavily leverage the fact that Nexus 2 writes artifacts
out to the standard filesystem whereas Nexus 3 only writes them out to a
blob store requiring rebuilding files on access by accessing an internal
H2 database as well as combining several files together.

Our leveraging of the filesystem configuration of Nexus 2 is used by our
log shipping routines as well as any javadoc sites that projects produce.

As such, if you look at most any of the CI setups that LF has put
together for any projects you will find a Nexus 2 in play. Nexus 3 shows
up if Docker or PyPi come into the picture.

-Andy-

-- 
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation

signature.asc
Description: OpenPGP digital signature
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [integration][vid][aai] Distribution status attribute in AAI for models

2018-05-03 Thread Andrew Fenner

Hi,

Looking at the latest (todays) images for VID and AAI I think I see a mismatch.

VID is doing a query into AAI looking for
{"start" : "service-design-and-creation/models/","query" : 
"query/serviceModels-byDistributionStatus?distributionStatus=DISTRIBUTION_COMPLETE_OK"}

But in the distributed model I only have
{
  "model-version-id": "2add64e4-9cce-46c1-82dd-7a7565fe2f89",
  "model-name": "EricssonMME",
  "model-version": "1.0",
  "model-description": "",
  "resource-version": "1525356180694"
}

No models were found by vid.

I updated the model with a PUT so that I had

{
  "model-version-id": "2add64e4-9cce-46c1-82dd-7a7565fe2f89",
 "model-name": "EricssonMME",
  "model-version": "1.0",
  "distribution-status": "DISTRIBUTION_COMPLETE_OK",
  "model-description": "",
  "resource-version": "1525365593392"
}

And then the model appears in VID.

Should AAI be setting the distribution-status ?? or is Vid been to strict 

Thanks

/Andrew

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [integration][vid][aai] Distribution status attribute in AAI for models

2018-05-03 Thread SMOKOWSKI, STEVEN

SO sets that field in A&AI, at distribution time.

Thanks

-Steve

From:  on behalf of Andrew Fenner 

Date: Thursday, May 3, 2018 at 12:51 PM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] [integration][vid][aai] Distribution status attribute 
in AAI for models

Hi,

Looking at the latest (todays) images for VID and AAI I think I see a mismatch.

VID is doing a query into AAI looking for
{"start" : "service-design-and-creation/models/","query" : 
"query/serviceModels-byDistributionStatus?distributionStatus=DISTRIBUTION_COMPLETE_OK"}

But in the distributed model I only have
{
  "model-version-id": "2add64e4-9cce-46c1-82dd-7a7565fe2f89",
  "model-name": "EricssonMME",
  "model-version": "1.0",
  "model-description": "",
  "resource-version": "1525356180694"
}

No models were found by vid.

I updated the model with a PUT so that I had

{
  "model-version-id": "2add64e4-9cce-46c1-82dd-7a7565fe2f89",
 "model-name": "EricssonMME",
  "model-version": "1.0",
  "distribution-status": "DISTRIBUTION_COMPLETE_OK",
  "model-description": "",
  "resource-version": "1525365593392"
}

And then the model appears in VID.

Should AAI be setting the distribution-status ?? or is Vid been to strict 

Thanks

/Andrew

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Onap-usecasesub] Usecase subcommittee meeting of 30/4/2018 - the summary

2018-05-03 Thread Stephen Terrill

Hi,

Currently we have the SDN-C and APP-C and VFC in the architecture.  There has 
been proposals in the directional architecture to bring this down to SDN-C and 
A Generic NF controller.  In this proposal it was focussed on increasing the 
alignment and replacing controllers, not putting an additional one.

Adding another controller "SDN-R" in addition seems to move in the other 
direction by increasing the overlap in the architecture - or do I 
mis-understand?  I would like to understand the motivation, and what cannot be 
done with the APPC and SDNC that are already in the architecture.

I am unsure which repo you are considering to upload to as I am not convinced 
this is in the scope of the SDNC project.

BR,

Steve


From: VAN BRAKLE, TRACY L [mailto:tv8...@att.com]
Sent: Wednesday, May 02, 2018 11:04 PM
To: BEGWANI, VIMAL ; Stephen Terrill 
; Alla Goldner ; 
onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: RE: [onap-discuss] [Onap-usecasesub] Usecase subcommittee meeting of 
30/4/2018 - the summary

Whatever we elect to call it, "SDN-R" in Casablanca is evolving to include all 
(or most) logic + features/functionality derived from CC-SDK, whether 
considered "SDN-C" or "APP-C."  This will include Ansible and Chef interfaces 
as well as the additional parameters that may be defined/documented within ONAP 
or within a related open source project.

Refer to the "ONAP OAM Controller" slides on SDN-R wiki page 
(https://wiki.onap.org/display/DW/SDN-R+Documents) that were reviewed with you 
and with others last month.

The seed code is already packaged and will be uploaded to the repository as 
soon as it becomes available.


From: 
onap-discuss-boun...@lists.onap.org 
mailto:onap-discuss-boun...@lists.onap.org>>
 On Behalf Of BEGWANI, VIMAL
Sent: Wednesday, May 02, 2018 4:30 PM
To: Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>; Alla 
Goldner mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; 
onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: Re: [onap-discuss] [Onap-usecasesub] Usecase subcommittee meeting of 
30/4/2018 - the summary

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Steve,
  We have a SDN-C sub-project called SND-R, that focuses on radio configuration 
using NetConf Yang, but it did not cover all the parameters needed for DU & CUs 
(and UPF) and need support Ansible.  We also realized that all mobility network 
elements should be managed by the same controllers (as we might combine CU-UP, 
a RAN element, with UPF, a core elements).  Hence, we need some of the 
capabilities from SDN-C  and some from App-C.  Therefore, we decided this 
controller persona should be created from CCSDK, taking required modules from 
SDN-C and App-C (we can give a short presentation either during 5G Use case 
call or use case subcommittee call).  This could be a starting point for 
generic NF 4-7 Controller.

Hope that helps.

Regards,
Vimal

From: 
onap-usecasesub-boun...@lists.onap.org
 
mailto:onap-usecasesub-boun...@lists.onap.org>>
 On Behalf Of Stephen Terrill
Sent: Wednesday, May 02, 2018 4:13 PM
To: Alla Goldner mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; 
onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: Re: [Onap-usecasesub] Usecase subcommittee meeting of 30/4/2018 - the 
summary

Hi Alla, All,

I had one question for clarification - in the 5G use case work there is the 
statement "Support full application level configuration (+ansible), allow 
various mobile network elements to be controlled from the same controller 
persona created from CC-SDK"

Today in the architecture we have the APP-C, VFC and SDNC.  I was wondering 
whether there was clarification on how the statement relates to the existing 
controllers, and the motivation for the "same" controller".

BR,

Steve.

From: onap-arc-boun...@lists.onap.org 
[mailto:onap-arc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Tuesday, May 01, 2018 3:46 PM
To: onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; 
onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: [Onap-arc] Usecase subcommittee meeting of 30/4/2018 - the summary

Hi all,

Thanks to all meeting attendants!

Here is the summary:

1.

Re: [onap-discuss] OOM deployment error - use HELM 2.8.2 up from 2.7.2 after OOM-779

2018-05-03 Thread VENKATESH KUMAR, VIJAY

Just to update; upgrading helm indeed did fix the issue.

Below are the steps incase someone else stumbles on similar issue.

wget 
https://storage.googleapis.com/kubernetes-helm/helm-v2.8.2-linux-amd64.tar.gz
gunzip helm-v2.8.2-linux-amd64.tar.gz
tar -xvf helm-v2.8.2-linux-amd64.tar
sudo mv linux-amd64/helm /usr/local/bin/helm
helm init --upgrade

Thanks,
Vijay
From: onap-discuss-boun...@lists.onap.org  
On Behalf Of VENKATESH KUMAR, VIJAY
Sent: Thursday, May 03, 2018 11:00 AM
To: OBRIEN, FRANK MICHAEL ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] OOM deployment error - use HELM 2.8.2 up from 2.7.2 
after OOM-779

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Hi Michael (and Josef)
Thank you for the update!

I will try switching to newer helm and check. The other warning reported was 
indeed noticed before (that dint really interfere with the deployment).

Regards
-Vijay

From: OBRIEN, FRANK MICHAEL
Sent: Thursday, May 03, 2018 10:52 AM
To: VENKATESH KUMAR, VIJAY mailto:vv7...@att.com>>; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] OOM deployment error - use HELM 2.8.2 up from 2.7.2 
after OOM-779

Vijaj,
   Hi, I was worried about this.  There was a change put in for APPC where a 
helm upgrade to 2.8.2 was required.
   We already were prototyping the 2.7.2 to 2.8.2 was beneficial for onap 
upgrades being run by Mike E. but those were in progress and did not require 
2.8.2 yet.
   Because of the commit below we now require 2.8.2 on all onap deployments

https://gerrit.onap.org/r/#/c/43005/3

https://jira.onap.org/browse/OOM-1036
https://jira.onap.org/browse/OOM-1033
https://jira.onap.org/browse/OOM-779

Also for everyone - this is a red herring - this other table error has been in 
since the helm install switch a month ago - looking into it
2018/05/03 02:36:05 warning: skipped value for image: Not a table.

Thank you
/michael

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of VENKATESH KUMAR, VIJAY
Sent: Thursday, May 3, 2018 9:05 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] OOM deployment error

OOM Team,
While deploying the latest (master) OOM charts, running into below error.

ubuntu@vv-k8-2:~/oom/kubernetes$  helm install local/onap -n dev --namespace 
onap
2018/05/03 02:36:05 warning: skipped value for image: Not a table.
Error: error validating "": error validating data: found invalid field 
annotations for v1.PersistentVolumeClaim


Any suggestions please?

Regards,
Vijay
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Please Update Docker Manifest

2018-05-03 Thread Gary Wu

Hi all,

It's come to our attention that some entries in the docker manifest do not 
actually exist in nexus3.  Since we're now past RC1, I'm turning on a 
validation to ensure that all the docker image versions specified in the 
manifest actually exist on nexus3.

While doing so, I had to change various docker image names and tags to ones 
that actually exist.  Please check the changes here:  
https://gerrit.onap.org/r/#/c/46041/3/version-manifest/src/main/resources/docker-manifest.csv
 so make sure that the new values are right for your images.

There are still quite a large number of docker images using tags containing 
"latest", "STAGING", or "SNAPSHOT" in the tag string.  By RC2, all docker 
images in the manifest must be release versions.  Please start releasing your 
docker images as you're ready, and be sure to update the manifest with your 
version updates when that happens.  This is the set of versions that 
Integration will use for the purposes of deployment and use-case testing.

Thanks,
Gary


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Queries regarding dcae_cli tool

2018-05-03 Thread Bisht, Suraj (Nokia - US/Irving)

Hi,

Kindly clarify following queries for dcae_cli tool

a)   Is dcae_cli postgress database for catalog a separate database, can we 
use existing database from other ONAP components (i.e. SDC)?

b)  Can dcae_cli tool generate csar without setting-up catalog database?

c)   Is there any sample csar available to verify deployment of dcae 
micro-service component?

Thanks,
Suraj
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [integration][oom] [portal] [so] Integration Working Session

2018-05-03 Thread Yunxia Chen

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Yunxia Chen:MAILTO:helen.c...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=onap-disc
 uss:MAILTO:onap-discuss@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=LUSHENG J
 I:MAILTO:l...@research.att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Yang Xu (
 Yang, Fixed Network)":MAILTO:yang@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Karin Ar
 nold':MAILTO:karin.arn...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='alan_jw_
 ch...@trend.com.tw':MAILTO:alan_jw_ch...@trend.com.tw
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Tina Tsou
 :MAILTO:tina.t...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=pierre.ly
 n...@keysight.com:MAILTO:pierre.ly...@keysight.com
DESCRIPTION;LANGUAGE=en-US:When: Friday\, May 04\, 2018 8:00 AM-10:00 AM. (
 UTC-08:00) Pacific Time (US & Canada)\nWhere: https://zoom.us/j/44
 \n\n*~*~*~*~*~*~*~*~*~*\n\n\n
SUMMARY;LANGUAGE=en-US:[integration][oom] [portal] [so] Integration Working
  Session
DTSTART;TZID=Pacific Standard Time:20180504T08
DTEND;TZID=Pacific Standard Time:20180504T10
UID:DB6723D8-86B6-4AEF-B6C9-D5C703B583A5
RECURRENCE-ID;TZID=Pacific Standard Time:20180504T08
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180504T052922Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:3
LOCATION;LANGUAGE=en-US:https://zoom.us/j/44
X-MICROSOFT-CDO-APPT-SEQUENCE:3
X-MICROSOFT-CDO-OWNERAPPTID:2116336784
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:TRUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Onap-usecasesub] Usecase subcommittee meeting of 30/4/2018 - the summary

[onap-discuss] Is Nexus2 legacy?

Re: [onap-discuss] [ONAP][SO] Unable to login : Camunda portal

Re: [onap-discuss] Weekly Service IM Discussion Call

[onap-discuss] SDC deployment on heat and OOM

Re: [onap-discuss] SDC deployment on heat and OOM

[onap-discuss] AAI R2 Vulnerability report

[onap-discuss] OOM deployment error

Re: [onap-discuss] [Onap-usecasesub] Usecase subcommittee meeting of 30/4/2018 - the summary

Re: [onap-discuss] [Onap-usecasesub] Usecase subcommittee meeting of 30/4/2018 - the summary

Re: [onap-discuss] [Onap-usecasesub] Usecase subcommittee meeting of 30/4/2018 - the summary

Re: [onap-discuss] SDC deployment on heat and OOM

Re: [onap-discuss] Regarding DCAE on OOM

Re: [onap-discuss] OOM deployment error - use HELM 2.8.2 up from 2.7.2 after OOM-779

Re: [onap-discuss] OOM deployment error - use HELM 2.8.2 up from 2.7.2 after OOM-779

Re: [onap-discuss] Is Nexus2 legacy?

[onap-discuss] [integration][vid][aai] Distribution status attribute in AAI for models

Re: [onap-discuss] [integration][vid][aai] Distribution status attribute in AAI for models

Re: [onap-discuss] [Onap-usecasesub] Usecase subcommittee meeting of 30/4/2018 - the summary

Re: [onap-discuss] OOM deployment error - use HELM 2.8.2 up from 2.7.2 after OOM-779

[onap-discuss] Please Update Docker Manifest

[onap-discuss] Queries regarding dcae_cli tool

[onap-discuss] [integration][oom] [portal] [so] Integration Working Session

23 matches

Site Navigation

Mail list logo

Footer information