from:"ROSE, DANIEL V"

Re: [onap-tsc] Suggestion to have component wise mailing list to declutter onap-discuss / tsc

2017-06-29 Thread ROSE, DANIEL V

Viswa,
I remember this was discussed at the may f2f (and im sure elsewhere) and the 
concensus was made that one list means there is less cross posting.

The way to filter if you personally care about only a few topics is to log into 
mailman and select the topics you care about (each approved project has at 
least 1 topic). The link for onap discuss is 
https://lists.onap.org/mailman/options/onap-discuss and then Which topic 
categories would you like to subscribe to?

If you still feel you want to request the change please proceed.

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

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Viswa KSP
Sent: Thursday, June 29, 2017 11:07 AM
To: onap-disc...@lists.onap.org; onap-tsc 
Subject: [onap-tsc] Suggestion to have component wise mailing list to declutter 
onap-discuss / tsc

Dear All,

I'm not sure if this has been already discussed, but I feel kinda difficult 
follow onap-discuss / onap-tsc mailng list. I feel there is too much traffic 
since same mailing list is being used for all component discussion and I often 
miss to notify updates from desired components.

Hence I would like to propose to have separate mailing list for each component 
established first and have the relevant discussions ( include ptl nomimations, 
poll results etc ) tracked there.

Just my 2 cents.

BR,
Viswa
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Optimization framework

2017-06-22 Thread ROSE, DANIEL V

The original design I saw had the SNIRO framework (att internal name for this) 
as being a few microservices deployed via OOM. OOM would then place them near 
other components based on needs (Ie if dcae needs a certain optimization 
service, instances of it would be deployed closer to the edge dace relies on. 
If it is something SO needs, it would be deployed closer to the core but that 
placement logic was all in oom. Not sure if that logic survives to the current 
proposal.

Thanks,

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

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Stephen Terrill
Sent: Thursday, June 22, 2017 3:22 PM
To: SPATSCHECK, OLIVER 
Cc: PUTHENPURA, SARAT ; onap-tsc 

Subject: Re: [onap-tsc] Optimization framework

Hi Oliver,

Thanks for the clarifications – I do understand better now and as a result I am 
fine with this.

Two questions/comments though:
-  I assume it could even be called by the controllers if this was 
relivant (e.g. the VF-C, OOM).

Perhaps in the description at the start just after where it says the project 
would provide 2 new services a) HAS and b) CMSO, you could put:
These will be delivered as 3 modules.  One for HAS, one for CMSO and one for 
the service design framework.
The HAS and CMSO modules will execute both as services on DCAE and independent 
processes.
--

BR,

Steve

From: SPATSCHECK, OLIVER (OLIVER) [mailto:spat...@research.att.com]
Sent: 22 June 2017 19:31
To: Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>
Cc: onap-tsc mailto:onap-tsc@lists.onap.org>>; 
PUTHENPURA, SARAT (SARAT) 
mailto:sa...@research.att.com>>
Subject: Re: [onap-tsc] Optimization framework


I think there are a couple of misconceptions here.

This is not the change management project. The change management project was 
about the end to end use case flow needed to perform change management.  This 
project ONLY provides the schedule optimization part of that flow. The flow 
itself touches many projects and as discussed I agree is best handled as a use 
case. The actual flows would be implemented using all the regular components 
which at one point in the flow call out to this project for an optimization 
decision.

The same is true for homing.

So let me try to illustrate the flow of this a bit better. The scope of the 
project is algorithms and a run time framework to :

1. gather and normalize data to perform an optimization decision based on a 
request
2. gather the polices from the policy engine provided by the policy project 
using standard APIs exported by that project
3. formulate the optimization problem
4. run the optimization algorithm (this might be iterative with the prior steps)
5. return an optimization result to the requestor

So let me give a homing related example.

Let’s assume a workflow in the SO is triggered to instantiate a VNF. As part of 
the workflow there might be a call into HAS to derive the optimal location. The 
constrains for the placement are associated with the policy (handled in the 
policy project) for that VNF. HAS will now go to A&AI and DCAE (using the 
regular A&AI and DCAE APIs) to gather enough data to make a placement decision 
at which point HAS would return the result back to the SO so the SO can proceed 
instantiating the VNF following the rules in it’s workflow.

Please note that the call out to HAS was part of the SO workflow for that 
particular VNF.  It’s under the control of whoever designs the SO workflow 
(likely the specific use case) if HAS gets called or not and what constraints 
are communicated.

In terms of execution of all of this. Parts currently run as independent MS 
other parts run as MS managed on DCAE. Again this project just uses 
infrastructure that already exists.

You also mentioned CLAMP. CLAMP flows as any other flow in ONAP could call out 
to the optimization framework if it helps. If it doesn’t the flows don’t.

So this should explain how this project does not “hurt” any other project and  
is aligned with the architecture.

Now if I interpret your second question correctly you are also asking “How does 
it help?” .

The reason we want to combine all of this in one project is that there is 
reusability in the code required in steps 1.-5.

For example:

1. + 2. requires code to gather information from many existing ONAP components 
and present them in a common format so they can be used to derive the 
optimization formulation.

3. + 4. as we do not believe that there is one formulation/optimizer which 
solvers every problem we do believe that the same formulation approach combined 
with a set of optimizers and constraints can cover a large set of diverse use 
cases leading to reuse in this area too.

 So the benefit of the project as the library of 
formulations/optimizers/runtime framework grows will be that instead of writing 
code for new optimization challenges they can be just configured or at least 
will require minimal code development.

D

Re: [onap-tsc] Special (and longer) TSC meeting this Thursday 6/22/17

2017-06-21 Thread ROSE, DANIEL V

I believe there was an email from Stephen T saying the network fuction change 
mgmt. team could go off and make use cases so hopefully some other tsc members 
can weigh in and we can make a decision.

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

-Original Message-
From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of SPATSCHECK, OLIVER
Sent: Wednesday, June 21, 2017 10:40 AM
To: Phil Robb 
Cc: onap-tsc 
Subject: Re: [onap-tsc] Special (and longer) TSC meeting this Thursday 6/22/17

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



Phil,



I thought we decided to pursue: "   • Network Function Change Management” 
as a use case in the use case sub committee instead of a project when we were 
in Beijing. Do we have to discuss this again? Please advice so I can make sure 
the correct experts will dial in.



Thx



Oliver



> On Jun 21, 2017, at 3:16 AM  EDT, Phil Robb  wrote:

> 

> Hello ONAP TSC Members:

> 

> We've been unable to get adequate response from TSC members in the Doodle 
> poll to determine when we could hold extra TSC meetings to close on the 
> remaining project proposals that would like to participate in Release-1.

> 

> Given the urgency of holding these reviews so that development teams can 
> actually get to work coding, we are going to hold a special TSC meeting on 
> Thursday morning during our regular TSC meeting slot, and we are extending 
> the meeting to two hours this week so that we can get through all of the 
> proposals.

> 

> Please look for an updated calendar event to this affect.

> 

> The agenda, including the order for each Project Creation Review is on the 
> TSC Meeting Wiki here: 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_TSC-2BMeeting-2BResources&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=PXUIufLo7FbnyzeFuMKlDoU-6k9WVXTciteWZ2L79wQ&s=hh6Jnd0_UnkYcQf1OMtvbQ_9PLwnAgc0Ek2XYOP-z9A&e=
>  

> 

> As we did before, one TSC member is responsible to "sheperd" the project 
> proposals that fall in their domain.  Please review the list on the agenda, 
> identify the projects that you are to be shepherding, and reach out to the 
> project contact to ensure they are available to present, *and* ensure that 
> there are no outstanding questions/issues from the rest of the TSC that have 
> not been addressed in the project proposals.

> 

> Let's try very hard to get through all of the remaining proposals on 
> Thursday.  If that doesn't work, then we will need to call another special 
> meeting (probably on Friday) to close on all of them.

> 

> Thanks in advance for your help with this. We have project teams *unable* to 
> work until the TSC completes these reviews.

> 

> Best,

> 

> Phil.

> 

> 

> -- 

> Phil Robb

> Executive Director, OpenDaylight Project

> VP Operations - Networking & Orchestration, The Linux Foundation

> (O) 970-229-5949

> (M) 970-420-4292

> Skype: Phil.Robb

> ___

> ONAP-TSC mailing list

> ONAP-TSC@lists.onap.org

> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4&m=m9Kks2xE5W3_0JTf6yJDnEuTUF2hMt9hz0dh9cQ3pG4&s=SAKmpkar1vXIHYgRw9hb0fSzfgzgsdNjYnNmz03j7gw&e=
>  



___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=PXUIufLo7FbnyzeFuMKlDoU-6k9WVXTciteWZ2L79wQ&s=6edJvc-CkTdWXskTcb5hAY388Av5psqzFOoPpfkCl5k&e=
 
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] 答复：RE: [onap-discuss] Question on ONAP Operations Manager (OOM)

2017-06-05 Thread ROSE, DANIEL V

I have reached out to my att colleagues who are working on this project to 
update the page with some clarification once they work with the other members.

Thanks,

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

From: fu.guangr...@zte.com.cn [mailto:fu.guangr...@zte.com.cn]
Sent: Monday, June 05, 2017 10:52 AM
To: r...@m0049295.ppops.net-00191d01; ROSE, DANIEL V 
Cc: onap-disc...@lists.onap.org; onap-tsc@lists.onap.org
Subject: 答复：RE: [onap-discuss] Question on ONAP Operations Manager (OOM)

Hi Daniel,
Thank you for your help.
I suggest you to clarify this on the proposal page of OOM. Otherwise it would 
remain confusing and ambiguous for others.
Have a nice day!
Regards,

Guangrong
原始邮件
发件人:ROSE,DANIELV
收件人:付光荣10144542;onap-disc...@lists.onap.org;onap-tsc@lists.onap.org;
日期:2017-06-05 21:50:22
主题：RE: [onap-discuss] Question on ONAP Operations Manager (OOM)

As I understand it, OOM would take over that role from DCAE Controller. Some of 
DCAE Controller’s paradigms would be moved into OOM.

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> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
fu.guangr...@zte.com.cn<mailto:fu.guangr...@zte.com.cn>
Sent: Monday, June 05, 2017 2:41 AM
To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: [onap-discuss] Question on ONAP Operations Manager (OOM)


Hi there,



After I went through the proposal page of OOM, I feel sort of confused on one 
point. I hope guys for OOM could help to figure it out.

To my understanding, one of the responsibilities of OOM is to manage the 
lifecycle of the ONAP components, as is mentioned on the page "The users can 
also deploy ONAP instances, a component, or a change to a software module 
within a component". But for some components, they have their own controllers 
to manage the lifecycle of their sub-components. Take DCAE for example, 
onboarding of microservices is currently being performed by the DCAE controller 
for analytics applications and data collectors. How does OOM cope with such 
kind of scenario? Will OOM take over the responsibility of the lifecycle 
management of sub-projects/sub-modules?



Regards,

Guangrong








___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [onap-discuss] Question on ONAP Operations Manager (OOM)

2017-06-05 Thread ROSE, DANIEL V

As I understand it, OOM would take over that role from DCAE Controller. Some of 
DCAE Controller’s paradigms would be moved into OOM.

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 
fu.guangr...@zte.com.cn
Sent: Monday, June 05, 2017 2:41 AM
To: onap-disc...@lists.onap.org; onap-tsc@lists.onap.org
Subject: [onap-discuss] Question on ONAP Operations Manager (OOM)


Hi there,



After I went through the proposal page of OOM, I feel sort of confused on one 
point. I hope guys for OOM could help to figure it out.

To my understanding, one of the responsibilities of OOM is to manage the 
lifecycle of the ONAP components, as is mentioned on the page "The users can 
also deploy ONAP instances, a component, or a change to a software module 
within a component". But for some components, they have their own controllers 
to manage the lifecycle of their sub-components. Take DCAE for example, 
onboarding of microservices is currently being performed by the DCAE controller 
for analytics applications and data collectors. How does OOM cope with such 
kind of scenario? Will OOM take over the responsibility of the lifecycle 
management of sub-projects/sub-modules?



Regards,

Guangrong








___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP R1 use cases, and open lab

2017-06-02 Thread ROSE, DANIEL V

Thanks I missed that page. I thought there was some info but wasn’t sure where 
it went!

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

From: Haiby, Ranny (Nokia - US/San Jose USA) [mailto:ranny.ha...@nokia.com]
Sent: Friday, June 02, 2017 11:13 AM
To: ROSE, DANIEL V ; Hellmann, Gil 
; GILBERT, MAZIN E ; 
Dhananjay Pavgi ; onap-tsc@lists.onap.org
Subject: RE: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP 
R1 use cases, and open lab

Hi,

Regarding virtual labs – There is a written definition of the requirements here:
https://wiki.onap.org/display/DW/Virtual+lab<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Virtual-2Blab&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=Ot5QoEbbKoBCNcGaJnuFR0hMgKYndHb4XSfJVA2dPnQ&s=VfPrIAWRQ7qAPexxxqBUvbg4JHlsbKGXKzL_ByrLSCk&e=>

Slide #13 has a summary of the requirements.

Ranny.


From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of ROSE, DANIEL V
Sent: Friday, June 2, 2017 7:16 AM
To: Hellmann, Gil 
mailto:gil.hellm...@windriver.com>>; GILBERT, MAZIN 
E mailto:ma...@research.att.com>>; Dhananjay Pavgi 
mailto:dp00476...@techmahindra.com>>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP 
R1 use cases, and open lab

Gil,


From vendor side:
There is some talk here: 
https://wiki.onap.org/display/DW/Lab+Resource<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Lab-2BResource&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=Ot5QoEbbKoBCNcGaJnuFR0hMgKYndHb4XSfJVA2dPnQ&s=oe2BBMlYK8GbUEfwngKqXHjXcjK7bEZloFX-1FIUsuo&e=>
However most of the stuff written so far has been about physical labs. If you 
are interested more in virtual labs, theres not so much written but there is an 
understanding we may need a virtual lab (ie hardware not owned by us) at some 
point.
Integration project welcomes feedback about that.

From code support side:
https://wiki.onap.org/pages/viewpage.action?pageId=3247262<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D3247262&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=Ot5QoEbbKoBCNcGaJnuFR0hMgKYndHb4XSfJVA2dPnQ&s=6W2UyOZQ897eDMx91GOuwoIvXaNRJyCMbuSDuAv2CXk&e=>
 has vim support that being discussed



Hope that helps,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: Hellmann, Gil [mailto:gil.hellm...@windriver.com]
Sent: Friday, June 02, 2017 10:06 AM
To: ROSE, DANIEL V mailto:dr6...@att.com>>; GILBERT, MAZIN E 
mailto:ma...@research.att.com>>; Dhananjay Pavgi 
mailto:dp00476...@techmahindra.com>>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP 
R1 use cases, and open lab

Hi Daniel,

Do we have a place where we can review the list of requirements ONAP need 
commercial VIM/Cloud vendors to comply with and by when in order to allow them 
to be part of release 1?

I am confident that there are commercial VIM/Cloud vendors which will be happy 
to review them and work toward providing support for release 1.

Best regards,
Gil Hellmann

From: "ROSE, DANIEL V" mailto:dr6...@att.com>>
Date: Friday, June 2, 2017 at 9:52 AM
To: Gil Hellmann 
mailto:gil.hellm...@windriver.com>>, "GILBERT, 
MAZIN E" mailto:ma...@research.att.com>>, Dhananjay 
Pavgi mailto:dp00476...@techmahindra.com>>, 
"onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" 
mailto:onap-tsc@lists.onap.org>>
Subject: RE: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP 
R1 use cases, and open lab

https://wiki.onap.org/pages/viewpage.action?pageId=3247262<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D3247262&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=nwGjhsGkc0EpZil0bDZwLMEd6NJJbusvvHOWbglXOCU&s=N3Xg8ygsKqUUAQzxn4iYosHlZMGZwvjxn5g_qf87Jkw&e=>
 mentions org.onap.multicloud/openstack, org.onap.multicloud/vmware, 
org.onap.multicloud/azure as output so I don’t think commercial vims are out of 
scope. I don’t even think there is a fundamental intolerance to commercial vims 
even in release 1 but like mazin said a release 1 commercial vim may not happen 
if we don’t get everything we need both on the code side to support it and 
vendor side to enable it.


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

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Hellmann, Gil
Sent: Friday, June 02, 2017 8:10 AM
To: GILBERT, MAZIN E mailto:ma..

Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP R1 use cases, and open lab

2017-06-02 Thread ROSE, DANIEL V

Gil,


From vendor side:
There is some talk here: https://wiki.onap.org/display/DW/Lab+Resource
However most of the stuff written so far has been about physical labs. If you 
are interested more in virtual labs, theres not so much written but there is an 
understanding we may need a virtual lab (ie hardware not owned by us) at some 
point.
Integration project welcomes feedback about that.

From code support side:
https://wiki.onap.org/pages/viewpage.action?pageId=3247262 has vim support that 
being discussed



Hope that helps,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: Hellmann, Gil [mailto:gil.hellm...@windriver.com]
Sent: Friday, June 02, 2017 10:06 AM
To: ROSE, DANIEL V ; GILBERT, MAZIN E ; 
Dhananjay Pavgi ; onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP 
R1 use cases, and open lab

Hi Daniel,

Do we have a place where we can review the list of requirements ONAP need 
commercial VIM/Cloud vendors to comply with and by when in order to allow them 
to be part of release 1?

I am confident that there are commercial VIM/Cloud vendors which will be happy 
to review them and work toward providing support for release 1.

Best regards,
Gil Hellmann

From: "ROSE, DANIEL V" mailto:dr6...@att.com>>
Date: Friday, June 2, 2017 at 9:52 AM
To: Gil Hellmann 
mailto:gil.hellm...@windriver.com>>, "GILBERT, 
MAZIN E" mailto:ma...@research.att.com>>, Dhananjay 
Pavgi mailto:dp00476...@techmahindra.com>>, 
"onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" 
mailto:onap-tsc@lists.onap.org>>
Subject: RE: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP 
R1 use cases, and open lab

https://wiki.onap.org/pages/viewpage.action?pageId=3247262<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D3247262&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=nwGjhsGkc0EpZil0bDZwLMEd6NJJbusvvHOWbglXOCU&s=N3Xg8ygsKqUUAQzxn4iYosHlZMGZwvjxn5g_qf87Jkw&e=>
 mentions org.onap.multicloud/openstack, org.onap.multicloud/vmware, 
org.onap.multicloud/azure as output so I don’t think commercial vims are out of 
scope. I don’t even think there is a fundamental intolerance to commercial vims 
even in release 1 but like mazin said a release 1 commercial vim may not happen 
if we don’t get everything we need both on the code side to support it and 
vendor side to enable it.


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

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Hellmann, Gil
Sent: Friday, June 02, 2017 8:10 AM
To: GILBERT, MAZIN E mailto:ma...@research.att.com>>; 
Dhananjay Pavgi 
mailto:dp00476...@techmahindra.com>>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP 
R1 use cases, and open lab

Hi Mazin,

Thanks for the replay. All the points and requirements in your replay below 
make a lot of sense, and should address the use of commercial VNFs in R1, but 
what about the use of commercial infrastructure (NFVI+VIM) as part of R1? The 
VNFs need to run on an infrastructure?

I see that the same rules should be applied to the usage of commercial 
infrastructure. What is the TSC thinking about this?

Best regards,
Gil Hellmann

From: "GILBERT, MAZIN E (MAZIN E)" 
mailto:ma...@research.att.com>>
Date: Friday, June 2, 2017 at 7:50 AM
To: Dhananjay Pavgi 
mailto:dp00476...@techmahindra.com>>, 
"onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" 
mailto:onap-tsc@lists.onap.org>>
Cc: Rajesh Gadiyar mailto:rajesh.gadi...@intel.com>>, 
Gil Hellmann mailto:gil.hellm...@windriver.com>>
Subject: Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP 
R1 use cases, and open lab

Gil,

Thanks for the kind words regarding the ONAP community.
Let me make sure I respond to your question and put this subject to rest
as it was discussed numerous times by the TSC.

1. Our first integrated release (ONAP seeded by ECOMP and Open-O) will be the 
first week of Nov.
This is our goal and the TSC community is committed to this.
2. Two broad sets of services have been identified for vetting the integrated 
release; vEPC/VoLTE and vCPE
3. Each broad use case will have options of open source VNFs and several 
commercial VNFs.
4. It is our desire to use commercial VNFs if we can make our release date; 
otherwise we will revert to Open Source. This means
a. licenses are available in time that is aligned with our release planning,
b. VNFs can be stood up in the ONAP OpenLabs in time that align with our 
release.
c. Developers get complete support during testing, dev and certification
d. VNF vendors are willing to further extend their VNFs to m

Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP R1 use cases, and open lab

2017-06-02 Thread ROSE, DANIEL V

https://wiki.onap.org/pages/viewpage.action?pageId=3247262 mentions 
org.onap.multicloud/openstack, org.onap.multicloud/vmware, 
org.onap.multicloud/azure as output so I don’t think commercial vims are out of 
scope. I don’t even think there is a fundamental intolerance to commercial vims 
even in release 1 but like mazin said a release 1 commercial vim may not happen 
if we don’t get everything we need both on the code side to support it and 
vendor side to enable it.


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

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Hellmann, Gil
Sent: Friday, June 02, 2017 8:10 AM
To: GILBERT, MAZIN E ; Dhananjay Pavgi 
; onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP 
R1 use cases, and open lab

Hi Mazin,

Thanks for the replay. All the points and requirements in your replay below 
make a lot of sense, and should address the use of commercial VNFs in R1, but 
what about the use of commercial infrastructure (NFVI+VIM) as part of R1? The 
VNFs need to run on an infrastructure?

I see that the same rules should be applied to the usage of commercial 
infrastructure. What is the TSC thinking about this?

Best regards,
Gil Hellmann

From: "GILBERT, MAZIN E (MAZIN E)" 
mailto:ma...@research.att.com>>
Date: Friday, June 2, 2017 at 7:50 AM
To: Dhananjay Pavgi 
mailto:dp00476...@techmahindra.com>>, 
"onap-tsc@lists.onap.org" 
mailto:onap-tsc@lists.onap.org>>
Cc: Rajesh Gadiyar mailto:rajesh.gadi...@intel.com>>, 
Gil Hellmann mailto:gil.hellm...@windriver.com>>
Subject: Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP 
R1 use cases, and open lab

Gil,

Thanks for the kind words regarding the ONAP community.
Let me make sure I respond to your question and put this subject to rest
as it was discussed numerous times by the TSC.

1. Our first integrated release (ONAP seeded by ECOMP and Open-O) will be the 
first week of Nov.
This is our goal and the TSC community is committed to this.
2. Two broad sets of services have been identified for vetting the integrated 
release; vEPC/VoLTE and vCPE
3. Each broad use case will have options of open source VNFs and several 
commercial VNFs.
4. It is our desire to use commercial VNFs if we can make our release date; 
otherwise we will revert to Open Source. This means
a. licenses are available in time that is aligned with our release planning,
b. VNFs can be stood up in the ONAP OpenLabs in time that align with our 
release.
c. Developers get complete support during testing, dev and certification
d. VNF vendors are willing to further extend their VNFs to meet our ONAP VNF 
requirements for R1.

I encourage VNF vendors who are interested in meeting those guidelines to sign 
up on our wiki asap.

The TSC is excited about the first release and look forward to working with the 
entire community to
make this a huge success.

Thanks
mazin


On Jun 2, 2017, at 12:27 AM, Dhananjay Pavgi 
mailto:dp00476...@techmahindra.com>> wrote:

+1. For lab having commercial ecosystem of VNFs; we may consider Tech 
Mahindra’s VNFXchange lab.

thanks & regards,
Dhananjay Pavgi
Mobile : +91 98220 22264
   
www.techmahindra.com
 Platinum Member. Visit : 
http://www.onap.org

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Gadiyar, Rajesh
Sent: Friday, June 02, 2017 2:48 AM
To: Hellmann, Gil (Wind River) 
mailto:gil.hellm...@windriver.com>>; 
onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP 
R1 use cases, and open lab

+1

I was taking this as a given. We need a robust vendor/commercial ecosystem of 
VNFs and NFVI software, in addition to open source. I see that the vCPE and 
vVoLTE use case documents on the wiki already incorporate this; which I am 
supportive.

From: mailto:onap-tsc-boun...@lists.onap.org>> 
on behalf of Gil Hellmann 
mailto:gil.hellm...@windriver.com>>
Date: Thursday, June 1, 2017 at 2:08 PM
To: "onap-tsc@lists.onap.org" 
mailto:onap-tsc@lists.onap.org>>
Subject: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP R1 
use cases, and open lab

Dear TSC members,

It is very exciting to see the great momentum and grow in the ONAP community, I 
hear that there is different opinion / debate with regard to whe

Re: [onap-tsc] Call for vCPE VNFs proposals

2017-06-01 Thread ROSE, DANIEL V

Viability to even be included is certainly an important point.

But I think oliver’s point is there is always some work to get a vnf to be onap 
ready, and then some more work to configure it to work in our use case. Someone 
in the ONAP project has to take ownership and agree to either do that work, or 
find someone (possibly the projects actual contributors) to do that work.  This 
is analogous to a vendor who agrees to support their vnf in the use cases we 
use them for.

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 SULLIVAN, BRYAN L
Sent: Thursday, June 01, 2017 10:31 AM
To: SPATSCHECK, OLIVER ; Zhou, Danny 

Cc: onap-discuss ; onap-tsc@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] Call for vCPE VNFs proposals

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Having support info in the table of open source VNFs, as well as notes on 
functional limitations / fitness for a particular purpose, and some consensus 
assessment [limited, viable] or status [experimental, lab-ready, deployed] that 
can change over time, would be useful. There are various types/levels of 
purpose here, and for the community’s need, functionally complete / 
production-ready open source VNFs while clearly a desired goal, are a 
would-be-nice.

Viability would include the level of community support for maintaining or 
further developing the VNF. But some VNFs may be still be viable for particular 
purposes (e.g. in tests for performance or lifecycle automation) even if they 
are incomplete or there is no active community.

Thanks,
Bryan Sullivan | AT&T

From: SPATSCHECK, OLIVER
Sent: Thursday, June 01, 2017 6:07 AM
To: Zhou, Danny mailto:danny.z...@intel.com>>
Cc: SULLIVAN, BRYAN L mailto:bs3...@att.com>>; KLUGER, YOAV 
mailto:yoav.klu...@amdocs.com>>; 
onap-tsc@lists.onap.org; onap-discuss 
mailto:onap-disc...@lists.onap.org>>
Subject: Re: [onap-tsc] Call for vCPE VNFs proposals


Could we also start listing who is supporting the open source VNFs? E.g. even 
the simple open source based VNFs we are using for the current ONAP demo  based 
on the seed code took a couple of people 2 months or so to get to work properly 
in the integration environment. I would assume that for commercial VNFs this 
support will be provided by the vendor. However, for open source VNFs we need 
volunteers to take on that role. I would track those on the Wiki or identify 
them as gaps. If we can’t find that support we can’t use that VNF.

Thx

Oliver

On May 31, 2017, at 11:36 PM, Zhou, Danny 
mailto:danny.z...@intel.com>> wrote:

The wiki 
page
 already lists preferred and usable open source VNFs like below, but the ONOS 
vBNG as open source vBNG and OpenWRT as open source vHGW does not make sense to 
me. Specifically, the ONOS vBNG is essentially a L3 NAT without the 
capabilities to address requirement such as session management, traffic 
aggregation and routing, etc., and in addition to OpenWRT acting as vHGW, VPP 
based high performance Home 
Gateway
 as well 
asvRouter
 should be better.

  *   vDHCP: ISC DHCP
  *   vDNS:   ISC Bind
  *   vAAA:   FreeRADIUS

-Danny Zhou
Intel

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of SULLIVAN, BRYAN L
Sent: Thursday, June 1, 2017 3:36 AM
To: KLUGER, YOAV mailto:yoav.klu...@amdocs.com>>; 
onap-tsc@lists.onap.org; onap-discuss 
mailto:onap-disc...@lists.onap.org>>
Subject: Re: [onap-tsc] Call for vCPE VNFs proposals

I recommend that any available open source implementations of these VNFs also 
be included. I am aware of several potential VNFs as used in the R-CORD 
project, and as being collected through the similar ODL VCO (Virtualized 
Central Office) project. These are being collected and assessed for deployment 
on OPNFV reference platforms as part of the proposed “Edge” project: 
https://wiki.opnfv.org/display/PROJ/Multi-Ac

Re: [onap-tsc] Thoughts on next steps.

2017-05-18 Thread ROSE, DANIEL V

Well reading between the lines of what oliver is kind of saying: when there is 
something like 
https://networkbuilders.intel.com/blog/opening-the-way-to-a-more-efficient-core-network
 (which is a new epc that i havent played with it yet so dont know what it does 
but intel is involved there so maybe they could say) that is opensource, does 
that meet the use cases easier than adding in commercial vnfs do?

Clearly for an interoperability or certification lab we want to take tons of 
commercial vnfs and pnfs but for use cases what do we want to do?

On May 18, 2017, at 9:01 PM, Yunxia Chen 
mailto:helen.c...@huawei.com>> wrote:

Hi, Yuan Yue,
I am very glad that ZTE would like to help on integration testing evn for 
developer. Let’s have a meeting to discuss more details on how this could 
complement with other testing env in Integration project. And I also have 
concern with license and would like to know more. Could some of those skeleton 
VNF code be leveraged inside “reference VNFs project” inside Integration 
project?

Regards,

Helen Chen

From: mailto:onap-tsc-boun...@lists.onap.org>> 
on behalf of "yuan@zte.com.cn" 
mailto:yuan@zte.com.cn>>
Date: Friday, May 19, 2017 at 8:35 AM
To: 
"spatsch...@mail.linuxfoundation.org"
 
mailto:spatsch...@mail.linuxfoundation.org>>,
 "SPATSCHECK, OLIVER" 
mailto:spat...@research.att.com>>
Cc: "onap-tsc@lists.onap.org" 
mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] Thoughts on next steps.


Oliver,



About integration environment,  I totally understand how helpful having a 
integration environment applied for debugging and testing code during 
developing. I should say it was also my dream having a integration environment 
before I write code when I was a developer. But my boss never provided such 
costly convenience to me. I have to write test code for unit test and use test 
tools for integration test during developing. The integrated environment only 
provided for final integration test. I believe most open source practice is 
same with our internal developing in this case. The draft roadmap of ONAP first 
release on wiki shows Test Lab Ready on middle of September, just before R0. So 
my understanding is developing team should use test tools simulating real E2E 
environment during developing.  Deadline of test lab is mid-September not June 
29.



We will provide commercial vNFs with limited license(like only supporting 5 to 
10 end user)  and limited time (like expired after one year) for integrated 
testing. Either Ericsson or Huawei can touch these vNFs in ONAP test lab like 
we have already done in OPEN-O test lab. We are not worry about being stolen of 
a binary vNF while we are keeping upgrading this vNF.



We have three use cases for different purpose. Some operators are interested in 
vCPE while mobile operators regard core network as key requirement for a MANO 
system and developers might prefer simple vFW deployed in Rackspace cloud. I 
agree that all tests should be repeatable in more than one test lab. How many 
test labs and how to run these test labs for three use cases would be discussed 
in integration project.





Best Regards,

Yuan Yue





袁越 yuanyue

资深战略规划师   Senior Strategy Planner

技术规划部/技术规划部/系统产品 Technology Planning Dept./Technology Planning Dept./System 
Product





南京市雨花区软件大道50号中兴通讯3号楼
1/F,Building 3, ZTE Nanjing R&D Center II, No.50, Software Avenue,YuHua 
District,Nanjing,P.R.China 210012

T: +025 88013478
M: +86 13851446442
E: yuan@zte.com.cn
www.zte.com.cn

原始邮件
发件人： ＜spat...@research.att.com＞;
收件人：袁越10008526;
抄送人： ＜onap-tsc@lists.onap.org＞;
日 期 ：2017年05月17日 20:57
主 题 ：Re: [onap-tsc] Thoughts on next steps.



Yuan,

let me separate things a bit.

The way I look at it is that there is a set of use cases which gate the success 
of the release. Those use cases have a set of VNFs.

I completely agree with you that ONAP should support many commercial VNFs. In 
fact I would like all commercial VNFs to be supported by ONAP that’s the 
ultimate goal of AT&T, however, that does not mean that all of them have to be 
part of the set of VNFs used for the use case which gates the release.

Now let’s focus on the VNFs which gate the release as the others can be worked 
using proprietary or bilateral agreements.  As stated below I don’t know how to 
do that efficiently. That doesn’t mean there isn’t a solution. So if you can 
outline one that would be great. I see three main challenges:

1. Developer access to VNFs. From experience you can speed up development 
substantially if you give developers access t

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

2017-05-16 Thread ROSE, DANIEL V

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&AI, 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-disc...@lists.onap.org; onap-tsc@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&AI, 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&AI, 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-tsc@lists.onap.org＞; 
＜onap-disc...@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&AI. When comes to the 
realization, ESR will be realized relying on A&AI (store the external system 
data in A&AI).



Thanks,

LiZi












发件人： ＜jpianigi...@juniper.net＞;
收件人： 
＜stephen.terr...@ericsson.com＞;李滋00164331; 
 ＜onap-tsc@lists.onap.org＞; 
＜onap-disc...@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-tsc@lists.onap.org; 
onap-disc...@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&AI? (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&AI 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-tsc@lists.onap.org; 
onap-disc...@lists.onap.org
Subject: [onap-tsc] Project Proposal: External System Register




Dear ONAP TSC,



We would like to formally propose the External System Register project for ONAP.



ONAP components need to talk with external systems such as VIM/VNFM/SDNC/EMS to 
orchestrate a network service, for example, SO/VF-C need to talk with VIM to 
allocate resource and VNFM   to deploy a VNF. So they should get the 
information of available external systems from a registry before call the 
Interfaces of these external systems.  ESR provides a service to centralized 
management of the information (name, vendor, version, acess end  point,  etc.) 
of external systems. So the ONAP components can get the system information with 
unified API from a logical single point.



The proposal wiki page, which includes details of the project description 
(including sub projects), project scopes, and pr

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

2017-05-15 Thread ROSE, DANIEL V

Hi LiZi,

How would you compare this project with the MSB project?

MSB lists

Service discovery - Server side discovery

and you list

•  Register/query/update/delete function of VIM
•  Register/query/update/delete function of VNFM
•  Register/query/update/delete function of SDN Controller
•  Register/query/update/delete function of EMS.

Can you say how they are different?

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

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of li.z...@zte.com.cn
Sent: Sunday, May 14, 2017 10:32 PM
To: onap-tsc@lists.onap.org; onap-disc...@lists.onap.org
Subject: [onap-tsc] Project Proposal: External System Register




Dear ONAP TSC,



We would like to formally propose the External System Register project for ONAP.



ONAP components need to talk with external systems such as VIM/VNFM/SDNC/EMS to 
orchestrate a network service, for example, SO/VF-C need to talk with VIM to 
allocate resource and VNFM to deploy a VNF. So they should get the information 
of available external systems from a registry before call the Interfaces of 
these external systems.  ESR provides a service to centralized management of 
the information (name, vendor, version, acess end point, etc.) of external 
systems. So the ONAP components can get the system information with unified API 
from a logical single point.



The proposal wiki page, which includes details of the project description 
(including sub projects), project scopes, and proposed repo names, can be found 
at: 
https://wiki.onap.org/display/DW/External+System+Register



Thanks,



LiZi









李滋 lizi



IT开发工程师 IT Development Engineer
网管及服务开发二部/中心研究院/系统产品 Network Management & Service Development Dept. II/Central 
R＆D Institute/System Product


[cid:image001.gif@01D2CD63.08C0DFC0]

[cid:image002.gif@01D2CD63.08C0DFC0]
成都市高新区天府大道中段800号中兴通大厦
ZTE Corporation Building, No. 800 Middle Section Tianfu Avenue,
Chengdu, P..R.China, 610041
M: +86 15583405168
E: li.z...@zte.com.cn
www.zte.com.cn


___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] CI/CD

2017-05-11 Thread ROSE, DANIEL V

I think we can just drop in ONAP to that list were Open-O is.
There is an integration project here in ONAP being proposed so that would apply 
still unless the TSC wants a separate coordinator here instead.


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

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Stephen Terrill
Sent: Thursday, May 11, 2017 4:47 PM
To: onap-tsc 
Subject: [onap-tsc] CI/CD

Hi All,

I've become aware of colloborative work between a number of communities 
regarding CI/CD, where there is information here: 
https://wiki.opnfv.org/display/INF/Infra+Collaboration

I assume it would be good to consider this as well from an ONAP perspective.  
Any ideas on how we should?  Under the integration project? Or opensource 
coordinator?

Best regards,

Steve.


[Ericsson]
STEPHEN TERRILL
Technology Specialist
DUIC, Systems and Technology
Development Unit IP & Cloud
Business Unit, IT & Cloud Products

Ericsson
Ericsson R&D Center, via de los Poblados 13
28033, Madrid, Spain
Phone +34 339 3005
Mobile +34 609 168 515
stephen.terr...@ericsson.com
www.ericsson.com


[http://www.ericsson.com/current_campaign]

Legal entity: Ericsson España S.A, compay registration number ESA288568603. 
This Communication is Confidential. We only send and receive email on the basis 
of the terms set out at 
www.ericsson.com/email_disclaimer

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Seed code for Service Orchestrator

2017-05-11 Thread ROSE, DANIEL V

There has been a ton of change on the page in the last day: 
https://wiki.onap.org/pages/diffpagesbyversion.action?pageId=4719246&selectedPageVersions=29&selectedPageVersions=6

I hope everyone who needed to be involved has been involved because I didn't 
see much public discussion about this project on this mailing lists. 

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

-Original Message-
From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of SPATSCHECK, OLIVER
Sent: Thursday, May 11, 2017 4:05 PM
To: eric.deb...@orange.com; dewa...@gigaspaces.com
Cc: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Seed code for Service Orchestrator

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


So am I.  I thought in the charter we had agreed that the MSO code base would 
be used for this. Similar to the 3 legacy Open-O components.

Was there any discussion on this anywhere?

Thx

Oliver

> On May 11, 2017, at 3:48 PM  EDT, eric.deb...@orange.com wrote:
> 
> Hello
>  
> I am surprised to discover that open-o/gso is considered as the seed code for 
> the Service Orchestrator.
>  
> As far as I know, we never decided such choice during the discussions last 
> week and it should be a TSC decision.
>  
> Regards
>  
> Eric
> _
> 
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
> Thank you.
> 
> ___
> ONAP-TSC mailing list
> ONAP-TSC@lists.onap.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4&m=yopWEEan7upXoI1z2e3hU3o52mzgW69H-rB7ZIT8-A8&s=r3tAPP-TO6TFW9dliuNeUQRkuweOwDof8ZXXYNxy8nw&e=

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=P3ocIvjpt_xeLNXVAxRECvAWNuMr4HDtz-qc9fROO9A&s=e4Ns63-VStxhnMGdv7vWHVfxhjlPO8z9gu3k3E6shes&e=
 
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Project Proposal: ONAP CLI

2017-05-09 Thread ROSE, DANIEL V

As someone worked on the test automation for release 1, I would agree that that 
a powerful rest API is my preferred way of doing it. Not saying there isn’t a 
need for a cli or not, but an ONAP that takes a strong “API First” approach 
would meet testing needs in my opinion.

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

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Sauvageau, David
Sent: Tuesday, May 09, 2017 9:10 AM
To: Dhananjay Pavgi ; FREEMAN, BRIAN D 
; Kanagaraj Manickam ; 
t...@lists.onap.org
Subject: Re: [onap-tsc] Project Proposal: ONAP CLI

Agreed with Brian as well.

Maybe CLI could be added at a later time but to me should not be a priority for 
2017 Release 1.

From: mailto:onap-tsc-boun...@lists.onap.org>> 
on behalf of Dhananjay Pavgi 
mailto:dp00476...@techmahindra.com>>
Date: Tuesday, May 9, 2017 at 8:59 AM
To: "FREEMAN, BRIAN D" mailto:bf1...@att.com>>, Kanagaraj 
Manickam mailto:kanagaraj.manic...@huawei.com>>, 
"t...@lists.onap.org" 
mailto:t...@lists.onap.org>>
Subject: Re: [onap-tsc] Project Proposal: ONAP CLI

Spot on, Brian. You got it.

thanks & regards,
Dhananjay Pavgi
Mobile : +91 98220 22264
[id:image002.png@01CE7323.F2727500]   [NAP_logo_Sig]
www.techmahindra.com
 Platinum Member. Visit : 
http://www.onap.org

From: FREEMAN, BRIAN D [mailto:bf1...@att.com]
Sent: Tuesday, May 09, 2017 10:55 PM
To: Dhananjay Pavgi 
mailto:dp00476...@techmahindra.com>>; Kanagaraj 
Manickam mailto:kanagaraj.manic...@huawei.com>>; 
t...@lists.onap.org
Subject: RE: Project Proposal: ONAP CLI


Scripting is useful but shell scripts that wrap curl  functions are the method 
we are pushing folks towards. Separate CLI and REST API’s are generally a 
waste. With automation we see less pressure to have a CLI and more a need to be 
able to get the work done and CURL/POSTMAN are the tools of the new devops 
environment.

Brian

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Dhananjay Pavgi
Sent: Tuesday, May 09, 2017 6:32 AM
To: Kanagaraj Manickam 
mailto:kanagaraj.manic...@huawei.com>>; 
t...@lists.onap.org
Subject: Re: [onap-tsc] Project Proposal: ONAP CLI

Thanks. Don’t agree with the comment on GUI can’t be used in DevOps. Wonder how 
CLI would be easier in any which ways to work with clumsy yaml/TOSCA files. CLI 
was good for short service commands.

While it would still make sense to have it for VNFs; for some of the reasons 
sighted below. For Network Automation Platform like ONAP; still ponder over 
it’s necessity.

thanks & regards,
Dhananjay Pavgi
Mobile : +91 98220 22264
[id:image002.png@01CE7323.F2727500]   [NAP_logo_Sig]
www.techmahindra.com
 Platinum Member. Visit : 
http://www.onap.org

From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com]
Sent: Tuesday, May 09, 2017 7:37 PM
To: Dhananjay Pavgi 
mailto:dp00476...@techmahindra.com>>; 
t...@lists.onap.org
Subject: RE: Project Proposal: ONAP CLI

Thanks for sharing your comments. Pls find my inputs below:

CLI has its own advantages over GUI in following aspects:

  1.  ONAP Continuous integration (CI), where we want to perform various ONAP 
operations, CLI will be very handy option. This is applicable to 3rd party CI 
as well.
  2.  While GUI is the preferred interface for end-user, back-end operators and 
 admin always prefer CLI (it’s an industry trend !) as its simpler, faster.
  3.  Installation scripting, VNF boot scripting with ONAP.
  4.  Dev testing … integration testing.
  5.  OSS/BSS products would want to perform any automation on top of ONAP, it 
could go either with CLI or SDK.
In short, GUI can’t be used in devops environment, and CLI fills the gap.

In addition, CLI provides an alternate option to GUI,  for operating back ONAP 
functionalities.

And to feel the importance of CLI, Pls refer some existing active automation 
proj

Re: [onap-tsc] [onap-discuss] MSB Technical Deep Dive and ONAP Uses on Friday May 5th

2017-05-05 Thread ROSE, DANIEL V

FYI we are using this room, thanks for the patience.

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

From: Amir Levy [mailto:a...@gigaspaces.com]
Sent: Thursday, May 04, 2017 3:50 PM
To: RAJU, CHINNAPPA ; ROSE, DANIEL V 
Cc: Meador, Guy (CCI-Atlanta) ; Yoram Zini (yzini) 
; onap-disc...@lists.onap.org; onap-tsc@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] MSB Technical Deep Dive and ONAP Uses on 
Friday May 5th

Guys - You can use the following ZOOM bridge. It doesn’t require an host to 
start. It will get recorded in the cloud - so i will send you guys the link 
once the meeting concludes.


Hi there,

Amir Levy is inviting you to a scheduled Zoom meeting.

Topic: MSB Technical Deep Dive and ONAP Uses
Time: May 5, 2017 8:00 AM Eastern Time (US and Canada)

Join from PC, Mac, Linux, iOS or Android: 
https://gigaspaces.zoom.us/j/191174169<https://urldefense.proofpoint.com/v2/url?u=https-3A__gigaspaces.zoom.us_j_191174169&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=4hRWS7q017xk66faJQJT6MwUEpnTD51oLn87E-zJ8ZA&s=vTYZLZ16xdTnFJVgW6Nqb5AJNXIwRlTM5hJS1QBY0Bg&e=>

Or iPhone one-tap (US Toll Free):  +18773690926,191174169#

Or Telephone:
Dial:
+1 877 369 0926 (US Toll Free)
+1 408 638 0968 (US Toll)
+33 (0) 1 8288 0188 (France Toll)
+353 (0) 1 691 7488 (Ireland Toll)
+972 (0) 3 978 6688 (Israel Toll)
+39 069 480 6488 (Italy Toll)
+48 22 307 3488 (Poland Toll)
+44 (0) 20 3695 0088 (United Kingdom Toll)
Meeting ID: 191 174 169
International numbers available: 
https://gigaspaces.zoom.us/zoomconference?m=1m2AOpkdYqD4dnCmtOgbka-bZNT-PM63<https://urldefense.proofpoint.com/v2/url?u=https-3A__gigaspaces.zoom.us_zoomconference-3Fm-3D1m2AOpkdYqD4dnCmtOgbka-2DbZNT-2DPM63&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=4hRWS7q017xk66faJQJT6MwUEpnTD51oLn87E-zJ8ZA&s=6-1G3gF0DQOagTRw8LBRiORVAO5MwdSSZVwAlsA97VM&e=>



On May 4, 2017, at 10:28 AM, RAJU, CHINNAPPA 
mailto:cr7...@att.com>> wrote:

Setup a zoom meeting, non-ATT folks can join as well.


Thanks & Regards,
Chinnappa Raju
SENIOR QUALITY TESTER
ECOMP Open Source Automation

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of ROSE, DANIEL V
Sent: Thursday, May 04, 2017 9:21 AM
To: Meador, Guy (CCI-Atlanta) mailto:guy.mea...@cox.com>>; 
Yoram Zini (yzini) mailto:yz...@cisco.com>>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-tsc] [onap-discuss] MSB Technical Deep Dive and ONAP Uses on 
Friday May 5th

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
I can setup an att connect bridge, I don’t know if I can setup a recording. I 
will reply with what I have here tomorrow.


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> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Meador, Guy 
(CCI-Atlanta)
Sent: Thursday, May 04, 2017 10:20 AM
To: Yoram Zini (yzini) mailto:yz...@cisco.com>>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-discuss] [onap-tsc] MSB Technical Deep Dive and ONAP Uses on 
Friday May 5th

+1


On May 4, 2017, at 9:31 AM, Yoram Zini (yzini) 
mailto:yz...@cisco.com>> wrote:

Hi,

For those who cannot attend Friday’s meetings, I would be very helpful to have 
recorded sessions.

Thanks,
Yoram Zini
Cisco

From: mailto:onap-tsc-boun...@lists.onap.org>> 
on behalf of "ROSE, DANIEL V" mailto:dr6...@att.com>>
Date: Wednesday, May 3, 2017 at 8:41 AM
To: "Arun Arora (c)" mailto:aroraa...@vmware.com>>, 
"zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>" 
mailto:zhao.huab...@zte.com.cn>>, 
"onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" 
mailto:onap-tsc@lists.onap.org>>, 
"onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" 
mailto:onap-disc...@lists.onap.org>>, "SENESTRARO, 
DAVID" mailto:ds2...@att.com>>, "FREEMAN, BRIAN D" 
mailto:bf1...@att.com>>, "SPATSCHECK, OLIVER" 
mailto:spat...@research.att.com>>, "LEFEVRE, 
CATHERINE" mailto:cl6...@intl.att.com>>, "KLEIN, REUBEN" 
mailto:rk1...@att.com>>
Subject: Re: [onap-tsc] [onap-discuss] MSB Technical Deep Dive and ONAP Uses on 
Friday May 5th

I don’t think we have any recording going on for Friday sessions

Thanks,

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

From: Arun Arora (c) [mailto:aroraa...@vmware.co

Re: [onap-tsc] [onap-discuss] MSB Technical Deep Dive and ONAP Uses on Friday May 5th

2017-05-04 Thread ROSE, DANIEL V

I can setup an att connect bridge, I don’t know if I can setup a recording. I 
will reply with what I have here tomorrow.


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 Meador, Guy 
(CCI-Atlanta)
Sent: Thursday, May 04, 2017 10:20 AM
To: Yoram Zini (yzini) 
Cc: onap-disc...@lists.onap.org; onap-tsc@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] MSB Technical Deep Dive and ONAP Uses on 
Friday May 5th

+1


On May 4, 2017, at 9:31 AM, Yoram Zini (yzini) 
mailto:yz...@cisco.com>> wrote:

Hi,

For those who cannot attend Friday’s meetings, I would be very helpful to have 
recorded sessions.

Thanks,
Yoram Zini
Cisco

From: mailto:onap-tsc-boun...@lists.onap.org>> 
on behalf of "ROSE, DANIEL V" mailto:dr6...@att.com>>
Date: Wednesday, May 3, 2017 at 8:41 AM
To: "Arun Arora (c)" mailto:aroraa...@vmware.com>>, 
"zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>" 
mailto:zhao.huab...@zte.com.cn>>, 
"onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" 
mailto:onap-tsc@lists.onap.org>>, 
"onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" 
mailto:onap-disc...@lists.onap.org>>, "SENESTRARO, 
DAVID" mailto:ds2...@att.com>>, "FREEMAN, BRIAN D" 
mailto:bf1...@att.com>>, "SPATSCHECK, OLIVER" 
mailto:spat...@research.att.com>>, "LEFEVRE, 
CATHERINE" mailto:cl6...@intl.att.com>>, "KLEIN, REUBEN" 
mailto:rk1...@att.com>>
Subject: Re: [onap-tsc] [onap-discuss] MSB Technical Deep Dive and ONAP Uses on 
Friday May 5th

I don’t think we have any recording going on for Friday sessions

Thanks,

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

From: Arun Arora (c) [mailto:aroraa...@vmware.com]
Sent: Wednesday, May 03, 2017 6:14 AM
To: zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; ROSE, DANIEL V 
mailto:dr6...@att.com>>; SENESTRARO, DAVID 
mailto:ds2...@att.com>>; FREEMAN, BRIAN D 
mailto:bf1...@att.com>>; SPATSCHECK, OLIVER 
mailto:spat...@research.att.com>>; LEFEVRE, CATHERINE 
mailto:cl6...@intl.att.com>>; KLEIN, REUBEN 
mailto:rk1...@att.com>>
Subject: RE: [onap-discuss] MSB Technical Deep Dive and ONAP Uses on Friday May 
5th

Will the recording of the session be available for people from remote locations 
or for those who cannot join?

Thanks,
Arun

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>
Sent: Wednesday, April 26, 2017 8:10 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
dr6...@att.com<mailto:dr6...@att.com>; ds2...@att.com<mailto:ds2...@att.com>; 
bf1...@att.com<mailto:bf1...@att.com>; 
spat...@research.att.com<mailto:spat...@research.att.com>;cl6...@intl.att.com<mailto:cl6...@intl.att.com>;
 rk1...@att.com<mailto:rk1...@att.com>
Subject: [onap-discuss] MSB Technical Deep Dive and ONAP Uses on Friday May 5th

Hello all

We're happy to let you know that we will have a MSB(Microservice Bus) Technical 
Deep Dive and ONAP Uses breakout on Friday May 5th.
Time:08:00-12:00
Venue: A5-5A05, AT&T Labs, Middletown, NJ

The room can hold around 24-30 people, welcome to join us if you're interested 
in this topic.

MSB features:
• Service Registration & Discovery
• Service routing & load balancing
• Facilitate Service High Availability
• Facilitate centralized authentication and authorization
• Service Management Portal
• Service Healthy Monitoring
• API Metrics and Analytics
• Pluggable Architecture

Best regards,
Daniel & Huabing



___
onap-discuss mailing list
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
https://lists.onap.org/mailman/listinfo/onap-discuss<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=5Y19x1LOG_4qa3QxVlpKBrFiC7EwrqeTiTLSCrYKowI&s=6DBgsD4pyqGO_C8RFpaFe-caGqjr1gxgPpOeljiGzpM&e=>

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [onap-discuss] MSB Technical Deep Dive and ONAP Uses on Friday May 5th

2017-05-03 Thread ROSE, DANIEL V

I don't think we have any recording going on for Friday sessions

Thanks,

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

From: Arun Arora (c) [mailto:aroraa...@vmware.com]
Sent: Wednesday, May 03, 2017 6:14 AM
To: zhao.huab...@zte.com.cn; onap-tsc@lists.onap.org; 
onap-disc...@lists.onap.org; ROSE, DANIEL V ; SENESTRARO, DAVID 
; FREEMAN, BRIAN D ; SPATSCHECK, OLIVER 
; LEFEVRE, CATHERINE ; KLEIN, 
REUBEN 
Subject: RE: [onap-discuss] MSB Technical Deep Dive and ONAP Uses on Friday May 
5th


Will the recording of the session be available for people from remote locations 
or for those who cannot join?



Thanks,

Arun



From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>
Sent: Wednesday, April 26, 2017 8:10 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
dr6...@att.com<mailto:dr6...@att.com>; ds2...@att.com<mailto:ds2...@att.com>; 
bf1...@att.com<mailto:bf1...@att.com>; 
spat...@research.att.com<mailto:spat...@research.att.com>; 
cl6...@intl.att.com<mailto:cl6...@intl.att.com>; 
rk1...@att.com<mailto:rk1...@att.com>
Subject: [onap-discuss] MSB Technical Deep Dive and ONAP Uses on Friday May 5th



Hello all



We're happy to let you know that we will have a MSB(Microservice Bus) Technical 
Deep Dive and ONAP Uses breakout on Friday May 5th.

Time:08:00-12:00

Venue: A5-5A05, AT&T Labs, Middletown, NJ



The room can hold around 24-30 people, welcome to join us if you're interested 
in this topic.



MSB features:

* Service Registration & Discovery

* Service routing & load balancing

* Facilitate Service High Availability

* Facilitate centralized authentication and authorization

* Service Management Portal

* Service Healthy Monitoring

* API Metrics and Analytics

* Pluggable Architecture



Best regards,

Daniel & Huabing






___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Updated TSC Charter

2017-04-21 Thread ROSE, DANIEL V

Would it be fair to say this then?:

The tsc approach described in the charter applies to projects
The tsc approach described in the charter DOES NOT apply to subprojects

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

-Original Message-
From: onap-tsc-bounces at lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of SPATSCHECK, OLIVER
Sent: Friday, April 21, 2017 12:22 PM
To: Ed Warnicke 
Cc: SULLIVAN, BRYAN L ; Ed Warnicke ; 
onap-tsc at lists.onap.org
Subject: Re: [onap-tsc] Updated TSC Charter

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

I guess you could argue that our current code base is not well formed but if 
you look at Gerrit right now you see about 60+ repos for the couple of 
components we have.  

Let?s just start with A. A&AI in my mind is one project. The scope of the 
project is to provide a current inventory for ONAP.  

It consist of 5 repos.

- AAI Chef cookbooks

- AAI Chef environment files

- AAI REST based services

- AAI common logging library

- Loads SDC Models into A&AI

now could we have thrown all of this into one repo? Sure we could have but I 
think they are functionally separate enough that they shouldn?t be in the same 
repo so they can be managed separately (e.g. versioning, patches, releases 
etc?). Also not every ONAP user might use all of them (e.g. somebody might not 
want to use chef and add an ansible repo)

This is true pretty much for every component we have right now as you can see 
in gerrit. 

Now I guess you could argue that we should file a sub project proposal for each 
of those repos but I am not sure if e.g. creating two repos for  Check 
cookbooks and Check environment files is really a decision which needs TSC 
input. That could perfectly be handled by the project team. After all we are 
trusting the project team to write the code so why not trust them with this? 

So in my mind this will either lead to:

A.) unnecessary red tape overhead

B.) people combining things into a single repo because they don?t want to do 
the red tape.

(and believe me I know red tape ?.). Probably you get a bit of both.

Oliver

> On Apr 21, 2017, at 12:07 PM  EDT, Ed Warnicke  wrote:

> 

> Oliver,

> 

> For my edification, can you give an example or two of where a well scoped 
> project would set up multiple repos?

> 

> Ed

> 

> On Fri, Apr 21, 2017 at 8:47 AM, SPATSCHECK, OLIVER (OLIVER)  research.att.com> wrote:

> I have another question on the charter. I just noticed that a project (or sub 
> project) and a repo are the same thing.  I find this to be sub optimal. In my 
> mind a project is a well defined scope of work. A repo has to do with how to 
> optimize my code management.  Am I the only one with the concern that binding 
> the two will force people into sub optimal repo structures?

> 

> Thx

> 

> Oliver

> ___

> ONAP-TSC mailing list

> ONAP-TSC at lists.onap.org

> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=7fQgrg00vjmsI6lDObOMQ5GuJP5yULjerbc7r7aW87k&s=ZSmUVqKmGf-wX91p0D_iHy-NgTvWR5qV7065BPRObr8&e=
>  

> 

___
ONAP-TSC mailing list
ONAP-TSC at lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=7fQgrg00vjmsI6lDObOMQ5GuJP5yULjerbc7r7aW87k&s=ZSmUVqKmGf-wX91p0D_iHy-NgTvWR5qV7065BPRObr8&e=

[onap-tsc] Some questions regarding Controllers in ONAP Architecture

2017-04-18 Thread ROSE, DANIEL V

Dhananjay,

The VIM in our release 1.0.0. reference example is Rackspace in particular and 
we have a beta version of a generic openstack VIM implementation but I think 
you'll see more beyond even openstack soon. MSO talks to the VIMs.

The way I have been describing it is network controller is layer 0-3 and appc 
controller is layer 4-7 but in the ETSI NFV-MANO architecture both would be 
thought of as VNF-M since they both handle various parts of the lifecycle of 
VNFs. MSO also talks to these VNF-Ms, being the NFVO

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

From: Dhananjay Pavgi [mailto:dp00476...@techmahindra.com]
Sent: Tuesday, April 18, 2017 12:23 PM
To: ROSE, DANIEL V ; HU, BIN ; onap-tsc 
at lists.onap.org; discuss at lists.onap.org
Subject: RE: [onap-tsc] Some questions regarding Controllers in ONAP 
Architecture

Can we then say, Network Controller is some sort of VIM and App Controller is 
sort of VNF-m.

thanks & regards,
Dhananjay Pavgi
Mobile : +91 98220 22264
[cid:image002.png at 01CE7323.F2727500]   [ONAP_logo_Sig]
www.techmahindra.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=pJRMzpAZI48vAs1W0RFwUQN6asJWXq2sfpR8psP6jKA&s=83lnXzr79xICpR9jL-FyiPiumwP0tC_OpWbBo8rG8vg&e=>
 Platinum Member. Visit : 
http://www.onap.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.onap.org_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=pJRMzpAZI48vAs1W0RFwUQN6asJWXq2sfpR8psP6jKA&s=lTXn5C5poB4pHrZRZ0a72jrBwy-VAopVK-qNqBhS1iY&e=>

From: onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at 
lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of ROSE, 
DANIEL V
Sent: Tuesday, April 18, 2017 9:33 PM
To: HU, BIN mailto:bh526r at att.com>>; onap-tsc at 
lists.onap.org<mailto:onap-tsc at lists.onap.org>; discuss at 
lists.onap.org<mailto:discuss at lists.onap.org>
Subject: Re: [onap-tsc] Some questions regarding Controllers in ONAP 
Architecture

-  SDN Agent: [1] was a proposal and not how it is implemented 
today so I will leave the discussion of that to someone else but my 
understanding is it would be in the open-o repo (if it exists at all today)
-  Infrastructure Controller: right now its openstack (not just 
nova) but I know we are adding more. MSO would have the multicloud logic (maybe 
via cloudify or something) to handle that. The code you should be looking for 
is the po adapters in MSO 
(https://gerrit.onap.org/r/gitweb?p=mso/libs.git;a=tree;h=refs/heads/release-1.0.0;hb=refs/heads/release-1.0.0<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Dmso_libs.git-3Ba-3Dtree-3Bh-3Drefs_heads_release-2D1.0.0-3Bhb-3Drefs_heads_release-2D1.0.0&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=pJRMzpAZI48vAs1W0RFwUQN6asJWXq2sfpR8psP6jKA&s=e2UijRPqz6R3-V6_hbDmcIVuqHrrWuDPqAdRWy-6ZLs&e=>).
-  Network Controller: SDN-GC is the network controller and is odl 
based. Check out 
https://wiki.onap.org/display/DW/Architecture<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Architecture&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=pJRMzpAZI48vAs1W0RFwUQN6asJWXq2sfpR8psP6jKA&s=cJG2BA14nmTJ1R5byfLw4cbuov_0XTJ9a6dz2Gass4w&e=>
 for the architecture of each part. The extra logic we have like sli is a 
separate docker which is then called by odl at certain points.
-  App Controller: Has the same architecture as SDN-GC (ie is odl + 
sli based). It's basically different karaf plugins and you could run them on 
either platform - it is an architecture distinction more at this point I believe

For either controller Brian freeman can go into more detail.

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

From: onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at 
lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of HU, BIN
Sent: Tuesday, April 18, 2017 11:53 AM
To: onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org>; discuss at 
lists.onap.org<mailto:discuss at lists.onap.org>
Subject: [onap-tsc] Some questions regarding Controllers in ONAP Architecture

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

Reading current ONAP architecture [1] and tutorial of setting up the base ONAP 
stack [2], I have a few questions regarding those controllers:

-  SDN Agent:

o   What is the role, features and functions of SDN Agent? How is it different 
from Network Controller?

o   I couldn't find any code of SDN Agent in ONAP repo [3]. Does anyone know 
where it is?

-  Infrast

[onap-tsc] Some questions regarding Controllers in ONAP Architecture

2017-04-18 Thread ROSE, DANIEL V

-  SDN Agent: [1] was a proposal and not how it is implemented 
today so I will leave the discussion of that to someone else but my 
understanding is it would be in the open-o repo (if it exists at all today)
-  Infrastructure Controller: right now its openstack (not just 
nova) but I know we are adding more. MSO would have the multicloud logic (maybe 
via cloudify or something) to handle that. The code you should be looking for 
is the po adapters in MSO 
(https://gerrit.onap.org/r/gitweb?p=mso/libs.git;a=tree;h=refs/heads/release-1.0.0;hb=refs/heads/release-1.0.0).
-  Network Controller: SDN-GC is the network controller and is odl 
based. Check out https://wiki.onap.org/display/DW/Architecture for the 
architecture of each part. The extra logic we have like sli is a separate 
docker which is then called by odl at certain points.
-  App Controller: Has the same architecture as SDN-GC (ie is odl + 
sli based). It's basically different karaf plugins and you could run them on 
either platform - it is an architecture distinction more at this point I believe

For either controller Brian freeman can go into more detail.

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

From: onap-tsc-bounces at lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of HU, BIN
Sent: Tuesday, April 18, 2017 11:53 AM
To: onap-tsc at lists.onap.org; discuss at lists.onap.org
Subject: [onap-tsc] Some questions regarding Controllers in ONAP Architecture

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

Reading current ONAP architecture [1] and tutorial of setting up the base ONAP 
stack [2], I have a few questions regarding those controllers:

-  SDN Agent:

o   What is the role, features and functions of SDN Agent? How is it different 
from Network Controller?

o   I couldn't find any code of SDN Agent in ONAP repo [3]. Does anyone know 
where it is?

-  Infrastructure Controller:

o   Is it OpenStack Nova? Or is it agnostic of any VIM and OpenStack is just 
one of the VIM?

o   If the intention is to be agnostic of VIM, and support other VIMs, where is 
a plugin/adaptor from architecture point of view?

o   I couldn't find code either in ONAP [3]. Does anyone know where it is?

-  Network Controller:

o   Is it OpenStack Neutron or ODL? Or Neutron with ODL as backend?

o   I found the code in [3], but it seems it only installs ODL there (correct 
me if I am wrong).

o   What is the primary role, features and functions of Network Controller 
other than those in ODL?

-  App Controller:

o   Are we using ODL too as App Controller?

o   Or Is it a container orchestrator or something else?

Appreciate if someone can explain some details, or give the pointer to more 
detailed documentation.

Thanks
Bin

[1] https://wiki.onap.org/display/DW/ONAP at 
ONS2017?preview=/3245268/3245303/ONAP%20Architecture%20Overview%20_Final-1.pdf
[2] 
https://wiki.onap.org/display/DW/Tutorial%3A+Configuring+and+Starting+Up+the+Base+ONAP+Stack
[3] 
https://git.onap.org/

-- next part --
An HTML attachment was scrubbed...
URL:

[onap-tsc] Query on Installing and Setting up ONAP

2017-04-17 Thread ROSE, DANIEL V

Check out the bottom of the page:

https://wiki.onap.org/display/DW/Tutorial%3A+Configuring+and+Starting+Up+the+Base+ONAP+Stack


we may need to move to some clearer spot

Thanks,

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

From: onap-tsc-bounces at lists.onap.org [mailto:onap-tsc-bounces at 
lists.onap.org] On Behalf Of nagendra.kum...@wipro.com
Sent: Monday, April 17, 2017 12:11 AM
To: onap-tsc at lists.onap.org
Subject: [onap-tsc] Query on Installing and Setting up ONAP

Dear Team,

Can you please provide me wiki link / manual for Installing and setting up 
basic ONAP environment as well as minimum system requirements for setting up 
the same? Many Thanks in advance...


Thanks & Best Regards,

[cid:image001.png at 
01D15BB5.EDD2D300]

Nagendra Prabhu Kumble

Senior Architect | NEP - Telecom Testing

Wipro Limited

M +91 (0) 9739480007 |  O +91 (0) 9739480007

Wipro Ltd., No 72, Keonics Electronic City, 560100- Bangalore | India
Email: nagendra.kumble at wipro.com I 
Website: 
www.wipro.com



[cid:image002.png at 01D15BB5.EDD2D300]

DO BUSINESS BETTER

CONSULTING | SYSTEM INTEGRATION | BUSINESS PROCESS SERVICES




[cid:image003.png at 
01D15BB5.EDD2D300]

[cid:image004.png at 
01D15BB5.EDD2D300]

[cid:image005.png at 
01D15BB5.EDD2D300]

[cid:image006.png at 
01D15BB5.EDD2D300]





The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. WARNING: Computer viruses can be transmitted via email. The 
recipient should check this email and any attachments for the presence of 
viruses. The company accepts no liability for any damage caused by any virus 
transmitted by this email. www.wipro.com
-- next part --
An HTML attachment was scrubbed...
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 29190 bytes
Desc: image001.png
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1775 bytes
Desc: image002.png
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 934 bytes
Desc: image003.png
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 906 bytes
Desc: image004.png
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 1038 bytes
Desc: image005.png
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 1115 bytes
Desc: image006.png
U

Re: [onap-tsc] Suggestion to have component wise mailing list to declutter onap-discuss / tsc

Re: [onap-tsc] Optimization framework

Re: [onap-tsc] Special (and longer) TSC meeting this Thursday 6/22/17

Re: [onap-tsc] 答复：RE: [onap-discuss] Question on ONAP Operations Manager (OOM)

Re: [onap-tsc] [onap-discuss] Question on ONAP Operations Manager (OOM)

Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP R1 use cases, and open lab

Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP R1 use cases, and open lab

Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP R1 use cases, and open lab

Re: [onap-tsc] Call for vCPE VNFs proposals

Re: [onap-tsc] Thoughts on next steps.

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

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

Re: [onap-tsc] CI/CD

Re: [onap-tsc] Seed code for Service Orchestrator

Re: [onap-tsc] Project Proposal: ONAP CLI

Re: [onap-tsc] [onap-discuss] MSB Technical Deep Dive and ONAP Uses on Friday May 5th

Re: [onap-tsc] [onap-discuss] MSB Technical Deep Dive and ONAP Uses on Friday May 5th

Re: [onap-tsc] [onap-discuss] MSB Technical Deep Dive and ONAP Uses on Friday May 5th

[onap-tsc] Updated TSC Charter

[onap-tsc] Some questions regarding Controllers in ONAP Architecture

[onap-tsc] Some questions regarding Controllers in ONAP Architecture

[onap-tsc] Query on Installing and Setting up ONAP

22 matches

Site Navigation

Mail list logo

Footer information