Information Technology Reference
In-Depth Information
FIGURE 10.4
Example of a MOF i le of SLA-based service for SLA negotiation operations.
declare a number of other modules by uploading the respective models to
the SAP. It is possible for the service provider to modify the meta-models
of certain modules without affecting the others. The SAP maintains the
model validation mechanisms to check and validate the modii cation of
the models at runtime to ensure that violations or conl icts do not occur.
10.4
In this section, we will describe the data model in SLA Manager, referred
to as an
SLA model, and present its UML design. The SLA model dei nes
the data structure of the SLA templates and SLAs which are used to create
respective SLA templates and SLA proposals/agreements during the SLA
negotiation process. We will discuss the lifecycle of an SLA and the imple-
mentation details to realize SLA negotiations in this section.
SLA Model and Its Implementation
10.4.1
SLA Model
The SLA model contains complete information regarding the service
type, user requirements, business values, and so on. It takes advantage of
the standard object-oriented paradigms such as inheritance and class
hierarchy. We dei ne the SLACommon class as the core of the SLA model.
This allows us to group common functionalities used by both the SLA
class and the SLATemplate class.
Figure 10.5
shows the UML diagram of
the SLACommon class and its associations with the SLA class and the
SLATemplate class. The SLACommon class consists of four major data struc-
tures: context information, service terms, guarantee terms, and service-level
Search WWH ::
Custom Search