Hi we are trying to address these topics as part of the Orchestration
Scenarios Task Force (
https://wiki.onap.org/display/DW/Orchestration+Scenarios), ie the ETSI
Alignment Support (https://wiki.onap.org/display/DW/ETSI+Alignment+Support)
effort.   Some more comments below:

   1. The MANO architecture doesn't address most of the FCAPS functions,
   leaving it to the EM component.  However, as part of the SOL003 (
   https://wiki.onap.org/display/DW/SOL003+Adapter) & SOL002 (
   https://wiki.onap.org/display/DW/SOL002+Adapter) functionality we will
   be adding support for receiving Life Cycle Notifications from an external
   VNF Manager and translating them into DCAE events (part of F).  We are also
   planning to add support for ModifyVnfInfo to the SOL003 Adapter along with
   a SOL003 plugin for APP-C that would enable (C). We have not yet planned
   for addingSOL002/SOL003  indicator support which could be used for F&P
   support in the future.
   2. ETSI MANO is does not try to address this.
   3. The Frankfurt release will support onboarding, and deployment of ETSI
   NFV SOL004/SOL001 v2.5.1 compliant VNFs using and external VNFM or the
   embedded NFVO/VNFM in VF-C.
   4. Part of the SOL002 work is to leverage the EM capabilities of ONAP to
   support monitoring and configuration of VNFs
   5. SOL002 & SOL003 adapter interface along with the ONAP DCAE could
   support most of the orchestration and many of the OSS functions
   6. CNF (pre ETSI NFV standard) support is being proposed for the Guilin
   release.

BR,
Fred Oliveira

On Fri, Mar 6, 2020 at 6:04 PM <[email protected]> wrote:

> Dear Members,
> I would like to understand how ETSI MANO based Architecture of ONAP is
> being brought in use for 5G OSS & Orchestration in respect to:
>
>    1.  Fault, Configuration & Performance (*FC*A*P*S) & its imminent
>    relationship to 3GPP standards if any.
>    2. Interfaces for consistent data exchange to & fro between 5GS,
>    Transport, other conforming devices.
>    3. Feasible deployment of VMs & NFs & their management from ONAP
>    itself.
>    4. Mapping, if any between EM->VNF, VF Controllers ->VNFM, VIM, NFs.
>    5. Analytic Components with containment of AI, ML, DL & its presence
>    in complete OSS & Orchestrator architecture.
>    6. Already deployed NFs(P/N/C) integration & Service Discovery.
>
> Please do let me know of any advancements being considered & if possible
> do provide the links to their resource material.
> Thanks in Advance :)
> 
>
>

-- 
Fred Oliveira
Fellow - Technology
M:+1774-505-3703 O:+1781-663-3965

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

View/Reply Online (#20214): https://lists.onap.org/g/onap-discuss/message/20214
Mute This Topic: https://lists.onap.org/mt/71861291/21656
Mute #cds: https://lists.onap.org/mk?hashtag=cds&subid=2740164
Mute #changemgmt: https://lists.onap.org/mk?hashtag=changemgmt&subid=2740164
Mute #performance: https://lists.onap.org/mk?hashtag=performance&subid=2740164
Mute #sdc: https://lists.onap.org/mk?hashtag=sdc&subid=2740164
Mute #5g: https://lists.onap.org/mk?hashtag=5g&subid=2740164
Mute #aai: https://lists.onap.org/mk?hashtag=aai&subid=2740164
Mute #msb: https://lists.onap.org/mk?hashtag=msb&subid=2740164
Mute #vfc: https://lists.onap.org/mk?hashtag=vfc&subid=2740164
Mute #so: https://lists.onap.org/mk?hashtag=so&subid=2740164
Mute #docker: https://lists.onap.org/mk?hashtag=docker&subid=2740164
Mute #heat: https://lists.onap.org/mk?hashtag=heat&subid=2740164
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to