CN108737591B

CN108737591B - Service configuration method and device

Info

Publication number: CN108737591B
Application number: CN201810493764.7A
Authority: CN
Inventors: 瞿秋亮; 王洋; 李海华
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-05-22
Filing date: 2018-05-22
Publication date: 2021-09-14
Anticipated expiration: 2038-05-22
Also published as: CN108737591A

Abstract

The application provides a service configuration method including domain name allocation and a device for realizing the method. In the current method, an applicant proposes a domain name application, manually fills the domain name of the application, and performs configuration and issue after a domain name distribution platform performs uniqueness check. This makes domain name assignment inefficient and less standardized. According to the method, the domain name is distributed in a mode that the domain name is automatically generated according to the unique identifier, the efficiency of a domain name distribution system is improved on the premise that the uniqueness of the domain name is guaranteed, and in the elastic load balancing scene, after the domain name is generated, a method of carrying out load balancing configuration on a client applying for the domain name is adopted, so that the efficiency and the standardization degree of the system are further improved.

Description

Service configuration method and device

Technical Field

The present application relates to the field of network communication technologies, and in particular, to the field of service configuration technologies.

Background

The network is based on the transmission control protocol/internet protocol (english: TCP/IP) protocol for communication and connection, and each host has a unique fixed-identity IP address to distinguish thousands of users and computers on the network. Since the IP address of the digital type is difficult to memorize and write, a symbolized address scheme, i.e., a domain name, is developed on the basis of the IP address. A domain name is the name of a computer or group of computers on the internet, consisting of a string of characters separated by dots, used to indicate the electronic orientation of the computer at the time of data transmission. The Domain Name System (DNS) is a distributed database on the internet as a mapping between Domain names and IP addresses, and enables users to access the internet more conveniently without remembering IP strings that can be read directly by a machine. Like IP addresses, domain names that perform the recognition function need to be unique.

In a cloud scene, the application can implement cross-Available Zone (referred to as Available Zone, for short, AZ) load balancing through the domain name, that is, after the domain name is allocated, the configuration of the load balancing policy of the servers in different zones is performed. The servers used to support the access of domain names may be hosted in multiple locations around the world, which are made up of zones and available areas, each zone being a separate geographic area, and within each zone there are multiple locations isolated from each other, called available areas. The Elastic Load Balancing (ELB) can automatically distribute incoming application program traffic among a plurality of target entities (such as Elastic computing clouds, containers, IP addresses and the like), realize Load Balancing of a back-end server, relieve application pressure and improve system availability. The Load Balancing configuration of the generated domain name comprises Global Server Load Balancing (GSLB for short) and Local Server Load Balancing (LSLB for short). The GSLB is used as an authoritative DNS to finish the resolution of domain names and cross-AZ flow scheduling, thereby realizing the cross-AZ high availability of services; and the back-end LSLB distributes the service flow to the real back-end server in a balanced manner, so as to realize load balance among the servers in the AZ.

At present, when service configuration including domain name allocation is required, a domain name application is usually provided by an applicant, and the applied domain name is manually filled in to request the agreement of a domain name allocation platform. The domain name distribution platform compares the applied domain name with the existing domain name in order to ensure the uniqueness of the domain name, and requires the application party to refill if the applied domain name already exists. And if the applied domain name does not exist, the domain name allocation platform agrees with the domain name application, allocates an IP address for the domain name and performs configuration issuing. The service configuration method has the problems of low efficiency and low standardization degree after the processes of domain name application, uniqueness check, IP address allocation and the like, and is difficult to meet the current cloud requirements.

Disclosure of Invention

Embodiments of the present application provide a method and an apparatus for service configuration, so that a cloud service system can generate a unique domain name through time information of a domain name application, and perform load balancing configuration on the generated domain name, thereby improving efficiency and standardization degree of service configuration.

In a first aspect, the present application provides a service configuration method, which is applied to a cloud service system. The cloud service system comprises a domain name distribution platform and at least one server, wherein the at least one server is used for providing elastic load balancing service for a client, and the service configuration method comprises the following steps: receiving a domain name application sent by a client, wherein the domain name application comprises service information of the client; generating a unique domain name for the client according to the time information of the domain name application; and configuring a load balancing rule for the client according to the domain name and the service information of the client, wherein the load balancing rule is used for at least one server to provide services for the client.

In the scheme, the domain name is automatically generated by the domain name distribution platform according to the time of domain name application, so that the efficiency of the whole cloud service system can be improved. And a domain name is generated according to a set rule, and a load balancing rule is configured for the client according to the domain name and the service information of the client after the domain name is generated, so that the standardization degree of the cloud service system is improved.

According to the first aspect of the present application, a possible implementation method is that the generated domain name contains a unique identifier, which is a universally unique identifier UUID. By including a unique identifier with the generated domain name, the generated domain name does not conflict with the existing domain name, and stability of the cloud service system is provided.

According to the first aspect of the present application, another possible implementation manner is that the load balancing configuration includes a global server load balancing configuration and a local server load balancing configuration. By configuring load balancing rules including global server load balancing and local server load balancing for the client, the efficiency of the cloud service system can be improved.

According to the first aspect of the present application, another possible implementation manner is that, after a load balancing rule is configured for a client, a local server load balancing configuration name is generated according to a generated unique domain name. By the method, the local server load balancing configuration name can be unique, and the stability of the cloud service system is improved.

According to the first aspect of the present application, another possible implementation manner is that the service information of the client further includes available area information, where the available area information includes information on the number of available areas for providing services to the client. The number information of the available areas is used as the service information of the client side and sent to the domain name distribution platform, so that better load balancing rules can be configured for the client side, and the efficiency of the cloud service system is improved.

A second aspect of the present application provides a computer apparatus comprising: the receiving module is used for receiving a domain name application sent by a client, wherein the domain name application comprises service information of the client; the generating module is used for generating a unique domain name for the client according to the time information of the domain name application; and the configuration module is used for configuring a load balancing rule for the client according to the domain name and the service information of the client, wherein the load balancing rule is used for at least one server to provide services for the client.

According to the second aspect of the present application, one possible implementation manner is that the generated domain name contains a unique identifier, which is a universally unique identifier UUID.

According to the second aspect of the present application, another possible implementation manner is that the load balancing configuration includes a global server load balancing configuration and a local server load balancing configuration.

According to the second aspect of the present application, another possible implementation manner is that the generating module is further configured to, after configuring the load balancing rule for the client, generate the local server load balancing configuration name according to the generated unique domain name.

According to the second aspect of the present application, another possible implementation is that the service information of the client includes available area information including information on the number of available areas for providing the service to the client.

In a third aspect, the present application provides a computer apparatus comprising a processor and a memory, the memory storing program code, the processor being configured to invoke the program code in the memory to perform the service configuration method as provided in the first aspect of the present application.

Drawings

Fig. 1 is a schematic flow chart illustrating a process of assigning a domain name to a domain name applicant in the prior art.

Fig. 2 is a schematic diagram of a service distribution process in an ELB scenario in the prior art.

Fig. 3 is a schematic composition diagram of a cloud service system in an embodiment of the present application.

Fig. 4 is a flowchart illustrating service configuration in an embodiment of the present application.

Fig. 5 is a functional structure diagram of a computer device in an embodiment of the present application.

Fig. 6 is a schematic structural diagram of a computer device in an embodiment of the present application.

Detailed Description

In order to make the above objects, technical solutions and advantages of the present application more comprehensible, detailed descriptions are provided below. The detailed description sets forth various embodiments of the devices and/or processes via the use of block diagrams, flowcharts, and/or examples. Since these block diagrams, flowcharts, and/or examples contain one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within these block diagrams, flowcharts, or examples can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or any combination thereof.

The domain name is a symbolic electronic scheme introduced for users to conveniently access the internet, and is the name of a certain computer or group of computers on the internet, which is composed of a string of characters separated by dots, and is used for indicating the electronic orientation of the computer when data is transmitted. Fig. 1 is a flow of applying for a conventional domain name. As shown in fig. 1, first, the host applies for a domain name from the domain name management device, and the host fills the domain name by itself. Because the domain name needs to be identified, the domain name needs to be unique. In order to ensure that the newly applied domain name is not repeated with the existing domain name, the domain name distribution platform carries out uniqueness checking operation on the domain name filled by the host computer. If the domain name is duplicated with the existing domain name, the client applying for the domain name needs to refill the domain name, and then check the uniqueness of the refilled domain name. If the uniqueness passes the verification, the domain name allocation platform allocates an IP address for the domain name, and performs configuration such as load balancing on the generated domain name and the like under the condition of need.

Under an ELB service scene, load balancing configuration can be performed through a GSLB configuration module and an LSLB configuration module, wherein the GSLB configuration module and the LSLB configuration module can be a single GSLB device and a single LSLB device, and can also be integrated on a server. As shown in fig. 2, load balancing configuration is performed on a domain name http:// www/domain.com:80, a GSLB policy is configured under the domain name first, on one hand, the policy is used as an authoritative DNS to realize resolution of the domain name, and on the other hand, traffic is distributed to different AZ according to address information, health conditions and the like. For example, users in different regions access the domain name, and the GSLB configuration module may access the nearest site through proximity judgment and DNS redirection, thereby achieving the effect of cross-region load balancing according to the domain name. Each AZ usually has at least one GSLB configuration module, and the GSLB configuration module can redistribute the traffic flow in one AZ to servers such as different Elastic computing clouds (hereinafter referred to as "Elastic computing Cloud" for short, EC2) according to a predetermined LSLB policy, thereby realizing load balancing between different servers in the same AZ.

In the prior art, because a method of manually configuring a domain name is adopted, an applicant firstly designates the domain name, and then a domain name distribution platform carries out uniqueness check on the domain name designated by the applicant, the service flow is long, and the efficiency is low. And when the uniqueness passes the verification, the administrator configures the load balancing strategy, so that the standardization degree is not high, and the efficiency of the system is further reduced.

Embodiments of the present application provide a method and apparatus for service configuration based on the objective of improving the standardization of service configuration including domain name allocation and improving efficiency. In the prior art, domain name allocation is performed manually, which results in low efficiency, and thus embodiments of the present application use a mode of automatically generating a domain name to allocate a domain name. Meanwhile, in order to ensure the uniqueness of the domain name, the automatic generation of the domain name is based on a unique identifier, so that the domain name automatically generated every time is different. The unique identifier may have a variety of generation rules, typically determined by the time of domain name application. Under an ELB service scene, after the domain name is generated, GSLB and LSLB configuration is carried out on the generated domain name, and all processes can be automatically carried out by automatically generating the domain name, so that the flow is reduced, and the efficiency of the system is improved.

FIG. 3 is a system architecture diagram of one embodiment of the present application. As shown in fig. 3, the present application relates to a cloud service system 300. The cloud service system 300 includes a domain name assignment platform 310, a GSLB configuration module 320, a LSLB configuration module 330, and a LSLB configuration module 331, and several servers. The GSLB configuration module and the LSLB configuration module may be a GSLB device and a LSLB device, or may be integrated on a server. The domain name assignment platform 310 provides an interface for an applicant, typically in the form of a client, to apply for a domain name. The applicant usually includes service information of the client in the domain name application, and for example, may select whether to deploy single AZ or multiple AZ in the domain name application interface. The cloud service 300 includes a GSLB configuration module 320, and the GSLB configuration module 320 generally appears in pairs, and is used as a master and a slave respectively to provide global load balancing and domain name resolution service. Specifically, the GSLB configuration module 320 parses the domain name, and resolves the domain name used by the client into a service virtual IP address corresponding to a certain AZ according to a predetermined policy. Each AZ involved by cloud service 300 typically includes at least one LSLB configuration module 330. As with the GSLB configuration module, the LSLB configuration module 330 is also typically present in pairs, each serving as a master. The LSLB configuration module 330 matches the service policy and distributes traffic to some of the servers according to the service policy.

FIG. 4 is a flow chart of one embodiment of the present application. The method comprises the following specific steps:

s410: a client acting as a domain name applicant applies for a domain name on an interface provided by the domain name assignment platform 310. Further, the client may also select whether the generated domain name is deployed singly or across AZ, and configure other service information about GSLB and LSLB on the interface, such as information about protocols, ports, health check algorithms, and geographic information algorithms.

And S420, after receiving the domain name application instruction sent by the client, the domain name distribution platform 310 generates the domain name according to the unique identifier corresponding to the application and the established rule. The generated domain name may be implemented in the form of a unique identifier plus a serving domain name suffix, such as (unique identifier). To ensure that the generated domain name is unique, the unique identifier may be generated based on the Machine Code (english) of the server that received the domain name application and the time at which the domain name application was received. The machine code is a unique label of the computer, is usually taken from a serial number of computer hardware, and is obtained from a MAC address of a network card if the network card exists, or is obtained in other modes if the network card does not exist. Since the same server cannot receive and process a plurality of domain name applications at the same time, when the unique identifier is generated from the machine code of the server that received the domain name application and the time at which the domain name application was received, the uniqueness of the unique identifier can be ensured.

In the embodiment of the present application, the Unique Identifier used for generating the domain name may be a Universal Unique Identifier (UUID). A UUID refers to a number generated on one machine that is guaranteed to be unique to all machines in the same air at the same time. According to the standard established by the open software foundation, the generation of the UUID relates to parameters such as Ethernet network card address, nanosecond time and the like. A UUID typically consists of several parts: first, the current date and time; second, a clock sequence; third, the globally unique IEEE machine code, if there is a network card, is obtained from the network card MAC address, and no network card is obtained in other ways. The UUID is used as the unique identifier, so that the domain name which does not conflict with the domain name in the past can be generated every time, and the problem of uniqueness of the domain name is well solved.

More specifically, the Unique Identifier may be a Globally Unique Identifier (Globally referred to as "global Unique Identifier", abbreviated as "GUID"). A GUID is an algorithmically generated, 128-bit binary-length numeric identifier that is used primarily in networks and systems that have multiple nodes, multiple computers. The GUID is in the format "xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx", where each x is a hexadecimal number in the range of 0-9 or a-f. In theory, no computer or cluster of computers will generate two identical GUIDs and can be automatically generated according to an algorithm and thus can be used as a unique identifier in embodiments of the present application.

S430: when a domain name is generated using a unique identifier, the generated domain name must be resolved by the GSLB configuration module 320 in order to be accessed. Meanwhile, the GSLB configuration module 320 configures a global server load balancing rule for the client applying for the domain name to meet the high availability requirement of the generated domain name single AZ or cross AZ.

The GSLB configuration rules mainly include health check, geographical information, and IP address weights. For example, for health check, GSLB configuration module 320 performs a fourth layer TCP/UDP health check on the virtual IP address or server referred to by the generated domain name and a seventh layer application health check, and a site failing the health check may not be selected as the best content node. For geographic information, GSLB configuration module 320 may prioritize users of a particular IP range into sites that are geographically relatively close, based on the IP address of the visitor's local DNS. For IP address weights, GSLB configuration module 320 may assign a weight to each IP address in the DNS reply that determines the proportion of traffic assigned to that IP address compared to other candidate IPs.

S440: after the GSLB configuration is completed, the LSLB configuration module 330 configures an LSLB rule configuration for the client that applies for the domain name, so as to achieve load balancing of the background server and issue the load balancing.

In order to ensure the uniqueness of the LSLB configuration name for load balancing configuration of each client, as well as the generation of the domain name, a unique identifier may be added to the LSLB configuration name, so that the LSLB configuration name generated each time is also unique.

Furthermore, the number and the name of the AZ can be added into the LSLB configuration name, thereby facilitating subsequent operation and maintenance by an administrator of the domain name allocation system. For example, the LSLB configuration name may be set to (unique identifier) · (AZ number) · (AZ name) · (custom suffix).

The rules of the LSLB mainly include a random method, a weighted round robin method, a minimum number of connections method, and the like. For example, for the random method, the LSLB configuration module 330 randomly selects one of the servers to access according to the list size value of the backend server through a random algorithm. As can be known from the probability statistics theory, as the number of accesses increases, the actual effect of the access is closer to the average allocation of the allocation amount to each server at the back end. For the weighted polling method, the LSLB configuring module 330 configures a higher weight for a server configured with a high load and a low load, so that the server processes more requests; and low, high load servers are configured and assigned a lower weight, thereby reducing their system load. For the minimum connection number method, the LSLB configuration module 330 dynamically selects one server with the least backlog connection number to process the current request according to the connection condition of the current server, so as to improve the utilization efficiency of the backend service as much as possible.

After the above steps are completed, the user can perform service access to the client applying for the domain name based on the generated domain name. When a user accesses a service to a client through a domain name, the GSLB configuration module 320 parses the application domain name, and resolves the domain name into a virtual IP address corresponding to the AZ with a healthy service. The LSLB configuration module 330 matches the rules and distributes the traffic load to one of the servers according to the rules.

Based on the foregoing technical solution, referring to fig. 5, an embodiment of the present application provides a computer device 500, where the computer device 500 is configured to generate a domain name according to a domain name application provided by a client, and perform load balancing configuration on the generated domain name. As shown in fig. 5, the computer apparatus 500 includes:

the receiving module 510 is configured to receive a domain name application sent by a client. Further, the receiving module 510 may also receive other information provided by the client regarding the domain name application, for example, information about the number of available areas for providing services to the client applying for the domain name, and other service information regarding load balancing configuration for the client.

The generating module 520 is configured to generate the domain name according to a predetermined rule according to the unique identifier corresponding to the domain name application received by the receiving module 510. The unique identifier corresponding to the domain name application is associated with the machine code of the server receiving the domain name application and the time of receiving the domain name application, so as to ensure that the domain name generated by the generation module 520 according to the unique identifier does not conflict with the existing domain name.

A configuring module 530, configured to perform load balancing configuration on the domain name generated by the generating module 530, where the load balancing configuration includes global server load balancing configuration and local server load balancing configuration. The configuration module 530 also configures the generated domain name to be issued so that the generated domain name can be accessed.

The computer device 500 provided by the embodiment of the present application may refer to the method for configuring the service shown in fig. 4.

Fig. 6 is a schematic structural diagram of a computer device according to an embodiment of the present application.

As shown in fig. 6, the computer device 610 includes a host 600, the host 600 includes a processor 601, and the processor 601 is connected to a system memory 605. The Processor 601 may be a Central Processing Unit (CPU), an image Processor (GPU), a Field Programmable Gate Array (FPGA), a Digital Signal Processor (DSP), or any combination thereof. Processor 601 may be a single core processor or a multi-core processor.

The bus 609 is used for transmitting information between the components of the host 600, and the bus 609 may be connected by a wire or wirelessly, which is not limited in this application. A secondary storage 602, an input/output interface 603, and a communication interface 604 are also connected to the bus 609.

The secondary memory 602 is also generally referred to as an external memory, and the storage medium of the secondary memory 602 may be a magnetic medium (e.g., a floppy disk, a hard disk, or a magnetic tape), an optical medium (e.g., an optical disk), or a semiconductor medium (e.g., a Solid State Disk (SSD)). In some embodiments, the secondary memory 602 may further include a remote memory separate from the processor 601, such as a Network disk (including a Network or cluster File System, such as a Network File System (NFS) for example) accessible via the communication interface 604 and the Network 611.

The input/output interface 603 is connected to an input/output device for receiving input information and outputting an operation result. The input/output device may be a mouse, a keyboard, a display, or an optical drive, etc.

The communication interface 604 enables communication with other devices or networks 611 using transceiver means such as, but not limited to, transceivers, and the communication interface 604 may be interconnected with the networks 611 in a wired or wireless fashion.

Some of the features of the embodiments of the present application may be performed/supported by the processor 601 executing software code in the system memory 605. System memory 605 may include software such as an operating system 608 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system (e.g., Vxworks)), applications 607, and so forth.

Moreover, FIG. 6 is merely an example of a computing device 610, and computing device 610 may include more or fewer components than shown in FIG. 6, or have a different arrangement of components. Also, the various components illustrated in FIG. 6 may be implemented in hardware, software, or a combination of hardware and software.

Claims

1. A service configuration method is applied to a cloud service system, the cloud service system comprises a domain name allocation platform and at least one server, the at least one server is used for providing an elastic load balancing service for a client, and the method comprises the following steps:

receiving a domain name application sent by a client, wherein the domain name application comprises service information of the client;

generating a unique domain name for the client according to the time information of the domain name application;

and configuring a load balancing rule for the client according to the domain name and the service information of the client, wherein the load balancing rule is used for the at least one server to provide services for the client.

2. The method of claim 1,

the domain name contains a unique identifier, which is a universally unique identifier UUID.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

the load balancing configuration comprises a global server load balancing configuration and a local server load balancing configuration.

4. The method according to claim 1 or 2, wherein after configuring the load balancing rule for the client, the method further comprises:

and generating a local server load balancing configuration name according to the unique domain name.

5. The method according to claim 1 or 2,

the service information of the client further includes available area information, wherein the available area information includes information on the number of available areas for providing services to the client.

6. A computer device, the computer device comprising:

the receiving module is used for receiving a domain name application sent by a client, wherein the domain name application comprises service information of the client;

the generating module is used for generating a unique domain name for the client according to the time information of the domain name application;

and the configuration module is used for configuring a load balancing rule for the client according to the domain name and the service information of the client, wherein the load balancing rule is used for at least one server to provide services for the client.

7. The computer device of claim 6,

8. The computer device of claim 6 or 7,

9. The computer device of claim 6 or 7,

the generating module is further configured to generate a local server load balancing configuration name according to the unique domain name after configuring a load balancing rule for the client.

10. The computer device of claim 6 or 7,

11. A computer apparatus, wherein the cloud service system comprises:

a processor and a memory, the memory storing program code, the processor for invoking the program code in the memory to perform the service configuration method of any one of claims 1-5.