Hi Alla, Do you have a feel for how much guidance is required for R1, I believe we said the call flows should be high level, though I can understand that there are questions from ptls that we need to answer.
BR, steve Sent from my Phone, please forgive typos > On 11 Jul 2017, at 09:03, Alla Goldner <[email protected]> wrote: > > Hi all, > > Thanks a lot to meeting’s attendants. > > Here is the meeting’s summary. As there are also action items to all PTLs, I > distribute it to the whole TSC list. I encourage PTLs and all potentially > involved people to register to dedicated usecasesub list. > > 1. Doodle poll is created (and email is sent by Kenny) to see > preference for Use case subcommittee meetings’ occurrence – weekly or > bi-weekly. All interested parties are encouraged to vote. > > 2. The highest priority now is to compete R1 use cases discussion. In > parallel we should start working on R2 use cases. Thus, please start > including your R2 use case description proposals under this created link: > https://wiki.onap.org/display/DW/Release+2+Use+Cases . We can then start > email discussions in parallel to our meetings. > > 3. vCPE and vVOLTE use cases leaders have meetings with a different > projects. The objective is to complete all use cases description with all > flows and involved modules functionality by next week. Use cases leaders are > requested to upload and distribute all meetings notes. The work is done and > organized in a very close cooperation with Integration project. In case of a > need, we may schedule dedicated meeting to review remaining points with > projects this week > a. vCPE: > i. Still > under discussion: > 1. DCAE/Intel discussion to close packets’ format (please involve Alok > Gupta per his request) > 2. Interactions with SDC will be further clarified > 3. SDN-C functional extension will be discussed with SDN-C team > 4. Onboarding of vCPE VNFs scenario - DCAE Telemetry issue will be > clarified > > b. vVoLTE > i. There > is need to check legal process of commercial VNFs approval. Perhaps this is > not needed as commitment is only for integration testing. In any case, we > will ask Phil to help validating this issue > ii. There > is need to involve VNF requirements project to double check whether > documentation of Open-O is merged with ecomp documentation to create a single > set of guidelines > iii. There > is request to include model which drives the use case in the vVolTE use case > description > iv. A > question on whether vIMS+vEPC is enforced as a single request coming from SO > (i.e. as a single network service or not). It was clarified that it is up to > implementation, as VF-C can support it both ways. The corresponding > clarification should be included in the use case description > v. Still > under discussion: > 1. SDC for design time functionality > 2. SDN-C interaction with 3rd party controller > 3. For overlay – whether Openstack or hardware will be used – > discussions with Brian Freeman are initiated > > 4. PTL of projects with specific issues related to use cases > implementation are requested to provide their questions in advance and also > to attend Use case subcommittee meetings in such a cases. PTLs who has no > clear information on what their project should implement per R1 use cases > (and those projects are not mentioned under point 3 above) are requested to > approach me ASAP. > > > Best regards, > > Alla Goldner > > Open Network Division > Amdocs Technology > > > <image001.png> > > 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 > [email protected] > https://lists.onap.org/mailman/listinfo/onap-discuss
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
