|
At this tier, ASSL exposes service-level objectives, self-management policies, architecture and AS-level actions, events, and metrics.
 |
|
ASSL SLO Specification |
AS SLO. Service-level objectives (SLO) are a higher-level form of behavioral specification that establishes objectives -
for example, performance. The ASSL concept assumes that the AS service-level objectives (AS SLO) constitute a global task, the
realization of which is to be decomposed into lower-level Autonomic Element (AE) service-level objectives (AE SLO).
 |
|
ASSL Self-management Policy Specification |
AS Self-Management Policies. At this tier, the ASSL formal model specifies the four (so-called self-CHOP) AS self-management policies:
self-configuring, self-healing, self-optimizing, and self-protecting. In addition, ASSL leaves open the option of specifying other
AS-level policies that cannot be classified as any of these four policies. ASSL specifies the policies with fluents and mappings,
which are using AS-level actions and events.
AS Architecture. ASSL addresses ASs as multiagent systems, where the individual agents are AEs controlling resources and
delivering services. Each AS agent is an AE. At this tier, the ASSL framework helps us to specify the topology of the AS.
The architecture is specified as a correlation between the AEs or groups of AEs.
 |
|
ASSL Action Specification |
AS Actions & Events. The AS-level actions and events have the same structure as the AE-level actions and events have, but are
applicable mainly at the AS level.
AS Metrics. ASSL generally classifies metrics as AS-level metrics and AE-level metrics, together constituting a set of global
metrics - parameters and observables, which the AEs can control at a lower level.
|
