Information Technology Reference
In-Depth Information
the central management component module that manages service
requests, pricing, resource allocations, and so on.
Service operator: the service operator is responsible for day-to-
•
day operation and supervision of the service's functioning. This
role may be i lled by a person or a piece of software, or both.
Service owner: the service owner is responsible for setting busi-
•
ness policies to be followed by the service provider. This role may
be i lled by a person or a piece of software, or both.
With the above dei nitions of the roles, we note that the SLA Manager
is located inside a service entity as a software component to facilitate the
establishment of SLAs for the service provider and its customers. We
therefore consider designing a generic model-based design for SLA man-
agement, which can not only provide basic functionalities for the SLA
management but also be customizable to meet the needs of various service
providers in distributed environments.
10.3.1.2
SLA Manager
SLA Manager provides interfaces for the service client to query the service
provider's offerings, interfaces to communicate with the service manager
and operator-specii c interfaces. The core of SLA Manager is a software
module called the SLA-based service that facilitates the basic communica-
tions between the service provider and the service client. SLA Manager
includes different submodules to support various SLA-relevant opera-
tions. The operations can be classii ed into four groups: (1) specii cation
and negotiation, (2) validation and creation, (3) monitoring and archiving,
and (4) violation and adaptation.
10.3.1.2.1
When a client requests a service, SLA Manager will allow the client to
retrieve the SLA templates offered by the service provider and specify
their requirements in an SLA proposal. During the negotiation process,
SLA Manager allows the clients to submit a proposal based on the tem-
plate and enables both parties to go through a negotiation process that results
in the proposal being either accepted or rejected. During the negotiation
process, both parties can offer counter-proposals and maintain copies of
the intermediate states and the i nal SLA. Some of the basic operations
for the SLA-based service include getSLATemplate(), proposeSLA(),
signSLA(), rejectSLA(), and cancelSLA().
Specii cation and negotiation
10.3.1.2.2
Before an SLA is created, a validation process is required to check whether
the SLA proposal satisi es the SLA creation constraints [9]. The service
Validation and creation
Search WWH ::
Custom Search