How can we maximize Hyper-V virtualization?

It has been a while for developers with limited funds to use public cloud services to guide the project. However, IT administrators must point out the prospect of deploying public cloud services from different perspectives.

For example, how do they expand our application servers to the cloud? How do they provide unified single sign-on from a non-network connection location to their domain )? How do they ensure they comply with their SLA )?

IT administrators need to see these factors and decide how to use these new resources when providing security, predictable availability, and consolidation points for existing infrastructure. If you have deployed Microsoft's Hyper-V virtualization, you have taken a step toward the cloud.

There are many cloud types, ranging from platform to storage, but most enterprise administrators want to start at the infrastructure level. Using your existing computing resources to drive servers is the first step towards cloud integration. Since cloud infrastructure is based on Virtualization on some forms of management program core, having a high degree of Virtualization in your own data center is a key step to prepare for migration to the cloud. VMware has made a lot of news recently on the provision of cloud services based on VMware ESX compatibility, but this only verifies one truth: migrating virtual machines to the cloud is like migrating virtual machines between internal hosts.

Which system is available on the cloud?

When deciding what a cloud-available system is, let's look at your application portfolio and make a decision. Many companies are trying to use less critical applications at the beginning. You may want to use a back-end system for applications that do not require too much integration, such as some websites or independent website systems. Many people are also cautious about the security of sensitive information. Even if a cloud system is not exposed to large data attacks, it is better to familiarize yourself with the environment and ensure its security, rather than at the risk of losing sensitive data.

Integrate Hyper-V virtual machines into the cloud

There are two methods to integrate Hyper-V. Microsoft prefers to work with partners and provide its own solutions. First, Microsoft's Aure platform provides an infrastructure as a service (IaaS) key in a data center dominated by Microsoft. For example, the cloud-based SQL Server and IIS-based. NET platform make it easier to migrate existing systems to the cloud. Now the system is developed for the Microsoft ecosystem.

The only field that Microsoft lags behind is to provide a full Hyper-V Service Selection managed by the Administrator. But now it provides the VM role on the Azure platform. This Server enables you to use a custom Windows Server 2008 R2 operating system to install the load automatically. You are still limited by Azure rules, which means you must deploy stateless applications to prevent data loss. Classic, stateful Client/Server execution is not supported. When you decide to deploy an application in this role, think about network services.

The VM role allows you to run your own VHD on the cloud, even though Microsoft still manages the underlying operating system, network, and IP structure. The main difference between VM roles and other roles is that patches are not automatically managed. Although it is still being tested, VM roles hopefully will soon be integrated into Azure solutions.

Future versions of the system center will provide closer integration with Azure, providing a single way to manage and monitor VM roles. Although VMware vSphere is far ahead of integration in this field, Microsoft's system center 2012 should bring close integration to local Hyper-V machines and Azure Virtual Machine roles. This includes supply, self-service functions, and the ability to upload VHD to the cloud, or the ability to deploy custom templates without uploading additional bytes to deploy standardized images.

Clearly, Azure is not a pure IaaS battlefield. It does focus on building. NET applications as a platform-as-a-service SaaS) rather than running custom operating systems, including applications. Microsoft does understand that too many applications cannot be deployed only from one. NET console, so there is a choice.

If you want to deploy a real IaaS, you will want the provider to give you more freedom to choose what you deploy on the cloud machine instance. The best example of IaaS is Amazon EC2, which allows you to spin machine instances up to Amazon cloud. Although Amazon only supports centralized deployment of certain types of network services, they do give you some freedom.

Some manufacturers will assist in transferring your internal VHD to the cloud, but many will want you to gradually clear a new build. If you plan to use cloud providers in hybrid scenarios, integration points may be very important. In hybrid scenarios, you want to extend private hosted applications to the public cloud. If you plan to keep these application servers and networks independent, this will not be a big problem.

Another aspect of understanding includes possible authentication integration. If you want these public cloud machines to operate using your Internal Active Directory, You need to combine your directory or provide some virtual networks in the public cloud, it allows your network to expand to the vendor's domain. Amazon uses Virtual Private clouds to prepare for this field, but other vendors are eager to provide the same custom integration points.

It is too early for Hyper-V cloud

Although Hyper-V is still in the cloud field, it has developed rapidly. You will be very helpful if you start to study your choice and select several applications that can prove your concept. The development environment and network-oriented applications are both the first choice. Once you understand the power of cloud services, you will use it as another tool to resize and increase reasonable startup costs, with ample global availability.