Beware of clouds washing white: public, private and mixed clouds

"The public cloud is homogeneous and the private cloud is heterogeneous," said Bob Muglia, a former president of Microsoft server and tools, at a developer conference a few years ago. "The two-point statement is flawed.

The relative diversity of cloud computing resources has never been a part of cloud discussions and has not been a source of distinction among cloud deployment models. The complexity of implementing a cloud's demand elasticity and resource pool features also makes heterogeneity impractical. However, Muglia's citation is useful for highlighting the technological differences between public and private clouds. In fact, the cloud deployment model only distinguishes between http://www.aliyun.com/zixun/aggregation/13748.html "> Infrastructure sharing in one environment." In addition, the private cloud is no different from any other cloud. Clouds of white washing further complicate the incident.

National Institute of Standards and technology the definition of cloud shows three parts: basic features, service models, and deployment models. Since these three parts are not dependent, cloud washing is difficult to define; there is no architecture for the public cloud to have a set of features, and the private cloud has another. Choosing a deployment model with a small security component is a primary business decision. Does the requirements of the organization allow infrastructure sharing? If not, the private cloud is the right way.

Where does cloud wash white start to play a role? Private clouds are seen as a combination of the high efficiency of the cloud and the simplification of the allocation of control that enterprise it craves. This permits sharing in the cloud while reducing perceived risk. However, the potential input-output ratio is very low and only provides a little improvement in the current approach, such as virtualization.

Capital expenditure on cloud promises vs. Operating costs

A large number of cloud dialogues focus on the public cloud, and many of the advantages of a public cloud apply only to a lesser extent than a private cloud. A big topic for the public cloud is the exchange of capital expenditure models for the operating cost model, which translates large amounts of up-front spending over time into distributed spending.

There are several problems with this model in the enterprise, the first is the variable cost challenge of the budget system based on fixed cost. But assuming that the variable cost model can operate in an enterprise, the local private cloud does not provide this advantage.

Private cloud elements

Now we're going to reveal the difference between the advantages of a public cloud and a private cloud, and we should focus on private cloud characteristics. Here is a brief analysis of the five key cloud features that apply to the private cloud model:

1. On-demand self-service: good, but leads to the risk of resource allocation and hibernation.

2. Broadband network access: good, but need to seriously consider storage.

3. Resource pool: Very good, but if need to meet the needs of the service, homogeneity becomes necessary.

4. Fast elasticity: If there is enough capacity is good. But enough capacity needs to be set aside; Utilization requirements Apply the schema model using the Cloud extensibility model.

5. Measurable services: Getting better, but the detachment needs to be integrated into the account useful.

Since the current focus is on self service, private clouds provide less improvement on existing virtualization models and retain the same risks as existing models-complexity, poor resource utilization, and so on. It is important to establish a process to ensure resource allocation and unused resource recovery.

Private cloud can satisfy all requirements and provide the value of cloud computing, however, additional effort is needed to implement and apply it. Remember, the cloud solves web scalability issues that can fix some enterprise scalability issues.

On-demand service and quick elasticity are the two key features of cloud computing, but using them in an enterprise requires a completely different way of consuming IT resources. For example, the workload is separated by a resource table, and the same resources can be used. This requires that each workload can consume the same set of resources, rather than customizing the configured server. This affects application development and operations.

Seasonal workloads run best in mixed cloud models, significantly impacting development and operations. Creating an application core, running in a private cloud at off-peak hours, invoking resources from an external cloud to meet peak-level requirements requires a complex architecture.

So, is the private cloud right for you? To determine if it is the best cloud model for your business, ask the following four questions:

1. Is there a business problem that can be solved with cloud technology?

2. Do your security and regulations significantly affect the use of private clouds?

3. Can private cloud prepaid capital be offset by improved productivity and/or profit?

4. Can your organization change its application techniques to business solutions?

If the private cloud is good enough to meet your business needs, deploy one. But make sure it's a real private cloud, not a cloud-washed, virtualized datacenter.