Content Steering (we need to write down test cases)

[tobbee]

Desired features:

• livesim2 should provide a built-in content steering server(CSS)
• livesim2 should support two or more "Root CDN paths"
• a configurable external CSS URL
• a configurable UUID in the URLS like /uuid_jljljlajf
• It should be possible to get a list of requests per ContentSteering server filtered by UUID
• The built in CSS should be configurable to change prioritised CDNs in a pattern
• Missing segments or other triggers for client action should be possible

Further thoughts:

• It should be possible to create a session via a REST API and get a specific URL and an ID
• livesim2 can then monitor what the client does as different content steering responses are returned
• It should be possible to fetch the report of what happened via the REST API by using the ID in the response
  • This would make livesim2 stateful, so configurations must expire etc.

• What content steering patterns are desired?
  • Based on wall-clock (e.g. every Xs there is a change)
  • network issue simulations