@rootwyrm @aneel Who said that? Me? I don’t even think this was the discussion topic… 🙂

@simoncrosby And if MS doesn’t, at least it needs to secure key APM tech partners that fill the gap and tightly integrate with SC2012.

@rootwyrm @aneel Thus, different audience, different UX, different scalability requirements.

@rootwyrm @aneel Disagree. You need 1 console to design a catalog object, and 1 to provision it. Not said the second is just for tech-savvy

@rootwyrm @aneel There’s difference between the orchestrator UI and the self-service provisioning portal or the VM life cycle management UIs

@rootwyrm @aneel By “objects” with mean multi-VM business services, right? If so, I don’t think the large majority of ent orgs are even near

@rootwyrm @aneel Agree. In fact it depends on the context. A solution targeting private clouds won’t need to manage 20M catalog objects.

Static automation workflows won’t help to guarantee service levels. It’s the capacity modeling engine that must generates rules.

Monitoring dashboards need to scale as well. Consoles that look useful with 20 VMs, are probably impossibly ugly with 20K catalog objects.

Static optimization thresholds are not a scalable approach to resource optimization in clouds. Self-learning analytics badly needed.