Fabric based computing infrastructure
Tight integration and sharing of IO resources - data, network, interprocessor, to create virtualized infrastructure in a nutshell is fabric based computing. Cisco UCS is the most publicized example. Obvious benefits "wire once", integrated management, rapid provisioning of compute resources, increased capacity utilization, integration with legacy SAN and LAN infrastructure. High speed network interconnect based on 10gb Ethernet, FCoE provide unified fabric. Migration from legacy compute to UCS would be facilitated by virtualization, vmotion the VM's out of legacy platform to UCS (caveat - source and target CPU's must be compatible). Please share your thoughts on what are the reasons (besides legacy asset life) IT infrastructure managers would not go to fabric based computing.
Subscribe to:
Post Comments (Atom)
3 comments:
Buying IT infrastructure takes a long time of contractual negotiations, all these benefits need to deliver quantifiable value. Why not wait for your incumbent vendor to release their products?
Sunk cost in infrastructure - cabling already done, there is no saving now. Maybe more because you have to undo it.
Skills of IT staff
Post a Comment