WO2020097814A1 - 一种容器编排引擎的安装方法、装置及电子设备 - Google Patents

一种容器编排引擎的安装方法、装置及电子设备 Download PDF

Info

Publication number
WO2020097814A1
WO2020097814A1 PCT/CN2018/115360 CN2018115360W WO2020097814A1 WO 2020097814 A1 WO2020097814 A1 WO 2020097814A1 CN 2018115360 W CN2018115360 W CN 2018115360W WO 2020097814 A1 WO2020097814 A1 WO 2020097814A1
Authority
WO
WIPO (PCT)
Prior art keywords
installation
target
cluster
version
target cluster
Prior art date
Application number
PCT/CN2018/115360
Other languages
English (en)
French (fr)
Inventor
张永苏
Original Assignee
深圳市互盟科技股份有限公司
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 深圳市互盟科技股份有限公司 filed Critical 深圳市互盟科技股份有限公司
Priority to PCT/CN2018/115360 priority Critical patent/WO2020097814A1/zh
Publication of WO2020097814A1 publication Critical patent/WO2020097814A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements 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/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines

Definitions

  • the present invention relates to the field of software development, and more specifically, to a method, device and electronic device for installing a container orchestration engine.
  • the application container engine (Docker) has suddenly risen in recent years and has become hot. It has become the de facto standard for container technology.
  • container orchestration technology the key to successful deployment and operation of containers in a build environment.
  • the final container orchestration engine (Kubernetes, K8S) stands out as the most popular container orchestration tool; the Kubernetes architecture is very complex and the components are very flexible. For beginners or start-ups If you want to get started, the first problem you face is the complicated installation and deployment, which makes it more difficult for beginners to get started.
  • the purpose of the present invention is to provide a method and device for installing a container orchestration engine and electronic equipment in view of the defects in the prior art, which solves the problem of complicated installation and deployment.
  • a method for installing a container orchestration engine includes:
  • the target cluster type includes at least one of a federal cluster, a high-availability cluster, and an ordinary cluster;
  • the initialization of the installation environment to configure the target installation environment required by the target cluster type includes:
  • selecting the version of the target cluster for installation includes:
  • the availability check includes a health check
  • the performing an availability check on the installed target cluster, and upgrading or completing the installation on the installed target cluster according to the availability check includes:
  • the upgrade of the target cluster version after installation or output of success information according to the check result includes:
  • a device for installing a container orchestration engine includes:
  • the type selection module is used to select a target cluster type for installation, and the target cluster type includes at least one of a federal cluster, a high-availability cluster, and an ordinary cluster;
  • An initialization module configured to initialize the installation environment to configure the target installation environment required by the target cluster type
  • a version installation module used to select the version of the target cluster for installation in the target installation environment
  • the checking module is used to check the availability of the installed target cluster, and upgrade or complete the installation of the installed target cluster according to the availability check.
  • the initialization module includes:
  • Cleaning unit used to clean the installation environment to remove residual files
  • Configuration unit used to configure the cleaned-up installation environment
  • the preparation unit is used to prepare the corresponding installation package of the target cluster type to obtain the target installation environment.
  • the version installation module includes:
  • a version selection unit used to actively or by default select the version of the target cluster to be installed in the target installation environment
  • An installation subunit configured to distribute the installation files in the corresponding installation package of the version of the target cluster to the target installation environment, and install and deploy the target cluster.
  • an embodiment of the present invention provides an electronic device, including: a memory, a processor, and a computer program stored on the memory and executable on the processor. The steps in the installation of the container orchestration engine provided by the embodiments of the present invention are implemented.
  • an embodiment of the present invention provides a computer-readable storage medium having a computer program stored on the computer-readable storage medium. Steps in installation.
  • the beneficial effects brought by the present invention select a target cluster type for installation, the target cluster type includes at least one of a federal cluster, a high-availability cluster, and an ordinary cluster; initialize the installation environment to configure the target cluster type required The target installation environment; in the target installation environment, select the version of the target cluster for installation; perform an availability check on the installed target cluster, and upgrade the installed target cluster according to the availability check or Complete the installation, so as to automatically complete the installation or upgrade of the container orchestration engine, greatly reducing the threshold for beginners or start-up companies.
  • FIG. 1 is a schematic flowchart of a method according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of another method according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a device module according to an embodiment of the invention.
  • FIG. 4 is a schematic diagram of another device module according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of another device module according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of another device module according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of another device module according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of another device module according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of electronic settings according to an embodiment of the present invention.
  • the invention provides a method, device and electronic equipment for installing a container orchestration engine.
  • a method for installing a container orchestration engine may be integrated into a system or a product platform, and the container orchestration may be implemented through the system or the product platform
  • the engine installation method is to automatically install and deploy the container orchestration engine.
  • the system or the product platform may include installation packages or download paths of various types and versions of the container orchestration engine.
  • the product platform can also include a mirror download path.
  • the method includes steps:
  • the target cluster type includes at least one of a federation cluster (Federation Cluster), a high availability cluster (High Availability Cluster, abbreviated as HA Cluster), and an ordinary cluster (Cluster).
  • a federation cluster Federation Cluster
  • High Availability Cluster High Availability Cluster
  • Cluster an ordinary cluster
  • the federation cluster can realize multi-cluster management and scheduling. Further, the federation cluster can be deployed redundantly across clusters. When a certain cluster is in a fault area, the entire service is not affected. The federation cluster can also detect whether the cluster is in an unavailable state in the cluster federation, and if a certain cluster is found to be in an unavailable state, the failed task can be redistributed to other clusters in the available state in the cluster federation.
  • the high-availability cluster can realize the high availability of the cluster.
  • the high-availability cluster refers to the server cluster technology for the purpose of reducing service interruption time. It protects the user's business program from providing services to the outside world continuously. The impact of the resulting failure on the business is reduced to a minimum. When the user chooses to deploy a certain type of cluster and enter the corresponding configuration, the method or system will record the corresponding information.
  • the three cluster modes of the federal cluster, high-availability cluster, and ordinary cluster can be deployed according to the user's usage scenario, and the user can choose the usage scenario by himself, through the system or product integrating the installation method of the container orchestration engine
  • the platform matches this usage scenario and selects the type of target cluster for installation and deployment.
  • the user can also choose the type of target cluster for installation and deployment.
  • it can also be automatically detected by the system or product platform that integrates the installation method of the container orchestration engine. For example, according to the user ’s software requirements and usage habits, the user can be scored and the user can be scored based on this score Automatically select usage scenarios, so recommend or default a cluster module for deployment.
  • Initialization is to assign variables to default values, set controls to default state, and prepare unprepared, when the startup environment is initialized, according to the target cluster type, the system that integrates the installation method of the container orchestration engine Or the product platform will be connected to the environment that needs to be initialized.
  • Execution environment cleaning includes: uninstalling the previous version, clearing related file information, etc.
  • environment preparation includes: operating system kernel (kernel) check, application container engine environment installation, host name specification, Time synchronization, firewall settings, etc., to get the target installation environment.
  • kernel kernel
  • the target installation environment corresponds to one of the three cluster modes of the federal cluster, high availability cluster, and ordinary cluster, and the initialization of the target installation environment depends on the three cluster modes of the federal cluster, high availability cluster, and ordinary cluster In which cluster mode is the target cluster.
  • the version selection of the target cluster can be selected by the user to allow the user to install Is the target cluster version specified by the user, for example, some users prefer the old version, they can specify the old version as the installation version, of course, the target cluster version selection can also be integrated by the container orchestration
  • the system or product platform of the engine installation method is automatically selected, and the automatic selection may be selected according to the new or old version of the target cluster or the stability, or may be selected according to the installation volume of each version of the target cluster, for example, the federal cluster
  • One of the installed versions has the largest number of installers, which can be used to show that this version is highly liked by users. You can automatically select this version of the federal cluster for installation.
  • S104 Perform an availability check on the installed target cluster, and upgrade or complete the installation on the installed target cluster according to the availability check.
  • the availability check includes whether the components in the cluster are ready, whether the application programming interface (API) of the cluster is normal, and the hypertext transfer protocol / Whether the Secure Socket Layer Hypertext Transfer Protocol (http / https) can be accessed normally, and finally will be tested for high availability cluster switching, cluster application deployment, and federal cluster scheduling.
  • API application programming interface
  • the method for installing a container orchestration engine provided by an embodiment of the present invention can be applied to installation equipment for a container orchestration engine, such as computers, servers, mobile phones, and other devices that can install a container orchestration engine.
  • a target cluster type is selected for installation, and the target cluster type includes at least one of a federal cluster, a high-availability cluster, and an ordinary cluster; the installation environment is initialized to configure the target required by the target cluster type Installation environment; in the target installation environment, select the version of the target cluster for installation; perform an availability check on the installed target cluster, and upgrade or complete the installed target cluster according to the availability check Installation, so as to automatically complete the installation or upgrade of the container orchestration engine, greatly reducing the threshold for beginners or start-up companies.
  • the initialization of the installation environment to configure the target installation environment required by the target cluster type includes:
  • the container orchestration engine For some devices that have previously installed the container orchestration engine, they need to be cleaned up. Such a cleanup can either uninstall the current version or check and clean up the remaining files after uninstallation. In addition. Configure the cleaned-up installation environment, including configuring the operating system and virtual machine, and configuring the virtual machine's address, node, and network support.
  • the operating system may be a community enterprise operating system (Community Enterprise Operating System, CentOS for short).
  • CentOS Common Enterprise Operating System
  • the target cluster After the target cluster is determined, it can be downloaded through a built-in link, or each version of the cluster can be configured in the installation method integrating the container orchestration engine
  • the system or product platform that integrates the installation method of the container orchestration engine may periodically check the version of the cluster, and check out the latest version for configuration.
  • selecting the version of the target cluster for installation in the target installation environment includes:
  • the version of the target cluster that needs to be installed by default may be the latest version, the most stable version, or the latest stable version, and the latest stable version may be the most stable among the updated versions
  • the version can also be the latest version in the stable version.
  • the availability check includes a health check
  • the performing an availability check on the installed target cluster, and upgrading or completing the installation on the installed target cluster according to the availability check includes:
  • the health check includes whether the various components in the cluster are ready, whether the cluster application programming interface is normal, whether the hypertext transfer protocol / secure socket layer hypertext transfer protocol can be accessed normally, etc. Finally, the high availability cluster switch will be initiated , Cluster application deployment, federal cluster scheduling and other tests. In the tests of corresponding high-availability cluster switching, cluster application deployment, and federal cluster scheduling, the nodes between the clusters can also be checked to see whether the nodes are completely available. In checking whether the Hypertext Transfer Protocol / Secure Socket Layer Hypertext Transfer Protocol can be accessed normally, it is mainly to check the cluster network.
  • the upgrade of the target cluster version after installation or output of success information according to the check result includes:
  • the user may choose to install at a lower version.
  • the system or product platform that integrates the installation method of the container orchestration engine may detect that the target cluster is a non-default version After the non-recommended version, the user is prompted whether to upgrade the version.
  • the environment will be cleaned up or the initialization of the installation environment will be restarted.
  • the installation environment will be cleaned again. After the cleaning is completed, it will enter the version selection again. After that, you can choose a higher version for reinstallation and deployment.
  • the system or product platform that integrates the installation method of the container orchestration engine detects that the target cluster is a non-default version or a non-recommended version, it may not upgrade by default.
  • the output success information includes the type of cluster, component, server, API, access address, etc. These information can be Help users to know the situation of the target cluster after the installation, as a kind of installation feedback, the installation feedback can also feedback the files cleaned up during the installation environment initialization during the installation process, and can also feedback during the installation process
  • the selection method of the target cluster version is displayed as manual selection or default selection, for example.
  • the method before the selection of the target cluster type for installation, the method further includes:
  • multiple cluster modes are deployed on the system or platform on which the container orchestration engine is automatically installed.
  • the system or product platform When the user chooses to deploy a certain type of cluster and enters the corresponding configuration, the system or product platform will record the corresponding information and start the corresponding environment initialization operation.
  • users who have appeared in the above embodiments may also be referred to as users or users.
  • platform deployment According to the user's usage scenario, three cluster modes are available: federated cluster, high-availability cluster, and ordinary cluster.
  • the federated cluster implements multi-cluster management and scheduling. Available clusters achieve high availability of clusters.
  • the method or system When users choose to deploy a certain type of cluster and enter the corresponding configuration, the method or system will record the corresponding information and start the corresponding environment initialization operation.
  • Initialize the environment When the startup environment is initialized, the method or system will connect to the environment that needs to be initialized, perform environment cleanup (uninstall the previous version, clear related file information, etc.) and environment preparation (kernel check, docker environment installation, host name specification , Time synchronization, firewall settings, etc.).
  • the cluster version After the environment is initialized, the cluster version will be selected. The default is the latest stable version. The cluster version can also be upgraded in the version management module. The selected version includes the user-specified version and the automatic default version.
  • Installation After the cluster installation version is determined, this method or system will distribute the corresponding installation files to the initialization environment and perform cluster installation and deployment.
  • Availability check After the installation and deployment of the cluster is completed, the corresponding availability check will be started according to the type of the cluster, including the health status of the cluster, whether the various components in the cluster are ready, whether the cluster API is normal, and whether http / https can be accessed normally. Tests such as high availability cluster switching, cluster application deployment, and federal cluster scheduling will be initiated.
  • Version upgrade The user may choose to install a lower version when installing.
  • a prompt will be issued to whether the version is upgraded (the default is not to upgrade). After the upgrade is selected, the environment cleanup will be started and the cleanup is completed. After that, you will enter the version management link again, and then you can choose a higher version to reinstall and deploy. Completion: At this point, the automatic deployment of the entire Kubernetes is completed, and a success message will be output, which includes the cluster type, components, server, API, access address, etc.
  • the installation method of the container orchestration engine provided by the present invention improves the efficiency of the installation and deployment of the entire Kubernetes cluster, and avoids unknown errors in the manual installation and deployment process; this method standardizes and fully automates the installation of Kubernetes, not only improves the current Kubernetes manual Or the lack of semi-automated installation and deployment has reduced the cost of entry and learning for beginners or start-up companies, and has taken the first step for enterprise containerization, microservices, and DevOps.
  • a device for installing a container orchestration engine includes:
  • the type selection module 31 is used to select a target cluster type for installation, and the target cluster type includes at least one of a federal cluster, a high-availability cluster, and an ordinary cluster;
  • An initialization module 32 configured to initialize the installation environment to configure the target installation environment required by the target cluster type
  • the version installation module 33 is configured to select a version of the target cluster to install in the target installation environment
  • the checking module 34 is configured to check the availability of the target cluster after installation, and upgrade or complete the installation of the target cluster according to the availability check.
  • the initialization module 32 includes:
  • the cleaning unit 321 is used for cleaning the installation environment to remove residual files
  • the configuration unit 322 is used to configure the cleaned-up installation environment
  • the preparing unit 323 is configured to prepare corresponding installation packages of the target cluster type to obtain the target installation environment.
  • the version installation module 33 includes:
  • the version selection unit 331 is used to actively or by default select the version of the target cluster to be installed in the target installation environment;
  • the installation unit 332 is configured to distribute the installation file in the corresponding installation package of the version of the target cluster to the target installation environment, and install and deploy the target cluster.
  • the availability check includes a health check
  • the inspection module 34 includes:
  • the checking unit 341 is used to check the health status of the target cluster after installation to obtain the check result
  • the selection unit 342 is configured to upgrade the version of the installed target cluster or output success information according to the check result.
  • the selection unit 342 includes:
  • the upgrade subunit 3421 is used to clean up the installation environment to upgrade the target cluster after the installation to obtain the target upgrade environment;
  • the output subunit 3423 is configured to output success information to the target cluster after installation if the version upgrade of the target cluster after installation is not performed, obtain an installation result, and complete the installation.
  • the device further includes:
  • the deployment module 30 is configured to deploy multiple cluster modes on the system or platform on which the container orchestration engine is automatically installed according to user usage scenarios.
  • the apparatus for analyzing social relationships of persons provided in the embodiments of the present invention can implement various implementation methods in the method embodiments of FIG. 1 and FIG. 2 and corresponding beneficial effects. To avoid repetition, details are not described herein again.
  • the apparatus for container orchestration engines provided in the embodiments of the present invention can be applied to installation equipment for container orchestration engines, such as computers, servers, mobile phones, and other devices that can be used to install container orchestration engines.
  • an embodiment of the present invention provides an electronic device, including: a memory 401, a processor 402, and a computer program stored on the memory and executable on the processor, the When the processor executes the computer program, the steps in the installation of the container orchestration engine provided by the embodiment of the present invention are implemented.
  • an embodiment of the present invention provides a computer-readable storage medium storing a computer program on the computer-readable storage medium, which when executed by a processor implements a container orchestration engine provided by an embodiment of the present invention Steps in installation.
  • processors and chips in the embodiments of the present invention may be integrated into one processing unit, or may exist alone physically, or two or more hardwares may be integrated into one unit.
  • the computer-readable storage medium or computer-readable program may be stored in a computer-readable memory.
  • the technical solution of the present invention essentially or part of the contribution to the existing technology or all or part of the technical solution can be embodied in the form of a software product, the computer software product is stored in a memory, Several instructions are included to enable a computer device (which may be a personal computer, server, network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present invention.
  • the aforementioned memory includes: U disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.
  • the program may be stored in a computer-readable memory, and the memory may include: a flash disk , Read-only memory (English: Read-Only Memory, abbreviation: ROM), random access device (English: Random Access Memory, abbreviation: RAM), magnetic disk or optical disk, etc.

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

本发明公布了提供一种容器编排引擎的安装方法、装置及电子设备，所述方法包括：选择目标集群类型进行安装，所述目标集群类型包括联邦集群、高可用集群、普通集群中至少一个；对安装环境进行初始化以配置出所述目标集群类型所需要的目标安装环境；在所述目标安装环境中，选择所述目标集群的版本进行安装；对所述安装后的目标集群进行可用性检查，根据所述可用性检查对所述安装后的目标集群进行升级或完成安装。本发明可以自动化完成容器编排引擎的安装或升级，大大降低了初学者或初创企业的使用门槛。

Description

一种容器编排引擎的安装方法、装置及电子设备 技术领域
本发明涉及软件开发领域，更具体的说，是涉及一种容器编排引擎的安装方法、装置及电子设备。
背景技术
随着容器技术的发展，应用容器引擎(Docker)近几年突然崛起，变得炙手可热，已经成为容器技术的事实标准，然而想要在生成环境中成功部署和操作容器的关键是容器编排技术，经过市场多年实践的淬炼，最终容器编排引擎(Kubernetes，简称：K8S)脱颖而出，成为最受欢迎的容器编排工具；Kubernetes架构非常复杂，组件也十分灵活，对于初学者或是初创型企业而言想要入门，首先面临的就是安装部署复杂的问题，加大了初学者入门的难度。
发明内容
本发明的目的是针对上述现有技术存在的缺陷，提供一种容器编排引擎的安装方法、装置及电子设备，解决了安装部署复杂的问题。
本发明的目的是通过以下技术方案来实现的：
第一方面，提供一种容器编排引擎的安装方法，所述方法包括：
选择目标集群类型进行安装，所述目标集群类型包括联邦集群、高可用集群、普通集群中至少一个；
对安装环境进行初始化以配置出所述目标集群类型所需要的目标安装环境；
在所述目标安装环境中，选择所述目标集群的版本进行安装；
对所述安装后的目标集群进行可用性检查，根据所述可用性检查对所述安装后的目标集群进行升级或完成安装。
优选的，所述对安装环境进行初始化以配置出所述目标集群类型所需要的目标安装环境包括：
对安装环境进行清理，以清除残留文件；
对清理后的安装环境进行配置；
对所述目标集群类型的对应安装包进行准备，得到所述目标安装环境。
优选的，所述在所述目标安装环境中，选择所述目标集群的版本进行安装包括：
在所述目标安装环境中，主动选择或默认选择需要安装的所述目标集群的版本；
将所述目标集群的版本的所述对应安装包中的安装文件分发到所述目标安装环境中，对所述目标集群进行安装部署。
优选的，所述可用性检查包括健康状况检查；
所述对所述安装后的目标集群进行可用性检查，根据所述可用性检查对所述安装后的目标集群进行升级或完成安装包括：
对所述安装后的目标集群进行健康状况检查，得到检查结果；
根据所述检查结果对所述安装后的目标集群进行版本升级或输出成功信息。
优选的，所述根据所述检查结果进行所述安装后的目标集群版本升级或输出成功信息包括：
若对所述安装后的目标集群进行版本升级，则对安装环境进行清理，得到目标升级环境；
在所述目标升级环境中，选择所述目标集群的版本进行升级；
若若不对所述安装后的目标集群进行版本升级，则对所述安装后的目标集群进行输出成功信息，得到安装结果，完成安装。
第二方面，提供一种容器编排引擎的安装装置，所述装置包括：
类型选择模块，用于选择目标集群类型进行安装，所述目标集群类型包括联邦集群、高可用集群、普通集群中至少一个；
初始化模块，用于对安装环境进行初始化以配置出所述目标集群类型所需要的目标安装环境；
版本安装模块，用于在所述目标安装环境中，选择所述目标集群的版本进行安装；
检查模块，用于对所述安装后的目标集群进行可用性检查，根据所述可用性检查对所述安装后的目标集群进行升级或完成安装。
优选的，所述初始化模块包括：
清理单元，用于对安装环境进行清理，以清除残留文件；
配置单元，用于对清理后的安装环境进行配置；
准备单元，用于对所述目标集群类型的对应安装包进行准备，得到所述目标安装环境。
优选的，所述版本安装模块包括：
版本选择单元，用于在所述目标安装环境中，主动选择或默认选择需要安装的所述目标集群的版本；
安装子单元，用于将所述目标集群的版本的所述对应安装包中的安装文件分发到所述目标安装环境中，对所述目标集群进行安装部署。
第三方面，本发明实施例提供一种电子设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现本发明实施例提供的容器编排引擎的安装中的步骤。
第四方面，本发明实施例提供一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现本发明实施例提供的容器编排引擎的安装中的步骤。
本发明带来的有益效果：选择目标集群类型进行安装，所述目标集群类型包括联邦集群、高可用集群、普通集群中至少一个；对安装环境进行初始化以配置出所述目标集群类型所需要的目标安装环境；在所述目标安装环境中，选择所述目标集群的版本进行安装；对所述安装后的目标集群进行可用性检查，根据所述可用性检查对所述安装后的目标集群进行升级或完成安装，从而自动化完成容器编排引擎的安装或升级，大大降低了初学者或初创企业的使用门槛。
附图说明
图1为本发明实施例的方法流程示意图；
图2为本发明实施例的另一种方法流程示意图；
图3为本发明实施例的一种装置模块示意图；
图4为本发明实施例的另一种装置模块示意图；
图5为本发明实施例的另一种装置模块示意图；
图6为本发明实施例的另一种装置模块示意图；
图7为本发明实施例的另一种装置模块示意图；
图8为本发明实施例的另一种装置模块示意图；
图9为本发明实施例的电子设置示意图。
具体实施方式
下面描述本发明的优选实施方式，本领域普通技术人员将能够根据下文所述用本领域的相关技术加以实现，并能更加明白本发明的创新之处和带来的益处。
本发明提供了一种容器编排引擎的安装方法、装置及电子设备。
本发明的目的是通过以下技术方案来实现的：
第一方面，提供一种容器编排引擎的安装方法，所述容器编排引擎的安装方法可以集成在一个系统中或是一个产品平台上，通过该系统或是该产品平台，可以实现所述容器编排引擎的安装方法以将所述容器编排引擎进行自动化安装和部署，该系统中或是该产品平台上可以包括所述容器编排引擎的各类型和版本的安装包或下载路径，该系统中或是该产品平台上还可以包括镜像下载路径。
所如图1所示，述方法包括步骤：
S101、选择目标集群类型进行安装，所述目标集群类型包括联邦集群(Federation Cluster)、高可用集群(High Availability Cluster，简称HA Cluster)、普通集群(Cluster)中至少一个。
其中，所述联邦集群可以实现多集群的管理与调度，进一步的，所述联邦集群可以跨集群冗余部署，当某个集群所在区域出现故障时，并不影响整个服务。所述联邦集群在集群联邦中还可以检测集群是否为不可用状态，如果发现某个集群为不可用状态时，可以将失败的任务重新分配给集群联邦中其他可用状态的集群上。所述高可用集群可以实现集群的高可用，高可用集群是指以减少服务中断时间为目的的服务器集群技术，它通过保护用户的业务程序对外不间断提供的服务，把因软件、硬件、人为造成的故障对业务的影响降低到最小程度。当使用者选择部署某种类型的集群并输入相应的配置后，该方法或系统会记录相应的信息。
对所述联邦集群、高可用集群、普通集群三种集群模式，可以根据用户的使用场景进行部署，用户可以自行选择使用场景，通过所述集成了所述容器编排引擎的安装方法的系统或产品平台对该使用场景进行匹配，选择目标集群的类型进行安装和部署，当然，在用户自行选择使用场景的前提下，用户也可以自行选择目标集群的类型进行安装和部署；另外，对于选择使用场景来说，也可以是由所述集成了所述容器编排引擎的安装方法的系统或产品平台自动检 测，比如，根据用户对软件的要求及使用习惯，可以对用户进行评分，根据这个评分为用户自动选择使用场景，从而推荐或默认一种集群模块进行部署。
S102、对安装环境进行初始化以配置出所述目标集群类型所需要的目标安装环境。
初始化就是把变量赋为默认值，把控件设为默认状态，把没准备的准备好，当启动环境初始化后，根据所述目标集群类型，所述集成了所述容器编排引擎的安装方法的系统或产品平台会连接到需要初始化的环境中，执行环境清理包括：卸载之前版本，清除相关文件信息等，以及环境准备包括：操作系统内核(kernel)检查、应用容器引擎环境安装、主机名规范、时间同步、防火墙设置等，得到目标安装环境。
所述目标安装环境对应于所述联邦集群、高可用集群、普通集群三种集群模式之一，所述目标安装环境的初始化，取决于所述联邦集群、高可用集群、普通集群三种集群模式中，哪种集群模式为目标集群。
S103、在所述目标安装环境中，选择所述目标集群的版本进行安装。
在所述联邦集群、高可用集群、普通集群三种集群模式中，可以为每种集群模式设置多个版本进行选择，对于所述目标集群的版本选择，可以让用户自行选择，从而使用户安装的是由用户指定的目标集群版本，比如，有的用户偏爱老版本，就可以指定老版本做为安装版本，当然，对所述目标集群的版本选择也可以由所述集成了所述容器编排引擎的安装方法的系统或产品平台进行自动选择，自动选择可以根据所述目标集群的版本新旧或稳定性进行选择，也可以根据所述目标集群的各个版本的安装量进行选择，比如，联邦集群的某一个安装版本的安装人数最多，可以借以说明这个版本受到用户的喜爱程度高，可以自动选择这个版本的联邦集群进行安装。
S104、对所述安装后的目标集群进行可用性检查，根据所述可用性检查对所述安装后的目标集群进行升级或完成安装。
集群安装部署完成后，会根据集群的类型启动相应的可用性检查，所述可用性检查包括集群中各个组件是否准备就绪，集群应用程序编程接口(Application Programming Interface,简称API)是否正常、超文本传输协议/安全套接字层超文本传输协议(http/https)能否正常访问等，最后会对应启动高可用集群切换、集群应用部署、联邦集群调度等测试。
需要说明的是，本发明实施例提供的容器编排引擎的安装方法可以应用于容器编排引擎的安装设备，例如：计算机、服务器、手机等可以进行容器编排 引擎安装的设备。
在本发明实施例中，选择目标集群类型进行安装，所述目标集群类型包括联邦集群、高可用集群、普通集群中至少一个；对安装环境进行初始化以配置出所述目标集群类型所需要的目标安装环境；在所述目标安装环境中，选择所述目标集群的版本进行安装；对所述安装后的目标集群进行可用性检查，根据所述可用性检查对所述安装后的目标集群进行升级或完成安装，从而自动化完成容器编排引擎的安装或升级，大大降低了初学者或初创企业的使用门槛。
可选的，在上述实施例中，所述对安装环境进行初始化以配置出所述目标集群类型所需要的目标安装环境包括：
对安装环境进行清理，以清除残留文件；
对清理后的安装环境进行配置；
对所述目标集群类型的对应安装包进行准备，得到所述目标安装环境。
对于一些之前已经安装过容器编排引擎的设备，需要对其进行清理，这样的清理可以是卸载当前版本，也可以是卸载后对残留文件进行检查和清理，另外。对清理后的安装环境进行配置，包括配置操作系统及虚拟机，并配置虚拟机的地址、节点及网络支持，所述操作系统可以是社区企业操作系统(Community Enterprise Operating System，简称：CentOS)。安装包可以从各个资源平台上进行获取，在确定所述目标集群后，可以通过内置的链接的进行下载，或者可以将所述集群各版本配置在所述集成了所述容器编排引擎的安装方法的系统或产品平台上，所述集成了所述容器编排引擎的安装方法的系统或产品平台可以定期对所述集群的版本进行检查，检查出最新版本进行配置。
优选的，在上述实施例中，所述在所述目标安装环境中，选择所述目标集群的版本进行安装包括：
在所述目标安装环境中，主动选择或默认选择需要安装的所述目标集群的版本；
将所述目标集群的版本的所述对应安装包中的安装文件分发到所述目标安装环境中，对所述目标集群进行安装部署。
其中，所述默认选择需要安装的所述目标集群的版本可以是最新版本，也可以是最稳定的版本，还可以是最新稳定版本，所述最新稳定版本可以是在更新的版本中最稳定的版本，也可以是在稳定的版本中最新的版本。在选择最新稳定版本时，可以通过评分进行确定是所述在更新的版本中最稳定的版本还是所述在稳定的版本中最新的版本，比如，可以对所述集群版本按新旧程度做一 个评分，对所述集群版本按稳定程度做另一个评分，将两个评分进行相加，选出最高或最低的所述集群版本做为默认的选择。
优选的，所述可用性检查包括健康状况检查；
所述对所述安装后的目标集群进行可用性检查，根据所述可用性检查对所述安装后的目标集群进行升级或完成安装包括：
对所述安装后的目标集群进行健康状况检查，得到检查结果；
根据所述检查结果对所述安装后的目标集群进行版本升级或输出成功信息。
所述健康状况检查包括集群中各个组件是否准备就绪，集群应用程序编程接口是否正常、超文本传输协议/安全套接字层超文本传输协议能否正常访问等，最后会对应启动高可用集群切换、集群应用部署、联邦集群调度等测试。在所述对应启动高可用集群切换、集群应用部署、联邦集群调度等测试中，还可以对集群之间的节点进行检查，看节点是否完整可用。在检查超文本传输协议/安全套接字层超文本传输协议能否正常访问中，主要是对集群的网络进行检查。
优选的，所述根据所述检查结果进行所述安装后的目标集群版本升级或输出成功信息包括：
若对所述安装后的目标集群进行版本升级，则对安装环境进行清理，得到目标升级环境；
在所述目标升级环境中，选择所述目标集群的版本进行升级；
若不对所述安装后的目标集群进行版本升级，则对所述安装后的目标集群进行输出成功信息，得到安装结果，完成安装。
用户在安装集群时的时候有可能会选择低版本进行安装，在可用性检查完成后，所述集成了所述容器编排引擎的安装方法的系统或产品平台会检测到所述目标集群为非默认版本或非推荐版本后，向用户发送是否升级版本的提示，当用户选升级后，会进行环境清理或重新启动对安装环境的初始化，再次对安装环境进行清理，清理完成后会再次进入到版本选择环节，之后可选择较高的版本进行重新安装部署。做为一种可能的实施方式，所述集成了所述容器编排引擎的安装方法的系统或产品平台会检测到所述目标集群为非默认版本或非推荐版本时，也可以默认不升级。
当不对所述安装后的目标集群进行版本升级，则对所述安装后的目标集群进行输出成功信息，所述输出成功信息包括集群的类型、组件、服务器、API、 访问地址等，这些信息可以帮助用户知道所述安装后的目标集群的情况，做为一种安装反馈，所述安装反馈还可以反馈在安装过程中对安装环境初始化时，清理掉的文件，也还可以反馈在安装过程中对所述目标集群版本的选择方式，比如显示为手动选择或是默认选择等等。
可选的，在上述实施例中，在所述选择目标集群类型进行安装之前，还包括：
按照用户的使用场景，在所述自动安装容器编排引擎的系统或平台部署多种集群模式。
当用户选择部署某种类型的集群并输入相应的配置后，所述系统或产品平台会记录相应的信息，并启动相应的环境初始化操作。
需要说明的是，上述实施例中出现过的用户，也可以称作使用者或使用人员等。
具体可选的，如图2所示，平台部署：按照用户的使用场景，提供三种集群模式可选：联邦集群、高可用集群、普通集群，其中联邦集群实现多集群的管理与调度，高可用集群实现集群的高可用，当使用者选择部署某种类型的集群并输入相应的配置后，该方法或系统会记录相应的信息，并启动相应的环境初始化操作。初始化环境：当启动环境初始化后，该方法或系统会连接到需要初始化的环境中，执行环境清理(卸载之前版本，清除相关文件信息等)和环境准备(kernel检查、docker环境安装、主机名规范、时间同步、防火墙设置等)。选择版本：环境初始化完成后，会进行集群版本的选择，默认为最新稳定版本，在版本管理模块中还可以进行集群版本的升级，选择版本包括用户指定版本及自动默认版本。安装：集群安装版本确定后，该方法或系统会将对应的安装文件分发到初始化环境中，并执行集群安装部署。可用性检查：集群安装部署完成后，会根据集群的类型启动相应的可用性检查，包括集群的健康状况检查，集群中各个组件是否准备就绪，集群API是否正常、http/https能否正常访问等，最后会启动高可用集群切换、集群应用部署、联邦集群调度等测试。版本升级：使用者在安装的时候有可能会选择低版本进行安装，在可用性检查完成后，会进行是否版本升级的提示(默认不升级)，当选升级后，会启动环境的清理工作，清理完成后会再次进入到版本管理环节，之后可选择较高的版本进行重新安装部署。完成：到这为止，完成了整个Kubernetes的自动部署，并会输出成功信息，信息包括集群的类型、组件、服务器、API、访问地址等。
本发明提供的容器编排引擎的安装方法，提高了整个Kubernetes集群安装 部署的效率，规避了人工在安装部署过程中的未知错误；本方法将Kubernetes安装标准化和全自动化，不仅仅完善了当前Kubernetes人工或半自动化安装部署的缺失，更是降低了初学者或初创企业入门学习的成本，为企业应用容器化、微服务化、DevOps等迈开第一步。
第二方面，如图3所示，提供一种容器编排引擎的安装装置，所述装置包括：
类型选择模块31，用于选择目标集群类型进行安装，所述目标集群类型包括联邦集群、高可用集群、普通集群中至少一个；
初始化模块32，用于对安装环境进行初始化以配置出所述目标集群类型所需要的目标安装环境；
版本安装模块33，用于在所述目标安装环境中，选择所述目标集群的版本进行安装；
检查模块34，用于对所述安装后的目标集群进行可用性检查，根据所述可用性检查对所述安装后的目标集群进行升级或完成安装。
优选的，如图4所示，所述初始化模块32包括：
清理单元321，用于对安装环境进行清理，以清除残留文件；
配置单元322，用于对清理后的安装环境进行配置；
准备单元323，用于对所述目标集群类型的对应安装包进行准备，得到所述目标安装环境。
优选的，如图5所示，所述版本安装模块33包括：
版本选择单元331，用于在所述目标安装环境中，主动选择或默认选择需要安装的所述目标集群的版本；
安装单元332，用于将所述目标集群的版本的所述对应安装包中的安装文件分发到所述目标安装环境中，对所述目标集群进行安装部署。
优选的，如图6所示，所述可用性检查包括健康状况检查；
所述检查模块34包括：
检查单元341，用于对所述安装后的目标集群进行健康状况检查，得到检查结果；
选择单元342，用于根据所述检查结果对所述安装后的目标集群进行版本升级或输出成功信息。
优选的，如图7所示，所述选择单元342包括：
升级子单元3421，用于若对所述安装后的目标集群进行版本升级，则对安 装环境进行清理，得到目标升级环境；
选择子单元3422，用于在所述目标升级环境中，选择所述目标集群的版本进行升级；
输出子单元3423，用于若不对所述安装后的目标集群进行版本升级，则对所述安装后的目标集群进行输出成功信息，得到安装结果，完成安装。
可选的，如图8所示，所述装置还包括：
部署模块30，用于按照用户的使用场景，在所述自动安装容器编排引擎的系统或平台部署多种集群模式。
本发明实施例提供的人员社交关系分析装置能够实现图1和图2的方法实施例中的各个实施方式，以及相应有益效果，为避免重复，这里不再赘述。
需要说明的是，本发明实施例提供的容器编排引擎的装置可以应用于容器编排引擎的安装设备，例如：计算机、服务器、手机等可以进行容器编排引擎安装的设备。
第三方面，如图9所示，本发明实施例提供一种电子设备，包括：存储器401、处理器402及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现本发明实施例提供的容器编排引擎的安装中的步骤。
第四方面，本发明实施例提供一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现本发明实施例提供的容器编排引擎的安装中的步骤。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本发明并不受所描述的动作顺序的限制，因为依据本发明，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于可选实施例，所涉及的动作和模块并不一定是本发明所必须的。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在本发明所提供的几个实施例中，应该理解到，所揭露的装置，可通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的
另外，在本发明各个实施例中的处理器、芯片可以集成在一个处理单元中，也可以是单独物理存在，也可以两个或两个以上硬件集成在一个单元中。计算机可读存储介质或计算机可读程序可以存储在一个计算机可读取存储器中。基 于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储器中，包括若干指令用以使得一台计算机设备(可为个人计算机、服务器或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储器包括：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序可以存储于一计算机可读存储器中，存储器可以包括：闪存盘、只读存储器(英文：Read-Only Memory，简称：ROM)、随机存取器(英文：Random Access Memory，简称：RAM)、磁盘或光盘等
以上内容是结合具体的优选实施方式对本发明所作的进一步详细说明，不能认定本发明的具体实施方式只局限于这些说明。对于本发明所属技术领域的普通技术人员来说，在不脱离本发明构思的前提下，还可以做出若干简单推演或替换，都应当视为属于本发明的保护范围。

Claims (10)

  1. 一种容器编排引擎的安装方法，所述方法用于自动安装容器编排引擎的系统或平台其特征在于，所述方法包括：
    选择目标集群类型进行安装，所述目标集群类型包括联邦集群、高可用集群、普通集群中至少一个；
    对安装环境进行初始化以配置出所述目标集群类型所需要的目标安装环境；
    在所述目标安装环境中，选择所述目标集群的版本进行安装；
    对所述安装后的目标集群进行可用性检查，根据所述可用性检查对所述安装后的目标集群进行升级或完成安装。
  2. 如权利要求1所述的方法，其特征在于，所述对安装环境进行初始化以配置出所述目标集群类型所需要的目标安装环境包括：
    对安装环境进行清理，以清除残留文件；
    对清理后的安装环境进行配置；
    对所述目标集群类型的对应安装包进行准备，得到所述目标安装环境。
  3. 如权利要求1所述的方法，其特征在于，所述在所述目标安装环境中，选择所述目标集群的版本进行安装包括：
    在所述目标安装环境中，主动选择或默认选择需要安装的所述目标集群的版本；
    将所述目标集群的版本的所述对应安装包中的安装文件分发到所述目标安装环境中，对所述目标集群进行安装部署。
  4. 如权利要求1至4中任一所述的方法，其特征在于，所述可用性检查包括健康状况检查；
    所述对所述安装后的目标集群进行可用性检查，根据所述可用性检查对所述安装后的目标集群进行升级或完成安装包括：
    对所述安装后的目标集群进行健康状况检查，得到检查结果；
    根据所述检查结果对所述安装后的目标集群进行版本升级或输出成功信息。
  5. 如权利要求4所述的方法，其特征在于，所述根据所述检查结果进行所述安装后的目标集群版本升级或输出成功信息包括：
    若对所述安装后的目标集群进行版本升级，则对安装环境进行清理，得到 目标升级环境；
    在所述目标升级环境中，选择所述目标集群的版本进行升级；
    若不对所述安装后的目标集群进行版本升级，则对所述安装后的目标集群进行输出成功信息，得到安装结果，完成安装。
  6. 一种容器编排引擎的安装装置，其特征在于，所述装置包括：
    类型选择模块，用于选择目标集群类型进行安装，所述目标集群类型包括联邦集群、高可用集群、普通集群中至少一个；
    初始化模块，用于对安装环境进行初始化以配置出所述目标集群类型所需要的目标安装环境；
    版本安装模块，用于在所述目标安装环境中，选择所述目标集群的版本进行安装；
    检查模块，用于对所述安装后的目标集群进行可用性检查，根据所述可用性检查对所述安装后的目标集群进行升级或完成安装。
  7. 如权利要求6所述的装置，其特征在于，所述初始化模块包括：
    清理单元，用于对安装环境进行清理，以清除残留文件；
    配置单元，用于对清理后的安装环境进行配置；
    准备单元，用于对所述目标集群类型的对应安装包进行准备，得到所述目标安装环境。
  8. 如权利要求6所述的装置，其特征在于，所述版本安装模块包括：
    版本选择单元，用于在所述目标安装环境中，主动选择或默认选择需要安装的所述目标集群的版本；
    安装子单元，用于将所述目标集群的版本的所述对应安装包中的安装文件分发到所述目标安装环境中，对所述目标集群进行安装部署。
  9. 一种电子设备，其特征在于，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如权利要求1至5中任一项所述的容器编排引擎的安装方法中的步骤。
  10. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至5中任一项所述的容器编排引擎的安装方法中的步骤。
PCT/CN2018/115360 2018-11-14 2018-11-14 一种容器编排引擎的安装方法、装置及电子设备 WO2020097814A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/115360 WO2020097814A1 (zh) 2018-11-14 2018-11-14 一种容器编排引擎的安装方法、装置及电子设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/115360 WO2020097814A1 (zh) 2018-11-14 2018-11-14 一种容器编排引擎的安装方法、装置及电子设备

Publications (1)

Publication Number Publication Date
WO2020097814A1 true WO2020097814A1 (zh) 2020-05-22

Family

ID=70731017

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/115360 WO2020097814A1 (zh) 2018-11-14 2018-11-14 一种容器编排引擎的安装方法、装置及电子设备

Country Status (1)

Country Link
WO (1) WO2020097814A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112463535A (zh) * 2020-11-27 2021-03-09 中国工商银行股份有限公司 多集群异常处理方法及装置
CN112527368A (zh) * 2020-12-02 2021-03-19 北京百度网讯科技有限公司 集群内核版本更新方法、装置、电子设备和存储介质
CN113377387A (zh) * 2021-06-28 2021-09-10 中煤能源研究院有限责任公司 一种煤矿智能应用的统一发布、部署、升级的方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107483572A (zh) * 2017-08-08 2017-12-15 北京奇艺世纪科技有限公司 一种服务器的部署方法和装置
CN108763090A (zh) * 2018-05-31 2018-11-06 上海陆家嘴国际金融资产交易市场股份有限公司 测试环境部署方法、装置、计算机设备和存储介质
CN108809722A (zh) * 2018-06-13 2018-11-13 郑州云海信息技术有限公司 一种部署Kubernetes集群的方法、装置和存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107483572A (zh) * 2017-08-08 2017-12-15 北京奇艺世纪科技有限公司 一种服务器的部署方法和装置
CN108763090A (zh) * 2018-05-31 2018-11-06 上海陆家嘴国际金融资产交易市场股份有限公司 测试环境部署方法、装置、计算机设备和存储介质
CN108809722A (zh) * 2018-06-13 2018-11-13 郑州云海信息技术有限公司 一种部署Kubernetes集群的方法、装置和存储介质

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112463535A (zh) * 2020-11-27 2021-03-09 中国工商银行股份有限公司 多集群异常处理方法及装置
CN112463535B (zh) * 2020-11-27 2024-05-10 中国工商银行股份有限公司 多集群异常处理方法及装置
CN112527368A (zh) * 2020-12-02 2021-03-19 北京百度网讯科技有限公司 集群内核版本更新方法、装置、电子设备和存储介质
CN112527368B (zh) * 2020-12-02 2024-03-22 北京百度网讯科技有限公司 集群内核版本更新方法、装置、电子设备和存储介质
CN113377387A (zh) * 2021-06-28 2021-09-10 中煤能源研究院有限责任公司 一种煤矿智能应用的统一发布、部署、升级的方法
CN113377387B (zh) * 2021-06-28 2024-05-17 中煤能源研究院有限责任公司 一种煤矿智能应用的统一发布、部署、升级的方法

Similar Documents

Publication Publication Date Title
JP7391862B2 (ja) 自動的に配備される情報技術（ｉｔ）システム及び方法
US11093230B2 (en) Consistent operating system servicing for distributed nodes
CN106528224B (zh) 一种Docker容器的内容更新方法、服务器及系统
US20210406079A1 (en) Persistent Non-Homogeneous Worker Pools
CN115190035B (zh) 用于提供移动设备支持服务的系统、方法、装置和介质
WO2020097814A1 (zh) 一种容器编排引擎的安装方法、装置及电子设备
US7937697B2 (en) Method, system and computer program for distributing software patches
US8332496B2 (en) Provisioning of operating environments on a server in a networked environment
US8407689B2 (en) Updating nodes considering service model constraints
US9026858B2 (en) Testing server, information processing system, and testing method
US20150309922A1 (en) On-demand software test environment generation
US7293255B2 (en) Apparatus and method for automated creation of resource types
US20090144720A1 (en) Cluster software upgrades
US20170052854A1 (en) Method and system for performing automatic system recovery
JP2017529628A (ja) マルチテナントアプリケーションサーバ環境においてパッチングをサポートするためのシステムおよび方法
US9286046B2 (en) Method and apparatus for distributed operating system image deployment
CN104915226B (zh) 一种网络设备软件启动方法、装置及网络设备
CN102662884B (zh) 一种基于网络的设备驱动程序配置方法
JP2007052519A (ja) 情報処理装置および方法、並びにプログラム
CN106445580A (zh) 一种带外升级bmc的方法及装置
CN107506295A (zh) 虚拟机备份的测试方法、设备及计算机可读存储介质
US20060271672A1 (en) System and method for loading various operating systems from a remote console
US10102008B2 (en) Managed boot process system
EP3120496B1 (en) Configuration generation based on availability-estimate
Guide v5. 4.0

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18939840

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18939840

Country of ref document: EP

Kind code of ref document: A1