WO2024021471A1 - 一种服务更新方法、装置、系统和存储介质 - Google Patents
一种服务更新方法、装置、系统和存储介质 Download PDFInfo
- Publication number
- WO2024021471A1 WO2024021471A1 PCT/CN2022/141412 CN2022141412W WO2024021471A1 WO 2024021471 A1 WO2024021471 A1 WO 2024021471A1 CN 2022141412 W CN2022141412 W CN 2022141412W WO 2024021471 A1 WO2024021471 A1 WO 2024021471A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- cluster
- event
- monitor
- domain name
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 46
- 230000008859 change Effects 0.000 claims abstract description 65
- 238000012544 monitoring process Methods 0.000 claims abstract description 11
- 238000012217 deletion Methods 0.000 claims description 26
- 230000037430 deletion Effects 0.000 claims description 26
- 238000004590 computer program Methods 0.000 claims description 13
- 238000010586 diagram Methods 0.000 description 17
- 230000008569 process Effects 0.000 description 14
- 238000005516 engineering process Methods 0.000 description 8
- 230000004044 response Effects 0.000 description 7
- 238000004458 analytical method Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 230000008602 contraction Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1031—Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
Definitions
- the present application relates to the field of cloud computing technology, and in particular, to a service update method, device, system and storage medium.
- the operations in related technologies are based on manual operations.
- the global load balancing responds to the domain name and adds the service IP (full name Internet Protocol (Internet Protocol) resolution; or, first remove the global load balancing response domain name, and release the service after the service IP resolution is completed.
- IP full name Internet Protocol
- the artificial link is long, and there is no unified response mechanism from the service to the global load balancing domain name resolution in the cluster network. , for service expansion and contraction, it is impossible to automatically update the global load balancing analysis in real time.
- This application provides a service update method, device, system and storage medium to at least solve the problems in related technologies of slow global load balancing domain name resolution and long artificial links.
- An embodiment of the present application provides a service update system, which includes:
- a service scheduling engine and at least one service monitor; each service monitor is deployed in a service cluster;
- Each of the service monitors is used to monitor the service change status of each service in the corresponding service cluster; based on the service change status of each service, generate an event notification containing event information corresponding to the corresponding service, and send the Service scheduling engine;
- the service scheduling engine is configured to receive event notifications from at least one service monitor; based on the event information contained in each received event notification, generate a service domain name resolution value corresponding to the corresponding service and issue the configuration.
- the service change status includes at least one of the following: service new status, service deletion status;
- the event information includes: an event type corresponding to the service change status, a service domain name of the corresponding service, and an access address of the corresponding service.
- the service monitor is specifically used to:
- the service change status of the newly started service in the service cluster is the service new status; based on the service new status of the service, an event type containing an event type used to characterize the new service is generated. event notification; and/or
- the service change status of the released service in the service cluster is the service deletion status; based on the service deletion status of the service, an event notification containing an event type used to characterize the deletion of the service is generated. .
- the service scheduling engine is specifically used to:
- the service domain name resolution value of the service is obtained.
- the embodiment of the present application provides a service update method, which is applied to the service monitor in the service update system.
- the method includes:
- the embodiment of the present application provides a service update method, which is applied to the service scheduling engine in the service update system.
- the method includes:
- a service domain name resolution value corresponding to the corresponding service is generated and the configuration is issued.
- the event information includes the service domain name of the corresponding service and the access address of the corresponding service;
- a service domain name resolution value corresponding to the corresponding service is generated, including:
- the service domain name resolution value of the service is obtained.
- the monitoring unit monitors the service change status of each service in the corresponding service cluster
- a generating unit based on the service change status of each service, generates an event notification containing event information corresponding to the corresponding service;
- the notification unit sends the event notification to the service scheduling engine in the service update system, so that the service scheduling engine obtains the service domain name resolution value.
- the receiving unit receives an event notification containing event information from at least one service monitor, wherein the event notification is based on the service change status of each service in the corresponding service cluster monitored by the service monitor in the service update system, Generated and sent to the service scheduling engine, each service monitor is deployed in a service cluster;
- the generation unit based on the event information contained in the event notification, generates a service domain name resolution value corresponding to the corresponding service and issues the configuration.
- the event information includes the service domain name of the corresponding service and the access address of the corresponding service.
- the generating unit is specifically configured to:
- the service domain name resolution value of the service is obtained.
- An embodiment of the present application provides a computer-readable storage medium, which includes a computer program.
- the computer program When the computer program is run on an electronic device, the computer program is used to cause the electronic device to perform the steps of any of the above service update methods. .
- Embodiments of the present application provide a service update method, device, system and storage medium. Since service update operations in related technologies are completed based on manual time limits, there is no unified response mechanism for domain name resolution from services to global load balancing in the cluster network, and rapid automatic updates cannot be achieved.
- this application deploys a service in each service cluster. The monitor monitors the change status of the service, and generates corresponding event notifications and sends them to the service scheduling engine to obtain the new resolution value of the service domain name. Finally, the service scheduling engine sends it to the global load balancing to take effect in real time, achieving rapid service delivery. Automatic updates.
- Figure 1 is a schematic diagram of an application scenario of a service update method provided by an embodiment of the present application
- Figure 2A is an overall flow chart of a service update method provided by an embodiment of the present application.
- Figure 2B is an overall flow chart of another service update method provided by an embodiment of the present application.
- Figure 2C is an interaction diagram between a service monitor and a service scheduling engine provided by this application;
- Figure 3 is an event notification form corresponding to a new event provided by an embodiment of the present application.
- Figure 4 is an event notification form corresponding to another new event provided by an embodiment of the present application.
- Figure 5 is an event notification form corresponding to a deletion event provided by an embodiment of the present application.
- Figure 6 is an overall flow chart of service update based on actual application scenarios provided by the embodiment of the present application.
- Figure 7 is a schematic structural diagram of a service update device provided by an embodiment of the present application.
- Figure 8 is a schematic structural diagram of another service update device provided by an embodiment of the present application.
- Figure 9 is a schematic structural diagram of a system provided by an embodiment of the present application.
- Service cluster A group of node computers used to run containerized applications, providing network resources as a whole; in this application, there are multiple service clusters, and each service cluster has multiple services and a service monitor. When services are added The service cluster expands and shrinks when the service is deleted.
- Service monitor Deployed in each service cluster, it is responsible for monitoring the service change status of the services in each service cluster, and generating corresponding event notifications for the changed services and sending them to the service scheduling engine.
- Service scheduling engine It can set up and manage service scheduling, and provides scheduling functions for various scenarios that require scheduling.
- the service scheduling engine provides a service change interface, receives event notifications sent by the service monitor, and processes them based on the event notifications.
- Domain name resolution of the service obtains the resolution value of the service domain name, and sends it to the global load balancing to make the resolution effective.
- Global load balancing The full name is Global Server Load Balancing, or GSLB for short. It is responsible for load balancing among server groups that are placed in different geographical locations and have different network structures. Load balancing is responsible for balancing and distributing load across multiple operating units to evenly send network traffic to multiple servers.
- Service change status The services in the service cluster are changed due to addition or release.
- the service change status includes service new status and service deletion status. If one or more services are added to the service cluster, it is called this one.
- the service change status of one or more services is the service new status; if one or more services are deleted from the service cluster, the service change status of the one or more services is called the service deletion status.
- Event notification A notification with event information generated by the service monitor when it detects the addition or deletion of services in the service cluster.
- the event information includes the event type corresponding to the service change status, the service domain name of the corresponding service, and the corresponding The access address of the service.
- the application scenario diagram includes a service monitor 110 and a service scheduling engine 120.
- the service monitor 110 in the service cluster where the video service is added detects service changes.
- the status is the new status of the service. That is, after a new service is added to the service cluster, the event notification corresponding to the service is obtained and generated.
- the event notification includes the event type corresponding to the service change status, the service domain name of the corresponding service, and The access address of the corresponding service, and then the service monitor 110 sends the event notification to the service scheduling engine 120 .
- the service monitor 110 detects that the service change status of the service is the service deletion status, obtains and generates an event notification corresponding to the service, and sends it to the service scheduling engine 120 .
- the service scheduling engine 120 After receiving the event notification, the service scheduling engine 120 determines the service with the same service domain name based on the received event notification, obtains the service domain name resolution value of the service based on the access address of the service, and finally delivers it to the global load balancing, so that The analysis takes effect.
- embodiments of the present application can be applied to various scenarios, including but not limited to cloud technology, artificial intelligence, smart transportation and other scenarios.
- FIG. 2A is an implementation flow chart of a service update method provided by an embodiment of the present application, with the service monitor as the execution subject.
- the specific implementation process of the method is as follows S201A-S202A:
- S201A Monitor the service change status of each service in the service cluster.
- a service cluster is a group of node computers used to run containerized applications and provides network resources as a whole; there are usually multiple service clusters, and each service cluster has multiple services and a service monitor.
- the service monitor is responsible for Monitor the service change status of services in each service cluster, that is, whether services in the service cluster are added or deleted.
- Each service cluster has a service monitor, that is, there is service monitor 1 in service cluster 1, service monitor 2 in service cluster 2, and service cluster 3. There is a service monitor 3. There is an existing service A, which is deployed in service cluster 1 and service cluster 2. The service monitors in each service cluster can detect the service changes of the respective service clusters and the service change status of the service.
- S202A Based on the service change status of each service, generate an event notification containing event information corresponding to the corresponding service, and send it to the service scheduling engine.
- the service change status includes service new status and service deletion status. If one or more services are added to the service cluster, the service change status of this one or more services is called the service new status; if one or more services are deleted from the cluster, or multiple services, the service change status of one or more services is called the service deletion status.
- the event notification is generated by the service monitor when it detects the addition or deletion of services in the service cluster.
- the notification contains event information.
- the event information includes: the event type corresponding to the service change status, the service domain name of the corresponding service, and the corresponding The access address of the service.
- the service monitor After a service in the service cluster is changed, the service monitor generates an event notification containing event information corresponding to the service based on the service change status of the changed service.
- the service monitor detects the expansion of the service cluster where it is located, it determines that the service change status of the newly started service in the service cluster is the service new status. Based on the service new status of the service, an event notification corresponding to the service is generated.
- the event The notification includes the event type used to indicate that the service is a new service, the service domain name of the service, and the access address of the service.
- the service monitor detects the shrinkage of the service cluster where it is located, it determines that the service change status of the released service in the service cluster is the service deletion status. Based on the service deletion status of the service, an event notification corresponding to the service is generated. In the event notification It includes the event type used to indicate that the service is a deleted service, the service domain name of the service, and the access address of the service.
- this application realizes real-time monitoring of services in the service cluster network through the service monitor, and can realize notification of multi-cluster service expansion and contraction events.
- service monitor 1 in service cluster 1 and service monitor 2 in service cluster 2 monitor their respective service clusters.
- the service changes, that is, a new service A is added.
- Service Monitor 1 and Service Monitor 2 determine that the service change status of service A is the service new status, then an event notification corresponding to service A is generated, as shown in Figure 3, as
- the embodiment of the present application provides an event notification table corresponding to a new event, in which event A1 is an event notification corresponding to service A generated by service monitor 1, and event A2 is an event notification corresponding to service A generated by service monitor 2.
- Event notification contains the event type ADD, indicating that service A is a new service in service cluster 1 and service cluster 2. It also contains the service domain name of service A: service1.x.y.z, and the access IP of service A, that is, Access addresses: 111.111.221.221 and 111.111.221.222.
- service monitor 3 in service cluster 3 detects that a new service A has been added to the service cluster, and determines that the service change status of service A is service If a new status is added, an event notification corresponding to service A is generated.
- an event notification table corresponding to another new event provided by the embodiment of the present application, in which event A3 is generated by service monitor 3.
- the event notification contains the event type ADD, indicating that service A is a new service in service cluster 2. It also contains the service domain name of service A: sevice1.x.y.z, and the access IP of service A, that is, Access address: 111.111.221.223.
- service monitor 2 in service cluster 2 detects changes in the services of the service cluster, that is, service A is deleted, and service monitor 2 determines the service of service A.
- the change status is the service deletion status, and then an event notification corresponding to service A is generated.
- an event notification form corresponding to the deletion event provided by the embodiment of the present application, in which event A4 is generated by service monitor 2
- the event notification corresponding to service A contains the event type DEL, indicating that service A is a deletion service in service cluster 2. It also contains the service domain name of service A: sevice1.x.y.z, and the access IP of service A, that is, Access address: 111.111.221.222.
- the service monitor sends the event notification to the service scheduling engine in the service update system so that the service scheduling engine generates the service domain name resolution value corresponding to the corresponding service and issues the configuration based on the event information contained in each received event notification.
- FIG. 2B is an implementation flow chart of another service update method provided by the embodiment of the present application, with the service scheduling engine as the execution subject.
- the specific implementation process of this method is as follows:
- S201B Receive event notification from the service monitor.
- the event notification is generated and sent to the service scheduling engine by the service monitor in the service update system based on the monitored service change status of each service in the corresponding service cluster.
- Each service monitor is deployed in a service cluster. .
- S202B Based on the event information contained in each received event notification, generate a service domain name resolution value corresponding to the corresponding service and deliver the configuration.
- the service scheduling engine can set up and manage service scheduling, and provide scheduling functions for various scenarios that require scheduling.
- the service scheduling engine can provide a centralized unified interface with the ability to update global load balancing analysis in real time; that is, service
- the scheduling engine provides a service change interface, receives event notifications sent by the service monitor, and processes the domain name resolution of the service based on the event notification, obtains the resolution value of the service domain name, and sends it to the global load balancing to make the resolution effective.
- Global load balancing is to balance the load among server groups that are placed in different geographical locations and have different network structures. Load balancing is responsible for balancing and distributing load across multiple operating units to evenly send network traffic to multiple servers.
- the service scheduling engine After receiving the event notification sent by each service monitor, the service scheduling engine generates the service domain name resolution value corresponding to the corresponding service based on the event information contained in the received event notification and issues the configuration.
- the service domain name resolution value of the service is obtained by the service scheduling engine first determining the service with the same service domain name and obtaining it based on the access address of the service with the same service domain name.
- this application can provide a centralized unified interface through the service scheduling engine, update the global load balancing analysis in real time, and improve the versatility of the underlying capabilities.
- service monitor 1 in service cluster 1 and service monitor 2 in service cluster 2 generate corresponding services.
- A's event notification, and the event notification is sent to the service scheduling engine.
- the service scheduling engine determines the service with the same service domain name sevice1.x.y.z, and recombines the service domain name; According to the access IP of service A, the resolution values of the service domain name are 111.111.221.221 and 111.111.221.222; then they are delivered to the global load balancing to make them effective.
- service monitor 3 in service cluster 3 detects that service A is started, and generates an event notification corresponding to service A, and sends the event notification to the service scheduling engine.
- Service Scheduling After the engine receives the event A3 sent by the service monitor, it determines the services with the same service domain name sevice1.x.y.z, and recombines the service domain names; according to the access IP of service A, the parsed values of the service domain names are 111.111.221.221, 111.111.221.222 and 111.111.221.223; then deliver it to global load balancing to make it effective.
- service domain name sevice1.x.y.z of service A they may access service A with IP address 111.111.221.221 in service cluster 1, or access IP address 111.111.221.222 in service cluster 2.
- Service A, or accessing Service A with IP address 111.111.221.223 in Service Cluster 3 that is, visitors have a chance of accessing Service A in Service Cluster 3 and getting a response.
- service monitor 2 in service cluster 2 detects that service A is deleted, and generates an event notification corresponding to service A, and sends the event notification to the service scheduling engine.
- the service scheduling engine receives the After the event A4 is sent by the service monitor, the services with the same service domain name sevice1.x.y.z are determined, and the service domain names are reorganized; according to the access IP of service A, the parsed values of the service domain names are 111.111.221.221 and 111.111.221.223; and then the service domain names are reorganized. Send it to global load balancing to make it effective.
- FIG. 2C it is an interaction diagram between a service monitor and a service scheduling engine provided by this application.
- the specific process is as follows:
- Step 201C Monitor the service change status of each service in the service cluster.
- Step 202C Based on the service change status of each service, generate an event notification containing event information corresponding to the corresponding service.
- Step 203C Send the event notification to the service scheduling engine.
- Step 204C Based on the event information contained in each received event notification, generate a service domain name resolution value corresponding to the corresponding service and issue the configuration.
- Step 601 The service monitor monitors the service change status of each service in the corresponding service cluster.
- Step 602 The service monitor determines the service change status of the changed service B.
- Step 603 The service monitor generates a corresponding event notification containing event information based on the service new status of service B.
- Step 604 The service monitor generates a corresponding event notification containing event information based on the service deletion status of service B.
- Step 605 The service scheduling engine determines services with the same service domain name based on the event information contained in the received event notification.
- Step 606 The service scheduling engine obtains the service domain name resolution value of the service based on the access address of the service with the same service domain name.
- Step 607 The service scheduling engine delivers the service domain name resolution value to the global load balancing.
- FIG. 7 is a schematic structural diagram of a service update device 700, which may include:
- the monitoring unit 701 monitors the service change status of each service in the corresponding service cluster
- the generation unit 702 generates an event notification containing event information corresponding to the corresponding service based on the service change status of each service;
- the notification unit 703 sends the event notification to the service scheduling engine in the service update system, so that the service scheduling engine obtains the service domain name resolution value.
- this application can provide the ability to automatically update the global load balancing analysis in real time for service expansion and contraction in multiple clusters in different regions and different cloud providers. That is, this application is suitable for accessing multi-cluster services through global load balancing. In this case, it provides the ability to automatically update the global load balancing analysis in real time for multi-cluster service expansion and contraction.
- the embodiment of the present application also provides another service update device 800.
- another service update device 800 As shown in Figure 8, it is a schematic structural diagram of another service update device, which may include:
- the receiving unit 801 receives an event notification containing event information from at least one service monitor.
- the event notification is generated and sent by the service monitor in the service update system based on the monitored service change status of each service in the corresponding service cluster.
- each service monitor is deployed in a service cluster;
- the generation unit 802 generates a service domain name resolution value corresponding to the corresponding service based on the event information contained in the event notification and issues the configuration.
- the event information includes the service domain name of the corresponding service and the access address of the corresponding service.
- the generating unit 802 is specifically used to:
- the service domain name resolution value of the service is obtained.
- the embodiment of the present application also provides a system.
- the structure of the system can be shown in Figure 9, including a service cluster 901, a service monitor 9011, a service scheduling engine 902 and a global load balancing 903.
- the service cluster 901 serves as the control plane of the service.
- Each service monitor service cluster 901 is configured with a service monitor 9011; the service monitor 9011 monitors service changes, and when there are service changes in the service cluster 901 to which it belongs, the service monitor
- the server 9011 can monitor the corresponding change service information, generate an event, and send the relevant information to the service scheduling engine 902; the service scheduling engine 902 provides a service change interface, is responsible for uniformly processing the domain name resolution of the service, and obtains the corresponding response based on the received relevant information.
- the resolution value is sent to Global Load Balancing 903 to make the resolution effective; Global Load Balancing 903 provides DNS (Domain Name System) service, and visitors can access services in a certain service cluster through Global Load Balancing.
- the service change status includes the service new status and the service deletion status
- the event information includes: the event type corresponding to the service change status, the service domain name of the corresponding service, and the access address of the corresponding service.
- the service monitor 9011 determines that the service change status of the newly started service in the service cluster 901 is the service new status; based on the service new status of the service, it generates a service containing a new service to represent the new service.
- An event notification of the event type of the added service is sent to the service scheduling engine 902; if the shrinkage of the service cluster 901 is detected, it is determined that the service change status of the released service in the service cluster is the service deletion status; based on the service deletion status of the service, An event notification containing an event type characterizing the deletion of the service is generated and sent to the service scheduling engine 902 .
- the service scheduling engine 902 After receiving the event notification, the service scheduling engine 902 determines the service with the same service domain name based on the event information contained in the received event notification, and obtains the service domain name resolution value of the corresponding service based on the access address of the service with the same service domain name. , and finally send it to global load balancing 903 to make the resolution effective.
- embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
- computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
- These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions
- the device implements the functions specified in a process or processes in the flowchart and/or in a block or blocks in the block diagram.
- These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device.
- Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
Abstract
本申请涉及云计算技术领域，尤其涉及一种服务更新方法、装置、系统和存储介质，用以解决相关技术中，全局负载均衡域名解析速度较慢，人工链路长的问题。本申请方法包括：每个所述服务监视器，用于监测相应服务集群中的各个服务的服务变更状态；基于各个服务的服务变更状态，生成与相应服务对应的包含事件信息的事件通知，并发送服务调度引擎；服务调度引擎用于接收至少一个服务监视器的事件通知；基于接收到的各个事件通知包含的事件信息，生成与相应服务对应的服务域名解析值并下发配置。本申请通过服务监视器实现对服务的实时监控，针对多集群服务扩缩容，实现实时自动更新全局负载均衡解析。
Description
本申请涉及云计算技术领域，尤其涉及一种服务更新方法、装置、系统和存储介质。
随着互联网技术的发展，网络服务逐渐丰富，随着服务内容和用户规模的不断增加，对低成本高质量服务的需求越来越迫切，因此云计算及边缘计算得以发展，而其中的k8s（全称kubernetes，或简称为kube）集群网络服务因其能够快速实现业务扩缩容、调度需求受到广泛应用。如今随着边缘计算的不断发展普及，存在选择从不同地区、不同云、不同提供商或不同k8s集群进行部署服务的情况，这就涉及到集群网络中，服务的全局负载均衡域名解析的实时更新。
然而相关技术中的操作是基于人工操作，在部署完服务后，全局负载均衡响应域名，添加服务IP（全称Internet
Protocol，网际互连协议）解析；或者，先移除全局负载均衡响应域名，在服务IP解析完成后释放掉服务，人工链路长，集群网络中服务到全局负载均衡域名解析没有统一的响应机制，针对服务扩缩容，无法做到实时自动更新全局负载均衡解析。
综上，相关技术中的全局负载均衡域名解析速度较慢，人工链路长。
本申请提供一种服务更新方法、装置、系统和存储介质，以至少解决相关技术中，全局负载均衡域名解析速度较慢，人工链路长的问题。
本申请实施例提供的一种服务更新系统，该系统包括：
服务调度引擎，和至少一个服务监视器；每个服务监视器部署于一个服务集群中；
每个所述服务监视器，用于监测相应服务集群中的各个服务的服务变更状态；基于所述各个服务的服务变更状态，生成与相应服务对应的包含事件信息的事件通知，并发送所述服务调度引擎；
所述服务调度引擎，用于接收至少一个服务监视器的事件通知；基于接收到的各个事件通知包含的事件信息，生成与相应服务对应的服务域名解析值并下发配置。
在一些可选的实施例中，所述服务变更状态包括以下至少一种：服务新增状态、服务删除状态；
所述事件信息包括：与所述服务变更状态相应的事件类型、相应服务的服务域名、相应服务的访问地址。
在一些可选的实施例中，所述服务监视器具体用于：
监测到一个服务集群扩容后，确定所述服务集群中新启动服务的所述服务变更状态为服务新增状态；基于所述服务的服务新增状态，生成包含用于表征新增服务的事件类型的事件通知；和/或
监测到一个服务集群缩容后，确定所述服务集群中释放服务的所述服务变更状态为服务删除状态；基于所述服务的服务删除状态，生成包含用于表征删除服务的事件类型的事件通知。
在一些可选的实施例中，所述服务调度引擎具体用于：
基于接收到的所述事件通知包含的事件信息，确定具有相同服务域名的服务；
基于所述具有相同服务域名的服务的访问地址，获得所述服务的服务域名解析值。
本申请实施例提供的一种服务更新方法，应用于服务更新系统中的服务监视器，该方法包括：
监测相应服务集群中的各个服务的服务变更状态；
基于所述各个服务的服务变更状态，生成与相应服务对应的包含事件信息的事件通知；
将所述事件通知发送给所述服务更新系统中的服务调度引擎，以使所述服务调度引擎基于接收到的各个事件通知包含的事件信息，生成与相应服务对应的服务域名解析值并下发配置。
本申请实施例提供的一种服务更新方法，应用于服务更新系统中的服务调度引擎，该方法包括：
接收至少一个服务监视器发送的包含事件信息的事件通知，其中，所述事件通知是由所述服务更新系统中服务监视器，基于监测到的相应服务集群中的各个服务的服务变更状态，生成并发送至所述服务调度引擎的，每个服务监视器部署于一个服务集群中；
基于所述事件通知包含的事件信息，生成与相应服务对应的服务域名解析值并下发配置。
在一些可选的实施例中，所述事件信息包括相应服务的服务域名、相应服务的访问地址；
基于所述事件通知包含的事件信息，生成与相应服务对应的服务域名解析值，包括：
基于接收到的所述事件通知包含的事件信息，确定具有相同服务域名的服务；
基于所述具有相同服务域名的服务的访问地址，获得所述服务的服务域名解析值。
本申请实施例提供的一种服务更新装置，包括：
监测单元，监测相应服务集群中的各个服务的服务变更状态；
生成单元，基于所述各个服务的服务变更状态，生成与相应服务对应的包含事件信息的事件通知；
通知单元，将所述事件通知发送给所述服务更新系统中的服务调度引擎，以使所述服务调度引擎获取服务域名解析值。
本申请实施例提供的一种服务更新装置，包括：
接收单元，接收至少一个服务监视器包含事件信息的事件通知，其中，所述事件通知是由所述服务更新系统中服务监视器，基于监测到的相应服务集群中的各个服务的服务变更状态，生成并发送至所述服务调度引擎的，每个服务监视器部署于一个服务集群中；
生成单元，基于所述事件通知包含的事件信息，生成与相应服务对应的服务域名解析值并下发配置。
在一些可选的实施例中，所述事件信息包括相应服务的服务域名、相应服务的访问地址，所述生成单元具体用于：
基于接收到的所述事件通知包含的事件信息，确定具有相同服务域名的服务；
基于所述具有相同服务域名的服务的访问地址，获得所述服务的服务域名解析值。
本申请实施例提供一种计算机可读存储介质，其包括计算机程序，当所述计算机程序在电子设备上运行时，所述计算机程序用于使所述电子设备执行上述任一服务更新方法的步骤。
本申请有益效果如下：
本申请实施例提供了一种服务更新方法、装置、系统和存储介质。由于相关技术中服务更新操作都是基于人工时限完成，集群网络中服务到全局负载均衡域名解析没有统一的响应机制，无法做到快速自动更新，而本申请通过在各个服务集群中增加部署一个服务监视器，监测服务的变更状态，并生成对应的事件通知发送给服务调度引擎以获取服务域名的新的解析值，最后由服务调度引擎下发至全局负载均衡使其实时生效，实现服务的快速自动更新。
本申请的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请而了解。本申请的目的和其他优点可通过在所写的说明书、权利要求书、以及附图中所特别指出的结构来实现和获得。
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1为本申请实施例提供的一种服务更新方法的应用场景示意图；
图2A为本申请实施例提供的一种服务更新方法的整体流程图；
图2B为本申请实施例提供的另一种服务更新方法的整体流程图；
图2C为本申请提供的一种服务监视器与服务调度引擎的交互图；
图3为本申请实施例提供的一种新增事件对应的事件通知表格；
图4为本申请实施例提供的另一种新增事件对应的事件通知表格；
图5为本申请实施例提供的一种删除事件对应的事件通知表格；
图6为本申请实施例提供的一种基于实际应用场景下服务更新的整体流程图；
图7为本申请实施例提供的一种服务更新装置的组成结构示意图；
图8为本申请实施例提供的另一种服务更新装置的组成结构示意图；
图9为本申请实施例提供的一种系统组成结构示意图。
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合本申请实施例中的附图，对本申请的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请技术方案的一部分实施例，而不是全部的实施例。基于本申请文件中记载的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请技术方案保护的范围。
下面对本申请实施例中涉及的部分概念进行介绍。
服务集群：一组用于运行容器化应用的节点计算机，作为一个整体提供网络资源；本申请中，服务集群有多个，每个服务集群中有多个服务以及一个服务监视器，服务增加时服务集群扩容，服务删除时服务集群缩容。
服务监视器：部署于各个服务集群中，负责监测各个服务集群中服务的服务变更状态，并将发生变更的服务生成对应的事件通知发送给服务调度引擎。
服务调度引擎：能够对服务调度进行设置与管理，为各种需要调度的场景提供调度功能，本申请中，服务调度引擎提供服务变更接口，接收服务监视器发送的事件通知，并基于事件通知处理服务的域名解析，获取服务域名的解析值，下发至全局负载均衡，使解析生效。
全局负载均衡：全称Global Server Load Balancing，简称GSLB，负责对分别放置在不同的地理位置、有不同网络结构的服务器群间作负载均衡。负载均衡负责将负载平衡、分摊到多个操作单元上进行运行，以将网络流量平均发送到多个服务器。
服务变更状态：服务集群中的服务发生因为增加或释放发生变更，本申请中，服务变更状态包括服务新增状态与服务删除状态，若服务集群中新增一个或多个服务，则称这一个或多个服务的服务变更状态为服务新增状态；若服务集群中删除一个或多个服务，则称这一个或多个服务的服务变更状态为服务删除状态。
事件通知：由服务监视器在监测到服务集群中发生服务的增加或删除时生成的，带有事件信息的通知，事件信息包含了与服务变更状态相应的事件类型、相应服务的服务域名以及相应服务的访问地址。
以下结合说明书附图对本申请的优选实施例进行说明，应当理解，此处所描述的优选实施例仅用于说明和解释本申请，并不用于限定本申请，并且在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
如图1所示，其为本申请实施例的应用场景示意图。该应用场景图中包括服务监视器110与服务调度引擎120。
假设，某视频公司推出一个新视频，并将该视频添加至多个服务集群，例如具有监视服务变更能力的k8s集群，被添加视频服务的服务集群中的服务监视器110监测到有服务的服务变更状态为服务新增状态，即有新的服务添加至该服务集群中后，获取并生成该服务对应的事件通知，事件通知中包含有与服务变更状态相应的事件类型、相应服务的服务域名以及相应服务的访问地址，进而，服务监视器110将事件通知发送给服务调度引擎120。同样的，若有服务在服务集群中删除，服务监视器110监测到该服务的服务变更状态为服务删除状态，获取并生成该服务对应的事件通知并发送给服务调度引擎120。
服务调度引擎120在接收到事件通知后，基于接收到的事件通知确定具有相同服务域名的服务，并根据服务的访问地址，获得该服务的服务域名解析值，最后下发至全局负载均衡，使解析生效。
需要说明的是，图1所示只是举例说明，实际上服务监视器和服务集群的数量不受限制，在本申请实施例中不做具体限定。
此外，本申请实施例可应用于各种场景，包括但不限于云技术、人工智能、智慧交通等场景。
下面结合上述描述的应用场景，参考附图来描述本申请示例性实施方式提供的服务更新方法，需要注意的是，上述应用场景仅是为了便于理解本申请的精神和原理而示出，本申请的实施方式在此方面不受任何限制。
参阅图2A，其为本申请实施例提供的一种服务更新方法的实施流程图，以服务监视器为执行主体，该方法的具体实施流程如下S201A-S202A：
S201A：监测服务集群中的各个服务的服务变更状态。
其中，服务集群是一组用于运行容器化应用的节点计算机，作为一个整体提供网络资源；服务集群通常有多个，每个服务集群中有多个服务以及一个服务监视器，服务监视器负责监测各个服务集群中服务的服务变更状态，即服务集群中的服务是否发生增加或删除。
假设存在服务集群1，服务集群2，服务集群3，每个服务集群中都有一个服务监视器，即服务集群1中有服务监视器1，服务集群2中有服务监视器2，服务集群3中有服务监视器3，现有一服务A，部署在服务集群1与服务集群2中，各个服务集群中的服务监视器能够检测到各自服务集群的服务变化，及服务的服务变更状态。
S202A：基于各个服务的服务变更状态，生成与相应服务对应的包含事件信息的事件通知，并发送至服务调度引擎。
其中，服务变更状态包括服务新增状态及服务删除状态，若服务集群中新增一个或多个服务，则称这一个或多个服务的服务变更状态为服务新增状态；若集群中删除一个或多个服务，则称这一个或多个服务的服务变更状态为服务删除状态。事件通知是由服务监视器在监测到服务集群中发生服务的增加或删除时生成的，带有事件信息的通知，事件信息包括：与服务变更状态相应的事件类型、相应服务的服务域名、相应服务的访问地址。
在服务集群中的服务发生变更后，服务监视器基于发生变更的服务的服务变更状态，生成与该服务对应的包含事件信息的事件通知。
具体地，若服务监视器监测到所在的服务集群扩容，则确定服务集群中新启动服务的服务变更状态为服务新增状态，基于服务的服务新增状态，生成对应该服务的事件通知，事件通知中包含有用于表征该服务为新增服务的事件类型、该服务的服务域名及该服务的访问地址。
同样的，若服务监视器监测到所在的服务集群缩容，则确定服务集群中释放服务的服务变更状态为服务删除状态，基于服务的服务删除状态，生成对应该服务的事件通知，事件通知中包含有用于表征该服务为删除服务的事件类型、该服务的服务域名及该服务的访问地址。
因此，本申请通过服务监视器实现了对服务集群网络中服务的实时性监控，可以实现多集群服务扩缩容事件的通知。
依旧以S201A中的假设为例，在服务A部署到服务集群1与服务集群2中并启动后，服务集群1中的服务监视器1与服务集群2中的服务监视器2监测到各自服务集群的服务发生变化，即新增一个服务A，服务监视器1与服务监视器2确定服务A的服务变更状态为服务新增状态，则生成对应服务A的事件通知，如图3所示，为本申请实施例提供的一种新增事件对应的事件通知表格，其中，事件A1即为服务监视器1生成的对应服务A的事件通知，事件A2即为服务监视器2生成的对应服务A的事件通知，事件通知中包含了事件类型ADD，表明服务A在服务集群1与服务集群2中是一个新增服务，还包含服务A的服务域名：sevice1.x.y.z，以及服务A的访问IP，即访问地址：111.111.221.221与111.111.221.222。
同样的，若在服务集群3中进行扩容服务A，服务A顺利启动后，服务集群3中的服务监视器3监测到所在服务集群新增一个服务A，且确定服务A的服务变更状态为服务新增状态，则生成对应服务A的事件通知，如图4所示，为本申请实施例提供的另一种新增事件对应的事件通知表格，其中，事件A3即为服务监视器3生成的对应服务A的事件通知，事件通知中包含了事件类型ADD，表明服务A在服务集群2中是一个新增服务，还包含服务A的服务域名：sevice1.x.y.z，以及服务A的访问IP，即访问地址：111.111.221.223。
若此后在服务集群2中缩容服务A，即将服务A删除，服务集群2中的服务监视器2监测到服务集群的服务发生变化，即服务A被删除，服务监视器2确定服务A的服务变更状态为服务删除状态，之后生成对应服务A的事件通知，如图5所示，为本申请实施例提供的一种删除事件对应的事件通知表格，其中，事件A4即为服务监视器2生成的对应服务A的事件通知，事件通知中包含了事件类型DEL，表明服务A在服务集群2中是一个删除服务，还包含服务A的服务域名：sevice1.x.y.z，以及服务A的访问IP，即访问地址：111.111.221.222。
之后，服务监视器将事件通知发送给服务更新系统中的服务调度引擎以使服务调度引擎基于接收到的各个事件通知包含的事件信息，生成与相应服务对应的服务域名解析值并下发配置。
下面从服务调度引擎侧，对本申请实施例中的服务更新方法进行简单介绍：
参阅图2B所示，为本申请实施例提供的另一种服务更新方法的实施流程图，以服务调度引擎为执行主体，该方法的具体实施流程如下：
S201B：接收服务监视器的事件通知。
其中，事件通知是由服务更新系统中服务监视器，基于监测到的相应服务集群中的各个服务的服务变更状态，生成并发送至服务调度引擎的，每个服务监视器部署于一个服务集群中。
S202B：基于接收到的各个事件通知包含的事件信息，生成与相应服务对应的服务域名解析值并下发配置。
服务调度引擎是能够进行对服务调度进行设置与管理，为各种需要调度的场景提供调度功能，本申请中，服务调度引擎能够提供中心化统一接口进行实时更新全局负载均衡解析的能力；即服务调度引擎提供服务变更接口，接收服务监视器发送的事件通知，并基于事件通知处理服务的域名解析，获取服务域名的解析值，下发至全局负载均衡，使解析生效。全局负载均衡则是对分别放置在不同的地理位置、有不同网络结构的服务器群间作负载均衡。负载均衡负责将负载平衡、分摊到多个操作单元上进行运行，以将网络流量平均发送到多个服务器。
具体地，服务调度引擎接收到各个服务监视器发送的事件通知后， 基于接收到的事件通知包含的事件信息，生成与相应服务对应的服务域名解析值并下发配置。
其中，服务的服务域名解析值的获取，具体是服务调度引擎首先确定拥有相同服务域名的服务，并基于具有相同服务域名的服务的访问地址得到的。
因此，本申请通过服务调度引擎，能够提供中心化统一接口，实时更新全局负载均衡解析，提升底层能力的通用性。
依旧以S201A中的假设为例，在服务A部署到服务集群1与服务集群2中并启动后，服务集群1中的服务监视器1与服务集群2中的服务监视器2生成了各自对应服务A的事件通知，并将事件通知发送至服务调度引擎，服务调度引擎接收到服务监视器发送的事件A1与事件A2后，确定拥有相同服务域名sevice1.x.y.z的服务，即将服务域名进行重新组合；根据服务A的访问IP得到服务域名的解析值为111.111.221.221和111.111.221.222；之后将其下发至全局负载均衡使其生效。
此时，若有访客访问服务A的服务域名sevice1.x.y.z，即可能会访问到服务集群1中访问IP为111.111.221.221的服务A，或访问到服务集群2中访问IP为111.111.221.222的服务A，得到响应。
同样的，在服务集群3中进行扩容服务A后，服务集群3中的服务监视器3监测到服务A启动，则生成对应服务A的事件通知，并将事件通知发送至服务调度引擎，服务调度引擎接收到服务监视器发送的事件A3后，确定拥有相同服务域名sevice1.x.y.z的服务，即将服务域名进行重新组合；根据服务A的访问IP得到服务域名的解析值为111.111.221.221、111.111.221.222和111.111.221.223；之后将其下发至全局负载均衡使其生效。
此时，若再有访客访问服务A的服务域名sevice1.x.y.z，即可能会访问到服务集群1中访问IP为111.111.221.221的服务A，或访问到服务集群2中访问IP为111.111.221.222的服务A，或访问到服务集群3中访问IP为111.111.221.223的服务A，即访客有几率访问到服务集群3中的服务A，得到响应。
在服务集群2中缩容服务A后，服务集群2中的服务监视器2监测到服务A删除，则生成对应服务A的事件通知，并将事件通知发送至服务调度引擎，服务调度引擎接收到服务监视器发送的事件A4后，确定拥有相同服务域名sevice1.x.y.z的服务，即将服务域名进行重新组合；根据服务A的访问IP得到服务域名的解析值为111.111.221.221和111.111.221.223；之后将其下发至全局负载均衡使其生效。
此时访客再次访问服务A的服务域名sevice1.x.y.z，即只会访问到服务集群1中访问IP为111.111.221.221的服务A，或访问到服务集群3中访问IP为111.111.221.223的服务A，得到响应，即访客无法再访问到服务集群2中的服务A。
如图2C，为本申请提供的一种服务监视器与服务调度引擎的交互图，具体过程如下：
步骤201C：监测服务集群中的各个服务的服务变更状态。
步骤202C：基于各个服务的服务变更状态，生成与相应服务对应的包含事件信息的事件通知。
步骤203C：将事件通知发送给服务调度引擎。
步骤204C：基于接收到的各个事件通知包含的事件信息，生成与相应服务对应的服务域名解析值并下发配置。
基于上述过程，假设现有多个服务集群，每个服务集群中都有一个服务监视器，服务B存在于上述多个服务集群中的部分集群中，现在针对服务B在上述多个服务集群中的某些服务集群，进行了扩容或缩容，如图6所示，为基于该应用场景下，本申请实施例提供的一种服务更新的整体流程图。
步骤601：服务监视器监测相应服务集群中的各个服务的服务变更状态。
步骤602：服务监视器确定发生变更的服务B的服务变更状态。
步骤603：服务监视器基于服务B的服务新增状态，生成对应的包含事件信息的事件通知。
步骤604：服务监视器基于服务B的服务删除状态，生成对应的包含事件信息的事件通知。
步骤605：服务调度引擎基于接收到的事件通知包含的事件信息，确定具有相同服务域名的服务。
步骤606：服务调度引擎基于具有相同服务域名的服务的访问地址，获得服务的服务域名解析值。
步骤607：服务调度引擎将服务域名解析值下发至全局负载均衡。
基于相同的发明构思，本申请实施例还提供一种服务更新装置，如图7所示，其为服务更新装置700的结构示意图，可以包括：
监测单元701，监测相应服务集群中的各个服务的服务变更状态；
生成单元702，基于各个服务的服务变更状态，生成与相应服务对应的包含事件信息的事件通知；
通知单元703，将事件通知发送给服务更新系统中的服务调度引擎，以使服务调度引擎获取服务域名解析值。
综上，本申请可以提供在不同地区、不同云提供商的多集群中，对服务扩缩容自动化实时更新全局负载均衡解析的能力，即本申请适用于对多集群服务通过全局负载均衡进行访问的情况，提供多集群服务扩缩容自动化实时更新全局负载均衡解析的能力。
基于相同的发明构思，本申请实施例还提供另一种服务更新装置800。如图8所示，其为另一种服务更新装置的结构示意图，可以包括：
接收单元801，接收至少一个服务监视器包含事件信息的事件通知，其中，事件通知是由服务更新系统中服务监视器，基于监测到的相应服务集群中的各个服务的服务变更状态，生成并发送至服务调度引擎的，每个服务监视器部署于一个服务集群中；
生成单元802，基于事件通知包含的事件信息，生成与相应服务对应的服务域名解析值并下发配置。
在一些可选的实施例中，事件信息包括相应服务的服务域名、相应服务的访问地址，生成单元802具体用于：
基于接收到的事件通知包含的事件信息，确定具有相同服务域名的服务；
基于具有相同服务域名的服务的访问地址，获得服务的服务域名解析值。
在介绍了本申请示例性实施方式的服务更新方法和装置之后，接下来，介绍根据本申请的另一示例性实施方式的系统。
所属技术领域的技术人员能够理解，本申请的各个方面可以实现为系统、方法或程序产品。因此，本申请的各个方面可以具体实现为以下形式，即：完全的硬件实施方式、完全的软件实施方式（包括固件、微代码等），或硬件和软件方面结合的实施方式，这里可以统称为“电路”、“模块”或“系统”。
与上述方法实施例基于同一发明构思，本申请实施例中还提供了一种系统。系统的结构可以如图9所示，包括服务集群901，服务监视器9011，服务调度引擎902以及全局负载均衡903。
其中，服务集群901作为服务的控制面，每个服务监视器服务集群901都配置一个服务监视器9011；服务监视器9011监控服务的变更，并在所属的服务集群901存在服务变更时，服务监视器9011可以监测到对应的变更服务的信息，生成事件，将相关信息发送给服务调度引擎902；服务调度引擎902提供服务变更接口，负责统一处理服务的域名解析，根据接收到的相关信息得到对应的解析值并下发至全局负载均衡903使解析生效；全局负载均衡903则提供DNS（全称Domain Name System，域名系统）服务，访客可以通过全局负载均衡访问到某一服务集群中的服务。
其中，服务变更状态包括服务新增状态和服务删除状态；事件信息包括：与服务变更状态相应的事件类型、相应服务的服务域名、相应服务的访问地址。
具体的，服务监视器9011在监测到所在服务集群901扩容后，确定服务集群901中新启动服务的服务变更状态为服务新增状态；基于该服务的服务新增状态，生成包含用于表征新增服务的事件类型的事件通知并发送至服务调度引擎902；若监测到所在服务集群901缩容，则确定服务集群中释放服务的服务变更状态为服务删除状态；基于该服务的服务删除状态，生成包含用于表征删除服务的事件类型的事件通知并发送至服务调度引擎902。服务调度引擎902在接收到事件通知后，基于接收到的事件通知包含的事件信息，确定具有相同服务域名的服务，并基于具有相同服务域名的服务的访问地址，获得对应服务的服务域名解析值，最后下发至全局负载均衡903使解析生效。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质（包括但不限于磁盘存储器、CD-ROM、光学存储器等）上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备（系统）、和计算机程序产品的流程图和／或方框图来描述的。应理解可由计算机程序指令实现流程图和／或方框图中的每一流程和／或方框、以及流程图和／或方框图中的流程和／或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和／或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和／或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和／或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。
Claims (10)
- 一种服务更新系统，其特征在于，该系统包括：服务调度引擎，和至少一个服务监视器；每个服务监视器部署于一个服务集群中；每个所述服务监视器，用于监测相应服务集群中的各个服务的服务变更状态；基于所述各个服务的服务变更状态，生成与相应服务对应的包含事件信息的事件通知，并发送所述服务调度引擎；所述服务调度引擎，用于接收至少一个服务监视器的事件通知；基于接收到的各个事件通知包含的事件信息，生成与相应服务对应的服务域名解析值并下发配置。
- 如权利要求1所述的系统，其特征在于，所述服务变更状态包括以下至少一种：服务新增状态、服务删除状态；所述事件信息包括：与所述服务变更状态相应的事件类型、相应服务的服务域名、相应服务的访问地址。
- 如权利要求2所述的系统，其特征在于，所述服务监视器具体用于：监测到一个服务集群扩容后，确定所述服务集群中新启动服务的所述服务变更状态为服务新增状态；基于所述服务的服务新增状态，生成包含用于表征新增服务的事件类型的事件通知；和/或监测到一个服务集群缩容后，确定所述服务集群中释放服务的所述服务变更状态为服务删除状态；基于所述服务的服务删除状态，生成包含用于表征删除服务的事件类型的事件通知。
- 如权利要求2所述的系统，其特征在于，所述服务调度引擎具体用于：基于接收到的所述事件通知包含的事件信息，确定具有相同服务域名的服务；基于所述具有相同服务域名的服务的访问地址，获得所述服务的服务域名解析值。
- 一种服务更新方法，其特征在于，应用于服务更新系统中的服务监视器，该方法包括：监测相应服务集群中的各个服务的服务变更状态；基于所述各个服务的服务变更状态，生成与相应服务对应的包含事件信息的事件通知；将所述事件通知发送给所述服务更新系统中的服务调度引擎，以使所述服务调度引擎基于接收到的各个事件通知包含的事件信息，生成与相应服务对应的服务域名解析值并下发配置。
- 一种服务更新方法，其特征在于，应用于服务更新系统中的服务调度引擎，该方法包括：接收至少一个服务监视器发送的包含事件信息的事件通知，其中，所述事件通知是由所述服务更新系统中服务监视器，基于监测到的相应服务集群中的各个服务的服务变更状态，生成并发送至所述服务调度引擎的，每个服务监视器部署于一个服务集群中；基于所述事件通知包含的事件信息，生成与相应服务对应的服务域名解析值并下发配置。
- 如权利要求6所述的方法，其特征在于，所述事件信息包括相应服务的服务域名、相应服务的访问地址；基于所述事件通知包含的事件信息，生成与相应服务对应的服务域名解析值，包括：基于接收到的所述事件通知包含的事件信息，确定具有相同服务域名的服务；基于所述具有相同服务域名的服务的访问地址，获得所述服务的服务域名解析值。
- 一种服务更新装置，其特征在于，包括：监测单元，监测相应服务集群中的各个服务的服务变更状态；生成单元，基于所述各个服务的服务变更状态，生成与相应服务对应的包含事件信息的事件通知；通知单元，将所述事件通知发送给所述服务更新系统中的服务调度引擎，以使所述服务调度引擎获取服务域名解析值。
- 一种服务更新装置，其特征在于，包括：接收单元，接收至少一个服务监视器包含事件信息的事件通知，其中，所述事件通知是由所述服务更新系统中服务监视器，基于监测到的相应服务集群中的各个服务的服务变更状态，生成并发送至所述服务调度引擎的，每个服务监视器部署于一个服务集群中；生成单元，基于所述事件通知包含的事件信息，生成与相应服务对应的服务域名解析值并下发配置。
- 一种计算机可读存储介质，其特征在于，包括计算机程序，当所述计算机程序在电子设备上运行时，所述计算机程序用于使所述电子设备执行权利要求5~7中任一所述方法的步骤。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210905327.8A CN115225645B (zh) | 2022-07-29 | 一种服务更新方法、装置、系统和存储介质 | |
| CN202210905327.8 | 2022-07-29 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2024021471A1 true WO2024021471A1 (zh) | 2024-02-01 |
Family
ID=83614129
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2022/141412 WO2024021471A1 (zh) | 2022-07-29 | 2022-12-23 | 一种服务更新方法、装置、系统和存储介质 |
Country Status (1)
| Country | Link |
|---|---|
| WO (1) | WO2024021471A1 (zh) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140304399A1 (en) * | 2013-04-06 | 2014-10-09 | Citrix Systems, Inc. | Systems and methods for providing monitoring in a cluster system |
| CN111277631A (zh) * | 2020-01-13 | 2020-06-12 | 广州虎牙科技有限公司 | 负载均衡的配置方法、装置、系统、设备及存储介质 |
| CN113656168A (zh) * | 2021-07-16 | 2021-11-16 | 新浪网技术(中国)有限公司 | 一种流量的自动容灾和调度的方法、系统、介质和设备 |
| CN114745358A (zh) * | 2022-03-23 | 2022-07-12 | 网宿科技股份有限公司 | 负载均衡服务中的ip地址管理方法、系统及控制器 |
| CN115225645A (zh) * | 2022-07-29 | 2022-10-21 | 天翼云科技有限公司 | 一种服务更新方法、装置、系统和存储介质 |
-
2022
- 2022-12-23 WO PCT/CN2022/141412 patent/WO2024021471A1/zh unknown
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140304399A1 (en) * | 2013-04-06 | 2014-10-09 | Citrix Systems, Inc. | Systems and methods for providing monitoring in a cluster system |
| CN111277631A (zh) * | 2020-01-13 | 2020-06-12 | 广州虎牙科技有限公司 | 负载均衡的配置方法、装置、系统、设备及存储介质 |
| CN113656168A (zh) * | 2021-07-16 | 2021-11-16 | 新浪网技术(中国)有限公司 | 一种流量的自动容灾和调度的方法、系统、介质和设备 |
| CN114745358A (zh) * | 2022-03-23 | 2022-07-12 | 网宿科技股份有限公司 | 负载均衡服务中的ip地址管理方法、系统及控制器 |
| CN115225645A (zh) * | 2022-07-29 | 2022-10-21 | 天翼云科技有限公司 | 一种服务更新方法、装置、系统和存储介质 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115225645A (zh) | 2022-10-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11740975B2 (en) | System and method for managing blockchain nodes | |
| WO2020177533A1 (zh) | 电子票据标识分配方法、电子票据生成方法、装置及系统 | |
| US11553034B2 (en) | Server computer management system for supporting highly available virtual desktops of multiple different tenants | |
| JP4900982B2 (ja) | サーバ・クラスタにおいてフェイルオーバを管理するための方法、フェイルオーバ・サーバ及びコンピュータ・プログラム | |
| WO2019061720A1 (zh) | 一种数据同步的方法和系统 | |
| US9723110B2 (en) | System and method for supporting a proxy model for across-domain messaging in a transactional middleware machine environment | |
| CN110262902B (zh) | 信息处理方法及系统、介质和计算设备 | |
| CN107534570A (zh) | 虚拟化网络功能监控 | |
| CN110505275A (zh) | 数据传输方法、系统、服务器及计算机可读存储介质 | |
| CN111277432A (zh) | 配置信息更新方法、装置、电子设备及存储介质 | |
| CN109783151B (zh) | 规则变更的方法和装置 | |
| CN112882792B (zh) | 信息加载方法、计算机设备及存储介质 | |
| CN111064626A (zh) | 配置更新方法、装置、服务器及可读存储介质 | |
| US9106676B1 (en) | Grid-based server messaging infrastructure | |
| CN110413369A (zh) | 用于虚拟化环境中的备份的系统和方法 | |
| CN114615268B (zh) | 基于Kubernetes集群的服务网络、监控节点、容器节点及设备 | |
| WO2024021471A1 (zh) | 一种服务更新方法、装置、系统和存储介质 | |
| CN113726638B (zh) | 一种多云多芯容器管理的方法、装置及设备、存储介质 | |
| CN115225645B (zh) | 一种服务更新方法、装置、系统和存储介质 | |
| CN114598700A (zh) | 通信方法及通信系统 | |
| CN114338670A (zh) | 一种边缘云平台和具有其的网联交通三级云控平台 | |
| CN114930313A (zh) | 用于管理区块链节点的系统和方法 | |
| CN111209118A (zh) | 确定资源余量的方法、装置、存储介质和电子设备 | |
| CN114884956B (zh) | 多集群架构的实现方法、装置及多集群架构系统 | |
| KR20190074717A (ko) | 클라우드 컴퓨팅 환경에서 클러스터 구성 및 관리 시스템 및 그 방법 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22952902 Country of ref document: EP Kind code of ref document: A1 |