date:20170526

Re: [onap-tsc] wiki and conference calls

2017-05-26 Thread Casey Cain

I will echo a bit of what Ed and Bob stated.
We mostly use the IRC bot to capture the minutes.
I will soon create a page under "Getting Involved" called "Community
Meetings".
I will post the calendar there as well as the information for connecting to
the various community meetings and a link to the meeting minutes archive
(IRC and Zoom Recordings).

Best,
Casey

On Fri, May 26, 2017 at 10:55 AM, Bob Monkman  wrote:

> Right…the IRC bot process we use in OPNFV likewise records all minutes
> using webchat IRC commands into a specific directory for each channel
> created for a project. When we #endmeeting, I get the links to my saved
> minutes files and can save them under the meetings directory of my project
> wiki page. Super easy for me as a non-engineer project lead. 
>
>
>
> I recommend a similar process for ONAP.
>
> Bob
>
>
>
> Robert (Bob) Monkman
>
> Networking Software Strategy & Ecosystem Programs
>
> ARM
>
> 150 Rose Orchard Way
>
> San Jose, Ca 95134
>
> M: +1.510.676.5490 <(510)%20676-5490>
>
> Skype: robert.monkman
>
>
>
> *From:* onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-bounces@
> lists.onap.org] *On Behalf Of *Ed Warnicke
> *Sent:* Friday, May 26, 2017 10:05 AM
> *To:* Danny Lin 
> *Cc:* SPATSCHECK, OLIVER (OLIVER) ; onap-tsc <
> onap-tsc@lists.onap.org>
>
> *Subject:* Re: [onap-tsc] wiki and conference calls
>
>
>
> In many other communities, when a project get's approved it creates its
> own wiki page which has sub pages for things like its meetings, meeting
> minutes, etc.  Keeping IRC meeting minutes is a great practice, and highly
> recommended.  Do do that you can create and onap-* IRC channel and open a
> helpdesk ticket to add meetbot to it.
>
>
>
> Examples:
>
> https://wiki.fd.io/view/VPP <- VPP project page at fd.io
>
> https://wiki.fd.io/view/VPP/Meeting <- VPP project meeting page listing
> logistics, agenda, link to meeting minutes
>
> https://wiki.fd.io/view/VPP/project-meeting-minutes <- VPP project
> meeting minutes
>
> https://wiki.fd.io/view/IRC <- fd.io index of IRC channels
>
> https://wiki.fd.io/view/Meetings <- fd.io index of public meetings
>
>
>
> The goal is aggressive openness, not just making things publicly
> available, but easy to find.  Having a common pattern around project wiki
> pages etc is very helpful for that.
>
>
>
> Ed
>
>
>
>
>
> On Fri, May 26, 2017 at 8:58 AM, Danny Lin  wrote:
>
> +1
>
>
>
> In our Multi-Cloud project, we have discussed the similar issue, in a
> slightly different context. We typically record all meetings, and also have
> a meeting note. We are wondering if we should post these recording and
> meeting notes, and if so, where?
>
>
>
> Danny
>
>
>
> *From: * on behalf of Ed Warnicke <
> hagb...@gmail.com>
> *Date: *Friday, May 26, 2017 at 8:35 AM
> *To: *"SPATSCHECK, OLIVER (OLIVER)" 
> *Cc: *onap-tsc 
> *Subject: *Re: [onap-tsc] wiki and conference calls
>
>
>
> +1k
>
>
>
> I would strongly suggest we adopt the community norm that its totally cool
> for teams to start calls/IRC channels but they *really* need to list them
> in a central index so people can find them.  Aggressive Openness :)
>
>
>
> Ed
>
>
>
> On Fri, May 26, 2017 at 8:03 AM, SPATSCHECK, OLIVER (OLIVER) <
> spat...@research.att.com> wrote:
>
>
> I noticed that a substantial number of teams are starting either ad hoc or
> weekly conference calls.  As I think it’s great that the community is
> forming I am wondering if we can start tracking those calls on the ONAP
> wiki page  (can we add a calendar or something like that?).
>
> This would make it much easier to stay on top of attending the correct
> meetings … .
>
> Thx
>
> Oliver
> ___
> ONAP-TSC mailing list
> ONAP-TSC@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-tsc
> 
>
>
>
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
>
> ___
> ONAP-TSC mailing list
> ONAP-TSC@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-tsc
>
>


-- 
Casey Cain
Technical Program Manager
Linux Foundation
_
IRC - CaseyODL
Skype - wrathwolfk
WeChat - okaru6
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] project proposal: VNF SDK

2017-05-26 Thread Christopher Donley (Chris)

Dear ONAP TSC,

The VNF SDK team would like to formally propose the VNF SDK project: 
https://wiki.onap.org/display/DW/VNF+SDK.

Note that we have adjusted the scope of this project and split the original 
proposal into three parts.  VNF SDK (this project) is focused on developing 
tools for VNF packaging and validation.  It will work closely with two 
independent projects: VNF Requirements project 
(https://wiki.onap.org/display/DW/VNF+Requirements) and VNF Validation Program 
(TBD) projects, which will handle vnf guidelines and compliance/validation, 
respectively.

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

Re: [onap-tsc] [onap-discuss] ONAP Architecture subcommittee kickoff

2017-05-26 Thread Christopher Donley (Chris)

Team,

Just to clarify, this is a one-time meeting proposal.  There were limited slots 
next week, and this is the best I could find.  Next week, we will discuss 
recurring meeting times for future meetings.

Chris
From: Lingli Deng [mailto:denglin...@chinamobile.com]
Sent: Friday, May 26, 2017 5:17 PM
To: denghui (L); Christopher Donley (Chris); onap-tsc@lists.onap.org; 
onap-disc...@lists.onap.org
Subject: RE: [onap-discuss] [onap-tsc] ONAP Architecture subcommittee kickoff

Hui,

Thanks for the clarification.
Sorry for the confusion.

Lingli

From: denghui (L) [mailto:denghu...@huawei.com]
Sent: 2017年5月27日 8:12
To: Lingli Deng ; Christopher Donley (Chris) 
; onap-tsc@lists.onap.org; 
onap-disc...@lists.onap.org
Subject: RE: [onap-discuss] [onap-tsc] ONAP Architecture subcommittee kickoff

Lingli,

It doesn’t conflict with modeling (PDT 6-7AM), architecture will be PDT 8-9AM

Best regards,

DENG Hui

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Lingli Deng
Sent: Saturday, May 27, 2017 7:55 AM
To: Christopher Donley (Chris); 
onap-tsc@lists.onap.org; 
onap-disc...@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] ONAP Architecture subcommittee kickoff

Hi Chris,

Thanks for the arrangements.

I am interested to join but found a conflict with modeling weekly calls.
Will the suggested time slot be used for subsequent routine calls or is it only 
a one-time suggestion?
Since I expect several people including myself to be regularly attending both 
meeting series, would you consider the possibility that we might reschedule it 
to another slot?

Thanks again,
Lingli

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Christopher Donley (Chris)
Sent: 2017年5月27日 7:44
To: onap-tsc@lists.onap.org; 
onap-disc...@lists.onap.org
Subject: [onap-tsc] ONAP Architecture subcommittee kickoff

Dear ONAP community,

This is a call-for-participation message for our newly created architecture 
subcommittee.

We will have a kickoff meeting next Tuesday, May 30 at 1500 UTC.  Preliminary 
agenda includes:

  *   Introductions
  *   Discuss subcommittee goals, roles, purpose, processes/tools/communication 
mechanisms, and formation next steps
  *   Recurring meeting dates/times
  *   Discuss the starting point and open issues 
(https://wiki.onap.org/download/attachments/3245203/ONAP%20Architecture%20Evolution%2005022017_v7.pptx?version=1=1493761356000=v2)
  *   As time permits, continue the SO-APP-C-VF-C discussion


For those interested in joining, here are the logistics:
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/525972941

Or iPhone one-tap (US Toll):  +16465588656,525972941# or +14086380968,525972941#

Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
Meeting ID: 525 972 941
International numbers available: 
https://zoom.us/zoomconference?m=TTavi4JgYzPQg9seHf6L8GWCn-g6ehUy

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

Re: [onap-tsc] [onap-discuss] ONAP Architecture subcommittee kickoff

2017-05-26 Thread Lingli Deng

Hui,

 

Thanks for the clarification.

Sorry for the confusion.

 

Lingli

 

From: denghui (L) [mailto:denghu...@huawei.com] 
Sent: 2017年5月27日 8:12
To: Lingli Deng ; Christopher Donley (Chris)
; onap-tsc@lists.onap.org;
onap-disc...@lists.onap.org
Subject: RE: [onap-discuss] [onap-tsc] ONAP Architecture subcommittee
kickoff

 

Lingli, 

 

It doesn’t conflict with modeling (PDT 6-7AM), architecture will be PDT
8-9AM

 

Best regards,

 

DENG Hui

 

From: onap-discuss-boun...@lists.onap.org

[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Lingli Deng
Sent: Saturday, May 27, 2017 7:55 AM
To: Christopher Donley (Chris); onap-tsc@lists.onap.org
 ; onap-disc...@lists.onap.org
 
Subject: Re: [onap-discuss] [onap-tsc] ONAP Architecture subcommittee
kickoff

 

Hi Chris,

 

Thanks for the arrangements. 

 

I am interested to join but found a conflict with modeling weekly calls.

Will the suggested time slot be used for subsequent routine calls or is it
only a one-time suggestion?

Since I expect several people including myself to be regularly attending
both meeting series, would you consider the possibility that we might
reschedule it to another slot?

 

Thanks again,

Lingli

 

From: onap-tsc-boun...@lists.onap.org

[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Christopher Donley
(Chris)
Sent: 2017年5月27日 7:44
To: onap-tsc@lists.onap.org  ;
onap-disc...@lists.onap.org  
Subject: [onap-tsc] ONAP Architecture subcommittee kickoff

 

Dear ONAP community,

 

This is a call-for-participation message for our newly created architecture
subcommittee.

 

We will have a kickoff meeting next Tuesday, May 30 at 1500 UTC.
Preliminary agenda includes:

*   Introductions
*   Discuss subcommittee goals, roles, purpose,
processes/tools/communication mechanisms, and formation next steps
*   Recurring meeting dates/times
*   Discuss the starting point and open issues
(https://wiki.onap.org/download/attachments/3245203/ONAP%20Architecture%20Ev
olution%2005022017_v7.pptx?version=1

=1493761356000=v2)
*   As time permits, continue the SO-APP-C-VF-C discussion 

 

 

For those interested in joining, here are the logistics:

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/525972941

 

Or iPhone one-tap (US Toll):  +16465588656,525972941# or
+14086380968,525972941#

 

Or Telephone:

Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)

Meeting ID: 525 972 941

International numbers available:
https://zoom.us/zoomconference?m=TTavi4JgYzPQg9seHf6L8GWCn-g6ehUy

 

Chris

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

Re: [onap-tsc] [onap-discuss] ONAP Architecture subcommittee kickoff

2017-05-26 Thread denghui (L)

Lingli,

It doesn’t conflict with modeling (PDT 6-7AM), architecture will be PDT 8-9AM

Best regards,

DENG Hui

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Lingli Deng
Sent: Saturday, May 27, 2017 7:55 AM
To: Christopher Donley (Chris); onap-tsc@lists.onap.org; 
onap-disc...@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] ONAP Architecture subcommittee kickoff

Hi Chris,

Thanks for the arrangements.

I am interested to join but found a conflict with modeling weekly calls.
Will the suggested time slot be used for subsequent routine calls or is it only 
a one-time suggestion?
Since I expect several people including myself to be regularly attending both 
meeting series, would you consider the possibility that we might reschedule it 
to another slot?

Thanks again,
Lingli

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Christopher Donley (Chris)
Sent: 2017年5月27日 7:44
To: onap-tsc@lists.onap.org; 
onap-disc...@lists.onap.org
Subject: [onap-tsc] ONAP Architecture subcommittee kickoff

Dear ONAP community,

This is a call-for-participation message for our newly created architecture 
subcommittee.

We will have a kickoff meeting next Tuesday, May 30 at 1500 UTC.  Preliminary 
agenda includes:

  *   Introductions
  *   Discuss subcommittee goals, roles, purpose, processes/tools/communication 
mechanisms, and formation next steps
  *   Recurring meeting dates/times
  *   Discuss the starting point and open issues 
(https://wiki.onap.org/download/attachments/3245203/ONAP%20Architecture%20Evolution%2005022017_v7.pptx?version=1=1493761356000=v2)
  *   As time permits, continue the SO-APP-C-VF-C discussion


For those interested in joining, here are the logistics:
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/525972941

Or iPhone one-tap (US Toll):  +16465588656,525972941# or +14086380968,525972941#

Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
Meeting ID: 525 972 941
International numbers available: 
https://zoom.us/zoomconference?m=TTavi4JgYzPQg9seHf6L8GWCn-g6ehUy

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

Re: [onap-tsc] [onap-tsc-private] Lab and Intgeration

2017-05-26 Thread John Zannos

Makes sense but you may still follow open-o model of ramping up labs. Given 
size and interest of ONAP it may take a little time to align across the 
community. 

Best 
John 

John Zannos

> On May 26, 2017, at 7:44 PM, Lingli Deng  wrote:
> 
> To clarify, I fully agree to the considerations on having different types of 
> physical/virtual/CICI labs. However, not having a strong opinion on whether 
> or not to consolidate the different teams.
>  
> OPEN-O operated with one lab with Release 1 and added another in Release 2, 
> we had separate sub-teams for labs because the tasks and people involved are 
> rather different from CI/CD integration team.
> Considering the interest we have so far, ONAP is likely to start with several 
> physical labs, and virtual labs in the same time. It might make sense to 
> separate it from CI/CD integration.
>  
> Lingli
>  
> From: onap-tsc-boun...@lists.onap.org 
> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Lingli
> Sent: 2017年5月27日 7:01
> To: Chen Yan 
> Cc: xiexj...@chinatelecom.cn; onap-tsc@lists.onap.org
> Subject: Re: [onap-tsc] [onap-tsc-private] Lab and Intgeration
>  
> +1 
> 
> Lingli
>  
>  
> China Mobile Research Institute
> On 05/26/2017 23:33, Chen Yan wrote:
> Dear TSC,
>  
> From the above discussions we learned the opinions of the ONAP members on 
> Open Lab. As Xiaojun mentioned, China Telecom would like to provide a 
> physical lab for ONAP. Actually,  in last year, China Telecom has already 
> established a Physical Lab for Open-O mercury release, and finished the E2E 
> connection test for vCPE extension use case.
>  
> In the near future, a Physical Lab is still important and necessary, 
> especially for operators with intention to deploy operational systems to 
> manage not only the NFV networks/VNFs but also PNFs.
> China Telecom is going to introduce SDN techniques in our Backbone Network, 
> e.g. Segment routing and TE. In this case, SDN enabled Physical Network and a 
> corresponding Lab is our scope of works.
>  
> I would suggest to build up multiple labs, including Virtual labs and 
> Physical labs, and solving connectivity issues under integration team/LF 
> governance, in order to address on different use cases covering most of the 
> operators interests.
>  
> Best Regards
> Chen Yan
>  
> 发件人: xiexj...@chinatelecom.cn [mailto:xiexj...@chinatelecom.cn] 
> 发送时间: 2017年5月23日,星期二 09:56
> 收件人: Deng邓灵莉/Lingli; roberto.k...@orange.com; Haiby, Ranny (Nokia - US/San 
> Jose USA); Christopher.Donley; 'Jason Hunt'; MAZIN E GILBERT; sunqiong.bri
> 抄送: tsc-priv...@lists.onap.org; SPATSCHECK, OLIVER \(OLIVER\); 'Yunxia Chen'
> 主题: Re: Re: [onap-tsc-private] Lab and Intgeration
>  
> China Telecom also has a lab for OPEN-O. Based on this lab, China Telecom is 
> willing to provide a physical lab for ONAP too.
>  
> Best Regards,
>  
> Xiaojun 
>  
> From: Lingli Deng
> Date: 2017-05-23 09:05
> To: roberto.k...@orange.com; 'Haiby, Ranny \(Nokia - US/San Jose USA\)'; 
> 'Christopher Donley \(Chris\)'; 'Jason Hunt'; ma...@research.att.com
> CC: tsc-private; spatsch; 'Yunxia Chen'
> Subject: Re: [onap-tsc-private] Lab and Intgeration
> China Mobile is willing to provide a physical lab too, based on the existing 
> OPEN-O lab and do enhancement as needed.
>  
> Lingli
>  
> From: onap-tsc-private-boun...@lists.onap.org 
> [mailto:onap-tsc-private-boun...@lists.onap.org] On Behalf Of 
> roberto.k...@orange.com
> Sent: 2017年5月23日 8:28
> To: Haiby, Ranny (Nokia - US/San Jose USA) ; 
> Christopher Donley (Chris) ; Jason Hunt 
> ; ma...@research.att.com
> Cc: Yunxia Chen ; tsc-priv...@lists.onap.org; 
> spat...@research.att.com
> Subject: Re: [onap-tsc-private] Lab and Intgeration
>  
> Orange is willing to provide a physical lab with connectivity from remote, or 
> be part of the set up of the virtual lab.
>  
> I think that what is important is to have clear specification of what is 
> required (Open-O experience would help) asap, so that we can start to 
> implement. This may be independent from the integration project if it allows 
> us to be more efficient. 
>  
> RK
>  
> PS: actually, today we have an operation lab that is shared (from our 
> internal research, our work with universities to our testing for deployment). 
> So the set up would be done marginally. We need to see the tooling of course.
>  
> De : onap-tsc-private-boun...@lists.onap.org 
> [mailto:onap-tsc-private-boun...@lists.onap.org] De la part de Haiby, Ranny 
> (Nokia - US/San Jose USA)
> Envoyé : mardi 23 mai 2017 02:03
> À : Christopher Donley (Chris); Jason Hunt; ma...@research.att.com
> Cc : tsc-priv...@lists.onap.org; spat...@research.att.com; Yunxia Chen
> Objet : Re: [onap-tsc-private] Lab and Intgeration
>  
> Chris,
>  
> You actually bring up an excellent point. In order to demonstrate and test 
> real life scenarios

Re: [onap-tsc] ONAP Architecture subcommittee kickoff

2017-05-26 Thread Lingli Deng

Hi Chris,

 

Thanks for the arrangements. 

 

I am interested to join but found a conflict with modeling weekly calls.

Will the suggested time slot be used for subsequent routine calls or is it
only a one-time suggestion?

Since I expect several people including myself to be regularly attending
both meeting series, would you consider the possibility that we might
reschedule it to another slot?

 

Thanks again,

Lingli

 

From: onap-tsc-boun...@lists.onap.org
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Christopher Donley
(Chris)
Sent: 2017年5月27日 7:44
To: onap-tsc@lists.onap.org; onap-disc...@lists.onap.org
Subject: [onap-tsc] ONAP Architecture subcommittee kickoff

 

Dear ONAP community,

 

This is a call-for-participation message for our newly created architecture
subcommittee.

 

We will have a kickoff meeting next Tuesday, May 30 at 1500 UTC.
Preliminary agenda includes:

*   Introductions
*   Discuss subcommittee goals, roles, purpose,
processes/tools/communication mechanisms, and formation next steps
*   Recurring meeting dates/times
*   Discuss the starting point and open issues
(https://wiki.onap.org/download/attachments/3245203/ONAP%20Architecture%20Ev
olution%2005022017_v7.pptx?version=1

=1493761356000=v2)
*   As time permits, continue the SO-APP-C-VF-C discussion 

 

 

For those interested in joining, here are the logistics:

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/525972941

 

Or iPhone one-tap (US Toll):  +16465588656,525972941# or
+14086380968,525972941#

 

Or Telephone:

Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)

Meeting ID: 525 972 941

International numbers available:
https://zoom.us/zoomconference?m=TTavi4JgYzPQg9seHf6L8GWCn-g6ehUy

 

Chris

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

Re: [onap-tsc] [onap-tsc-private] Lab and Intgeration

2017-05-26 Thread Lingli Deng

To clarify, I fully agree to the considerations on having different types of 
physical/virtual/CICI labs. However, not having a strong opinion on whether or 
not to consolidate the different teams. 

OPEN-O operated with one lab with Release 1 and added another in Release 2, we 
had separate sub-teams for labs because the tasks and people involved are 
rather different from CI/CD integration team. 

Considering the interest we have so far, ONAP is likely to start with several 
physical labs, and virtual labs in the same time. It might make sense to 
separate it from CI/CD integration.

Lingli

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Lingli
Sent: 2017年5月27日 7:01
To: Chen Yan 
Cc: xiexj...@chinatelecom.cn; onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] [onap-tsc-private] Lab and Intgeration

+1 

Lingli

China Mobile Research Institute 

On 05/26/2017 23:33,   Chen Yan wrote: 

Dear TSC,

>From the above discussions we learned the opinions of the ONAP members on Open 
>Lab. As Xiaojun mentioned, China Telecom would like to provide a physical lab 
>for ONAP. Actually,  in last year, China Telecom has already established a 
>Physical Lab for Open-O mercury release, and finished the E2E connection test 
>for vCPE extension use case.

In the near future, a Physical Lab is still important and necessary, especially 
for operators with intention to deploy operational systems to manage not only 
the NFV networks/VNFs but also PNFs.

China Telecom is going to introduce SDN techniques in our Backbone Network, 
e.g. Segment routing and TE. In this case, SDN enabled Physical Network and a 
corresponding Lab is our scope of works.

I would suggest to build up multiple labs, including Virtual labs and Physical 
labs, and solving connectivity issues under integration team/LF governance, in 
order to address on different use cases covering most of the operators 
interests.

Best Regards

Chen Yan

发件人: xiexj...@chinatelecom.cn   
[mailto:xiexj...@chinatelecom.cn] 
发送时间: 2017年5月23日,星期二 09:56
收件人: Deng邓灵莉/Lingli; roberto.k...@orange.com  ; 
Haiby, Ranny (Nokia - US/San Jose USA); Christopher.Donley; 'Jason Hunt'; MAZIN 
E GILBERT; sunqiong.bri
抄送: tsc-priv...@lists.onap.org  ; 
SPATSCHECK, OLIVER \(OLIVER\); 'Yunxia Chen'
主题: Re: Re: [onap-tsc-private] Lab and Intgeration

China Telecom also has a lab for OPEN-O. Based on this lab, China Telecom is 
willing to provide a physical lab for ONAP too.

Best Regards,

Xiaojun 

From: Lingli Deng  

Date: 2017-05-23 09:05

To: roberto.k...@orange.com  ; 'Haiby, Ranny 
\(Nokia - US/San Jose USA\)'  ; 'Christopher 
Donley \(Chris\)'  ; 'Jason Hunt' 
 ; ma...@research.att.com 

CC: tsc-private  ; spatsch 
 ; 'Yunxia Chen' 

Subject: Re: [onap-tsc-private] Lab and Intgeration

China Mobile is willing to provide a physical lab too, based on the existing 
OPEN-O lab and do enhancement as needed.

Lingli

From: onap-tsc-private-boun...@lists.onap.org 

[mailto:onap-tsc-private-boun...@lists.onap.org] On Behalf Of 
roberto.k...@orange.com  
Sent: 2017年5月23日 8:28
To: Haiby, Ranny (Nokia - US/San Jose USA)  >; Christopher Donley (Chris) 
 >; Jason 
Hunt  >; ma...@research.att.com 

Cc: Yunxia Chen  >; 
tsc-priv...@lists.onap.org  ; 
spat...@research.att.com  
Subject: Re: [onap-tsc-private] Lab and Intgeration

Orange is willing to provide a physical lab with connectivity from remote, or 
be part of the set up of the virtual lab.

I think that what is important is to have clear specification of what is 
required (Open-O experience would help) asap, so that we can start to 
implement. This may be independent from the integration project if it allows us 
to be more efficient. 

RK

PS: actually, today we have an operation lab that is shared (from our internal 
research, our work with universities to our testing for deployment). So the set 
up would be done marginally. We need to see the tooling of course. 

De : onap-tsc-private-boun...@lists.onap.org

[onap-tsc] Schedule for ONAP Project Proposal Initial Feedback

2017-05-26 Thread Phil Robb

Hello OpenDaylight TSC Members.

As you all know we have many initial project proposals to review, reconcile
and (hopefully) approve over the next couple of weeks.

As Mazin has stated earlier, we will be doing this in a couple of different
steps:
First, we will break into teams focused on different groups of proposals.
You all have already signed up for the various groups and we appreciate
your participation.  These groups will meet multiple times next week to
ensure we get through all of the projects and provide some initial feedback
to each project so that they have time to modify/refine their proposal
prior to their formal Creation Review if needed.  Please look for meeting
invitations for these initial discussions shortly receiving this email.

Second, during the Face to Face meeting on June 8th and 9th, we will be
conducting formal creation reviews for those projects requesting them (as
time permits).  Our goal is to at least get through the Creation Reviews
for the initial key projects necessary to support the First Release.  We
will continue to perform Creation Reviews at subsequent TSC meetings if we
are unable to get through all of the projects during the Face to Face.

As requested, I've created a wiki page where we can collect and collate
*TSC Member* feedback to the projects.  That wiki page is located here:
https://wiki.onap.org/display/DW/Initial+Project+Proposal+Feedback+From+the+TSC
... Please use that wiki page to post your comments and/or "+1" comments
made by other TSC Members.
A note to ONAP technical community members that are not part of the TSC.
We also welcome your input on project proposals but please do not use the
above wiki to post your comments.  The above wiki is reserved for TSC
member usage.  If you are not a voting member on the TSC then please
provide your feedback on project proposals via the "Comments" feature
within the Project Proposal's wiki page.

As a reminder TSC Members, the ruberic to keep in mind when performing your
initial review of each proposal is below:

Framework for TSC Project Feedback

1.Clarity

a. Reasonable and well defined scope

b.Identification of software modules and APIs being developed and
delivered to ONAP and other components.

c. Following project and LF guidelines for contributors/committers

d.Identification of dependencies and assumptions on other components
and open source.

2.Overlap

a. Intentional and unintentional overlap

b.Overlap with external open source efforts

3.Risk management

a. Sufficient development resources allocated to deliver on time

b.At least 3-4 companies involved to provide diversity

c. Availability of seed code and its maturity

4.Relevance and prioritization

a. Alignment with merger release

b.Alignment with use cases

c.Sound technical solution for solving a real need
If you have any questions, please do not hesitate to contact me.

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://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [onap-tsc-private] Lab and Intgeration

2017-05-26 Thread Lingli

Dear TSC, From the above discussions we learned the opinions of the ONAP members on Open Lab. As Xiaojun mentioned, China Telecom would like to provide a physical lab for ONAP. Actually,  in last year, China Telecom has already established a Physical Lab for Open-O mercury release, and finished the E2E connection test for vCPE extension use case. In the near future, a Physical Lab is still important and necessary, especially for operators with intention to deploy operational systems to manage not only the NFV networks/VNFs but also PNFs.China Telecom is going to introduce SDN techniques in our Backbone Network, e.g. Segment routing and TE. In this case, SDN enabled Physical Network and a corresponding Lab is our scope of works. I would suggest to build up multiple labs, including Virtual labs and Physical labs, and solving connectivity issues under integration team/LF governance, in order to address on different use cases covering most of the operators interests. Best RegardsChen Yan 发件人: xiexj...@chinatelecom.cn [mailto:xiexj...@chinatelecom.cn] 发送时间: 2017年5月23日,星期二 09:56收件人: Deng邓灵莉/Lingli; roberto.k...@orange.com; Haiby, Ranny (Nokia - US/San Jose USA); Christopher.Donley; 'Jason Hunt'; MAZIN E GILBERT; sunqiong.bri抄送: tsc-priv...@lists.onap.org; SPATSCHECK, OLIVER \(OLIVER\); 'Yunxia Chen'主题: Re: Re: [onap-tsc-private] Lab and Intgeration China Telecom also has a lab for OPEN-O. Based on this lab, China Telecom is willing to provide a physical lab for ONAP too. Best Regards, Xiaojun  From: Lingli DengDate: 2017-05-23 09:05To: roberto.k...@orange.com; 'Haiby, Ranny \(Nokia - US/San Jose USA\)'; 'Christopher Donley \(Chris\)'; 'Jason Hunt'; ma...@research.att.comCC: tsc-private; spatsch; 'Yunxia Chen'Subject: Re: [onap-tsc-private] Lab and IntgerationChina Mobile is willing to provide a physical lab too, based on the existing OPEN-O lab and do enhancement as needed. Lingli From: onap-tsc-private-boun...@lists.onap.org [mailto:onap-tsc-private-boun...@lists.onap.org] On Behalf Of roberto.k...@orange.comSent: 2017年5月23日 8:28To: Haiby, Ranny (Nokia - US/San Jose USA) ; Christopher Donley (Chris) ; Jason Hunt ; ma...@research.att.comCc: Yunxia Chen ; tsc-priv...@lists.onap.org; spat...@research.att.comSubject: Re: [onap-tsc-private] Lab and Intgeration Orange is willing to provide a physical lab with connectivity from remote, or be part of the set up of the virtual lab. I think that what is important is to have clear specification of what is required (Open-O experience would help) asap, so that we can start to implement. This may be independent from the integration project if it allows us to be more efficient.  RK PS: actually, today we have an operation lab that is shared (from our internal research, our work with universities to our testing for deployment). So the set up would be done marginally. We need to see the tooling of course.  De : onap-tsc-private-boun...@lists.onap.org [mailto:onap-tsc-private-boun...@lists.onap.org] De la part de Haiby, Ranny (Nokia - US/San Jose USA)Envoyé : mardi 23 mai 2017 02:03À : Christopher Donley (Chris); Jason Hunt; ma...@research.att.comCc : tsc-priv...@lists.onap.org; spat...@research.att.com; Yunxia ChenObjet : Re: [onap-tsc-private] Lab and Intgeration Chris, You actually bring up an excellent point. In order to demonstrate and test real life scenarios we will need to tie in physical equipment.  However, it may not be practical to have all the necessary physical equipment in the lab. Therefore a more practical approach could be providing connectivity from the lab to physical equipment located on an operator or vendor premise. This could be done using some sort of VPN or secure tunnels over the internet. Consider the vVoLTE use case. It could be possible to test and demonstrate calls between handsets on an operator premise and ECP/IMS in the ONAP lab using tunnel connectivity (see attached diagram for a high level concept). So solving the remote equipment connectivity is a requirement for any ONAP lab, and once we address this, it does not matter anymore if the lab is physical or virtual. I am putting together a draft proposal for a virtual lab, it should be ready for discussion later this week. Regards, Ranny.  From: onap-tsc-private-boun...@lists.onap.org [mailto:onap-tsc-private-boun...@lists.onap.org] On Behalf Of Christopher Donley (Chris)Sent: Monday, May 22, 2017 2:34 PMTo: Jason Hunt ; ma...@research.att.comCc: Yunxia Chen ; tsc-priv...@lists.onap.org; spat...@research.att.comSubject: Re: [onap-tsc-private] Lab and Intgeration Bringing in Helen. In OPEN-O, we did find it valuable to have physical labs (not just virtual) to demonstrate integration with PNFs (not just VNFs).  I think we may want to consider the same approach in ONAP. That is, there’s a place for virtual labs for our CI/CD environment, but I think we want to

Re: [onap-tsc] [Onap-marketing] Reminder & updated information - ONAP Mini Summit at OPNFV 2017 - June 12 - From 9.00 am to 12. 30 pm

2017-05-26 Thread Lisa Caywood

Nermin, the day and time aren't able to be changed--these are the days when
OPNFV was able to allocate extra rooms for other events.

Your help in driving awareness of the CFP and encouraging submissions would
be great!

Thanks, Lisa

On Fri, May 26, 2017 at 12:49 PM, Nermin Mohamed 
wrote:

> All,
>
> I think it is better to have the ONAP summit last day similar w=to what we
> did in ONS and we then have Marketing, TSC and GB meetings and social
> events.
>
>
>
> Some people may be traveling on Sunday and may miss the first day of OPNFV
> summit. In order to have most people attend, we should move the event to
> Thursday.
>
>
>
> Thanks!
>
> Nermin
>
>
>
> *From:* onap-marketing-boun...@lists.onap.org [mailto:onap-marketing-
> boun...@lists.onap.org] *On Behalf Of *Balaji Ethirajulu
> *Sent:* Thursday, May 25, 2017 6:49 PM
> *To:* 'Lisa Caywood'; 'GILBERT, MAZIN E (MAZIN E)'; '
> onap-tsc@lists.onap.org'
> *Cc:* 'Lara Taback'; 'onap-market...@lists.onap.org'
> *Subject:* [Onap-marketing] Reminder & updated information - ONAP Mini
> Summit at OPNFV 2017 - June 12 - From 9.00 am to 12. 30 pm
>
>
>
> Dear ONAP team,
>
>
>
> The ONAP Mini Summit will take place on Monday, June 12th from 9.00 am to
> 12.30 pm.  The CFP will be kept open until 11.59 PST on May 31st. I
> encourage you to submit your proposals as soon as possible. We have
> provided some guidance in the web site about the areas that you can talk
> about.
>
>
>
> We are organizing a Panel at the end of the mini summit, so please do not
> submit any panel proposal.
>
> Please reach out to me if you have any questions.
>
>
>
> BR/Balaji.
>
> 408-458-0642 <(408)%20458-0642>.
>
>
>
>
>
> *From:* Balaji Ethirajulu
> *Sent:* Monday, May 22, 2017 9:13 PM
> *To:* Lisa Caywood ; GILBERT, MAZIN E (MAZIN
> E) ; onap-tsc@lists.onap.org
> *Cc:* onap-market...@lists.onap.org; Lara Taback <
> ltab...@linuxfoundation.org>
> *Subject:* ONAP Mini Summit at OPNFV 2017 - June 12 to 15
>
>
>
> Hi ONAP Team,
>
>
>
> We are organizing a ONAP Mini Summit at OPNFV 2017 in Beijing. It will be
> probably either Monday or Tuesday of that week. We will let you know the
> exact dates!
>
> We have opened a CFP and please submit your speaking proposal. It will be
> a ½ day Mini summit. We will have 30 minutes sessions. So, as you plan for
> your topic and abstract, please plan for 30 minutes presentation. It is
> also posted at the OPNFV event summit.
>
>
>
> website http://events.linuxfoundation.org/events/opnfv-summit/extend-the-
> experience/onap
>
>
>
> BR/Balaji.
>



-- 
*Lisa Caywood*
Director of Ecosystem Development | OpenDaylight Project |
lcayw...@opendaylight.org | +1 408 857 3642
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [Onap-marketing] Reminder & updated information - ONAP Mini Summit at OPNFV 2017 - June 12 - From 9.00 am to 12. 30 pm

2017-05-26 Thread Nermin Mohamed

All,
I think it is better to have the ONAP summit last day similar w=to what we did 
in ONS and we then have Marketing, TSC and GB meetings and social events.

Some people may be traveling on Sunday and may miss the first day of OPNFV 
summit. In order to have most people attend, we should move the event to 
Thursday.

Thanks!
Nermin

From: onap-marketing-boun...@lists.onap.org 
[mailto:onap-marketing-boun...@lists.onap.org] On Behalf Of Balaji Ethirajulu
Sent: Thursday, May 25, 2017 6:49 PM
To: 'Lisa Caywood'; 'GILBERT, MAZIN E (MAZIN E)'; 'onap-tsc@lists.onap.org'
Cc: 'Lara Taback'; 'onap-market...@lists.onap.org'
Subject: [Onap-marketing] Reminder & updated information - ONAP Mini Summit at 
OPNFV 2017 - June 12 - From 9.00 am to 12. 30 pm

Dear ONAP team,

The ONAP Mini Summit will take place on Monday, June 12th from 9.00 am to 12.30 
pm.  The CFP will be kept open until 11.59 PST on May 31st. I encourage you to 
submit your proposals as soon as possible. We have provided some guidance in 
the web site about the areas that you can talk about.

We are organizing a Panel at the end of the mini summit, so please do not 
submit any panel proposal.
Please reach out to me if you have any questions.

BR/Balaji.
408-458-0642.


From: Balaji Ethirajulu
Sent: Monday, May 22, 2017 9:13 PM
To: Lisa Caywood >; 
GILBERT, MAZIN E (MAZIN E) 
>; 
onap-tsc@lists.onap.org
Cc: onap-market...@lists.onap.org; Lara 
Taback >
Subject: ONAP Mini Summit at OPNFV 2017 - June 12 to 15

Hi ONAP Team,

We are organizing a ONAP Mini Summit at OPNFV 2017 in Beijing. It will be 
probably either Monday or Tuesday of that week. We will let you know the exact 
dates!
We have opened a CFP and please submit your speaking proposal. It will be a ½ 
day Mini summit. We will have 30 minutes sessions. So, as you plan for your 
topic and abstract, please plan for 30 minutes presentation. It is also posted 
at the OPNFV event summit.

website 
http://events.linuxfoundation.org/events/opnfv-summit/extend-the-experience/onap

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

Re: [onap-tsc] wiki and conference calls

2017-05-26 Thread Bob Monkman

Right…the IRC bot process we use in OPNFV likewise records all minutes using 
webchat IRC commands into a specific directory for each channel created for a 
project. When we #endmeeting, I get the links to my saved minutes files and can 
save them under the meetings directory of my project wiki page. Super easy for 
me as a non-engineer project lead. 

I recommend a similar process for ONAP.
Bob

Robert (Bob) Monkman
Networking Software Strategy & Ecosystem Programs
ARM
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490
Skype: robert.monkman

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Ed Warnicke
Sent: Friday, May 26, 2017 10:05 AM
To: Danny Lin 
Cc: SPATSCHECK, OLIVER (OLIVER) ; onap-tsc 

Subject: Re: [onap-tsc] wiki and conference calls

In many other communities, when a project get's approved it creates its own 
wiki page which has sub pages for things like its meetings, meeting minutes, 
etc.  Keeping IRC meeting minutes is a great practice, and highly recommended.  
Do do that you can create and onap-* IRC channel and open a helpdesk ticket to 
add meetbot to it.

Examples:
https://wiki.fd.io/view/VPP <- VPP project page at fd.io
https://wiki.fd.io/view/VPP/Meeting <- VPP project meeting page listing 
logistics, agenda, link to meeting minutes
https://wiki.fd.io/view/VPP/project-meeting-minutes <- VPP project meeting 
minutes
https://wiki.fd.io/view/IRC <- fd.io index of IRC channels
https://wiki.fd.io/view/Meetings <- fd.io index of public meetings

The goal is aggressive openness, not just making things publicly available, but 
easy to find.  Having a common pattern around project wiki pages etc is very 
helpful for that.

Ed

On Fri, May 26, 2017 at 8:58 AM, Danny Lin 
> wrote:
+1

In our Multi-Cloud project, we have discussed the similar issue, in a slightly 
different context. We typically record all meetings, and also have a meeting 
note. We are wondering if we should post these recording and meeting notes, and 
if so, where?

Danny

From: > 
on behalf of Ed Warnicke >
Date: Friday, May 26, 2017 at 8:35 AM
To: "SPATSCHECK, OLIVER (OLIVER)" 
>
Cc: onap-tsc >
Subject: Re: [onap-tsc] wiki and conference calls

+1k

I would strongly suggest we adopt the community norm that its totally cool for 
teams to start calls/IRC channels but they *really* need to list them in a 
central index so people can find them.  Aggressive Openness :)

Ed

On Fri, May 26, 2017 at 8:03 AM, SPATSCHECK, OLIVER (OLIVER) 
> wrote:

I noticed that a substantial number of teams are starting either ad hoc or 
weekly conference calls.  As I think it’s great that the community is forming I 
am wondering if we can start tracking those calls on the ONAP wiki page  (can 
we add a calendar or something like that?).

This would make it much easier to stay on top of attending the correct meetings 
… .

Thx

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

IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Use case subcommittee

2017-05-26 Thread GILBERT, MAZIN E (MAZIN E)

Thank you to Alla, I have now posted a framework for the use case subcommittee 
on the wiki page.
Your feedback is appreciated. I will advise the TSC next week to vote to 
formally establish this subcommittee.
We will then do self-nomination for a lead.

Mazin

https://wiki.onap.org/display/DW/Usecase+subcommittee
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] wiki and conference calls

2017-05-26 Thread Ed Warnicke

In many other communities, when a project get's approved it creates its own
wiki page which has sub pages for things like its meetings, meeting
minutes, etc.  Keeping IRC meeting minutes is a great practice, and highly
recommended.  Do do that you can create and onap-* IRC channel and open a
helpdesk ticket to add meetbot to it.

Examples:
https://wiki.fd.io/view/VPP <- VPP project page at fd.io
https://wiki.fd.io/view/VPP/Meeting <- VPP project meeting page listing
logistics, agenda, link to meeting minutes
https://wiki.fd.io/view/VPP/project-meeting-minutes <- VPP project meeting
minutes
https://wiki.fd.io/view/IRC <- fd.io index of IRC channels
https://wiki.fd.io/view/Meetings <- fd.io index of public meetings

The goal is aggressive openness, not just making things publicly available,
but easy to find.  Having a common pattern around project wiki pages etc is
very helpful for that.

Ed


On Fri, May 26, 2017 at 8:58 AM, Danny Lin  wrote:

> +1
>
>
>
> In our Multi-Cloud project, we have discussed the similar issue, in a
> slightly different context. We typically record all meetings, and also have
> a meeting note. We are wondering if we should post these recording and
> meeting notes, and if so, where?
>
>
>
> Danny
>
>
>
> *From: * on behalf of Ed Warnicke <
> hagb...@gmail.com>
> *Date: *Friday, May 26, 2017 at 8:35 AM
> *To: *"SPATSCHECK, OLIVER (OLIVER)" 
> *Cc: *onap-tsc 
> *Subject: *Re: [onap-tsc] wiki and conference calls
>
>
>
> +1k
>
>
>
> I would strongly suggest we adopt the community norm that its totally cool
> for teams to start calls/IRC channels but they *really* need to list them
> in a central index so people can find them.  Aggressive Openness :)
>
>
>
> Ed
>
>
>
> On Fri, May 26, 2017 at 8:03 AM, SPATSCHECK, OLIVER (OLIVER) <
> spat...@research.att.com> wrote:
>
>
> I noticed that a substantial number of teams are starting either ad hoc or
> weekly conference calls.  As I think it’s great that the community is
> forming I am wondering if we can start tracking those calls on the ONAP
> wiki page  (can we add a calendar or something like that?).
>
> This would make it much easier to stay on top of attending the correct
> meetings … .
>
> Thx
>
> Oliver
> ___
> ONAP-TSC mailing list
> ONAP-TSC@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-tsc
> 
>
>
>
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] wiki and conference calls

2017-05-26 Thread SPATSCHECK, OLIVER (OLIVER)

Yes and we should keep that organized. If we post them on random wiki pages 
nobody will find them… .

Seems Casey has a plan.

Casey,

do you think you can put a concrete proposal out with a process on how people 
can get there meetings/notes/recordings listed and organized?

Thx

Oliver

On May 26, 2017, at 11:58 AM, Danny Lin 
> wrote:

+1

In our Multi-Cloud project, we have discussed the similar issue, in a slightly 
different context. We typically record all meetings, and also have a meeting 
note. We are wondering if we should post these recording and meeting notes, and 
if so, where?

Danny

From: > 
on behalf of Ed Warnicke >
Date: Friday, May 26, 2017 at 8:35 AM
To: "SPATSCHECK, OLIVER (OLIVER)" 
>
Cc: onap-tsc >
Subject: Re: [onap-tsc] wiki and conference calls

+1k

I would strongly suggest we adopt the community norm that its totally cool for 
teams to start calls/IRC channels but they *really* need to list them in a 
central index so people can find them.  Aggressive Openness :)

Ed

On Fri, May 26, 2017 at 8:03 AM, SPATSCHECK, OLIVER (OLIVER) 
> wrote:

I noticed that a substantial number of teams are starting either ad hoc or 
weekly conference calls.  As I think it’s great that the community is forming I 
am wondering if we can start tracking those calls on the ONAP wiki page  (can 
we add a calendar or something like that?).

This would make it much easier to stay on top of attending the correct meetings 
… .

Thx

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

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

Re: [onap-tsc] wiki and conference calls

2017-05-26 Thread Danny Lin

+1

In our Multi-Cloud project, we have discussed the similar issue, in a slightly 
different context. We typically record all meetings, and also have a meeting 
note. We are wondering if we should post these recording and meeting notes, and 
if so, where?

Danny

From:  on behalf of Ed Warnicke 

Date: Friday, May 26, 2017 at 8:35 AM
To: "SPATSCHECK, OLIVER (OLIVER)" 
Cc: onap-tsc 
Subject: Re: [onap-tsc] wiki and conference calls

+1k

I would strongly suggest we adopt the community norm that its totally cool for 
teams to start calls/IRC channels but they *really* need to list them in a 
central index so people can find them.  Aggressive Openness :)

Ed

On Fri, May 26, 2017 at 8:03 AM, SPATSCHECK, OLIVER (OLIVER) 
> wrote:

I noticed that a substantial number of teams are starting either ad hoc or 
weekly conference calls.  As I think it’s great that the community is forming I 
am wondering if we can start tracking those calls on the ONAP wiki page  (can 
we add a calendar or something like that?).

This would make it much easier to stay on top of attending the correct meetings 
… .

Thx

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

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

Re: [onap-tsc] wiki and conference calls

2017-05-26 Thread John Zannos

Agreed.  Are we planning for the wiki to be central hub of information or 
github? 

John Zannos

> On May 26, 2017, at 8:35 AM, Ed Warnicke  wrote:
> 
> +1k
> 
> I would strongly suggest we adopt the community norm that its totally cool 
> for teams to start calls/IRC channels but they *really* need to list them in 
> a central index so people can find them.  Aggressive Openness :)
> 
> Ed
> 
>> On Fri, May 26, 2017 at 8:03 AM, SPATSCHECK, OLIVER (OLIVER) 
>>  wrote:
>> 
>> I noticed that a substantial number of teams are starting either ad hoc or 
>> weekly conference calls.  As I think it’s great that the community is 
>> forming I am wondering if we can start tracking those calls on the ONAP wiki 
>> page  (can we add a calendar or something like that?).
>> 
>> This would make it much easier to stay on top of attending the correct 
>> meetings … .
>> 
>> Thx
>> 
>> Oliver
>> ___
>> ONAP-TSC mailing list
>> ONAP-TSC@lists.onap.org
>> https://lists.onap.org/mailman/listinfo/onap-tsc
> 
> ___
> ONAP-TSC mailing list
> ONAP-TSC@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-tsc
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] wiki and conference calls

2017-05-26 Thread Ed Warnicke

+1k

I would strongly suggest we adopt the community norm that its totally cool
for teams to start calls/IRC channels but they *really* need to list them
in a central index so people can find them.  Aggressive Openness :)

Ed

On Fri, May 26, 2017 at 8:03 AM, SPATSCHECK, OLIVER (OLIVER) <
spat...@research.att.com> wrote:

>
> I noticed that a substantial number of teams are starting either ad hoc or
> weekly conference calls.  As I think it’s great that the community is
> forming I am wondering if we can start tracking those calls on the ONAP
> wiki page  (can we add a calendar or something like that?).
>
> This would make it much easier to stay on top of attending the correct
> meetings … .
>
> Thx
>
> Oliver
> ___
> ONAP-TSC mailing list
> ONAP-TSC@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-tsc
>
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] wiki and conference calls

[onap-tsc] project proposal: VNF SDK

Re: [onap-tsc] [onap-discuss] ONAP Architecture subcommittee kickoff

Re: [onap-tsc] [onap-discuss] ONAP Architecture subcommittee kickoff

Re: [onap-tsc] [onap-discuss] ONAP Architecture subcommittee kickoff

Re: [onap-tsc] [onap-tsc-private] Lab and Intgeration

Re: [onap-tsc] ONAP Architecture subcommittee kickoff

Re: [onap-tsc] [onap-tsc-private] Lab and Intgeration

[onap-tsc] Schedule for ONAP Project Proposal Initial Feedback

Re: [onap-tsc] [onap-tsc-private] Lab and Intgeration

Re: [onap-tsc] [Onap-marketing] Reminder & updated information - ONAP Mini Summit at OPNFV 2017 - June 12 - From 9.00 am to 12. 30 pm

Re: [onap-tsc] [Onap-marketing] Reminder & updated information - ONAP Mini Summit at OPNFV 2017 - June 12 - From 9.00 am to 12. 30 pm

Re: [onap-tsc] wiki and conference calls

[onap-tsc] Use case subcommittee

Re: [onap-tsc] wiki and conference calls

Re: [onap-tsc] wiki and conference calls

Re: [onap-tsc] wiki and conference calls

Re: [onap-tsc] wiki and conference calls

Re: [onap-tsc] wiki and conference calls

19 matches

Site Navigation

Mail list logo

Footer information