Re: [onap-discuss] [onap-tsc] Action Plan towards Casablanca

[Sauvageau, David]

Bell would like to contribute to the end user committee

Envoyé de mon iPhone

Le 31 mars 2018 à 07:08, Alla Goldner 
> a écrit :

Thanks, Mazin,

We will definitely not slow down as time issue is becoming critical and try to 
come up with our proposal of realistic scope per defined prioritized areas.

We also need to define what percentage of work in Casablanca would be dedicated 
by the projects to leftovers from Beijing and to extension of S3P work.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology




From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Saturday, March 31, 2018 3:56 AM
To: Alla Goldner >
Cc: onap-usecase...@lists.onap.org; 
onap-discuss@lists.onap.org; 
onap-...@lists.onap.org P 
>
Subject: Re: [onap-discuss] Action Plan towards Casablanca
Importance: High

Thanks Alla for the summary.

Here is what we agreed to at the TSC meeting.
There are three work plans for Casablanca. The theme is increase deployability 
of ONAP.

1. Functional requirements and use cases. We agreed to establish an end-user 
advisory committee that will be driven by the equivalent of product managers 
across operators who will help to set priorties that can accelerate 
deployability of ONAP. The work of your committee on use cases and 5G 
solutioning will help to provide options for the end-user advisory committee.

2. Platform Evolution. This includes some of your list items
a. S3P new target (including code coverage)
b. Backward compatibility
c. Improve modularity and simplicity of using ONAP.

3. Broader learning and education of ONAP.
The Education committee will develop a proposal for weekly Webinars.

I am working to assemble 1. My hope is to have 3-4 operators signed up next 
week so they can meet with your team and get the work started.
Phil will make that committee official as a subgroup under LFN end-user 
advisory committee. Until then, let’s not slow down.

We also discussed what we want to accomplish prior to the Beijing meeting in 
June. We will discuss that further at the TSC meeting this week,
and also vote on the release planning for Casablanca.

Great progress by the team on Beijing. Most projects hit M4 already. Momentum 
is amazing.

Mazin


On Mar 30, 2018, at 5:03 AM, Alla Goldner 
> wrote:

Hi all,

I re-attach the picture which describes high level priorities as discussed 
during the meeting called by me on Wednesday evening. I understand this was 
discussed in details also during the TSC meeting.

What we had on the table was:

1.   Leftovers from Beijing remained from :
a.   Functional requirements (PNF, Scaling, Change Management, HPA)
b.  Leftovers from S3P support
2.   New S3P requirements
3.   All new use cases and requirements coming to Casablanca (you could see 
the variety during our meeting on Monday)
4.   A different projects proposed extensions
5.   Possibly, new projects potentially proposed for Casablanca
6.   Architecture evolution related modifications

Clearly, this whole scope will not be accomplished in a single Release, this is 
why we needed to see what would be areas of priorities.
Clearly, we may get additional input from the Service Providers, as discussed, 
but in the mean time, in order to make progress, let’s assume these are the 
priorities.

Now, in order to do constructive work and move forward towards Casablanca 
Release, specifically for Usecase subcommittee, we need to see what ongoing 
work matches the Deployability goal as defined and, additionally, extract 
generic functional requirements from the use cases brought to the table/see if 
some requirements brought to the table can be generalized.

I identify the following areas for our activities out of proposed prioritized 
areas:

1.   Leftovers of functional requirements from Beijing – as scope is pretty 
clear, I would say that at this point the required actions are:
a.   Have a detailed list of functionality proposed to move to Casablanca
b.  Negotiate with involved projects on this functionality and resources 
assigned to these activities

2.   All 5G related requirements:
a.   A realistic plan of what can be implemented in Casablanca (a subset of 
functionality discussed so far), based on available/emulated VNFs/PNFs, 3GPP 
standards’ availability etc. with flows, needed resources, affected modules

3.   All external controllers related activities – this work should be 
generalized and common principle should be developed on what we bring to 
Casablanca in such a way that it can be utilized by several use cases. Some 
initial work on this was also done in Beijing.
a.   A concrete 

Re: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB resource needs

[Sauvageau, David]

Thanks Roger. Gildas, do you need anything else for OOM?

From: 
>
 on behalf of Roger Maitland 
>
Date: Friday, December 1, 2017 at 2:02 PM
To: "PLATANIA, MARCO (MARCO)" 
>, "FREEMAN, BRIAN 
D" >, Gildas Lanilis 
>, "TIMONEY, DAN" 
>, onap-release 
>
Cc: onap-discuss 
>
Subject: Re: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB 
resource needs

I’ve gathered some data from Michael’s CD system to determine the size of the 
deployment – see the attached excel spreadsheet.  This data is from December 
1st, just before noon EST.  Here is a graph that summarizes the memory 
requirements:
[cid:image001.png@01D36AAD.03CE1400]
There are only 7 containers with memory usage over 1.5 GB.

The total memory usage peaks at just over 50 GB (my analysis was done just 
after the peak so the numbers are a little lower):
[cid:image005.png@01D36AAD.03CE1400]

Please keep in mind that there is no traffic on this CD systems so actually 
usage in a real-world deployment will be higher.

Cheers,
Roger
From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO 
(MARCO)
Sent: Thursday, November 30, 2017 9:57 AM
To: FREEMAN, BRIAN D >; Gildas Lanilis 
>; TIMONEY, DAN 
>; onap-release 
>
Cc: onap-discuss 
>
Subject: Re: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB 
resource needs

I don’t think there is a real relationship between number of containers and 
resource needed, it mainly depends on what kind of computation you are doing. I 
leave the answer to the experts (OOM team) but a while ago I was told that on 
average you roughly need 2 GB per container, but I don’t know how accurate this 
is.

Today’s OOM cluster is 64 GB (without DCAE). That seems OK for non-replicated 
ONAP.

Marco

From: "FREEMAN, BRIAN D" >
Date: Thursday, November 30, 2017 at 9:46 AM
To: "PLATANIA, MARCO (MARCO)" 
>, Gildas Lanilis 
>, "TIMONEY, DAN" 
>, onap-release 
>
Cc: onap-discuss 
>
Subject: RE: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB 
resource needs

That does make sense – perhaps another set of columns or separate table for 
container data.

How do you measure/estimate the memory needed for a container ?

Brian



From: PLATANIA, MARCO
Sent: Thursday, November 30, 2017 9:41 AM
To: FREEMAN, BRIAN D >; Gildas Lanilis 
>; TIMONEY, DAN 
>; onap-release 
>
Cc: onap-discuss 
>
Subject: Re: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB 
resource needs

Brian,

Thanks for the clarification, I was also confused. Resource assessment is 
important for HEAT, which needs to know #CPUs, memory, etc. of each specific VM.

If we use OOM for Beijing (as I understand), in my opinion the right way to 
think about it is container-level, rather than VM-level. This means that PTLs 
should tell how many instances of their component they need (or, put in another 
way, how many replicas of their containers they need). Resource sizing is then 
made at cluster level. Depending on how many containers we’ll need to support, 
the OOM cluster size will be adjusted.

Does it make sense?

Marco

From: 
>
 on behalf of "FREEMAN, BRIAN D" >
Date: Thursday, November 30, 2017 at 9:07 AM
To: Gildas Lanilis 
>, "TIMONEY, DAN" 
>, onap-release 
>
Cc: onap-discuss 
>
Subject: Re: 

[onap-discuss] [OOM] Request for new committer on OOM - Borislav Glozman

[Sauvageau, David]

Dear OOM committers,

This is a request to promote Borislav as a committer on the OOM project. I 
would need all OOM committers to vote on Borislav’s promotion by replying +1, 0 
or –1 on this email. If we get a majority of +1, I will then bring the request 
to the TSC.

Thanks!

From: Borislav Glozman 
>
Date: Sunday, November 5, 2017 at 2:48 AM
To: David Sauvageau >
Cc: Alla Goldner >
Subject: ONAP OOM committer for Borislav Glozman

Hi David,

I would like to officially become OOM committer.
I fix defects, commit code, participate in meetings, participate in design of 
features, participated in Paris ONAP event and presented there.
I also lead a team of developers who work on OOM.

Could you please assist me in becoming a committer in OOM project so that I 
could actively participate in Beijing release in OOM?
Please let me know what is the process.

Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726

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

[onap-discuss] [OOM] urgent: can't open zoom meeting

[Sauvageau, David]

Hi Kenny,

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

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

Re: [onap-discuss] Versioning for Amsterdam

[Sauvageau, David]

Hi Gildas,

What process to you recommend so that we can settle on this? Do we need to go 
through TSC?

On Jul 21, 2017, at 6:22 PM, Gildas Lanilis 
> wrote:

I see Olivier is leading a session on versioning, excellent I will attend. I 
won't have time to cover this during Release Planning.

Looks like there is a trend toward option 2 (multiple version of jars files 
embedded within 1 docker image) with some good reasons. Thinking loud, as all 
projects will be a Docker image, when we will release these Docker images in 
November, I will be incline to mark these Docker images as version 1.0.0. for 
Amsterdam and later 2.0.0 for Beijing (and of course with semantic versioning 
if we need in the middle to deliver patches).

So we will end up with Something like:

Amsterdam Release:1.0.0

AAI Docker Image: 1.0.0
 AAI cpt 1: 2.0.3
 AAI cpt2: 1.4.2
 AAI cpt3: 0.0.9
 Other stuff: 1.2.6

AAFDocker Image: 1.0.0
 AAI cpt 1: 2.0.3
 AAI cpt2: 2.4.2
 AAI cpt3: 1.0.9
Other stuff: 1.2.7

Beijing: 2.0.0

AAI Docker Image: 2.0.0
 AAI cpt1: 2.5.3
 AAI cpt2: 2.4.2
 AAI cpt3: 1.0.9
 Other stuff: 1.2.8

AAF Docker Image: 2.0.0
 AAF cpt1: 2.9.3
 AAF cpt2: 3.5.2
 AAF cpt3: 1.0.9
Other stuff: 2.2.6


Let me know if that resonate to you or if I should stop and go in weekend ☺

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287


-Original Message-
From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Andrew Grimberg
Sent: Thursday, July 20, 2017 11:00 AM
To: Gary Wu >
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Versioning for Amsterdam

It's the same process we would follow for a single simultaneous release.
The difference is that each component would be (and presently ONAP does
this) producing their own staging repository.

So, the release is then a matter of identifying which repositories are part of 
the release and doing the artifact signing on those and releases in nexus to 
the release repository.

The Simultaneous Release would be more of an identifying what components are 
actually part of the tested SR and potentially some final single produced 
downloadable object that doesn't do the build, but just incorporates the 
individually released components.

LF Release Engineering (RelEng) has been fixing up our release scripts dealing 
with this sort of thing. They are now part of the lftools python project [0] 
[1] (installable via PyPi). ODL itself has started down the road of individual 
components being able to release off sync from each other with the current 
Nitrogen release cycle. The odlparent project has already had at least 3 
different releases in the middle of the cycle! We expect that the next project 
up the stack (yangtools) will do that with the Oxygen release as they 
transition to SemVer which really is a requirement for this to work correctly.

We have additional work coming that will allow us to automate the artifact 
signing and will therefore allow us to move more of the release processes into 
the hands of the community itself instead of relying on RelEng for so much of 
it.

-Andy-

[0] https://gerrit.linuxfoundation.org/infra/#/admin/projects/releng/lftools
[1] https://github.com/lfit/releng-lftools

On 07/20/2017 10:41 AM, Gary Wu wrote:
> Hi Andy,
>
> Can you chime in on how the release process would work (vis-à-vis use of 
> staging repos, artifact signings, etc.) if ONAP decides to have independent 
> version numbers and possibly independent release cycles for each module?
>
> Thanks,
> Gary
>
>
> -Original Message-
> From: 
> onap-discuss-boun...@lists.onap.org
> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gino Fraboni
> Sent: Thursday, July 20, 2017 7:04 AM
> To: SPATSCHECK, OLIVER (OLIVER) 
> >; Yunxia
> Chen >
> Cc: onap-discuss@lists.onap.org
> Subject: Re: [onap-discuss] Versioning for Amsterdam
>
>
> I'll throw in my +1 for version 2 as well.
> And semantic versioning makes complete sense to me.
>
>
> Gino Fraboni
> Senior Software Developer
> Amdocs Data Experience
>
>
>
> A Platinum member of ONAP
> Read the latest on Amdocs.com and the Amdocs blog network 
> – and follow us on Facebook, Twitter, LinkedIn and YouTube.
>
>
>
> -Original Message-
> From: 
> onap-discuss-boun...@lists.onap.org
> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of SPATSCHECK,
> OLIVER (OLIVER)
> Sent: Thursday, July 20, 2017 9:54 AM
> To: Yunxia Chen 

Re: [onap-discuss] [MSB][OOM]The July Virtual Developers Event Topic : OOM & MSB Interaction

[Sauvageau, David]

Thanks John
And generally speaking let's make sure cloudify remains an option for the 
operators, and not a mandatory component as I believe most operators won't need 
that scale

Envoyé de mon iPhone

Le 26 juil. 2017 à 18:06, NG, JOHN <jn1...@att.com<mailto:jn1...@att.com>> a 
écrit :

Hi David,
We added a list of user stories to the OOM JIRA.  Not all the user stories will 
make the Amsterdam release by the Functionality Freeze date.  But some will 
make it – especially Consul, component/service registration, state monitoring, 
and TOSCA/Cloudify creating the rest of the OOM modules.  I will update you on 
the demo and seed code.

John

---
John Ng
AT Labs – D2 Architecture
200 Laurel Ave, D5-3D16
Middletown, NJ 07748
+1 732 420 3742
+1 732 310 3253 (mobile)
joh...@att.com<mailto:joh...@att.com>
---

From: Sauvageau, David [mailto:david.sauvag...@bell.ca]
Sent: Wednesday, July 26, 2017 7:39 AM
To: NG, JOHN <jn1...@att.com<mailto:jn1...@att.com>>
Cc: zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>; LUCAS, JACK 
<jflu...@research.att.com<mailto:jflu...@research.att.com>>; HU, JUN NICOLAS 
<jh2...@att.com<mailto:jh2...@att.com>>; BENNETT, RICH 
<rb2...@att.com<mailto:rb2...@att.com>>; TORAB, HABIB M 
<ht1...@att.com<mailto:ht1...@att.com>>; 
roger.maitl...@amdocs.com<mailto:roger.maitl...@amdocs.com>; MURRAY, JOHN 
<j...@research.att.com<mailto:j...@research.att.com>>; 
meng.zhaoxi...@zte.com.cn<mailto:meng.zhaoxi...@zte.com.cn>; RATH, CHRISTOPHER 
A <c...@research.att.com<mailto:c...@research.att.com>>; GAULD, ANDREW G 
<ag1...@att.com<mailto:ag1...@att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [MSB][OOM]The July Virtual Developers Event Topic :  OOM & MSB 
Interaction

Hi John

Let’s recap what was discussed and agreed as a team:
* For Amsterdam release, Kubernetes is the first OOM technical implementation 
to be created. This is the seed code available and what the team agreed to work 
on
* The cloudily implementation has not been demoed yet and no seed code 
available. It was agreed by the team that cloudily would be a stretch target.

I want to make sure we align to what the OOM team has agreed to deliver.

Comments?


On Jul 25, 2017, at 6:39 PM, NG, JOHN <jn1...@att.com<mailto:jn1...@att.com>> 
wrote:

Huabing,
Ok, let’s focus on Consul integration for the Amsterdam release …

-  In Day 0 OOM instantiation, Cloudify is the first OOM module to be 
created.

-  Cloudify creates Consul as the next OOM module.   Cloudify registers 
itself in Consul.

-  Cloudify then creates the rest of the OOM modules (Postgres, API 
Handler, Dashboard), and registers each module in Consul.  And Consul starts 
performing health checks against them.

-  OOM instantiation is now complete.

-  OOM deploys MSB as one of the first ONAP components.  OOM 
provides/configures MSB with the location of the Consul API for access and 
discovery.

-  OOM then continues to deploy the rest of the ONAP components and 
modules, and registers them with Consul.
Comments?

John

---
John Ng
AT Labs – D2 Architecture
200 Laurel Ave, D5-3D16
Middletown, NJ 07748
+1 732 420 3742
+1 732 310 3253 (mobile)
joh...@att.com<mailto:joh...@att.com>
---

From: zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn> 
[mailto:zhao.huab...@zte.com.cn]
Sent: Monday, July 24, 2017 9:48 PM
To: NG, JOHN <jn1...@att.com<mailto:jn1...@att.com>>
Cc: LUCAS, JACK <jflu...@research.att.com<mailto:jflu...@research.att.com>>; 
HU, JUN NICOLAS <jh2...@att.com<mailto:jh2...@att.com>>; BENNETT, RICH 
<rb2...@att.com<mailto:rb2...@att.com>>; 
david.sauvag...@bell.ca<mailto:david.sauvag...@bell.ca>; TORAB, HABIB M 
<ht1...@att.com<mailto:ht1...@att.com>>; 
roger.maitl...@amdocs.com<mailto:roger.maitl...@amdocs.com>; MURRAY, JOHN 
<j...@research.att.com<mailto:j...@research.att.com>>; 
meng.zhaoxi...@zte.com.cn<mailto:meng.zhaoxi...@zte.com.cn>; RATH, CHRISTOPHER 
A <c...@research.att.com<mailto:c...@research.att.com>>; GAULD, ANDREW G 
<ag1...@att.com<mailto:ag1...@att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re:RE: [MSB][OOM]The July Virtual Developers Event Topic :  OOM & MSB 
Interaction

Hi John,

I'm afraid that I can't agree that.

There is a clear boundary between OOM and MSB and their project scopes are 
totally different. I think these have already been fully discussed in the 
community in the last few months and approved by TSC at 

Re: [onap-discuss] Invitation: [oom] Weekly Meeing @ Weekly from 7am to 8am on Wednesday (PDT) (david.sauvag...@bell.ca)

[Sauvageau, David]

Agenda for tomorrow:

· Status update

oCloudify for OOM: set timing for demo and seed code review

oOOM - MSB Integration: followup from the email from Huabing

oPlatform configuration management: A proposed approach by AMDOCS

· Getting momentum: Next steps for kicking-off implementation
Thanks,

From: linuxfoundation.org_1rmtb5tpr3uc8f76fmflplo...@group.calendar.google.com
When: 10:00 AM - 11:00 AM July 19, 2017
Subject: Invitation: [oom] Weekly Meeing @ Weekly from 7am to 8am on Wednesday 
(PDT) (david.sauvag...@bell.ca)
Location: https://zoom.us/j/118908904


more details 
»
[oom] Weekly Meeing

Hi there,

ONAP Meeting 5 is inviting you to a scheduled Zoom meeting.


Join from PC, Mac, Linux, iOS or Android: 


https://zoom.us/j/118908904


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


Or Telephone:


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


+1 855 880 1246 (US Toll Free)


+1 877 369 0926 (US Toll Free)


Meeting ID: 118 908 904


International numbers available: 


https://zoom.us/zoomconference?m=RjcDSzvXlwMWG5gaHA7q936bD1fmNWjr












When

Weekly from 7am to 8am on Wednesday Pacific Time

Where

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

Calendar

david.sauvag...@bell.ca

Who

•

kp...@linuxfoundation.org - creator

•

david.sauvag...@bell.ca

•

onap-discuss@lists.onap.org



Going? All events in this series: 
Yes
 - 
Maybe
 - 
No
 more options 
»


Invitation from Google Calendar

You are receiving this courtesy email at the account david.sauvag...@bell.ca 
because you are an attendee of this event.

To stop receiving future updates for this event, decline this event. 
Alternatively you can sign up for a Google account at 
https://www.google.com/calendar/ and control your notification settings for 
your entire calendar.

Forwarding this invitation could allow any recipient to modify your RSVP 
response. Learn 
More.


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

Re: [onap-discuss] [oom] TOSCA Model Driven Orchestration across Containers and Non-Container Deployment Options

[Sauvageau, David]

Hi John,

I believe one of the action item from the last meeting was to schedule a 
followup demo of the cloudify implementation. When is the earliest this demo 
can happen? Would you suggest we do the demo at our weekly meeting?

If we want to include such an implementation for the Amsterdam release, we need 
to have the seed code available as soon as possible.

Thanks!

From:  on behalf of "NG, JOHN" 

Date: Tuesday, July 11, 2017 at 10:40 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] [oom] TOSCA Model Driven Orchestration across 
Containers and Non-Container Deployment Options

OOM Contributors and Committers,
I have uploaded the deck that was shared at our meeting today.  I also inserted 
a link in the OOM M1 Release Planning wiki page.

https://wiki.onap.org/download/attachments/8229362/OOM_R1_ProposedScope_att.pdf?version=1=1499783392000=v2

thanks,
John
---
John Ng
AT Labs – D2 Architecture
200 Laurel Ave, D5-3D16
Middletown, NJ 07748
+1 732 420 3742
+1 732 310 3253 (mobile)
joh...@att.com
---

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

[onap-discuss] Invitation: [oom] Weekly Meeting followup

[Sauvageau, David]

Hi oom committers

Please use the following webex instead of  the zoom meeting from the invite. 
There is an issue with zoom

https://bchmtw.webex.com/join/david.sauvageaubell.ca



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

[onap-discuss] Invitation: [oom] Weekly Meeting followup

[Sauvageau, David]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:US Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Sauvageau, David":MAILTO:david.sauvag...@bell.ca
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:\n\nmore details »<https://www.google.com/calen
 dar/event?action=VIEW=ZnFocjBscjVhcDRtNzljZHR2aGs1ZmY2aGMgZGF2aWQuc2F1
 dmFnZWF1QGJlbGwuY2E=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zj
 c2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tMzg4YTBkNDZhMDQyOWI4ZGE0
 NTcxNTZhNDU2NThhMTdlMDBkZDE3NQ=America/Los_Angeles=en>\n\n[oom] Wee
 kly Meeing\n\n\n\nHi there\,\n\nONAP Meeting 5 is inviting you to a schedu
 led Zoom meeting.\n\n\n\nJoin from PC\, Mac\, Linux\, iOS or Android:\n\n\nhttps://zoom.us/j/118908904\n\n\n\nOr iPhone one-tap (US To
 ll): +14086380968\,\,118908904# or +16465588656\,\,118908904#\n\n\n\nOr Te
 lephone:\n\n\n\n\nDial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US T
 oll)\n\n\n\n\n+1 855 880 1246 (US Toll Free)\n\n\n\n\n+1 877 369 0926 (US 
 Toll Free)\n\n\n\n\nMeeting ID: 118 908 904\n\n\n\n\nInternational numbers
  available:\n<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fzoomcon
 ference%3Fm%3DRjcDSzvXlwMWG5gaHA7q936bD1fmNWjr=D=2=AFQjCNG7DcTq
 8EK0xbSNTfUkrgZFVafwOg>\n\nhttps://zoom.us/zoomconference?m=RjcDSzvXlwMWG5
 gaHA7q936bD1fmNWjr<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fzo
 omconference%3Fm%3DRjcDSzvXlwMWG5gaHA7q936bD1fmNWjr=D=2=AFQjCNG
 7DcTq8EK0xbSNTfUkrgZFVafwOg>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
 \n\n\nWhen\nWeekly from 7am to 8am on Wednesday Pacific Time\n\nWh
 ere\nhttps://zoom.us/j/118908904 (map<https://www.google.com/url?q
 =https%3A%2F%2Fzoom.us%2Fj%2F118908904=D=2=AFQjCNHVxs43K273zX8z
 rH6oVdZ_sDJiKQ>)\n\nCalendar\ndavid.sauvag...@bell.ca\n\nWho\n
 •\nkp...@linuxfoundation.org - creator\n\n•\ndavid
 .sauvag...@bell.ca\n\n•\nonap-discuss@lists.onap.org\n\n\nGoing?
  All events in this series: Yes<https://www.google.com/calendar/event?acti
 on=RESPOND=ZnFocjBscjVhcDRtNzljZHR2aGs1ZmY2aGMgZGF2aWQuc2F1dmFnZWF1QGJ
 lbGwuY2E=1=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1
 mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tMzg4YTBkNDZhMDQyOWI4ZGE0NTcxN
 TZhNDU2NThhMTdlMDBkZDE3NQ=America/Los_Angeles=en> - Maybe - No<https://www.google.com/calendar/event?action=RESPOND;
 eid=ZnFocjBscjVhcDRtNzljZHR2aGs1ZmY2aGMgZGF2aWQuc2F1dmFnZWF1QGJlbGwuY2E
 t=2=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OE
 Bncm91cC5jYWxlbmRhci5nb29nbGUuY29tMzg4YTBkNDZhMDQyOWI4ZGE0NTcxNTZhNDU2NThh
 MTdlMDBkZDE3NQ=America/Los_Angeles=en> more options »<https://www.
 google.com/calendar/event?action=VIEW=ZnFocjBscjVhcDRtNzljZHR2aGs1ZmY2
 aGMgZGF2aWQuc2F1dmFnZWF1QGJlbGwuY2E=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm
 10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tMzg4YTBk
 NDZhMDQyOWI4ZGE0NTcxNTZhNDU2NThhMTdlMDBkZDE3NQ=America/Los_Angeles=
 en>\n\nInvitation from Google Calendar<https://www.google.com/calendar/>\n
 \nYou are receiving this courtesy email at the account david.sauvageau@bel
 l.ca because you are an attendee of this event.\n\nTo stop receiving futur
 e updates for this event\, decline this event. Alternatively you can sign 
 up for a Google account at https://www.google.com/calendar/ and control yo
 ur notification settings for your entire calendar.\n\nForwarding this invi
 tation could allow any recipient to modify your RSVP response. Learn More<
 https://support.google.com/calendar/answer/37135#forwarding>.\n\n\n\n\n
SUMMARY;LANGUAGE=en-US:Invitation: [oom] Weekly Meeting followup
DTSTART;TZID=US Eastern Standard Time:20170706T09
DTEND;TZID=US Eastern Standard Time:20170706T093000
UID:132CB7B95EF340828C8DF76E925F6F970
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170706T124155Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:1
LOCATION;LANGUAGE=en-US:https://zoom.us/j/118908904
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:2115449333
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Invitation: [oom] Weekly Meeting followup

[Sauvageau, David]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:US Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Sauvageau, David":MAILTO:david.sauvag...@bell.ca
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:\n\nmore details »<https://www.google.com/calen
 dar/event?action=VIEW=ZnFocjBscjVhcDRtNzljZHR2aGs1ZmY2aGMgZGF2aWQuc2F1
 dmFnZWF1QGJlbGwuY2E=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zj
 c2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tMzg4YTBkNDZhMDQyOWI4ZGE0
 NTcxNTZhNDU2NThhMTdlMDBkZDE3NQ=America/Los_Angeles=en>\n\n[oom] Wee
 kly Meeing\n\n\n\nHi there\,\n\nONAP Meeting 5 is inviting you to a schedu
 led Zoom meeting.\n\n\n\nJoin from PC\, Mac\, Linux\, iOS or Android:\n\nhttps://zoom.us/j/118908904\n\n\n\nOr iPhone one-tap (US Toll
 ): +14086380968\,\,118908904# or +16465588656\,\,118908904#\n\n\n\nOr Tele
 phone:\n\n\n\nDial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
 \n\n\n\n+1 855 880 1246 (US Toll Free)\n\n\n\n+1 877 369 0926 (US Toll Fre
 e)\n\n\n\nMeeting ID: 118 908 904\n\n\n\nInternational numbers available:\
 n<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fzoomconference%3Fm%
 3DRjcDSzvXlwMWG5gaHA7q936bD1fmNWjr=D=2=AFQjCNG7DcTq8EK0xbSNTfUk
 rgZFVafwOg>\nhttps://zoom.us/zoomconference?m=RjcDSzvXlwMWG5gaHA7q936bD1fm
 NWjr<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fzoomconference%3
 Fm%3DRjcDSzvXlwMWG5gaHA7q936bD1fmNWjr=D=2=AFQjCNG7DcTq8EK0xbSNT
 fUkrgZFVafwOg>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nWhen\n  
   Weekly from 7am to 8am on Wednesday Pacific Time\n\nWhere\nh
 ttps://zoom.us/j/118908904 (map<https://www.google.com/url?q=https%3A%2F%2
 Fzoom.us%2Fj%2F118908904=D=2=AFQjCNHVxs43K273zX8zrH6oVdZ_sDJiKQ
 >)\n\nCalendar\ndavid.sauvag...@bell.ca\n\nWho\n•\n 
kp...@linuxfoundation.org - creator\n\n•\ndavid.sauvageau@bel
 l.ca\n\n•\nonap-discuss@lists.onap.org\n\n\nGoing? All events in
  this series: Yes<https://www.google.com/calendar/event?action=RESPOND
 =ZnFocjBscjVhcDRtNzljZHR2aGs1ZmY2aGMgZGF2aWQuc2F1dmFnZWF1QGJlbGwuY2E=1
 =NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBnc
 m91cC5jYWxlbmRhci5nb29nbGUuY29tMzg4YTBkNDZhMDQyOWI4ZGE0NTcxNTZhNDU2NThhMTd
 lMDBkZDE3NQ=America/Los_Angeles=en> - Maybe<https://www.google.com/
 calendar/event?action=RESPOND=ZnFocjBscjVhcDRtNzljZHR2aGs1ZmY2aGMgZGF2
 aWQuc2F1dmFnZWF1QGJlbGwuY2E=3=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10
 YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tMzg4YTBkND
 ZhMDQyOWI4ZGE0NTcxNTZhNDU2NThhMTdlMDBkZDE3NQ=America/Los_Angeles=en
 > - No<https://www.google.com/calendar/event?action=RESPOND=ZnFocjBscj
 VhcDRtNzljZHR2aGs1ZmY2aGMgZGF2aWQuc2F1dmFnZWF1QGJlbGwuY2E=2=NzIjbG
 ludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxl
 bmRhci5nb29nbGUuY29tMzg4YTBkNDZhMDQyOWI4ZGE0NTcxNTZhNDU2NThhMTdlMDBkZDE3NQ
 =America/Los_Angeles=en> more options »<https://www.google.com/cal
 endar/event?action=VIEW=ZnFocjBscjVhcDRtNzljZHR2aGs1ZmY2aGMgZGF2aWQuc2
 F1dmFnZWF1QGJlbGwuY2E=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4
 Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tMzg4YTBkNDZhMDQyOWI4ZG
 E0NTcxNTZhNDU2NThhMTdlMDBkZDE3NQ=America/Los_Angeles=en>\n\nInvitat
 ion from Google Calendar<https://www.google.com/calendar/>\n\nYou are rece
 iving this courtesy email at the account david.sauvag...@bell.ca because y
 ou are an attendee of this event.\n\nTo stop receiving future updates for 
 this event\, decline this event. Alternatively you can sign up for a Googl
 e account at https://www.google.com/calendar/ and control your notificatio
 n settings for your entire calendar.\n\nForwarding this invitation could a
 llow any recipient to modify your RSVP response. Learn More<https://suppor
 t.google.com/calendar/answer/37135#forwarding>.\n\n\n\n\n
SUMMARY;LANGUAGE=en-US:Invitation: [oom] Weekly Meeting followup
DTSTART;TZID=US Eastern Standard Time:20170706T09
DTEND;TZID=US Eastern Standard Time:20170706T09
UID:132CB7B95EF340828C8DF76E925F6F970
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170706T124124Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://zoom.us/j/118908904
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2115449333
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR

Re: [onap-discuss] OOM PTL Poll Result

[Sauvageau, David]

Hi Viswa
Welcome! We will have a demo of what is available on the seed code and discuss 
milestone planning on our first weekly meeting next week. Trying to get the LF 
to send an invite
Thanks!

Envoy? de mon iPhone

Le 29 juin 2017 ? 03:41, Viswa KSP 
<kspviswa.git...@gmail.com<mailto:kspviswa.git...@gmail.com>> a ?crit :

Hi David,

I'm Viswa from Verizon and interested in joining? this efforts.

Please have me looped in.

BR,
Viswa

On Jun 29, 2017 12:53 AM, "Sauvageau, David" 
<david.sauvag...@bell.ca<mailto:david.sauvag...@bell.ca>> wrote:
Thanks all!

I will be setting up weekly meetings with the LF.

We have also uploaded seed code that we can start working from together! A 
Kubernetes/docker demo for installing key onap components is also available, so 
let me know if you are interested.

From: 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "HU, JUN NICOLAS" <jh2...@att.com<mailto:jh2...@att.com>>
Date: Monday, June 26, 2017 at 9:31 AM
To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: [onap-discuss] OOM PTL Poll Result


Hi there,

I'd like to share with you that the OOM PTL poll has been ended according to 
the planned poll period and the elected PTL is David Sauvageau.

Poll result: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4516726d2434dd38

Congratulations David.

Jun Nicolas Hu
SR MEMBER OF TECHNICAL 
STAFF<http://webphone.att.com/cgi-bin/orglist.pl?id=jh245g=0869=2=html>
AT
Email : jun.nicolas...@att.com<mailto:jun.nicolas...@att.com>
Office : +1 (732) 420-0743
200 S Laurel Ave, Rm D5-3B34
Middletown, NJ 08873
USA


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

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

Re: [onap-discuss] OOM PTL Poll Result

[Sauvageau, David]

Thanks all!

I will be setting up weekly meetings with the LF.

We have also uploaded seed code that we can start working from together! A 
Kubernetes/docker demo for installing key onap components is also available, so 
let me know if you are interested.

From:  on behalf of "HU, JUN NICOLAS" 

Date: Monday, June 26, 2017 at 9:31 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] OOM PTL Poll Result


Hi there,

I'd like to share with you that the OOM PTL poll has been ended according to 
the planned poll period and the elected PTL is David Sauvageau.

Poll result: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4516726d2434dd38

Congratulations David.

Jun Nicolas Hu
SR MEMBER OF TECHNICAL 
STAFF
AT
Email : jun.nicolas...@att.com
Office : +1 (732) 420-0743
200 S Laurel Ave, Rm D5-3B34
Middletown, NJ 08873
USA

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

[onap-discuss] [OOM] ONAP Operations Manager Project PTL Nominations

[Sauvageau, David]

Dear OOM Committers,

I would like to nominate myself as PTL for the ONAP Operations Manager (OOM) 
project.

I have been working at Bell Canada for 13 years in various technical roles IT 
and Networking domains and I am currently leading the technical team 
responsible for delivering ONAP into production for Bell Canada. I have been 
working on several network automation initiatives for the last 2 years with 
open source ECOMP/ONAP and other vendor products and know very well the 
challenges ahead of us. I have extensive agile project delivery experience and 
I believe that our objective to be fully operational into production with ONAP 
containers in 2017 as a service provider can greatly help shape the OOM project.

Thank you for your consideration and I look forward to working with the ONAP 
community!

David Sauvageau


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

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

[Sauvageau, David]

Hi Daniel.

For clarification, in the context of an L3 router.