[onap-tsc] Reproducible Beijing Deployments

Hello I agree we need a stable installation, but the creation of a new branch should be decided at the TSC level and not by "some key members of the Community". To be considered as lessons learnt and Casablanca. We must improve the way to setup ONAP and work as early as possible for

[onap-tsc] [onap-discuss] Action Plan towards Casablanca => ONAP introduction course

Hello A very good EdX course on ONAP introduction "Introduction to ONAP: Complete Network Automation" https://courses.edx.org/courses/course-v1:LinuxFoundationX+LFS163x+1T2018/course/ After reminding some basic NFV concepts, the course explains ONAP, the architecture, the main components and

[onap-tsc] tagging issues

Hello We still have some problems in the ONAP versioning/tagging. In the Amsterdam version environment file (https://git.onap.org/demo/plain/heat/ONAP/onap_openstack.env?h=amsterdam) , there is still one project based on master branch. The Docker tags are not all aligned (some start with v,

[onap-tsc] Does this work?

Hello and happy new year 2018 Both links work fine for me. Best Regards Eric _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou

[onap-tsc] Project part of Wiki

Hello I think the Wiki should only list the projects for Beijing Release. The list of projects per (old) release should only be described on the Readthedocs. Best Regards Eric

[onap-tsc] Project minutes report using ircbot

Hello Morgan proposed to use the ircbot to generate the minutes for Integration project https://lists.onap.org/pipermail/onap-discuss/2017-December/006780.html I think the proposal from Morgan is great and should be used by the various projects ;-) Best Regards Eric

[onap-tsc] Use-Case documents

Hello There are 2 interesting short documents to explain the Amsterdam blueprints. https://www.onap.org/wp-content/uploads/sites/20/2017/11/ONAP_CaseSolution_vCPE_FNL.pdf https://www.onap.org/wp-content/uploads/sites/20/2017/11/ONAP_CaseSolution_VoLTE_FNL.pdf Who did produce these documents and

[onap-tsc] [arch] Corrections for the architecture document.

Hello Please find some corrections for the Architecture document https://www.onap.org/wp-content/uploads/sites/20/2017/11/ONAP_CaseSolution_Architecture_FNL.pdf As noticed by Nermin, the D2 term should be removed from Figure 1 P7. Controllers I think the VF-C definition is not exact according

[onap-tsc] ona-user mailing list?

+10 Very good idea. We should also share some artifacts on any open source VNF we tested ;-) Eric _ Ce message et ses pieces jointes peuvent contenir des informations

[onap-tsc] Transparency first

Hello I would like to share some feedbacks from the yesterday TSC. We are working in an open source community with some guidelines from the ONAP TSC Charter "The Open Network Automation Platform (ONAP) will operate transparently, openly, collaboratively, and ethically". As a result, we must

[onap-tsc] ONAP Branching : Amsterdam maintenance

Hello As we are discussing branching topics for the TSC Call today, I would like to share some vision from a service provider perspective. We intend to use Amsterdam Release for internal POC and first trial to demonstrate the capabilities to operational teams, to educate...While I know some

[onap-tsc] Linux Foundation Networking Projects Informational Update

Thanks Kenny for sharing the recording Is it possible to get the slide deck ? It is easier to share. Best Regards Eric _ Ce message et ses pieces jointes peuvent contenir

[onap-tsc] Global technical vision

Hello I would like to share a topic raised by Michal on DCAE GEN2 dependency on OpenStack Designate (https://lists.onap.org/pipermail/onap-discuss/2017-October/005660.html) I believe that the TSC should be informed when a project takes a technical decision that may impact other projects or the

[onap-tsc] First ONAP Hackathon

Thanks Alla for sharing. It is cool that some VNF vendors could integrate their own VNF with ONAP. I think we organize such events in various places to promote ONAP. Best Regards Eric

[onap-tsc] Proposing ONAP CLI as MVP

Hello Kanagaraj I confirm that ONAP CLI is very important for a 'carrier-grade' solution to help developers or operation people to use/test the various components. ONAP CLI passed M4 milestone and I believe that ONAP CLI should be part of R1. Best Regards Eric

[onap-tsc] [tsc]Vote: ONAP Deployment Proposal for Amsterdam Release

Hello We agree that Heat template for OpenEcomp was first designed to run on Rackspace environment. However, the Heat template evolved to remove the Rackspace dependencies and I believe that the various tests we can produce on various OpenStack solutions in the community should eliminate the

[onap-tsc] R2 use cases planning

I think we should capture the feedbacks from various collaborative projects using ONAP. As an illustration, MEF is working on a project involving ONAP https://mef.net/News/MEF-In-The-News MEF members currently are working on three 3 reference implementation projects on MEFnet: ... (2) an

[onap-tsc] [R2] Prioritization

Hello Following discussions in use-case & architecture subcommittees and the TSC, I think we should not only focus on use-case definition to drive the R2. The R1 release will not be perfect and there will be a lot of efforts to improve it. We should first prioritize the major topics not solved

[onap-tsc] [onap-discuss] [sdc] API documentation for on-boarding

Hello I can not find documentation to describe the "on-boarding" part for the SDC API (eg http://:8080/onboarding-api/v1.0/vendor-license-models) Regards Eric _ Ce message

[onap-tsc] Code Review: how to avoid long delay to review

Hello There was a code review pending since 5 days due to a lack of reviewers. I think we should adopt some best practices to avoid such delay. A committer should inform the PTL and a list of reviewers by mail (typically the project committers and other people involved in the project) OPNFV

[onap-tsc] Enforcing an "Upstream first" approach to ONAP

+1 for raising this topic We should avoid 10k LOC patches because it is very complex to review and is not aligned with an open source spirit. I do not believe that we should create another subcommitte to handle such issue. The integration project may be able to detect such behavior and alerts

[onap-tsc] Vote on Date & Location of Next ONAP Developer Face To Face

+1 Eric _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans

[onap-tsc] TR: TSC VOTE on Repos for AAI, AAF, Modeling & MSB

Hello +1 All I replace Jamil. Best Regards Eric De : CHAWKI Jamil IMT/OLN Envoyé : mercredi 2 août 2017 14:13 À : DEBEAU Eric IMT/OLN Objet : Fwd: [onap-tsc] TSC VOTE on Repos for AAI, AAF, Modeling & MSB Cordialement Jamil Début du message transféré : Expéditeur: Kenny Paul

Re: [onap-tsc] Seed code for Service Orchestrator

+1 De : Ed Warnicke [mailto:hagb...@gmail.com] Envoyé : jeudi 11 mai 2017 22:17 À : ROSE, DANIEL V Cc : SPATSCHECK, OLIVER; DEBEAU Eric IMT/OLN; dewa...@gigaspaces.com; onap-tsc@lists.onap.org Objet : Re: [onap-tsc] Seed code for Service Orchestrator In many other communities, as a matter of

[onap-tsc] Seed code for Service Orchestrator

Hello I am surprised to discover that open-o/gso is considered as the seed code for the Service Orchestrator. As far as I know, we never decided such choice during the discussions last week and it should be a TSC decision. Regards Eric