The disadvantages of Openstack for VMware

On the left is my personal, if you need further communication, please add. On the right is my public number "OpenStack private cloud", if interested, please pay attention.

Two blog posts, "OpenStack kills VMware (1)", "OpenStack kills VMware (2)", and provides some comparisons between OpenStack and VMware, My starting point is to use the Community open source version of OpenStack instead of VMware to achieve cost savings for the enterprise. In addition, based on the current situation of the vagaries of international trade, maybe when someone else EMC does not give us business, we final touches is also very necessary.

After a few VMware project practices, and discovering the advantages of VMware as a commercial product, the first two articles are the advantages of OpenStack, and here I want to talk about its disadvantage, or the community open source version of OpenStack if it is to actually fall, There are places where we have to work hard to improve. Below is a brief summary of the following for example, note that OpenStack refers to the community open source version of OpenStack:

1, the use of VMware easy, the entire operation configuration process is easy to understand.

As a mature commercial product, VMware products first from the convenience of use more than OpenStack, all of its installation packages directly from the official website download, the entire installation process is a graphical interface, for users accustomed to the Windows operation is very comfortable. OpenStack if the operation of the official website, for ordinary users, is simply an impossible task, even with the corresponding technical level of engineers, it takes a long time to explore the familiar process of experiment, at the same time, the community's documentation is not responsible for correctness, in accordance with the community document operation, always encounter some pits, In addition, there is a big obstacle is the installation process needs networking, and some installation packages in foreign sites, in our "wall of the country" domestic many times to visit foreign web site speed is too slow. Although for this piece we have been greatly resolved through the package installation image, see "OpenStack Kolla installation Image", but the subsequent personalized configuration and more advanced features of the configuration is not as convenient as VMware.

2, VMware has a dedicated P2V migration tools and monitoring tools.

VMware's P2V migration tools and monitoring tools are also directly download the corresponding mirror image installation deployment, are both a tool-and graphical solution, easy to use. Solve the actual use of virtual machine migration and online virtual machine monitoring, for a mature product, these two pieces of content are very useful functions. If OpenStack is to implement virtual machine migration, the process is complex and time consuming, and it is generally recommended that the application be migrated instead of the virtual machine or the physical machine's overall migration. The monitoring tool OpenStack has its own ceilometer component provided, but the individual is not recommended to install because the monitoring program generates a lot of data and it is recommended to use other monitoring tools, such as Zabbix.

3. Unplanned physical server downtime, VMware's HA feature protects virtual machines running on corrupted servers, and automatically migrates to other working hosts in a reboot without manual manual intervention. OpenStack If you enable Ceph distributed storage, you can take time to heat the migration, but need manual operation, for unexpected physical machine failure downtime, but also need to post-mortem manual intervention to recover, although the operation is very simple, but still do not fully automatic failure recovery.

4, the difficulty of maintenance of VMware is much simpler than OpenStack. VMware If there is a failure of the virtualization software itself, such as vcenter failure, directly reloading vcenter can not affect the operation of other virtual machines, ESXi node failure, if HA is enabled, also does not affect. In contrast, if the controller node fails for OpenStack, if HA is not enabled, then the entire virtualized environment will be affected if HA is not enabled. In addition, if the OpenStack Control node controller in a component problems, positioning and solve the problem requires a considerable level of technical ability, need to be familiar with the corresponding knowledge areas, such as MARIADB, Rabbitmq,haproxy,keepalive, Ceph, Docker, and so on.

The disadvantages of Openstack for VMware