Most Infrastructure as a Service clouds present limited capabilities to control how a service behaves at runtime, once it has been deployed, beyond basic low-level scalability rules for VMs. Higher-level approaches fail to provide mechanisms for a fine grained level of control of the service at runtime, being only focused on scaling. These scalability rules are based on an ad hoc \"Grammar\" that is not expressive enough to reflect other desired control mechanisms at runtime (e.g. reconfigurations, dynamic changes in the rules or in the components of the application, retiering, etc.). Here, the authors present an analysis on different alternatives for supporting such features.