Skip to content

v5.0 (2019-09-06)
Compare
Choose a tag to compare
@ekapassa ekapassa released this 06 Sep 11:25
· 11 commits to v5.0 since this release
5.0
5fc258e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
  • 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
Assets 2
Loading