1. Integrating HA Legacy Products into OpenSAF based system
Mario Angelic
Ericsson
June 4th, 2009

2. Presentation Outline
AMF support for integrating of legacy products
Type of legacy products
Approaches for integrating HA legacy products

3. AMF Support AMF different concepts to support legacy application
From availability integration:
Concept of wrapper process The wrapper process typically consists of one processes that interacts with the AMF on the one hand and with the legacy software (hardware) on the other hand. The wrapper and the legacy software together constitute a single component.
Concept of non-SA-aware component Node code modification required. AMF just manages lifecycle. Still component can be monitored using concepts like External Active Monitor and Passive Monitoring
Concept of proxy-proxied component In this case legacy software can be considered to be a separate component managed by the proxy component. Appropriate in cases when either redundancy model of proxied component is different then redundancy model of proxy component or the failure zone of proxied components is different between proxy and proxied component.

4. Type of legacy products
“Simple” legacy products (daemons), not containing any HA functionality
Example: snmp daemon
Legacy products with own HA, controlling only own availability
Example: HA Database, HA SS7 stack
Legacy products with own HA, controlling lifecycle of whole execution environment
Example: Legacy middleware

5. “Simple” Legacy products (daemons)
Easy to make HA using these alternatives:
Wrapper Process
To AMF it will look as normal sa-aware component
Modeling as non-sa-aware component
No need for any code, just configuration
Use External Active Monitor for monitoring state of component

6. Legacy products with own HA
We take a DBMS as example of such product
Scope is integration of such product into OpenSAF/SAF based system
Integration can be divided in two areas:
High-Availability Integration (Integration with AMF)
Managebility integration (Integration with NTF, IMM, SMF, LOG)

7. High-Availability Integration
There are different ways to model availability and depending on existing DBMS architecture some are more appropriate then others
One of AMF integration examples:
Model DB functionality per node as sa-aware local component
Can be done by:
Adapting DB process to handle life cycle and workload management API
Adding wrapper process which toward SAF implements life cyle and workload management API and toward DBMS adapts to DBMS specific API (Note: Important to correlate life cycle of registered process and DB process/es on that node.)

8. High-Availability Integration, cont.
Component will be part of specific Service Unit containing just that component.
Service unit will be part of own Service Group that will use one of AMF specified redundancy models (corresponding to existing redundancy model (if existing) in DBMS solution). Common redundancy models are N-way active and 2N. For specific DBMS architectures other redundancy models could be more appropriate.
Shared library with DBMS API shall be provided (Connector)
Communication mechanism between Shared library and database component must be based on reliable protocol (For example SAF MSG service or another commonlly available protocol (for example TCP)). Failover&Swicover of DBMS nodes should be done as transparentlly as possible toward users (Application).

9. Example 1 DBMS using 2N redundancy model
Application using N-way active redundancy model
Node U
Node V
Node W
Node X
Service Group
Service Unit
Service Unit
Service Group
Component
Component
Service Unit
Service Unit
DBMS
DBMS
Component
Component
proprietary
App
App
RegP
RegP
DB API
DB API
AIS
AIS
AIS
AIS
SAF MW

10. Example 2 DBMS using N-way active redundancy model
Mgmt part using 2N redundancy model
Application using N-way active redundancy model
Modelling DBMS component as proxied (Mgmt component is proxy) or sa-aware.
Node 1
Node 2
Node 3
Node 4
Node 5
Node 6
Node 7 SG SG SU SU SU SU SU SG
Component
Component
Component
Component
Component SU SU
DBMS
DBMS
DBMS
Mgmt
Mgmt
Component
Component
proprietary
App
App
RegP
RegP
DBMS specific HA
DB API
DB API
AIS
AIS
AIS
AIS
AIS
AIS
AIS
SAF MW

11. Management Integration
Fault Management integration
Alarms & Alerts are sent/received using Notification service
Configuration Management integration
Configuration done by Information Management Model service
Provide Information Model describing configuration and runtime objects and attributes of a DB (model whole/most_commonlly_used configuration capabilities of a specific DB solution)
Adapt DB solution to use IMM OI API, eiher nativelly integrating or adapting proprietary configuration API to IMM API.

12. Management Integration, cont.
SMF
Packaged as SW Bundle
Log integration
DBMS should use SAF Log for logging

13. Shared-disk databases
DBMS architectures
Shared-disk databases
Using shared storage for storing state
Shared-nothing databases
Data stored in memory, typically partitioned and replicated for availability reasons

14. Shared-disk DBMS Wrapper method used
Node W
Node X
Node 1
Node 2
DBMS
SAF MW
Component
proprietary SU SG
AIS
Node 3
RegP
Apps
DB API (Connector)
DBMS Load Balancing
Shared Storage
Wrapper method used
Each DBMS component is sharing workload
N-way active could be appropriate redundancy model to use for modeling DBMS in this case

15. Shared-nothing DBMS architecture
In a shared-nothing cluster database all nodes are independent, and neither disk nor memory is shared between them.
Each server in the cluster has its own independent subset of the data which it can work on without risk for contention (i.e. data is partitioned) and one or more replica of partitioned data is created for high-availability purposes.
The clustered processors communicate by passing messages through a network. Database access from clients is automatically routed to the correct server.

16. Shared-nothing DBMS, total replication use-case
Number of replicas are same as number of Database Servers (total replication of all data). This use case could be attractive for smaller amount of data that are seldom written but often read; for example configuration data.
In this use case each Database server has full copy of database and that means that availability characteristics are same as for Shared-Disk solution. After failure of some Database Servers remaining once will be able to serve the traffic since they have full copy of database. So this case can be modeled with N-way active redundancy model.

17. Shared-nothing DBMS, data segmentation use-case
Number of replica is larger then one, and smaller then number of nodes. Specifically we will discuss case when there exists two replicas of each data partition. Following figure illustrates such case. P1 P2 P3 P4
Database X
DB Server 1
P2’
DB Server 2
P1’
P4’
P3’
DBMS
Partition Group

18. “Black-box” approach Using N-way active
Node W
Node X
“Black-box” approach
Apps
Apps
DB API (Connector)
DB API (Connector)
Using N-way active
Database connector sharing workload and routing database requests to DBMS instance holding requested data
DBMS Load Balancing
Node 1
Node 2
Node 3
Node 4 SG
SU 1
SU 2
SU 3
SU 4
Component
Component
Component
Component
Component
DBMS
DBMS
DBMS
DBMS
proprietary
proprietary
proprietary
RegP
RegP
RegP
RegP
AIS
AIS
AIS
AIS
SAF MW
active
active
active
active SI
CSI

19. “Black-box” approach Failure of Node 4 SI is still assigned Apps Apps
Node W
Node X
“Black-box” approach
Apps
Apps
DB API (Connector)
DB API (Connector)
Failure of Node 4
SI is still assigned
DBMS Load Balancing
Node 1
Node 2
Node 3
Node 4 SG
SU 1
SU 2
SU 3
SU 4
Component
Component
Component
Component
Component
DBMS
DBMS
DBMS
DBMS
proprietary
proprietary
proprietary
RegP
RegP
RegP
RegP
AIS
AIS
AIS
AIS
SAF MW
active
active
active
active SI
CSI

20. “Black-box” approach Failure of Node 4 Failure of Node 3
Node W
Node X
“Black-box” approach
Apps
Apps
DB API (Connector)
DB API (Connector)
Failure of Node 4
Failure of Node 3
SI is still assigned
But data partition located n Node 3 and Node 4 is lost
N-way active is not appropriate for this DBMS solution
“Improvement” to N-way active by specifying minimum number of assigned SI could solve this problem
DBMS Load Balancing
Node 1
Node 2
Node 3
Node 4 SG
SU 1
SU 2
SU 3
SU 4
Component
Component
Component
Component
Component
DBMS
DBMS
DBMS
DBMS
proprietary
proprietary
proprietary
RegP
RegP
RegP
RegP
AIS
AIS
AIS
AIS
SAF MW
active
active
active
active SI
CSI

21. Using SI –SI dependency feature
Node W
Node X
Node 1
Node 2
DBMS
SAF MW
Component
proprietary
SU 1
SU 2
SG 1
AIS
Node 3
SU 4
RegP
Apps
DB API (Connector)
DBMS Load Balancing
Node 4
SU 3
SG 2
SIPG1
CSI
SIPG2
SIPG1’
SIPG2’
depends
active
Using SI –SI dependency feature
Exploring SI dependency approach to try to model exact data partitioning
Note: This is just suggestion (do not try it at home ;-))
Component providing service when both CSIs are assigned

22. Using SI –SI dependency feature
Node W
Node X
Node 1
Node 2
DBMS
SAF MW
Component
proprietary
SU 1
SU 2
SG 1
AIS
Node 3
SU 4
RegP
Apps
DB API (Connector)
DBMS Load Balancing
Node 4
SU 3
SG 2
SIPG1
CSI
SIPG2
SIPG1’
SIPG2’
depends
active
Using SI –SI dependency feature
Failure of Node 4

23. Using SI –SI dependency feature
Node W
Node X
Node 1
Node 2
DBMS
SAF MW
Component
proprietary
SU 1
SU 2
SG 1
AIS
Node 3
SU 4
RegP
Apps
DB API (Connector)
DBMS Load Balancing
Node 4
SU 3
SG 2
SIPG1
CSI
SIPG2
SIPG1’
SIPG2’
depends
active
Using SI –SI dependency feature
Failure of Node 4 & Node 3
DBMS does not provide

24. Using SI –SI dependency feature
Node W
Node X
Using SI –SI dependency feature
Apps
Apps
DB API (Connector)
DB API (Connector)
DBMS Load Balancing
Failure of Node 4 & Node 1
DBMS still provides service
Node 1
Node 2
Node 3
Node 4
SG 1
SG 2
SU 4
SU 1
SU 2
SU 3
Component
Component
Component
Component
Component
DBMS
DBMS
DBMS
DBMS
proprietary
proprietary
proprietary
RegP
RegP
RegP
RegP
AIS
AIS
AIS
AIS
SAF MW
active
active
SIPG1
SIPG2
CSI
CSI
depends
depends
SIPG1’
SIPG2’
CSI
CSI

25. Summary “Integrating” Legacy products Integration approach:
Availability integration
Manageability integration
Integration approach:
“Hook up” to SAF/OpenSAF environment; not requiring rewrite and you still get SAF look and feel
There is no One approach how to model solution in AMF; will depend on DBMS architecture and requirements put on DBMS integration

26. Questions ?

27. Thank You!
For more information: