CN110278243B

CN110278243B - Load balancing application management method and device, computer equipment and storage medium

Info

Publication number: CN110278243B
Application number: CN201910414016.XA
Authority: CN
Inventors: 黄桂钦
Original assignee: Ping An Technology Shenzhen Co Ltd
Current assignee: Ping An Technology Shenzhen Co Ltd
Priority date: 2019-05-17
Filing date: 2019-05-17
Publication date: 2023-05-23
Anticipated expiration: 2039-05-17
Also published as: CN110278243A

Abstract

The embodiment of the application provides a load balancing application management method, a load balancing application management device, computer equipment and a storage medium, which relate to the technical field of cloud computing and can be applied to a PaaS platform. The method comprises the following steps: f5 load balancing application is created according to a preset creation interface; after the F5 load balancing application is established, if an opening instruction for opening a preset management interface is received, opening the preset management interface according to the opening instruction; and if a management instruction triggered by a management interface corresponding to a preset management interface is received, managing the created F5 load balancing application according to the management instruction. The embodiment of the application can manage the F5 load balancing application created through the preset creation interface on the management interface corresponding to the preset management interface. Different information of the created F5 load balancing application can be managed through a management interface of a preset management interface, so that the efficiency of F5 load balancing application management is improved, and the user experience is improved.

Description

Load balancing application management method and device, computer equipment and storage medium

Technical Field

The present disclosure relates to the field of cloud computing technologies, and in particular, to a method and apparatus for managing load balancing applications, a computer device, and a storage medium.

Background

At present, the PaaS Platform (Platform-as-a-Service) on the market is used for manually modifying F5 load balancing application by logging on F5 equipment by users with corresponding rights, so that load balancing information is opaque, and the users needing modification have higher professional background knowledge and are very complicated to operate.

Disclosure of Invention

The embodiment of the application provides a load balancing application management method, a device, computer equipment and a storage medium, which can manage the created F5 load balancing application through a management interface corresponding to a preset management interface, and improve the efficiency of F5 load balancing application management.

In a first aspect, an embodiment of the present application provides a method for managing a load balancing application, where the method includes:

f5 load balancing application is created according to a preset creation interface; after the F5 load balancing application is established, if an opening instruction for opening a preset management interface is received, opening the preset management interface according to the opening instruction; and if a management instruction triggered by a management interface corresponding to a preset management interface is received, managing the created F5 load balancing application according to the management instruction.

In a second aspect, an embodiment of the present invention provides a load balancing application management apparatus, where the load balancing application management apparatus includes a unit corresponding to the method for executing the first aspect.

In a third aspect, an embodiment of the present invention provides a computer device, where the computer device includes a memory, and a processor connected to the memory;

the memory is configured to store a computer program, and the processor is configured to execute the computer program stored in the memory, so as to perform the method according to the first aspect.

In a fourth aspect, an embodiment of the present invention provides a computer readable storage medium storing a computer program, which when executed by a processor, implements the method according to the first aspect.

The embodiment of the application can manage the F5 load balancing application created through the preset creation interface on the management interface corresponding to the preset management interface. Different information of the created F5 load balancing application can be managed through a management interface of a preset management interface, so that corresponding management is not needed to be carried out on specific F5 equipment, the management operation is convenient and simple, errors are not easy to occur, and the efficiency of F5 load balancing application management is improved; the management interface of the preset management interface can be used for intuitively and clearly acquiring various relevant information of the created F5 load balancing application, the information is transparent and intuitive, and the user experience is improved; in addition, when the load balancing application fails, related information can be quickly acquired for troubleshooting, so that the positioning failure can be cleared.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a flow chart of a load balancing application management method provided in an embodiment of the present application;

FIG. 2 is a schematic diagram of a setup interface provided by an embodiment of the present application;

fig. 3 is a schematic sub-flowchart of a load balancing application management method according to an embodiment of the present application;

FIG. 4 is a schematic illustration of a setup interface provided in another embodiment of the present application;

fig. 5a is a schematic diagram of information of an F5 load balancing application provided in an embodiment of the present application;

FIG. 5b is a schematic diagram of information of a virtual server according to an embodiment of the present application;

fig. 6 is a flowchart of a modification method of the load balancing application management method provided in the embodiment of the present application;

fig. 7 is a flowchart of an adding method of the load balancing application management method provided in the embodiment of the present application;

fig. 8 is a flowchart of a deletion method of a load balancing application management method according to an embodiment of the present application;

FIG. 9 is a schematic block diagram of a load balancing application management apparatus provided by an embodiment of the present application;

FIG. 10 is a schematic block diagram of a first creation unit provided by an embodiment of the present application;

FIG. 11 is a schematic block diagram of a management unit provided by an embodiment of the present application;

FIG. 12 is a schematic block diagram of a management unit provided by an embodiment of the present application;

FIG. 13 is a schematic block diagram of a management unit provided by an embodiment of the present application;

fig. 14 is a schematic block diagram of a computer device provided in an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

Fig. 1 is a flow chart of a load balancing application management method according to an embodiment of the present application. As shown in FIG. 1, the method includes S101-S103.

S101, creating F5 load balancing application according to a preset creation interface.

The preset creation interfaces comprise a first preset creation interface and a second preset creation interface. The first preset creating interface is used for firstly creating the container application, then creating the F5 load balancing application of the container application, and setting the association relation between the container application and the F5 load balancing application. It can be understood that, through the first preset creation interface, the container application and the F5 load balancing application of the container application are created at one time, that is, the F5 load balancing application of the container application is created while the container application is created, and the association relationship between the container application and the F5 load balancing application is set. The second preset creating interface is used for creating the F5 load balancing application. Applicable scenarios include the following: the container application has been created, such as by running the container application for a period of time, and then determining to create an F5 load balancing application for the container application. In this scenario, a load balancing application needs to be created separately for the container application, i.e. a second pre-set creation interface needs to be used. Specifically, the first preset creation interface and the second preset creation interface may exist in the form of a setup interface and an interface function.

It should be noted that only the F5 load balancing application created through the preset creation interface can be managed on the management interface corresponding to the preset management interface.

In an embodiment, if the preset creation interface is the first preset creation interface, the F5 load balancing application is created according to the preset creation interface, that is, step S101 includes the following steps:

acquiring information of a container application and information of a load balancing application set through a first preset creation interface, wherein the type of the load balancing application is F5; and creating the container application and the F5 load balancing application by using a first preset creation interface according to the set information of the container application, the set information of the load balancing application and the preset load balancing parameter information, and setting the association relation between the created container application and the F5 load balancing application.

The first preset creating interface comprises a setting interface through which information of the container application and information of the load balancing application are set, wherein the setting interface is written by a developer and can be presented in the form of a setting interface. As shown in fig. 2, a schematic diagram of a setting interface corresponding to the setting interface is shown. And setting information of the container application to be created and information of the load balancing application through a setting interface of the first preset creation interface. Specifically, information of a container application to be created and information of a load balancing application input/selected by a user are received. Because the information of the container application and the information of the load balancing application can be set in the preset creation interface, the information of the container application and the information of the load balancing application are acquired simultaneously.

The information of the container application comprises application environment of the container application, area of the container application, number of container instances of the container application, mirror image information of the container application and the like. The information of the container application also includes whether monitoring is enabled, an application administrator or application creator (the person who created the container application may manage the created container application), a resource group of the container application, and the like. The application environment of the container application comprises a production environment, a test environment, a development environment and the like. Wherein, the production environment means that the container application is successfully established and then is connected with the external environment or is accessed by an external user; the test environment means that the container application is used for testing after being successfully created; the development environment means that the container application is successfully created for development and use. The area of the container application refers to the location of the machine room where the container application was created, and consists of two parts: "region" + "safe region". Where a "safe zone" is a sub-zone below the "zone". It is understood that the container application is created in the machine room of the "xxx security zone" below the "xx zone". However, determining in which specific machine room the container application is created needs to be decided together according to the application environment of the container application and the area of the container application, which can be understood as creating the container application in the machine room corresponding to the area of the container application in a certain application environment. It is understood that the machine room corresponding to different application environments in the same area is different. The number of container instances of a container application refers to the number of containers of the container application, and the number of containers of a container application is not limited. Wherein the number of container instances may be determined based on the amount of access to the container application. The container instance image information includes an image version, an image type, and an image name. Wherein the mirrored version includes an official version, an unofficial version, version 1.1, version 4.5, etc.; the image type refers to which image is used by the container instance, such as nginx, tomcat, weblogic, springboot, etc.; mirror name refers to a specific mirror name, such as tomcat1.1, etc. The mirror image information can be obtained from a corresponding mirror image warehouse for selection by a user, wherein the corresponding mirror image warehouse refers to a mirror image warehouse under the machine room, wherein the application environment of the container application and the area of the container application are determined together. The creation of the container application is charged, and the resource group of the container application includes a resource account for the fee used by the container application creation. Whether monitoring is enabled refers to whether monitoring of the container instance of the container application is selected, such as the use of resources such as CPU/memory/IO of the container instance. In some embodiments, the information of the container application further includes a beneficiary resource pool, which refers to a sub-company/department that creates the container application, decides the IP network segments assigned by the created container and the host resources of the container, and uses different IP network segments and host resources for different resource pools. If the information of the container application also includes a beneficiary resource pool, the beneficiary resource pool, along with the application environment of the container application, the region of the container application, determines the IP network segment allocated by the created container instance, and the host resources of the container instance.

The information of the load balancing application comprises the type of the load balancing application and port information of a Virtual Server (VS) of the load balancing application, wherein the type of the load balancing application is F5. The port information of the virtual server of the load balancing application can be one or a plurality of, wherein one port corresponds to one VS, and a plurality of ports correspond to a plurality of VSs. The ports of the virtual server refer to the access ports supported by the F5 load balancing application, namely the ports accessed by the http mode, such as ports 80 and 443.

In an embodiment, as shown in fig. 3, according to the set information of the container application, the information of the load balancing application, and the preset load balancing parameter information, using a first preset creation interface, creating the container application and the F5 load balancing application, and setting an association relationship between the created container application and the F5 load balancing application, including the following steps S301-S305. The first preset creation interface further comprises an interface function. The first preset creation interface is understood as an interface function corresponding to the first preset creation interface.

S301, a first preset creation interface is utilized to create container instances of the container application according to the application environment of the container application, the area of the container application, the number of container instances and the container application mirror image information in the container application information.

Specifically, determining a container instance IP of the container application according to the application environment of the container application, the area of the container application and the number of container instances of the container application in the set container application information; determining a mirror image warehouse for storing mirror image information of the container application according to the application environment of the container application and the area of the container application, and extracting a specific mirror image required for creating the container instance from the determined mirror image warehouse according to the mirror image type, the mirror image version and the mirror image name of the mirror image information of the container application; determining resources to be occupied by creating the container instance according to the container mirror image type and the mirror image version, and determining a host machine for creating the container instance according to the application environment of the container application, the area of the container application and the resources to be occupied by creating the container instance; creating a container instance of the container application on the determined host according to the determined specific image, and binding the created container instance with the determined container instance IP to set the determined container instance IP to the IP of the created container instance.

Wherein, the location of the creation of the container application, i.e. in which specific machine room the container application is created, can be determined according to the application environment of the container application, the area of the container application. It should be noted that the mirror warehouse for storing the mirror resources corresponds to each region in each application environment. All the mirror resources needed to be used by the region in the application environment are stored in the mirror repository. Determining a host machine that creates a container application includes: acquiring an IP address pool of a host machine which is pre-allocated at a corresponding position (under the machine room) in a database and used for creating a container instance; and determining the host machine for creating the container instance from the IP address pool of the host machine according to the resources required to be occupied by the container instance. Creating a container instance requires some resources to be taken up on the host, and therefore the resources to be taken up to create the container instance need to be determined first to determine whether the host has sufficient resources to create the container instance. The resources needed to be occupied by creating the container instance comprise a CPU, a memory, monitoring resources and the like. Wherein creating a container instance of the container application on the determined host according to the determined specific image and IP binding the created container instance with the determined container instance comprises: transmitting, by the container orchestration tool, the determined specific image to the determined host that created the container instance, for creation of the container instance; the creation is completed and the container instance is bound to the determined container instance IP by an operation tool, such as an easy tool, to connect the container instance.

S302, determining the virtual IP of the virtual server of the load balancing application and F5 equipment for creating the load balancing application according to the application environment of the container application and the area of the container application.

The Virtual IP is Virtual IP, which may be abbreviated VIP. VIP is also an IP address, which is the destination address for receiving external (internet users or other users) access requests, and also internal (servers providing application services) sending messages to external source IP addresses. Typically, one container application corresponds to one VIP, which may correspond to multiple VS (virtual servers). Such as VIP 10.1.2.4. If there are two ports of the virtual server, 80 and 443 are respectively. Then 10.1.2.4:80 corresponds to one VS and 10.1.2.4:443 corresponds to the other VS. I.e. a VS comprising a VIP and a port information. It is also understood that a virtual server may be accessed through the VIP and a port.

Specifically, step S302 includes: determining a virtual IP address pool according to the application environment of the container application and the area of the container application in the set container application information; determining an IP address from a virtual IP address pool, and setting the determined IP address as the virtual IP of the virtual server; f5 equipment groups are determined according to the application environment of the container application and the area of the container application; an F5 device is determined from the F5 device group as the F5 device that created the load balancing application. It should be noted that the load balancing application F5 is a hard load balancing, i.e. a load balancing application needs to be created on a specific hardware device F5. Since the F5 device needs to be purchased, for cost reasons, there is typically only one F5 device under one machine room, and then the device is taken as the F5 device that creates the load balancing application. It should be noted that the order of determining the F5 device for creating the load balancing application and determining the VIP is not limited, and the F5 device may be determined first and then the VIP may be determined.

S303, associating the created container instance with the virtual server to obtain an association relationship, and packaging the association relationship, the information of the created container instance, the port information, the virtual IP and preset load balancing parameter information into an object.

Wherein the information of the created container instance mainly refers to the IP of the container instance. In some embodiments, the information of the created container instance further includes a container instance port. A container instance port refers to a port, such as an 8080 port, where the container instance (server) provides application services. If the set container application information further includes an application manager, the application manager needs to be encapsulated into the object.

Specifically, step S303 includes: taking each container instance as an associated server, and taking all the created container instances as an associated server cluster; generating the name of an associated server cluster, the name of the virtual server and the name of the container application according to a preset name generation rule; associating each associated server with a server in the server cluster, and associating the associated server cluster with the server cluster of the virtual server to obtain an association relationship; and packaging the generated names, the association relation, the information of the created container instance, the port information, the virtual IP and the preset load balancing parameter information into objects.

Wherein one Virtual Server (VS) corresponds to one server cluster (pool). A server cluster may be understood as a server cluster corresponding to a load balancing application, where a server cluster (pool) has a plurality of server members (pool members) that are configured to actually respond to an external access request. After receiving the external access request, the VS distributes the external access request to one server in the server cluster according to a load balancing algorithm, and the distributed server responds to the external access request. The virtual servers are associated with the associated server cluster, such as setting the server cluster (pool) of the virtual servers as the associated server cluster. And associating the servers in the server cluster of the virtual server with a plurality of associated servers, for example, setting server members (poolmers) of the server cluster of the virtual server as the plurality of associated servers, wherein the number of the server members in the server cluster is the number of the associated servers.

The load balancing parameter information includes parameters such as a listening protocol (e.g., TCP, etc.), a load balancing algorithm (e.g., rotation, a least connection method, etc.), an Http profile (e.g., http-transparent, http-explicit, http-xforward, etc.), a health check method (for selecting a mode of applying a listening container to the load balancing F5 application, e.g., F5 monweb), a Snat mode (for selecting a Snat mode of VIP function address conversion of a virtual server, including a Snat/DANT universal mode, a Snat mode, etc.), a cookie mode (a value of a cookie mode, e.g., NONE, source-addr, hash, dest-addr, ssl, cookie, etc.), a SnatPool (for selecting an IP address pool of the Snat mode, i.e., an IP address range after converting an access request source address/destination address), etc. The method for obtaining the preset load balancing parameter information comprises the following steps: presetting a default value for each load balancing parameter according to the current operation requirement of an enterprise; and taking the default value of each set load balancing parameter as preset load balancing parameter information. The default value of each load balancing parameter is set according to the current operation requirement of the enterprise, and it can be understood that the default value best matches the current requirement of the enterprise.

S304, calling a creation interface of the F5 load balancing application according to the packaged object to create a virtual server of the load balancing application on the determined F5 equipment, and generating a configuration file of the virtual server.

Wherein the creation interface of the load balancing application is a function, and parameters in the function comprise the packaged object. The F5 load balancing application can be automatically created on the F5 equipment according to the related information of the packaged object through the function, and a configuration file of the F5 load balancing application is generated in the creation process.

S305, if a message that the virtual server is successfully created is received, an access domain name is generated according to a preset domain name generation rule, and the access domain name is bound with the virtual IP of the virtual server so as to access the virtual server through the access domain name.

And after the F5 load balancing application is established, automatically starting the load balancing service of the VS. After starting, the operation state of the VS, the operation state of the pool and the operation state of each pool member are changed from the stop state to the start state. Since the F5 load balancing application is created on the F5 device, relevant information is returned whether the creation was successful or failed. If a returned message of successful creation of the load balancing F5 application is received, an access domain name is generated; if a message of returning failure is received, the problem is positioned according to the reason of the failure. And generating the access domain name according to a preset domain name generation rule. And binding the access domain name with the virtual IP after generating the access domain name so as to access the virtual server through the access domain name.

The F5 load balancing application is created while the container application is created, and the created container application and the created F5 load balancing application are automatically associated, so that the whole process is automatically completed, the creation speed and efficiency are further improved, and the time cost and the labor cost are saved.

In an embodiment, if the preset creation interface is the second preset creation interface, the F5 load balancing application is created according to the preset creation interface, that is, step S101 includes the following steps:

acquiring information of a load balancing application set through a second preset creation interface and information of an associated application associated with the load balancing application, wherein the type of load balancing is F5; and creating the F5 load balancing application by using a second preset creation interface according to the set information of the load balancing application and the information of the associated application.

The second preset creation interface comprises a setting interface through which information of a load balancing application to be created and an associated application associated with the load balancing application are set, wherein the setting interface is written by a developer and can be presented in the form of a setting interface. As shown in fig. 4, a schematic diagram of a setting interface corresponding to the setting interface of the second preset creation interface is shown. And setting information of the load balancing application to be created and an associated application associated with the load balancing application through the setting interface. The information of the load balancing application includes parameters such as a load balancing application type (default F5), an associated application, http profile (e.g., http), a load balancing algorithm (e.g., training, etc.), a health check mode (e.g., F5 monweb), a Snat mode (Snat/DANT universal mode), snat Pool, a port (e.g., 80 ports of a virtual server of the F5 load balancing application), and the like.

The second preset creating interface further includes an interface function, and the creating of the F5 load balancing application by using the second preset creating interface may be understood as obtaining a name of the set associated application by using the interface function corresponding to the second preset creating interface, obtaining information of the associated application, and then creating the F5 load balancing application of the associated application according to the information of the associated application and the information of the F5 load balancing application.

It should be noted that, the load balancing parameters in the first preset creating interface are preset load balancing parameters, and when the load balancing application is created through the second preset creating interface, the parameters of the load balancing application can be set through the setting interface of the second preset creating interface.

S102, after the F5 load balancing application is established, if an opening instruction for opening the preset management interface is received, opening the preset management interface according to the opening instruction.

The preset management interfaces are a plurality of different management interfaces written by developers. All information of all F5 load balancing applications created through a preset creation interface can be checked in the management interface. And modifying all information of all F5 load balancing applications which are created.

Wherein each F5 load balancing application includes information of the F5 load balancing application, information of VS of the F5 load balancing application, information of a server cluster (pool) in the virtual server, and information of each server member (pool member) in the server cluster.

Fig. 5a is a schematic diagram of information of an F5 load balancing application provided in an embodiment of the present application. It should be noted that fig. 5a is only an example, and in practice, more or less information may be displayed. The information of the F5 load balancing application includes VIP and VS names of the F5 load balancing application, container application names related to the F5 load balancing application, ports of the VS, access domain names corresponding to the F5 load balancing application, the number of containers of the F5 load balancing application (the number of container instances corresponding to the F5 load balancing application), an F5 load balancing application creator or an application administrator, and the like. And on a management interface corresponding to the information of the F5 load balancing application, an editing button, a query button and the like are correspondingly arranged. Triggering the editing button, and further viewing information of VS related to the F5 load balancing application on another management interface; and triggering the query button to acquire the F5 load balancing application information to be queried from the F5 load balancing application information.

Fig. 5b is a schematic diagram of information of a virtual server according to an embodiment of the present application. It should be noted that the load balancing parameter information is not listed in fig. 5b due to the limitations of the display. It should be noted that fig. 5b is only an example, and in practice, more or less information may be displayed. The information of the VS of the F5 load balancing application includes the VS name of the F5 load balancing application, the server cluster name, the virtual IP, the port of the VS, the running state of the VS (including running, stopping, etc.), load balancing parameter information, etc. The load balancing parameter information comprises Http profile, cookie mode, snat mode and SnatPool. And the management interface corresponding to the information of the VS of the F5 load balancing application is correspondingly provided with a change button, a delete button, a start button, a stop button and the like, so that the information of the VS can be respectively changed (such as parameters including a change Httpprofile, cookie mode, a Snat mode, a SnatPool and the like), the information of the VS is deleted, the VS is started, the VS is stopped and the like.

As shown in fig. 5b, the information of the server cluster in the virtual server includes the server cluster name, the number of server members included in the server cluster, the running state of the server cluster, a load balancing algorithm (such as a rotation, a minimum connection mode, etc.) in the load balancing parameter information, a monitoring protocol, etc. On the management interface corresponding to the information of the server cluster, there are a change button, a Pool member viewing button, a delete button, etc., and the corresponding functions that can be implemented are respectively to change the information of the server cluster (for example, change a load balancing algorithm, a monitoring protocol, etc.), view the information of the server members in the server cluster, and delete the Pool.

The server member information in the server cluster includes server IP (container instance IP), server port, running status, and the like. On the management interface corresponding to the server member information, there is information of each server member, and each server member corresponds to an add button, a delete button, a start button, a stop button, and the like. The method comprises the steps of adding a server, deleting the server, starting the server and stopping the server.

And S103, if a management instruction triggered by a management interface corresponding to a preset management interface is received, managing the created F5 load balancing application according to the management instruction.

The management instructions are triggered by a user clicking on an associated button on the management interface, wherein the management instructions include a query instruction, a change instruction, a delete instruction, a start instruction, a stop instruction, and the like.

If the management instruction is a query instruction. If a management instruction triggered by a management interface corresponding to a preset management interface is received, managing the created F5 load balancing application according to the management instruction, wherein the management instruction comprises the following steps: if a query instruction triggered by a management interface corresponding to a preset management interface is received, acquiring a query condition in the query instruction, wherein the query condition comprises a query object, and the query object comprises information of F5 load balancing application, information of a virtual server of the F5 load balancing application, information of a server cluster in the virtual server and information of a server member in the server cluster; and according to the query conditions, acquiring information matched with the query conditions from all the information of the created F5 load balancing application, and returning the matched information to a management interface for reference. In an embodiment, the query condition further includes an application environment to which the load balancing application belongs, such as information of all F5 load balancing applications created in the query development environment. By the query instruction, information of VS of a certain F5 load balancing application, information of server clusters in the VS, information of each server member in the server clusters, and the like can be also referred.

Through the query instruction, various different information related to F5 load balancing application can be intuitively and clearly seen on a management interface corresponding to a preset management interface, and the information is very transparent; meanwhile, when the container application fails, different information related to the F5 load balancing application can be quickly acquired, so that the fault can be easily detected and located.

If the management instruction is a change instruction. As shown in fig. 6, a flowchart of a modification method of the load balancing application management method according to an embodiment of the present application is shown, where the modification method includes the following steps S601-S604.

S601, if a change instruction triggered by a management interface corresponding to a preset management interface is received, obtaining a change object in the change instruction, wherein the change object comprises information of a virtual server of F5 load balancing application and information of a server cluster in the virtual server.

If the change object in the change instruction is the information of the virtual server of the F5 load balancing application, wherein the information of the changeable virtual server comprises parameters such as Http profile, cookie mode, snat mode, snatPool and the like, and the parameters such as the changeable Http profile, cookie mode, snat mode, snatPool and the like are taken as the attributes of the virtual server, and one parameter corresponds to one attribute.

S602, acquiring candidate options corresponding to the attribute of the change object from F5 equipment for creating the F5 load balancing application according to the change object.

F5 equipment for creating F5 load balancing application of the virtual server is obtained according to the information of the virtual server, candidate options of each attribute which can be changed are obtained in real time from the F5 equipment, and the candidate options of the Http profile attribute comprise Http and Http-transparent, http-explicit, http-xforward; candidate options for cookie mode attributes include NONE, source-addr, hash, dest-addr, ssl, cookie, and the like.

S603, receiving target options selected by the user from the candidate options.

If the target option selected by the user from the candidate options is Http for the Http profile attribute, then receiving the Http selected by the user from the candidate options. For the cookie mode attribute, the target option selected by the user from the candidate options is ssl, and the ssl selected by the user from the candidate options is received.

S604, if a change determining instruction is received, the selected target option is taken as a value corresponding to the attribute of the change object, and the attribute value of the change object is changed in the configuration file of the virtual server.

If a change determining instruction is received, taking the selected target option as a value corresponding to the attribute of the change object, for example, taking the selected Http as a value corresponding to the Http profile attribute, and taking the selected ssl as a value corresponding to the cookie mode attribute; and changing the attribute value of the change object in the configuration file of the virtual server so as to write the changed information on the management interface into the configuration file of the virtual server. The change determining instruction is triggered by a user clicking a button for determining change, etc., specifically, a change interface (which can also be understood as a change function) of the F5 load balancing application is called, and the attribute of the change object and a value corresponding to the attribute are transmitted to the change interface, so that the attribute value of the change object in the configuration file of the virtual server is changed through the change interface.

If the management instruction is an add instruction. As shown in fig. 7, a flowchart of an adding method of the load balancing application management method according to the embodiment of the present application is shown, where the adding method includes the following steps S701-S705.

S701, if an adding instruction triggered by a management interface corresponding to a preset management interface is received, an adding object in the adding instruction is obtained, wherein the adding object comprises server member information in a server cluster, and the server cluster is a server cluster of a virtual server of the F5 load balancing application.

S702, acquiring a container application with an association relation with the F5 load balancing application, and acquiring IP of a container instance of the container application and port information of a server corresponding to the container instance for providing services.

The obtained container instance IP of the container application may be all container instance IPs of the container application, and the port information for providing services of the server corresponding to the container instance refers to port information for providing services of all container instances. The obtained container instance IP of the container application may also be a container instance IP not added as a server member, and then the port information for providing the service by the server corresponding to the container instance refers to the port information for providing the service by the container instance not added as a server member.

S703, determining the IP and port information of the server member to be added according to the IP of the container instance and the port information of the server for providing service.

If all the container instance IPs of the container application are obtained, firstly, determining the container instance IPs which are not added as server members from all the container instance IPs (for example, setting the container instance IPs which are already added as server members to be in a non-selectable state and the container instance IPs which are not added as server members to be in a selectable state), then determining one container instance IP from the container instance IPs which are not added as server members as the IPs of the server members to be added, and taking the port information corresponding to the determined container instance as the port information of the server members to be added. For example, a container instance IP may be randomly selected from container instances IPs that are not added as server members as the IP of the server members to be added, and the port information of the container instance selected randomly is used as the port information of the server members to be added.

And S704, if an addition determination instruction is received, the determined IP and port information are used as information of the server member to be added, and the server member is set as one server member in the virtual server cluster.

Wherein the addition determination instruction is triggered by a user clicking a button for determining addition or the like.

S705, adding the added information of the server member to the configuration file of the virtual server, and adding 1 to the number of server members in the server cluster.

And adding the information of the added server members in the configuration file of the virtual server, and adding 1 to the number of the server members in the server cluster so as to write the added information on the management interface into the configuration file of the virtual server. Specifically, an add interface (also known as an add function) of the F5 load balancing application is called, information of the added server member is transferred to the add interface, so that the information of the server member is added in a configuration file of the virtual server through the add interface, and meanwhile, the number of server members in the server cluster is increased by 1.

If the management instruction is a deletion instruction, as shown in fig. 8, a flowchart of a deletion method of the load balancing application management method provided in the embodiment of the present application is shown, where the deletion method includes the following steps S801 to S804.

S801, if a deletion instruction triggered by a management interface corresponding to a preset management interface is received, a deletion object in the deletion instruction is obtained, wherein the deletion object comprises information of a virtual server of F5 load balancing application, information of a server cluster of the virtual server and information of server members in the server cluster.

S802, detecting whether the server member corresponding to the deleted object is shared by other virtual servers.

If the container application with the association relation with the F5 load balancing application is detected to be offline, the information of the virtual server of the F5 load balancing application with the association relation with the container application can be deleted. Or if the creation of the F5 load balancing application on the F5 device fails, the information of the virtual server of the load balancing application may be deleted.

Shared by other virtual servers, it is understood that at least two virtual servers use the same server member.

If the deleted object is the information of the virtual server of the F5 load balancing application, judging whether the server cluster of the virtual server has the condition that the server members are shared by other virtual servers or not; and if the deleted object is the information of the server cluster of the virtual server, judging whether the server cluster has the condition that the server members are shared by other virtual servers. If one server member is shared by other virtual servers, the server member is determined to be shared by other virtual servers, and if all the server members are not shared by other virtual servers, the server member is determined to be not shared by other virtual servers. If the deleted object is the information of the server member in the server cluster, judging whether the server member is shared by other virtual servers, if the server member is not shared by other virtual servers, determining that the server member is not shared by other virtual servers, and if the server member is shared by other virtual servers, determining that the server member is shared by other virtual servers.

And S803, if the server member corresponding to the deletion object is not shared by other virtual servers, deleting the deletion object, and deleting the information to be deleted of the deletion object in the configuration file of the virtual server.

If the deletion object is the information of the virtual server of the F5 load balancing application, the corresponding information to be deleted comprises the information of the virtual server, the information of a server cluster of the virtual server and the information of all server members in the server cluster. If the deleted object is the information of the server cluster of the virtual server, the information to be deleted includes the information of the server cluster of the virtual server and the information of all the server members in the server cluster. And if the deleting object is the information of the server members in the server cluster, deleting the information of the server members, and subtracting 1 from the number of the server members in the server cluster. It should be noted that deleting the information of the server member does not delete the container instance of the container application corresponding to the server member.

Specifically, a deletion interface (which may be also understood as a deletion function) of the F5 load balancing application is called, and the information of the deletion object is transferred to the deletion interface, so that the information of the deletion object, which corresponds to the information to be deleted, is deleted in the configuration file of the virtual server through the deletion interface.

And S804, if the server member corresponding to the deleted object is shared by other virtual servers, prompting.

Such as prompting that deletion is not possible. In some embodiments, if the deleted object is information of a server member in the server cluster, if the server member is shared by other virtual servers, the server member is removed, and the number of server members in the server cluster is reduced by 1. It will be appreciated that the removal is simply the deletion of the server member from the server cluster, but the server member still exists; and after deletion, the server member does not exist.

If the management instruction is a starting instruction, a starting object in the starting instruction is obtained, wherein the starting object comprises information of a virtual server of the F5 load balancing application and information of server members in a server cluster of the virtual server; and starting the starting object, and setting the running state of the starting object as a starting state. Wherein the starting object is started by using a starting command. If the failure of a certain server member in the server cluster is relieved, the server member is started to operate according to the starting instruction.

If the management instruction is a stop instruction, a stop object in the stop instruction is obtained, wherein the stop object comprises information of a virtual server of the F5 load balancing application and information of server members in a server cluster of the virtual server; stopping the stopping object, and setting the running state of the stopping object as a stopping state. Wherein stopping the stopping object can be achieved using a stop command. If the virtual server of the F5 load balancing application fails, stopping the virtual server according to the stopping instruction. After the virtual server stops running, the F5 load balancing application corresponding to the virtual server also stops running. If a certain server member in the server cluster fails, stopping the operation of the server member according to the stop instruction. After the server member stops running, the running of other server members is not influenced.

It should be noted that, in the above management methods, other methods besides the query method can adaptively modify the corresponding data in the database.

The method embodiment can realize the management of different information of the created F5 load balancing application through the management interface of the preset management interface, so that the user does not need to log on specific F5 equipment to perform corresponding management, and the management operation is convenient and simple and is not easy to make mistakes; on the other hand, various relevant information of the created load balancing F5 can be obtained very intuitively and clearly through a management interface of a preset management interface, the information is very transparent and intuitive, and the user experience is improved; and when the container application fails, all information of the F5 load balancing application of the container application can be quickly acquired, so that the troubleshooting and the positioning of the failure can be facilitated.

Fig. 9 is a schematic block diagram of a load balancing application management apparatus provided in an embodiment of the present application. As shown in fig. 9, the apparatus includes a unit for executing the above-described load balancing application management method. Specifically, as shown in fig. 9, the apparatus 90 includes a creation unit 901, an opening unit 902, and a management unit 903.

A creating unit 901, configured to create an F5 load balancing application according to a preset creating interface;

an opening unit 902, configured to, after the F5 load balancing application is created, open a preset management interface according to an opening instruction if the opening instruction for opening the preset management interface is received;

the management unit 903 is configured to, if a management instruction triggered by a management interface corresponding to a preset management interface is received, manage the created F5 load balancing application according to the management instruction.

In an embodiment, if the preset creation interface is a first preset creation interface, the creation unit 901 includes a first acquisition unit and a first creation unit. The first obtaining unit is used for obtaining information of the container application and information of the load balancing application set through the first preset creating interface, wherein the type of the load balancing application is F5. The first creating unit is used for creating the container application and the F5 load balancing application by utilizing a first preset creating interface according to the set information of the container application, the set information of the load balancing application and the preset load balancing parameter information, and setting the association relation between the created container application and the F5 load balancing application.

In an embodiment, as shown in fig. 10, the first creation unit 100 includes an application creation unit 101, a determination unit 102, an encapsulation unit 103, a load creation unit 104, and a domain name binding unit 105.

The application creating unit 101 is configured to create, using a first preset creating interface, a container instance of the container application according to an application environment of the container application, an area of the container application, the number of container instances, and container application mirror information in the container application information. A determining unit 102, configured to determine, according to an application environment of the container application, an area of the container application, a virtual IP of a virtual server of a load balancing application, and an F5 device that creates the load balancing application. And the encapsulation unit 103 is configured to associate the created container instance with the virtual server to obtain an association relationship, and encapsulate the association relationship, the information of the created container instance, the port information, the virtual IP, and preset load balancing parameter information into an object. The load creating unit 104 is configured to call a creating interface of the F5 load balancing application according to the encapsulated object, so as to create a virtual server of the load balancing application on the determined F5 device, and generate a configuration file of the virtual server. And the domain name binding unit 105 is configured to generate an access domain name according to a preset domain name generation rule if a message that the virtual server is successfully created is received, and bind the access domain name with the virtual IP of the virtual server, so as to access the virtual server through the access domain name.

In an embodiment, if the preset creation interface is a second preset creation interface, the creation unit 901 includes a second acquisition unit and a second creation unit. The second acquisition unit is used for acquiring information of the load balancing application set through the second preset creation interface and information of the associated application associated with the load balancing application, wherein the type of load balancing is F5. And the second creating unit is used for creating the F5 load balancing application by utilizing a second preset creating interface according to the set information of the load balancing application and the information of the related application.

In an embodiment, if the management instruction is a query instruction, the management unit 903 includes a query condition acquiring unit and a query information acquiring unit. The query condition acquisition unit is used for acquiring the query condition in the query instruction if receiving the query instruction triggered by the management interface corresponding to the preset management interface, wherein the query condition comprises a query object, and the query object comprises information of a virtual server of the F5 load balancing application, information of a server cluster in the virtual server and information of a server member in the server cluster. And the query information acquisition unit is used for acquiring information matched with the query conditions from all the information of the created F5 load balancing application according to the query conditions, and returning the matched information to a management interface for reference.

In an embodiment, if the management instruction is a change instruction, as shown in fig. 11, the management unit 903 includes a change object obtaining unit 111, an attribute option obtaining unit 112, a selection receiving unit 113, and a change unit 114. The modification object obtaining unit 111 is configured to obtain, if a modification instruction triggered by a management interface corresponding to a preset management interface is received, a modification object in the modification instruction, where the modification object includes information of a virtual server of the F5 load balancing application and information of a server cluster in the virtual server. And the attribute option obtaining unit 112 is configured to obtain, according to the change object, a candidate option corresponding to an attribute of the change object from the F5 device that creates the F5 load balancing application. A selection receiving unit 113 is configured to receive a target option selected by the user from the candidate options. And a modifying unit 114, configured to take the selected target option as a value corresponding to the attribute of the modification object if a modification determining instruction is received, and modify the attribute value of the modification object in the configuration file of the virtual server.

In an embodiment, if the management instruction is an add instruction, as shown in fig. 12, the management unit 903 includes an add object obtaining unit 121, an instance obtaining unit 122, an instance determining unit 123, and an add setting unit 124. The adding object obtaining unit 121 is configured to obtain an adding object in an adding instruction if an adding instruction triggered by a management interface corresponding to a preset management interface is received, where the adding object includes server member information in a server cluster, and the server cluster is a server cluster of a virtual server of an F5 load balancing application. An instance obtaining unit 122, configured to obtain a container application associated with the F5 load balancing application, and obtain an IP of a container instance of the container application and port information of a server corresponding to the container instance for providing a service. An instance determining unit 123, configured to determine the IP and port information of the server member to be added according to the IP of the container instance and the port information of the server for providing the service. An adding setting unit 124, configured to set the determined IP and port information as information of a server member to be added, and set the server member as one server member in the server cluster, if an adding determination instruction is received; and adding the added information of the server members to the configuration file of the virtual server, and adding 1 to the number of the server members in the server cluster.

In an embodiment, if the management instruction is a delete instruction, as shown in fig. 13, the management unit 903 includes a delete object obtaining unit 131, a common detecting unit 132, a deleting unit 133, and a prompting unit 134. The deleted object obtaining unit 131 is configured to obtain, if a deleted instruction triggered by a management interface corresponding to a preset management interface is received, a deleted object in the deleted instruction, where the deleted object includes information of a virtual server of the F5 load balancing application, information of a server cluster of the virtual server, and information of a server member in the server cluster. The common detection unit 132 is configured to detect whether the server member corresponding to the deletion object is shared by other virtual servers. And a deleting unit 133, configured to delete the deletion object if the server member corresponding to the deletion object is not shared by other virtual servers, and delete the information to be deleted by the deletion object in the configuration file of the virtual server. And a presenting unit 134, configured to present if the server member corresponding to the deletion object is shared by other virtual servers.

It should be noted that, as those skilled in the art can clearly understand the specific implementation process of the foregoing apparatus and each unit, reference may be made to the corresponding description in the foregoing method embodiment, and for convenience and brevity of description, no further description is provided herein.

The above-described apparatus may be implemented in the form of a computer program which is executable on a computer device as shown in fig. 14.

Fig. 14 is a schematic block diagram of a computer device according to an embodiment of the present application. The device is a terminal and other devices, such as a server in a PaaS platform. The device 140 includes a processor 142, memory, and a network interface 143 connected by a system bus 141, where the memory may include a non-volatile storage medium 144 and an internal memory 145.

The non-volatile storage medium 144 may store an operating system 1441 and a computer program 1442. The computer program 1442 stored in the nonvolatile storage medium, when executed by the processor 142, can implement the load balancing application management method described in the server. The processor 142 is used to provide computing and control capabilities to support the operation of the overall device 140. The internal memory 145 provides an environment for the execution of a computer program in a non-volatile storage medium that, when executed by the processor 142, causes the processor 142 to perform the load balancing application management method described in the server above. The network interface 143 is used for network communication. It will be appreciated by those skilled in the art that the structure shown in fig. 14 is merely a block diagram of a portion of the structure associated with the present application and does not constitute a limitation of the apparatus to which the present application is applied, and that a particular apparatus may include more or less components than those shown in the drawings, or may combine certain components, or have a different arrangement of components.

Wherein the processor 142 is configured to execute a computer program stored in the memory to implement the steps of:

In an embodiment, the management instruction includes a query instruction, and when the processor 142 executes the step of managing the created F5 load balancing application according to the management instruction if the management instruction triggered by the management interface corresponding to the preset management interface is received, the specific implementation steps are as follows:

if a query instruction triggered by a management interface corresponding to a preset management interface is received, acquiring a query condition in the query instruction, wherein the query condition comprises a query object, and the query object comprises information of a virtual server of F5 load balancing application, information of a server cluster in the virtual server and information of a server member in the server cluster; and according to the query conditions, acquiring information matched with the query conditions from all the information of the created F5 load balancing application, and returning the matched information to a management interface for reference.

In an embodiment, the management instruction includes a change instruction, and when the processor 142 executes the step of managing the created F5 load balancing application according to the management instruction if the management instruction triggered by the management interface corresponding to the preset management interface is received, the specific implementation steps are as follows:

if a change instruction triggered by a management interface corresponding to a preset management interface is received, obtaining a change object in the change instruction, wherein the change object comprises information of a virtual server of F5 load balancing application and information of a server cluster in the virtual server; acquiring candidate options corresponding to the attribute of the change object from F5 equipment for creating F5 load balancing application according to the change object; receiving a target option selected by a user from the candidate options; and if a change determining instruction is received, taking the selected target option as a value corresponding to the attribute of the change object, and changing the attribute value of the change object in the configuration file of the virtual server.

In an embodiment, the management instruction includes an add instruction, and when the processor 142 executes the step of managing the created F5 load balancing application according to the management instruction if the management instruction triggered by the management interface corresponding to the preset management interface is received, the specific implementation steps are as follows:

If an adding instruction triggered by a management interface corresponding to a preset management interface is received, an adding object in the adding instruction is obtained, wherein the adding object comprises server member information in a server cluster, and the server cluster is a server cluster of a virtual server of F5 load balancing application; acquiring a container application with an association relation with the F5 load balancing application, and acquiring IP of a container instance of the container application and port information of a server corresponding to the container instance for providing service; determining the IP and port information of a server member to be added according to the IP of the container instance and the port information of the server corresponding to the container instance for providing service; if an addition determining instruction is received, the determined IP and port information are used as information of a server member to be added, and the server member is set as one server member in a server cluster; the added information of the server members is added to the configuration file of the virtual server, and the number of the server members in the server cluster is increased by 1.

In an embodiment, the management instruction includes a delete instruction, and when the processor 142 executes the step of managing the created F5 load balancing application according to the management instruction if the management instruction triggered by the management interface corresponding to the preset management interface is received, the specific implementation steps are as follows:

If a deleting instruction triggered by a management interface corresponding to a preset management interface is received, acquiring a deleting object in the deleting instruction, wherein the deleting object comprises information of a virtual server of F5 load balancing application, information of a server cluster of the virtual server and information of server members in the server cluster; detecting whether the server member corresponding to the deleted object is shared by other virtual servers or not; if the server member corresponding to the deletion object is not shared by other virtual servers, deleting the deletion object, and deleting the information to be deleted of the deletion object in the configuration file of the virtual server; and if the server member corresponding to the deleted object is shared by other virtual servers, prompting.

In an embodiment, the preset creating interface includes a first preset creating interface, and the processor 142 specifically implements the following steps when executing the step of creating the F5 load balancing application according to the preset creating interface:

In an embodiment, the preset creating interface includes a second preset creating interface, and the processor 142 specifically implements the following steps when executing the step of creating the F5 load balancing application according to the preset creating interface:

It should be appreciated that in embodiments of the present application, the processor 142 may be a central processing unit (Central Processing Unit, CPU), which may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (application lication Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

Those skilled in the art will appreciate that all or part of the flow in a method embodying the above described embodiments may be accomplished by computer programs instructing the relevant hardware. The computer program may be stored in a storage medium, which may be a computer readable storage medium. The computer program is executed by at least one processor in the computer system to implement the flow steps of the embodiments of the method described above.

Accordingly, the present application also provides a storage medium. The storage medium may be a computer-readable storage medium including a non-volatile computer-readable storage medium. The storage medium stores a computer program which, when executed by a processor, performs the steps of:

In an embodiment, the management instruction includes a query instruction, and when the processor executes the step of managing the created F5 load balancing application according to the management instruction if the management instruction triggered by the management interface corresponding to the preset management interface is received, the processor specifically implements the following steps:

In an embodiment, the management instruction includes a change instruction, and when the processor executes the step of managing the created F5 load balancing application according to the management instruction if receiving the management instruction triggered by the management interface corresponding to the preset management interface, the processor specifically implements the following steps:

In an embodiment, the management instruction includes an add instruction, and when the processor executes the step of managing the created F5 load balancing application according to the management instruction if receiving the management instruction triggered by the management interface corresponding to the preset management interface, the processor specifically implements the following steps:

In an embodiment, the management instruction includes a delete instruction, and when the processor executes the step of managing the created F5 load balancing application according to the management instruction if the management instruction triggered by the management interface corresponding to the preset management interface is received, the processor specifically implements the following steps:

In an embodiment, the preset creating interface includes a first preset creating interface, and the processor specifically implements the following steps when executing the step of creating the F5 load balancing application according to the preset creating interface:

In an embodiment, the preset creating interface includes a second preset creating interface, and the processor specifically implements the following steps when executing the step of creating the F5 load balancing application according to the preset creating interface:

The storage medium may be a U-disk, a removable hard disk, a Read-Only Memory (ROM), a magnetic disk, or an optical disk, or other various computer-readable storage media that can store program codes.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus, device, and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and the division of the units is merely a logical function division, and other divisions may be implemented in practice. It will be clearly understood by those skilled in the art that, for convenience and brevity of description, specific working procedures of the apparatus, device and unit described above may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein. While the invention has been described with reference to certain preferred embodiments, it will be understood by those skilled in the art that various changes and substitutions of equivalents may be made and equivalents will be apparent to those skilled in the art without departing from the scope of the invention. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for load balancing application management, the method comprising:

f5 load balancing application is created according to a preset creation interface, wherein the preset creation interface comprises a first preset creation interface;

After the F5 load balancing application is established, if an opening instruction for opening a preset management interface is received, opening the preset management interface according to the opening instruction;

if a management instruction triggered by a management interface corresponding to a preset management interface is received, managing the created F5 load balancing application according to the management instruction, wherein the management instruction comprises a query instruction, a change instruction, an addition instruction and a deletion instruction;

the step of creating the F5 load balancing application according to the preset creation interface comprises the following steps:

acquiring information of a container application and information of a load balancing application set through a first preset creation interface, wherein the type of the load balancing application is F5;

and creating the container application and the F5 load balancing application by using a first preset creation interface according to the set information of the container application, the set information of the load balancing application and the preset load balancing parameter information, and setting the association relation between the created container application and the F5 load balancing application.

2. The method according to claim 1, wherein the management instruction includes a query instruction, and the managing the created F5 load balancing application according to the management instruction if the management instruction triggered by the management interface corresponding to the preset management interface is received includes:

If a query instruction triggered by a management interface corresponding to a preset management interface is received, acquiring a query condition in the query instruction, wherein the query condition comprises a query object, and the query object comprises information of a virtual server of F5 load balancing application, information of a server cluster in the virtual server and information of a server member in the server cluster;

and according to the query conditions, acquiring information matched with the query conditions from all the information of the created F5 load balancing application, and returning the matched information to a management interface for reference.

3. The method according to claim 1, wherein the management instruction includes a change instruction, and the managing the created F5 load balancing application according to the management instruction if the management instruction triggered by the management interface corresponding to the preset management interface is received includes:

if a change instruction triggered by a management interface corresponding to a preset management interface is received, obtaining a change object in the change instruction, wherein the change object comprises information of a virtual server of F5 load balancing application and information of a server cluster in the virtual server;

Acquiring candidate options corresponding to the attribute of the change object from F5 equipment for creating F5 load balancing application according to the change object;

receiving a target option selected by a user from the candidate options;

and if a change determining instruction is received, taking the selected target option as a value corresponding to the attribute of the change object, and changing the attribute value of the change object in the configuration file of the virtual server.

4. The method according to claim 1, wherein the management instruction includes an add instruction, and the managing the created F5 load balancing application according to the management instruction if the management instruction triggered by the management interface corresponding to the preset management interface is received includes:

if an adding instruction triggered by a management interface corresponding to a preset management interface is received, an adding object in the adding instruction is obtained, wherein the adding object comprises server member information in a server cluster, and the server cluster is a server cluster of a virtual server of F5 load balancing application;

acquiring a container application with an association relation with the F5 load balancing application, and acquiring IP of a container instance of the container application and port information of a server corresponding to the container instance for providing service;

Determining the IP and port information of a server member to be added according to the IP of the container instance and the port information of the server corresponding to the container instance for providing service;

if an addition determining instruction is received, the determined IP and port information are used as information of a server member to be added, and the server member is set as one server member in a server cluster;

the added information of the server members is added to the configuration file of the virtual server, and the number of the server members in the server cluster is increased by 1.

5. The method according to claim 1, wherein the management instruction includes a delete instruction, and the managing the created F5 load balancing application according to the management instruction if the management instruction triggered by the management interface corresponding to the preset management interface is received includes:

if a deleting instruction triggered by a management interface corresponding to a preset management interface is received, acquiring a deleting object in the deleting instruction, wherein the deleting object comprises information of a virtual server of F5 load balancing application, information of a server cluster of the virtual server and information of server members in the server cluster;

Detecting whether the server member corresponding to the deleted object is shared by other virtual servers or not;

if the server member corresponding to the deletion object is not shared by other virtual servers, deleting the deletion object, and deleting the information to be deleted of the deletion object in the configuration file of the virtual server;

and if the server member corresponding to the deleted object is shared by other virtual servers, prompting.

6. The method of claim 1, wherein the pre-set creation interface comprises a second pre-set creation interface, and wherein creating the F5 load balancing application from the pre-set creation interface comprises:

acquiring information of a load balancing application set through a second preset creation interface and information of an associated application associated with the load balancing application, wherein the type of load balancing is F5;

and creating the F5 load balancing application by using a second preset creation interface according to the set information of the load balancing application and the information of the associated application.

7. A load balancing application management apparatus, characterized in that the load balancing application management apparatus comprises:

the F5 load balancing application is created according to a preset creation interface, wherein the preset creation interface comprises a first preset creation interface;

The opening unit is used for opening the preset management interface according to the opening instruction if the opening instruction for opening the preset management interface is received after the F5 load balancing application is established;

the management unit is used for managing the created F5 load balancing application according to the management instruction if receiving the management instruction triggered by the management interface corresponding to the preset management interface, wherein the management instruction comprises a query instruction, a change instruction, an addition instruction and a deletion instruction;

the creation unit includes:

the first acquisition unit is used for acquiring information of the container application and information of the load balancing application set through the first preset creation interface, wherein the type of the load balancing application is F5;

the first creating unit is used for creating the container application and the F5 load balancing application by utilizing a first preset creating interface according to the set information of the container application, the set information of the load balancing application and the preset load balancing parameter information, and setting the association relation between the created container application and the F5 load balancing application.

8. A computer device comprising a memory, and a processor coupled to the memory;

The memory is used for storing a computer program; the processor is configured to execute a computer program stored in the memory to perform the method of any one of claims 1-6.

9. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program which, when executed by a processor, implements the method according to any of claims 1-6.