Re: [onap-tsc] Use case subcommittee

2017-06-06 Thread John Zannos
Alla,

Can you add me but at my email of jaazan...@gmail.com.

I have left Canonical but will stay active in ONAP.

Best
John

John Zannos
Vice President - Cloud Platform / Business Development
Canonical / Ubuntu
john.zan...@canonical.com
+1 978 375 0742
IRC: jzannos
www.ubuntu.com | www.canonical.com


On Fri, Jun 2, 2017 at 12:03 AM, Alla Goldner 
wrote:

> Hi all,
>
>
>
> Yesterday we approved creation of Use case subcommittee.
>
> I propose to have bi-weekly conference calls, starting after next week’s
> f2f meeting.
>
>
>
> I will ask Linux Foundation to send out invitation and create wiki page
> for this subcommittee.
>
>
>
> Best regards,
>
>
>
> *Alla Goldner*
>
>
>
> Open Network Division
>
> Amdocs Technology
>
>
>
>
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> you may review at https://www.amdocs.com/about/email-disclaimer
>
> ___
> ONAP-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] ONAP TSC Members - Are you Attending the China Face To Face Next Week?

2017-06-02 Thread John Zannos
Not attending in person but yes remotely.

Best
John

John Zannos
Vice President - Cloud Platform / Business Development
Canonical / Ubuntu
john.zan...@canonical.com
+1 978 375 0742
IRC: jzannos
www.ubuntu.com | www.canonical.com


On Fri, Jun 2, 2017 at 10:57 AM, Phil Robb 
wrote:

> Please +1 or -1 if you are attending or not.
>
> Please respond ASAP so that we can know who can help facilitate different
> aspects of the event.
>
> Thanks!
>
> Phil.
>
> --
> Phil Robb
> Executive Director, OpenDaylight Project
> VP Operations - Networking & Orchestration, The Linux Foundation
> (O) 970-229-5949 <(970)%20229-5949>
> (M) 970-420-4292 <(970)%20420-4292>
> Skype: Phil.Robb
>
> ___
> 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] [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-p

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] Release Naming

2017-05-19 Thread John Zannos
I think second option is best.

Best
john

John Zannos
Vice President - Cloud Platform / Business Development
Canonical / Ubuntu
john.zan...@canonical.com
+1 978 375 0742
IRC: jzannos
www.ubuntu.com | www.canonical.com


On Tue, May 16, 2017 at 1:58 PM, Alla Goldner 
wrote:

> Second option, in my view.
>
>
>
> Best regards,
>
>
>
> *Alla Goldner*
>
>
>
> Open Network Division
>
> Amdocs Technology
>
>
>
>
>
>
>
> *From:* onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-bounces@
> lists.onap.org] *On Behalf Of *GILBERT, MAZIN E (MAZIN E)
> *Sent:* Tuesday, May 16, 2017 8:23 PM
> *To:* onap-tsc 
> *Subject:* [onap-tsc] Release Naming
>
>
>
> Team,
>
>
>
> I have two  proposals for release naming. One from Rueben Klein and the
> other
>
> from Gildas Lanilis.
>
>
>
> The first is famous cities belonging to platinum members, and the other is
> famous conductors in
>
> the domain of orchestrating:-) Both follow the alphabet style.
>
> Please review and share comments before our TSC meeting on Thursday.
>
>
>
> Thanks
>
> Mazin
>
>
>
>
>
> Option 1
>
> *Platinum Member*
>
> *Country
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_Country&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=SzgbQMfNr3fZoBR_SjXxblyJEpSPOTDUI8MQquOqyzI&s=NSkr48qokE_fsPEScprurl5LH2_NnfUfZmYR9mXODiU&e=>*
>
> *Major Locations*
>
> IBM
>
> US
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_Peru&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=SzgbQMfNr3fZoBR_SjXxblyJEpSPOTDUI8MQquOqyzI&s=tQRfIQXJOYqhuK_mwy_BfjadPPlBsfUlcz_TOW5jKFo&e=>
>
> Armonk
>
> China Mobile/Telecom
>
> China
>
> Beijing
>
> Amdocs
>
> US
>
> Chesterfield
>
> AT&T
>
> US
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_Egypt&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=SzgbQMfNr3fZoBR_SjXxblyJEpSPOTDUI8MQquOqyzI&s=kk5F5x3gUBkCCjG9y8SIy8CHLwUaoT14XoylofBH7-4&e=>
>
> Dallas
>
> Nokia
>
> Finland
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_Vietnam&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=SzgbQMfNr3fZoBR_SjXxblyJEpSPOTDUI8MQquOqyzI&s=rk5QoP5ur9Gz8JIwa1htetsl01vE4BAxoR-MsGDsmuw&e=>
>
> Espoo
>
> VMWare
>
> US (IL)
>
> Herzliya
>
> Intel
>
> US
>
> Irvine
>
> Ericsson
>
> Sweden
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_Pakistan&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=SzgbQMfNr3fZoBR_SjXxblyJEpSPOTDUI8MQquOqyzI&s=wZV79oAeqlvTzwKrdfMzRBOkqOBImNA9IPK0xny3bT8&e=>
>
> Kista
>
> Tech Mahindra
>
> India
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_Canada&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=SzgbQMfNr3fZoBR_SjXxblyJEpSPOTDUI8MQquOqyzI&s=5m-snnD_j5tbPtS0MzIcGbAPrSurGg-G2kcPRYWsU_I&e=>
>
> Mumbai
>
> Gigaspaces
>
> US
>
> New York
>
> Bell Canada
>
> Canada
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_Republic-5Fof-5FIreland&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=SzgbQMfNr3fZoBR_SjXxblyJEpSPOTDUI8MQquOqyzI&s=vTwVDfqRKekRqOgMvIDOcRKWVJ3NUJgEVnL92x4MeHU&e=>
>
> Ottawa
>
> Orange
>
> France
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_France&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=SzgbQMfNr3fZoBR_SjXxblyJEpSPOTDUI8MQquOqyzI&s=1ZKIZT1nhfSal9pxJqMrR_Gy8JsJ9gc0q43FCPwNauM&e=>
>
> Paris
>
> Cisco
>
> US
>
> San Jose
>
> Huawei
>
> China
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_Ukraine&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=SzgbQMfNr3fZoBR_SjXxblyJEpSPOTDUI8MQquOqyzI&s=0pSzLF1o46ZRle-UmWsashceiPTEt8NC1HQzmtPq1AA&e=>
>
> Shenzhen
>
> ZTE
>
> China
>
> Tianjin
>
>
>
>
>
> Option 2
>
>
>
> *Famous Conductors:*
>
> As ONAP plays in the domain of orchestrating, we could use the name of
> famous conductors.
>
> *Continuous Naming*: Amadeus, Beethoven, Chopin, Debussy, Enescu, Foote,
> Gershwin, Handel, Ilyich, Johannes
>
> *Non-Continuous naming*: Amadeus, Beethoven, Chopin, Debussy, Gershwin,
> Liszt, Puccini, Ravel, Schubert, Tchaikovsky, Vivaldi, Wagner
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> you may review at https://www.amdocs.com/about/email-disclaimer
>
> ___
> ONAP-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] Congratulations to Lingli Deng - ONAP Vice Chair

2017-05-07 Thread John Zannos
Congratulations on the TSC vice chair. I look forward to working with you
on ONAP.

Best
John

John Zannos
Vice President - Cloud Platform / Business Development
Canonical / Ubuntu
john.zan...@canonical.com
+1 978 375 0742
IRC: jzannos
www.ubuntu.com | www.canonical.com


On Sat, May 6, 2017 at 8:02 AM, Gadiyar, Rajesh 
wrote:

> Dear friends,
>
>
>
> Please join me in Congratulating my dear friend Lingli, a deserved winner
> for the ONAP Vice Chair. Her thorough, detail oriented approach will be a
> great asset for us in ONAP. Congratulations Lingli and I look forward to
> working closely with you.
>
> --
>
> Regards,
>
> Rajesh
>
>
>
>
>
> *From: * on behalf of Phil Robb <
> pr...@linuxfoundation.org>
> *Date: *Saturday, May 6, 2017 at 4:32 AM
> *To: *"onap-tsc@lists.onap.org" 
> *Subject: *[onap-tsc] The TSC Vice Chairperson Election Has Concluded
>
>
>
> Hello ONAP TSC Members:
>
>
>
> The TSC Vice Chairperson Election has concluded.  For the TSC members,
> there is a link on the email that was your original invitation to vote that
> has the results.  A copy of that information is also provided below for the
> rest of the community.
>
>
>
> Congratulations Lingli, and thanks to all of the excellent candidates in
> this election.
>
>
> Result
>
> 1. *Lingli Deng*  (Condorcet winner: wins contests with all other choices)
>
> 2. Chris Donley  loses to Lingli Deng by 9–5
>
> 3. Rajesh Gadiyar  loses to Lingli Deng by 10–5, loses to Chris Donley by
> 8–7
>
> 4. Alla Goldner  loses to Lingli Deng by 11–4, loses to Rajesh Gadiyar by
> 9–5
> Result details Hide details
>
>
>
>
>
> *1*
>
> *2*
>
> *3*
>
> *4*
>
> *1. Lingli Deng*
>
>
>
> -
>
> *9*
>
> *10*
>
> *11*
>
> *2. Chris Donley*
>
>
>
> *5*
>
> -
>
> *8*
>
> *9*
>
> *3. Rajesh Gadiyar*
>
>
>
> *5*
>
> *7*
>
> -
>
> *9*
>
> *4. Alla Goldner*
>
>
>
> *4*
>
> *6*
>
> *5*
>
> -
> Ballot report
>
>
>
> *Alla Goldner*
>
> *Chris Donley*
>
> *Lingli Deng*
>
> *Rajesh Gadiyar*
>
> 1.
>
> 1
>
> 3
>
> 4
>
> 2
>
> 2.
>
> 3
>
> 2
>
> 1
>
> 4
>
> 3.
>
> 3
>
> 4
>
> 1
>
> 2
>
> 4.
>
> 3
>
> 4
>
> 1
>
> 2
>
> 5.
>
> 4
>
> 3
>
> 2
>
> 1
>
> 6.
>
> 4
>
> 3
>
> 2
>
> 1
>
> 7.
>
> 1
>
> 4
>
> 2
>
> 3
>
> 8.
>
> 4
>
> 2
>
> 1
>
> 3
>
> 9.
>
> 3
>
> 1
>
> 4
>
> 2
>
> 10.
>
> 2
>
> 3
>
> 1
>
> 4
>
> 11.
>
> 4
>
> 1
>
> 2
>
> 3
>
> 12.
>
> 2
>
> 3
>
> 4
>
> 1
>
> 13.
>
> 3
>
> 2
>
> 1
>
> 4
>
> 14.
>
> 4
>
> 1
>
> 2
>
> 3
>
> 15.
>
> 4
>
> 1
>
> 1
>
> 4
>
> Ballots are shown in a randomly generated order.
>
> [*Download ballots in CSV format*
> <http://civs.cs.cornell.edu/cgi-bin/download_ballots.pl?id=E_d3396c661f75e3c2>
> ]
>
> The following matrix shows the strength of the strongest beatpath
> connecting each pair of choices. Choice 1 is ranked above choice 2 if there
> is a stronger beatpath leading from 1 to 2 than any leading from 2 to 1.
>
>
>
>
>
> *1.*
>
> *2.*
>
> *3.*
>
> *4.*
>
> *1. Lingli Deng*
>
>
>
> -
>
> *9**–5*
>
> *10**–5*
>
> *11**–4*
>
> *2. Chris Donley*
>
>
>
> *.*
>
> -
>
> *8**–7*
>
> *9**–6*
>
> *3. Rajesh Gadiyar*
>
>
>
> *.*
>
> *.*
>
> -
>
> *9**–5*
>
> *4. Alla Goldner*
>
>
>
> *.*
>
> *.*
>
> *.*
>
> -
>
> Best,
>
>
>
> Phil.
>
> --
>
> Phil Robb
>
> Executive Director, OpenDaylight Project
>
> VP Operations - Networking & Orchestration, The Linux Foundation
>
> (O) 970-229-5949 <(970)%20229-5949>
>
> (M) 970-420-4292 <(970)%20420-4292>
>
> Skype: Phil.Robb
>
> ___
> 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