How to build a cloud factory

The continuous efforts of mankind seem to be lagging behind the change in IT industry. While industry standards for it are essential to drive change in the IT industry, the power of cloud computing to drive change in it is surprising. Recently some companies are deploying "legacy systems" for the introduction of virtualization, and it is worth emphasizing that change is the only constant for data centers. Careful planning is essential to deal with this major change involving the entire enterprise workload-hosting model.

To meet this challenge, it is important to develop an appropriate framework for the issue of cloud transformation. This involves many aspects, including the agility of the cloud, flexibility, transparency, and the interests of end users. Many of them are ultimately related to new and specific infrastructure requirements; the use of self-service portals hosts new applications or host transient processing requirements. Agility is often a beneficial experience when hundreds of thousands of existing workloads move clouds infrastructure. In fact, the opposite is often the case, because the cloud presents a higher standard of demand (for example, qualifying the scale of the catalog and the choice of software), and actually migrating existing physical and virtual servers to the cloud model is quite difficult. In other words, in terms of the expansion of the new workload, it looks less agile in another way.

This is the source of the concept of cloud factory. In the process of industrial production, the factory is the epitome of measuring productivity. In spite of some efforts to prepare for processing machinery, it is essential to provide effective inputs and outputs once the company is to be formed. Migrate to the cloud infrastructure by adopting a common approach, the appropriate design to provide repeatable results, and the Organization's ability to devote the least amount of time and effort.

Under the guidance of this concept, it is important to further elaborate the appropriate design. Many companies can solve such problems from the grassroots, using spreadsheets and the ingenuity of smart people to determine action. The problem with this approach is that it rarely touches on the main point-the answer is really accurate, mainly because the problem is too complex. Migrating workloads to the cloud is related to many aspects, such as handling large amounts of historical data, analyzing configuration information on servers, migrating applications, scaling and software heap layers of modeling targets, enforcing enterprise and regulatory requirements, complying with service level agreements, and data protection rules. The use of spreadsheets is not very good, roughly the same way, the enterprise accounting platform is not suitable for the use of spreadsheets. Even if they are tricked into giving decent answers to this simple environment, they may not generate reports to satisfy shareholders, managers, engineers, operators, etc. All of these personnel need important and detailed decisions to ensure achievement and risk minimization.

The

effort to analyze the cloud migration list concludes that a key concept connects all of these. This concept is a strategy that represents the basic rules including how to manage the workload, where they should go, how much resources should be apportioned, etc. There is no appropriate strategy; The hosting decision leaves the practitioner to perform the migration; There is no plan whether they did the right thing. Cloud infrastructure planning and management do not have the right strategy to try to fill out a tax application without instructions-too many variables are getting the right strategy.