1. OpenSAF Wanted Architecture TLC view
Mario Angelic
Technical Co-Chair
OpenSAF Project
June 4th, 2009

2. OpenSAF TLC view on architectural evolution
Presentation Scope
OpenSAF TLC view on architectural evolution
Architectural aspects covered in this presentation
Modularity
Improving current support on modularity
Functional content
Addition of new functionality
Streamlining of functionality

3. Modularity What do we want to achieve? Why ? How ?
OpenSAF functionality delivered as number of functional modules
Why ?
Reducing entry-cost for Application
Reducing maintainance overhead for ”functionality” applications they do not need
Addressing wider range of applications
How ?
Analysing intrinsical service inter-dependency
Identifying ”modules” and it’s boundaries
Cleaning up ”module” dependencies

4. Analyzing service inter-dependency
Standardization View (SA Forum)
Describe dependency between services
Describe Possible Modularization alternatives allowed by standard
Implementation View (OpenSAF)
Describe actually implemented SAF services
Implementation dependencies
OpenSAF infrastructure services

5. Standardization view: Functional content
AIS Utility Services
AIS Management Services
Checkpoint (CKPT)
Information Model
Management (IMM)
AIS Frameworks
Event (EVT)
Notification (NTF)
Availability
Management
Framework (AMF)
Lock (LCK)
Logging (LOG)
Messaging (MSG)
Security (SEC)
Software
Management
Framework (SMF)
Naming (NAM
TImer (TMR)
Cluster Membership Service (CLM)
Legend
Platform Management Service (PLM)
AIS
Services and
Frameworks
AIS Platform Services
HPI
Services
Hardware Platform Interface (HPI)

6. Standardization view: Typical Service Dependencies
Optional
AIS
Management
Services
AIS Utility
Services
AIS
Frameworks
CKPT
SMF
IMM
EVT
LOG
LCK
AMF
NTF
MSG
NAM
SEC
CLM
TMR
PLM
HPI
Optional
AIS Platform
Services

7. Implementation view: SAF Services
AIS Utility Services
AIS Management Services
Checkpoint (CKPT)
Information Model
Management (IMM)
Event (EVT)
AIS Frameworks
Availability
Management
Framework (AMF)
Notification (NTF)
Lock (LCK)
Logging (LOG)
Messaging (MSG)
Software
Management
Framework (Rel 4)
Legend
Cluster Membership Service (CLM)
AIS
Services and
Frameworks
AIS Platform Services
HPI
Services
Hardware Platform Interface (HPI)

8. OpenSAF Service Dependencies (Release 3)
AIS
Frameworks
AIS
Management
Services
AIS Utility
Services
SMF
CKPT
IMM
EVT
AMF
LOG
LCK
CLM
NTF
MSG
OpenSAF Infrastructure Services
OpenSAF CLI
RDE
MDS
Logtrace
SRMSv
MASv
HPI
Optional
HISv
MBCSv
LEAP
DTS
IFSv
PSSv
Optional

9. OpenSAF Infrastructure Services
“OpenSAF Core”
AIS
Management
Services
Minimum set of inter-dependent services
Offers high-availability and managebility support usable to wide-range of applications
SA Forum Services:
AMF (Availability Management Framework)
CLM (Cluster Membership Service)
IMM (Information Model Management)
NTF (Notification Service)
LOG (Logging Servive)
PLM (Platform Management Service)
OpenSAF Infrastructure Services:
MDS (Message Distribution Service)
RDE (Role Determination Engine)
MBCSv (Message Based Checkpoint Service)
DTS (Distributed Trace Service)
Logtrace (Log&Trace foront-end)
AIS
Frameworks
SMF
IMM
AMF
LOG
CLM
NTF
AIS Platform
Services
(move CLM here)
PLM
OpenSAF Infrastructure Services
RDE
MDS
Logtrace
DTS
MBCSv
LEAP
Optional

10. OpenSAF Wanted Architecture
Management Clients
(3pp, etc.)
OpenSAFCLI
AIS Utility
Services
OpenSAF GUI
Possible finer-grained modularity
CKPT
EVT
After PLM introduced
AIS
Management
Services
AIS
Frameworks
LCK
HISv
SMF
PSSv
IMM
MSG
Deprecated
&
Removed
AMF
...
MASv
LOG
CLM
SRMSv
NTF
Same package
AIS Platform
Services
(move CLM here)
PLM
OpenSAF Infrastructure Services
MDS
MBCSv
LEAP
IFSv ??
Optional
DTS
RDE
Logtrace
Optional
HPI

11. Streamlined Architecture
Reuse internally
Ex. Consolidated Logging
Rely on standard interfaces
C standard library
POSIX interfaces
Reuse from external open-source projects
Using open-source trace backend
Focusing on key values/advantages

12. Consolidated logging
Today, OpenSAF have several means of logging information:
Stdout redirected to files
Per service log files
Using DTS service
Using syslog
Using LogTrace
(log levels to syslog, trace levels to file)
Using SA Forum Log service
Preferred method for logging is by using SAF Log service, but …. some services need to be started before SAF Log service (like IMM), so what should use IMM for logging?

13. Consolidated logging, cont.
Proposal is that:
All OpenSAF services use Logtrace API as Log and Trace interface (front-end)
Trace API would then use syslog as backend for logging until SAF Log is started. Once SAF Log starts Trace API will dynamically switch to use SAF Log service for logging.
Trace API will use DTS as trace backend, or some other available open-source tracing backend (like LTTng, for example)

14. Consolidated Logging in OpenSAF, proposal
LogTrace API
In future replaced with some open-source trace backend (for example, LTTng)
Trace levels
DTS
OpenSAF services
LogTrace
SAF Log available?
SAF Log
Log levels
Front End
Back-End
Part of Operating System layer
syslog

15. Consolidated logging, cont.
What about Applications ?
They should directly use SAF Log service
Application will not have any problem (compared to middleware services) since SAF Log services will always be available prior any application is started

16. Relay on standardized interfaces
Relying more on POSIX and C stdlib
LEAP becomes more as utility library then porting layer
Improves coding style/readability of OpenSAF services

17. Status for architecture related features
Addressed in Release 3
IMM, NTF part of OpenSAF
Addressed in Release 4
SMF part of OpenSAF
Configuration framework: MASv -> IMM
AMF using NTF for sending notifications

18. Questions ?

19. Thank You!
For more information: