1. OpenSAF Roadmap
Murthy Esakonu
GoAhead Software Inc
OpenSAF TLC

2. Presentation Outline OpenSAF Roadmap Process
OpenSAF 4.2 Feature Highlights
Beyond 4.2

3. Basic Feature Lifecycle
I need Feat. A
I’ll implement Feat. A
Feat. A
Feat. A
”Wish-list”
User
Developer
Feat. A + Time Estimate
Major Feature
Feat A Feat B Feat C
OpenSAF Roadmap
Minor Feature
TLC
Release Manager
Betas
I have Feat. A !
Feat. B
Milestones
Feat. A
Feat. C FC FC
Detailed Plan for Release N RC M
General Availability M
User
Dev Trunk
Release N Stable Trunk
OpenSAF Release N

4. OpenSAF4.2 Architecture Features
IMM Multiple appliers
Enabler for “hot standby” object implementers such as AMF and applications
Distribution of configuration in cluster.
Simpler object implementer logic (less need for internal check pointing)
IMM further Characteristics improvements
All object implementers will benefit, less blocking calls
Improved fail/switch-over time
Reduced CPU load and responsiveness
AMF Hot Standby Support
Decreased controller switchover & failover times.

5. OpenSAF4.2 Usability Features
AMF B API
Improved IMM OI error handling capabilities
Sample SMF integration with Linux Package Management
Application Dependency Modeling Improvements

6. Beyond 4.2 Aligning to Latest SAF specs
Python Bindings for SAF services
Performance characterization & Improvements
IMM Replication domain
CKPT & MSG
Remove need for shared file system
Eco System
Included in Linux distribution(s)
Integrate OpenSAF with Sailfin to test the whole JSR 319 feature
Language Bindings
Java bindings for OpenSAF services
EVT, IMM, NTF
AMF & CLM already exist.
Aligning to Latest SAF specs
AMF B (missing Features)
NTF A.03.01
PLM A implementation Gaps (Virtualization, multiple domain support)

7. Beyond 4.2 Tools New Services Implementation Security improvements
- generating SMF campaigns and AMF model
- generating IMM OI skeletons based on class definitions
New Services Implementation
Security (SAI-AIS-SEC-A.01.01)
Naming (SAI-AIS-NAM-A.01.01)
Security improvements
Start AMF applications as non root
Restrict/control changes of Information Model

8. Questions