Parsing how to choose the right virtual machine for a private cloud

Industry dialogues have gone beyond understanding http://www.aliyun.com/zixun/aggregation/14032.html > What is Cloud computing, and in an enterprise IT environment decide how to deploy it better. This evolution is similar to the debate over past virtualization candidates-knowing how to determine whether a physical server can be a good virtual machine. The idea of the

Cloud candidate is to choose the best candidate when you enable the cloud, as well as to maximize the return on your cloud investment. Here's a checklist to determine the best candidate for your private cloud. What network does the

cloud load need? such as virtual server threads, memory requirements, the total load of network resources, the consumption of applications in the private cloud, these are extremely important.

The need for a busy network resource load to link to other servers in the LAN so that it does not create the best cloud candidate. Putting these loads into a private cloud can cause problems such as bandwidth or latency that can affect the overall performance of the cloud. Measure network utilization of the cloud server and other servers located in the local data center.

What other services are interconnected with private clouds? Consider the communication between cloud load and cloud workload load in other networks. For example, almost all windows-based IT services tend to be Active Directory certified, because desktop operating systems do this. Domain controllers must handle a lot of traffic, so moving them completely into the cloud may be a bad idea.

In addition, the service has some interaction with other services in the local data center and is unlikely to be affected by the relocation of the location. Delay has little effect. Viewing interoperability in virtual machines is a good way to find the resources that are ready in the cloud. Is there a clear separation between the workload in the

Private cloud and other workloads (for example, "hard wire")? The isolation cloud service can be used as a good cloud candidate and a separator between bad lines. Orphaned services can create brilliant cloud candidates, such as whether those services are in your DMZ. By design, the DMZ has a "hard line" around its services, especially in firewalls, which can be separated from the network and LAN. Partitioning means that you can easily move everything from the DMZ to the cloud. The DMZ can be clearly divided into what makes a good private cloud candidate. Combining the isolation of virtual firewalls between different cloud services and DMZ services is likely to be successful in the cloud.

Cloud services are friendly to replicate? Some IT services have begun to design replication in mind: Design communications to support latency, bandwidth types, and you will experience it in LAN and cloud communications. These services may include offsite backups, server failover, or other servicesProtocol, for the network can not meet the speed of the LAN to prepare.

How painful would you be if the data in the private cloud were compromised? The final check, indeed, is a direct result of early attention to cloud security and data ownership. When you choose to put a virtual machine in the cloud, the security, ownership, and management issues surrounding the data must be considered factors, and some virtual machines and some IT resources work with the data, and if lost or compromised, it can cause significant pain to the enterprise.

Note that a potential data type that enables a cloud virtual machine can be handled. If lost or exposed, the value of the data is greater than migrating to the cloud, then it is best to place the virtual machine in the datacenter.

To select the correct virtual machine for the private cloud, you want to analyze the resources used by each virtual machine and service. You also need to check the risk of moving these resources into the cloud. With the right survey, you can find the best resources and services, and you can deploy them to a private cloud relatively easily.

(editor: Heritage)