VF Event Streaming (VES) YAML Artifact to Policy Creation PoC

Transcription

1 VF Event Streaming (VES) YAML Artifact to olicy Creation oc Sept 5 th, 2017 For Question lease Contact Alok Gupta +1 (732) ag1367@att.com AT&T Intellectual roperty. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual roperty.

2 oc Objective 2 hase 1: Enable Recommended olicies Creation from VES YAML on-boarding artifact. Converting Recommended olicies to Executable olicies by Technology/Operations using GUI hase 2: Current Different interfaces and formats reuiring customization (3 to 6 months development) Defined by vendors Varies by network functions and software releases Future Build/Test end-to-end CLAM Flows to demonstrate use of olicy with Microservices (misshb MS, TCA MS, Fault MS) and operation olicy. hase 3: Common predictable, flexible, reusable event format for all VFs => Closed Loop Automation Defined by AT&T based on conformance to standards Vendor agnostic and Configurable Repeat hase 1 and 2 for Infrastructure using collectd Yaml artifact

3 ONA Self-Serve Event rocessing olicy Generation OC Legend: C : configuration : policy VNF/Cloud Onboarding Reg YAML SDC catalog DCAE Design Studio 1) Select VNF 2) Query olicy for confirmation that Reg YAML has been processed and policies approved: provide status to user; direct them to olicy to complete these tasks. 6) Retrieve approved policies from olicy. 7) Add policies to VNF blueprint and distribute/activate them DCAE Service Chg Handler Blueprints DCAE Inv DCAE policies olicy Engine 3) Select VNF 4) ull Reg YAML from ASDC catalog and process Reg YAML into pending policies 5) Support policy approval GUIs/process Design Time Flow olicy Scope Includes: Threshold Crossing olicies Alarm generation policies Closed Loop olicies (Restart, Rebuild, Migrate, Scale In, Scale Out) Correlation policies Distribute olicies 3 VNF Guest OS Cloud Bare Metal DCAE Collector D M a a MissHB Micro Service Fault Micro Service TCA Micro Service olicy Driven Flow Operations in Control 2017 AT&T Intellectual roperty. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual roperty. AT&T roprietary (Secure Restricted) - Only for use by authorized individuals as approved by an Officer of the AT&T Companies D M a a olicy Engine for Closed Loop Ticketing Runtime Flow Defined by CLAM

4 roposed Heartbeat oc Flow VNF VES Coll DMaa misshb DMaa olicy Engine Create tickets for Closed Loop Ticketing Reuired olicy Fields HB Micro-service Event Name Source Name Heartbeat Interval/Duration Missing Heartbeat Count Operational olicy Closed Loop Name VES Collector receives heartbeat from a VNF. After verifying syntax and security credential, the heartbeat is place in DMaa using appropriate Topic Control. Highland ark receives Heartbeat olicy (H) and monitors for missing heartbeat events. Once a condition matching olicy is found, H will publish a synthetic alarm (fault event), with Recommended Action in internal header fields closedloopcontrolname and closedloopflag set. olicy Engine subscribes to the Synthetic alarms and executes operational policy specified in the controlloopname (restart vm, rebuild vnf, etc) AT&T Intellectual roperty. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual roperty.

5 roposed oc Flows for VES Fault Runtime VNF VES 5.3 Format VES Coll (Fault) DMaa A&AI Enricher MS DMaa CorrMS FaultMS DMaa olicy Engine Create tickets for Closed Loop Ticketing Reuired olicy Fields FM Micro-service Event Name Source Name Event Source type/interface Name Operational olicy Closed Loop Name + Onset or cleared VES Collector receives Fault from a VNF. After verifying syntax and security credential, the heartbeat is place in DMaa using appropriate Topic Control. Fault MS will receive Fault olicy, it will update VES Events internal header fields closedloopcontrolname and closedloopflag set with data from Fault olicy. If needed Fault MS will send event to Corr MS to identify root cause fault event and report Synthetic Fault. lease note the co-relation is done on events from H and each event must have closedloopcontrolname and closedloopflag already set. Corr MS will publish the root cause synthetic fault event, with internal header fields closedloopcontrolname and closedloopflag copied from original fault event. It will also populate correlation related data (correlationeventtype, correlationfirstepoch, correlationname, correlationrooteventid, correlationtype) in the internal header olicy Engine executes operational policy to take closed loop (restart vm, rebuild vnf, etc) Open Loop Action (create ticket) AT&T Intellectual roperty. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual roperty.

6 roposed oc Flows for VES M VNF C VES Coll DMaa VES 5.x Format TCA DMaa olicy Engine Create tickets for Closed Loop Ticketing Reuired olicy Fields TCA Micro-service Event Name Source Name Measurement Interval Metric Name KI Name Threshold/Critical Watermark Direction Suppression eriod Clear Suppression eriod Operational olicy Closed Loop Name + Onset or Abated VES Collector receives measurementforvfscaling events from a VNF. After verifying syntax and security credential, the events are placed in DMaa using appropriate Topic Control. TCA MS receives mfvs olicy and subscribes to DMaa for mfvs events. When threshold is reached based on the olicy, it publishes VES TCA event (eventname = tca_vmrf_ kpiname ) to DMaa. The data will also include kpiname, closedloopcontrolname and closedloopflag and will be populated in the Internal Header. olicy Engine to receive TCA event from DMaa, executes operational policy in the closed loop (scale out etc). Legend: C : configuration : policy AT&T Intellectual roperty. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual roperty. AT&T roprietary (Secure Restricted) - Only for use by authorized individuals as approved by an Officer of the AT&T Companies

7 olicy Update GUI GUI for Recommended olicy Review and Update => Enforcebale olicy event: {presence: reuired, action: [ any, any, alarm003, RECO-rebuildVnf ], structure: { commoneventheader: {presence: reuired, structure: { domain: {presence: reuired, value: fault}, eventname: {presence: reuired, value: Fault_vMrf_alarm003}, eventid: {presence: reuired}, priority: {presence: reuired, value: Medium}, reportingentityid: {presence: reuired}, reportingentityname: {presence: reuired}, seuence: {presence: reuired}, sourceid: {presence: reuired}, sourcename: {presence: reuired}, startepochmicrosec: {presence: reuired}, lastepochmicrosec: {presence: reuired}, version: {presence: reuired, value: 3.0} }}, faultfields: {presence: reuired, structure: { alarmcondition: {presence: reuired, value: alarm003}, eventseverity: {presence: reuired, value: MAJOR}, eventsourcetype: {presence: reuired, value: virtualnetworkfunction}, faultfieldsversion: {presence: reuired, value: 2.0}, specificroblem: {presence: reuired, value: "Configuration file was corrupt or not present"}, vfstatus: {presence: reuired, value: "Reuesting Termination"} }} }} AT&T Intellectual roperty. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual roperty.

8 oc Recommendations A dialogue with Vendors to provide more meaningful event definition that could be used to create olicy. A policy for every event received from VNF. Move control of event processing to Operations as they are able to fine tune the decision logic via olicies for closed/open loop processing. A need to add new closed loop actions (beyond current scale-out, scale-in, restart, rebuild, and migrate) such as notifications, logging, create ticket etc. to ensure we have a policy for each event A simplified architecture that merges Design Studio, olicy, CLAM GUIs to work with Vendor provided recommendations. As an extension of this work, the structured approach helps use of machine learning/ artificial intelligence to create new polices from the event repository AT&T Intellectual roperty. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual roperty.

9 Thank You AT&T Intellectual roperty. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual roperty.