Draft: Cdn requester
Draft use for discussion for the future cdn-requester. Having not done any serious SlapOS for the past years, it is needed to go in the right direction. And easier than emails.
TODO
-
Garbage collect of stopped or destroyed slave??? -
Check domain name via CDN via software PY -
Do not request to CDN with default parameters -
Add promise for failing instance to help operator debug -
Add clear parameters for computer uid / instance uid for sla -
Add Egg tests -
Use JSON parameters -
Add SR tests -
Request 1000 share instance to test scalability and garbage collection
Notes from initial discussion:
So domain name validation should be done in a separate SR that request through a remote node to the Node.
SR CDN is purely technical now called "technical CDN". New SR is business is doing a lot a validation.
Premium CDN existing Shared instance are all ported to new SR.
Remove everyone from premium CDN project aside from its operators.
New SR can use Jinja with Buildout.
At the moment the Business CDN SR will only do the Domain name validation.
XXX Maybe we want to sign the parameters provided by the Business CDN to make sure we trust the source. After cleaning up the current data.
For each shared instance on the Business CDN it request a Shared Instance on the technical CDN