CoolingTower deployment service design

Version 1

    At the moment - the deltacloud model is used for the allocation rules - this perhaps needs to move up a level of abstraction to clusters, database and front end model (as per CirrAS). When a new cluster is created THEN deltacloud model kicks in.

     

    Promotion: need a model for promotion of applications and config through dev/test/qa/prod etc... (hudson promotion plugin has some good ideas there). A different "region", eg QA, is at least a partial clone of production (dev would be cut down) - needs to be reflected in the policy rules.