Cisco公司对虚拟技术的理解与实现.pptVIP

* /ISM/ServiceCatalog/MyServices/VirtualEnvironment The requester does not need to know about which VLAN the VM will be provisioned on, just the Usage Questions? Transcript: Let me introduce you what the concept of CITEIS is and really the framework of what were trying to provide. What we want to do is paint a picture of, I provided timings on the previous slide of how long it took to provision these cycles. Well lets look a little bit and lets peel that layer a little bit and look at what the details are. What went into a manual provisioning effort? You have the architecture and the design. You had to go through scramble and try to figure out where to put these resources. You not only had to figure out where you had to put the resources, you had to procure them, install them, configure them and then as an afterthought think about securing it and then deliver it with really a low confidence because theres so many hands were in the way or hands were part of the process and to delivering these resources. What we determined before CITEIS is that it was very machine-oriented meaning one application to one machine and we wanted to decouple that. There was manual provisioning efforts and as you can see those manual provisioning efforts are called out on the visual above. It was hard to control the utilization. We didnt have a solid understanding where we had ideas of where capacity optimization was but where to put these resources, it was a challenge. What we determined is that that was definitely a requirement and a risk that we wanted to control. Then we looked at some of the cost models that were associated with that and that was the tie provisioning time and the operational cost associated with it. Both of those are negative customer satisfaction so were looking to resolve that and we have resolved that. Then finally the configuration risk. There were lots of hands involved, lots of handoffs that occurred and what we realize is that when theres too many hands in the