v5.1 (2020-01-08)

• Add listener to check the license expiration date
• Update monitoring rules based on new metrics
• Update license validation
• Improve API response messages
• Improve logging system
• Minor bug fixes

v5.0 (2019-09-06)

• Update SLA Schema (YML, JSON)
  • Simplify & Optimize the SLA Schema
  • Update SLA schema to support Licensing information
  • Update SLA schema to support optional guarantee terms
• Add cleaned up SLA examples (YML, JSON)
• Standardize logs (Apache Log4j2 logging services)
• Optimize the SLA Template generation
• Mapping of SLOs with monitoring parameters in the SLA template
• Introduce User Authentication in SLAs
  • Include user authentication in all SLA APIs
  • Include user authentication in all RabbitMQ messaging
  • Include user information in Templates
  • Include user information in Agreements
  • Include user information in Licenses
• Support Kubernetes (K8s) compatible development
  • Support multiple RabbitMQ instances
  • Both scenarios (OpenStack WIM/K8s) are supported
• Introduce new SLA parameters (availability, packet loss, input connections)
• Introduce mapping between low-level QoS parameters and high-level SLA terms
  • Usage of deployment flavors in order to solve the problem of deploying different flavours of a NS according to the SLA
  • Create the mapping between a desired deployment flavor and an SLA during the SLA Template creation
  • Support of efficient CRUD operations for managing and configuring the deployment flavor in the SLA Template, through RESTful APIs.
• Introduce Licensing as a Service into SLAs:
  • Add Licensing as a Service Level Objective (SLO)
  • Include license information into the SLA Template
  • Introduce license per NS and customer
  • Introduce three kinds of license types (Public, Trial, Private)
  • Introduce buying of a license in case of private license
  • License specifies the number of allowed NS instances
  • Check license status during NS instantiation
  • Support of efficient CRUD operations for managing and configuring all the Licensing information, through RSTful APIs.
  • Create relevant database table for storing correlation records between NS-SLA-Customer
• Provide statistic information for graphs creation
  • Nº SLA Agreements vs. Violations
  • Nº Licenses Utilized / Nº Licenses Expired / Nº Licenses Acquired
• Updated integration with:
  • tng-portal
  • son-monitor
  • tng-cat
  • son-broker
  • son-postgre
  • tng-api-gtw
  • tng-gtk-sp
  • tng-schema

V4.0 (31/07/2018)

SLA Management Framework (tng-sla-mgmt)

1. SLA Schema Introduced (YML, JSON)
2. SLA Template examples provided (YML, JSON)
3. Create a new SLA Template with one or more guarantee terms
4. Automatic formulation of the Agreement, when a Network Service is instantiated
5. Mark SLA (Agreement) as ‘TERMINATED’ on service termination
6. Mark SLA (Agreement) as ‘VIOLATED’APIs for SLAs Management are introduced (Check WIKI pages)
7. Consume SLA violation alert from Monitoring Manager (Through MQ)
8. Publish violation alert to another topic (SLA manager driven)
9. Unit tests developed
10. CheckStyle tests developed
11. Integration tests developed (tng-tests Github’s Repository)
12. Health Check developed (PING/PONG)
13. Integrated with:
    1. tng-portal
    2. son-monitoring-manager
    3. tng-cat
    4. son-broker
    5. son-postgre
    6. tng-api-gtw