Service Availability: Principles and Practice

Chapter 14

Integration of the VideoLAN Client with OpenSAF: An Example

Anik Mishra1 and Ali Kanso2

1Ericsson, Town of Mount Royal, Quebec, Canada

2Concordia University, Montreal, Quebec, Canada

14.1 Introduction

The Availability Management Framework (AMF) manages the high availability (HA) of the services provided by an application through dynamically assigning the workload to the application's components and controlling their life-cycle. To achieve the highest level of availability, the application's components typically need to interface with the AMF [48] and possibly with other services. This design decision is usually made in the development process of the application's components. However legacy applications do not implement this interface that would allow them to interact with AMF. In order to improve the availability of such applications, different levels of integration are possible: They range from the nonproxied-non-SA-aware integration that leaves the application's code intact, through SA-aware integration in which the application is modified allowing more interaction with AMF, to the integrations with additional services of the Service Availability (SA) Forum middleware (e.g., Checkpoint).

In any case, for AMF to manage the availability of an application, it requires a configuration describing the application.

In this chapter we illustrate how these different levels of integration offered by the SA Forum middleware can be used to improve the availability of a legacy ...