Service Oriented Data Center using VFrame

Cisco VFrame Data Center is appliance based network orchestration solution (based on linux). VFrame provides dynamic pooling, sharing, and virtualization of server, storage, and network resources. VFrame connected via GE and FC to the network (IP) and storage.

VFrame works by defining application requirements based on service requirements. The data center will be treated as pools of resource types and freely share resources among applications based on usage patterns and availability requirements.

For example : at peak usage time, your database application might need ten servers, but afterwork hours, that requirement might drop to one server.

• Traditional provisioning models : You would have to dedicate ten servers to the application;
• Service model : you could provision ten servers during peak hours, but during off-hours you could provision one server, and reprovision the other nine servers to another application, such as network backup.

VFrame Benefits

• Physical resources are acquired only when you deploy a service network and are released when you undeploy it.
• VFrame monitors the service and remaps, reconfigures, reacquires, or otherwise alters the resources as required by the service’s operations.

Related Products

• Intel/AMD based blade servers running Windows/Linux OS
  
• Catalyst switches
• Cisco MDS Fiber Channel switches
• Storage vendors (EMC etc.)
• Firewall Service Modules (FWSM), Load Balancer Modules
  
• Cisco Secure ACS to control user authentication to VFrame Virtual Contexts (ways of limiting user access to VFrame features)
• Golden Image Repository (collection of operating system and application software copied from a model server, which is a server that you have configured for running a particular application). Supported OS & application software : Windows OS/Linux/VMware ESX server (to enable server virtualization on the blade)
  
• Client system running java (JRE), supported os is Windows 2000 or XP

VFrame and VMware
VFrame will load ESX onto an empty blade and then configure all the network and storage connections that the ESX hypervisor needs. The VMware software can then take over to load and configure virtual machines on top of the hypervisor.