CN115604101B

CN115604101B - System management method and related equipment

Info

Publication number: CN115604101B
Application number: CN202211199195.8A
Authority: CN
Inventors: 陈宝泉
Original assignee: Beijing Wellintech Co Ltd
Current assignee: Beijing Wellintech Co Ltd
Priority date: 2022-09-29
Filing date: 2022-09-29
Publication date: 2024-02-02
Anticipated expiration: 2042-09-29
Also published as: CN115604101A

Abstract

The application relates to a system management method and related equipment, and relates to the technical field of software. In the present application, the management system may determine a hierarchical relationship between a plurality of systems, and then determine an installation order of the plurality of systems according to the hierarchical relationship between the plurality of systems. Therefore, the management system can sequentially install the systems based on the case sequences of the systems, and the installation efficiency of the cloud system is improved.

Description

System management method and related equipment

Technical Field

The present disclosure relates to the field of software technologies, and in particular, to a system management method and related devices.

Background

With the continuous development of technology, cloud technology is receiving more and more attention. One scenario of cloud technology is a cloud platform. For example, a user may conduct development of an Application (APP) through a cloud platform. Cloud platforms can be classified into public clouds, private clouds, and hybrid clouds according to types. Hybrid clouds refer to a combination of public and private clouds.

However, the construction of a cloud platform is a complex process, whether it is public or private or hybrid. The developer needs to manually configure and install the nodes (also called servers) in the cloud platform one by one, and in the case that the number of the nodes of the cloud platform is large, the efficiency of using a manual mode is low.

Disclosure of Invention

The application provides a system management method and related equipment, which can improve the installation efficiency of a cloud platform.

The technical scheme of the application is as follows:

in a first aspect, the present application provides a system management method, including: determining a hierarchical relationship between a plurality of systems; an installation order of the plurality of systems is determined according to a hierarchical relationship between the plurality of systems.

In some implementations, the method for determining the installation order of the plurality of systems according to the hierarchical relationship between the plurality of systems specifically includes: the plurality of systems are installed in order of the hierarchy from top to bottom determined based on the hierarchy relation.

Optionally, the hierarchical relationship includes a parent-child relationship and a grandchild relationship; and/or the method further comprises: after the subsystem is installed, the subsystem is communicatively connected with its corresponding parent system and the information of the subsystem is synchronized to the parent system.

Optionally, the plurality of systems are of different types, the types of systems including an end system, an edge system, and a cloud system, the end system having a capacity less than the edge system, the edge system having a capacity less than the cloud system.

Alternatively, different types of systems include different numbers of nodes.

In some implementations, before installing the plurality of systems, the method further includes: and respectively configuring the systems, and connecting the configured systems in a communication way.

In some implementations, the plurality of systems includes a first system and a second system, the method comprising: and if the second system is an end system, installing the second system according to the configuration information of the second system. If the first system is the upper system of the second system, after all nodes of the first system are installed, the nodes of the second system are installed.

In some implementations, the method further includes: determining the role type of each node in a plurality of nodes included in a second system, wherein the nodes comprise management nodes, service nodes and storage nodes; the management node is used for managing a plurality of nodes, the service node is used for processing service data of the second system, and the storage node is used for storing the service data.

In some implementations, the "node for installing the second system" includes: installing application programs corresponding to a plurality of nodes in the second system according to the role type of each node of the second system; the role types of the nodes comprise management types, service processing types and storage data types, and application programs corresponding to different role types are different.

In some implementations, the method for installing the application programs corresponding to the plurality of nodes in the second system according to the role type of each node in the second system specifically includes: installing application programs corresponding to management nodes in the plurality of nodes; after the application programs corresponding to the management nodes are installed, the application programs corresponding to the service nodes and the application programs corresponding to the storage nodes in the plurality of nodes are installed.

In a second aspect, the present application provides a management system, which may be used to implement the system management method according to the first aspect and any one of the possible implementation manners of the first aspect. The functions of the system can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software comprises one or more modules or units corresponding to the steps in the application management method according to the first aspect and any possible implementation manner of the first aspect.

For example, the system includes: a determining unit configured to determine a hierarchical relationship between a plurality of systems; and the processing unit is used for determining the installation sequence of the systems according to the hierarchical relationship among the systems.

Optionally, the hierarchical relationship includes a parent-child relationship and a grandchild relationship; the method further comprises the steps of: after the subsystem is installed, the subsystem is communicatively connected with its corresponding parent system and the information of the subsystem is synchronized to the parent system.

Alternatively, different types of systems include different numbers of nodes.

In some implementations, prior to installing the plurality of systems, the processing unit is further to: and respectively configuring the systems, and connecting the configured systems in a communication way.

In some implementations, the plurality of systems includes a first system and a second system, the processing unit further configured to: and if the second system is an end system, installing the second system according to the configuration information of the second system. If the first system is the upper system of the second system, after all nodes of the first system are installed, the nodes of the second system are installed.

In some implementations, the determining unit is further configured to: determining the role type of each node in a plurality of nodes included in a second system, wherein the nodes comprise management nodes, service nodes and storage nodes; the management node is used for managing a plurality of nodes, the service node is used for processing service data of the second system, and the storage node is used for storing the service data.

In some implementations, the processing unit is specifically configured to: installing application programs corresponding to a plurality of nodes in the second system according to the role type of each node of the second system; the role types of the nodes comprise management types, service processing types and storage data types, and application programs corresponding to different role types are different.

In some implementations, the processing unit is specifically configured to: installing application programs corresponding to management nodes in the plurality of nodes; after the application programs corresponding to the management nodes are installed, the application programs corresponding to the service nodes and the application programs corresponding to the storage nodes in the plurality of nodes are installed.

In a third aspect, the present application provides an electronic device, the electronic device comprising: a processor, a memory for storing processor-executable instructions; the processor is configured to execute the instructions to cause the electronic device to implement the method as described in the first aspect and any one of the possible implementations of the first aspect.

In a fourth aspect, the present application provides a computer-readable storage medium having stored thereon computer program instructions; the computer program instructions, when executed by an electronic device, cause the electronic device to implement the method as described in the first aspect and any one of the possible implementations of the first aspect.

In a fifth aspect, the present application provides a computer program product comprising computer readable code, or a non-transitory computer readable storage medium carrying computer readable code, which when run in an electronic device, causes a processor in the electronic device to implement a method as described in any one of the first aspect and any one of the possible implementations of the first aspect.

In the present application, after determining the hierarchical relationship between the plurality of systems, the plurality of system installation orders may be determined according to the hierarchical relationship of the plurality of systems. That is, the present application can install each system step by step based on the hierarchical relationship of a plurality of systems. Compared with the manual mode of installing each system, the system installation method has the advantages that the installation logic relation of the system is defined, automatic installation of the system can be realized through the installation logic, the installation complexity of the system is reduced, the installation time of the system is shortened, and the installation efficiency is improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application and do not constitute an undue limitation on the application.

Fig. 1 is a flow chart of a system management method according to an embodiment of the present application;

FIG. 2 is a schematic diagram of a hierarchical relationship between a plurality of systems according to an embodiment of the present disclosure;

fig. 3 is a flow chart of a system management method according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a plurality of system interactions according to an embodiment of the present application;

FIG. 5 is a flowchart illustrating another system management method according to an embodiment of the present disclosure;

FIG. 6 is a flowchart of another system management method according to an embodiment of the present disclosure;

fig. 7 is a schematic structural diagram of a system management device according to an embodiment of the present application.

Detailed Description

In order to enable those skilled in the art to better understand the technical solutions of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.

It should be noted that the terms "first," "second," and the like in the description and claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that embodiments of the present application described herein may be implemented in sequences other than those illustrated or otherwise described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.

It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, and/or components.

"and/or", "and/or" are used to describe association relationships of association objects, meaning that three relationships may exist. For example, a and/or B may represent: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.

Cloud computing is an important technology in the field of computers, and with the development of technology, the application range of cloud computing is more and more wide, and the cloud computing has been developed to a cloud protogenesis stage. Cloud protogenesis is a technology for building a cloud architecture and running cloud services, and has the characteristics of containerization, micro-services, continuous integration (continuous integration, CI)/continuous delivery (continuous delivery, CD), processes, methods, systems (development operations, devOps) and the like.

Among other things, cloud architecture may include multiple tiers of infrastructure-as-a-service (infrastructure as a service, IAAS), platform-as-service (platform as a service, PAAS), software-as-a-service (SAAS), and the like. IAAS is a service provided through infrastructure and is the basis of cloud protogenesis. The PAAS is a platform/service, integrates physical machines, application services and data, shields an infrastructure, and can provide services to the outside. The SAAS provides services to users in the form of an Internet browser or web page program connection.

Depending on the type of cloud platform, the cloud platform may include public clouds, private clouds, and hybrid clouds. The public cloud may refer to a cloud platform capable of providing public cloud services. Private clouds may refer to cloud platforms that individually provide cloud services for an enterprise or factory. The hybrid cloud refers to a cloud platform combining public cloud and private cloud.

In one scenario, when cloud computing applications are in the industry (i.e., industrial clouds), PAAS services are typically provided through public clouds. Relatively few private and hybrid clouds can be provided. However, in the industrial field, there is an increasing demand for private clouds or hybrid clouds due to sensitivity and security of industrial data.

However, since the cloud platform may be composed of a plurality of nodes, it takes a lot of time and effort to build or maintain the cloud platform, whether it is a public cloud or a private cloud. Thus leading to slower development progress of the industrial cloud platform.

At present, the Cloud platform can be installed and maintained through K8S packaging technology or products such as Cloud foundation. But these products are mainly used for deployment maintenance of application services at the internet consumer end. For the industrial field, the construction of the cloud platform still has the problem of complex installation.

In one example, some underlying services may be installed directly and manually on nodes of the cloud platform using an open source tool (such as CDH), and then application services may be installed using an open source such as openhift, to finally complete the installation of a single-layer cloud and/or single-layer edge platform. In turn, other nodes are installed in this manner. After the nodes are installed, the nodes are required to be configured, so that the cloud platform is built.

However, the manual installation of the nodes of the cloud platform is inefficient. Under the condition that the number of the nodes of the cloud platform is large, a large amount of manpower and time are required to be consumed, so that the construction efficiency of the cloud platform is low, and the cost is high.

Based on the above, the embodiment of the application provides a system management method, which can be applied to a management system to determine a hierarchical relationship among a plurality of systems, so that the installation sequence of the plurality of systems can be determined according to the hierarchical relationship among the plurality of systems. Furthermore, the step-by-step installation of the systems is realized according to the installation sequence of the systems, so that the installation efficiency of the systems is improved.

In the embodiment of the present application, the system may also be referred to as a region, a regional system, or a distributed system. A system may include one or more nodes. For example, a node may comprise a server, a computer, a physical machine, a virtual machine, etc., and one or more nodes of a system may be deployed in the same area.

In one example, a system may include multiple types. For example, end systems, edge systems, and cloud systems may be included. Wherein the capacity of the end system is less than the capacity of the side system, which is less than the capacity of the cloud system.

Alternatively, in yet another example, the capability of the end system is less than the capability of the side system, which is equal to or greater than the capability of the cloud system.

The capabilities of the system may include, among other things, business service capabilities and data storage capabilities. Business service capability may refer to data processing capability of a node in a system, e.g., the business capability of the system may be determined by a central processing unit (Central Processing Unit, CPU), running memory of the node comprised by the system. The better the CPU performance of the system's nodes, the higher the business service capability of the system. The larger the memory of the node of the system, the higher the business service capability of the system. The data storage capacity of the system may be determined by the storage capacity of the memory (e.g., hard disk, input/output) of the node the system includes. The larger the storage space of the nodes of the system, the higher the data storage capacity of the system.

It should be noted that, in the embodiments of the present application, a cloud platform may include a cloud system, one or more edge systems, and/or one or more end systems. One cloud system and the corresponding side system of the cloud system can independently operate.

Further, the number of nodes included in different types of systems may be the same or different. For example, the cloud system includes a number of nodes that is greater than or equal to the number of nodes that the edge system includes. The cloud system and the edge system each include a greater number of nodes than the end system. For example, a cloud system may include 10 or more nodes, an edge system may include 5 or more nodes, and an end system may include 1 node.

The method may be implemented on a hardware device corresponding to the management system, for example: the hardware devices may include servers, computers, electronic devices, and the like. The server may be a single server, or may be a server cluster formed by a plurality of servers. In some implementations, the server cluster may also be a distributed cluster. The application does not limit the specific implementation manner of the hardware device corresponding to the management system. It should be noted that, the implementation steps on the management system side in the embodiments of the present application may be implemented by hardware devices corresponding to the management system.

Fig. 1 is a flow chart of a system management method according to an embodiment of the present application. As shown in fig. 1, the system management method may include:

s101, determining a hierarchical relationship among a plurality of systems.

The hierarchical relationships between the systems may include parent-child relationships, grandchild relationships, etc., and may also include peer relationships. For example, as shown in fig. 2, the above-described end system, side system, and cloud system are combined. The hierarchical relationship between the end system and the edge system may be a parent-child relationship (i.e., the end system is a subsystem of the edge system). The hierarchical relationship between the end system and the cloud system may be a parent-child relationship or a grandchild relationship (i.e., the end system may be a subsystem of the cloud system or a grandchild system). The hierarchical relationship between the edge system and the cloud system may be a parent-child relationship (i.e., the edge system is a subsystem of the cloud system). Based on the setting of the end system, the side system and the cloud system, the installation structure of the cloud platform can be flexibly selected, and the application range is wider.

In one possible implementation, the management system may determine a hierarchical relationship between the plurality of systems based on the number and configuration of nodes the systems include. The configuration of the node may include the CPU, running memory, storage of the node.

For example, taking an example in which the plurality of systems includes a first system and a second system, when the first system includes a plurality of nodes greater than the second system, and/or the configuration of the nodes of the first system is greater than the configuration of the nodes of the second system, the first system may be a parent system of the second system, or the first system may be a grandparent system of the second system.

For another example, the first system and the second system may include the same number and configuration of nodes, and the first system and the second system may be in peer relationship, or the first system may be a parent system of the second system, or the second system may be a parent system of the first system.

Of course, in the embodiment of the present application, the plurality of systems is not limited to the two systems described above, and may include a larger number of systems, for example, may include 3 or more than 3 systems. Specifically, the number of the systems can be flexibly determined according to the specific structure of the cloud platform.

It should be noted that, in the embodiment of the present application, based on the hierarchical relationship between the multiple systems, when the data storage capability and/or the service capability of the lower system cannot meet the requirements in the operation process of the lower system, the lower system may use the upper system to continue to store data and/or operate services.

S102, determining the installation sequence of the systems according to the hierarchical relation among the systems.

Wherein, the installation order of the plurality of systems may refer to an installation priority of the plurality of systems. The higher the level of the system, the higher the installation priority. For example, the parent system has a higher installation priority than the subsystem.

In one possible implementation, the management system may sequentially install the plurality of systems in a top-down hierarchical order determined based on a hierarchical relationship between the plurality of systems. For example, the first system is a superior system (such as a parent system or a grandparent system) of the second system, and the first system may be installed first, and after the first system is installed, the second system may be installed.

In this embodiment of the present application, installing a plurality of systems may refer to installing nodes in the plurality of systems. For example, the management system may install a corresponding application for a node according to the role type of the node in the system. The nodes can be divided into management nodes, service nodes and storage nodes according to role types. Nodes of different role types have different applications installed. For example, the management node installs an application of a management class (or control class). The service node installs the application of the service processing type. The storage node installs an application of the data storage type.

The management node can be used for managing other nodes of the system and belongs to a control layer of the system. For example, nodes may be added, nodes deleted, configuration information of nodes updated (e.g., names of modified nodes, underlying operating system parameter configuration, firewall on or off, log information), and applications controlling other nodes installed. The application corresponding to the management node may be used to run and control applications (referred to as control services) of other systems or nodes.

The service node may be used to execute the service of the system, and belongs to the service layer of the system. The application program corresponding to the business node can be used for providing business services. For example, business data of the system (referred to as system services or business services) may be run. For example, the service data may be processed to obtain a service processing result. For example, for a business for developing an industrial application, after acquiring data (e.g., configuration parameters, functional requirements) for developing the industrial application, the business process type application may run the data to obtain an application model for the industrial application. Therefore, compared with a mode of manually developing the application program, the development efficiency is improved.

The storage node may be used to store operational data of the system in which it is located. The application programs corresponding to the storage nodes can be used for providing storage and caching of data and messages, providing support for business services and control services (also called support services), and belonging to the storage layer of the system. For example, writing or reading of data, a storage location of data, or the like may be controlled.

It should be noted that, in the embodiment of the present application, the application program that provides the support service is open-source, and therefore, the support service may also be referred to as an open-source service.

In one example, the management system may determine the role of a node based on configuration information of the node. The configuration information of the node comprises a CPU, a running memory and a storage of the node. For example, the plurality of nodes includes 3 nodes (node 1, node 2, and node 3, respectively) as an example. The memory space of the memory of the node 1 is larger than the memory spaces of the nodes 2 and 3, and the performance of the CPU of the node 2 is higher than that of the CPUs of the nodes 1 and 3. Node 1 may be a storage node, node 2 may be a service node, and node 3 may be a management node.

It should be noted that, in the embodiment of the present application, since the end system includes one node, the node may be used as a management node, or may be used as a service node and a storage node. That is, the management system may install management type applications, business process type applications, and data store type applications at nodes of the end system.

In one example, when installing multiple nodes of a system, a management system may determine an installation order of the multiple nodes according to a role type of the nodes of the system. For example, the management system may first install an application corresponding to the management node, and after the application corresponding to the management node is installed, install an application corresponding to the service node and the storage node. Thus, after the management node installs the corresponding application program, the installation of the application programs corresponding to the processing node and the storage node can be controlled based on the application program of the management node. Therefore, the management system can flexibly select the installation mode according to the types of the systems, and can adapt to a plurality of scenes.

Based on the technical solution of fig. 1, after determining the hierarchical relationship between the systems, the management system may determine the installation order of the systems according to the hierarchical relationship of the systems. That is, the present application can install each system step by step based on the hierarchical relationship of a plurality of systems. Compared with the manual mode of installing each system, the embodiment of the application makes clear the installation logic relation of the system, the automatic installation of the system can be realized through the installation logic, the installation complexity of the system is reduced, the installation time of the system is further shortened, and the installation efficiency is improved.

In some embodiments, as shown in fig. 3, the method provided in the embodiments of the present application may further include:

s301, after the sub-system is installed, the sub-system is in communication connection with a corresponding parent system, and information of the sub-system is synchronized to the parent system.

Before the subsystem is installed, the parent system corresponding to the subsystem is installed.

In one possible implementation, when installing the subsystem and the parent system, the IP address of the subsystem may be configured to the parent system and the internet protocol (internet protocol, IP) address of the parent system may be configured to the subsystem. In this manner, the subsystem and parent system may be communicatively coupled based on the IP address.

After the subsystem establishes a communication connection with the parent system, the subsystem may synchronize information of the subsystem to the parent system, and the subsystem may also cache information of the parent system.

The information of the subsystem may include a name of the subsystem (including a name of the node), function information, address information (such as an IP address) of the node, an activation state (including available or unavailable), an operation state (a size of a CPU of the node, a size of a memory), and the like. The information of the parent system may include address information of nodes of the parent system, names of the nodes, activation states, and the like.

In one example, as shown in fig. 4, when the cloud system is a parent system of the end system, the end system may synchronize information of the end system to the cloud system and cache information of the cloud system. When the cloud system is a parent system of the side system, the side system can synchronize information of the side system to the side system and buffer the information of the side system, and the side system can synchronize the information of the side system to the cloud system and buffer the information of the cloud system.

Based on the technical scheme of fig. 3, the management system may establish communication connection between the plurality of systems after sequentially installing the plurality of systems according to the hierarchical relationship between the plurality of systems. Meanwhile, the subsystem can be controlled to synchronize the information of the subsystem to the parent system. Thus, a plurality of systems can be connected in series to obtain the finished cloud platform.

In some embodiments, to establish a communication connection between multiple systems, the method may further include S501, as shown in fig. 5.

S501, configuring a plurality of systems respectively, and connecting the configured systems in a communication way.

Wherein configuring the system may also be described as initializing the system. The configured system can realize communication connection among a plurality of systems according to configuration information of other systems.

In one example, for a subsystem in a plurality of systems, a management system may first install and run an application corresponding to a management node in the subsystem, and configure an installation package of other role types for the management node. Meanwhile, when the application program corresponding to the management node runs, the management node can be triggered to synchronize the information of the subsystem to the parent system. In this manner, the management system may initialize the subsystem (also referred to as a system environment installation).

After initializing the subsystem, the management system may initialize the service node and the storage node (also referred to as installation of the node environment). For example, the management system may configure the operating environment (e.g., jdk installation, network parameter configuration, node system environment configuration, node installation control services and operations, etc.) of the application for the business nodes and storage nodes. After the service node and the storage node are initialized, the management node may use the installation package corresponding to the service process to install the application program on the service node (that is, install the service support service), and use the storage node corresponding to the installation package to install the application program on the storage node. Thus, a plurality of service nodes in the system can be communicated to form a service processing cluster, and a plurality of storage nodes in the system are communicated to form a data storage cluster.

It should be noted that, corresponding to an end system including a node, the management system may directly use the memory of the node to store data, and use the running system of the node to perform business operation, so that the node of the opposite end system does not need to initialize the business node and the storage node.

Further, after the installation of the application program on each node of the system, the management system may install a system service (e.g., database system service, security audit system service) on each node of the system. For example, the management system may store the installation package of the system service to the node (e.g., in a mirror repository corresponding to the node). Based on the above-described business process clusters and data storage clusters, installation and operation of system services (i.e., support service installation) can be performed.

That is, in the present application, the system is installed step by step in a plurality of stages (four stages of system environment installation, node environment installation, support service installation, system service installation, etc.). The system service installation depends on the supporting service installation result, the supporting service installation depends on the node environment installation result, the node environment installation depends on the regional environment installation result and depends step by step, and a complete cloud platform installation flow is formed. The installation process of the cloud platform is clarified, so that the installation complexity and cost of the cloud platform are reduced, and the installation efficiency of the cloud platform is improved.

It should be noted that, for the end system, the management system may directly perform installation and operation of the system service.

Based on the installation process, the management system can construct installation logic for the installation system, the nodes, the service and the like, the system is installed based on the installation logic, automatic hierarchical installation among a plurality of systems is realized, and the installation flow of the cloud platform is defined. Meanwhile, when a plurality of systems are installed, the automatic installation of the whole cloud platform can be completed only by carrying out configuration corresponding to the type according to the type of the system.

In a scenario, taking a case that a plurality of systems include a first system and a second system as an example, if the second system is an end system, the management system can install the second system according to configuration information of the second system; if the first system is a superior system of the second system, the management system may continue to install the nodes of the second system after all the nodes of the first system are installed, until all the systems are installed.

Based on the embodiment, the plurality of systems are respectively configured, so that the configured plurality of systems can be in communication connection, the plurality of systems can be communicated, and the cloud platform is built.

In some embodiments, as shown in fig. 6, a system management method provided in an embodiment of the present application includes:

s601, determining a system type corresponding to each node cluster in the plurality of node clusters.

The system types may include cloud systems, edge systems, and end systems, among others. S601 may refer to the description of the above embodiments, and will not be repeated.

In one possible implementation, after determining the system corresponding to each node cluster, an identifier may be set for the node cluster, where the identifier may be used to indicate the system corresponding to each node.

S602, determining a hierarchical relationship among a plurality of systems.

The description of S101 may be referred to in S602, and will not be repeated.

S603, determining whether the target system is an end system.

The target system may be any one of a plurality of systems.

In one possible implementation, the management system determines whether the target system is an end system according to the identification of the node in the target system.

If the target system is an end system, S604 and S605 are executed; if the target system is not an end system, S606 to S609 are executed.

S604, configuring nodes in the target system, and installing system services according to the configured target system.

S605, installing the system service according to the installation information of the nodes, and storing the installation information of the system service.

S606, storing information of the target system and information of a parent system of the target system.

The information of the target system and the information of the parent system may refer to the description of the foregoing embodiments, which is not repeated.

S607, installing the nodes of the target system and storing the installation information of the nodes.

In S607, reference may be made to the installation process of the system in S102, which is not described herein.

S608, installing the open source service according to the installation information of the nodes of the target system, and storing the installation information of the open source service.

S609, installing a service system according to the installation information of the open source service, and storing the installation information of the system service.

After S605 or S609, S610 is performed.

S610, detecting whether all the systems are installed.

If all the systems are installed, ending the system installation; if there are uninstalled systems, S603 to S609 are re-executed until all the plurality of systems are installed.

Based on the embodiment, the installation flow of the cloud system is clarified, and the complex configuration operation from the node to the open source service installation process is encapsulated, so that the automatic installation of various cloud systems is realized.

It will be appreciated that, in actual implementation, the nodes in the system according to the embodiments of the present application may include one or more hardware structures and/or software modules for implementing the corresponding system management method described above, where the executing hardware structures and/or software modules may constitute an electronic device. Those of skill in the art will readily appreciate that the algorithm steps of the examples described in connection with the embodiments disclosed herein may be implemented as hardware or a combination of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

Based on such understanding, taking a hardware structure and/or a software module included in a management system as an example, the embodiments of the present application further correspondingly provide a system management device, which may be applied to the above management system (such as a hardware device corresponding to the management system). Fig. 7 is a schematic structural diagram of a management system according to an embodiment of the present application. As shown in fig. 7, the management system may include: a determining unit 701 for determining a hierarchical relationship between a plurality of systems; a processing unit 702, configured to determine an installation order of the plurality of systems according to a hierarchical relationship between the plurality of systems.

Alternatively, different types of systems include different numbers of nodes.

In some implementations, before installing the plurality of systems, the processing unit 702 is further configured to: and respectively configuring the systems, and connecting the configured systems in a communication way.

In some implementations, the plurality of systems includes a first system and a second system, and the processing unit 702 is further configured to: and if the second system is an end system, installing the second system according to the configuration information of the second system. If the first system is the upper system of the second system, after all nodes of the first system are installed, the nodes of the second system are installed.

In some implementations, the determining unit 701 is further configured to: determining the role type of each node in a plurality of nodes included in a second system, wherein the nodes comprise management nodes, service nodes and storage nodes; the management node is used for managing a plurality of nodes, the service node is used for processing service data of the second system, and the storage node is used for storing the service data.

In some implementations, the processing unit 702 is specifically configured to: installing application programs corresponding to a plurality of nodes in the second system according to the role type of each node of the second system; the role types of the nodes comprise management types, service processing types and storage data types, and application programs corresponding to different role types are different.

In some implementations, the processing unit 702 is specifically configured to: installing application programs corresponding to management nodes in the plurality of nodes; after the application programs corresponding to the management nodes are installed, the application programs corresponding to the service nodes and the application programs corresponding to the storage nodes in the plurality of nodes are installed.

As described above, the embodiment of the present application may divide functional modules for each execution subject involved in the application management method according to the above-described method example. The integrated modules may be implemented in hardware or in software functional modules. In addition, it should be noted that, in the embodiment of the present application, the division of the modules is schematic, only one logic function is divided, and another division manner may be implemented in actual implementation. For example, each functional module may be divided corresponding to each function, or two or more functions may be integrated in one processing module.

The specific manner in which each module performs the operation and the beneficial effects of the application management device in the foregoing embodiment are described in detail in the foregoing method embodiment, and are not described herein again.

The embodiment of the application also provides an electronic device, which can be a hardware device corresponding to the management system or a node in the system. An electronic device includes: a processor, a memory for storing processor-executable instructions; the processor is configured to execute the instructions, to cause the electronic device to implement the method as described in the previous embodiments.

In an exemplary embodiment, the present application also provides a computer-readable storage medium having stored thereon computer program instructions; the computer program instructions, when executed by an electronic device, cause the electronic device to implement the method as described in the previous embodiments.

Alternatively, the above-described computer-readable storage medium may be a non-transitory computer-readable storage medium, which may be, for example, a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

In an exemplary embodiment, the present application also provides a computer program product comprising a computer readable code, or a non-transitory computer readable storage medium carrying computer readable code, which when run in an electronic device, causes a processor in the electronic device to carry out the method as described in the previous embodiments.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It is to be understood that the present application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. A system management method, the method comprising:

determining a hierarchical relationship between a plurality of systems according to the number and configuration of nodes included in each system;

determining the installation sequence of the systems according to the hierarchical relationship among the systems;

and based on the hierarchical relationship among the systems, when a lower system in the systems is in operation, if the data storage capacity and/or the business service capacity of the lower system cannot meet the requirements, the lower system uses an upper system of the lower system to continue data storage and/or operation business.

2. The method of claim 1, wherein determining the order of installation of the plurality of systems based on the hierarchical relationship between the plurality of systems comprises:

and sequentially installing the systems according to the hierarchical order from top to bottom determined based on the hierarchical relationship.

3. The method of claim 2, wherein the hierarchical relationships comprise parent-child relationships, grandchild relationships; and/or the number of the groups of groups,

the method further comprises the steps of:

after the subsystem is installed, the subsystem is in communication connection with its corresponding parent system and the information of the subsystem is synchronized to the parent system.

4. The method of claim 1, wherein the plurality of systems are of different types, the types comprising an end system, an edge system, and a cloud system, the end system having a capability that is less than a capability of the edge system, the edge system having a capability that is less than a capability of the cloud system.

5. The method of claim 4, wherein different types of systems include different numbers of nodes.

6. The method of claim 2, wherein prior to installing the plurality of systems, the method further comprises:

and respectively configuring the systems, and connecting the configured systems in a communication way.

7. The method of claim 6, wherein the plurality of systems includes a first system and a second system, the method further comprising:

if the second system is an end system, installing the second system according to the configuration information of the second system;

if the first system is a superior system of the second system, after all nodes of the first system are installed, the nodes of the second system are installed.

8. The method of claim 7, wherein the method further comprises:

determining a role type of each node in a plurality of nodes included in the second system; the nodes comprise management nodes, service nodes and storage nodes; the management node is used for managing the plurality of nodes, the service node is used for processing service data of the second system, and the storage node is used for storing the service data.

9. The method of claim 8, wherein the node that installs the second system comprises:

installing application programs corresponding to a plurality of nodes in the second system according to the role type of each node of the second system;

the role types comprise a management type, a service processing type and a storage data type, and the application programs corresponding to different role types are different.

10. The method according to claim 9, wherein installing the application programs corresponding to the plurality of nodes in the second system according to the role type of each node in the second system includes:

installing application programs corresponding to management nodes in the plurality of nodes;

after the application programs corresponding to the management nodes are installed, the application programs corresponding to the service nodes and the application programs corresponding to the storage nodes in the plurality of nodes are installed.

11. A management system, the system comprising:

a determining unit configured to determine a hierarchical relationship between a plurality of systems according to data and configuration of nodes included in each of the plurality of systems;

a processing unit for determining an installation order of the plurality of systems according to a hierarchical relationship between the plurality of systems;

12. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the system management method of any of claims 1-10 when the program is executed by the processor.

13. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the steps of the system management method according to any of claims 1-10.