Introduction - sonata-nfv/tng-sla-mgmt GitHub Wiki
5GTANGO's SLA Management Framework is part of the SONATA powered by 5GTANGO Service Platform. The SLA Management repository includes the SLAs descriptors examples and schemas, as well as all mechanisms that are implemented. The schema files are written in JSON-Schema and they are available here
SLA Templates:
Initial SLA Templates are defined. An SLA template refers to an initial advertisement of the provider regarding the attached NS, while it also describes what type of QoS commitments the provider is willing to take. Each template includes a set of specific Service Level Objectives (SLOs), which defines the maximum values and thresholds allowed for a set of network and service-specific parameters, that ar ealso available and re-confgurable here.
SLA Agreements:
As long as a service is successfully instantiated in the 5GTANGO Service Platform, the Agreement is automatically created. Specifically, once the deployment of the service is completed, the corresponding SLA template is promoted to an actual agreement that is being enforced (i.e. instance of the SLA template). Once the agreement is established the guaranteed requirements of the service start being monitored and checked for breaches of contract.
SLA Violations:
The violation of a SLA agreement is important to the customer. For this reason, while monitoring data are gathered by the monitoring manager, are then published to the SLA manager in case of a SLA violation. An example of an SLA violation can be the following. In this release, availability among others, is a supported metric by the monitoring manager. Different values of service's availability can be signed in the SLA agreement. If 98% is chosen by the customer, this is translated into maximum downtime of his/her service 1.5 seconds in a windows of 60 secs. IF this limit is reached, an alert from the monitoring manager is produced.
License-based SLAs:
An important addition to the SLA Manager is the introduction of licenses in the SLAs. 5GTANGO SLA Manager proposes a service-based licensing model, which links a license to a specific customer and an instantiated NS, by specifying also the number of allowed NS instances. The model provides three types of licenses: a) trial, which supports limited time of trying the desired NS before license purchasing, b) public, which comes with no instantiation restrictions, and c) private, which specifies as mandatory the purchase of a license before instantiating a NS. It is worth mentioning that licensing is provided "as a service” and it is included into the provided SLAs. You can find more information about the License-based SLAs here.