Autonomics - TM Forum Live

Autonomics Standardization
Summary: TMF, IETF, ONF
Dr. John Strassner
TMF ZOOM Zo-Chair
Agenda
Overview of SDO Activities
 ZOOM Roadmap
 IETF SUPA Roadmap
 Autonomics
Autonomics - Strassner
Page 2
SDO Activity Overview
 TM Forum ZOOM
− Defined specification for policy management architecture
− Redoing policy information model
 IETF SUPA
− Adding detail to basic ZOOM model, but only for ECA and
declarative (i.e., “intent”) policies
− Really focused on building generic YANG data models
 ODL NIC, ONF Intent-based work
− NIC has stalled
− Co-author of emerging draft from ONF NBI WG
 Others
− Mention policy, but lack detail
Autonomics - Strassner
Page 3
Agenda
 Overview of SDO Activities
ZOOM Roadmap
 IETF SUPA Roadmap
 Autonomics
Autonomics - Strassner
Page 4
Current ZOOM Policy Info Model
Autonomics - Strassner
Page 5
Current ZOOM Policy Architecture
Protocol and Information
Exchange Requirements
Policy Domain
Policy
Repository
Policy Creation
and Editing


Policy Validation
(Local Conflict
Resolution)
Policy

Verification
Event Bus

Policy Language
Translation

Policy
Execution

Policy
Decisions


 A protocol for encoding
logic definitions is needed
 Policy editing should use
simple text or XML
 So should policy translation
 Policy apps and brokers,
along with policy decision,
execution, and verification,
may need richer forms of
information transfer
Other Policy
Domains
Policy
 Applications
Policy Broker
Extracted from TM Forum TR234 Information Model Snapshot R14.5.0
Autonomics - Strassner
Page 6
ZOOM Policy Roadmap Thoughts
 Unified Architecture for SDN, NFV, and Legacy
− Dedicated WG in Theme 4 for working on Policy
− Theme 4 also working on a wider information model, metadata, …
 Preparing for Autonomics
− Integrating other ZOOM work, particularly on closed control loops
and E2E architecture
− Revisiting two key building blocks: policy continuum and
software contracts
− Probably need dedicated metamodel concepts
 Closely tied with IETF SUPA
− ZOOM is focused on overall architecture
− SUPA is focused on implementation
 Possibly tied to Other SDOs
Autonomics - Strassner
Page 7
Agenda
 Overview of SDO Activities
 ZOOM Roadmap
IETF SUPA Activities
 Autonomics
Autonomics - Strassner
Page 8
IETF SUPA Roadmap Thoughts
 Focus is above Device, but below Orchestrator
− However, nothing prevents SUPA from being used anywhere…
 IETF93 MAY determine the fate of SUPA
 If WG is formed:
− Continue work as outlined, continue relationship with ZOOM
(and possibly other SDOs)
− Define policy information model fragments for generic policy
concepts, ECA policy rules, and Declarative Policy Statements
− Focus on implementing YANG models
− Stretch goal: define formal model transformations
 IF WG is NOT formed:
− Good question!
− Need a home for the work
Autonomics - Strassner
Page 9
Current IETF SUPA Model
Autonomics - Strassner
Page 10
Agenda
 Overview of SDO Activities
 ZOOM Roadmap
 IETF SUPA Roadmap
Autonomics
Autonomics - Strassner
Page 12
Autonomics
 Starting to “Revive” FOCALE Architecture
 One Focus is Metadata
− Developing model-driven patterns and architecture for
dynamically defining and orchestrating services and resources
− NO recompilation, redeployment is required
− Done many places, but not really in networking
 Another Focus is Adaptive Control Loops
− Analytics as an integral part of the Control Loop (similar to the
Big Data OSS Catalyst that I helped mentor here in Nice)
− Extension of machine reasoning (in original FOCALE) to better
model cognition
 Needs an SDO Home – AFI/NTECH?
Autonomics - Strassner
Page 13
FOCALE Autonomic Architecture
Context Manager
Policy Manager
Policies control application of intelligence
Autonomic Manager
Control
Control
Control
YES
Managed
Managed
Resource
Resource
Model
-Based
Model-Based
Translation
Translation
Analyze
AnalyseData
Data
andEvents
Events
and
Determine
Actual State
Control
Current State =
Desired State?
NO
Ontological
Comparison
Reasoning and
Learning
Define New Device
Configuration(s))
Control
Autonomics - Strassner
Page 14
Questions?
Questions?
“Create like a god. Command like a king. Work like a slave”
- Constantin Brancusi
Autonomics - Strassner
Page 15
Modeling Concepts
Independent of
Vendor-, Platform,vendor,
language,
Language-,
and
protocol,
Protocol-Neutraland
Information
Model
repository
Data Model
(RDBMS)
Data Model
(NoSQL)
Data Model
(Directory)
Independent of
vendor; dependent
Vendor-Independent;
Platform-,
Language-,
on language,
and Protocol-Specific
protocol, and
repository
Dependent on
Data Model
(Oracle PL/SQL)
Autonomics - Strassner
Data Model
(Microsoft T-SQL)
Data Model
(PostgreSQL
PL/pgSQL)
Vendor-, Platform,vendor,
language,
Language-, and
protocol, and
Protocol-Specific
repository
Page 16
Policy Continuum
SUPA
I2RS, others
interface loopback 0
ip address 130.93.2.1 255.255.255.255
interface POS 3/0
ip address 130.93.1.1 255.255.255.0
ip ospf cost 1
ip ospf hello-interval 5
router bgp 100
network 130.93.0.0
neighbor internal peer-group
neighbor internal remote-as 100
neighbor internal update-source loopback 0
neighbor internal route-map set-med out
neighbor internal filter-list 1 out
neighbor internal filter-list 2 in
neighbor 171.69.232.53 peer-group internal
neighbor 171.69.232.54 peer-group internal
neighbor 171.69.232.55 peer-group internal
router ospf 100
network 130.93.0.0 0.0.255.255 area 0.0.0.0
route-map set-med 10 permit
match as-path 1
Bus: Give Customer Gold Service
Sys: Define Bus Concepts in
technology terms
- map customer to addr range
- map Gold to types of apps
…
Net: For Services1-j
- create L3VPN
- define port
- define routing protocol
…
Dev: account for device-specific
naming, restrictions, etc.
Business View: SLAs, Processes, Guidelines, and Goals
Policy
Continuum,
Applicable
to both Goal
and ECA
Policy Rules
System View: Device- and Technology-Independent Operation
Network View: Device- Independent, Technology -Specific Operation
Device View: Device- and Technology-Specific Operation
Instance View: Device-Specific MIBs, PIBs, CLI, etc. Implementation
Autonomics - Strassner
Page 17
Why Multiple Types of Policy Rules?
It’s all bad!
What to do?
Gold-Silver Tradeoff
Gold: IF (RTG > 100 msec)
THEN (Increase CPUG by 5%)
Silver: IF (RTS > 200 msec)
THEN (Increase CPUS by 5%)
1
There are different types of policy rules;
SUPA will initially consider two
It’s all good!
What is best?
Autonomics - Strassner
Conflict:
Gold/Silver Tradeoff
What to do?
Page 18
Types of Policy Rules (1)
 Event-Condition-Action (ECA)
− IF the clause of Events evaluates to TRUE
» IF the clause of Conditions evaluates to TRUE
o THEN execute the clause of Actions
− Explicit programming of state (rationality is compiled
into the policy!)
Autonomics - Strassner
Page 19
Types of Policy Rules (2)
 Goal (Intent)
− Express what should be done, not how to do it
− Specifies criteria for choosing a set of states, any of
which is acceptable
− Rationality is generated by optimizer/planner
Autonomics - Strassner
Page 20