Re: [onap-tsc] Please join the ONAP PTL meeting NOW!

2020-03-09 Thread Stephen Terrill via Lists.Onap.Org 
Hi,

There was a TSC decision on this 13, March, 2019: 
https://wiki.onap.org/display/DW/2019+TSC+Decisions

Each meeting can of course decide to change the meeting time wrt to UTC, as 
usual.

BR,

Steve

From: onap-tsc@lists.onap.org  On Behalf Of Morgan 
Richomme via Lists.Onap.Org
Sent: Monday, 9 March 2020 14:32
To: onap-tsc@lists.onap.org
Cc: DESBUREAUX Sylvain TGI/OLN 
Subject: Re: [onap-tsc] Please join the ONAP PTL meeting NOW!

Hi,

I already mentioned it in ONAP and OPNFV, the time MUST be in UTC - U means 
Universal, it is a reference to avoid confusion, it does not change whatever 
the timezone -
in the agenda the meeting is at 2PM UTC, so it starts in 30 minutes...

everybody usually knows the time change of his/her timezone but cannot know all 
the time changes of every time zones.

/Morgan



Le lundi 09 mars 2020 à 06:11 -0700, David McBride a écrit :
Team,

Sorry for the confusion.  The calendar currently lists the PTL meeting starting 
at 7 a.m. Pacific, in approximately 55 minutes.  That is NOT correct.  The 
meeting has started now.  If you are available, please join the call.  We will 
try to get the calendar fixed this week.

David


_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#6000): https://lists.onap.org/g/onap-tsc/message/6000
Mute This Topic: https://lists.onap.org/mt/71834092/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] [onap-modelingsub] Email Poll on As Built License Management Information Model

2019-12-11 Thread Stephen Terrill via Lists.Onap.Org 
Hi Andy, TSC, All,

I think that there are clarifications required on this before it can move 
forward as there are few things that I think we need to have this sorted.

  *   In archcom on 2019-10-08, the following was presented: 
https://wiki.onap.org/download/attachments/50202249/ONAP%20and%20xNF%20license%20mgmt%20-%20ArchCom%202019-10-08.pptx?api=v2
 .
 *   The conclusion was "Archcom recommends the following principle: "xNF 
capacity and feature license management is outside of the scope of the ONAP 
functionality." for now.
*   Need to show the interactions with the licence server in the flows."
  *   Then in modcom 2019-10-22 this was also discussed and I listened to the 
recording and I understood that the archcom decision was recognised and that a 
few representatives from ModCom were on that call.
 *   I hear in that recording that there were questions about whether this 
was the ArchCom recommendation, and this was questioned as there wasn't a vote 
or poll.  ArchCom has been driven by consensus driven discussions and I asked 
several times whether there was objections to the statements above, and there 
were not so that is the archcom recommendation
 *   There was a discussion about then why is there a use case.  The use 
case, as you probably know, is to show how the interaction with the licence 
manager (outside of onap) can work when the number of instances is not licence 
controlled.
 *   I find it strange to hear a discussion that is "I was in that 
discussion, I didn't say anything but I don't necessarily agree" and then go 
ahead and propose what appears to be recommendations in a different direction 
without coming back to where the original recommendation was mode.  It should 
be noted that the vendors proposing this have done so openly in the usecase 
subcommittee and in archcom.
  *   I am unsure whether the intention to approve this model is to state that 
this is the only way that xnfs can be licenced.  I don't want to go into the 
pros and cons of different licence approaches (as I am not an expert in that), 
but I do want to state that we can't have ONAP being a limit to the different 
licencing approaches.  Can you clarify whether the approval of this model is 
against the recommendation made in Archcom?

Then I have been of the understanding that the modelling to be approved was 
addressing the needs of the functional, non-functional and use case 
requirements, which is why the model approval was wanted before a certain time. 
 I was un-clear on which use case this particular model was addressing?  I was 
unclear on how it actually addresses the use cases that are in the scope of the 
frankfurt release.  If there are principle approaches here, then I think they 
need to be raised upto the TSC.

I would suggest a clarification to the TSC on the above.

Best Regards,

Steve

From: onap-modeling...@lists.onap.org  On 
Behalf Of Andy Mayer via Lists.Onap.Org
Sent: Tuesday, 10 December 2019 16:10
To: onap-modeling...@lists.onap.org
Subject: Re: [onap-modelingsub] Email Poll on As Built License Management 
Information Model

POLLING DEADLINE EXTENDED
The polling period will be open until 22:00GMT on 19 December. 2019.
We will address rough consensus during the 13 January 2020 Modeling 
Subcommittee weekly call.

Best Regards,
Andy and DENG Hui


From: onap-modeling...@lists.onap.org 
mailto:onap-modeling...@lists.onap.org>> On 
Behalf Of MAYER, ANDREW J
Sent: Wednesday, December 4, 2019 12:00 PM
To: onap-modeling...@lists.onap.org
Subject: [onap-modelingsub] Email Poll on As Built License Management 
Information Model

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

According to last week's modeling call, the Modeling Subcommittee has initiated 
a poll to determine whether the modeling of the "as built" ONAP "License 
Management Information Model" is ready to be moved to the "Clean" state.

The related wiki pages can be found at: 
https://wiki.onap.org/display/DW/License+Management

Please submit only 1 vote per company to this email list. The polling period 
will be open until 22:00GMT on 12 19 December. 2019.
We will address rough consensus during the 17 December 2019 13 January 2020 
Modeling Subcommittee weekly call.
The chairs strongly recommend that clear rationale be expressed along with any 
"No" vote.

To vote: Please reply to this email (to onap-modelingsub@lists-onap-org) with: 
"YES"; "NO"; or "Abstain" to indicate:
YES: The proposed model IS ready to move to the "Clean" State
NO: The propose

Re: [onap-tsc] Reorg of subcommittee pages on ONAP Wiki?

2019-11-21 Thread Stephen Terrill via Lists.Onap.Org 
+1

From: onap-tsc@lists.onap.org  On Behalf Of Chaker 
Al-Hakim via Lists.Onap.Org
Sent: Thursday, 21 November 2019 20:50
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Reorg of subcommittee pages on ONAP Wiki?

Hi Kenny,

Even though I am no longer a member of the TSC  I do like your idea. In 
addition, and at the same level as the subcommittee  page, you may want to 
consider a place holders for "Task Force", "Special Projects", "TCC" , etc..

Regards,
Chaker


From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Kenny 
Paul via Lists.Onap.Org
Sent: Thursday, November 21, 2019 2:40 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Reorg of subcommittee pages on ONAP Wiki?

Hello everyone,

Currently all the subcommittee pages are direct children of the TSC page. To 
clean things up a bit I would like to realign the subcommittee landing pages 
under a parent subcommittee page.

Proposed structure:  TSC Home -> Subcommittee Home -> Subc-A, Subc-B, Subc-C, 
...

Thoughts?

Thanks!
-kenny



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5692): https://lists.onap.org/g/onap-tsc/message/5692
Mute This Topic: https://lists.onap.org/mt/61117266/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Prague co-meeting with CNTT

2019-11-21 Thread Stephen Terrill via Lists.Onap.Org 
Hi Jim,

It would be helpful if you could elaborate on what you saw as the most 
significant intersecting topics  as the term “solution deployment” is quite a 
large scope -  Actually – it would be great if there were suggestions from CNTT 
on the questions that have where ONAP could help – orchestration is clear – but 
beyond that it wasn’t obvious from the last joint meeting nor in the meeting 
planning , then I think the time allocation can be considered.

BR,

Steve



From: onap-tsc@lists.onap.org  On Behalf Of Jim Baker 
via Lists.Onap.Org
Sent: Thursday, 21 November 2019 20:29
To: onap-tsc 
Cc: Lincoln Lavoie ; Rabi, Abdel, Vodafone Group 
; COTTRELL, MARK ; BELTRAN, JONATHAN 
; TENNANT, RICK 
Subject: [onap-tsc] Prague co-meeting with CNTT

Greetings!
With the Prague f2f meeting looming, I wanted to reach out to the ONAP 
community and plan the CNTT interactions in Prague. We can allocate 2-3 hours 
of time to this collaboration if we can come up with an appropriate agenda. 
While CNTT is chartered to specify the Common NFVI, the CNTT community is 
concerned about the time to solution deployment - which includes VNFs and 
orchestrators. Since ONAP contributes to both VNF validation and orchestration, 
it would make sense to focus our attentions there...

Please respond to all on this email with your ideas for topics. Once I get a 
set of ideas, I'll consolidate and share back to you and offer up a discussion 
time (if needed) for the agenda planning. Please focus on discussion topics 
that need inputs/discussion, NOT on presentation that tend to be one-way 
conversations. Also, while I suggested an obvious area of interest, many other 
areas are fertile for topics: security, solution stack testing, etc. are all 
welcome!

LFN Developer and Testing Forums is the place where the community comes 
together and is one of the key benefits of LFN membership - let's make it 
count! ALL ideas are welcome - this is a community brain-storming session - so 
bring your ideas!
Kind regards,
Jim


--
Jim Baker
Linux Foundation Networking - Technical Program Manager
mobile: +1 970 227 6007


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5691): https://lists.onap.org/g/onap-tsc/message/5691
Mute This Topic: https://lists.onap.org/mt/61115299/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Lab closure clarification

2019-11-21 Thread Stephen Terrill via Lists.Onap.Org 
Hi David,

I think it will help ( - certainly Jan 9th seems very challenging); and it 
depends on the community as well – additional meetings can be called – I want 
to highlight it for the overall planning; previously we did about 4 projects a 
meeting (1/2 hour each) – meaning about 7-8 meetings worth.  I wanted to 
highlight that now so that I don’t get to the start the start of January and 
try to review everything in one week.

BR,

Steve

From: onap-tsc@lists.onap.org  On Behalf Of David 
McBride via Lists.Onap.Org
Sent: Thursday, 21 November 2019 15:05
To: onap-tsc 
Subject: Re: [onap-tsc] Lab closure clarification

Thanks, Steve.

Are you saying that the proposed schedule change to Jan 21 will not allow 
enough time for the project level arch review? Please advise.

David

On Wed, Nov 20, 2019 at 2:19 PM Stephen Terrill via 
Lists.Onap.Org<https://protect2.fireeye.com/v1/url?k=63e6cd51-3f32c437-63e68dca-8610d8a762ca-ca68787d527ada62&q=1&e=d334cd11-4325-4b65-9ee5-0ffe0dfad928&u=http%3A%2F%2Flists.onap.org%2F>
 
mailto:ericsson@lists.onap.org>>
 wrote:
Hi David,

Not on the topic of the lab closure – but on the topic of the M2/M3 milestone- 
One thing to keep in mind – for M2/M3 there should be a project level 
architecture review.  This time I would like to see that we approve the 
architecture description for each project in the project architecture review – 
the update of these 
(https://wiki.onap.org/display/DW/ONAP+Architecture+Component+Description+-+Frankfurt<https://protect2.fireeye.com/v1/url?k=00f2662c-5c266f4a-00f226b7-8610d8a762ca-711dfebe7ed83edb&q=1&e=d334cd11-4325-4b65-9ee5-0ffe0dfad928&u=https%3A%2F%2Fwiki.onap.org%2Fdisplay%2FDW%2FONAP%2BArchitecture%2BComponent%2BDescription%2B-%2BFrankfurt>)
 – I will send out instructions.  I can only assume that it will take a few 
weeks to process the review.

Best Regards,

Steve.

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
mailto:onap-tsc@lists.onap.org>> On Behalf Of David 
McBride via 
Lists.Onap.Org<https://protect2.fireeye.com/v1/url?k=cab12a0e-96652368-cab16a95-8610d8a762ca-8e840e36ac13c47b&q=1&e=d334cd11-4325-4b65-9ee5-0ffe0dfad928&u=http%3A%2F%2Flists.onap.org%2F>
Sent: Friday, 15 November 2019 23:46
To: onap-tsc mailto:onap-tsc@lists.onap.org>>; Brian 
Freeman mailto:bf1...@att.com>>
Subject: Re: [onap-tsc] Lab closure clarification

Brian,

Yes, I agree.

Please excuse my ignorance as I climb the learning curve with ONAP, but could 
you explain in more detail specifically what functionality is being lost during 
the move?  Thanks.

David

On Fri, Nov 15, 2019 at 11:39 AM Brian Freeman 
mailto:bf1...@att.com>> wrote:
Yipan,

Staring on Jan 6th seems like a very reasonable start date. We would plan for a 
week as you suggest just in case.
I assume all the data will be preserved (cinder volumes, vm’s and stacks etc) ?
Will we need to help gracefully shutdown things in advance ?

Probably need to have a planning session on anything we can do to help ensure 
success as tenants :)

David,

We need to make sure that M2/M3 is after Jan 14th . Right now per 
https://wiki.onap.org/display/DW/Release+Planning%3A++Frankfurt<https://protect2.fireeye.com/v1/url?k=f89ba827-a41207aa-f89be8bc-0cc47ad93de2-9523f07ad69ca42a&q=1&e=041e58b2-365f-43be-86cc-20f323d1c1f3&u=https%3A%2F%2Fwiki.onap.org%2Fdisplay%2FDW%2FRelease%2BPlanning%253A%2B%2BFrankfurt>
 I think its January 9th.

Brian




From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Yipan 
Deng
Sent: Friday, November 15, 2019 2:17 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-tsc] Lab closure clarification

Hi David & TSC,

For Intel/Windriver Integration Lab located at Intel campus in Oregon, 
currently we are looking at moving the physical Lab starting from Jan. 6th, 
2020 for about a week (or shorter). During that period of time, there won’t be 
any remote access to the lab.

We tentatively shooting for this window considering the New Year holiday impact 
and believed this might create the least disruption to the ONAP community. 
Please feel free to let us know if you have different opinion and we are open 
for community feedbacks on lab move window.

Thanks,
Yipan
Intel ONAP/Akraino PM

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
mailto:onap-tsc@lists.onap.org>> On Behalf Of David 
McBride
Sent: Friday, November 15, 2019 9:05 AM
To: onap-tsc mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] Lab closure clarification

Who can provide detailed input about these events?

For both, we need to know:

  *   Start date
  *   Duration
  *   Degree of confidence in timing
  *   Scope of impact
David

On Thu, Nov 14, 2019 at 11:06 AM Brian Freeman 
mailto:bf1...@att.com>> wrote:
Two different events bu

Re: [onap-tsc] Lab closure clarification

2019-11-20 Thread Stephen Terrill via Lists.Onap.Org 
Hi David,

Not on the topic of the lab closure – but on the topic of the M2/M3 milestone- 
One thing to keep in mind – for M2/M3 there should be a project level 
architecture review.  This time I would like to see that we approve the 
architecture description for each project in the project architecture review – 
the update of these 
(https://wiki.onap.org/display/DW/ONAP+Architecture+Component+Description+-+Frankfurt)
 – I will send out instructions.  I can only assume that it will take a few 
weeks to process the review.

Best Regards,

Steve.

From: onap-tsc@lists.onap.org  On Behalf Of David 
McBride via Lists.Onap.Org
Sent: Friday, 15 November 2019 23:46
To: onap-tsc ; Brian Freeman 
Subject: Re: [onap-tsc] Lab closure clarification

Brian,

Yes, I agree.

Please excuse my ignorance as I climb the learning curve with ONAP, but could 
you explain in more detail specifically what functionality is being lost during 
the move?  Thanks.

David

On Fri, Nov 15, 2019 at 11:39 AM Brian Freeman 
mailto:bf1...@att.com>> wrote:
Yipan,

Staring on Jan 6th seems like a very reasonable start date. We would plan for a 
week as you suggest just in case.
I assume all the data will be preserved (cinder volumes, vm’s and stacks etc) ?
Will we need to help gracefully shutdown things in advance ?

Probably need to have a planning session on anything we can do to help ensure 
success as tenants :)

David,

We need to make sure that M2/M3 is after Jan 14th . Right now per 
https://wiki.onap.org/display/DW/Release+Planning%3A++Frankfurt
 I think its January 9th.

Brian




From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Yipan 
Deng
Sent: Friday, November 15, 2019 2:17 PM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Lab closure clarification

Hi David & TSC,

For Intel/Windriver Integration Lab located at Intel campus in Oregon, 
currently we are looking at moving the physical Lab starting from Jan. 6th, 
2020 for about a week (or shorter). During that period of time, there won’t be 
any remote access to the lab.

We tentatively shooting for this window considering the New Year holiday impact 
and believed this might create the least disruption to the ONAP community. 
Please feel free to let us know if you have different opinion and we are open 
for community feedbacks on lab move window.

Thanks,
Yipan
Intel ONAP/Akraino PM

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of David 
McBride
Sent: Friday, November 15, 2019 9:05 AM
To: onap-tsc mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] Lab closure clarification

Who can provide detailed input about these events?

For both, we need to know:

  *   Start date
  *   Duration
  *   Degree of confidence in timing
  *   Scope of impact
David

On Thu, Nov 14, 2019 at 11:06 AM Brian Freeman 
mailto:bf1...@att.com>> wrote:
Two different events but need to undertand the timing with the latest Frankfurt 
schedule to assess impact.

Brian


From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Kenny 
Paul
Sent: Thursday, November 14, 2019 2:02 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Lab closure clarification

From the minutes today Srini brought up the Intel lab closure in January.
Brian asked a schedule question resulting from the Windriver lab closure.

In this context, one in the same or 2 different events?

Thanks!
-kenny



--
David McBride
Release Manager
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
IRC: dmcbride


--
David McBride
Release Manager
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
IRC: dmcbride


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5673): https://lists.onap.org/g/onap-tsc/message/5673
Mute This Topic: https://lists.onap.org/mt/57995264/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Courtesy update regarding the ONAP TSC Elections

2019-11-04 Thread Stephen Terrill via Lists.Onap.Org 
Dear All,

I wanted to take a few moments to share a few words.  As you know I have been 
involved with the ONAP journey from the TSC perspective (architecture and 
SECCOM  as well) from its inception and have seen the creation and growth of 
this community which has been an amazing journey.  We see that as part of this 
journey, ONAP is now moving to a phase with ever increasing relevance for 
product development, and as such we want to adjust our contribution to the 
community (TSC) steering accordingly.For this purpose I am very happy that 
Ciaran has stepped up to self nominate as I have been working with him for 
quite some time and I am sure, if elected, he will do a great job - and indeed 
he has also been my stand-in a number of times.  I wanted to add - this is not 
an exit but a transformation - my intention to remain involved, but from 
another supporting perspective as time allows.

Best Regards,

Steve

[http://www.ericsson.com]

Stephen Terrill
Senior Expert, Automation and Management

TECHNOLOGY SPECIALIST
BDGS RDP Architecture & Technology
Phone: +34913393005
Mobile: +34609168515
stephen.terr...@ericsson.com

Ericsson
C/ Via de los Poblados 13. B
28033,Madrid, Madrid
Spain
ericsson.com

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

Our commitment to Technology for 
Good 
and Diversity and 
Inclusion contributes 
to positive change.
Follow us on: Facebook 
LinkedIn 
Twitter

Legal entity:ERICSSON AB registration number 556056-6258, registered office in 
Stockholm.
This communication is confidential. Our email terms: 
www.ericsson.com/en/legal/privacy/email-disclaimer

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5570): https://lists.onap.org/g/onap-tsc/message/5570
Mute This Topic: https://lists.onap.org/mt/41267004/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] [Onap-arc] Arch Tracking for Frankfurt

2019-10-07 Thread Stephen Terrill via Lists.Onap.Org 
Hi Lin,

Thank-you for the update.   I believe that the original request was to have the 
requirements clear and ready by the end of September for prioritization, so I 
guess as soon as is feasible.

To be fair, the multi-domain optical service has been presented and there 
weren’t noted issues, just requesting due diligence by checking synergies with 
CCVPN, but we should still close that off properly.  The slicing – I assume its 
OK – I just don’t know as any updates and implications havent’t been seen.

BR,

Steve

From: LinMeng 
Sent: Saturday, 5 October 2019 16:03
To: Stephen Terrill ; onap-...@lists.onap.org; 
onap-tsc@lists.onap.org
Cc: denise.provenc...@us.fujitsu.com; swaminathan.seethara...@wipro.com; 
xin.m...@us.fujitsu.com; Henry Yu ; Gaurav agrawal 

Subject: Re: [Onap-arc] Arch Tracking for Frankfurt

Hi Steve,
REQ-146 is also relavant to slicing evolution. But According to F2F discussion, 
REQ-158 and REQ-146 will be merged into one use case. We are working on the 
combination work for Arc review.

Also, Mutidomain optical service is also asked to be merged into CCVPN, so we 
also need to merge REQ-37 and REQ-141. We also will prensent our combination 
work for Arc review.

May I ask when is the deadline for us to present our combination work and when 
is the due for finalizing Arc requirement for Frankfurt?

Best,
Lin

发件人: mailto:onap-...@lists.onap.org>> 代表 "Stephen 
Terrill via Lists.Onap.Org" 
mailto:stephen.terrill=ericsson@lists.onap.org>>
答复: mailto:stephen.terr...@ericsson.com>>
日期: 2019年10月3日 星期四 23:17
收件人: "onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>" 
mailto:onap-...@lists.onap.org>>, 
"onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" 
mailto:onap-tsc@lists.onap.org>>
抄送: mailto:onap-...@lists.onap.org>>
主题: [Onap-arc] Arch Tracking for Frankfurt

Hi,

I have been trying to track what I think is relivant to consider from an 
architecture prespective for the frankfurt release and note it here: 
https://wiki.onap.org/display/DW/ONAP+Frankfurt+Release+Architecture+Requirements

Later I can fold these results into the pink/purple recommendation in the 
frankfurt requirements.

If you feel this is incorrect, please let me know.

BR,

Steve

[http://mediabank.ericsson.net/internet-media/Email_logo_Ericsson.png]<http://www.ericsson.com/>

Stephen Terrill
Senior Expert, Automation and Management

TECHNOLOGY SPECIALIST
BDGS RDP Architecture & Technology
Phone: +34913393005
Mobile: +34609168515
stephen.terr...@ericsson.com<mailto:stephen.terr...@ericsson.com>

Ericsson
C/ Via de los Poblados 13. B
28033,Madrid, Madrid
Spain
ericsson.com<http://www.ericsson.com/>

[http://mediabank.ericsson.net/internet-media/Email_Message.gif]<http://www.ericsson.com/current_campaign>

Our commitment to Technology for 
Good<http://www.ericsson.com/thecompany/sustainability-corporateresponsibility> 
and Diversity and 
Inclusion<http://www.ericsson.com/thecompany/diversity-inclusion> contributes 
to positive change.
Follow us on: Facebook<https://www.facebook.com/ericsson> 
LinkedIn<https://www.linkedin.com/company/ericsson> 
Twitter<https://twitter.com/Ericsson>

Legal entity:ERICSSON AB registration number 556056-6258, registered office in 
Stockholm.
This communication is confidential. Our email terms: 
www.ericsson.com/en/legal/privacy/email-disclaimer<https://www.ericsson.com/en/legal/privacy/email-disclaimer>


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5460): https://lists.onap.org/g/onap-tsc/message/5460
Mute This Topic: https://lists.onap.org/mt/34405274/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Arch Tracking for Frankfurt

2019-10-03 Thread Stephen Terrill via Lists.Onap.Org 
Hi,

I have been trying to track what I think is relivant to consider from an 
architecture prespective for the frankfurt release and note it here: 
https://wiki.onap.org/display/DW/ONAP+Frankfurt+Release+Architecture+Requirements

Later I can fold these results into the pink/purple recommendation in the 
frankfurt requirements.

If you feel this is incorrect, please let me know.

BR,

Steve

[http://www.ericsson.com]

Stephen Terrill
Senior Expert, Automation and Management

TECHNOLOGY SPECIALIST
BDGS RDP Architecture & Technology
Phone: +34913393005
Mobile: +34609168515
stephen.terr...@ericsson.com

Ericsson
C/ Via de los Poblados 13. B
28033,Madrid, Madrid
Spain
ericsson.com

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

Our commitment to Technology for 
Good 
and Diversity and 
Inclusion contributes 
to positive change.
Follow us on: Facebook 
LinkedIn 
Twitter

Legal entity:ERICSSON AB registration number 556056-6258, registered office in 
Stockholm.
This communication is confidential. Our email terms: 
www.ericsson.com/en/legal/privacy/email-disclaimer

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5454): https://lists.onap.org/g/onap-tsc/message/5454
Mute This Topic: https://lists.onap.org/mt/34383091/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] WIKI access

2019-09-16 Thread Stephen Terrill via Lists.Onap.Org 
Hi,

It seems like the ability to log into the ONAP wiki is down for the moment.

BR,

Steve

[http://www.ericsson.com]

Stephen Terrill
Senior Expert, Automation and Management

TECHNOLOGY SPECIALIST
BDGS RDP Architecture & Technology
Phone: +34913393005
Mobile: +34609168515
stephen.terr...@ericsson.com

Ericsson
C/ Via de los Poblados 13. B
28033,Madrid, Madrid
Spain
ericsson.com

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

Our commitment to Technology for 
Good 
and Diversity and 
Inclusion contributes 
to positive change.
Follow us on: Facebook 
LinkedIn 
Twitter

Legal entity:ERICSSON AB registration number 556056-6258, registered office in 
Stockholm.
This communication is confidential. Our email terms: 
www.ericsson.com/en/legal/privacy/email-disclaimer

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5426): https://lists.onap.org/g/onap-tsc/message/5426
Mute This Topic: https://lists.onap.org/mt/34164690/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Vodafone - TSC transition

2019-09-02 Thread Stephen Terrill via Lists.Onap.Org 
Thank-you for your contribution Susana, it was nice to cross paths again.  
Welcome Davide.

From: onap-tsc-priv...@lists.onap.org  On 
Behalf Of Susana Sabater via Lists.Onap.Org
Sent: Monday, 2 September 2019 8:55
To: onap-tsc-priv...@lists.onap.org; onap-tsc@lists.onap.org
Cc: onap-tsc-priv...@lists.onap.org
Subject: [onap-tsc-private] Vodafone - TSC transition

Dear all,

As you may have noticed, I have been out of the TSC for several months as I am 
engaged in other initiatives. As my available time to dedicate to ONAP is not 
expected to increase, I have decided to resign and appoint Davide Cherubini to 
take the Vodafone TSC seat in accordance to clause 4.2.3.4 of the community 
charter.
Davide is an active member of the community as per his stats.
I wish you all the best luck with ONAP!

Best regards
/Susana



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5398): https://lists.onap.org/g/onap-tsc/message/5398
Mute This Topic: https://lists.onap.org/mt/33108630/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-