A method, device, storage medium and electronic device for addressing test

Abstract

This specification discloses a method, apparatus, storage medium, and electronic device for addressing testing. In the addressing testing method provided in this specification, a virtual middleware is created according to the real address in the cloud architecture, and a channel from the virtual middleware to the user in the cloud architecture is established. Through the addressing middleware, based on the attribute information of the addressed user and the channel, the address of the addressed virtual middleware is determined as the test address. The standard address is determined according to the attribute information of the addressed user and the channel. The test result is obtained by comparing the test address with the standard address, thereby completing the test of the addressing middleware. It can be seen from the above method that this method simulates the channel between the middleware and the user in the cloud architecture by obtaining real nodes, accurately tests the addressing result of the addressing middleware, and this method is not limited to the actual application scenario and can be arbitrarily extended, which not only ensures accuracy but also saves costs and is conducive to privacy protection.

Description

Technical Field

[0001] This application relates to the field of computers, and particularly to a method, apparatus, storage medium, and electronic device for addressing testing. Background Art

[0002] With the continuous development of Internet technologies and the digital economy, the business forms of various industries have become open and Internet-based. To meet the elastic demand for resources by sudden services in the Internet business form, the distributed architecture has gradually evolved into an elastic hybrid cloud architecture, that is, the combination of the distributed architecture and cloud native.

[0003] In the cloud-native era, cloud operators provide many convenient and fast middleware while protecting user privacy to better serve users. Users can complete the invocation of middleware through a standardized Application Programming Interface (API), and thus obtain the services provided by the invoked middleware.

[0004] In addition to the middleware that provides services to users, there is also a special middleware whose function is to find the address of the middleware required by users. When users invoke middleware to serve them, it is very important for users whether the addressing middleware can accurately locate the address of the middleware to be invoked. That is, the addressing accuracy of the addressing middleware is crucial to the impact on all users. Therefore, how to test the addressing accuracy of the addressing middleware is an urgent problem to be solved. Summary of the Invention

[0005] This specification provides a method, apparatus, storage medium, and electronic device for addressing testing to at least partially solve the above problems existing in the prior art.

[0006] This specification adopts the following technical solutions:

[0007] This specification provides an addressing testing method, including:

[0008] Responding to a creation request for a virtual middleware, creating the virtual middleware;

[0009] Responding to the configuration request for the virtual middleware, selecting at least one actual address from the actual addresses of each node included in the cloud architecture as the address of the virtual middleware, and establishing a channel from the virtual middleware to a user in the cloud architecture according to the address of the virtual middleware;

[0010] When testing the addressing middleware, running a test case through the addressing middleware; the test case includes an addressing request for addressing the virtual middleware;

[0011] Through the addressing middleware, based on the attribute information of the user who sends the addressing request and the channel, determine the address of the virtual middleware obtained by addressing as the test address;

[0012] Compare the test address with the standard address to obtain the test result of the addressing middleware; the standard address is determined in advance according to the attribute information of the user and the channel.

[0013] Optionally, the channel includes a common channel;

[0014] Establishing a channel from the virtual middleware to the user in the cloud architecture specifically includes:

[0015] For each address of the virtual middleware, when establishing a common channel from this address of the virtual middleware to the user in the cloud architecture, configure this address as the address corresponding to the common channel, and configure the attribute information of the user who is allowed to access this address for the common channel;

[0016] The attribute information includes at least one of the logical computer room where the user is located, the physical computer room where the user is located, and the geographical area where the user is located.

[0017] Optionally, the channel includes a dedicated channel; the users in the cloud architecture include users of the logical control center LDC;

[0018] Establishing a channel from the virtual middleware to the user in the cloud architecture specifically includes:

[0019] For each address of the virtual middleware, when establishing a dedicated channel from this address of the virtual middleware to the LDC user in the cloud architecture, configure this address as the address corresponding to the dedicated channel, and determine the LDC user who needs to establish the dedicated channel as the LDC user who is allowed to access this address, and configure the attribute information of the LDC user who is allowed to access this address for the dedicated channel;

[0020] The attribute information includes at least one of the tenant to which the LDC user belongs, the logical computer room where the LDC user is located, the physical computer room where the LDC user is located, and the geographical area where the LDC user is located.

[0021] Optionally, the channel includes a dedicated channel; the users in the cloud architecture include non-logical control center LDC users;

[0022] Establishing a channel from the virtual middleware to the user in the cloud architecture specifically includes:

[0023] For each address of the virtual middleware, when establishing a dedicated channel from this address of the virtual middleware to a non-LDC user in the cloud architecture, configure this address as the address corresponding to the dedicated channel, and determine the non-LDC user who needs to establish the dedicated channel as the non-LDC user allowed to access this address, and configure the attribute information of the non-LDC users allowed to access this address for the dedicated channel;

[0024] The attribute information includes at least one of the tenant to which the non-LDC user belongs, the physical computer room where the non-LDC user is located, and the geographical area where the non-LDC user is located.

[0025] Optionally, through the addressing middleware, based on the attribute information of the user sending the addressing request and the channel, determine the address of the virtual middleware obtained by addressing, specifically including:

[0026] For each channel, through the addressing middleware, determine whether the configuration of this channel contains at least one piece of attribute information of the user sending the addressing request. If so, determine this channel as the channel that matches the attribute information of the user sending the addressing request; otherwise, determine this channel as not the channel that matches the attribute information of the user sending the addressing request;

[0027] Determine the address corresponding to the channel that matches the attribute information of the user sending the addressing request as the address of the virtual middleware obtained by addressing.

[0028] Optionally, after establishing a channel from the virtual middleware to a user in the cloud architecture, the method further includes:

[0029] Determine the environment screening conditions corresponding to the established channel;

[0030] Before determining that this channel is the channel that matches the attribute information of the user sending the addressing request, the method further includes:

[0031] Determine that the environment where the user sending the addressing request is located meets the environment screening conditions corresponding to this channel.

[0032] Optionally, the address of the virtual middleware includes more than two actual addresses;

[0033] Compare the test address with the standard address to obtain the test result of the addressing middleware, specifically including:

[0034] Determine whether the test address obtained by addressing and the standard address correspond one by one;

[0035] If so, determine that the addressing result of the addressing middleware is accurate,

[0036] Otherwise, it is determined that the addressing result of the addressing middleware is inaccurate.

[0037] This specification provides an addressing test device, including:

[0038] A creation module, configured to create a virtual middleware in response to a creation request of the virtual middleware received;

[0039] A configuration module, configured to, in response to a configuration request of the virtual middleware, select at least one actual address from the actual addresses of each node included in the cloud architecture as the address of the virtual middleware, and establish a channel from the virtual middleware to a user in the cloud architecture according to the address of the virtual middleware;

[0040] An operation module, configured to, when testing the addressing middleware, run a test case through the addressing middleware; the test case includes an addressing request for addressing the virtual middleware;

[0041] An addressing module, configured to, through the addressing middleware, determine the address of the virtual middleware obtained by addressing as a test address based on the attribute information of the user sending the addressing request and the channel;

[0042] A comparison module, configured to compare the test address with a standard address to obtain a test result of the addressing middleware; the standard address is determined in advance according to the attribute information of the user sending the addressing request and the channel.

[0043] Optionally, the channel includes a common channel;

[0044] Specifically, for each address of the virtual middleware, when establishing a common channel from the address of the virtual middleware to a user in the cloud architecture, the configuration module configures the address as the address corresponding to the common channel, and configures the attribute information of the users allowed to access the address for the common channel; the attribute information includes at least one of the logical computer room where the user is located, the physical computer room where the user is located, and the geographical area where the user is located.

[0045] Optionally, the channel includes a dedicated channel; the users in the cloud architecture include users of a logical control center LDC;

[0046] Specifically, for each address of the virtual middleware, when establishing a dedicated channel from this address of the virtual middleware to an LDC user in the cloud architecture, the configuration module configures this address as the address corresponding to the dedicated channel, determines the LDC user who needs to establish the dedicated channel as the LDC user allowed to access this address, and configures the attribute information of the LDC user allowed to access this address for the dedicated channel; the attribute information includes at least one of the tenant to which the LDC user belongs, the logical computer room where the LDC user is located, the physical computer room where the LDC user is located, and the geographical region where the LDC user is located.

[0047] Optionally, the channel includes a dedicated channel; the users in the cloud architecture include non-logical control center LDC users;

[0048] Specifically, for each address of the virtual middleware, when establishing a dedicated channel from this address of the virtual middleware to a non-LDC user in the cloud architecture, the configuration module configures this address as the address corresponding to the dedicated channel, determines the non-LDC user who needs to establish the dedicated channel as the non-LDC user allowed to access this address, and configures the attribute information of the non-LDC user allowed to access this address for the dedicated channel; the attribute information includes at least one of the tenant to which the non-LDC user belongs, the physical computer room where the non-LDC user is located, and the geographical region where the non-LDC user is located.

[0049] Optionally, specifically for each channel, the addressing module determines, through the addressing middleware, whether the configuration of the channel contains at least one piece of attribute information of the user sending the addressing request. If so, it determines that this channel is a channel matching the attribute information of the user sending the addressing request; otherwise, it determines that this channel is not a channel matching the attribute information of the user sending the addressing request; and determines the address corresponding to the channel matching the attribute information of the user sending the addressing request as the addressed address of the virtual middleware.

[0050] Optionally, the configuration module is further configured to determine the environment screening conditions corresponding to the established channel after establishing the channel from the virtual middleware to the user in the cloud architecture;

[0051] The addressing module is further configured to determine that the environment where the user sending the addressing request is located meets the environment screening conditions corresponding to this channel before determining that this channel is a channel matching the attribute information of the user sending the addressing request.

[0052] Optionally, the address of the virtual middleware includes more than two actual addresses;

[0053] The comparison module is specifically configured to determine whether the test address obtained by addressing corresponds one-to-one with the standard address; if so, it is determined that the addressing result of the addressing middleware is accurate, and if not, it is determined that the addressing result of the addressing middleware is inaccurate.

[0054] This specification provides a computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, the above-mentioned addressing test method is implemented.

[0055] This specification provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the above-mentioned addressing test method is implemented.

[0056] At least one of the above technical solutions adopted in this specification can achieve the following beneficial effects:

[0057] In the addressing test method provided in this specification, a virtual middleware is created according to the real address in the cloud architecture, a channel from the virtual middleware to the user in the cloud architecture is established according to the address of the virtual middleware, and through the addressing middleware, based on the attribute information of the user sending the addressing request and the channel, the address of the virtual middleware obtained by addressing is determined as the test address, the standard address is determined according to the attribute information of the user sending the addressing request and the channel, the test address is compared with the standard address, and the test result of the addressing middleware is obtained, thereby completing the test of the addressing middleware.

[0058] It can be seen from the above method that this method simulates the channel between the middleware and the user in the cloud architecture by obtaining real nodes, accurately tests the addressing result of the addressing middleware, and this method is not limited to the actual application scenario and can be arbitrarily extended, that is, it ensures accuracy and saves costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] The drawings described herein are used to provide a further understanding of this specification, and constitute a part of this specification. The illustrative embodiments of this specification and their descriptions are used to explain this specification and do not constitute an improper limitation of this specification. In the drawings:

[0060] Figure 1 is a schematic flow chart of an addressing test method in this specification;

[0061] Figure 2 is a schematic diagram of allocating an actual address to a virtual middleware provided in this specification;

[0062] Figure 3 is a schematic diagram of a configured virtual middleware provided in this specification;

[0063] Figure 4 A schematic diagram of establishing a channel provided in this specification;

[0064] Figure 5 A schematic diagram of an addressing test device provided in this specification;

[0065] Figure 6 Corresponding to what is provided in this specification Figure 1 Schematic diagram of the electronic device. Specific embodiments

[0066] To make the objectives, technical solutions and advantages of this specification clearer, the technical solutions of this specification will be clearly and completely described below in conjunction with specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, rather than all the embodiments. Based on the embodiments in this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the scope of protection of this application.

[0067] The following will detail the technical solutions provided by each embodiment of this specification in conjunction with the drawings.

[0068] Figure 1 A flowchart of an addressing test method provided in this specification, specifically including the following steps:

[0069] S100: Create a virtual middleware in response to a received creation request for the virtual middleware.

[0070] In order not to affect the normal operation of the actual middleware to provide services to users, a virtual middleware can be created first before the addressing test. The so-called middleware is an independent system software or service program that connects two independent application programs or independent system softwares, and is used to manage computer resources and network communications. Distributed application softwares share resources between different technologies with the help of this software. The virtual middleware created in the embodiments of this specification is a middleware created based on real nodes in the cloud architecture, and does not actually provide services to users, but has an actual address and is used to test the addressing accuracy of the addressing middleware.

[0071] Specifically, a creation request for creating a virtual middleware can be sent to the central control area in the cloud architecture, and the central control area creates a virtual middleware in response to the creation request for the virtual middleware to simulate the actual middleware for addressing test.

[0072] In addition, before the test, data that has nothing to do with this test and does not affect the operation of the actual middleware can be cleared first. These irrelevant data may be generated by previous tests. Clearing irrelevant data before the test can avoid the influence of irrelevant data on the test results, thereby resulting in inaccurate test results.

[0073] S102: In response to a configuration request of the virtual middleware, select at least one actual address from the actual addresses of each node included in the cloud architecture as the address of the virtual middleware, and establish a channel from the virtual middleware to a user in the cloud architecture according to the address of the virtual middleware.

[0074] After creating the virtual middleware in the central control area through step S100, although the virtual middleware does not actually provide services to users, it must have an address, otherwise it cannot be used for addressing tests. Therefore, after creating the virtual middleware in the central control area, the address of the virtual middleware also needs to be configured.

[0075] To ensure the authenticity of the test, the address assigned by the central control area to the virtual middleware is selected from the actual addresses of each node included in the cloud architecture, and at least one actual address is selected as the address of the virtual middleware. The address can be an Internet Protocol (IP) address. After a user obtains the IP address of a middleware, the user can access the middleware through the IP address of the middleware to obtain services. As Figure 2 shown, multiple virtual middleware including virtual middleware 1 to 3 are created. For virtual middleware 1, 4 actual addresses can be selected and configured as the address of the virtual middleware 1. These 4 actual addresses are respectively IP1 and IP2 of the nodes in physical computer room 1 in region 1, and IP3 and IP4 of the nodes in physical computer room 2 in region 2.

[0076] After the virtual middleware has an address, it is also necessary to simulate the addressing logic of the addressing middleware to establish a channel between the virtual middleware and the user before it can be used for addressing tests. Therefore, after assigning the actual address to the virtual middleware, the central control area also needs to establish a channel from the virtual middleware to a user in the cloud architecture. The established channels are as Figure 3 shown. The central control area has established channels 1, 2, and 3 from virtual middleware 1 to user A in the cloud architecture, and the central control area has established channels 4, 5, and 6 from virtual middleware 1 to user B in the cloud architecture. The channel is the corresponding relationship between the middleware and the user. Establishing a channel means establishing the corresponding relationship between the address of the middleware and the attribute information of the eligible user. As Figure 3As shown in the figure, Channel 1 is the correspondence between the address IP1 of Virtual Middleware 1 and the attribute information 1 of User A. Channel 2 is the correspondence between the address IP1 of Virtual Middleware 1 and the attribute information 2 of User B. Channel 3 is the correspondence between the address IP2 of Virtual Middleware 1 and the attribute information 1 of User A. Channel 4 is the correspondence between the address IP3 of Virtual Middleware 1 and the attribute information 2 of User B. Channel 5 is the correspondence between the address IP4 of Virtual Middleware 1 and the attribute information 2 of User B. Channel 6 is the correspondence between the address IP4 of Virtual Middleware 1 and the attribute information 1 of User A. Through the correspondence between the address of the middleware and the attribute information of eligible users, when addressing the middleware, the address of the middleware corresponding to the attribute information can be obtained through the user's own attribute information, so as to achieve the purpose of addressing.

[0077] S104: When testing the addressing middleware, run the test case through the addressing middleware; the test case contains an addressing request for addressing the virtual middleware.

[0078] After creating the virtual middleware and configuring the address and channels of the virtual middleware in advance through the above S100 and S102, the addressing middleware can be tested based on the configured virtual middleware.

[0079] Specifically, before testing the addressing middleware, a test case can be created first. The test case at least contains an addressing request for the user to address the virtual middleware. In addition, it can also include the user identifier of the user sending the addressing request, or the attribute information of the user sending the addressing request.

[0080] During the testing process, the Central Control Area can run the test case through the addressing middleware, and the addressing middleware can obtain the address of the virtual middleware through the following step S106.

[0081] S106: Through the addressing middleware, based on the attribute information of the user sending the addressing request and the channel, determine the address of the addressed virtual middleware as the test address.

[0082] When the created test case contains the addressing request sent by the user and the attribute information of the user sending the addressing request, after the addressing middleware runs the test case, the attribute information of the user can be obtained. Therefore, the addressing middleware can query the IP address of the virtual middleware corresponding to the attribute information of the user according to the channel configured for the virtual middleware in step S102 (that is, the correspondence between the address of the middleware and the attribute information of eligible users), and use the obtained IP address of the virtual middleware as the test address.

[0083] When the created test case contains the addressing request sent by the user and the user identification of the user who sends the addressing request, after the addressing middleware runs the test case, it can, according to the user identification of the user, find the attribute information of the user. After finding the attribute information of the user, the addressing middleware can, according to the channel configured for the virtual middleware in step S102, query the IP address of the virtual middleware corresponding to the attribute information of the user, and use the obtained IP address of the virtual middleware as the test address.

[0084] S108: Compare the test address with the standard address to obtain the test result of the addressing middleware; the standard address is determined in advance according to the attribute information of the user who sends the addressing request and the channel.

[0085] In the embodiment of the present specification, after configuring the IP address and the channel of the virtual middleware through the above step 102, the address of the virtual middleware corresponding to the attribute information of the user in the test case can be manually determined, and this address is the standard address. Then, after the addressing middleware obtains the test address in step S106, it can directly compare the obtained test address with the standard address. If the two are the same, it indicates that the addressing result of the addressing middleware is accurate; otherwise, it indicates that the addressing result of the addressing middleware is inaccurate.

[0086] If the address of the virtual middleware includes more than two actual addresses, it can be determined whether the test address obtained by addressing corresponds one by one to the standard address. If so, it is determined that the addressing result of the addressing middleware is accurate; if not, it is determined that the addressing result of the addressing middleware is inaccurate.

[0087] For example, as Figure 3 shown, user A needs to find the address of virtual middleware 1. The actual node IP addresses of virtual middleware 1 are IP1, IP2, IP3, and IP4. According to the pre-configured channel, it can be determined that the standard address is IP1, IP2, and IP4. Then, if the address found by the addressing middleware according to the attribute information of user A and the channel between user A and virtual middleware 1 is IP1, IP2, and IP4, it indicates that the test result is accurate; otherwise, assuming that the result found by the addressing middleware is only one or two of IP1, IP2, and IP4, or even no address is found, or the obtained test result includes IP4, it all indicates that the addressing result of the addressing middleware is inaccurate.

[0088] Optionally, after the test is completed, the test data used to test the above-mentioned addressing middleware can also be cleared to prevent impacts on other operations. For example, the virtual middleware created in the central control area in steps S100 and S102, as well as the addresses and channels configured for the virtual middleware, can be cleared. The test cases created in step S104 can also be cleared, and the test addresses and standard addresses determined in steps S106 and S108 can also be cleared.

[0089] As can be seen from the above method, this method simulates the channel between the middleware and the user in the cloud architecture by obtaining real nodes, accurately tests the addressing results of the addressing middleware, and this method is not limited to the actual application scenario and can be arbitrarily extended. Because the middleware used for testing in this method is a temporarily created virtual middleware, any number of virtual middleware can be created according to the test needs, any type of virtual middleware can be created, and the addresses and channels of these virtual middleware can be arbitrarily configured. These virtual middleware and their addresses and channels neither affect the operation of the actual middleware nor can the test be carried out smoothly, which not only ensures the test accuracy but also saves costs.

[0090] In the above step S102, the central control area configures the created virtual middleware, assigns actual addresses to the virtual middleware, and establishes a channel from the virtual middleware to the user in the cloud architecture (that is, the correspondence between the address of the middleware and the attribute information of the eligible user). In practical applications, if the types of the established channels are all the same, the addressing middleware can complete the basic addressing function, but correspondingly, the addressing efficiency of the addressing middleware is relatively low.

[0091] In practical applications, since cloud service providers provide services for many different tenants, different tenants need to be distinguished. Distinguishing different tenants is called tenant isolation. Tenant isolation means that the behavior of one tenant operating cloud computing resources cannot be perceived by other tenants. According to different tenant isolation conditions, users can be divided into Logic Data Center (LDC) tenants and non-Logic Data Center (LDC) tenants. The difference between the two is that non-LDC tenants take the physical computer room of the user as a necessary condition for tenant isolation, while LDC tenants can isolate tenants based on the logical computer room of the user. A physical computer room is an actual existing computer room that houses many hosts, and the cloud service provider provides its cloud resources to users. The logical computer room is essentially a logical split of the physical computer room, imagining one or more larger physical computer rooms as more smaller computer rooms, and realizing the logical split of the physical computer room through regional grouping.

[0092] For users of the above different tenant types, if the channels established between the virtual middleware and the users are the same, there may be a situation where users of different tenant types queue up to access the same channel, and the addressing efficiency of the addressing middleware is relatively low. If the channels are classified, when different types of users address through the addressing middleware, they can obtain addresses by accessing different channels, which can improve the addressing efficiency of the addressing middleware. Optionally, to improve the addressing efficiency of the addressing middleware, the established channels can be divided into two types: common channels and dedicated channels.

[0093] Name the channel directly established by the central control area for the virtual middleware as the common channel, and name the channel from the virtual middleware to the user created by the central control area in response to the user's channel establishment request as the dedicated channel. The establishment process is specifically as follows.

[0094] The process of establishing the common channel from the virtual middleware to the users in the cloud architecture specifically includes:

[0095] For each address of the virtual middleware, when establishing the common channel from this address of the virtual middleware to the users in the cloud architecture, configure this address as the address corresponding to the common channel, and configure the attribute information of the users allowed to access this address for the common channel; the attribute information includes at least one of the logical computer room where the user is located, the physical computer room where the user is located, and the geographical area where the user is located.

[0096] The dedicated channels are divided into dedicated channels for LDC tenants and dedicated channels for non-LDC tenants according to different tenant types of the users.

[0097] The process of establishing the dedicated channel for LDC tenants specifically includes:

[0098] For each address of the virtual middleware, when establishing the dedicated channel from this address of the virtual middleware to the LDC tenants in the cloud architecture, configure this address as the address corresponding to the dedicated channel, and determine the LDC tenant that needs to establish the dedicated channel as the LDC tenant allowed to access this address, and configure the attribute information of the LDC tenant allowed to access this address for the dedicated channel; the attribute information includes at least one of the tenant to which the LDC tenant belongs, the logical computer room where the LDC tenant is located, the physical computer room where the LDC tenant is located, and the geographical area where the LDC tenant is located.

[0099] The process of establishing the dedicated channel for non-LDC tenants specifically includes:

[0100] For each address of the virtual middleware, when establishing a dedicated channel from this address of the virtual middleware to a non-LDC tenant in the cloud architecture, configure this address as the address corresponding to the dedicated channel, and determine the non-LDC tenant that needs to establish the dedicated channel as the non-LDC tenant allowed to access this address, and configure the attribute information of the non-LDC tenant allowed to access this address for the dedicated channel; the attribute information includes at least one of the tenant to which the non-LDC tenant belongs, the physical computer room where the non-LDC tenant is located, and the geographical area where the non-LDC tenant is located.

[0101] Specifically, as Figure 4 shown, as described in steps S100 and S102, the central control area creates virtual middleware 1 and assigns IP addresses (IP1 to IP4) to virtual middleware 1. Tenant 1 is an LDC tenant, and tenant 2 is a non-LDC tenant. The following configurations are made for IP1 to IP4:

[0102] Channel 1: Configure channel 1 between virtual middleware 1 and the user whose affiliated tenant is tenant 1 as a dedicated channel for the LDC tenant, and configure one of the logical computer rooms (i.e., area 4-1), physical computer room 4, region 1, and tenant 1 of tenant 1 as the attribute information of the user allowed to access IP1 for channel 1;

[0103] Channel 2: Configure channel 2 between virtual middleware 1 and the user whose affiliated tenant is tenant 2 as a dedicated channel for the non-LDC tenant, and configure one of the physical computer rooms (physical computer room 4), region 3, and tenant 2 of tenant 2 as the attribute information of the user allowed to access IP1 for channel 2;

[0104] Channel 3: Configure channel 3 between virtual middleware 1 and the user whose affiliated tenant is tenant 1 as a shared channel, configure IP2 as the address corresponding to channel 3, and configure the attribute information of the user allowed to access this address for channel 3 as physical computer room 1, tenant 1 or tenant 2, region 1;

[0105] Channel 4: Configure channel 4 between virtual middleware 1 and the user whose affiliated tenant is tenant 2 as a shared channel, configure IP3 as the address corresponding to channel 4, and configure the attribute information of the user allowed to access this address for channel 4 as physical computer room 1, tenant 1 or tenant 2, region 1;

[0106] Channel 5: Configure channel 5 between virtual middleware 1 and the user whose affiliated tenant is tenant 2 as a dedicated channel for the non-LDC tenant, and configure one of the physical computer rooms (physical computer room 4), region 3, and tenant 2 of tenant 2 as the attribute information of the user allowed to access IP4 for channel 5;

[0107] Channel 6: Configure Channel 6 between the virtual middleware 1 and the users belonging to Tenant 1 as a dedicated channel for the LDC tenant. Configure one of the logical computer rooms (Area 4-4) of Tenant 1, Physical Computer Room 4, Region 1, and Tenant 1 as the attribute information of the users allowed to access IP4 through Channel 6.

[0108] For the channels in the above example, the corresponding addressing logic is as follows: For each channel, through the addressing middleware, determine whether the configuration of the channel contains at least one piece of attribute information of the user sending the addressing request. If so, determine that the channel matches the attribute information of the user sending the addressing request; otherwise, determine that the channel does not match the attribute information of the user sending the addressing request. Determine the address corresponding to the channel that matches the attribute information of the user sending the addressing request as the address of the virtual middleware obtained by addressing.

[0109] It should be noted that the shared channel is a channel directly created by the cloud provider for the virtual middleware. That is, the cloud provider directly configures the attribute information of the users allowed to access the address of the virtual middleware for the shared channel. If a user wants to access the shared channel to obtain the address of the virtual middleware corresponding to the shared channel, determine whether the configuration of the shared channel given by the cloud provider contains at least one piece of attribute information of the user sending the addressing request. If so, the user can access the shared channel to obtain the address of the virtual middleware; otherwise, the user cannot access the shared channel to obtain the address of the virtual middleware. The dedicated channel is a channel that the user needs to create between the user and the virtual middleware, and then the cloud provider establishes the channel between the user and the virtual middleware. The cloud provider configures the attribute information of the user who needs to create the channel as the attribute information of the users allowed to access the address of the virtual middleware for the dedicated channel. If other users want to access the dedicated channel to obtain the address of the virtual middleware corresponding to the dedicated channel, determine whether the configuration of the shared channel contains at least one piece of attribute information of the user sending the addressing request, that is, whether the attribute information of the user who created the dedicated channel contains at least one piece of attribute information of the user sending the addressing request. If so, the user can access the shared channel to obtain the address of the virtual middleware; otherwise, the user cannot access the shared channel to obtain the address of the virtual middleware.

[0110] Continuing with the above example, specifically, as Figure 4 shown, the tenant to which User A belongs is Tenant 1, the tenant to which User B belongs is Tenant 2, the attribute information of User A is Area 1-1 (i.e., the logical computer room to which B belongs), Physical Computer Room 1, Region 1, and Tenant 1, and the attribute information of User B is Physical Computer Room 7, Region 1, and Tenant 2.

[0111] For each user, the specific addressing is as follows:

[0112] User A: Sends a request to the addressing virtualization middleware 1.

[0113] For Channel 1, through the addressing middleware, it is determined that the type of Channel 1 is a dedicated channel. It is determined that the logical computer room (Region 1-1) in the attribute information of User A is different from the attribute information of the user allowed to access IP1 of Channel 1. It is further determined that the physical computer room 1 in the attribute information of User A is different from the attribute information of the user allowed to access IP1 of Channel 1. It is further determined that the region 1 in the attribute information of User A is the same as the attribute information of the user allowed to access IP1 of Channel 1. Therefore, IP1 is returned to User A;

[0114] For Channel 3, through the addressing middleware, it is determined that the type of Channel 3 is a shared channel. It is determined that the physical computer room 1 in the attribute information of User A is the same as the attribute information of the user allowed to access IP2 of Channel 3. Therefore, IP2 is returned to User A;

[0115] For Channel 6, through the addressing middleware, it is determined that the type of Channel 6 is a dedicated channel. It is determined that the logical computer room (Region 1-1) in the attribute information of User A is different from the attribute information of the user allowed to access IP4 of Channel 6. Then it is further determined that the physical computer room 1 in the attribute information of User A is different from the attribute information of the user allowed to access IP4 of Channel 6. It is further determined that the region 1 in the attribute information of User A is the same as the attribute information of the user allowed to access IP4 of Channel 6. Therefore, IP4 is returned to User A.

[0116] User B: Sends a request to the addressing virtualization middleware 1.

[0117] For Channel 2, through the addressing middleware, it is determined that the type of Channel 2 is a shared channel. It is determined that the physical computer room 7 in the attribute information of User B is different from the attribute information of the user allowed to access IP1 of Channel 2. It is further determined that the region 1 in the attribute information of User B is different from the attribute information of the user allowed to access IP1 of Channel 2. It is further determined that the tenant 2 in the attribute information of User B is the same as the attribute information of the user allowed to access IP1 of Channel 2. Therefore, IP1 is returned to User B;

[0118] For Channel 4, through the addressing middleware, it is determined that the type of Channel 4 is a shared channel. It is determined that the physical computer room 7 in the attribute information of User B is different from the attribute information of the user allowed to access IP3 of Channel 4. It is further determined that the region 1 in the attribute information of User B is the same as the attribute information of the user allowed to access IP3 of Channel 4. Therefore, IP3 is returned to User B;

[0119] For Channel 5, through the addressing middleware, it is determined that the type of Channel 5 is a dedicated channel. It is judged that the attribute information of Physical Machine Room 7 in the attribute information of User B is different from the attribute information of the user who is allowed to access IP4 through Channel 5. It continues to judge that Region 1 in the attribute information of User B is different from the attribute information of the user who is allowed to access IP4 through Channel 5. It continues to judge that Tenant 2 in the attribute information of User B is the same as the attribute information of the user who is allowed to access IP4 through Channel 5. Therefore, IP4 is returned to User B.

[0120] Optionally, after establishing the channel from the virtual middleware to the user in the cloud architecture, the method further includes determining the environment screening conditions corresponding to the established channel. Before determining that the channel is a channel that matches the attribute information of the user who sends the addressing request, the method further includes: determining that the environment where the user who sends the addressing request is located meets the environment screening conditions corresponding to the channel.

[0121] The environment refers to the differences in the production links among different users belonging to the same tenant. For example, User C, User D, User E, and User F all belong to the same tenant, but the production link where User C is located is development, the production links where User D and User F are located are testing, and the production link where User E is located is operation and maintenance. Then User D and User F belong to the same environment, User C and other users (User D - F) do not belong to the same environment, and User E and other users (User C, D, and F) do not belong to the same environment. Correspondingly, if the environment corresponding to a channel is testing, then User D and User F belong to the same environment as the channel, while User C and User E belong to different environments from the channel.

[0122] The environment screening condition means that only when the user who sends the addressing request and the channel accessed by the addressing are in the same environment can it be determined that the channel matches the attribute information of the user who sends the addressing request; if the user who sends the addressing request and the channel accessed by the addressing are in different environments, then it cannot be determined that the channel matches the attribute information of the user who sends the addressing request.

[0123] Optionally, after creating the virtual middleware and configuring the virtual middleware as described in the above steps S100 to 102, a test case is created based on the configuration in the above step S104. The central control area can run the test case through the addressing middleware. The addressing middleware can obtain the address of the virtual middleware through step S106. Before performing step S106, it can be determined whether the environment where the user sending the addressing request is located meets the environment screening conditions corresponding to the channel. If it meets, step S106 is continued. If it does not meet, it is determined that the channel does not match the attribute information of the user sending the addressing request. It can also be after performing step S106. If at least one attribute information of the user sending the addressing request is included in the configuration of the channel, it is continued to determine whether the environment where the user sending the addressing request is located meets the environment screening conditions corresponding to the channel. If it meets, it is determined that the channel matches the attribute information of the user sending the addressing request. If it does not meet, it is determined that the channel does not match the attribute information of the user sending the addressing request.

[0124] After determining the channel that matches the attribute information of the above users A to C, the address of the middleware can be determined as the test address, and finally the test can be completed by comparing the test address with the standard address.

[0125] The above is the addressing test method provided by one or more embodiments of this specification. Based on the same idea, this specification also provides a corresponding addressing test device, as Figure 4 shown.

[0126] Figure 5 It is a schematic diagram of an addressing test device provided by this specification, specifically including:

[0127] A creation module 501, configured to create a virtual middleware in response to a received creation request for the virtual middleware;

[0128] A configuration module 502, configured to, in response to the configuration request for the virtual middleware, select at least one actual address from the actual addresses of each node included in the cloud architecture as the address of the virtual middleware, and establish a channel from the virtual middleware to the users in the cloud architecture according to the address of the virtual middleware;

[0129] An operation module 503, configured to run a test case through the addressing middleware when testing the addressing middleware; the test case includes an addressing request for addressing the virtual middleware;

[0130] An addressing module 504, configured to determine, through the addressing middleware, the address of the addressed virtual middleware as the test address based on the attribute information of the user sending the addressing request and the channel;

[0131] A comparison module 505 is configured to compare the test address with a standard address to obtain a test result of the addressing middleware; the standard address is pre-determined according to the attribute information of the user who sends the addressing request and the channel.

[0132] Optionally, the channel includes a common channel;

[0133] Specifically, for each address of the virtual middleware, when establishing a common channel from the address of the virtual middleware to a user in the cloud architecture, the configuration module 502 configures the address as the address corresponding to the common channel, and configures the attribute information of the users allowed to access the address for the common channel; the attribute information includes at least one of the logical computer room where the user is located, the physical computer room where the user is located, and the geographical area where the user is located.

[0134] Optionally, the channel includes a dedicated channel; the users in the cloud architecture include Logical Control Center (LDC) users;

[0135] Specifically, for each address of the virtual middleware, when establishing a dedicated channel from the address of the virtual middleware to an LDC user in the cloud architecture, the configuration module 502 configures the address as the address corresponding to the dedicated channel, determines the LDC users who need to establish the dedicated channel as the LDC users allowed to access the address, and configures the attribute information of the LDC users allowed to access the address for the dedicated channel; the attribute information includes at least one of the tenant to which the LDC user belongs, the logical computer room where the LDC user is located, the physical computer room where the LDC user is located, and the geographical area where the LDC user is located.

[0136] Optionally, the channel includes a dedicated channel; the users in the cloud architecture include non-Logical Control Center (LDC) users;

[0137] Specifically, for each address of the virtual middleware, when establishing a dedicated channel from the address of the virtual middleware to a non-LDC user in the cloud architecture, the configuration module 502 configures the address as the address corresponding to the dedicated channel, determines the non-LDC users who need to establish the dedicated channel as the non-LDC users allowed to access the address, and configures the attribute information of the non-LDC users allowed to access the address for the dedicated channel; the attribute information includes at least one of the tenant to which the non-LDC user belongs, the physical computer room where the non-LDC user is located, and the geographical area where the non-LDC user is located.

[0138] Optionally, the addressing module 504 is specifically configured to, for each channel, determine, through the addressing middleware, whether the configuration of the channel contains at least one piece of attribute information of the user who sends the addressing request. If so, determine that the channel is a channel that matches the attribute information of the user who sends the addressing request; otherwise, determine that the channel is not a channel that matches the attribute information of the user who sends the addressing request; and determine the address corresponding to the channel that matches the attribute information of the user who sends the addressing request as the addressed address of the virtual middleware.

[0139] Optionally, the configuration module 502 is further configured to, after establishing a channel from the virtual middleware to a user in the cloud architecture, determine an environment screening condition corresponding to the established channel;

[0140] The addressing module 504 is further configured to, before determining that the channel is a channel that matches the attribute information of the user who sends the addressing request, determine that the environment where the user who sends the addressing request is located meets the environment screening condition corresponding to the channel.

[0141] Optionally, the address of the virtual middleware includes more than two actual addresses;

[0142] The comparison module 505 is specifically configured to determine whether the addressed test address and the standard address correspond one by one; if so, determine that the addressing result of the addressing middleware is accurate; if not, determine that the addressing result of the addressing middleware is inaccurate.

[0143] This specification also provides a computer-readable storage medium storing a computer program, which can be used to execute the above Figure 1 provided addressing test method.

[0144] This specification also provides Figure 6 a schematic structural diagram of the electronic device shown. As Figure 6 described, at the hardware level, the driverless device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory. Of course, it may also include other hardware required for other services. The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it to implement the above Figure 1 described addressing test method. Of course, in addition to the software implementation manner, this specification does not exclude other implementation manners, such as logical devices or a combination of software and hardware. That is to say, the execution subject of the following processing flow is not limited to each logical unit, and may also be hardware or a logical device.

[0145] In the 1990s, it was quite obvious to distinguish whether an improvement to a technology was an improvement in hardware (e.g., improvement to circuit structures such as diodes, transistors, switches, etc.) or an improvement in software (improvement to method flows). However, with the development of technology, many improvements to method flows today can be regarded as direct improvements to hardware circuit structures. Almost all designers obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement to a method flow cannot be implemented with a hardware entity module. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program by themselves to "integrate" a digital system on a single PLD, without having to ask a chip manufacturer to design and fabricate a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used in programming and writing. The original code before compilation also has to be written in a specific programming language, which is called a Hardware Description Language (HDL), and there is not only one kind of HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones currently are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also be aware that only by slightly logically programming the method flow with the above-mentioned several hardware description languages and programming it into the integrated circuit can the hardware circuit implementing the logic method flow be easily obtained.

[0146] The controller can be implemented in any suitable manner. For example, the controller can take the form of, for example, a microprocessor or a processor, and a computer-readable medium storing computer-readable program code (such as software or firmware) executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of the controller include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that, in addition to implementing the controller in the form of pure computer-readable program code, it is entirely possible to implement the same function by logically programming the method steps so that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be regarded as the structures within the hardware component. Or even, the devices for implementing various functions can be regarded as either software modules for implementing the method or structures within the hardware component.

[0147] The systems, devices, modules, or units illustrated in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0148] For the convenience of description, when describing the above devices, they are described separately as various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0149] Those skilled in the art should understand that the embodiments of the present invention can be provided as a method, a system, or a computer program product. Therefore, the present invention can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present invention can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memories, CD-ROMs, optical memories, etc.) containing computer-usable program code.

[0150] The present invention is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to embodiments of the invention. It should be understood that each flow and / or block in the flowchart and / or block diagram, as well as the combination of flows and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices produce means for implementing the specified functions in one or more of the flows Figure 1 one or more of the flows and / or blocks Figure 1 or means for implementing the specified functions in one or more of the blocks.

[0151] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory produce a manufacture including instruction means that implement the specified functions in one or more of the flows Figure 1 one or more of the flows and / or blocks Figure 1 or means for implementing the specified functions in one or more of the blocks.

[0152] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the specified functions in one or more of the flows Figure 1 one or more of the flows and / or blocks Figure 1 or means for implementing the specified functions in one or more of the blocks.

[0153] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0154] The memory may include non-permanent memory in the form of computer-readable media, random access memory (RAM), and / or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). The memory is an example of computer-readable media.

[0155] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0156] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0157] It will be appreciated by those skilled in the art that the embodiments of this specification may be provided as methods, systems or computer program products. Therefore, this specification may take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0158] This specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0159] Each embodiment in this specification is described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for the relevant parts, reference can be made to the corresponding description in the method embodiment.

[0160] The above description is only for the embodiments of this specification and is not intended to limit this specification. For those skilled in the art, various modifications and changes can be made to this specification. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this specification shall be included within the scope of the claims of this application.

Claims

1. A method for addressing test, which is applied to an addressing middleware in a test cloud architecture, and the method includes: Creating a virtual middleware in response to a received creation request of the virtual middleware; In response to the configuration request of the virtual middleware, selecting at least one actual address from the actual addresses of each node included in the cloud architecture as the address of the virtual middleware, and establishing a channel from the virtual middleware to a user in the cloud architecture according to the address of the virtual middleware; When testing the addressing middleware, running a test case through the addressing middleware; the test case includes an addressing request for addressing the virtual middleware; Through the addressing middleware, determining the address of the addressed virtual middleware based on the attribute information of the user sending the addressing request and the channel as a test address; Comparing the test address with a standard address to obtain a test result of the addressing middleware; the standard address is determined in advance according to the attribute information of the user sending the addressing request and the channel.

2. The method according to claim 1, wherein the channel includes a common channel; Specifically, establishing the channel from the virtual middleware to a user in the cloud architecture includes: For each address of the virtual middleware, when establishing a common channel from the address of the virtual middleware to a user in the cloud architecture, configuring the address as the address corresponding to the common channel, and configuring the attribute information of the user allowed to access the address for the common channel; The attribute information includes at least one of a logical computer room where the user is located, a physical computer room where the user is located, and a geographical area where the user is located.

3. The method according to claim 1, wherein the channel includes a dedicated channel; the users in the cloud architecture include Logical Control Center (LDC) users; Specifically, establishing the channel from the virtual middleware to a user in the cloud architecture includes: For each address of the virtual middleware, when establishing a dedicated channel from the address of the virtual middleware to an LDC user in the cloud architecture, configuring the address as the address corresponding to the dedicated channel, and determining the LDC user who needs to establish the dedicated channel as the LDC user allowed to access the address, and configuring the attribute information of the LDC user allowed to access the address for the dedicated channel; The attribute information includes at least one of a tenant to which the LDC user belongs, a logical computer room where the LDC user is located, a physical computer room where the LDC user is located, and a geographical area where the LDC user is located.

4. The method according to claim 1, wherein the channel includes a dedicated channel; the users in the cloud architecture include non-Logical Control Center (LDC) users; Specifically, establishing the channel from the virtual middleware to a user in the cloud architecture includes: For each address of the virtual middleware, when establishing a dedicated channel from this address of the virtual middleware to a non-LDC user in the cloud architecture, configure this address as the address corresponding to the dedicated channel, and determine the non-LDC user who needs to establish the dedicated channel as the non-LDC user allowed to access this address, and configure the attribute information of the non-LDC user allowed to access this address for the dedicated channel; The attribute information includes at least one of the tenant to which the non-LDC user belongs, the physical computer room where the non-LDC user is located, and the geographical area where the non-LDC user is located.

5. The method according to any one of claims 2 to 4, wherein, through the addressing middleware, based on the attribute information of the user sending the addressing request and the channel, determining the address of the virtual middleware obtained by addressing specifically includes: For each channel, through the addressing middleware, determine whether the configuration of this channel contains at least one piece of attribute information of the user sending the addressing request. If so, determine this channel as the channel matching the attribute information of the user sending the addressing request; otherwise, determine this channel is not the channel matching the attribute information of the user sending the addressing request; Determine the address corresponding to the channel matching the attribute information of the user sending the addressing request as the address of the virtual middleware obtained by addressing.

6. The method according to claim 5, after establishing the channel from the virtual middleware to the user in the cloud architecture, the method further includes: Determine the environment screening conditions corresponding to the established channel; Before determining that this channel is the channel matching the attribute information of the user sending the addressing request, the method further includes: Determine that the environment where the user sending the addressing request is located meets the environment screening conditions corresponding to this channel.

7. The method according to claim 1, wherein the address of the virtual middleware includes two or more actual addresses; Comparing the test address with the standard address to obtain the test result of the addressing middleware specifically includes: Determine whether the test address obtained by addressing corresponds one by one with the standard address; If so, determine that the addressing result of the addressing middleware is accurate; If not, determine that the addressing result of the addressing middleware is inaccurate.

8. An addressing test device, the device is applied to test the addressing middleware in the cloud architecture, and the device includes: A creation module, configured to create a virtual middleware in response to a received creation request for the virtual middleware; A configuration module, configured to, in response to the configuration request for the virtual middleware, select at least one actual address from the actual addresses of each node included in the cloud architecture as the address of the virtual middleware, and establish a channel from the virtual middleware to the user in the cloud architecture according to the address of the virtual middleware; An operation module, configured to, when testing the addressing middleware, run a test case through the addressing middleware; the test case includes an addressing request for addressing the virtual middleware; An addressing module, configured to determine, through the addressing middleware, the address of the addressed virtual middleware based on the attribute information of the user sending the addressing request and the channel, and use it as the test address; A comparison module, configured to compare the test address with the standard address to obtain the test result of the addressing middleware; the standard address is pre-determined based on the attribute information of the user sending the addressing request and the channel.

9. The apparatus according to claim 8, wherein the channel includes a common channel; The configuration module is specifically configured to, for each address of the virtual middleware, when establishing a common channel from the address of the virtual middleware to a user in the cloud architecture, configure the address as the address corresponding to the common channel, and configure the attribute information of the users allowed to access the address for the common channel; the attribute information includes at least one of the logical computer room where the user is located, the physical computer room where the user is located, and the geographical area where the user is located.

10. The apparatus according to claim 8, wherein the channel includes a dedicated channel; the users in the cloud architecture include Logical Control Center (LDC) users; The configuration module is specifically configured to, for each address of the virtual middleware, when establishing a dedicated channel from the address of the virtual middleware to an LDC user in the cloud architecture, configure the address as the address corresponding to the dedicated channel, and determine the LDC users who need to establish the dedicated channel as the LDC users allowed to access the address, and configure the attribute information of the LDC users allowed to access the address for the dedicated channel; the attribute information includes at least one of the tenant to which the LDC user belongs, the logical computer room where the LDC user is located, the physical computer room where the LDC user is located, and the geographical area where the LDC user is located.

11. The apparatus according to claim 9, wherein the channel includes a dedicated channel; the users in the cloud architecture include non-Logical Control Center (LDC) users; The configuration module is specifically configured to, for each address of the virtual middleware, when establishing a dedicated channel from the address of the virtual middleware to a non-LDC user in the cloud architecture, configure the address as the address corresponding to the dedicated channel, and determine the non-LDC users who need to establish the dedicated channel as the non-LDC users allowed to access the address, and configure the attribute information of the non-LDC users allowed to access the address for the dedicated channel; the attribute information includes at least one of the tenant to which the non-LDC user belongs, the physical computer room where the non-LDC user is located, and the geographical area where the non-LDC user is located.

12. The device according to any one of claims 9 to 11, wherein the addressing module is specifically configured to, for each channel, determine, through the addressing middleware, whether the configuration of the channel contains at least one piece of attribute information of the user sending the addressing request; if so, determine that the channel is a channel matching the attribute information of the user sending the addressing request, otherwise, determine that the channel is not a channel matching the attribute information of the user sending the addressing request; and determine the address corresponding to the channel matching the attribute information of the user sending the addressing request as the addressed address of the virtual middleware.

13. The device according to claim 12, wherein the configuration module is further configured to determine an environment screening condition corresponding to the established channel after establishing a channel from the virtual middleware to the user in the cloud architecture; The addressing module is further configured to determine that the environment where the user sending the addressing request is located meets the environment screening condition corresponding to the channel before determining that the channel is a channel matching the attribute information of the user sending the addressing request.

14. The device according to claim 8, wherein the address of the virtual middleware includes more than two actual addresses; The comparison module is specifically configured to determine whether the addressed test address and the standard address correspond one by one; if so, determine that the addressing result of the addressing middleware is accurate, otherwise, determine that the addressing result of the addressing middleware is inaccurate.

15. A computer-readable storage medium storing a computer program, which when executed by a processor, implements the method according to any one of claims 1 to 7 above.

16. An electronic device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein when the processor executes the program, it implements the method according to any one of claims 1 to 7 above.

Images