Archive for the ‘IT Technical Architecture’ Category
“The scope of this document is to provide customers with the necessary guidance to develop solutions for a Microsoft private cloud infrastructure in accordance with the IaaS PLA patterns that are identified for use with the Windows Server 2012 operating system. This document provides specific guidance for developing fabric architectures (compute, network, storage, and virtualization layers) of an overall private cloud solution.”
“The scope of this document is to provide customers with the necessary guidance to develop solutions for a Microsoft private cloud infrastructure in accordance with the IaaS PLA patterns that are identified for use with the Windows Server 2012 and System Center 2012 Service Pack 1 (SP1). This document provides specific guidance for developing a management architecture for an overall private cloud solution.”
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.
Offloaded Data Transfer (ODX) and data de-duplication are just two of the features in Windows Server 2012 Storage. An overview of all of the new features can be found in the Windows Server 2012 Storage Whitepaper.
Technology Roadmapping is concerned with mapping goals to specific technologies and as such is about the timeline for the goals (or market spaces) as matching the lifecycle of the technology.
The wikipedia article references the Sandia Labs paper which seems to be the defining reference in this area and these cover generic technology roadmapping as might be used by a manufacturer to plan product lines for technology products.
In IT services the technology underlies the service and so roadmaps are critical documents for showing AS-IS to TO BE matched to goal, budget, vendor and technology timelines. A possible approach (a commercial offering but with quite a bit of detail on the approach) for developing such a roadmap is here.
In looking for specific examples relating to roadmapping for IT infrastructure I have found very few over the years, one I found recently and particularly like for an IT infrastructure area (Data Center) technology roadmap is the one used at MIT, their IT Roadmaps are here and the specific example is here. If you know of other examples in IT infrastructure please leave a comment.