Under the trend of cloud computing resource scenario application, Fit2cloud IaaS + DevOps can realize application Lifecycle Automation management

Docker has been accepted by Azure and GCP has proved the need for cloud computing resource scenario application, dispersed and fragmented cloud resources can not meet the needs of enterprise users and operational dimensions. However, Fit2cloud's automation coverage is wider and deeper, and perhaps you no longer need to touch the IaaS backstage.

Cloud storage, Cloud virtual machine, database, Web site and back-end program deployment ... Too much repetitive work and fragmented back-end platforms give them a lot of management and maintenance burdens for complex, broadly-covered companies-not the idea of cloud computing.

MOTO, Hewlett-Packard, Samsung and other multinational companies engaged in cloud computing related work for many years Lan Zhimin understand the inconvenience. During his tenure, he also tried to start PaaS products, but Cloudfoundry's rapid rise made him realise that his small company was not moving fast enough. This time take the scene cloud middleware as the cut-in point, solves oneself in the work as the user firsthand experience the question, he has driven an early set.

The presence of IaaS eliminates the need for businesses such as purchasing and managing machines, and PaaS allows the process to be further streamlined to "requirements validation" and "Application development". But in Lan Zhimin's view, the excessive streamlining of PaaS allows customers to reduce the controllability of technical details and to meet customized details. Fit2cloud's IaaS + DevOps model is his solution to the problem: a more comprehensive, deeper "Docker". Its integration will also include virtual machine management, allowing users to use different language scripts to define "Application lifecycle" automation scenarios, including software installation, application development, application deployment, and system operation, based on application scenarios and application requirements.

For example, the user can define the number of virtual machines/configuration, storage, database, Wordpress installation as a complete process, a key to open, copy, or after the failure to rebuild. In addition, Fit2cloud allows users to monitor and analyze resources in a unified way, and then develop flexible flex scripts or thresholds for resources based on monitoring data.

So far, Fit2cloud has supported AWS, Aliyun and Qingyun. The follow-up will support other cloud services, but they are temporarily focused on perfecting existing services due to the current manpower reasons. For large and medium sized enterprises, the virtual machine scale brought by the increase of business scope will make the operation and maintenance management become complex, and it is necessary to classify these resources according to the application scenario or specific business to make these cloud resources orderly. The open API of the IaaS service provider makes this possible.

According to Lan Zhimin's description, Fit2cloud's Cloud resource Management Service is focused on the rigid requirements in the niche market: for individual users, the number of virtual machines is very few, and manual management is not a hindrance; for large enterprises, their in-house engineers have their own tools and adequate operational capabilities. But for a growing group of small and medium-sized start-ups, a one-stop automated lifecycle Management Service can significantly reduce their operational pressures and expenditures, thus focusing on development and products.

Outside the Rigntscale, SCALR, there are Fit2cloud, cloud (similar function), such as cloud resource management has become a cloud computing unified backend potential. They have across virtual machine service providers, single service providers across the room, across the virtual machine, across the application of global management capabilities. Next, Fit2cloud will be deeply integrated Docker, not only make one-click multiple virtual machine upgrades, patches become possible, but also to a multiple virtual machine a key production environment, application deployment/management becomes convenient.

In fact, taking Fit2cloud and Docker is a less rigorous approach, because Cloud Source Management and Docker coverage of the scope of the comparison. Fit2cloud's cloud management covers creating resources, server automation, mixed cloud management, application automation, and continuous delivery throughout the depth. Docker, which runs within the virtual machine, can only automate application and continuous delivery, and its functionality can be replaced by Fit2cloud scripts or Chef integrations.

Almost at the same time, the need for "cloud computing resource Scenarios" became commonplace. The function of all-inclusive is complicated, it needs to be rearranged and arranged according to requirement to meet the precondition of large-scale application and management.