Shulou(Shulou.com)06/01 Report--

OpenStack has become a trend, but the release OpenStack is not perfect. If enterprises want to build a private cloud, they must fully understand the shortcomings of the release OpenStack in advance, and seek the help and cooperation of professional OpenStack providers in order to give full play to the advantages of OpenStack and build a private cloud that maximizes the competitive advantage of enterprises.

How to use OpenStack in the enterprise? What other problems need to be solved? how can OpenStack be used well in the enterprise? Developers think it's a matter of posture; users think it's stable and reliable, and they can't keep downtime; the boss thinks it can be done by hiring a few more developers and operators.

In fact, the problems of OpenStack in commercial use are mainly in the following five aspects: stability, integrity, high availability, ease of use, dual active and disaster recovery.

Let's start with stability. A good product, performance is not the first element, stability is the most important for the enterprise.

A.OpenStack is far from scalable and stable and needs to be carefully polished.

With the growth from dozens of units to thousands or even tens of thousands of units, can we continue to work steadily without problems? Practice has proved that with the expansion of scale, the overall architecture needs to do enough homework in terms of stability.

For example, you need to design multiple NOVA API and multiple mirrors, load balancing, high availability of nodes, and concurrent response of the database.

In addition, the upgrade problem that is most complained about in the community-Nova,Swift,Cinder and Neutron respectively use their own database to store configuration information, to upgrade, you have to modify multiple database schema, there is no hot upgrade (the upgrade problem has been improved after H version).

For another example, an enterprise encountered a nightmare experience when deploying network services (Neutron), and had to rewrite the code of network components in order to meet the requirements of large-scale applications.

B.OpenStack lacks integrity.

A mature cloud platform should provide computing, storage, network, security, database, big data, middleware, DevOps, monitoring operation and maintenance and other cloud products. OpenStack can only provide three kinds of cloud products: computing, storage and network. If enterprise customers need information security protection products, they must self-help information security platform and integrate third-party products. For example, big data analyzed that Hadoop clusters can be quickly deployed through Sahara, so how can we get through the account, security, management, and operation and maintenance monitoring system between OpenStack and Hadoop?

The high availability of c.OpenStack 's virtual machine level is not doing well.

There is no official statement that OpenStack supports high availability at the virtual machine level, which was proposed in the Folsom version but later abandoned.

Currently, OpenStack has an incubation project, Evacuate, which is used to provide high availability support for OpenStack at the virtual machine level. Currently, Evacuate can only be initiated manually by an administrator. Evacuate does not take into account the deployment attributes of VM, resulting in the invalidation of resource scheduling policy. The change of hostname will cause all virtual machines to be mistakenly deleted during nova-compute restart. This problem is mainly due to the cleaning mechanism of Evacuate. This BUG has been fixed in the L version.

The ease of use of d.OpenStack is not good enough.

With FUEL, you can quickly install OpenStack, but many configuration operations require a command line, which is still a long way from automated deployment with one-click delivery. For example, CEPH distributed storage system, which is widely used on OpenStack, has not yet realized the interface operation and configuration. In addition, OpenStack also lacks a general-purpose basic version.

The use of OpenStack will not be locked by the manufacturer, but there are more than 20 customized versions of OpenStack that can be downloaded, and the customer's choice is very important.

e. The problem of double living and disaster recovery.

Large enterprises have relatively high requirements for business continuity, and the key core businesses have the needs of double living in the same city and disaster recovery in different places. Double active users in the same city means that users' key business systems run in two data centers in the same city at the same time, and provide services to users at the same time. When there is something wrong with the application system of one data center, there is another data center application to continue.

Remote disaster recovery, as the name implies, is to build one or more of the same applications or databases in different regions to take over immediately after a disaster. We can see that although OpenStack also has single-site (Smaug+Cinder) and cross-site (Smaug+Swift) backup and recovery solutions, it is still a long way from the real business dual activity and remote disaster recovery.

For example, the cascading across data centers implemented by Tricircle still requires Cinder to rely on the storage backend's own capabilities for disaster recovery. Tricircle itself is only used as a forwarding relay to find the correct site for users to operate, and it cannot achieve disaster recovery across data centers, which is different from VMWARE's SRM.

We can see that there is still a gap between OpenStack and VMware in terms of functional support and specific details, and we still need to make continuous progress in order to do better. However, as an open source management framework, OpenStack is designed with good intentions. With the use and development of OpenStack in enterprises, it will promote and accelerate its maturity.

Finally, there is operation and maintenance automation. In the large-scale cloud operation and maintenance scene, it is necessary to trigger the repetitive work based on intelligent decision-making of monitoring data to realize the operation and maintenance capability of unattended automatic operation. This part has yet to be discovered by OpenStack.

Conclusion

The process of building an enterprise private cloud is not achieved overnight, and it will be a continuous investment process, which needs to be groped forward in practice. In the next 10 years, it will be the era of cloud 2.0, and enterprises will be the main representatives of cloud. Look to the future and embrace open source. In China, in Asia, in the world, OpenStack has become a trend, we have reason to believe that in the next three years, OpenStack will become the first choice for enterprises to go to V.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.