ELAlto DCAE Enhancements Frankfurt Planning Vijay Venkatesh Kumar

  • Slides: 5
Download presentation
EL-Alto DCAE Enhancements & Frankfurt Planning Vijay Venkatesh Kumar (AT&T)

EL-Alto DCAE Enhancements & Frankfurt Planning Vijay Venkatesh Kumar (AT&T)

EL-Alto DCAE Enhancements § DCAE Platform § Dashboard deployed via Helm. * All DCAE

EL-Alto DCAE Enhancements § DCAE Platform § Dashboard deployed via Helm. * All DCAE Platform components: Cloudify, Config. Binding. Service, Inventory. API, Service. Change. Handler, Policy. Handler, Healthcheck moved to Helm in Dublin § DCAE Cloudify deployed MS pods auto-cleanup (triggered via Helm) § DCAE MS § Static deployment § § Support integration usecases Dynamic deployment § cloudify cli or dashboard or CLAMP § Dmaap Plugin enablement § Bootstrap updates § § § Configmap, consul entry, Update k 8 s plugin key to include configmap, Dependency on k 8 s version ( MS for Frankurt will be required to switch to new version Tested both MR and DR dynamic topic/feed § DFC and Pm-Mapper were pilot MS Bp-gen tool enhanced to support dmaap plugin integration § TLS Enablement § Config. Binding. Service deployment modified to support 2 services § Deployment Handler and Inventory. API § Cloudify § Security updates § Image optimization (alpine) § § CBS, Inventory-API, Service. Change. Handler, HV-VES, PRH, Son-handler Non-root § SON-handler, PRH, VES*, Service. Change. Handler, CBS, Inventory-API, HV_VES

DCAE impacts for Frankfurt § Design change for onboarding § Blueprint can be created

DCAE impacts for Frankfurt § Design change for onboarding § Blueprint can be created via new DS flow (standalong Bp-gen tool also available) using component spec § Microservice Deployment § All MS deployment supported only via Cloudify blueprint § Minimize Bootstrap service (only VES and TCA) § All usecase specific MS to be installed on-demand § VESCollector default enabled for HTTPS § Multi-site deployment § Alignment with rest of ONAP for determining remote cluster § Policy Model updates flow § Policy Handler updates for recieving notification from Policy via DMaa. P § DCAE TLS init container § Dynamic cert generation through AAF § OTI Integration

Simplified Onboarding/Design with DCAE MOD VNF Onboarding & Design Service DCAE MOD Scope Acumos

Simplified Onboarding/Design with DCAE MOD VNF Onboarding & Design Service DCAE MOD Scope Acumos Marketplace Catalog Microservice Developer MS Package m. S Metadata (Spec. json & Data. Format. json) DCAE m. S Adaptor for Acumos-ONAP Integration Service Designer Standard VNF Package m. S Policy Model Developer onboards with CLI (today) or GUI (future) DCAE m. S Adaptor uses APIs Onboarding CLIs/GUIs/APIs MS Image (Docker or k 8) SE Service Designer Ops DCAE Design Catalog Distribution API To runtime env To be replaced by setting design time parameter values using DCAE MOD and setting runtime parameters values using DCAE Dashboard m. S Configuration Input File Generation inputs. json BP Generator DCAE m. S Runtime Deployment API Dockercentral (Nexus) Design Studio SDC Design Catalog DCAE Designer GUI DCAE Service Assurance Design Onboard to DCAE Design DB SDC GUI SDC DCAE Inventory m. S/DMaa. P Flow Design m. S Design Time Configurations m. S Runtime Configurations Distribute for Blueprint Generation Policy Model DCAE Flow m. S BP GUI DCAE Dashboard Ops m. S Deployment Runtime Environment AT&T Proprietary (Restricted) Policy CLAMP

Frankfurt – Self Serve Control Loops using DCAE MOD 1 2 SDC • Replace

Frankfurt – Self Serve Control Loops using DCAE MOD 1 2 SDC • Replace DCAE-DS with a new DCAE Designer • DCAE generates BP at the end of the design process • Simplify the process from design to runtime Design Catalog SDC/DCAE Catalog integration APIs as Post Frankfurt feature 3 • DCAE uses Policy API to send policy models • DCAE Designer sends flow artifact to CLAMP • CLAMP retrieves BP from DCAE 5 • Establish GUI and Catalog integration APIs between DCAE-MOD and SDC (future) Policy is onboarded with the associated m. S Acumos Marketplac e Catalog Acumos. ONAP DCAE Adaptor 1 m. S Onboarding CLI or API 5 4 m. S metadata m. S Policy Spec. json Dataformat. json Model Service Design CSAR DCAE Onboarding/Design DCAE Designer DCAE Design Catalog m. S Policy Model Flow Artifacts Distribution Non m. S related Policy Model • Change the m. S onboarding process with just the metadata (no BP) • Onboard m. S policy model the same way as m. S, via the new DCAE Onboarding process NF Service CSAR Only CSAR Policy Designer Policy Platform CSAR CL Designer CLAMP 3 A 4 A 4 B DCAE Dashboard 2 BPG BP BP DCAE Inventory 5