CN113886093B - Cloud resource management system based on multi-cloud architecture and electronic equipment - Google Patents

Cloud resource management system based on multi-cloud architecture and electronic equipment Download PDF

Info

Publication number
CN113886093B
CN113886093B CN202111480005.5A CN202111480005A CN113886093B CN 113886093 B CN113886093 B CN 113886093B CN 202111480005 A CN202111480005 A CN 202111480005A CN 113886093 B CN113886093 B CN 113886093B
Authority
CN
China
Prior art keywords
cloud
cloud resource
service node
module
resources
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202111480005.5A
Other languages
Chinese (zh)
Other versions
CN113886093A (en
Inventor
王浩原
王成太
曹永浩
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Vhall Time Technology Co ltd
Original Assignee
Beijing Vhall Time Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Vhall Time Technology Co ltd filed Critical Beijing Vhall Time Technology Co ltd
Priority to CN202111480005.5A priority Critical patent/CN113886093B/en
Publication of CN113886093A publication Critical patent/CN113886093A/en
Application granted granted Critical
Publication of CN113886093B publication Critical patent/CN113886093B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/50Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005Allocation of resources, e.g. of the central processing unit [CPU] to service a request

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The application provides a cloud resource management system and electronic equipment based on a multi-cloud architecture, which comprise a cloud resource acquisition module, a cloud resource management module and a cloud resource management module, wherein the cloud resource acquisition module is used for acquiring cloud resources needing to be managed; the cloud resource query module is used for querying service node information corresponding to the cloud resources, and the service node information comprises at least one service node which is configurable by the cloud resources; the execution service node module is used for configuring the at least one service node for the cloud resource; a service node configuration state obtaining module, configured to obtain a configuration state of the at least one service node; the service node configuration state display module is used for displaying the configuration state of the at least one service node; a service node configuration completion judging module, configured to judge whether configuration of the at least one service node is completed; and the cloud resource storage module is used for persisting the configured cloud resources. According to some embodiments of the present application, different host initialization effects required by different application scenarios can be achieved.

Description

Cloud resource management system based on multi-cloud architecture and electronic equipment
Technical Field
The application relates to the field of internet operation and maintenance under a multi-cloud architecture, in particular to a cloud resource management system and electronic equipment based on the multi-cloud architecture.
Background
With the development of cloud computing technology, in order to meet the business requirements of enterprises, most internet enterprises adopt a plurality of cloud manufacturer products at the same time.
Due to the product difference of each cloud manufacturer, the operation and maintenance work of the multi-cloud architecture becomes very complicated. At present, after each enterprise accesses a multi-cloud platform, IT personnel of the enterprise usually manually operate each cloud platform, purchase and start a host and record the host into each associated system, which is time-consuming and labor-consuming.
The existing cloud management platform mainly has resource input/discovery capability, does not relate to starting, initialization configuration and the like of resources, and has insufficient support for the asset initialization capability of business requirements.
Therefore, the demand for a solution capable of realizing automatic batch multi-cloud host purchasing, starting and completing initialization configuration is more obvious.
Disclosure of Invention
The application provides a cloud resource management system and electronic equipment based on a multi-cloud architecture, which are used for solving the problem that the solution of a cloud host in the multi-cloud architecture in the prior art cannot meet the enterprise requirements.
According to one aspect of the application, a cloud resource management system based on a multi-cloud architecture is provided, which comprises a cloud resource acquisition module, a cloud resource management module and a cloud resource management module, wherein the cloud resource acquisition module is used for acquiring cloud resources to be managed; the cloud resource query module is used for querying service node information corresponding to the cloud resources, and the service node information comprises at least one service node which is configurable by the cloud resources; the execution service node module is used for configuring the at least one service node for the cloud resource, the at least one service node comprises a first service node and a second service node, the configuration process of the first service node and the configuration process of the second service node are not in a sequential relationship, and the configuration result of the first service node does not affect the second service node; a service node configuration state obtaining module, configured to obtain a configuration state of the at least one service node; the service node configuration state display module is used for displaying the configuration state of the at least one service node; a service node configuration completion judging module, configured to judge whether configuration of the at least one service node is completed; and the cloud resource storage module is used for persisting the configured cloud resources.
According to some implementations, the cloud resources include cloud hosts, RDS, Redis.
According to some implementations, the cloud resource management system further includes a cloud resource creation module configured to create the cloud resource according to a user requirement.
According to some implementations, the create cloud asset module includes a cloud resource requirement obtaining unit, configured to obtain a cloud resource requirement of a user; the cloud resource list acquiring unit is used for acquiring a cloud resource list of at least one cloud manufacturer; the cloud resource selection unit is used for selecting cloud resources meeting the cloud resource requirements from the cloud resource list; a cloud resource confirming unit configured to confirm the cloud resource information selected by the cloud resource selecting unit; and the cloud resource snapshot unit is used for storing the cloud resource information.
According to some implementations, the cloud resource information includes details of a service on which the cloud resource is started, a quantity of the cloud resource, hardware information of the cloud resource, software information of the cloud resource, and/or a price of the cloud resource.
According to some implementations, the at least one service node includes initializing a host scripting service, joining a bastnasi system service, joining a zabbix service, joining a configuration management system service, joining a container management platform service, and/or joining a kubernets cluster service.
According to some implementations, the executive service node module includes a message queue module to store the at least one service node task that needs to be executed; and/or the service node script scheduling module is used for calling the task script corresponding to the at least one service node according to the at least one service node task.
According to some implementations, the cloud resource management module further includes a cloud resource warehousing status updating module, configured to update warehousing information of the cloud resources, so as to ensure consistency with the cloud resource information persisted by the cloud manufacturer.
According to some implementations, the cloud resource management module further includes a cloud resource startup module to start the cloud resource before the cloud resource configures the at least one service node.
According to an aspect of the application, an electronic device is presented, comprising one or more processors; storage means for storing one or more programs; when executed by the one or more processors, cause the one or more processors to implement the functions implemented by the cloud resource management system as previously described.
According to some example embodiments of the application, different service node combinations are configured in different application scenes by flexibly configuring service nodes for a cloud host, so that different cloud resource initialization effects required in different application scenes are achieved.
According to some embodiments of the application, the common content of the cloud resources of the cloud manufacturers is abstracted into the unified template, when the cloud resources are purchased, only the host computer needs to be purchased according to the template, the problem that the user needs to purchase the cloud resources individually is avoided, the time is saved, and the labor cost is reduced.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments will be briefly introduced below.
FIG. 1 shows a system architecture diagram according to an example embodiment of the present application.
Fig. 2 is a block diagram of a cloud resource management system based on a multi-cloud architecture according to an example embodiment of the present application.
Fig. 3 illustrates a block diagram of a creating cloud asset module based on a multi-cloud architecture according to an example embodiment of the present application.
Fig. 4 shows a block diagram of an electronic device according to an exemplary embodiment of the present application.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The same reference numerals denote the same or similar parts in the drawings, and thus, a repetitive description thereof will be omitted.
The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the embodiments of the disclosure can be practiced without one or more of the specific details, or with other means, components, materials, devices, or operations. In such cases, well-known structures, methods, devices, implementations, materials, or operations are not shown or described in detail.
The flow charts shown in the drawings are merely illustrative and do not necessarily include all of the contents and operations/steps, nor do they necessarily have to be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.
The terms "first," "second," and the like in the description and claims of the present application and in the above-described drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.
FIG. 1 shows a system architecture diagram according to an example embodiment of the present application. Referring now to fig. 1, a detailed description of a system architecture according to an exemplary embodiment of the present application is provided.
The cloud resources shown in fig. 1 are cloud hosts purchased from cloud vendors. Cloud manufacturers include Ali, Tengchong, Huaqi, etc.
The user operates through front-end reference.
The back-end API interface is used to provide data lookup for the front-end.
The back-end API interface is also used for receiving a request sent by the system script timing task to inquire the state of the host in storage so as to ensure the consistency with the host information provided by the cloud manufacturer;
the back-end API interface is also used for calling the interface to inquire the service node information supported by the system and sending the service node information to the front end for display for configuration selection.
The back-end API interface is also used for calling the API interface of the cloud manufacturer to acquire the host list and selecting the cloud host to be purchased according to the user requirement. Thereafter, an initializing host message is sent to the RabbitMQ message queue.
And the RabbitMQ message queue sends the message to a script scheduling center and starts an initialization task. And the script scheduling center calls the corresponding script to execute according to the host configuration service node information inquired in the MySQL. And after the service node configured by the host is executed, the script scheduling center calls a back-end API (application program interface) to record the newly generated host into the asset library.
According to the system architecture shown in fig. 1 and according to the exemplary embodiment of the present application, through cooperation of the front end and the back end for data and scheduling of task execution by the scheduling center, a user can view an execution state of a current task through presentation of a front end page. Each time of scheduling and executing of the script scheduling center, the current state of the executing state of the service node is changed in time, and error information is written in when the executing fails, so that the current state can be displayed and visualized in time.
Fig. 2 is a block diagram of a cloud resource management system based on a multi-cloud architecture according to an example embodiment of the present application. A cloud resource management system based on a multi-cloud architecture according to an exemplary embodiment of the present application will be described in detail below with reference to fig. 2.
As shown in fig. 2, a cloud resource management system based on a multi-cloud architecture includes a cloud resource obtaining module 201, a cloud resource querying module 203, an execution service node module 205, a service node configuration state obtaining module 207, a service node configuration state displaying module 209, a service node configuration completion determining module 211, and a cloud resource warehousing module 213.
The cloud resource acquiring module 201 is configured to acquire cloud resources to be managed. According to some embodiments, the cloud resources include cloud hosts, RDS, Redis.
According to some embodiments of the present application, the cloud resource acquiring module 201 is configured to acquire cloud resources that have been purchased from various cloud vendors and have not been configured yet.
The cloud resource query module 203 is configured to query service node information corresponding to the cloud resource. The service node information comprises at least one service node with configurable cloud resources.
According to some embodiments of the present application, the service node includes initializing a host script service, joining a bastion system service, joining a zabbix service, joining a configuration management system service, joining a container management platform service, and/or joining a kubernets cluster service.
The service node executing module 205 is configured to configure at least one service node for the cloud resource, where the at least one service node includes a first service node and a second service node, the configuration process of the first service node and the configuration process of the second service node are not in a sequential relationship, and the configuration result of the first service node does not affect the second service node.
According to some embodiments, there is no restriction on execution order among a plurality of service nodes for the configuration of the cloud resource, and whether one service node is executed successfully does not affect the execution of other service nodes.
According to some embodiments, if the service node fails to be configured, it is verified again whether the service node is successfully configured after a certain time interval, for example, 10 minutes. And if the configuration is still unsuccessful, storing the configuration state and the configuration failure reason of the service node into a database for a worker to check, and manually configuring the service node. For example, calling a service script of the service node by using Paramiko, storing the message in a message queue, waiting for a verification script execution result, such as a RabbitMQ, completing the execution of the service node if the verification is passed, and circularly calling the verification if the verification is not passed.
According to some embodiments, initializing the host script service is done by executing a shell script remotely using Paramiko. The shell script contains host initialization commands. Paramiko is SSH2 remote secure connection realized based on python, and supports authentication and key modes. The functions of remote command execution, file transmission, intermediate SSH proxy and the like can be realized.
According to some embodiments, the baster system comprises a Jumpsserver. Jumpserver is a springboard machine/bastion machine system written by python, is an operation and maintenance safety audit system containing authentication, authorization, account number and audit, and meets the management requirements of enterprises on cloud resources in a multi-cloud environment in a software subscription service or software and hardware integrated machine mode.
According to some embodiments of the application, the bastion machine system service is added to the bastion machine by calling an HTTP interface, so that a demand side can log in the system to use the machine after the machine is added.
Zabbix is a distributed network monitoring management system based on a WEB interface. According to some embodiments, adding zabbix is adding the newly created cloud resource to zabbix by invoking the zabbix system.
The adding configuration management system is to use Salt to issue a general configuration information instruction file storing cloud resources to each cloud resource, and to add the cloud resources to the configuration management system in the form of an HTTP interface. Salt is implemented by using Pathon, and can help operation and maintenance personnel to manage configuration files according to the production environment of the operation and maintenance personnel.
According to some embodiments, the container management platform is used for managing containers owned by each cloud resource, such as dockers, and displaying the contents of the containers. According to some embodiments, the joining container management platform service joins the cloud resources into the resource groups of the container in the form of an HTTP interface, which facilitates subsequent implementation of cloud resource management in the container management platform. For example, start-up containers, destroy containers.
Kubernets is an open source system for automatically deploying, extending and managing containerized applications. At present, each cloud manufacturer has a self-built kubernets cluster. According to some embodiments, joining the kubernets cluster service is to join cloud resources into the kubernets cluster, so that automatic operation is achieved.
The service node configuration status obtaining module 207 is configured to obtain a configuration status of the at least one service node.
According to some embodiments, the configuration state of the service node comprises configuration in, configuration complete. According to some embodiments, the configuration completion includes a configuration success and a configuration failure.
According to some embodiments of the present application, the configuration state of the service node acquired by the service node configuration state acquiring module 207 is to provide data for the service node configuration state displaying module 209, so as to realize timely display and visualization of the current execution state of the service node.
The service node configuration status display module 209 is configured to display a configuration status of at least one service node.
According to some embodiments of the present application, the service node configuration state display module 209 is configured to display the configuration state of the service node, so as to enable timely display and visualization of the current execution state of the service node. According to some embodiments, the service node configuration state display module 209 is further configured to display service node information corresponding to the cloud resource queried by the cloud resource querying module 203, and display the service node information that needs to be executed by the cloud resource.
The service node configuration completion determining module 211 is configured to determine whether configuration of at least one service node is completed.
According to some embodiments, the service node configuration completion determining module 213 is configured to determine whether the service node is configured completely. According to some embodiments, the completion of configuration is noted whenever the execution is completed, regardless of whether the service node's configuration state is successful or not. According to some embodiments, after all the service nodes required to be configured by the cloud resources are executed, the cloud resources are put into storage.
The cloud resource warehousing module 213 is configured to persist the configured cloud resources.
According to some embodiments, the cloud resource warehousing module 213 is configured to persist, in the database, the cloud resources that are completely executed by the service node.
According to some embodiments, the cloud resource management system further includes a cloud resource warehousing status updating module, configured to update warehousing information of the cloud resources, so as to ensure consistency with persistent cloud resource information of a cloud vendor. For example, persistent cloud resource information of a cloud manufacturer is obtained by calling a cloud resource list interface provided by the cloud manufacturer and is compared with the cloud resource information stored in a warehouse, so that cloud resource data synchronization is realized.
According to some embodiments, the cloud resource management system further comprises a message queue module for storing at least one service node task that needs to be executed.
According to some embodiments, the cloud resource management system further includes a service node script scheduling module, configured to invoke a task script corresponding to the at least one service node according to the at least one service node task.
According to some embodiments, the cloud resource management system further comprises a cloud resource starting module for starting the cloud resource before the cloud resource configures the at least one service node.
According to some embodiments, the cloud resource management system further comprises a cloud resource creation module for creating cloud resources according to user requirements.
According to the cloud resource management system shown in fig. 2, different service node combinations are configured in different application scenarios by flexibly configuring service nodes for a cloud host, so as to achieve different cloud resource initialization effects required in different application scenarios.
Fig. 3 illustrates a block diagram of a creating cloud asset module based on a multi-cloud architecture according to an example embodiment of the present application. A creating cloud asset module based on a multi-cloud architecture according to an exemplary embodiment of the present application will be described in detail with reference to fig. 3.
Referring to fig. 3, a cloud asset creation module based on a multi-cloud architecture includes a cloud resource demand obtaining unit 301, a cloud resource list obtaining unit 303, a cloud resource selecting unit 305, a cloud resource confirming unit 307, and a cloud resource snapshot unit 309.
The cloud resource requirement obtaining unit 301 is configured to obtain a cloud resource requirement of a user.
According to some embodiments, a cloud resource information description template is formulated according to cloud resource description information of cloud vendors. And configuring the cloud resource requirements according to the cloud resource information description template.
According to some embodiments, the cloud resource description names of the cloud vendors are not uniform. Therefore, when the cloud resource information description template is formulated, the cloud resource information description template needs to correspond to the cloud resource description names of cloud manufacturers.
The cloud resource list acquiring unit 303 is configured to acquire a cloud resource list of at least one cloud vendor.
According to some embodiments, the cloud resource list acquiring unit 303 uses the cloud resource list interfaces of the cloud manufacturers to collect the cloud resource lists of the cloud manufacturers, so that the cloud resources can be selected conveniently according to the cloud resource requirements acquired by the cloud resource requirement acquiring unit 301.
The cloud resource selecting unit 305 is configured to select a cloud resource satisfying the cloud resource requirement from the cloud resource list.
According to some embodiments, the cloud resource selecting unit 305 selects a cloud resource satisfying a requirement from cloud resources of cloud manufacturers according to the cloud resource requirement acquired by the cloud resource requirement acquiring unit 301 and the cloud resource category acquired by the cloud resource list acquiring unit 303.
The cloud resource confirming unit 307 is configured to confirm the cloud resource information selected by the cloud resource selecting unit.
According to some embodiments, the cloud resource information comprises details of a service on which the cloud resource is started, a quantity of the cloud resource, hardware information of the cloud resource, software information of the cloud resource, and/or a price of the cloud resource.
According to some embodiments, the cloud resource information further comprises service node information configured for the cloud resource.
The cloud resource snapshot unit 309 is configured to save cloud resource information.
According to some embodiments, after the cloud resource is confirmed, the cloud resource snapshot unit 309 creates a snapshot for the created cloud resource, so that asset tracing is facilitated.
According to the cloud asset creating module shown in fig. 3, by abstracting the common content of the cloud resources of the cloud manufacturers into the unified template, when the cloud resources are purchased, only the host needs to be purchased according to the template, so that the problem that the user needs to purchase the cloud resources individually is solved, the time is saved, and the labor cost is reduced.
An electronic device 200 according to this embodiment of the present application is described below with reference to fig. 4. The electronic device 200 shown in fig. 4 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.
As shown in fig. 4, the electronic device 200 is embodied in the form of a general purpose computing device. The components of the electronic device 200 may include, but are not limited to: at least one processing unit 210, at least one memory unit 220, a bus 230 connecting different system components (including the memory unit 220 and the processing unit 210), a display unit 240, and the like. Wherein the storage unit stores program code that can be executed by the processing unit 210 such that the processing unit 210 performs the methods according to various exemplary embodiments of the present application described herein. For example, processing unit 210 may execute a cloud resource management system as shown in fig. 2.
The storage unit 220 may include readable media in the form of volatile storage units, such as a random access memory unit (RAM) 2201 and/or a cache memory unit 2202, and may further include a read only memory unit (ROM) 2203.
The storage unit 220 may also include a program/utility 2204 having a set (at least one) of program modules 2205, such program modules 2205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
Bus 230 may be one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.
The electronic device 200 may also communicate with one or more external devices 300 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 200, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 200 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 250. Also, the electronic device 200 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the Internet) via the network adapter 260. The network adapter 260 may communicate with other modules of the electronic device 200 via the bus 230. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 200, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. The technical solution according to the embodiments of the present application may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, or a network device, etc.) to execute the above method according to the embodiments of the present application.
The software product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
A computer readable storage medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable storage medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
The computer readable medium carries one or more programs which, when executed by a device, cause the computer readable medium to perform the functions described above.
Those skilled in the art will appreciate that the modules described above may be distributed in the apparatus according to the description of the embodiments, or may be modified accordingly in one or more apparatuses unique from the embodiments. The modules of the above embodiments may be combined into one module, or further split into multiple sub-modules.
According to some example embodiments of the application, different service node combinations are configured in different application scenes by flexibly configuring service nodes for a cloud host, so that different cloud resource initialization effects required in different application scenes are achieved.
According to some embodiments of the application, the common content of the cloud resources of the cloud manufacturers is abstracted into the unified template, when the cloud resources are purchased, only the host computer needs to be purchased according to the template, the problem that the user needs to purchase the cloud resources individually is avoided, the time is saved, and the labor cost is reduced.
The foregoing detailed description of the embodiments of the present application has been presented to illustrate the principles and implementations of the present application, and the description of the embodiments is only intended to facilitate the understanding of the methods and their core concepts of the present application. Meanwhile, a person skilled in the art should, according to the idea of the present application, change or modify the embodiments and applications of the present application based on the scope of the present application. In view of the above, the description should not be taken as limiting the application.

Claims (8)

1. A cloud resource management system based on a multi-cloud architecture, comprising:
the cloud resource acquisition module is used for acquiring cloud resources to be managed by utilizing a unified template according to business requirements, wherein the cloud resources are purchased and not initialized and configured;
the cloud resource query module is used for querying service node information corresponding to the cloud resources, the service node information comprises at least one service node which is configurable by the cloud resources, and the service node comprises an initialization host script service, a bastdata server adding system service, a zabbix adding service, a configuration management system adding service, a container management platform adding service and/or a kubernets cluster adding service;
the service node execution module comprises a message queue module and a service node script scheduling module, and the service node script scheduling module executes a task script corresponding to a service node task according to the service node task to be executed and stored in the message queue module so as to realize the initial configuration of the cloud resources;
a service node configuration state obtaining module, configured to obtain a configuration state of the at least one service node;
the service node configuration state display module is used for displaying the configuration state of the at least one service node;
a service node configuration completion judging module, configured to judge whether configuration of the at least one service node is completed;
and the cloud resource storage module is used for persisting the configured cloud resources.
2. The cloud resource management system of claim 1, wherein:
the cloud resources comprise a cloud host, RDS and Redis.
3. The cloud resource management system of claim 2, wherein the cloud resource management system further comprises:
and the cloud resource creating module is used for creating the cloud resources according to the user requirements.
4. The cloud resource management system of claim 3, wherein the cloud resource creation module comprises:
the cloud resource demand acquisition unit is used for acquiring the cloud resource demand of the user;
the cloud resource list acquiring unit is used for acquiring a cloud resource list of at least one cloud manufacturer;
the cloud resource selection unit is used for selecting the information of the cloud resources meeting the cloud resource requirements from the cloud resource list;
a cloud resource confirming unit configured to confirm the cloud resource selected by the cloud resource selecting unit;
and the cloud resource snapshot unit is used for storing the information of the cloud resources.
5. The cloud resource management system of claim 4, wherein:
the information of the cloud resources comprises service details relied on when the cloud resources are started, the quantity of the cloud resources, hardware information of the cloud resources, software information of the cloud resources and/or prices of the cloud resources.
6. The cloud resource management system of claim 1, wherein the cloud resource management system further comprises:
and the cloud resource warehousing state updating module is used for updating warehousing information of the cloud resources so as to ensure that the warehousing information is consistent with the information of the cloud resources which are persisted by the cloud manufacturer.
7. The cloud resource management system of claim 1, wherein the cloud resource management system further comprises:
and the cloud resource starting module is used for starting the cloud resources before the cloud resources configure the at least one service node.
8. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the cloud resource management system of any of claims 1-7.
CN202111480005.5A 2021-12-07 2021-12-07 Cloud resource management system based on multi-cloud architecture and electronic equipment Active CN113886093B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111480005.5A CN113886093B (en) 2021-12-07 2021-12-07 Cloud resource management system based on multi-cloud architecture and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111480005.5A CN113886093B (en) 2021-12-07 2021-12-07 Cloud resource management system based on multi-cloud architecture and electronic equipment

Publications (2)

Publication Number Publication Date
CN113886093A CN113886093A (en) 2022-01-04
CN113886093B true CN113886093B (en) 2022-04-29

Family

ID=79015689

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111480005.5A Active CN113886093B (en) 2021-12-07 2021-12-07 Cloud resource management system based on multi-cloud architecture and electronic equipment

Country Status (1)

Country Link
CN (1) CN113886093B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115604101B (en) * 2022-09-29 2024-02-02 北京亚控科技发展有限公司 System management method and related equipment

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101826498B1 (en) * 2017-05-02 2018-02-07 나무기술 주식회사 Cloud platform system
CN108809715A (en) * 2018-06-11 2018-11-13 郑州云海信息技术有限公司 A kind of method and device of deployment management platform
CN108924217B (en) * 2018-06-29 2020-12-22 中山大学 Automatic deployment method of distributed cloud system
CN109120444B (en) * 2018-08-21 2021-06-29 陆明 Cloud resource management method, processor and storage medium
CN111475728B (en) * 2020-04-07 2023-04-07 腾讯云计算(北京)有限责任公司 Cloud resource information searching method, device, equipment and storage medium
CN111580930A (en) * 2020-05-09 2020-08-25 山东汇贸电子口岸有限公司 Native cloud application architecture supporting method and system for domestic platform
CN111708632A (en) * 2020-05-19 2020-09-25 中国人民财产保险股份有限公司 Cloud resource management method and device
CN112328390B (en) * 2020-10-13 2024-02-09 北京华胜天成科技股份有限公司 Method, device and storage medium for automatically implementing cloud management platform
CN112256439B (en) * 2020-12-08 2021-04-20 富通云腾科技有限公司 Service directory dynamic updating system and method based on cloud computing resource pool

Also Published As

Publication number Publication date
CN113886093A (en) 2022-01-04

Similar Documents

Publication Publication Date Title
CN111279321B (en) Binding backend service endpoints to API functions in an API registry
CN107370786B (en) General information management system based on micro-service architecture
US8881136B2 (en) Identifying optimal upgrade scenarios in a networked computing environment
US9176711B2 (en) System and method for automated on-demand creation of a customized software application
US9092243B2 (en) Managing a software appliance
US8924920B2 (en) Providing a software appliance based on a role
US10177992B2 (en) Application store interface for remote management of client devices
US20150271014A1 (en) Automatic configuration of new components by infrastructure management software
US20060168575A1 (en) Defining a software deployment
CN111357241B (en) System and method for integrating cloud applications into a cloud service proxy platform using automated universal connector packaging
US9912759B2 (en) Dynamically generating solution stacks
US20190045360A1 (en) Flexible remote server validation
KR101086620B1 (en) Smart office system and server for managing the sames and method for managing the sames
CN114115838A (en) Data interaction method and system based on distributed components and cloud platform
CN113886093B (en) Cloud resource management system based on multi-cloud architecture and electronic equipment
US10452371B2 (en) Automating enablement state inputs to workflows in z/OSMF
CN114661375A (en) Application integration method and device
CN113849399A (en) Automatic testing system and method for multi-machine cooperative software under multi-localization platform
CN116243929A (en) Automatic code package release system
CN115469807A (en) Disk function configuration method, device, equipment and storage medium
CN112579165A (en) Batch operation execution method and device, readable medium and electronic equipment
Sato Devops in Practice: Reliable and automated software delivery
US20240054066A1 (en) Portable binary files for client side execution of federated application programming interfaces
US20230103896A1 (en) Configuring dynamic interactions between application elements
US20230315723A1 (en) Low-development system for dynamic information queries

Legal Events

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