CN112000441A - Method for managing virtual machine life cycle based on kubernets acoustic arrangement - Google Patents

Method for managing virtual machine life cycle based on kubernets acoustic arrangement Download PDF

Info

Publication number
CN112000441A
CN112000441A CN202010857674.9A CN202010857674A CN112000441A CN 112000441 A CN112000441 A CN 112000441A CN 202010857674 A CN202010857674 A CN 202010857674A CN 112000441 A CN112000441 A CN 112000441A
Authority
CN
China
Prior art keywords
virtual machine
kubernets
api
crd
controller
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202010857674.9A
Other languages
Chinese (zh)
Other versions
CN112000441B (en
Inventor
潘峰
唐晓东
蔡卫卫
高传集
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Inspur Cloud Information Technology Co Ltd
Original Assignee
Inspur Cloud Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Inspur Cloud Information Technology Co Ltd filed Critical Inspur Cloud Information Technology Co Ltd
Priority to CN202010857674.9A priority Critical patent/CN112000441B/en
Publication of CN112000441A publication Critical patent/CN112000441A/en
Application granted granted Critical
Publication of CN112000441B publication Critical patent/CN112000441B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/45562Creating, deleting, cloning virtual machine instances
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/45591Monitoring or debugging support

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

The invention provides a method for managing a virtual machine life cycle based on kubernets declarative arrangement, which belongs to the technical field of kubernets cloud native computing. The VirtualMetaOperator tool consists of vm-Controller + vm-CRD + Provider-CRD and vmc-api components. By the method, the management of the life cycle of the virtual machine of the multi-cloud platform can be effectively improved, the complexity of arranging and using the large-batch virtual machines is reduced, and the working efficiency of operation and maintenance implementation is improved.

Description

Method for managing virtual machine life cycle based on kubernets acoustic arrangement
Technical Field
The invention relates to the technical field of kubernets cloud primary computing, in particular to a method for managing a virtual machine life cycle based on kubernets acoustic arrangement.
Background
There are two ways to manage virtual machines: the OpenStack community Kata project and the open source project Terraform multi-cloud management tool.
The Kata project mainly treats Kata-container as a plug-in of docker, and the Kata-container can be started through docker commands. The biggest highlight of Kata is to solve the security and isolation problems of the traditional container sharing kernel, the method is to make each container run in a lightweight virtual machine and use a separate kernel, but the use of the virtual machine is limited to OpenStack and is not flexible enough, and cannot meet the requirements of complex scenes.
The Terraform manages the virtual machine in a mode of adapting to the Provider call API of different cloud platforms, supports the cloud platforms of various manufacturers, and can also develop and extend the Provider plug-in of the Terraform by self to connect the cloud platforms of the Terraform. However, Terraform uses a command line to execute declarative management, and needs an operator to master the grammar of Terraform and write a corresponding template file; the command line execution is synchronous operation, and the command line is finished only after all steps are executed, so that the human-computer interaction operation is more, the automation cannot be realized, and the efficiency is lower.
Both Kata and Terraform cannot satisfy fast and flexible virtual machine arrangement management. In order to improve the efficiency of managing virtual machines and reduce the difficulty in implementing operation and maintenance, a new method must be developed to improve the capacity of arranging and managing virtual machines.
Disclosure of Invention
The technical task of the invention is to solve the defect that the Kata and Terraform modes in the prior art can not meet the requirement of fast and flexible arrangement management of virtual machines, and to improve the efficiency of virtual machine management and reduce the implementation operation and maintenance difficulty, the experience of personnel for manually operating and implementing operation and maintenance of Terraform is coded into a vm-Operator tool of Kubernetes by combining the Operator framework technology of Kubernetes. By means of a kubernetes cloud native technology, the virtual machine is integrated into a custom resource of the kubernetes, and the arranging and managing capacity of the virtual machine is improved.
The technical scheme adopted by the invention for solving the technical problems is as follows:
a method for managing a virtual machine life cycle based on kubernets acoustic arrangement is characterized in that a VirtualmetaOpera tool is realized based on an open-source Operator technical framework in kubernets, and the VirtualmetaOpera tool realizes automatic management of a virtual machine in a mode of monitoring resource object states and calling a terraform command line.
Optionally, the VirtualMetaOperator tool is composed of vm-Controller + vm-CRD + Provider-CRD and vmc-api components.
Optionally, an open source Operator in the kubernets: the method is a controller for sensing the application state, and automatically creates, manages and configures the application instance by extending the kubernets API.
Optionally, the CRD: the resource type is customized by the user in kubernets;
Virtailmachine-CRD: declaratively defining metadata of the Virtailmachine virtual machine, including virtual machine configuration related information;
the Provider-CRD declarative type defines a Virtailmachine-assisted metadata resource model containing relevant information of a cloud platform.
Optionally, the VirtaulMachine-Controller: the mechanism of kubernets controllers is utilized, the coordination logic is triggered by monitoring the state of vm-CRD or vmStateful-CRD resource objects, and different operation steps are driven through interface calls of vmc-api.
Optionally, the triggering coordination logic includes creating, deleting, updating a virtual machine or a virtual machine group related operation.
Optionally, the vmc-api: and a back-end service for providing an api interface, wherein the component encapsulates a command line tool of terraform to manage the life cycle of the virtual machine and is used for providing an asynchronous interface for a vm-controller service.
Optionally, a resource object of vm is created, and the implementation flow is as follows:
101. creating resource objects
apiVersion:infra.x.com/v1alpha1
kind:vm
metadata:
name:example-vm
spec:
#Add fields here
providerNam:OpenStack
...
apiVersion:infra.x.com/v1alpha1
kind:Provider
metadata:
name:OpenStack
spec:
#Add fields here
auth_url:http://10.1.10.4:8090/
...
102. The vm-controller monitors the newly added object of vm, starts a virtual machine creating process and calls vmc-api virtual machine creating interfaces;
103: vmc-api receives the request of creating virtual machine to check the parameter, then returns the response, and starts a task execution shell command in the background to call the terraform command line to create the virtual machine; after the execution is finished, analyzing the log result and reversely notifying the vm-controller by refreshing the state of the corresponding vm-CRD resource
104. After monitoring that the state of the vm resource object changes, if the vm resource object is application _ success, the vm controller task successfully establishes a terraform command line of the virtual machine, and then calls a monitoring virtual machine interface of vmc-api;
105. vmc-api will add the virtual machine into the monitoring queue, detect once every a period of time whether the ssh of the virtual machine is available, if so, refresh the vm state to running;
106. the vm-controller monitors that the virtual machine state becomes running, i.e. the created virtual machine is considered to be available.
Compared with the prior art, the method for managing the life cycle of the virtual machine based on kubernets declarative arrangement has the following beneficial effects:
by the method, the management of the life cycle of the virtual machine of the multi-cloud platform can be effectively improved, the complexity of arranging and using the large-batch virtual machines is reduced, and the working efficiency of operation and maintenance implementation is improved.
Drawings
To more clearly describe the operation principle of the method for managing the life cycle of a virtual machine based on kubernets declarative arrangement, a simplified diagram is attached for further description.
FIG. 1 is a schematic diagram of a method for managing a life cycle of a virtual machine based on kubernets declarative orchestration in accordance with the present invention;
FIG. 2 is a flow diagram of the present invention for creating a resource object for vm;
FIG. 3 is a flow diagram of the present invention for deleting a resource object for vm;
FIG. 4 is a flow diagram of the present invention updating a resource object for vm;
FIG. 5 is a flow diagram of the present invention for monitoring multiple virtual machines.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to fig. 1 to 5 in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
As shown in fig. 1, the method for declaratively arranging and managing the life cycle of a virtual machine based on kubernets according to the present invention realizes a VirtualMetaOperator tool (vm-oooperator for short) based on an open-source Operator technical framework in kubernets, and the tool realizes automatic management of a virtual machine by monitoring the state of a resource object and calling a terraform command line. The vm-oOperator tool is composed of VirtailMachine-Controller (vm-Controller for short), vm-CRD + Provider-CRD and vmc-api components.
kubernets Operator: is a framework introduced by CoreOS aimed at simplifying complex stateful application management, which is an application state-aware controller that automatically creates, manages, and configures application instances by extending the kubernets API.
CRD: user-defined resource types in kubernets:
Virtailmachine-CRD: the declaration defines metadata for the VirtaulMachine virtual machine. Mainly comprises related information such as virtual machine configuration and the like. Besides, some auxiliary metadata resource models exist, such as the Provider is relevant information of the cloud platform.
Virtailmachine-Controller (vm-Controller for short): by using a mechanism of a kubernets Controller, coordination logic (mainly operations related to creation, deletion and updating of a virtual machine or a virtual machine group) is triggered by monitoring the state of a resource object such as vm-CRD or vmStateful (CRD), and different operation steps are driven by interface calls of vmc-api.
vmc-api: and a back-end service for providing an api interface, wherein the component encapsulates a command line tool of terraform to manage the life cycle of the virtual machine, and the main value is to provide an asynchronous interface as a vm-controller service.
vmstateful (crd): metadata of a stateful virtual machine group is defined declaratively, the metadata mainly comprises host name rules, management ip, specifications and the like of a group of virtual machines, regular virtual machine attributes can be customized, and virtual machines in the group are different.
vmstatesless (crd): metadata of a stateless virtual machine set is defined declaratively, the metadata mainly comprises basic attributes such as number and specification, no personalized requirements exist, and virtual machines in the set are not different.
The example of managing a single virtual machine is as follows:
with reference to fig. 2, creating a resource object of a VirtualMachine (vm for short), may trigger the following process of creating a virtual machine:
101. creating resource objects
apiVersion:infra.x.com/v1alpha1
kind:vm
metadata:
name:example-vm
spec:
#Add fields here
providerNam:OpenStack
...
apiVersion:infra.x.com/v1alpha1
kind:Provider
metadata:
name:OpenStack
spec:
#Add fields here
auth_url:http://10.1.10.4:8090/
...
102. The vm-controller monitors the newly added object of vm, starts a virtual machine creating process and calls vmc-api virtual machine creating interfaces;
103: vmc-api receives the request of creating virtual machine to check the parameter, then returns the response, and starts a task execution shell command in the background to call the terraform command line to create the virtual machine; after the execution is finished, analyzing the log result and reversely notifying the vm-controller by refreshing the state of the corresponding vm-CRD resource
104. After monitoring that the state of the vm resource object changes, if the vm resource object is application _ success, the vm controller task successfully establishes a terraform command line of the virtual machine, and then calls a monitoring virtual machine interface of vmc-api;
105. vmc-api will add the virtual machine into the monitoring queue, detect once every a period of time whether the ssh of the virtual machine is available, if so, refresh the vm state to running;
106. the vm-controller monitors that the virtual machine state becomes running, i.e. the created virtual machine is considered to be available.
Deleting the vm resource object can trigger the virtual machine deleting process shown in fig. 3.
Updating the resource object of vm can trigger the process of fig. 4 for updating the virtual machine.
With reference to fig. 5, the arrangement and management of virtual machine resources can be divided into a stateful virtual machine group and a stateless virtual machine group according to different purposes, and the resource object concept in kubernets is referred to. The notion of stateful and stateless pod collections is managed similarly to in kubernets. Similar to the management of a single virtual machine, the vm-controller drives the creation, deletion, etc. of batches of virtual machines by monitoring the state of the virtual machine group resource objects.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that changes, modifications, substitutions and alterations can be made in these embodiments without departing from the principles and spirit of the invention, the scope of which is defined in the appended claims and their equivalents.

Claims (8)

1. A method for managing a virtual machine life cycle based on kubernets acoustic arrangement is characterized in that a VirtualmetaOpera tool is realized based on an open-source Operator technical framework in kubernets, and the VirtualmetaOpera tool realizes automatic management of a virtual machine in a mode of monitoring resource object states and calling a terraform command line.
2. The method for managing the life cycle of a virtual machine based on kubernets declarative organization of claim 1, wherein the VirtualMetaOperator tool is composed of vm-Controller + vm-CRD + Provider-CRD and vmc-api components.
3. The method of claim 2, wherein the open-source Operator in the kubernets: the method is a controller for sensing the application state, and automatically creates, manages and configures the application instance by extending the kubernets API.
4. The method of claim 2, wherein the CRD: the resource type is customized by the user in kubernets;
Virtailmachine-CRD: declaratively defining metadata of the Virtailmachine virtual machine, including virtual machine configuration related information;
the Provider-CRD declarative type defines a Virtailmachine-assisted metadata resource model containing relevant information of a cloud platform.
5. The method for managing a lifecycle of a virtual machine based on kubernets declarative orchestration according to claim 2, wherein the virtaulm machine-Controller: the mechanism of kubernets controllers is utilized, the coordination logic is triggered by monitoring the state of vm-CRD or vmStateful-CRD resource objects, and different operation steps are driven through interface calls of vmc-api.
6. The method of claim 5, wherein the triggering coordination logic comprises creating, deleting, updating a virtual machine or a virtual machine group-related operation.
7. The method of claim 2, wherein the vmc-api: and a back-end service for providing an api interface, wherein the component encapsulates a command line tool of terraform to manage the life cycle of the virtual machine and is used for providing an asynchronous interface for a vm-controller service.
8. The method of claim 6, wherein the creation of vm resource objects is performed by the following steps:
101. creating resource objects
apiVersion:infra.x.com/v1alpha1
kind:vm
metadata:
name:example-vm
spec:
#Add fields here
providerNam:OpenStack
...
apiVersion:infra.x.com/v1alpha1
kind:Provider
metadata:
name:OpenStack
spec:
#Add fields here
auth_url:http://10.1.10.4:8090/
...
102. The vm-controller monitors the newly added object of vm, starts a virtual machine creating process and calls vmc-api virtual machine creating interfaces;
3: vmc-api receives the request of creating virtual machine to check the parameter, then returns the response, and starts a task execution shell command in the background to call the terraform command line to create the virtual machine; after the execution is finished, analyzing the log result and reversely notifying the vm-controller by refreshing the state of the corresponding vm-CRD resource
104. After monitoring that the state of the vm resource object changes, if the vm resource object is application _ success, the vm controller task successfully establishes a terraform command line of the virtual machine, and then calls a monitoring virtual machine interface of vmc-api;
105. vmc-api will add the virtual machine into the monitoring queue, detect once every a period of time whether the ssh of the virtual machine is available, if so, refresh the vm state to running;
106. the vm-controller monitors that the virtual machine state becomes running, i.e. the created virtual machine is considered to be available.
CN202010857674.9A 2020-08-24 2020-08-24 Method for declaratively arranging and managing virtual machine life cycle based on kubernets Active CN112000441B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010857674.9A CN112000441B (en) 2020-08-24 2020-08-24 Method for declaratively arranging and managing virtual machine life cycle based on kubernets

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010857674.9A CN112000441B (en) 2020-08-24 2020-08-24 Method for declaratively arranging and managing virtual machine life cycle based on kubernets

Publications (2)

Publication Number Publication Date
CN112000441A true CN112000441A (en) 2020-11-27
CN112000441B CN112000441B (en) 2023-01-20

Family

ID=73470271

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010857674.9A Active CN112000441B (en) 2020-08-24 2020-08-24 Method for declaratively arranging and managing virtual machine life cycle based on kubernets

Country Status (1)

Country Link
CN (1) CN112000441B (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112506621A (en) * 2020-12-29 2021-03-16 浪潮云信息技术股份公司 Method and system for realizing containerization management of virtual machine life cycle
CN113296809A (en) * 2021-05-21 2021-08-24 南京大学 Declarative universal Kubernetes tuning method
CN115001990A (en) * 2022-05-25 2022-09-02 济南浪潮数据技术有限公司 Cross-region openstack cluster management method and system based on declarative API
US11550566B2 (en) 2021-02-09 2023-01-10 Red Hat, Inc. Automatically integrating software components into a control framework in a distributed computing environment
WO2023072042A1 (en) * 2021-10-26 2023-05-04 International Business Machines Corporation Event-driven provisioning of elastic orchestration platform
US11693649B2 (en) 2021-04-06 2023-07-04 International Business Machines Corporation Autonomous Kubernetes operator creation and management

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017107483A1 (en) * 2015-12-23 2017-06-29 中兴通讯股份有限公司 Load balancing method for virtualized network management file downloading, and network management server
CN107947961A (en) * 2017-10-17 2018-04-20 上海数讯信息技术有限公司 Kubernetes Network Management System and method based on SDN
CN110244964A (en) * 2019-05-28 2019-09-17 阿里巴巴集团控股有限公司 It is a kind of based on O&M application O&M method, O&M method, device and equipment
CN110750333A (en) * 2019-10-25 2020-02-04 浪潮云信息技术有限公司 Full life cycle management method for cloud service factory platform
CN110851145A (en) * 2019-09-30 2020-02-28 烽火通信科技股份有限公司 Edge cloud installation and maintenance method and system based on container arrangement
US20200076685A1 (en) * 2018-08-30 2020-03-05 Juniper Networks, Inc. Multiple networks for virtual execution elements
CN111049876A (en) * 2019-10-18 2020-04-21 烽火通信科技股份有限公司 Lightweight telecom cloud edge computing system architecture
EP3683675A1 (en) * 2019-01-18 2020-07-22 Siemens Aktiengesellschaft System, apparatus and method of integrated deployment

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017107483A1 (en) * 2015-12-23 2017-06-29 中兴通讯股份有限公司 Load balancing method for virtualized network management file downloading, and network management server
CN107947961A (en) * 2017-10-17 2018-04-20 上海数讯信息技术有限公司 Kubernetes Network Management System and method based on SDN
US20200076685A1 (en) * 2018-08-30 2020-03-05 Juniper Networks, Inc. Multiple networks for virtual execution elements
EP3683675A1 (en) * 2019-01-18 2020-07-22 Siemens Aktiengesellschaft System, apparatus and method of integrated deployment
CN110244964A (en) * 2019-05-28 2019-09-17 阿里巴巴集团控股有限公司 It is a kind of based on O&M application O&M method, O&M method, device and equipment
CN110851145A (en) * 2019-09-30 2020-02-28 烽火通信科技股份有限公司 Edge cloud installation and maintenance method and system based on container arrangement
CN111049876A (en) * 2019-10-18 2020-04-21 烽火通信科技股份有限公司 Lightweight telecom cloud edge computing system architecture
CN110750333A (en) * 2019-10-25 2020-02-04 浪潮云信息技术有限公司 Full life cycle management method for cloud service factory platform

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
MICHAL ORZECHOWSKI ET.AL: "Transparent Deployment of Scientific Workflows across Clouds-Kubernetes Approach", 《2018 IEEE/ACM INTERNATIONAL CONFERENCE ON UTILITY AND CLOUD COMPUTING COMPANION (UCC COMPANION)》 *
单朋荣 等: "基于Kubernetes云平台的弹性伸缩方案设计与实现", 《计算机工程》 *
文婷婷等: "基于OpenStack虚拟化网络管理平台的设计与实现", 《电子制作》 *
谭飞等: "虚机容器统一编排管理解决方案", 《装备维修技术》 *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112506621A (en) * 2020-12-29 2021-03-16 浪潮云信息技术股份公司 Method and system for realizing containerization management of virtual machine life cycle
US11550566B2 (en) 2021-02-09 2023-01-10 Red Hat, Inc. Automatically integrating software components into a control framework in a distributed computing environment
US11693649B2 (en) 2021-04-06 2023-07-04 International Business Machines Corporation Autonomous Kubernetes operator creation and management
CN113296809A (en) * 2021-05-21 2021-08-24 南京大学 Declarative universal Kubernetes tuning method
CN113296809B (en) * 2021-05-21 2023-12-12 南京大学 Declarative general Kubernetes tuning method
WO2023072042A1 (en) * 2021-10-26 2023-05-04 International Business Machines Corporation Event-driven provisioning of elastic orchestration platform
CN115001990A (en) * 2022-05-25 2022-09-02 济南浪潮数据技术有限公司 Cross-region openstack cluster management method and system based on declarative API

Also Published As

Publication number Publication date
CN112000441B (en) 2023-01-20

Similar Documents

Publication Publication Date Title
CN112000441B (en) Method for declaratively arranging and managing virtual machine life cycle based on kubernets
CN103051710B (en) A kind of virtual cloud platform management system
CN107431696B (en) Method and cloud management node for application automation deployment
CN102681899B (en) Virtual computing resource dynamic management system of cloud computing service platform
CN106484394B (en) A kind of fast software development system with double engines
US10575121B2 (en) System and method for instantiation of services at a location based on a policy
CN101271401B (en) Server cluster unit system with single system image
CN103955373B (en) A kind of method for designing of SDN application integration development environment
CN102609295A (en) Dynamic operation scheduling system of virtual machine
WO2009082384A1 (en) Modelling computer based business process and simulating operation
CN102375731A (en) Coding-free integrated application platform system
CN103092670A (en) Cross-platform virtual computing resource management method under cloud computing environment
WO2009082381A1 (en) Incorporating development tools in system for deploying computer based process on shared infrastructure
CN110362363B (en) Method for realizing terminal application control based on runtime model
CN103729235A (en) Java virtual machine (JVM) and compiling method thereof
CN102254021A (en) Method for constructing database based on virtual machine management system
CN110362301B (en) Processing method for terminal application behavior reflection
CN104714823B (en) Newly-built main frame collocation method based on OpenStack
CN103383650A (en) Management method and system thereof
CN104731600A (en) Implementation method for Android system service plug-in
EP2530590A1 (en) Object pipeline-based virtual infrastructure management
CN110941503A (en) Fault processing method and device and electronic equipment
CN103257883A (en) Web based wireless sensing network remote stimulation system
CN105577807A (en) Cloud computing data resource scheduling WEB management platform
CN104516735B (en) Realize the two-dimentional layered approach of cloud computing environment automation O&M

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant