CN112202879A - Middleware management method and device, electronic equipment and storage medium - Google Patents
Middleware management method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112202879A CN112202879A CN202011051274.5A CN202011051274A CN112202879A CN 112202879 A CN112202879 A CN 112202879A CN 202011051274 A CN202011051274 A CN 202011051274A CN 112202879 A CN112202879 A CN 112202879A
- Authority
- CN
- China
- Prior art keywords
- middleware
- container
- service
- module
- management
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000007726 management method Methods 0.000 title claims abstract description 97
- 241000380131 Ammophila arenaria Species 0.000 claims abstract description 23
- 238000012544 monitoring process Methods 0.000 claims abstract description 22
- 238000000034 method Methods 0.000 claims abstract description 20
- 238000006243 chemical reaction Methods 0.000 claims description 11
- 230000008569 process Effects 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 6
- 230000006870 function Effects 0.000 claims description 6
- 238000012545 processing Methods 0.000 claims description 5
- 230000002159 abnormal effect Effects 0.000 claims description 3
- 238000013079 data visualisation Methods 0.000 claims description 3
- 238000012217 deletion Methods 0.000 claims description 3
- 230000037430 deletion Effects 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000002360 explosive Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/61—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources taking into account QoS or priority requirements
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the invention discloses a middleware management method and device, electronic equipment and a storage medium, and relates to the field of cloud computing. The middleware management method comprises the following steps: receiving a middleware service request and performing authentication operation, wherein the middleware service request comprises service type and priority information; constructing a middleware message body corresponding to the service type according to the middleware service request; and deploying container middleware through a package manager helm according to the middleware message body, wherein the container middleware comprises terminal service, monitoring service, management service and log service. The method is applied to a middleware management platform, and achieves the purposes of uniformly managing the middleware and reducing mutual interference among the middleware.
Description
Technical Field
The embodiment of the invention relates to the field of cloud computing, in particular to a middleware management method and device, electronic equipment and a storage medium.
Background
With the explosive development of cloud computing technology, more and more enterprises adopt middleware to manage various systems and connect communication media. For the management and deployment problem of the middleware, an automated operation and maintenance tool is generally adopted in a traditional mode to deploy the middleware service on a cloud host or a physical machine according to different requirements of users.
However, when the traditional deployment method is deployed by using an automation operation and maintenance tool, due to the difference in operation modes between different tools, there is a great difference in configuration and dependency environment between the middleware deployed by one host, so that uniform management cannot be performed when the middleware is managed and isolation between middleware services is poor, which results in high management cost of the middleware and interference between different middleware.
Disclosure of Invention
An object of embodiments of the present invention is to provide a middleware management method, an apparatus, an electronic device, and a storage medium, which can uniformly manage deployed middleware without mutual interference between the middleware.
In order to solve the above technical problem, an embodiment of the present invention provides a middleware management method, including: receiving a middleware service request and performing authentication operation, wherein the middleware service request comprises service type and priority information; constructing a middleware message body corresponding to the service type according to the middleware service request; and deploying container middleware through a package manager helm according to the middleware message body, wherein the container middleware comprises terminal service, monitoring service, management service and log service.
An embodiment of the present invention further provides a middleware management apparatus, including:
the middleware service entrance is used for receiving a middleware service request and performing authentication operation, wherein the middleware service request comprises service type and priority information;
the API gateway module is connected with the middleware service inlet and used for constructing a middleware message body corresponding to the service type according to the middleware service request;
the K8S cluster module is connected with the API gateway module and used for deploying container middleware through a package manager helm according to the middleware message body, wherein the container middleware comprises terminal service, monitoring service, management service and log service;
the cluster management module is connected with the K8S cluster module and is used for updating the configuration information of the container middleware through a container management platform Rancher when detecting whether the configuration information of the container middleware needs to be updated;
and the Ceph cluster module is used for acquiring and storing the data information of the container middleware.
An embodiment of the present invention also provides an electronic device, including:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the middleware management method described above.
An embodiment of the present invention further provides a computer-readable storage medium storing a computer program, wherein the computer program is configured to implement the middleware management method described above when executed by a processor.
Compared with the prior art, the management platform receives the middleware service request and performs authentication operation, wherein the middleware service request comprises service type and priority information, and a middleware message body corresponding to the service type is constructed according to the middleware service request; the container middleware is deployed through the bag manager palm according to the middleware message body, wherein the container middleware comprises terminal service, monitoring service, management service and log service, the container middleware is deployed through the bag manager palm, the difference among the deployed container middleware is reduced, the container middleware is conveniently and uniformly managed, each container middleware is an independent environment, the mutual interference among the container middleware is avoided, and the problems that the deployed middleware cannot be uniformly managed and the middleware is easily interfered with each other in the prior art are solved.
In addition, a middleware management method according to an embodiment of the present invention is a middleware management method for constructing a middleware message body corresponding to the service type according to the middleware service request, including: acquiring a middleware message queue according to the middleware service request, and setting a priority for the middleware message queue according to the priority information, wherein the priority information comprises a product information influence factor, a project information influence factor and a weighted priority parameter; performing format conversion on the middleware message queue according to the service type; and constructing the middleware message body according to the middleware message queue after the format conversion and the priority information. According to the technical scheme provided by the invention, when the middleware message body is constructed, different types of middleware message bodies can be constructed according to the service type, and the construction sequence is felt according to the priority information, so that the method and the device can realize reasonable scheduling of tasks, are suitable for more application scenes, and have wider application range.
In addition, the middleware management method according to an embodiment of the present invention, before deploying container middleware by a package manager helm according to the middleware message body, further includes: acquiring network resources required by deploying the container middleware, and judging whether the network resources are sufficient or not; if the network resources are insufficient, an alarm is sent to a user; and if the network resources are sufficient, deploying the container middleware through a packet manager helm according to the middleware message body. According to the technical scheme provided by the invention, the condition of network resources can be checked before the container middleware is deployed, and the container middleware can be constructed only under the condition of sufficient resources, so that the failure of constructing the container middleware caused by limited resources is avoided, the success rate and the efficiency of constructing the container middleware can be improved, and the practicability is stronger.
In addition, the middleware management method according to an embodiment of the present invention, after deploying container middleware by a package manager helm according to the middleware message body, further includes: judging whether the container middleware is deployed successfully; if the container middleware is deployed successfully, returning a deployment result to a user; and if the deployment of the container middleware fails, deleting the abnormal container middleware and sending an alarm to a user. According to the technical scheme provided by the invention, whether the container middleware is successfully deployed or not can be checked after the container middleware is constructed, and the container middleware is returned to the user, so that the user can know the deployment result of the container middleware, and the use feeling of the user can be improved.
In addition, the middleware management method according to an embodiment of the present invention, after deploying container middleware by a package manager helm according to the middleware message body, further includes: and acquiring and storing the data information of the container middleware, wherein when the data information is detected to need updating, the data information is updated through a container management platform Rancher. The technical scheme provided by the invention can realize the unified storage of the data information of the container middleware after the container middleware is deployed, and complete the data updating operation of the container middleware, so that the invention can realize the persistent storage of the container middleware and ensure the effectiveness of the data information.
In addition, the middleware management method according to an embodiment of the present invention, after deploying container middleware by a package manager helm according to the middleware message body, further includes: and acquiring and storing the data information of the container middleware, wherein when the data information is detected to need updating, the data information is updated through a container management platform Rancher. The technical scheme provided by the invention can completely store the data information of the container middleware, completes the updating operation of the data information of the container middleware, and can ensure the validity of the data information of the container middleware, so that the invention can improve the stability of the deployed container middleware.
In addition, in the middleware management apparatus according to an embodiment of the present invention, the API gateway module includes: the message queue module is used for acquiring a middleware message queue according to the middleware service request, setting a priority for the middleware message queue according to the priority information, performing format conversion on the middleware message queue according to the service type, and constructing a middleware message body according to the middleware message queue after the format conversion, wherein the priority information comprises a product information influence factor, a project information influence factor and a weighted priority parameter; the load balancing module is used for assisting the message queue module to process the middleware service request; and the alarm module is used for monitoring the processing state and the result of the middleware service request and the state of the K8S cluster module and sending an alarm to a user when an exception occurs. The technical scheme provided by the invention can realize the functions of reasonably scheduling, distributing and monitoring the deployment middleware tasks, ensure the successful creation of the container middleware and realize the efficient and high-success-rate deployment of the container middleware.
In addition, in the middleware management apparatus according to an embodiment of the present invention, the K8S cluster module includes: the Helm management module is used for deploying the container middleware and configuring the container middleware; the mirror image warehouse management module is used for acquiring the mirror images of the container middleware from the mirror image warehouse and uniformly managing the acquired mirror images; the delivery module is interacted with the Helm management module and used for finishing the deployment and deletion of the container middleware; the terminal module is used for providing terminal service for the container middleware; the monitoring module is used for acquiring monitoring sample data of the container middleware and performing data visualization on the monitoring sample data; the management module is used for providing a management service function for the container middleware; the resource scheduling module is used for acquiring network resources required by deploying the container middleware and judging whether the network resources are sufficient or not; and the log module is used for collecting log data generated in the running process of the container middleware. The technical scheme provided by the invention can realize the operation and maintenance management work in the container middleware deployment process and after the deployment is successful, so that the invention can realize the unified management of the container middleware.
Drawings
One or more embodiments are illustrated by way of example in the accompanying drawings, which correspond to the figures in which like reference numerals refer to similar elements and which are not to scale unless otherwise specified.
FIG. 1 is a flowchart of a middleware management method according to a first embodiment of the present invention;
FIG. 2 is a flowchart of step 102 of the middleware management method provided by the first embodiment of the invention shown in FIG. 1;
FIG. 3 is a flowchart of a middleware management method according to a second embodiment of the present invention;
FIG. 4 is a flowchart of a middleware management method according to a third embodiment of the present invention;
FIG. 5 is a flowchart of a middleware management method according to a fourth embodiment of the present invention;
fig. 6 is a schematic structural diagram of a middleware management device provided in a fifth embodiment of the present invention;
fig. 7 is a schematic structural diagram of a middleware management apparatus according to a sixth embodiment of the present invention;
fig. 8 is a schematic structural diagram of a middleware management apparatus according to a seventh embodiment of the present invention;
fig. 9 is a schematic structural diagram of an electronic device according to an eighth embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. However, it will be appreciated by those of ordinary skill in the art that numerous technical details are set forth in order to provide a better understanding of the present application in various embodiments of the present invention. However, the technical solution claimed in the present application can be implemented without these technical details and various changes and modifications based on the following embodiments. The following embodiments are divided for convenience of description, and should not constitute any limitation to the specific implementation manner of the present invention, and the embodiments may be mutually incorporated and referred to without contradiction.
A first embodiment of the present invention relates to a middleware management method, as shown in fig. 1, specifically including:
In this embodiment, the middleware service request is received through a middleware service entry, the middleware service request is a web request sent by a user, the middleware service request carries a service type of the middleware and corresponding priority information in addition to basic information carried by a general web request, where the service type specifies a type of the container middleware constructed, the priority information specifies a sequence of constructing the container middleware, and the authentication operation on the middleware service request is performed from user authentication and network authentication, which may include user authentication, authority authentication, whether the service request is legal, whether the user accesses an illegal network, and the like.
And 102, constructing a middleware message body corresponding to the service type according to the middleware service request.
Specifically, as shown in fig. 2, step 102 further includes:
In this embodiment, first, a middleware message queue is obtained according to a received middleware service request, and then a priority is set for the middleware message queue according to priority information carried by the middleware service request, so as to ensure that the container middleware is constructed in order, where the priority information includes a product information impact factor, an item information impact factor, a weighted priority parameter, and the like, for example: when the service type is a resource application, if the product information impact factor of the middleware message queue 1 is a01, the item information impact factor is a02, and the weighted priority parameter is 0.85 (no weighting is performed), and if the product information impact factor of the middleware message queue 2 is a11, the item information impact factor is a12, and the weighted priority parameter is 0.95 (weighting is performed), the priority of the middleware message queue 2 is greater than that of the middleware message queue 1.
In this embodiment, the format of the middleware message queue obtained in step 201 needs to be converted into a middleware message queue corresponding to the service type according to the service type carried by the middleware service request, and the middleware message queue needs to be converted into a database type middleware message queue by taking the service type as the database type as an example.
And step 203, constructing a middleware message body according to the middleware message queue after format conversion and the priority information.
In this embodiment, a middleware message body is constructed according to priority information from a middleware message queue, and then the constructed middleware message body is issued.
103, deploying container middleware through a package manager helm according to a middleware message body, wherein the container middleware comprises terminal service, monitoring service, management service and log service.
In this embodiment, when receiving the delivered middleware message body, the package manager palm deploys the corresponding container middleware according to the service type of the middleware message body, where the deployed container middleware may include services such as terminal service, monitoring service, management service, log service, and the like.
Compared with the prior art, the management platform receives the middleware service request and performs authentication operation, wherein the middleware service request comprises service type and priority information, and a middleware message body corresponding to the service type is constructed according to the middleware service request; the container middleware is deployed through the bag manager palm according to the middleware message body, wherein the container middleware comprises terminal service, monitoring service, management service and log service, the container middleware is deployed through the bag manager palm, the difference between the deployed container middleware is reduced, the container middleware is convenient to manage uniformly, each container middleware is an independent environment, mutual interference between the container middleware is avoided, the problems that the deployed middleware cannot be managed uniformly in the prior art and mutual interference between the middleware is easy to happen are solved, meanwhile, the container middleware and the service are deployed in a Helm mode, the number of virtual machines for starting and managing can be reduced, the storage and the memory reduce the overall calculation overhead, the platform development and operation and maintenance cost is reduced, and the platform development and operation and maintenance cost is more economical.
A second embodiment of the present invention relates to a middleware management method, which is substantially the same as the middleware management method provided in the first embodiment of the present invention, and the difference is that whether network resources are sufficient needs to be determined between deployment container middleware, as shown in fig. 3, the method specifically includes:
In this embodiment, before deploying the container middleware, interaction with a resource storage module (in the present invention, a Ceph cluster module) at the bottom layer is required, a network resource required by the container middleware is acquired, after the network resource is acquired, whether the currently remaining network resource is sufficient is determined, if the network resource is sufficient, step 103 is executed, and if the network resource is insufficient, step 302 is known, wherein when the network resource is acquired, a memory resource, a CPU resource, a storage resource, and the like corresponding to the container middleware are also required to be acquired, and when it is determined that the network resource is sufficient, whether resources such as a memory resource, a CPU resource, a storage resource, and the like are sufficient is also determined, and the determination result is fed back together with the determination result of the network resource.
Step 302, an alert is initiated to a user.
In this embodiment, when the network resource is insufficient, the middleware request is considered to be failed to execute, an alarm is formed through the alarm module, and the administrator is notified of the failure through a third-party platform such as enterprise WeChat, email and the like to process the failure.
It should be noted that the present embodiment does not limit the specific execution positions of steps 301 and 302, and steps 301 and 302 may be performed multiple times in the present invention, and only when the current operation changes, it is necessary to determine whether the resources are sufficient.
Compared with the prior art, the implementation mode of the invention has the advantages that on the basis of realizing the beneficial effects brought by the first implementation mode, the network resource condition can be checked before the container middleware is deployed, and the container middleware can be constructed only under the condition of sufficient resources, so that the failure of constructing the container middleware due to limited resources is avoided, the success rate and the efficiency of constructing the container middleware can be improved, and the practicability is stronger.
A third embodiment of the present invention relates to a middleware management method, which is substantially the same as the middleware management method provided in the first embodiment, except that, as shown in fig. 4, after step 103, the method further includes:
In this embodiment, after the container middleware is deployed, it is determined whether the container middleware is successfully deployed, if the container middleware is successfully deployed, step 402 is executed, and if the container middleware is unsuccessfully deployed, step 403 is executed.
In this embodiment, when the container middleware is successfully deployed, a deployment result is returned to the user, and the user is informed that the container middleware can enter a use state.
And step 403, deleting the abnormal container middleware and initiating an alarm to the user.
In this embodiment, when the deployment of the container middleware fails, the contents of the container middleware that needs to be deleted and deployed are first deleted, then an alarm is formed through the alarm module, and the third-party platform such as enterprise WeChat and email informs an administrator of the processing.
Compared with the prior art, on the basis of realizing the beneficial effects brought by the first embodiment, whether the container middleware is successfully deployed or not can be checked after the container middleware is constructed and returned to the user, so that the user can know the deployment result of the container middleware, and the use feeling of the user can be improved.
A fourth embodiment of the present invention relates to a middleware management method which is substantially the same as the middleware management method provided in the first embodiment, except that, as shown in fig. 5, after step 103, the method further includes:
In this embodiment, after the container middleware is deployed successfully, all data information of the deployed container middleware needs to be acquired and stored, and when it is detected that the data information of the deployed container middleware needs to be updated, the data information may be updated through the container management platform Rancher, where the data information of the container middleware may be acquired and stored through the Ceph cluster module, and the data information needs to be updated may be caused by an operation such as an operation error of the container middleware or whether the container middleware needs to expand or contract.
Compared with the prior art, on the basis of realizing the beneficial effects brought by the first embodiment, the embodiment of the invention can completely store the data information of the container middleware, complete the updating operation of the data information of the container middleware, and ensure the validity of the data information of the container middleware, so that the invention can improve the stability of the deployed container middleware.
In addition, it should be understood that the above steps of the various methods are divided for clarity, and the implementation may be combined into one step or split into some steps, and the steps are divided into multiple steps, so long as the same logical relationship is included in the protection scope of the present patent; it is within the scope of the patent to add insignificant modifications to the algorithms or processes or to introduce insignificant design changes to the core design without changing the algorithms or processes.
A fifth embodiment of the present invention relates to a middleware management apparatus, as shown in fig. 6, specifically including:
the middleware service entry 601 is configured to receive a middleware service request and perform authentication operation, where the middleware service request includes service type and priority information;
the API gateway module 602 is connected with the middleware service entrance and used for constructing a middleware message body corresponding to the service type according to the middleware service request;
the K8S cluster module 603 is connected with the API gateway module and used for deploying container middleware through a package manager helm according to a middleware message body, wherein the container middleware comprises terminal service, monitoring service, management service and log service;
the cluster management module 604 is connected to the K8S cluster module, and is configured to update the configuration information of the container middleware through the container management platform Rancher when detecting whether the configuration information of the container middleware needs to be updated;
and the Ceph cluster module 605 is configured to obtain and store data information of the container middleware.
A sixth embodiment of the present invention relates to a middleware management apparatus, which is basically the same as the middleware management apparatus provided in the fifth embodiment, and as shown in fig. 7, the API gateway module 602 further includes:
a message queue module 701, configured to obtain a middleware message queue according to a middleware service request, set a priority for the middleware message queue according to priority information, perform format conversion on the middleware message queue according to the service type, and construct a middleware message body according to the middleware message queue after format conversion, where the priority information includes a product information impact factor, a project information impact factor, and a weighted priority parameter;
a load balancing module 702, configured to process the middleware service request by the message coordination queue module;
and the alarm module 703 is configured to monitor a processing state and a result of the middleware service request and a state of the K8S cluster module, and send an alarm to a user when an exception occurs.
A seventh embodiment of the present invention relates to a middleware management apparatus, which is basically the same as the middleware management apparatus provided in the sixth embodiment, and as shown in fig. 8, the K8S cluster module 603 further includes:
a Helm management module 801, configured to deploy container middleware and configure the container middleware;
a mirror image warehouse management module 802, configured to acquire a mirror image of the container middleware from a mirror image warehouse, and perform unified management on the acquired mirror image;
the delivery module 803 interacts with the Helm management module and is used for completing the deployment and deletion of the container middleware;
a terminal module 804, configured to provide terminal services for the container middleware;
the monitoring module 805 is configured to obtain monitoring sample data of the container middleware, and perform data visualization on the monitoring sample data;
a management module 806, configured to provide a management service function for the container middleware;
a resource scheduling module 807 for acquiring network resources required by the middleware of the deployment container and determining whether the network resources are sufficient;
and the log module 808 is used for collecting log data generated in the running process of the container middleware.
It should be noted that, in a middleware management device, the K8S cluster module may include a plurality of modules.
It should be noted that each of the modules in the fifth to seventh embodiments is a logical module, and in practical applications, one logical unit may be one physical unit, may be a part of one physical unit, and may be implemented by a combination of a plurality of physical units. In addition, in order to highlight the innovative part of the present invention, the elements that are not so closely related to solving the technical problems proposed by the present invention are not introduced in the fifth to seventh embodiments, but this does not indicate that there are no other elements in the fifth to seventh embodiments.
An eighth embodiment of the present invention relates to an electronic apparatus, as shown in fig. 9, including:
at least one processor 901; and the number of the first and second groups,
a memory 902 communicatively connected to the at least one processor 901; wherein,
the memory 902 stores instructions executable by the at least one processor 901, so that the at least one processor 901 can execute the middleware management method according to any embodiment of the present invention.
Where the memory and processor are connected by a bus, the bus may comprise any number of interconnected buses and bridges, the buses connecting together one or more of the various circuits of the processor and the memory. The bus may also connect various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A bus interface provides an interface between the bus and the transceiver. The transceiver may be one element or a plurality of elements, such as a plurality of receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by the processor is transmitted over a wireless medium via an antenna, which further receives the data and transmits the data to the processor.
The processor is responsible for managing the bus and general processing and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And the memory may be used to store data used by the processor in performing operations.
A ninth embodiment of the present invention relates to a computer-readable storage medium storing a computer program. The computer program realizes the above-described method embodiments when executed by a processor.
That is, as can be understood by those skilled in the art, all or part of the steps in the method for implementing the embodiments described above may be implemented by a program instructing related hardware, where the program is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the method described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It will be understood by those of ordinary skill in the art that the foregoing embodiments are specific examples for carrying out the invention, and that various changes in form and details may be made therein without departing from the spirit and scope of the invention in practice.
Claims (10)
1. A middleware management method, comprising:
receiving a middleware service request and performing authentication operation, wherein the middleware service request comprises service type and priority information;
constructing a middleware message body corresponding to the service type according to the middleware service request;
and deploying container middleware through a package manager helm according to the middleware message body, wherein the container middleware comprises terminal service, monitoring service, management service and log service.
2. The middleware management method according to claim 1, wherein said building a middleware message body corresponding to the service type according to the middleware service request comprises:
acquiring a middleware message queue according to the middleware service request, and setting a priority for the middleware message queue according to the priority information, wherein the priority information comprises a product information influence factor, a project information influence factor and a weighted priority parameter;
performing format conversion on the middleware message queue according to the service type;
and constructing the middleware message body according to the middleware message queue after the format conversion and the priority information.
3. The middleware management method according to claim 1, wherein before deploying container middleware by a package manager helm according to the middleware message body, further comprising:
acquiring network resources required by deploying the container middleware, and judging whether the network resources are sufficient or not;
if the network resources are insufficient, an alarm is sent to a user;
and if the network resources are sufficient, deploying the container middleware through a packet manager helm according to the middleware message body.
4. The middleware management method according to claim 1, further comprising after said deploying container middleware by a package manager helm according to the middleware message body:
judging whether the container middleware is deployed successfully;
if the container middleware is deployed successfully, returning a deployment result to a user;
and if the deployment of the container middleware fails, deleting the abnormal container middleware and sending an alarm to a user.
5. The middleware management method according to claim 1, further comprising after said deploying container middleware by a package manager helm according to the middleware message body:
and acquiring and storing the data information of the container middleware, wherein when the data information is detected to need updating, the data information is updated through a container management platform Rancher.
6. A middleware management apparatus, comprising:
the middleware service entrance is used for receiving a middleware service request and performing authentication operation, wherein the middleware service request comprises service type and priority information;
the API gateway module is connected with the middleware service inlet and used for constructing a middleware message body corresponding to the service type according to the middleware service request;
the K8S cluster module is connected with the API gateway module and used for deploying container middleware through a package manager helm according to the middleware message body, wherein the container middleware comprises terminal service, monitoring service, management service and log service;
the cluster management module is connected with the K8S cluster module and is used for updating the configuration information of the container middleware through a container management platform Rancher when detecting whether the configuration information of the container middleware needs to be updated;
and the Ceph cluster module is used for acquiring and storing the data information of the container middleware.
7. The middleware management apparatus according to claim 6 wherein the API gateway module comprises:
the message queue module is used for acquiring a middleware message queue according to the middleware service request, setting a priority for the middleware message queue according to the priority information, performing format conversion on the middleware message queue according to the service type, and constructing a middleware message body according to the middleware message queue after the format conversion, wherein the priority information comprises a product information influence factor, a project information influence factor and a weighted priority parameter;
the load balancing module is used for assisting the message queue module to process the middleware service request;
and the alarm module is used for monitoring the processing state and the result of the middleware service request and the state of the K8S cluster module and sending an alarm to a user when an exception occurs.
8. The middleware management device according to claim 6 wherein the K8S cluster module comprises:
the Helm management module is used for deploying the container middleware and configuring the container middleware;
the mirror image warehouse management module is used for acquiring the mirror images of the container middleware from the mirror image warehouse and uniformly managing the acquired mirror images;
the delivery module is interacted with the Helm management module and used for finishing the deployment and deletion of the container middleware;
the terminal module is used for providing terminal service for the container middleware;
the monitoring module is used for acquiring monitoring sample data of the container middleware and performing data visualization on the monitoring sample data;
the management module is used for providing a management service function for the container middleware;
the resource scheduling module is used for acquiring network resources required by deploying the container middleware and judging whether the network resources are sufficient or not;
and the log module is used for collecting log data generated in the running process of the container middleware.
9. An electronic device, comprising:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the middleware management method according to any one of claims 1 to 5.
10. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the middleware management method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011051274.5A CN112202879B (en) | 2020-09-29 | 2020-09-29 | Middleware management method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011051274.5A CN112202879B (en) | 2020-09-29 | 2020-09-29 | Middleware management method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112202879A true CN112202879A (en) | 2021-01-08 |
| CN112202879B CN112202879B (en) | 2022-12-27 |
Family
ID=74008529
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011051274.5A Active CN112202879B (en) | 2020-09-29 | 2020-09-29 | Middleware management method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112202879B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113259430A (en) * | 2021-05-11 | 2021-08-13 | 京东数字科技控股股份有限公司 | Message calling method and device, electronic equipment and storage medium |
| CN113342503A (en) * | 2021-06-30 | 2021-09-03 | 招商局金融科技有限公司 | Real-time progress feedback method, device, equipment and storage medium |
| CN114510258A (en) * | 2022-02-21 | 2022-05-17 | 深圳市金蝶天燕云计算股份有限公司 | Middleware management method, middleware management platform and computer readable storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101540776A (en) * | 2008-03-17 | 2009-09-23 | 储彬 | Grid middleware system supporting adaptive scheduling |
| US20140130036A1 (en) * | 2012-11-02 | 2014-05-08 | Wipro Limited | Methods and Systems for Automated Deployment of Software Applications on Heterogeneous Cloud Environments |
| CN103986709A (en) * | 2014-05-15 | 2014-08-13 | 重庆邮电大学 | Middleware registration method under RESTful framework |
| WO2018049873A1 (en) * | 2016-09-13 | 2018-03-22 | 华为技术有限公司 | Application scheduling method and device |
| CN110780918A (en) * | 2019-10-28 | 2020-02-11 | 江苏满运软件科技有限公司 | Middleware container processing method and device, electronic equipment and storage medium |
| CN111193782A (en) * | 2019-12-18 | 2020-05-22 | 北京航天智造科技发展有限公司 | PAAS cloud cluster construction method and device, electronic equipment and storage medium |
-
2020
- 2020-09-29 CN CN202011051274.5A patent/CN112202879B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101540776A (en) * | 2008-03-17 | 2009-09-23 | 储彬 | Grid middleware system supporting adaptive scheduling |
| US20140130036A1 (en) * | 2012-11-02 | 2014-05-08 | Wipro Limited | Methods and Systems for Automated Deployment of Software Applications on Heterogeneous Cloud Environments |
| CN103986709A (en) * | 2014-05-15 | 2014-08-13 | 重庆邮电大学 | Middleware registration method under RESTful framework |
| WO2018049873A1 (en) * | 2016-09-13 | 2018-03-22 | 华为技术有限公司 | Application scheduling method and device |
| CN110780918A (en) * | 2019-10-28 | 2020-02-11 | 江苏满运软件科技有限公司 | Middleware container processing method and device, electronic equipment and storage medium |
| CN111193782A (en) * | 2019-12-18 | 2020-05-22 | 北京航天智造科技发展有限公司 | PAAS cloud cluster construction method and device, electronic equipment and storage medium |
Non-Patent Citations (5)
| Title |
|---|
| ANGEL BELTRE; PANKAJ SAHA; MADHUSUDHAN GOVINDARAJU: "KubeSphere: An Approach to Multi-Tenant Fair Scheduling for Kubernetes Clusters", 《2019 IEEE CLOUD SUMMIT》 * |
| EDDY TRUYEN;MATT BRUZEK;DIMITRI VAN LANDUYT;BERT LAGAISSE;WOUTER: "Evaluation of Container Orchestration Systems for Deploying and Managing NoSQL Database Clusters", 《2018 IEEE 11TH INTERNATIONAL CONFERENCE ON CLOUD COMPUTING》 * |
| SOFIANE IMADALI;AYOUB BOUSSELMI: "Cloud Native 5G Virtual Network Functions: Design Principles and Use Cases", 《2018 IEEE 8TH INTERNATIONAL SYMPOSIUM ON CLOUD AND SERVICE COMPUTING (SC2)》 * |
| 华为云开发者论坛: "云图说 通过helm模板快速部署中间件应用 https://zhuanlan.zhihu.com/p/252361908", 《知乎》 * |
| 徐照旻;蔡铭;董金祥;: "基于面向服务中间件的集成化CAPP系统研究", 《计算机集成制造系统》 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113259430A (en) * | 2021-05-11 | 2021-08-13 | 京东数字科技控股股份有限公司 | Message calling method and device, electronic equipment and storage medium |
| CN113342503A (en) * | 2021-06-30 | 2021-09-03 | 招商局金融科技有限公司 | Real-time progress feedback method, device, equipment and storage medium |
| CN113342503B (en) * | 2021-06-30 | 2024-02-13 | 招商局金融科技有限公司 | Real-time progress feedback method, device, equipment and storage medium |
| CN114510258A (en) * | 2022-02-21 | 2022-05-17 | 深圳市金蝶天燕云计算股份有限公司 | Middleware management method, middleware management platform and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112202879B (en) | 2022-12-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112202879B (en) | Middleware management method and device, electronic equipment and storage medium | |
| US20170373931A1 (en) | Method for updating network service descriptor nsd and apparatus | |
| CN111212116A (en) | High-performance computing cluster creating method and system based on container cloud | |
| EP3629160B1 (en) | Method and device for managing vnf instantiation | |
| US20240118935A1 (en) | Pod deployment method and apparatus | |
| CN112631680B (en) | Micro-service container scheduling system, method, device and computer equipment | |
| CN114281573A (en) | Workflow data interaction method and device, electronic device and readable storage medium | |
| US20230342183A1 (en) | Management method and apparatus for container cluster | |
| CN115454636A (en) | Container cloud platform GPU resource scheduling method, device and application | |
| CN115499432A (en) | Family terminal computing resource management system and computing resource scheduling method | |
| CN114301914A (en) | Cloud edge coordination method and device and storage medium | |
| CN102868594B (en) | Method and device for message processing | |
| US20230040676A1 (en) | Network service construction system and network service construction method | |
| WO2022151386A1 (en) | Node batch and upgrade method, and related apparatus and device | |
| CN111857736B (en) | Cloud computing product generation method, device, equipment and storage medium | |
| US20230246911A1 (en) | Control device, control method, control program and control system | |
| CN112449357B (en) | Information interaction method and related equipment | |
| CN115550313A (en) | Communication method and device of external equipment, electronic equipment and storage medium | |
| CN112685613A (en) | Resource packet query method and device and information processing system | |
| CN111309467A (en) | Task distribution method and device, electronic equipment and storage medium | |
| CN113852479B (en) | Secure network construction method, device, equipment and computer storage medium | |
| CN113055211B (en) | Method for instantiating network service and network function virtualization orchestrator | |
| JP6750929B2 (en) | Method and apparatus for deploying network services | |
| CN117056029B (en) | Resource processing method, system, device, storage medium and electronic equipment | |
| CN116938757A (en) | Data processing method, device, electronic equipment and storage medium |
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 |