[onap-tsc] Dublin Release F2F Developer Design Forum - January 8-11, 2019, France

[Kenny Paul]

(bcc'd to onap-discuss)

 

Great News! The date and location for the F2F ONAP Developer Design Forum have 
been set!

 

Dates:  January 8-11, 2019

Location: 

Nokia Paris-Saclay
Route de Villejust, 91620 Nozay, France
+33 01 60 40 60 40 

A big thank you to Nokia for providing the event space! This is the same site 
as the developer forum we held in the Fall of 2017.

The registration page is not yet up but it will be within the next few days. As 
this event is being planned as a joint ONAP DDF and OPNFV Plugfest, I have 
created wiki page on the LFN site, rather than on the ONAP wiki. 
https://wiki.lfnetworking.org/display/LN/OPNFV-ONAP+January+2019  There you 
will find a link to start collecting Session Proposals. Note: you will need to 
create an LFN wiki account if you don't already have one to add something to 
the session page.

Additional details are still being fleshed out.

 

Best Regards, 
-kenny

Kenny Paul, Technical Program Manager, The Linux Foundation
kp...@linuxfoundation.org, 510.766.5945
San Francisco Bay Area, Pacific Time Zone

 

 


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

View/Reply Online (#3965): https://lists.onap.org/g/onap-tsc/message/3965
Mute This Topic: https://lists.onap.org/mt/27525808/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] ONAP items for online store

[Nermin Mohamed]

Hi,

There is web store that was launched spring 2018. This web store provides a 
catalog of items available for anyone and it will also be used to provide swag 
for events e.g a code will be distributed at the events and recipients will 
redeem them for free items and free shipping from the web store.

We are in the process of finalizing our 2019 marketing budget and would like to 
include budget for additional items for the web store so We want to collect a 
feedback from the ONAP community on the items that you all would like to have 
in 2019.

Please send your feedback to Casey, Lisa and myself cc'd above

Here is the link to the web store  https://linuxfoundation.store/ . It is also 
accessible from the main Wiki from the "about" section of onap.org.


Thanks!
Nermin



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

View/Reply Online (#3964): https://lists.onap.org/g/onap-tsc/message/3964
Mute This Topic: https://lists.onap.org/mt/27486839/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] SP priorities for Dublin

[Alla Goldner]

Hi,

I created the following table 
https://wiki.onap.org/display/DW/SP+priorities+for+Dublin for introducing SP 
priorities for Dublin both proactively and reactively (e.g. following proposals 
of a different functional requirements and use cases).

Functional requirements and use case owners - please include your favorite 
requirements into the table (and, if use case consists of several requirements  
- please split).
SP - please start including your own requirements from Dublin into this page.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D46A39.75129820]

“Amdocs’ email platform is based on a third-party, worldwide, cloud-based 
system. Any emails sent to Amdocs will be processed and stored using such 
system and are accessible by third party providers of such system on a limited 
basis. Your sending of emails to Amdocs evidences your consent to the use of 
such system and such processing, storing and access”.

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

View/Reply Online (#3963): https://lists.onap.org/g/onap-tsc/message/3963
Mute This Topic: https://lists.onap.org/mt/27486689/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] [onap-modeling], [onap-discuss], [modeling] Some thoughts regarding the modelling of VNFs/PNFs

[Bernard . Tsai]

Hello ONAP ARCHCOM and MODCOM members,

please allow me to introduce myself - I am working for Deutsche Telekom 
focussing on the automation of the lifecycle of VNFs residing in cloud 
infrastructures. Marc Fiedler and Andreas Geissler have asked me to share with 
the ONAP community some of our thoughts regarding the modelling of these 
entities and I would be very happy to join the discussion here and develop with 
you answers to some of the most urgent issues we are facing currently.

I apologize for the lengthy mail but do hope that some of the aspects presented 
here might be of interest for the community since they address issues which we 
have been facing and for which have not seen desirable solutions yet. So here 
goes:

Automation of the lifecycle of VNFs/PNFs
The main objectives when increasing the degree of automation of the lifecycles 
of VNFs and PNFs are to:

  *   increase the agility when introducing changes and updates,
  *   decrease the cost of operations and
  *   improve overall service quality.

This approach assumes that the effort involved with the introduction of new 
automation tools will be substantially less than when continuing with processes 
dominated by manual interventions. VNFs as well as PNFs nowadays consist of a 
multitude of different components with following characteristics:

  *   large number of elements
  *   huge variety of different technologies
  *   need for frequent changes (outages, patches, updates, capacity 
adjustments, ...)
  *   complex dependencies between the elements
  *   mixture of management concepts for both legacy and cloud native solutions
These aforementioned constraints unfortunately all increase the complexity for 
automation solutions.

Major issues
Solutions for two major obstacles still must be found to fully reap the 
benefits of automation in the VNF/PNF domain:

   Integration into the infrastructure environment
Mapping the capabilities of an automation solution onto a specific 
environment requires a clear policy of how to model and make use of these assets
(the specifics of the environment being: e.g. distribution of 
datacenter and availability zones, supported virtualization technology, 
supported optimized network drivers (smart NICs, SR-IOV, DPDK, ...), security 
constraints, ... ). Due to the variety of different possible environments the 
complexity of the automation solution might explode.

CI/CD integration
Lifecycle management of VNFs/PNFs requires close cooperation 
between the solution providers and the telco operators especially in the case 
where the responsibilities for the elements change in the course of the 
lifecycle (DevOps is only a partial answer if an external vendor provides the 
solution but an internal telco DevOps team is responsible  for integration and 
operations). The customization and configuration of the solutions require a 
clear understanding of which parameters are related to the telco specific 
context and which parameters are general characteristics of the product.

Modelling guidelines
It is necessary to differentiate between the tools (orchestrators, controllers, 
...) executing the instructions which have been captured in a set of abstracted 
models, the protocols (REST, api, cli, ...) of how the automation information 
is exchanged, the message format of the automation information (TOSCA, yaml, 
xml, json, ...) and the schema/semantic information describing the actual 
elements and their configuration (ETSI NFV, ...).

[onap.png]

Based on a crude schematic description of the ONAP architecture following 
guidelines are regarded to be useful:

  *   the designer is a tool which allows to describe the desired structure and 
interaction of the elements of the VNFs/PNFs
  *   controllers are specialized tools to manage the lifecycle of elements of 
a specific type
  *   orchestrators coordinate the individual actions of the controllers by 
taking care of the dependencies between different elements
  *   orchestrators should ideally not have to manipulate the configuration 
data of the various elements
  *   controllers receive configuration data from the controller and return 
state and endpoint information related to the services which the elements 
provide
  *   elements should ideally all support a basic set of lifecycle states and 
transitions (e.g. MTOSI)
  *   controllers are triggered by the orchestrator to drive an element towards 
a desired lifecycle state (intent based API) or are instructed to execute a 
specific lifecycle state transition (e.g. start, stop, ...)
  *   elements need to be mapped to a specific type which allows to identify 
which controller to choose for automating its lifecycle
  *   the dependencies between elements need to be categorized so that the 
orchestrator can make use of this information to trigger cascading actions in 
the course of changes of individual elements

Specifically:

  *   due to the 

Re: [E] [onap-tsc] MoM/Action Items (Oct 18th) and Agenda Preparation (Oct 25th) #tsc

[Catherine LEFEVRE]

Good morning Viswa,

Your understanding is correct.
The Wiki page has also been updated accordingly: 
https://wiki.onap.org/display/DW/Dublin+Architecture+Planning+Meeting
The registered people will also receive a notification.

Best regards
Catherine

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Viswanath Kumar Skand Priya via Lists.Onap.Org
Sent: Friday, October 19, 2018 10:40 AM
To: onap-tsc 
Subject: Re: [E] [onap-tsc] MoM/Action Items (Oct 18th) and Agenda Preparation 
(Oct 25th) #tsc

Hi Catherine,

Regarding Dublin Arch F2F, I'm understanding your mail as : the venue has been 
changed from  IBM Montreal Innovation 
Center
 to Montreal Marriott Chateau Champlain
Is my understanding correct?

BR,
Viswa

[http://ss7.vzw.com/is/image/VerizonWireless/vz-sig-verizon?$defaultscale$]

Viswanath Kumar Skand Priya
Senior Architect
Technology, Architecture & Planning



On Fri, Oct 19, 2018 at 1:46 PM Catherine LEFEVRE 
mailto:catherine.lefe...@intl.att.com>> wrote:
Dear ONAP Community,

Our Oct 18th TSC Meeting Notes have been posted – Thank you Kenny/Gildas !
https://wiki.onap.org/display/DW/TSC+2018-10-18

Here are the Urgent Tasks to be completed within the next 2 weeks:

· Kick-off the TSC Seat Vacant election process (self-nomination and 
vote) – Task Lead: Kenny Paul - Target: Oct 22th

· Security Assessment with PTLs (TSC-17) – Task Lead: Stephen Terrill – 
Target: Oct 25th

· 5G PNF Plug and Play Ansible Playbook (TSC-26) – Task Lead: Gildas - 
Target: Oct 25th

In preparation of the F2F Dublin Architecture/Modeling meeting, it will be 
important that the following activities are finalized by Oct 25th
So these inputs can be considered during the workshop:

· Collect Dublin LFN End User Group Use Cases (TSC-5) – Task Lead: Eric 
Debeau

· EUAG Survey (TSC-11) – Task Lead: Ranny Haiby

· Present Operator’s Feedback (TSC-9) – Task Lead: Phil Robb

· Accelerate adoption of ONAP in production (Dublin Use Cases) 
(TSC-13)- Task Force: Chaker Al-Hakim

TSC Dashboard:
https://jira.onap.org/secure/RapidBoard.jspa?projectKey=TSC=163

TSC Decisions
https://wiki.onap.org/display/DW/2018+TSC+Decisions

Next TSC Call
The TSC agenda will be reviewed on Wednesday (Oct 24th).
Priority to the Casablanca RC1 (Release Candidate 1) milestone review.

Here is the wiki link:
https://wiki.onap.org/display/DW/TSC+2018-10-25+Meeting+Agenda

Upcoming Events

•Oct 22nd-23rd (New York): ONAP Academic Summit: 
https://wiki.onap.org/display/DW/ONAP+Academic+Summit+-+October+2018

•Oct 29th- Oct 31st  (Montreal): F2F Architecture/Modeling Dublin 
Workshop: