Method for processing multiple servers
By grouping servers and selecting a group head node, and connecting them to the cloud management platform using transport layer security authentication or one-time password tokens, the problem of batch registration of server public keys is solved, achieving efficient automated deployment.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- LENOVO (BEIJING) LTD
- Filing Date
- 2026-03-31
- Publication Date
- 2026-06-23
AI Technical Summary
In existing technologies, when general-purpose servers are deployed at the edge, it is impossible to preload public keys to the cloud management platform in batches, resulting in cumbersome and inefficient manual operations.
Multiple servers are grouped, and one server is selected from the group as the group head node. The Uniform Resource Locator and public key of the cloud management platform are preloaded. A connection is established with the cloud management platform through transport layer security authentication or one-time password token to realize the automatic uploading of the public key.
It enables automated registration of public keys across multiple servers, reducing manual operations and improving deployment efficiency and convenience.
Smart Images
Figure CN122268908A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of servers, and in particular to a method for processing multiple servers. Background Technology
[0002] Currently, the deployment of general-purpose servers at the edge requires addressing the issue of how each node registers with the cloud. Existing edge server deployments involve preloading the public key and URL (Uniform Resource Locator) of the cloud portal to the edge server. The public and private keys of the edge server are generated in the factory, with the private key stored within the edge server itself. The public key of the edge server needs to be manually preloaded into the cloud management platform.
[0003] Because the number of general-purpose servers is quite large, when general-purpose servers are deployed as edge servers, it is not possible to manually preload the public keys of the general-purpose servers to the cloud management platform one by one. Summary of the Invention
[0004] The purpose of this application is to provide a multi-server processing method.
[0005] This application provides a multi-server processing method, including: Multiple servers are grouped according to a preset logic to obtain multiple server groups, and the multiple server groups include at least the first server group; Select any one server from the first server group as the first server; The first server preloads the Uniform Resource Locator (URL) of the cloud management platform and establishes a connection with the cloud management platform based on the URL; or, the first server preloads the URL and public key of the cloud management platform and establishes a connection with the cloud management platform based on the URL and public key. The first server provides at least one Uniform Resource Locator (URL) from the cloud management platform to the second server within its first server group; The second server establishes a connection with the cloud management platform based on a Uniform Resource Locator (URI), and sends the public key of the second server to the cloud management platform through the first server.
[0006] In some embodiments, a Uniform Resource Locator (URL) of a cloud management platform is preloaded in a first server, and the first server establishes a connection with the cloud management platform based on the URL, including: The first server preloads the Uniform Resource Locator (URL) of the cloud management platform. Based on the URL, the first server establishes a connection with the cloud management platform through transport layer security authentication.
[0007] In some embodiments, the first server establishes a connection with the cloud management platform based on a Uniform Resource Locator (URL) and via transport layer security authentication, including: The first server generates a first certificate signing request and sends it to the cloud management platform, which then issues a first sub-certificate with the cloud management platform's certificate as the root certificate based on the first certificate signing request, and loads the first sub-certificate onto the first server; the first certificate signing request contains the first server's public key; The first server uses the first sub-certificate to establish a two-way transport layer secure link with the cloud management platform.
[0008] In some embodiments, the second server establishes a connection with the cloud management platform based on a Uniform Resource Locator (URL), including: The second server generates a second certificate signing request and sends it to the first server, enabling the first server to issue a second sub-certificate with the first server's certificate as the root certificate based on the second certificate signing request, and to load the second sub-certificate into the second server; the second certificate signing request contains the second server's public key; The second server requests the Uniform Resource Locator (URL) from the first server to obtain the cloud management platform. The second server establishes a two-way transport layer secure link with the cloud management platform based on the obtained Uniform Resource Locator and using the second sub-certificate.
[0009] In some embodiments, the second server sends its public key to the cloud management platform through the first server, including: When the second server establishes a two-way transport layer secure link with the cloud management platform using the second sub-certificate, the cloud management platform can extract the public key of the second server through the second sub-certificate, or the second server can send its public key to the cloud management platform based on the two-way transport layer secure link.
[0010] In some embodiments, a Uniform Resource Locator (URL) and public key of a cloud management platform are preloaded in a first server. The first server establishes a connection with the cloud management platform based on the URL and public key, including: The first server preloads the Uniform Resource Locator (URL) and public key of the cloud management platform, and establishes a connection with the cloud management platform through a one-time password token.
[0011] In some embodiments, the first server establishes a connection with the cloud management platform via a one-time password token, including: The first server generates a first shared key based on its private key and the public key of the cloud management platform, and sends the first shared key to the cloud management platform. The cloud management platform preloads the public key of the first server. The cloud management platform generates a second shared key based on the private key of the cloud management platform and the public key of the first server, and verifies whether the first shared key and the second shared key are consistent. If they are consistent, the first server is allowed to establish a communication connection with the cloud management platform.
[0012] In some embodiments, the second server establishes a connection with the cloud management platform based on a Uniform Resource Locator (URL), and sends the public key of the second server to the cloud management platform through the first server, including: The second server requests the Uniform Resource Locator and public key of the cloud management platform from the first server; The second server uploads its public key to the cloud management platform through the connection channel between the first server and the cloud management platform. The second server generates a third shared key based on its private key and the public key of the cloud management platform, and sends the third shared key to the cloud management platform through the connection channel between the first server and the cloud management platform. The cloud management platform generates a fourth shared key based on the private key of the cloud management platform and the public key of the second server, and verifies whether the third shared key and the fourth shared key are consistent. If they are consistent, the second server is allowed to establish a communication connection with the cloud management platform.
[0013] In some embodiments, the plurality of server groups further includes a second server group, and the method further includes: Choose any one server from the second server group as the third server; The first server provides the third server with at least a Uniform Resource Locator (URL) for the cloud management platform; The third server establishes a connection with the cloud management platform based on a Uniform Resource Locator (URL), and sends the third server's public key to the cloud management platform through the first server.
[0014] In some embodiments, the method further includes: The third server provides at least one Uniform Resource Locator (URL) from the cloud management platform to the fourth server within its second server group; The fourth server establishes a connection with the cloud management platform based on the Uniform Resource Locator (URL), and sends the public key of the fourth server to the cloud management platform through the third server. Attached Figure Description
[0015] Figure 1 This is a flowchart illustrating a multi-server processing method provided in an embodiment of this application. Figure 2 This is a schematic diagram illustrating how multiple server groups establish a connection with a cloud portal via TLS authentication, as provided in an embodiment of this application. Figure 3 This is a schematic diagram illustrating how multiple server groups establish a connection with a cloud portal using a one-time password token, as provided in an embodiment of this application. Detailed Implementation
[0016] Various embodiments and features of this application are described herein with reference to the accompanying drawings.
[0017] It should be understood that various modifications can be made to the embodiments described herein. Therefore, the above description should not be considered as limiting, but merely as an example of embodiments. Other modifications within the scope and spirit of this application will be apparent to those skilled in the art.
[0018] The accompanying drawings, which are included in and form part of this specification, illustrate embodiments of the present application and, together with the general description of the present application given above and the detailed description of the embodiments given below, serve to explain the principles of the present application.
[0019] These and other features of this application will become apparent from the following description of preferred forms of embodiments given as non-limiting examples, with reference to the accompanying drawings.
[0020] It should also be understood that although this application has been described with reference to some specific examples, those skilled in the art can certainly implement many other equivalent forms of this application.
[0021] The above and other aspects, features and advantages of this application will become more apparent when taken in conjunction with the accompanying drawings and in view of the following detailed description.
[0022] Specific embodiments of this application are described thereafter with reference to the accompanying drawings; however, it should be understood that the claimed embodiments are merely examples of this application, which can be implemented in various ways. Well-known and / or repeated functions and structures are not described in detail to avoid unnecessary or redundant details that could obscure the application. Therefore, the specific structural and functional details claimed herein are not intended to be limiting, but merely serve as the basis and representative basis for the claims to teach those skilled in the art to use this application in a variety of substantially any suitable detailed structures.
[0023] This specification may use the phrases “in one embodiment,” “in another embodiment,” “in yet another embodiment,” or “in other embodiments,” all of which may refer to one or more of the same or different embodiments according to this application.
[0024] This application provides a multi-server processing method, such as... Figure 1 As shown, the multi-server processing method includes: S100: Group multiple servers according to a preset logic to obtain multiple server groups, and the multiple server groups include at least the first server group; Specifically, users can group servers according to their server numbers within the server cluster. For example, servers numbered 1-10 can be grouped into the first server group, and servers numbered 11-20 into the second server group, etc. Servers numbered 100-91 can also be grouped into the first server group, and servers numbered 90-81 into the second server group, etc. Users can also group servers according to their location within the server cluster. For example, servers located in the first region can be grouped into the first server group, and servers located in the second region can be grouped into the second server group, where the first and second regions are different. If multiple servers are located in the same region, they can be grouped according to their location, such as grouping servers that are close to each other. This application does not impose specific limitations on this. The servers in this embodiment can be general-purpose servers.
[0025] S200, determine any one server from the first server group as the first server; Specifically, the first server group may include multiple servers. Any one server in the first server group is selected as the first server and is used as the group head node.
[0026] S300, the first server preloads the Uniform Resource Locator (URL) of the cloud management platform and establishes a connection with the cloud management platform based on the URL; or, the first server preloads the URL and public key of the cloud management platform and establishes a connection with the cloud management platform based on the URL and public key. Specifically, the first server can preload the Uniform Resource Locator (URL) of the cloud management platform and establish a connection with the cloud management platform using a transport layer security certificate based on the URL. Alternatively, the first server can preload the URL and public key of the cloud management platform and establish a connection with the cloud management platform using a one-time cryptographic token based on the URL and public key.
[0027] S400, the first server provides at least one Uniform Resource Locator (URL) from the cloud management platform to the second server in the first server group to which it belongs; Specifically, the first server, acting as the group head node, can send an invitation to the second server within its group. The second server then requests the Uniform Resource Locator (URL) of the cloud management platform from the first server based on the invitation. The first server then provides the URL of the cloud management platform to the second server based on the request.
[0028] In the S500, the second server establishes a connection with the cloud management platform based on the Uniform Resource Locator (URL), and sends the public key of the second server to the cloud management platform through the first server.
[0029] Specifically, the second server, based on the Uniform Resource Locator obtained from the cloud management platform, can establish a connection with the cloud management platform through a transport layer security certificate or a one-time cryptographic token, and send the public key of the second server to the cloud management platform through the first server.
[0030] The multi-server processing method provided in this application involves grouping multiple servers according to a preset logic to obtain multiple server groups, each including at least a first server group. Then, any server from the first server group is designated as the first server. A Uniform Resource Locator (URI) of the cloud management platform is pre-loaded into the first server, and the first server establishes a connection with the cloud management platform based on the URI. Alternatively, the URI and public key of the cloud management platform are pre-loaded into the first server, and the first server establishes a connection with the cloud management platform based on the URI and public key. The first server provides at least the URI of the cloud management platform to the second server within its first server group. The second server establishes a connection with the cloud management platform based on the URI and sends its public key to the cloud management platform through the first server. In this way, the public keys of all servers within the first server group can be sent to the cloud management platform in this manner, and other server groups also send the public keys of all servers within their groups to the cloud management platform in the same way as the first server group, eliminating the need to manually pre-load the public keys of all servers into the cloud management platform one by one.
[0031] In some embodiments, a Uniform Resource Locator (URL) of a cloud management platform is preloaded in a first server, and the first server establishes a connection with the cloud management platform based on the URL, including: The first server preloads the Uniform Resource Locator (URL) of the cloud management platform. Based on the URL, the first server establishes a connection with the cloud management platform through transport layer security authentication.
[0032] Specifically, each server includes a BMC (Baseboard Management Controller), which is a dedicated controller used for monitoring and managing the server.
[0033] Users pre-install or load the Uniform Resource Locator (URL) of the cloud portal website into the BMC of the first server. Based on the URL, the BMC of the first server establishes a connection with the cloud management platform through transport layer security authentication.
[0034] In some embodiments, the first server establishes a connection with the cloud management platform based on a Uniform Resource Locator (URL) and via transport layer security authentication, including: The first server generates a first certificate signing request and sends it to the cloud management platform, which then issues a first sub-certificate with the cloud management platform's certificate as the root certificate based on the first certificate signing request, and loads the first sub-certificate onto the first server; the first certificate signing request contains the first server's public key; The first server uses the first sub-certificate to establish a two-way transport layer secure link with the cloud management platform.
[0035] Specifically, in combination Figure 2 As shown, the user sets up a BMC group (that is, grouping multiple servers), selects BMC1 (i.e., the BMC of the first server) as the group head node in the first server group, and pre-loads or loads the cloud portal URL for the first server.
[0036] From the first server group (such as...) Figure 2 In Group 1), any server is selected as the group head node. For example, BMC1 is selected as the group head node, and a cloud portal URL is pre-installed or loaded for the first server.
[0037] The user creates a new organization, BMC1, on the cloud portal website, corresponding to the first server group.
[0038] BMC1 generates the first certificate signing request and sends it to the cloud portal website. Then, the user issues the first sub-certificate with the cloud portal website certificate as the root certificate on the cloud portal website. The user loads the first sub-certificate into BMC1, and BMC1 uses the first sub-certificate to establish a bidirectional transport layer secure link with the cloud portal website.
[0039] The cloud portal calls BMC1's Application Programming Interface (API) to add BMC1 to the BMC1 organization on the cloud portal.
[0040] In some embodiments, the second server establishes a connection with the cloud management platform based on a Uniform Resource Locator (URL), including: The second server generates a second certificate signing request and sends it to the first server, enabling the first server to issue a second sub-certificate with the first server's certificate as the root certificate based on the second certificate signing request, and to load the second sub-certificate into the second server; the second certificate signing request contains the second server's public key; The second server requests the Uniform Resource Locator (URL) from the first server to obtain the cloud management platform. The second server establishes a two-way transport layer secure link with the cloud management platform based on the obtained Uniform Resource Locator and using the second sub-certificate.
[0041] Specifically, continue to combine Figure 2 As shown, BMCX generates a second certificate signing request and sends it to BMC1. Based on the second certificate signing request, BMC1 issues a second sub-certificate to BMCX with BMC1's certificate as the root certificate. Then, the second sub-certificate is loaded into BMCX. Here, BMCX represents the BMC of any second server, and X can be 11, 12, 13…, i.e., BMC11, BMC12, BMC13…, where BMC11 represents the BMC of the first second server, BMC12 represents the BMC of the second second server, BMC13 represents the BMC of the third second server, and so on.
[0042] BMCX requests a Uniform Resource Locator (URL) from BMC1 for the cloud portal website. Based on the obtained URL, BMCX establishes a two-way URL link with the cloud portal website using the second subcertificate.
[0043] The cloud portal calls the BMCX application programming interface to add BMCX to the BMC1 organization.
[0044] For example, the first server group (group 1) also includes BMC11, BMC12 and BMC13.
[0045] With a bidirectional transport layer secure link established between BMC1 and the cloud portal, BMC11 generates a second certificate signing request and sends it to BMC1. Based on this request, BMC1 issues a second sub-certificate to BMC11, with BMC1's certificate as the root certificate. This sub-certificate is then loaded into BMC11. BMC11 requests a Uniform Resource Locator (URL) from BMC1, and using the obtained URL and the second sub-certificate, establishes a bidirectional transport layer secure link with the cloud portal. The cloud portal then uses BMC11's application programming interface (API) to add BMC11 to its organization.
[0046] BMC12 generates a third-party certificate signing request and sends it to BMC11. Based on the request, BMC11 issues a third-party subcertificate to BMC12, with BMC11's certificate as the root certificate. This subcertificate is then loaded into BMC12. BMC12 requests a Uniform Resource Locator (URL) from BMC11 for the cloud portal website. Using the obtained URL and the third-party subcertificate, BMC12 establishes a bidirectional transport layer secure link with the cloud portal website. The cloud portal website then uses BMC12's application programming interface (API) to add BMC11 to its organization.
[0047] BMC13 generates a fourth certificate signing request and sends it to BMC12. Based on this request, BMC12 issues a fourth sub-certificate to BMC13, with BMC12's certificate as the root certificate. This sub-certificate is then loaded into BMC13. BMC13 requests a Uniform Resource Locator (URL) from BMC12 for the cloud portal website. Using this URL and the fourth sub-certificate, BMC13 establishes a bidirectional transport layer secure link with the cloud portal website. The cloud portal website then uses BMC13's application programming interface (API) to add BMC11 to BMC1's organization.
[0048] In this way, the first server (BMC1) and all the second servers (BMC11, BMC12, BMC13, etc.) in the first server group establish a two-way transport layer secure link with the cloud management platform through a transport layer security certificate chain.
[0049] In some embodiments, the second server sends its public key to the cloud management platform through the first server, including: When the second server establishes a two-way transport layer secure link with the cloud management platform using the second sub-certificate, the cloud management platform can extract the public key of the second server through the second sub-certificate, or the second server can send its public key to the cloud management platform based on the two-way transport layer secure link.
[0050] Specifically, when the second server establishes a two-way transport layer secure link with the cloud portal website, the cloud portal website can extract the public key of the second server through the second sub-certificate, or send the public key of the second server to the cloud management platform through the transport layer secure link, thereby uploading the public keys of all servers to the cloud management platform without having to manually preload the public keys of all servers to the cloud management platform one by one.
[0051] In some embodiments, a Uniform Resource Locator (URL) and public key of a cloud management platform are preloaded in a first server. The first server establishes a connection with the cloud management platform based on the URL and public key, including: The first server preloads the Uniform Resource Locator and public key of the cloud management platform, and establishes a connection with the cloud management platform through a one-time password token (HOTP token).
[0052] Specifically, each server includes a BMC, which is a dedicated controller used for monitoring and managing the server.
[0053] The first server preloads the Uniform Resource Locator (URL) and public key of the cloud portal website, and establishes a connection with the cloud portal website using a one-time password token.
[0054] In some embodiments, the first server establishes a connection with the cloud management platform via a one-time password token, including: The first server generates a first shared key based on its private key and the public key of the cloud management platform, and sends the first shared key to the cloud management platform. The cloud management platform preloads the public key of the first server. The cloud management platform generates a second shared key based on the private key of the cloud management platform and the public key of the first server, and verifies whether the first shared key and the second shared key are consistent. If they are consistent, the first server is allowed to establish a communication connection with the cloud management platform.
[0055] Specifically, in combination Figure 3 As shown, the user sets up a BMC group (that is, grouping multiple servers), selects BMC1 (i.e., the BMC of the first server) as the group head node in the first server group, and pre-installs or loads the Uniform Resource Locator (URL) and public key of the cloud portal website for the first server.
[0056] From the first server group (such as...) Figure 3 In Group 1), any server is selected as the group head node. For example, BMC1 (the BMC of the first server) is selected as the group head node, and the first server is pre-loaded or loaded with the Uniform Resource Locator of the cloud portal and the public key of the cloud portal. The public key of the first server is pre-loaded in the cloud portal.
[0057] The user creates a new organization, BMC1, on the cloud portal website, corresponding to the first server group.
[0058] BMC1 generates a first shared password using an asymmetric encryption algorithm based on the private key of the first server and the public key of the cloud portal website, and then sends the first shared password to the computing portal website.
[0059] The cloud portal website generates a second shared key using an asymmetric encryption algorithm based on its private key and BMC1's public key. It then verifies whether the first and second shared keys are consistent. If they are consistent, it allows BMC1 to establish a communication connection with the cloud portal website.
[0060] BMC1 establishes a connection with the cloud portal using a one-time password token.
[0061] The cloud portal calls BMC1's application programming interface to add BMC1 to the BMC1 organization.
[0062] In some embodiments, the second server establishes a connection with the cloud management platform based on a Uniform Resource Locator (URL), and sends the public key of the second server to the cloud management platform through the first server, including: The second server requests the Uniform Resource Locator and public key of the cloud management platform from the first server; The second server uploads its public key to the cloud management platform through the connection channel between the first server and the cloud management platform. The second server generates a third shared key based on its private key and the public key of the cloud management platform, and sends the third shared key to the cloud management platform through the connection channel between the first server and the cloud management platform. The cloud management platform generates a fourth shared key based on the private key of the cloud management platform and the public key of the second server, and verifies whether the third shared key and the fourth shared key are consistent. If they are consistent, the second server is allowed to establish a communication connection with the cloud management platform.
[0063] Specifically, continue to combine Figure 3 As shown, BMCX requests the Uniform Resource Locator (URL) and public key of the cloud portal from BMC1. BMCX then uploads its public key to the cloud portal through the connection channel between BMC1 and the cloud portal. Here, BMCX represents the BMC of any second server, and X can be 11, 12, 13…, i.e., BMC11, BMC12, BMC13… BMC11 represents the BMC of the first second server, BMC12 represents the BMC of the second second server, BMC13 represents the BMC of the third second server, and so on.
[0064] BMCX generates a third shared key using an asymmetric encryption algorithm based on the private key of the second server and the public key of the cloud portal website. The third shared key is then sent to the cloud portal website through the connection channel between the first server and the cloud management platform.
[0065] The cloud portal uses its private key and BMCX's public key to generate a fourth shared key via an asymmetric encryption algorithm. It then verifies the consistency between the third and fourth shared keys. If they match, BMCX is allowed to establish a communication connection with the cloud portal. BMCX establishes the connection with the cloud portal using a one-time cryptographic token.
[0066] The cloud portal calls the BMCX application programming interface to add BMCX to the BMC1 organization.
[0067] For example, the first server group (group 1) also includes BMC11, BMC12, and BMC13. Similarly, BMC11, BMC12, and BMC13 all establish a connection with the cloud portal website via a one-time password token in accordance with the BMCX described above, and complete the device registration process with the cloud portal website.
[0068] In this way, the first server (BMC1) and all the second servers (BMC11, BMC12, BMC13, etc.) in the first server group establish a connection with the cloud management platform through a one-time password token.
[0069] In some embodiments, the plurality of server groups further includes a second server group, and the method further includes: Choose any one server from the second server group as the third server; The first server provides the third server with at least a Uniform Resource Locator (URL) for the cloud management platform; The third server establishes a connection with the cloud management platform based on a Uniform Resource Locator (URL), and sends the third server's public key to the cloud management platform through the first server.
[0070] In some embodiments, the method further includes: The third server provides at least one Uniform Resource Locator (URL) from the cloud management platform to the fourth server within its second server group; The fourth server establishes a connection with the cloud management platform based on the Uniform Resource Locator (URL), and sends the public key of the fourth server to the cloud management platform through the third server.
[0071] For example, combined Figure 2 As shown, in the first server group ( Figure 2 After BMC1 of group 1 establishes a secure bidirectional link at the transport layer with the cloud portal, the second server group ( Figure 2 The group head node BMC21 of group 2) passes through the first server group ( Figure 2In the second server group (group 1), BMC1 issues a sub-certificate. Other servers in the second server group, such as BMC22, issue sub-certificates through the group head node BMC21, and BMC23 issues sub-certificates through BMC22. Thus, all servers in the second server group establish a connection with the cloud portal website using transport layer security certificates. Figure 2 The connection between the group head node BMC21 of group 2 and the cloud portal is established in the same way that the connection between BMCX and the cloud portal is established. Other servers in the second server group establish connections with the cloud portal through their respective group head nodes.
[0072] Optionally, multiple server groups may also include a third server group (such as...) Figure 2 The connection between the third server group (group 3) and the cloud portal website is established in the same way as that between the second server group and the cloud portal website, and will not be repeated here.
[0073] For example, combined Figure 3 As shown, in the first server group ( Figure 2 After BMC1 of group 1 establishes a connection with the cloud portal, the second server group ( Figure 2 In Group 2), the group head node BMC21 requests the Uniform Resource Locator (URL) and public key of the cloud portal from BMC1. It then uploads its public key to the cloud portal through the connection channel between BMC1 and the cloud portal. BMC21 and the cloud portal use their private and public keys to generate a one-time password token. BMC21 then establishes a connection with the cloud portal using this one-time password token. Thus, all servers in the second server group establish a connection with the cloud portal using this one-time password token. The second server group (…) Figure 2 The connection between the group head node BMC21 of group 2 and the cloud portal is established in the same way that the connection between BMCX and the cloud portal is established. Other servers in the second server group establish connections with the cloud portal through their respective group head nodes.
[0074] Optionally, multiple server groups may also include a third server group (such as...) Figure 2 The method by which the third server group (group 3) establishes a connection with the cloud portal is the same as the method by which the second server group establishes a connection with the cloud portal, and will not be repeated here.
[0075] The above embodiments are merely exemplary embodiments of this application and are not intended to limit this application. The scope of protection of this application is defined by the claims. Those skilled in the art can make various modifications or equivalent substitutions to this application within its substance and scope of protection, and such modifications or equivalent substitutions should also be considered to fall within the scope of protection of this application.
Claims
1. A multi-server processing method, comprising: Multiple servers are grouped according to a preset logic to obtain multiple server groups, and the multiple server groups include at least a first server group; Select any one server from the first server group as the first server; The first server preloads the Uniform Resource Locator (URL) of the cloud management platform and establishes a connection with the cloud management platform based on the URL; or, the first server preloads the URL and public key of the cloud management platform and establishes a connection with the cloud management platform based on the URL and public key. The first server provides at least one Uniform Resource Locator (URL) from the cloud management platform to the second server within the first server group to which it belongs; The second server establishes a connection with the cloud management platform based on the Uniform Resource Locator (URL), and sends the public key of the second server to the cloud management platform through the first server.
2. The method according to claim 1, wherein a Uniform Resource Locator (URL) of a cloud management platform is preloaded in the first server, and the first server establishes a connection with the cloud management platform based on the URL, comprising: The first server preloads the Uniform Resource Locator (URL) of the cloud management platform, and the first server establishes a connection with the cloud management platform based on the URL and through transport layer security authentication.
3. The method according to claim 2, wherein the first server establishes a connection with the cloud management platform based on the Uniform Resource Locator (URL) via transport layer security authentication, comprising: The first server generates a first certificate signing request and sends it to the cloud management platform, which then issues a first sub-certificate with the cloud management platform certificate as the root certificate based on the first certificate signing request, and loads the first sub-certificate onto the first server; the first certificate signing request contains the public key of the first server; The first server uses the first sub-certificate to establish a two-way transport layer secure link with the cloud management platform.
4. The method according to claim 2, wherein the second server establishes a connection with the cloud management platform based on the Uniform Resource Locator, comprising: The second server generates a second certificate signing request and sends it to the first server, causing the first server to issue a second sub-certificate with the first server's certificate as the root certificate based on the second certificate signing request, and load the second sub-certificate into the second server; the second certificate signing request contains the public key of the second server; The second server requests the Uniform Resource Locator (URL) of the cloud management platform from the first server; The second server establishes a bidirectional transport layer secure link with the cloud management platform based on the obtained Uniform Resource Locator and using the second sub-certificate.
5. The method according to claim 4, wherein the second server sends the public key of the second server to the cloud management platform through the first server, comprising: When the second server establishes a two-way transport layer secure link with the cloud management platform using the second sub-certificate, the cloud management platform extracts the public key of the second server through the second sub-certificate, or the second server sends its public key to the cloud management platform based on the two-way transport layer secure link.
6. The method according to claim 1, wherein a Uniform Resource Locator (URL) and a public key of a cloud management platform are preloaded in the first server, and the first server establishes a connection with the cloud management platform based on the URL and the public key, comprising: The first server preloads the Uniform Resource Locator (URL) and public key of the cloud management platform, and the first server establishes a connection with the cloud management platform through a one-time password token.
7. The method according to claim 6, wherein the first server establishes a connection with the cloud management platform via a one-time password token, comprising: The first server generates a first shared key based on its private key and the public key of the cloud management platform, and sends the first shared key to the cloud management platform; The cloud management platform preloads the public key of the first server. The cloud management platform generates a second shared key based on the private key of the cloud management platform and the public key of the first server, and verifies whether the first shared key and the second shared key are consistent. If they are consistent, the first server is allowed to establish a communication connection with the cloud management platform.
8. The method according to claim 6, wherein the second server establishes a connection with the cloud management platform based on the Uniform Resource Locator (URL), and sends the public key of the second server to the cloud management platform through the first server, comprising: The second server requests the Uniform Resource Locator and public key of the cloud management platform from the first server; The second server uploads its public key to the cloud management platform through the connection channel between the first server and the cloud management platform; The second server generates a third shared key based on its private key and the public key of the cloud management platform, and sends the third shared key to the cloud management platform through the connection channel between the first server and the cloud management platform. The cloud management platform generates a fourth shared key based on its private key and the public key of the second server, and verifies whether the third shared key and the fourth shared key are consistent. If they are consistent, the second server is allowed to establish a communication connection with the cloud management platform.
9. The method according to claim 1, wherein the plurality of server groups further comprises a second server group, and the method further comprises: Select any one server from the second server group as the third server; The first server provides the third server with at least a Uniform Resource Locator (URL) for the cloud management platform; The third server establishes a connection with the cloud management platform based on the Uniform Resource Locator (URL), and sends the public key of the third server to the cloud management platform through the first server.
10. The method according to claim 9, further comprising: The third server provides at least one Uniform Resource Locator (URL) for the cloud management platform to the fourth server in the second server group to which it belongs; The fourth server establishes a connection with the cloud management platform based on the Uniform Resource Locator (URL), and sends the public key of the fourth server to the cloud management platform through the third server.