Microsoft Cloud OS and Private Clouds
Ignoring the poor form of quoting oneself; in a post last year I commented on “amount of IT infrastructure capability it delivers as standard” in Windows Server 2012 and “Microsoft’s learning from the demands of running infrastructure at large scale with virtualization as an integrated part of that”. Microsoft’s recent announcement of System Center 2012 SP1 seems to reinforce this view.
Also on learning from scale: How Xbox can transform your datacentre
The Register’s view on How to build a perfect private cloud with Windows Server 2012 shows how this might all be put together on-premise.
That article also raises a key point about application availability and whether that is delivered by the application or the infrastructure. The move to application replication that we saw with, for example, database availability groups in Exchange 2010 and the use of local storage in that application, has begged questions about when is a SAN functionality required (thinking hardware-based storage replication) and raises the possibility of replication to public cloud. Where to place the responsibility for application availability is tricky as infrastructure architects may be reliant on platform or application architects to be aware of what availability models are in the application; that information could surface through technology roadmapping and vendor management. The separation of the application (software), platform and infrastructure layers in private cloud architectures can be seen in both the Microsoft model:
and the Cisco Domain Ten blueprint; for more on the latter see Introducing Cisco Domain Ten(SM) – Cisco Services’ Blueprint for Simplifying Data Center and Cloud Transformation.