...
Hide If | |||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||
|
Show If | ||
---|---|---|
| ||
This specification involves two resources: Service Level Agreement "SLA" and "SLA Violation" |
...
Service Level Agreement "SLA" Resource
This Service Level Agreement "SLA" Resource Model aims at illustrating the way to translating "SLA Resource Model" in JSON representation, reflecting the resource aspect described in the "SLA API Profile" (Management Requirements) document V0.2. Service Level Agreement (SLA) Resource Model and associate attributes are aligned with those described in SID Service Level Agreement modeling. Meaning no Resources are imported from other sources. Besides, the entities are represented in terms of roles, each with its rights & duties covering Multi-partner model illustrating B2BX model (SLA Provider, SLA Consumer, SLA Auditor, EndUser roles). In this model, "SLA Provider" is referring to a CSP while "SLA Consumer" is referring to a DSP. The "EndUser" is referring to the customer of the DSP, in some cases he could be a customer of both (CSP and DSP). "SLA Auditor" role is to monitor SLA as described in TR178V2. It could be played either by the CSP himself or delegated to a 3rd party. The "Agreed" or "Approved SLA" is described in terms of SLA rules which contains the Metrics, their related values or range, thresholds, valid period or date, consequences in case of violation of any clause of the SLA. It is also assumed all Metrics are the existing ones which are stored in the Service Provider "Metrics Library" with their attached references. Besides, each metric is attached to a given Product in the Catalogue with a dedicated reference e.g. "URL". The Service Level Agreement "SLA" resource model is also characterized by its "validity period". This use case covers the situation where the validity period is pre-determined (planned) which excludes the case of Time-variant SLA that could be attached to a "SLA on-Demand" use case. The latter could be considered in another release for specific use cases (Cloud, virtualization) for instance.
|
...
|
...
...
|
...
...
|
...
...
This "SLAViolation" is the second resource considered in this translation into JSON representation. The same representation used for "SLA" resource is applied and is aligned with the SID modeling as well.
|
...
...
|