Re: [onap-discuss] Integration with 3rd pary SDN Controllers

[Avi Chapnick]

Hi Michal,

The SDN Agent project is not part of ONAP.
SDNC component is actually the global controller which is used to integrate 
with 3rd party SDN controllers potentially such as ONOS
So you should investigate it , e.g. adding generic plugin which call ONOS.  
Notices that ccsdk project is where generic plugins are developed.

As for option 2 , in SDNC the ODL is used as a generic platform from mapping 
from ONAP model to a 3rd party model , it's not deployed as "standard" SDN 
controller.
So replacing ODL with ONOS will probably not serve the purpose you need.

Avi,

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Michal Mach
Sent: Wednesday, October 18, 2017 11:59 AM
To: onap-discuss@lists.onap.org
Cc: 'Gopinath Taget' 
Subject: [onap-discuss] Integration with 3rd pary SDN Controllers

Hello Onap!

I've been evaluating possibilities to integrate ONOS controller with ONAP and I 
see two approaches for that:

1.   Integrating via SDN Agent module, writing dedicated driver/adaptor for 
ONOS

2.   Replacing SDNC module that is based on ODL
As  the second option seems to be more hack than integration I have a few 
question regarding the first one.

Where can I find the code, designs and information about SDN Agent module? Is 
the API for writing Adaptor ready?
I've tried to find that information on ONAP Wiki, Github and Onap jira but I 
failed :(

[cid:image001.png@01D34727.AD981C00]

Best regards,

[cid:Z5JE7EUABGFC@namo.co.kr]

Michał Mach
Samsung R Institute Poland
Samsung Electronics

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] urgent: can't open zoom meeting

[Avi Chapnick]

Adding the help desk

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Sauvageau, David
Sent: Wednesday, August 2, 2017 5:07 PM
To: onap-discuss@lists.onap.org; Kenny Paul 
Subject: [onap-discuss] [OOM] urgent: can't open zoom meeting

Hi Kenny,

Can’t start the zoom meeting (The host has another meeting in progress). Can’T 
join audio as well. Anyone can help?

Thanks,
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] [oom] Application deployment configuration template

[Avi Chapnick]

Dear OOM members,

Following our meeting last week , I have updated OOM wiki with the proposal 
presentation and added section which describe the application deployment 
configuration template yaml file. (page  5-6)

I will appreciate your review and comments before working with the components 
for creating the per application files.

https://wiki.onap.org/pages/worddav/preview.action?fileName=ONAP+CM+v3.pptx=8229355


Thanks,

Avi Chapnick

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 
<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] YANG.XML format

[Avi Chapnick]

Hi,

Some of the questions below refers to SDNC managed devices YANG schemas , which 
ODL gets  from the devices once the device is mounted.
Are we planning to allow getting customized version of those schemas from SDC  
for allowing fixing problems on the managed devices yang?

Some of the answers referred  to the yang models which are being used to define 
SDNC NB interfaces (Service RPC+ data model + storage schema)
As Dan explained today these are required in compile time and for that there is 
no sense of getting in runtime via SDC.

In APPC we do allow getting YANG schema from SDC in runtime , we are using 
these to define the structure and  the storage schema of the specific VNF APPC 
Is managing.
Loading NB yang schema dynamically to ODL is tricky , mainly as ODL is not 
providing API for that  and forces you to upload a synthetic  OSGI bundle with 
yang schema embedded.
I have started the engagement with ODL community for adding this support while 
back , if SDNC has the same interest (which makes a lot of sense to me.) maybe 
its good time to revive this discussion.

Avi,



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of TIMONEY, DAN
Sent: Saturday, July 8, 2017 4:03 AM
To: ROZIN, EDEN ; Thomas Nadeau 
; FREEMAN, BRIAN D ; NOSHPITZ, CLAUDE 
; LANDO, MICHAEL ; Kedar Ambekar 

Cc: WRIGHT, STEVEN A ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] YANG.XML format

All,

The YANG.XML artifact type name is perhaps a bit confusing. The actual artifact 
itself is in XML format. The YANG.XML designation indicates that the structure 
of the file is defined by a Yang model. The Yang model itself isn't distributed 
by SDC.

In the case of SDNC, we need to have the Yang model available to us at compile 
time so that we can use it to generate the code to parse XML files defined by 
that model. So, right now there really wouldn't be much use at least to SDNC in 
distribution of the Yang model itself via SDC. In the longer term, though, we 
are looking into being able to handle Yang models more dynamically. So when we 
get that working, we may very well be very interested in receiving Yang models 
from SDC. But that would not be in scope for release 1.

Hope this helps,
Dan

Sent from MyOwn, an AT BYOD solution.


From: "ROZIN, EDEN" >
Date: Thursday, July 6, 2017 at 12:50:05 PM
To: "Thomas Nadeau" 
>, "FREEMAN, BRIAN D" 
>, "NOSHPITZ, CLAUDE" 
>, "LANDO, MICHAEL" 
>, "Kedar Ambekar" 
>
Cc: "WRIGHT, STEVEN A" >, 
"onap-discuss@lists.onap.org" 
>
Subject: Re: [onap-discuss] YANG.XML format
***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
The artifacts types are configurable, so there is a way to add 'YANG' as 
another type for artifacts upload.
All the artifacts are located inside the distributed CSAR that contain all the 
relevant Service information.
If SDN-C would like to get the artifacts, they can.

Eden

From: Thomas Nadeau [mailto:thomas.nad...@amdocs.com]
Sent: Thursday, July 06, 2017 12:26 AM
To: FREEMAN, BRIAN D >; NOSHPITZ, CLAUDE 
>; Lando,Michael 
>; Kedar Ambekar 
>; Rozin, Eden 
>
Cc: WRIGHT, STEVEN A >; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] YANG.XML format

+1

While I'd love for all the new features in 1.1 to be available, the bottom line 
is as Brian said: actual production device support which in my estimation will 
take a bit longer.

--Tom


From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of FREEMAN, BRIAN D
Sent: Wednesday, July 5, 2017 4:12 PM
To: NOSHPITZ, CLAUDE >; LANDO, MICHAEL 
>; Kedar Ambekar 
>; ROZIN, EDEN 
>
Cc: WRIGHT, STEVEN A >; 
onap-discuss@lists.onap.org
Subject: Re: 

Re: [onap-discuss] [onap-tsc] Project Proposal: External System Register

[Avi Chapnick]

Hi,

Reading the project scope it seems to me a real time configuration repository 
for external system location and credential specifically for VIM.
Probably this should be part of the multi-vim project which should own and 
manage this configuration.

I assume that  the component which is used for  storing/managing this 
configuration can be shared across different projects and/or might offered to  
be a service which any component can use.

Avi,


From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of ROSE, DANIEL V
Sent: Tuesday, May 16, 2017 6:51 PM
To: li.z...@zte.com.cn; jpianigi...@juniper.net
Cc: onap-discuss@lists.onap.org; onap-...@lists.onap.org
Subject: Re: [onap-tsc] [onap-discuss] Project Proposal: External System 
Register

I have to agree with Jacopo and Steve, that’s not business logic that’s basic 
endpoint health checking.

So to clarify on my and their inputs, it still seems like to me that the entire 
scope of this project is covered by some combination of A, ONAP OM or MSB 
depending on who you ask / how you look at it.

ONAP Operations manager in particular mentions (Which seems to cover most of 
your stuff.)

•  Platform Monitoring & healing: Monitor platform state, Platform health 
checks, fault tolerance and self-healing

Can you please work with someone like David Sauvageau on that project to be 
sure you have no overlap?

Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
li.z...@zte.com.cn
Sent: Tuesday, May 16, 2017 12:49 AM
To: jpianigi...@juniper.net
Cc: onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] Project Proposal: External System 
Register


Hi Jacopo,



Thanks for your quick response. The business logic can be information 
verification before store the data to A, and heartbeat detection of the 
system state.

For example, a user sent the authentic url, tenant, username and password of 
VIM to ESR. ESR try to connect the VIM with these information. After authentic 
succeed, ESR store these VIM information to A, do heartbeat detection for 
VIM status and present the system status to user.



Best regards,

LiZi






原始邮件
发件人： ＜jpianigi...@juniper.net＞;
收件人：李滋00164331;
抄送人： ＜stephen.terr...@ericsson.com＞; ＜onap-...@lists.onap.org＞; 
＜onap-discuss@lists.onap.org＞;
日 期 ：2017年05月16日 11:32
主 题 ：Re: [onap-tsc] Project Proposal: External System Register


Not clear what the business logic is.

Sent from my iPhone

On May 15, 2017, at 8:21 PM, "li.z...@zte.com.cn" 
＜li.z...@zte.com.cn＞ wrote:

Hi Jacopo, Steve:



Actually, ESR has some business logic to deal with about external system, such 
as information verification,  which is out the scope of A When comes to the 
realization, ESR will be realized relying on A (store the external system 
data in A).



Thanks,

LiZi












发件人： ＜jpianigi...@juniper.net＞;
收件人： 
＜stephen.terr...@ericsson.com＞;李滋00164331; 
 ＜onap-...@lists.onap.org＞; 
＜onap-discuss@lists.onap.org＞;
日 期 ：2017年05月16日 01:19
主 题 ：RE: [onap-tsc] Project Proposal: External System Register


Hi,
I would agree with Steve about the need to limit overlap between subprojects
Jacopo
From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Stephen Terrill
Sent: Monday, May 15, 2017 10:10 AM
To: li.z...@zte.com.cn; 
onap-...@lists.onap.org; 
onap-discuss@lists.onap.org
Subject: Re: [onap-tsc] Project Proposal: External System Register

Hi,

While I agree with the need of the external elements to be registered, is there 
a reason for why we need a separate register in addition to A? (note: I saw 
that Catherine   had a comment with a similar lines).  It may also relate to 
catalogue - LiZi, have you had a chance to chat with the A Project 
(https://wiki.onap.org/pages/viewpage.action?pageId=3246952
   ).

Best Regards,

Steve.

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of 
li.z...@zte.com.cn
Sent: 15 May 2017 04:32
To: onap-...@lists.onap.org; 

Re: [onap-discuss] Reference to VFC repo ?

[Avi Chapnick]

Re the integration between NFVO and GVNFM , it's  done via the MS layer
More specifically lcm/pub/msapi/vnfmdrive.py
Its build a URL, where the VNFM should be available , and execute it.

Avi,

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of ROSE, DANIEL V
Sent: Monday, May 8, 2017 7:35 PM
To: FREEMAN, BRIAN D ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Reference to VFC repo ?

https://git.open-o.org/nfvo/
https://git.open-o.org/gvnfm-vnflcm
https://git.open-o.org/gvnfm-vnfmgr
https://git.open-o.org/gvnfm-vnfres

are the 4 repos I have identified as being the seed part of vf-c


I believe an api between so and it is defined in 
https://git.open-o.org/nfvo/tree/lcm/lcm specifically via wsdl in 
https://git.open-o.org/nfvo/tree/lcm/lcm/ns/data/init

I don't think gvnfm interacts with so that ive seen

(Someone from open-o keep me honest)

Thanks,

Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of FREEMAN, BRIAN D
Sent: Monday, May 08, 2017 12:20 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Reference to VFC repo ?

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
I'm trying to understand the VF-C data model. Is this the right repo in Open-O 
(gvnfm-vnfmgr)  ?

There is a swagger.json for the interface - does anyone have a yang model that 
corresponds to it ?

Brian

https://gerrit.open-o.org/r/gitweb?p=gvnfm-vnfmgr.git;a=blob;f=mgr/mgr/swagger/swagger.json;h=552d26f230985c4407352b02c8841bf7d439a6bc;hb=HEAD

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