@@ -173,6 +173,24 @@ Give a worked example across service and network measurements based on the mpeg-
Discuss specific tags
### Decisions
Capacity Decision Context
* Provision compute node
* Provision network provider
Media Service Decision Context
* Place SF
* Unplace SF
* Boot SF
* Connect SF
* Route to SF against criteria
* Change resource allocation to SF
Health Checks?
## **Architecture**
### General ###
...
...
@@ -220,7 +238,9 @@ The second (currently preferred) choice only sends line protocol format over the
The pub/sub protocol still needs some work as we don't want the CLMC to have to subscribe to nodes as they start and stop. We want the nodes to register with a known CLMC and then start publishing data to the CLMC according to a monitoring configuration (e.g. sample rate, etc). So we want a "monitoring topic" that nodes publish to and that the CLMC can pull data from. This topic is on the CLMC itself and note the nodes. Reading the FLIPS specification it seems that this is not how the nodes current distribute data, although could be wrong
## Configuration Measurement Summary
## **Measurements Summary**
### Configuration
|Decision Context|Measurement|Description
|---|---|---|
...
...
@@ -232,9 +252,7 @@ The pub/sub protocol still needs some work as we don't want the CLMC to have to
|Media Service|vm_host_config|compute resources allocated to a VM|
|Media Service|net_port_config|networking constraints on port on a VM|
*Need to refer to TOSCA here*
## Monitoring (usage and performance) Measurement Summary
## Monitoring
|Decision Context|Measurement|Description
|---|---|---|
...
...
@@ -254,7 +272,7 @@ The pub/sub protocol still needs some work as we don't want the CLMC to have to
|Media Service|service|vm service perf metrics|
## Capacity
## Capacity Measurements
Capacity measurements measure the size of the infrastructure slice available to the platform that can be allocated on demand to tenants.
...
...
@@ -274,7 +292,7 @@ network_resource measures the overall capacity of the network available to the p