1. SAF Specifications and Architecture U.Kleber October 15, 2008

2. General Remarks  Presentation shows SAF Release 6  Release 6 will be published on October 21  TWG and BoD already voted (Oct 13)  SAF Leadership agreed to disclose  Mostly material of Educational Sessions (held during SAF F2F meetings) is used  Overview on Release 6 changes is added  Outlook on future Releases is added  Some Backup Material can be used if necessary

3. Architecture (Dave Penkler, AWG Chair)

4. Presentation Outline  Introduction to architecture  Services architecture  Basic concepts  Relationships between basic concepts  The bigger picture  SA Forum building blocks  Building blocks in a carrier-grade operating environment

5. Basic Architecture View Board 1 Board N Application and Control Plane Interconnect Transport Plane Interconnect Storage Plane Interconnect Out of Band Management Plane Interconnect Board 2 Hardware Platform General Purpose/RTOS Applications Other Middleware SA Forum Hardware Platform Interface (HPI) SA Forum Application Interface Spec (AIS) Frameworks, Utility and Platform Services SA Forum AIS Management Services: Configuration, Monitoring, Administration, Notifications, etc Other Middleware

6. Vertically Integrated Solution Layered Solution B Layered Solution A HW Platform Board 1 RTOS / Carrier Grade OS Proprietary HW Management Proprietary HA Middleware Management Svcs Applications & Application Services Board 2 Board 3 Board N... HW Platform Board 1 RTOS / Carrier Grade OS SA Forum HPI SA Forum AIS SA Forum AIS Mgmt Applications Board 2 Board 3 Board N... ISV App Svc HW Platform Board 1 Board 2 Board 3 Board N... RTOS / Carrier Grade OS SA Forum HPI SA Forum AIS SA Forum AIS Mgmt Applications ISV App Svc Independently Interchangeable HA Middleware HW Management HW supporting SAF HPI Implementation ISV App Svcs Management MW Standardised Interfaces Standardised Interfaces SA Forum Specifications for Portability

7. Hardware Platform Interface (HPI)  APIs for fine grained low level access to hardware:  Inventory  HPI accessible hardware managed by domains found in –HPI Domain presence table  Within each domain is a Resource Presence Table describing discovered management resources  HPI resource functions  Each resource has a Resource Data Record Repository for each of its managed entities. This RDR contains –Instrument capabilities, inventory data (e.g. manufacturer, serial no, version, asset tag etc)  Instrumentation: – Sensor, Control, Inventory Data Repository, Watchdog Timer, Annunciator (LEDs)  Management Capabilities : –Hot-swap, configuration, load, reset, and power management –Diagnostics and Firmware Upgrade  HPI per domain: events, event logs and alarm table

8. Application Interface Specification (AIS)  Platform Services  Platform Management service provides a convenient abstraction to monitor state changes in groups of entities comprising hardware, hypervisors and operating systems  A cluster management service that provides a consistent view of the healthy configured nodes in a cluster  Basic management services: Standard interfaces for applications and middleware:  Configuration & runtime management information  Administrative commands  Notification for alarms, state changes, object lifecycle changes, attribute changes and security alarms  Logging of alarms, notifications, system messages and application specific streams  Access security functions for the AIS and HPI services  Frameworks  Availability management of applications and middleware  Software management for managing HW, OS, middleware and application upgrades taking service availability into account  Utility Services provide common services required in distributed HA systems including  Checkpointing, Event distribution, distributed locks, message passing, name lookup and timer services

9. SA Forum Architecture Box diagram AIS Utility Services Checkpoint (CKPT) Event (EVT) Messaging (MSG) Naming (NAM TImer (TMR) Lock (LCK) Cluster Membership Service (CLM) AIS Frameworks Availability Management Framework (AMF) Software Management Framework (SMF) Platform Management Service (PLM) Hardware Platform Interface (HPI) AIS Management Services Information Model Management (IMM) Notification (NTF) Logging (LOG) Security (SEC) AIS Platform Services Legend AIS Management Services AIS Services and Frameworks HPI Services AIS

10. PLM CLM AIS Platform Services Typical SA Forum Service Dependencies HPI Optional ADMIN API for all services through IMM TMR LCK CKPT EVT MSG NAM AIS Utility Services AMF SMF AIS Frameworks IMM LOG NTF AIS Management Services SEC Optional

11. Basic Concepts SA Managed Objects Resources SA Logical Entities Physical Entities: CPU,Board,NIC,HBA,Switch,Disk Software: File systems, Files, OSs, Executables, etc Services: DCHP,FTP,DNS,MPEG transcoder, SIP Proxy Defined by SA Forum services e.g.: AMF: Application, Service Unit, Component, Service Instance SMF: Campaigns, Software Bundle CLM: Cluster, Cluster Node PLM: Hardware Element, Execution Environment HPI: HPI Resources, Management Instruments Represents Configuration, runtime and administrative aspects of the represented logical entities stored in IMM Represents Concepts defined by SA Forum Specs SA Forum defined information model

12. Basic Concepts in the Bigger Picture SA Managed Objects SA Managed Resources SA Logical Entities Represents Concepts defined by SA Forum Specs Application Managed Resources Other Resources Information Model Application Managed Objects Represents Actual System

13. Information Model Managed Object Relationships Execution Environment (EE) Cluster Node Cluster AMF Node AMF Cluster AMF Application Legend: Aggregation Association Maps On Hardware Element (HE) Hosted On Platform Management Scope (PLM) Cluster Management Scope (CLM) Availability Management Framework (AMF) Scope HPI Entity

14. SA Forum Information Model – AMF View (simplified) AMF Node Component Service Instance (CSI) Service Instance Service Unit Service Group AMF Application Component Hosted On Protects Assigned to AMF Cluster

15. SA Logical Entities Dependency Relationships EE AMF Node Service Unit HE CLM Cluster Application Service Instance Defined by A pplication M anagement F ramework Defined by Cl uster M embership Service Defined by Pl atform M anagement Service Component CSI Service Group PLM Entity Defined by H ardware P latform I nterface AMF Cluster HPI Entity PLM EntityGroup Protection Group CLM Node Logical Entity used in API’s

16. Resource Dependency Graph Application Operating System StorageCPU(s) Network & I/O PSUsFans OS SW Load Executable Diagnostics SW Application/ MW Process

17. Logical Entity to Resource Mapping SA Logical entities Component Application EE HE System Resources Application Operating System StorageCPU(s) Network & I/O PSUsFans OS SW Load Executable Diagnostics SW Application/ MW Process

18. CKPT SA Forum Specification Scope SNMP Management Agent AMF HPI CKPT Element Manager * Object Management API Object Implementer API Applications & Platform Extenstions Information Model Management Service SNMP CIM Agent CIM XML CORBA Agent IIOP CMIS Agent *Element Manager and agents can be implemented as AMF components SA Forum Management Environment CMIP PLM NTF Netconf Agent Netconf WS-M Agent WS HPI MIBS AIS MIBS SAF XMI Model SAF XSD Config Schema XML Config File proposed

19. HE IMM HPI E M AMF App PLM OS HE IMM HPI E M AMF App PLM OS Service Availability: Part of a Bigger Picture* HPI Entity IMM/ NTF/ LOG HPI Element Manager Statistics Usage Data Reconfig Test Alarms Events Provision Configure AMF Application Network Element Network Management Service Management Network Status Problem/repair notifications QoS Levels SLA impact Provisioning Activation Trouble report Work Order * Loosely based on TMF Telecom Operations Map # Optionally a SA Forum application or part of NE Management Information Flows # PLM Operating System HE IMM HPI E M AMF App PLM OS

20. Service Group Service Unit Component Service Unit Component Service Unit Component... Service Group Service Unit Component Service Unit Component Service Unit Component... SA Forum Building Blocks SA Forum Application Service Group Service Unit Component Service Unit Component Service Unit Component... AMF Config Application Configuration Carrier Grade Base Platform SA Forum Cluster Node 1 Node 2 Node 3 Node N mapping NIO Switch Storage NPU DSP NIO Switch Storage NPU DSP NIO Switch Storage NPU DSP External Resources SA Forum MW IMM AMF/SMF Cluster Services HPI/PLM Component Based Middleware Other CGMw TIPC SCTP CFS Platform Configuration Cluster Config defines Information Model Management defines

21. SA Forum in a Carrier-Grade Base Platform Blade Box GPU NIO Switch Storage Special ATCA Server GPU NIO Switch Storage NPU DSP Rack Server GPU NIO Storage Switch NIO Switch NAS NIC Storage SAN Switch IO Storage Hardware Various Internal & External Interconnects: GE,FC,Fabrics etc Standard and Embedded Operating Systems Drivers, Networking Stacks, Basic File systems HPI Provider Remote APIs RPC,CORBA,RMI/IIOP,SOAP CGTSvcs PLM Checkpoint Lock MessagingEvent Information Model Mgt NTF Naming SMF JVM Base Platform Management Svcs eg CIMOM, SNMP agent, Config.. Carrier Grade Base Platform Middleware Protocol Stacks Protocol Subsystems Database Subsystems Application Servers OAM&P Services Application Services / Enablers Application Specific Platform Extensions Network Applications Signaling Gateway CSCFHSS Media Gateway Media Gateway Controller GGSN / PDN GW Element Manager SA Forum Middleware AMF Component SA Forum Application CFS SA Forum Building Blocks IMS App Enablers AMF CLM LOG

22. Release 6 Changes

23. New / Changed Specifications  Split Overview Document:  SAI-Overview-B.05.01 (2MB)SAI-Overview-B.05.01  SAI-AIS-CPROG-B.05.01 (571K)SAI-AIS-CPROG-B.05.01  HPI  SAI-HPI-B.03.01 (2MB)SAI-HPI-B.03.01  AIS  SAI-AIS-PLM-A.01.01 (1MB)SAI-AIS-PLM-A.01.01  SAI-AIS-CLM-B.04.01 (837K)SAI-AIS-CLM-B.04.01  SAI-AIS-AMF-B.04.01 (5MB)SAI-AIS-AMF-B.04.01  SAI-AIS-IMM-A.03.01 (1MB)SAI-AIS-IMM-A.03.01  SAI-AIS-NTF-A.03.01 (2MB)SAI-AIS-NTF-A.03.01

24. Overview Documents  Overview Document  Architectural Description added  Glossary added  Programming Guide  Enhanced Track API

25. HPI Enhancements  The Firmware Upgrade Management Instruments (FUMI) API refined and extended  Hot Swap clarifications  Redefinition from simplified hot swap to unmanaged hot swap  Text string representation of entity paths  New resource events that allow dynamic updating of resources  Introduce functions to initialize and finalize  Usage of Threads in the HPI-Library  Introduce new function to determine own entity path

26. New PLM Service  Management of HW, Virtualization and OS Layer  Information Model, Tracking, Administrative Operations for Hardware Entities and Execution Environments

27. CLM Enhancements  Clarifications about unconfigured nodes and the behavior on non-member nodes  Interaction with PLM  A node now is mapped on an Execution Environment  Enhanced Track API  Validation, Start and Completed Steps  Correlation  Additional causes  Allow administrative unlock while a node is in state shutting-down  Deprecate SaClmClusterNodeEvictionCallbackT (covered by enhanced track API)

28. AMF Enhancements  HA Readiness State of a SU for an SI (&Component for CSI)  Allows an in-service component to reject a CSI assignment  Configure a capacity for a node and weights for SIs  Avoid overload (only static at configuration time)  Support correlation of notifications  Interactions with CLM and new PLM clarified  E.g. node failfast now can restart an execution environment  saAmfComponentUnregister() removed because AMF automatically unregisters components  Other clarifications  (good to read even when implementing earlier versions) SU = Service Unit SI = Service Instance CSI = Component Service Instance

29. IMM Enhancements  Enhanced definition of roles for the object implementer  CCB Validator  CCB Applier  Runtime owner  There may be multiple validators and appliers for an object  Allow global validation – independent of the order in the CCB  Allow multiple components validate a change  Allow mulitple components react on a change  Support correlating notifications to admin operations CCB = Configuration Change Bundle

30. NTF Enhancements  Changes on notification suppression (in producer interface)  New notification type “miscellaneous”  Used for HPI event notifications and to notify administrative operations  Handling of correlation identifiers  Preallocation of notification id to support correlation

31. Outlook on Future SAF Releases

32. Copyright© 2008 Service Availability™ Forum, Inc. - Other names and brands are properties of their respective owners. 32 SA Forum Roadmap MIBs defined within HPI & AIS Released Jan 2006 SysMan I HPI B.01.01 Released Nov 2004 HPI - B Naming Service Timer Service Svcs Updates HPI Updates Released Feb 2007 Release 4 AIS B.02.01 Released Jan 2006 AIS - B SMF AMF Java-Support Security Svcs Updates Released Oct 2007 Release 5 IMM Enhancements PLM Svcs Updates HPI Upates Release 6 CLM NTF AMF Java Release 5 CLM NTF AMF IMM Java Release 6 20082007 2009 200620052004200320022001 36 Global Members Quarterly meetings 9 work/subgroups 140+ active contributors Founded April 2001 SA Forum Founded AIS A.01.01 Released Apr 2003 AIS - A HPI A.01.01 Released Oct 2002 HPI - A HPI B.01.01 Compliance Suite Released Aug 2007 HPI-B Compliance

33. Mapping Specifications  Release 6 planned mappings  Java Mapping  Update of AMF, CLM, NTF to Release 6  Add IMM  MIBs for Release 6  HPI to ATCA Mapping  Java Mapping Release 2  Mappings for AMF.B.01 and CLM.B.01  Allows for OpenSAF Java integration  HPI B.02/B.03 Compliance Suite

34. Release 7  Content currently in discussion  Main Focus:  Complete SMF  All services need to support upgrade  E.g. AMF dynamic config changes  E.g. PLM support fallback  Modular HPI

35. Future Enhancements with Relevance for Implementers  Ongoing SEC work  Will affect all services  Service Degradation  Multi-Cluster Configurations  Different approaches:  Can one IMM host multiple AMF clusters?  Can one PLM “domain” host multiple IMM instances?  Can one HW entity host multiple PLM instances?  New Services/Frameworks like Trace, Overload, Diagnostics

36. Questions?

37. Open Specifications for Service Availability™