This document describe the configuration and monitoring specification for cross-layer management and control within the FLAME platform. All information measured by the CLMC aims to improve management and control decisions made by the platform against defined performance criteria such as increasing Quality of Experience and cost reduction.
This document describe the configuration and monitoring specification for cross-layer management and control within the FLAME platform. All information measured by the CLMC aims to improve management and control decisions made by the platform and/or media service providers against defined performance criteria such as increasing Quality of Experience and cost reduction.
## **Authors**
...
...
@@ -38,7 +38,7 @@ Service management decisions relate to processes for Service Request Management,
The management and control processes implemented by the FLAME platform define the decisions, variability and constraints. The detail for the implementation of orchestration, management and control is under discussion and the following is based on a best understanding of what was described in the FLAME architecture.
### **Static Configuration**
### **An Elementary Starting Point: The Static Configuration Scenario**
The 1st scenario to consider is an entirely static configuration. In this scenario a media service provider defines explicitly the infrastructure resources needed for a media service. The static configuration is what is proposed by the adopted of the current TOSCA specification for the Alpha release. Here an MSP declares the resources needed to deliver a desired performance level (implicitly known to the MSP). In an extreme case, the approach results in a static infrastructure configuration where the MSP defines the entire topology including servers, links and resource requirements. This would include server locations (central, metro and edge DCs) and when the servers are needed. The most basic case is deploy everything now for the lifetime of the media service. This full declaration would statically configure surrogates through the explicit declaration of servers and software deployed on those services.
...
...
@@ -74,7 +74,7 @@ Issues related to this decision include:
*D2 CLMC outcome: a set of measurements describing media service infrastructure requirements.*
### **Variable Configuration**
### **Where Next: Fast Variable Configuration Scenarios**
Variable configuration identifies configuration state that can change in the lifetime of a media service. Variability in configuration state includes:
...
...
@@ -88,8 +88,9 @@ Each transition in state is a decision that has a time in the lifecycle (when is
General issues reated to variable configuration include:
* What are the points of variability within the platform
* How is variability configured, either through default policy or TOSCA templates?
* What are the points of variability within the platform?
* How is variability configured, either through default platform policy or TOSCA templates?
* Where are we contributing innovation in variability? e.g. network + compute + service factors considered together
We now discuss key decisions associated variable configuration
