WO2021057650A1 - 数据访问方法、装置、系统、电子设备及计算机可读介质 - Google Patents

数据访问方法、装置、系统、电子设备及计算机可读介质 Download PDF

Info

Publication number
WO2021057650A1
WO2021057650A1 PCT/CN2020/116466 CN2020116466W WO2021057650A1 WO 2021057650 A1 WO2021057650 A1 WO 2021057650A1 CN 2020116466 W CN2020116466 W CN 2020116466W WO 2021057650 A1 WO2021057650 A1 WO 2021057650A1
Authority
WO
WIPO (PCT)
Prior art keywords
instance
management
control service
switch
rdma
Prior art date
Application number
PCT/CN2020/116466
Other languages
English (en)
French (fr)
Inventor
林沐晖
吴鑫
李舒楠
郭志雄
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Priority to US17/763,609 priority Critical patent/US11863520B2/en
Priority to EP20867551.2A priority patent/EP4037276A4/en
Publication of WO2021057650A1 publication Critical patent/WO2021057650A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/10Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/101Access control lists [ACL]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1097Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols

Definitions

  • the embodiments of the present application relate to the field of data access, and in particular, to a data access method, device, system, electronic device, and computer-readable medium.
  • the DCB Data Center Bridge, data center bridge
  • RoCE RDMA over Converged Ethernet, RDMA protocol based on enhanced Ethernet
  • the DCB is based on an enhanced Ethernet protocol, which guarantees data in the link through priority and flow control. Reliable transmission of layers.
  • the RDMA message based on RoCEv2 (the second version of RoCE) is embedded in the UDP (User Datagram Protocol, User Datagram Protocol) protocol message, and the UDP protocol relies on the TCP/IP protocol for routing. Because the TCP/IP protocol serves the general public, RoCE-based switching infrastructure may be used by different customers. Therefore, to provide RoCE-based RDMA communication functions on public cloud instances, it is necessary to solve the problem of different users accessing RoCE-based RDMA The problem of access isolation of network nodes. It can be seen that how to effectively solve the problem of access isolation for different users to access RDMA network nodes has become a technical problem that needs to be solved urgently.
  • the purpose of this application is to propose a data access method, device, system, electronic equipment, and computer readable medium, which are used to solve the problem of how to effectively solve the access isolation problem of different users accessing RDMA network nodes in the prior art.
  • a data access method includes: the RDMA management and control service is based on user information and the corresponding connection relationship between the first instance and the switch defined by the user, and the address segment is allocated to the first instance; the RDMA management and control service is based on the allocation for the first instance
  • the address segment constructs an access control list, where the access control list is used to control access between different first instances defined by the user; the RDMA management and control service sends the access control list to the switch management and control service, Enabling the switch management and control service to configure the access control list for the switch.
  • a data access device includes: an allocation module for allocating an address segment for the first instance based on user information and the corresponding connection relationship between the first instance and the switch defined by the user; and a building module for allocating an address segment for the first instance based on The allocated address segment is used to construct an access control list, and the access control list is used to control access between different first instances defined by the user; the first sending module is used to send the access control list to The switch management and control service enables the switch management and control service to configure the access control list for the switch.
  • a data access system includes: RDMA management and control service, which is used to allocate an address segment for the first instance based on user information and the corresponding connection relationship between the first instance and the switch defined by the user, and based on all the allocated address segments for the first instance.
  • the address segment is used to construct an access control list, the access control list is used to control access between different first instances defined by the user, and then the access control list is sent to the switch management and control service; the switch management and control service , Configured to configure the access control list for the switch according to the received access control list.
  • an electronic device including: one or more processors; a computer-readable medium configured to store one or more programs, when the one or more programs are The one or more processors execute, so that the one or more processors implement the data access method described in the first aspect of the foregoing embodiment.
  • a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, the data access method as described in the first aspect of the above-mentioned embodiment is implemented.
  • the RDMA management and control service is based on user information and the corresponding connection relationship between the user-defined first instance and the switch, and allocates an address segment to the first instance based on the allocation of the address segment to the first instance.
  • the access control list is constructed to control the access between different first instances defined by the user, and then the access control list is sent to the switch management and control service, so that the switch management and control The service configures the access control list for the switch.
  • the access control list constructed for the switch configuration can effectively control the access between different instances defined by the same user, thereby effectively solving the problem of different users accessing RDMA The problem of access isolation of network nodes.
  • FIG. 1A is a flow chart of the steps of the data access method provided in Embodiment 1 of this application;
  • FIG. 1B is a schematic structural diagram of a data access system based on a bare metal instance provided according to the first embodiment of the present application;
  • 2A is a flow chart of the steps of the data access method provided in the second embodiment of this application.
  • 2B is a schematic structural diagram of a data access system based on a virtual machine instance provided according to the second embodiment of the present application;
  • FIG. 3A is a schematic structural diagram of a data access system provided in Embodiment 3 of this application.
  • 3B is a schematic structural diagram of the data access system after the structure of the adapter provided according to the third embodiment of the present application is changed;
  • 3C is a schematic structural diagram of the data access system after the structure of the adapter provided in the third embodiment of the present application is changed;
  • FIG. 4 is a schematic structural diagram of a data access device in Embodiment 4 of this application.
  • FIG. 5 is a schematic diagram of the structure of the data processing device in the fifth embodiment of the application.
  • FIG. 6 is a schematic diagram of the structure of the electronic device in the sixth embodiment of the application.
  • FIG. 7 is the hardware structure of the electronic device in the seventh embodiment of the application.
  • FIG. 1A it shows a flowchart of the steps of the data access method in Embodiment 1 of the present application.
  • the data access method of this embodiment includes the following steps:
  • step S101 the RDMA management and control service allocates an address segment for the first instance based on the user information and the corresponding connection relationship between the first instance and the switch defined by the user.
  • the RDMA management and control service may be understood as a RoCE-based RDMA communication function service used to manage and control public cloud instances.
  • Processes, applications, virtual machines, or servers can be used to implement the RDMA management and control service.
  • the user information may be identification information of the user, for example, the user's account, the user's nickname, and so on.
  • the first instance can be understood as the core part of an ECS (Elastic Compute Service) product, that is, a server with corresponding CPU, memory, system disk, and running operating system configuration.
  • the first instance is the most basic resource of ECS. Only based on the first instance can other resources such as network, storage, and snapshots be used.
  • the switch may be a RoCE-based switch.
  • the corresponding connection relationship between the user-defined first instance and the switch can be understood as the corresponding connection relationship between the RoCE-based RDMA network port and the port of the RoCE-based switch of the user-defined first instance.
  • the address segment can be understood as a segment of continuous addresses.
  • the RoCE may be a DCB (Data Center Bridge, data center bridge) network. It can be understood that the above description is only exemplary, and the embodiments of the present application do not make any limitation on this.
  • the method before the RDMA management and control service allocates an address segment for the first instance, the method further includes: the RDMA management and control service receives the second instance sent by the second instance through its own network port that carries the A multicast packet of information about the network port; the RDMA management and control service sends a query request to the machine deployment management and control service based on the information of the network port carried in the multicast packet to query the deployment information of the second instance; The RDMA management and control service receives the deployment information returned by the machine deployment management and control service based on the query request, and determines the corresponding connection relationship between the second instance and the switch based on the deployment information.
  • the information of the network port may be the port numbers of the two ports of the RDMA network port of the second example, or the identification information of the RDMA network port of the second example.
  • the multicast message may be a multicast message based on the LLDP (Link Layer Discovery Protocol) protocol.
  • the machine deployment management and control service can be understood as a service for managing and controlling the deployment of an instance. Processes, applications, virtual machines, or servers can be used to implement the machine deployment management and control service.
  • the specific meaning of the second example is similar to the specific meaning of the first example, and will not be repeated here. It can be understood that the above description is only exemplary, and the embodiments of the present application do not make any limitation on this.
  • the method further includes: the RDMA management and control service stores the corresponding connection relationship between the second instance and the switch in a relationship table. Accordingly, by storing the corresponding connection relationship between the second instance and the switch in the relationship table, it is convenient to subsequently construct an access control list for controlling access between different first instances defined by the same user. It can be understood that the above description is only exemplary, and the embodiments of the present application do not make any limitation on this.
  • the machine deployment management and control service controls the adapter of the second instance through the management channel, and downloads the deployment image file from the designated deployment image storage service to the second instance.
  • the deployed image file can reach the second instance through the management channel or the path of the deployed image storage service to the Ethernet switch.
  • the machine deployment management and control service controls the adapter of the second instance to start the deployment image file arriving at the second instance through the management channel, so that the second instance performs related deployment.
  • the second example controls the two ports of the RDMA network port to respectively send LLDP multicast packets carrying the port information to the DCB switch, so that the LLDP multicast packets are sent to the RDMA management and control service.
  • the RDMA management and control service After receiving the LLDP multicast message, the RDMA management and control service sends a query request to the machine deployment management and control service to query the deployment information of the second instance.
  • the machine deployment management and control service returns the deployment information of the second instance to the RDMA management and control service.
  • the RDMA management and control service can establish the following corresponding relationship according to the deployment information of the second instance: the corresponding connection relationship between the RDMA network port of the second instance and the DCB switch.
  • the RDMA management and control service stores the corresponding connection relationship in the corresponding relationship table.
  • the deployment image storage service can be understood as a service for storing deployment image files. Processes, applications, virtual machines, or servers can be used to implement the deployment image storage service. It can be understood that the above description is only exemplary, and the embodiments of the present application do not make any limitation on this.
  • the method further includes: the RDMA management and control service receives an address allocation request sent by the instance management and control service based on the first instance; the RDMA management and control service queries the address allocation request based on the address allocation request The corresponding connection relationship between the first instance and the switch. Accordingly, by querying the corresponding connection relationship between the first instance and the switch based on the received address allocation request, it is convenient to construct an access control for controlling access between different first instances defined by the same user. List.
  • the instance management and control service can be understood as a service for controlling the first instance defined by the user. Processes, applications, virtual machines, or servers can be used to implement the instance management and control service. It can be understood that the above description is only exemplary, and the embodiments of the present application do not make any limitation on this.
  • the RDMA management and control service when the RDMA management and control service queries the corresponding connection relationship between the first instance and the switch based on the address allocation request, the RDMA management and control service is based on the address allocation request carried by the The identification information of the first instance is used to query a relationship table storing the corresponding connection relationship between the second instance and the switch to obtain the corresponding connection relationship between the first instance and the switch. It can be understood that the above description is only exemplary, and the embodiments of the present application do not make any limitation on this.
  • the RDMA management and control service is based on user information and the corresponding connection relationship between the first instance and the switch defined by the user.
  • the RDMA management and control service is based on the The user information carried in the address allocation request and the corresponding connection relationship between the first instance obtained by the query and the switch are invoked, and an address allocation service is invoked to allocate an address segment for the first instance.
  • the address allocation service can be understood as a service for allocating addresses. Processes, applications, virtual machines, or servers can be used to implement the address allocation service. It can be understood that the above description is only exemplary, and the embodiments of the present application do not make any limitation on this.
  • step S102 the RDMA management and control service constructs an access control list based on the address segment allocated for the first instance.
  • the access control list is used to control access between different first instances defined by the user. It can be understood that the above description is only exemplary, and the embodiments of the present application do not make any limitation on this.
  • the access control list when constructing the access control list, is constructed based on the addresses of different user-defined first instances included in the allocated address segment, so that one of the different first instances defined by the same user Interview. Specifically, access between different first instances defined by the same user is allowed, while access between first instances defined by different users is prohibited. It can be understood that the above description is only exemplary, and the embodiments of the present application do not make any limitation on this.
  • the user in order to create the first instance with RoCE-based RDMA communication function, the user can create the data structure of the instance cluster through the product's external service API (application program interface) or web console.
  • the instance management and control service returns the identification information of the instance cluster, and the user further uses the identification information to select the specifications of the corresponding elastic computing specification family, and calls the API to create a specific instance according to the specifications of the selected elastic computing specification family.
  • the instance management and control service requests the RDMA management and control service to allocate an address for the created specific instance according to the created specific instance, and the parameters carried in the request may include the identification information of the instance.
  • the RDMA management and control service queries the corresponding connection relationship between the network port of the instance and the switch according to the identification information of the instance carried in the request, and calls the DHCP (Dynamic Host Configuration Protocol) service to assign an address to the network port of the instance.
  • DHCP Dynamic Host Configuration Protocol
  • the two ports corresponding to the network ports of the instance may be bound, so one address or two addresses can be assigned according to the actual situation.
  • the DHCP service can be understood as an IP address allocation service.
  • the RDMA management and control service can query the RDMA network ports of the user-defined instance based on the identification information of the instance carried in the request.
  • the corresponding connection relationship with the DCB switch and based on the corresponding connection relationship between the RDMA network port of the user-defined instance and the DCB switch, and the user identification information carried in the address allocation request, an access control list is created for the user-defined instance.
  • the access control list acts on the DCB switch corresponding to the RDMA network ports of all instances defined by the user, and is configured to each DCB switch through the switch management and control service, so that the RDMA network ports of all instances of the same user can be mutually connected. Connected. It can be understood that the above description is only exemplary, and the embodiments of the present application do not make any limitation on this.
  • step S103 the RDMA management and control service sends the access control list to the switch management and control service, so that the switch management and control service configures the access control list for the switch.
  • the switch management and control service can be understood as a service for managing and controlling a RoCE-based switch. Processes, applications, virtual machines, or servers can be used to implement the switch management and control service.
  • the switch may be a DCB (Data Center Bridge) switch. It can be understood that the above description is only exemplary, and the embodiments of the present application do not make any limitation on this.
  • the method further includes: the RDMA management and control service returns to the instance management and control service that the address allocation service is The address segment allocated by the first instance enables the instance management and control service to start the first instance to obtain a mirror file matching the specifications of the first instance from the mirror service, and configure the address based on the mirror file The address segment allocated by the service for the first instance is allocated.
  • the mirroring service can be understood as a service for storing mirrored files. Processes, applications, virtual machines, or servers can be used to implement the mirroring service.
  • the instance management and control service can start the address segment allocated by the first instance configuration.
  • the RDMA management and control service After the switch management and control service configures the access control list for the DCB switch, the RDMA management and control service returns the address allocated by the address allocation service for the first instance to the instance management and control service.
  • the instance management and control service starts the instance and assigns it to the corresponding mirror service to obtain the mirror file of the specifications of the instance.
  • the instance After the image file is transferred to the corresponding instance and executed, the instance starts to configure the address requested by the instance management service for the instance, and configure it on the RDMA network port of the instance.
  • Users began to use this example with RoCE-based RDMA communication functions. It can be understood that the above description is only exemplary, and the embodiments of the present application do not make any limitation on this.
  • the method further includes: the RDMA management service receives a second instance release request sent by the instance management service based on the first instance release request sent by the user; the RDMA management service is based on the second instance release request; Instance release request, recover the address of the instance to be released corresponding to the instance identification information carried in the second instance release request, and configure the switch connected to the instance to be released through the switch management and control service, so that it is connected to the instance to be released The network port of the connected switch is disconnected from other network ports; the RDMA management and control service returns the release result of the to-be-released instance requested by the second instance release request to the instance management and control service, so that the instance The management and control service returns the to-be-released instance to the inventory, and returns the release success message to the user. In this way, the instance requested to be released by the user can be released through the received second instance release request. It can be understood that the above description is only exemplary, and the embodiments of the present application do not make any limitation on this.
  • the user sends an instance release request to the instance management service through the API or console.
  • the instance management service receives the request and requests the RDMA management service to release the instance.
  • the RDMA management and control service retrieves the address of the RDMA network port of the instance, and configures the DCB switch through the switch management and control service, configures the DCB switch corresponding to the RDMA network port of the instance to be disconnected from other network ports, and returns the instance release result to the instance Control services.
  • the instance management and control service continues to release other resources related to the instance, returns the instance to the inventory, and returns information to the user that the instance is released successfully.
  • the data access process can be described in detail in conjunction with the data access system shown in FIG. 1B.
  • the adapter of the bare metal instance can realize the docking between the bare metal instance and the elastic computing management and control.
  • the bare metal instance also has two RDMA network ports based on enhanced Ethernet, which are dual-uplinked to the DCB switch, and the DCB switch is further dual-uplinked to the DCB aggregation switch to avoid a single point of failure.
  • the data access system has a highly available machine deployment management and control service, which is connected to the bare metal instance and the RDMA management and control service through the management channel.
  • the RDMA control service is also a highly available configuration to avoid a single server failure causing the system to become unavailable. It is connected to the machine deployment control service and connected to the switch control service to control the configuration of the DCB switch.
  • the data access system also includes elastic bare metal ECS (Elastic Compute Service) production control services, which provide elastic computing services to the public through external service APIs or web consoles.
  • ECS Elastic Compute Service
  • the data access process combined with the data access system shown in Figure 1B is introduced in detail. Specifically, it includes the deployment phase, the user usage phase, and the user destruction phase.
  • the specific deployment phase is as follows: the machine deployment management and control service controls the adapter of the bare metal instance through the management channel, and downloads the deployment image file from the designated deployment image storage service to the bare metal instance.
  • the deployed image file can reach the bare metal instance through the management channel or the path of the deployed image storage service to the Ethernet switch.
  • the machine deployment management and control service controls the adapter of the bare metal instance to start the deployment image file that reaches the bare metal instance through the management channel, so that the bare metal instance is deployed.
  • the bare metal instance controls the two ports (port-a and port-b) of the RDMA network port, and respectively sends LLDP multicast packets carrying the port information to the DCB switch, so that the LLDP multicast packets are Send to RDMA control service.
  • the RDMA management and control service After receiving the LLDP multicast message, the RDMA management and control service sends a query request to the machine deployment management and control service to query the deployment information of the bare metal instance.
  • the machine deployment management and control service returns the deployment information of the bare metal instance to the RDMA management and control service.
  • the RDMA management and control service can establish the following corresponding relationship based on the deployment information of the bare metal instance: the corresponding connection relationship between the RDMA network port of the bare metal instance and the DCB switch.
  • the RDMA management and control service stores the corresponding connection relationship in the corresponding relationship table.
  • the user use stage is as follows: in order to create a bare metal instance with RoCE-based RDMA communication function, the user can create a bare metal instance cluster through the product's external service API (application program interface) or web console Data structure, the bare metal ECS instance management and control service returns the identification information of the bare metal instance cluster. The user further uses the identification information to select the specifications of the corresponding elastic computing specification family, and calls the API to create a specific bare metal according to the specifications of the selected elastic computing specification family. Examples of metals. The bare metal ECS instance management and control service requests the RDMA management and control service to allocate an address for the created specific bare metal instance according to the created specific bare metal instance.
  • API application program interface
  • web console Data structure the bare metal ECS instance management and control service returns the identification information of the bare metal instance cluster.
  • the user further uses the identification information to select the specifications of the corresponding elastic computing specification family, and calls the API to create a specific bare metal according to the specifications of the selected elastic computing specification family.
  • the parameters carried in the request may include the identification information of the bare metal instance and the identification information of the user.
  • the RDMA management and control service queries the corresponding connection relationship between the network port of the bare metal instance and the port of the DCB switch according to the identification information of the bare metal instance carried in the request, and calls the DHCP (Dynamic Host Configuration Protocol, dynamic host configuration protocol) service for the bare metal instance
  • DHCP Dynamic Host Configuration Protocol, dynamic host configuration protocol
  • the network port is assigned an address.
  • the two ports corresponding to the network ports of the bare metal instance may be bound, so one address or two addresses can be allocated according to the actual situation.
  • the RDMA management and control service can query the user-defined bare metal based on the identification information of the user-defined bare metal instance
  • the corresponding connection relationship between the RDMA network port of the instance and the DCB switch is based on the user-defined corresponding connection relationship between the RDMA network port of the bare metal instance and the DCB switch, and the user identification information carried in the address allocation request.
  • the metal instance creates an access control list.
  • the access control list acts on the DCB switch corresponding to the RDMA network ports of all bare metal instances defined by the user, and is configured to each DCB switch through the switch management and control service, so that the RDMA of all bare metal instances defined by the same user
  • the network ports can communicate with each other.
  • the switch management and control service configures the access control list for the DCB switch
  • the RDMA management and control service returns the address assigned by the address allocation service to the RDMA network port of the bare metal instance to the bare metal ECS instance management and control service.
  • the bare metal ECS instance management and control service starts the bare metal instance and assigns it to the corresponding image service to obtain the image file of the specifications of the bare metal instance.
  • the bare metal instance After the image file is transferred to the corresponding bare metal instance and execution is complete, the bare metal instance starts to configure the bare metal ECS instance management and control service to apply for the IP address of the bare metal instance, and configure it on the RDMA network port of the bare metal instance. Users began to use the bare metal instance with RoCE-based RDMA communication function.
  • the user destruction phase is as follows: the user sends a bare metal instance release request to the ECS instance management and control service through the API or console.
  • the ECS instance management and control service receives the request and sends a request to the RDMA management and control service to release the bare metal instance.
  • the RDMA management and control service recovers the address of the RDMA network port of the bare metal instance, and configures the DCB switch through the switch management and control service to set the RDMA network of the bare metal instance.
  • the DCB switch connected to the corresponding port is configured to be disconnected from other network ports, and the result of the release of the bare metal instance is returned to the ECS instance management and control service.
  • the ECS instance management and control service continues to release other resources related to the bare metal instance, returns the bare metal instance to the inventory, and returns information to the user that the bare metal instance is successfully released.
  • the bare metal instance can be understood as a server with only a set of corresponding CPU, memory, system disk, and running operating system configuration. It can be understood that the above description is only exemplary, and the embodiments of the present application do not make any limitation on this.
  • the RDMA management and control service is based on user information and the corresponding connection relationship between the first instance and the switch defined by the user, assigns an address segment to the first instance, and based on the first instance
  • the allocated address segment is used to construct an access control list
  • the access control list is used to control access between different first instances defined by the user, and then the access control list is sent to the switch management and control service, so that the switch
  • the management and control service configures the access control list for the switch.
  • the access control list constructed for the switch configuration can effectively control the access between different instances defined by the same user, thus effectively solving the access of different users.
  • the problem of access isolation of RDMA network nodes can effectively control the access between different instances defined by the same user, thus effectively solving the access of different users.
  • the data access method of this embodiment can be executed by any suitable device with data processing capabilities, including but not limited to: cameras, terminals, mobile terminals, PCs, servers, vehicle-mounted devices, entertainment devices, advertising devices, personal digital assistants ( PDA), tablet computers, notebook computers, handheld game consoles, smart glasses, smart watches, wearable devices, virtual display devices or display enhancement devices (such as Google Glass, Oculus Rift, Hololens, Gear VR), etc.
  • PDA personal digital assistants
  • tablet computers notebook computers
  • handheld game consoles smart glasses
  • smart watches wearable devices
  • virtual display devices or display enhancement devices such as Google Glass, Oculus Rift, Hololens, Gear VR
  • the data access method of this embodiment includes the following steps:
  • step S201 the RDMA management and control service allocates an address segment for the first instance based on the user information and the corresponding connection relationship between the first instance and the switch defined by the user.
  • step S201 is similar to the above-mentioned step S101, it will not be repeated here.
  • step S202 the RDMA management and control service receives an address allocation request sent by the instance management and control service based on the first instance.
  • the information carried in the address allocation request includes at least one of the following: identification information of the user, identification information of the user-defined instance cluster, and identification information of the instance. It can be understood that the above description is only exemplary, and the embodiments of the present application do not make any limitation on this.
  • step S203 the RDMA management and control service constructs the access control list based on the identification information of the cluster to which the first instance belongs, carried in the address allocation request, and the address segment allocated for the first instance .
  • the access control list is used to control access between different first instances belonging to the same cluster. It can be understood that the above description is only exemplary, and the embodiments of the present application do not make any limitation on this.
  • the RDMA management and control service when constructing the access control list, defines the user definitions included in the allocated address segment based on the identification information of the cluster to which the first instance belongs, carried in the address allocation request Perform a filtering operation on the addresses of different first instances of the same cluster to obtain addresses of different first instances belonging to the same cluster, and construct an access control list based on the addresses of different first instances belonging to the same cluster, so that the same user-defined Access is made between different first instances belonging to the same cluster. Specifically, access between different first instances defined by the same user belonging to the same cluster is allowed, while access between first instances defined by different users is prohibited, and access between first instances defined by the same user belonging to different clusters is prohibited. Interview. It can be understood that the above description is only exemplary, and the embodiments of the present application do not make any limitation on this.
  • step S204 the RDMA management and control service sends the access control list to the switch management and control service, so that the switch management and control service configures the access control list for the switch.
  • step S204 is similar to the above step S103, it will not be repeated here.
  • the data access process can be described in detail in conjunction with the data access system shown in FIG. 2B. Since the structure of the data access system shown in FIG. 2B is similar to the structure of the data access system shown in FIG. 1B, it will not be repeated here. Since the data access process combined with the data access system shown in FIG. 2B is roughly similar to the data access process combined with the data access system shown in FIG. 1B, details are not described herein again.
  • the difference between the data access process of a virtual machine instance and the data access process of a bare metal instance is that the virtual machine instance runs a virtual machine monitor (virtual machine monitor or hypervisor).
  • the enhanced Ethernet-based RDMA network port of the virtual machine instance is directly connected to the virtual machine of the virtual machine instance, and the enhanced Ethernet-based RDMA network port of the virtual machine instance is configured in the virtual machine On the virtual machine of the instance.
  • Pass-through methods include but are not limited to PF (physical function) pass-through or use SRIOV technology to use VF (virtual function) pass-through or other analog solutions.
  • the virtual machine instance can be understood as the core part of an ECS (Elastic Compute Service) product, a server configured by corresponding virtual CPU and virtual memory. It can be understood that the above description is only exemplary, and the embodiments of the present application do not make any limitation on this.
  • the RDMA management and control service is based on user information and the corresponding connection relationship between the first instance and the switch defined by the user, allocates an address segment for the first instance, and receives the instance management and control service based on the The address allocation request sent by the first instance is then based on the user-defined identification information of the cluster to which the first instance belongs and the address segment allocated for the first instance carried in the address allocation request to construct an access control list.
  • the data access method of this embodiment can be executed by any suitable device with data processing capabilities, including but not limited to: cameras, terminals, mobile terminals, PCs, servers, vehicle-mounted devices, entertainment devices, advertising devices, personal digital assistants ( PDA), tablet computers, notebook computers, handheld game consoles, smart glasses, smart watches, wearable devices, virtual display devices or display enhancement devices (such as Google Glass, Oculus Rift, Hololens, Gear VR), etc.
  • PDA personal digital assistants
  • tablet computers notebook computers
  • handheld game consoles smart glasses
  • smart watches wearable devices
  • virtual display devices or display enhancement devices such as Google Glass, Oculus Rift, Hololens, Gear VR
  • FIG. 3A a schematic structural diagram of the data access system in the third embodiment of the present application is shown.
  • the data access system provided by this embodiment includes: RDMA management and control service 301, which is used to allocate an address segment for the first instance based on user information and the corresponding connection relationship between the first instance and the switch defined by the user, and based on the The address segment allocated by the first instance constructs an access control list, and the access control list is used to control access between different first instances defined by the user, and then the access control list is sent to the switch management and control service
  • the switch management and control service 302 is configured to configure the access control list for the switch according to the received access control list.
  • the first instance includes an adapter, and the adapter is integrated with a network port.
  • the network port is an RDMA network port based on enhanced Ethernet.
  • the adapter of the bare metal instance integrates the RDMA network port of the bare metal instance based on the enhanced Ethernet.
  • the RDMA network port based on enhanced Ethernet of the bare metal instance is used as the transmission channel of RDMA based on enhanced Ethernet and at the same time as the transmission channel of ordinary Ethernet.
  • the adapter of the virtual machine instance integrates the virtual machine instance's RDMA network port based on enhanced Ethernet.
  • the integrated RDMA network port of the adapter is directly connected to the virtual machine of the virtual machine instance.
  • two uplink Ethernet switches can be omitted, and the enhanced Ethernet-based RDMA network port of the virtual machine instance is used as the transmission channel of the enhanced Ethernet-based RDMA and at the same time as the transmission channel of ordinary Ethernet.
  • the data access system of this embodiment is used to implement the corresponding data access methods in the foregoing multiple method embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.
  • FIG. 4 there is shown a schematic structural diagram of a data access device in the fourth embodiment of the present application.
  • the data access device of this embodiment includes: an allocation module 401, configured to allocate an address segment for the first instance based on user information and the corresponding connection relationship between the first instance and the switch defined by the user; For the address segment allocated for the first instance, an access control list is constructed, and the access control list is used to control access between different first instances defined by the user; the first sending module 403 is used to transfer The access control list is sent to the switch management and control service, so that the switch management and control service configures the access control list for the switch.
  • the data access device in this embodiment is used to implement the corresponding data access methods in the foregoing multiple method embodiments, and has the beneficial effects of the corresponding method embodiments, and will not be repeated here.
  • FIG. 5 there is shown a schematic structural diagram of a data access device in Embodiment 5 of the present application.
  • the data access device of this embodiment includes: an allocation module 505, configured to allocate an address segment to the first instance based on user information and the corresponding connection relationship between the first instance and the switch defined by the user; For the address segment allocated for the first instance, an access control list is constructed, and the access control list is used to control access between different first instances defined by the user; the first sending module 509 is used to transfer The access control list is sent to the switch management and control service, so that the switch management and control service configures the access control list for the switch.
  • the device further includes: a first receiving module 501, configured to receive a multicast message carrying information about the network port sent by the second instance through its own network port;
  • the second sending module 502 is configured to send a query request to the machine deployment management and control service based on the information of the network port carried in the multicast message to query the deployment information of the second instance;
  • the determining module 503 is configured to receive The machine deployment management and control service determines the corresponding connection relationship between the second instance and the switch based on the deployment information returned by the query request and based on the deployment information.
  • the device further includes: a storage module 504, configured to store the corresponding connection relationship between the second instance and the switch in a relationship table.
  • a storage module 504 configured to store the corresponding connection relationship between the second instance and the switch in a relationship table.
  • the device further includes: a second receiving module 506, configured to receive an address allocation request sent by the instance management and control service based on the first instance; a query module 507, configured to query the address allocation request based on the address allocation request The corresponding connection relationship between the first instance and the switch.
  • a second receiving module 506 configured to receive an address allocation request sent by the instance management and control service based on the first instance
  • a query module 507 configured to query the address allocation request based on the address allocation request The corresponding connection relationship between the first instance and the switch.
  • the allocation module 505 is specifically configured to: based on the user information carried in the address allocation request and the corresponding connection relationship between the first instance and the switch obtained by the query, invoking the address allocation service is The first example allocates address segments.
  • the query module 507 is specifically configured to query a relationship table storing the corresponding connection relationship between the second instance and the switch based on the identification information of the first instance carried in the address allocation request To obtain the corresponding connection relationship between the first instance and the switch.
  • the constructing module 508 is specifically configured to construct the allocating information based on the identification information of the cluster to which the first instance belongs and the address segment allocated for the first instance carried in the address allocation request.
  • the access control list is used to control access between different first instances belonging to the same cluster.
  • the device further includes: a first returning module 510, configured to return the address segment allocated by the address allocation service for the first instance to the instance management and control service, Causes the instance management and control service to start the first instance to obtain a mirror file matching the specifications of the first instance from a mirroring service, and configure the address allocation service to be allocated by the first instance based on the mirror file Address segment.
  • a first returning module 510 configured to return the address segment allocated by the address allocation service for the first instance to the instance management and control service, Causes the instance management and control service to start the first instance to obtain a mirror file matching the specifications of the first instance from a mirroring service, and configure the address allocation service to be allocated by the first instance based on the mirror file Address segment.
  • the device further includes: a second receiving module 511, configured to receive a second instance release request sent by the instance management service based on the first instance release request sent by the user; a release module 512, configured to receive a second instance release request based on the second instance release request sent by the user.
  • a second receiving module 511 configured to receive a second instance release request sent by the instance management service based on the first instance release request sent by the user
  • a release module 512 configured to receive a second instance release request based on the second instance release request sent by the user.
  • Instance release request recover the address of the instance to be released corresponding to the instance identification information carried in the second instance release request, and configure the switch connected to the instance to be released through the switch management and control service, so that it is connected to the instance to be released
  • the network port of the connected switch is disconnected from other network ports;
  • the second return module 513 is configured to return the release result of the to-be-released instance requested by the second instance release request to the instance management and control service, so that The instance management and control service returns the to-be-released instance to the inventory, and returns the release success message to the user.
  • the data access device in this embodiment is used to implement the corresponding data access methods in the foregoing multiple method embodiments, and has the beneficial effects of the corresponding method embodiments, and will not be repeated here.
  • FIG. 6 is a schematic diagram of the structure of the electronic device in the sixth embodiment of the application; the electronic device may include:
  • the computer-readable medium 602 may be configured to store one or more programs,
  • the one or more processors When the one or more programs are executed by the one or more processors, the one or more processors implement the data access method described in the first embodiment or the second embodiment.
  • FIG. 7 is the hardware structure of the electronic device in the seventh embodiment of the application; as shown in FIG. 7, the hardware structure of the electronic device may include: a processor 701, a communication interface 702, a computer-readable medium 703, and a communication bus 704;
  • the processor 701, the communication interface 702, and the computer-readable medium 703 communicate with each other through the communication bus 704;
  • the communication interface 702 may be an interface of a communication module, such as an interface of a GSM module;
  • the processor 701 may be specifically configured to: the RDMA management and control service is based on user information and the corresponding connection relationship between the first instance and the switch defined by the user, to allocate an address segment for the first instance; the RDMA management and control service is based on the The address segment allocated by the first instance constructs an access control list, and the access control list is used to control access between different first instances defined by the user; the RDMA management and control service sends the access control list To the switch management and control service, so that the switch management and control service configures the access control list for the switch.
  • the processor 701 may be a general-purpose processor, including a central processing unit (CPU), a network processor (Network Processor, NP), etc.; it may also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), etc. ), ready-made programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • CPU central processing unit
  • NP Network Processor
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA ready-made programmable gate array
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the computer-readable medium 703 may be, but is not limited to, a random access storage medium (Random Access Memory, RAM), a read-only storage medium (Read Only Memory, ROM), a programmable read-only storage medium (Programmable Read-Only Memory, PROM), Erasable Programmable Read-Only Memory (EPROM), Electrical Erasable Programmable Read-Only Memory (EEPROM), etc.
  • RAM Random Access Memory
  • ROM read-only storage medium
  • PROM Programmable Read-Only Memory
  • EPROM Erasable Programmable Read-Only Memory
  • EEPROM Electrical Erasable Programmable Read-Only Memory
  • an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes program code configured to execute the method shown in the flowchart.
  • the computer program may be downloaded and installed from the network through the communication part, and/or installed from a removable medium.
  • CPU central processing unit
  • the computer program executes the above-mentioned functions defined in the method of the present application.
  • the computer-readable medium described in this application may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two.
  • the computer-readable medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the above. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections with one or more wires, portable computer disks, hard disks, random access storage media (RAM), read-only storage media (ROM), erasable Type programmable read-only storage medium (EPROM or flash memory), optical fiber, portable compact disk read-only storage medium (CD-ROM), optical storage medium, magnetic storage medium, or any suitable combination of the above.
  • RAM random access storage media
  • ROM read-only storage media
  • EPROM or flash memory erasable Type programmable read-only storage medium
  • CD-ROM portable compact disk read-only storage medium
  • magnetic storage medium or any suitable combination of the above.
  • a computer-readable storage medium may be any tangible medium that contains or stores a program, and the program may be used by or in combination with an instruction execution system, apparatus, or device.
  • a computer-readable signal medium may include a data signal propagated in a baseband or as a part of a carrier wave, and a computer-readable program code is carried therein. This propagated data signal can take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • the computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium.
  • the computer-readable medium may send, propagate, or transmit a program configured to be used by or in combination with an instruction execution system, apparatus, or device. .
  • the program code contained on the computer-readable medium can be transmitted by any suitable medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.
  • the computer program code configured to perform the operations of this application can be written in one or more programming languages or a combination thereof.
  • the programming languages include object-oriented programming languages—such as Java, Smalltalk, C++, and also conventional The procedural programming language-such as "C" language or similar programming language.
  • the program code can be executed entirely on the user's computer, partly on the user's computer, executed as an independent software package, partly on the user's computer and partly executed on a remote computer, or entirely executed on the remote computer or server.
  • the remote computer can be connected to the user's computer through any kind of network: including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (for example, using an Internet service provider to connect to the Internet) connection).
  • LAN local area network
  • WAN wide area network
  • an Internet service provider to connect to the Internet
  • each block in the flowchart or block diagram may represent a module, program segment, or part of the code, and the module, program segment, or part of the code contains one or more configurations to realize the specified logical function Executable instructions.
  • sequence relationships there are specific sequence relationships, but these sequence relationships are only exemplary. In specific implementation, these steps may be fewer, more, or the execution order may be adjusted. That is, in some alternative implementations, the functions marked in the block may also occur in a different order from the order marked in the drawings.
  • each block in the block diagram and/or flowchart, and the combination of the blocks in the block diagram and/or flowchart can be implemented by a dedicated hardware-based system that performs the specified functions or operations Or it can be realized by a combination of dedicated hardware and computer instructions.
  • the modules involved in the embodiments described in this application can be implemented in software or hardware.
  • the described module may also be provided in the processor, for example, it may be described as: a processor includes a distribution module, a building module, and a first sending module.
  • the names of these modules do not constitute a limitation on the module itself under certain circumstances.
  • the distribution module can also be described as “based on user information and the corresponding connection relationship between the first instance and the switch defined by the user, which is The first example allocates the module of the address segment".
  • the present application also provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, the data access method as described in the first embodiment or the second embodiment is implemented.
  • the present application also provides a computer-readable medium.
  • the computer-readable medium may be included in the device described in the foregoing embodiment; or it may exist alone without being assembled into the device.
  • the above-mentioned computer-readable medium carries one or more programs.
  • the device When the above-mentioned one or more programs are executed by the device, the device: RDMA management and control service is based on user information and the corresponding connection relationship between the first instance and the switch defined by the user , Allocate an address segment for the first instance; the RDMA management and control service constructs an access control list based on the address segment allocated for the first instance, and the access control list is used to control different user-defined Access between the first instances; the RDMA management and control service sends the access control list to the switch management and control service, so that the switch management and control service configures the access control list for the switch.
  • first, second, the first or “the second” used in various embodiments of the present disclosure can modify various components regardless of order and/or importance , But these expressions do not limit the corresponding components.
  • the above expressions are only configured for the purpose of distinguishing elements from other elements.
  • the first user equipment and the second user equipment represent different user equipment, although both are user equipment.
  • the first element may be referred to as the second element, and similarly, the second element may be referred to as the first element.
  • an element for example, a first element
  • another element for example, a second element
  • an element e.g., a second element
  • an element e.g., a second element
  • the one element is directly connected to the other element or the one element is connected via another element (e.g., The third element) is indirectly connected to the other element.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Stored Programmes (AREA)
  • Small-Scale Networks (AREA)

Abstract

本申请实施例提供了一种数据访问方法、装置、系统、电子设备及计算机可读介质,涉及数据访问领域。其中,所述方法包括:RDMA管控服务基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为第一实例分配地址段;RDMA管控服务基于为第一实例分配的地址段,构建访问控制列表,访问控制列表用于控制用户定义的不同的第一实例之间进行访问;RDMA管控服务将访问控制列表发送至交换机管控服务,使得交换机管控服务为交换机配置访问控制列表。通过本申请实施例,能够有效控制同一用户定义的不同实例之间进行访问,从而有效解决了不同用户访问RDMA网络节点的访问隔离的问题。

Description

数据访问方法、装置、系统、电子设备及计算机可读介质
本申请要求2019年09月25日递交的申请号为201910912110.8、发明名称为“数据访问方法、装置、系统、电子设备及计算机可读介质”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及数据访问领域,尤其涉及一种数据访问方法、装置、系统、电子设备及计算机可读介质。
背景技术
基于RoCE(RDMA over Converged Ethernet,基于增强型以太网的RDMA协议)的DCB(Data Center Bridge,数据中心桥)网络是基于一种增强型以太网协议,通过优先级和流控保障数据在链路层的可靠传输。
基于RoCEv2(RoCE的第二个版本的)的RDMA报文嵌在UDP(User Datagram Protocol,用户数据报协议)协议报文中,而UDP协议依赖TCP/IP协议进行路由。由于TCP/IP协议服务的是社会大众,基于RoCE的交换基础设施有可能会被不同客户使用,因此,在公共云的实例上提供基于RoCE的RDMA通信功能,需要解决不同用户访问基于RoCE的RDMA网络节点的访问隔离的问题。由此可见,如何有效解决不同用户访问RDMA网络节点的访问隔离的问题成为当前亟待解决的技术问题。
发明内容
本申请的目的在于提出一种数据访问方法、装置、系统、电子设备及计算机可读介质,用于解决现有技术中存在的如何有效解决不同用户访问RDMA网络节点的访问隔离的问题。
根据本申请实施例的第一方面,提供了一种数据访问方法。所述方法包括:RDMA管控服务基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为所述第一实例分配地址段;所述RDMA管控服务基于为所述第一实例分配的所述地址段,构建访问控制列表,所述访问控制列表用于控制所述用户定义的不同的第一实例之间进行访问;所述RDMA管控服务将所述访问控制列表发送至交换机管控服务,使得所述交换机管控服务为所述交换机配置所述访问控制列表。
根据本申请实施例的第二方面,提供了一种数据访问装置。所述装置包括:分配模块,用于基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为所述第一实例分配地址段;构建模块,用于基于为所述第一实例分配的所述地址段,构建访问控制列表,所述访问控制列表用于控制所述用户定义的不同的第一实例之间进行访问;第一发送模块,用于将所述访问控制列表发送至交换机管控服务,使得所述交换机管控服务为所述交换机配置所述访问控制列表。
根据本申请实施例的第三方面,提供了一种数据访问系统。所述系统包括:RDMA管控服务,用于基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为所述第一实例分配地址段,并基于为所述第一实例分配的所述地址段,构建访问控制列表,所述访问控制列表用于控制所述用户定义的不同的第一实例之间进行访问,再将所述访问控制列表发送至交换机管控服务;所述交换机管控服务,用于根据接收到的所述访问控制列表,为所述交换机配置所述访问控制列表。
根据本申请实施例的第四方面,提供了一种电子设备,包括:一个或多个处理器;计算机可读介质,配置为存储一个或多个程序,当所述一个或多个程序被所述一个或多个处理器执行,使得所述一个或多个处理器实现如上述实施例的第一方面所述的数据访问方法。
根据本申请实施例的第五方面,提供了一种计算机可读介质,其上存储有计算机程序,该程序被处理器执行时实现如上述实施例的第一方面所述的数据访问方法。
根据本申请实施例提供的技术方案,RDMA管控服务基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为所述第一实例分配地址段,并基于为所述第一实例分配的所述地址段,构建访问控制列表,所述访问控制列表用于控制所述用户定义的不同的第一实例之间进行访问,再将所述访问控制列表发送至交换机管控服务,使得交换机管控服务为交换机配置访问控制列表,与现有的其它方式相比,通过为交换机配置构建得到的访问控制列表,能够有效控制同一用户定义的不同实例之间进行访问,从而有效解决了不同用户访问RDMA网络节点的访问隔离的问题。
附图说明
通过阅读参照以下附图所作的对非限制性实施例所作的详细描述,本申请的其它特征、目的和优点将会变得更明显:
图1A为本申请实施例一提供的数据访问方法的步骤流程图;
图1B为根据本申请实施例一提供的基于裸金属实例的数据访问系统的结构示意图;
图2A为本申请实施例二提供的数据访问方法的步骤流程图;
图2B为根据本申请实施例二提供的基于虚拟机实例的数据访问系统的结构示意图;
图3A为本申请实施例三提供的数据访问系统的结构示意图;
图3B为根据本申请实施例三提供的适配器的结构变动后的数据访问系统的结构示意图;
图3C为根据本申请实施例三提供的适配器的结构变动后的数据访问系统的结构示意图;
图4为本申请实施例四中数据访问装置的结构示意图;
图5为本申请实施例五中数据处理装置的结构示意图;
图6为本申请实施例六中电子设备的结构示意图;
图7为本申请实施例七中电子设备的硬件结构。
具体实施方式
下面结合附图和实施例对本申请作进一步的详细说明。可以理解的是,此处所描述的具体实施例仅仅配置为解释相关发明,而非对该发明的限定。另外还需要说明的是,为了便于描述,附图中仅示出了与有关发明相关的部分。
需要说明的是,在不冲突的情况下,本申请中的实施例及实施例中的特征可以相互组合。下面将参考附图并结合实施例来详细说明本申请。
参照图1A,示出了本申请实施例一的数据访问方法的步骤流程图。
具体地,本实施例的数据访问方法包括以下步骤:
在步骤S101中,RDMA管控服务基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为所述第一实例分配地址段。
在本申请实施例中,所述RDMA管控服务可理解为用于管控公共云的实例的基于RoCE的RDMA通信功能的服务。可以使用进程、应用、虚拟机或者服务器来实现所述RDMA管控服务。所述用户信息可以为用户的标识信息,例如,用户的账号、用户的昵称等。所述第一实例可理解为ECS(Elastic Compute Service,弹性计算服务)产品最核心的部分,也即是具有相应的CPU、内存、系统盘和运行的操作系统配置的服务器。第一实例是ECS最基本的资源,只有基于第一实例,才能使用网络、存储、快照等其他资 源。所述交换机可为基于RoCE的交换机。所述用户定义的第一实例与交换机的对应连接关系可理解为所述用户定义的第一实例的基于RoCE的RDMA网口与基于RoCE的交换机的端口的对应连接关系。所述地址段可理解为一段连续的地址。其中,所述RoCE可以为DCB(Data Center Bridge,数据中心桥)网络。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
在一些可选实施例中,所述RDMA管控服务为所述第一实例分配地址段之前,所述方法还包括:所述RDMA管控服务接收第二实例通过自身的网口发送的携带有所述网口的信息的组播报文;所述RDMA管控服务基于所述组播报文中携带的所述网口的信息,向机器部署管控服务发送查询请求,以查询所述第二实例的部署信息;所述RDMA管控服务接收所述机器部署管控服务基于所述查询请求返回的所述部署信息,并基于所述部署信息,确定所述第二实例与所述交换机的对应连接关系。其中,所述网口的信息可以是第二实例的RDMA网口的两个端口的端口号,还可以是第二实例的RDMA网口的标识信息。所述组播报文可以为基于LLDP(Link Layer Discovery Protocol,链路层发现协议)协议的组播报文。所述机器部署管控服务可理解为用于管控实例的部署的服务。可以使用进程、应用、虚拟机或者服务器来实现所述机器部署管控服务。所述第二实例的具体含义与所述第一实例的具体含义类似,在此不再赘述。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
在一些可选实施例中,所述方法还包括:所述RDMA管控服务将所述第二实例与所述交换机的对应连接关系存储至关系表中。籍此,通过将所述第二实例与所述交换机的对应连接关系存储至关系表中,能够方便后续构建用于控制同一用户定义的不同的第一实例之间进行访问的访问控制列表。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
在一个具体的例子中,机器部署管控服务通过管理通道控制第二实例的适配器,从指定的部署镜像存储服务下载部署镜像文件到第二实例。具体地,部署镜像文件可以通过管理通道或者部署镜像存储服务到以太网交换机的路径到达第二实例。然后,机器部署管控服务通过管理通道再控制第二实例的适配器启动到达第二实例的部署镜像文件,使得第二实例进行相关的部署。具体地,第二实例通过控制RDMA网口的两个端口,分别发送携带有该端口信息的LLDP组播报文到DCB交换机,使得该LLDP组播报文被发送至RDMA管控服务。RDMA管控服务收到该LLDP组播报文之后,向机器部署管控服务发送查询请求,以查询第二实例的部署信息。机器部署管控服务向RDMA管控服务 返回第二实例的部署信息。然后,RDMA管控服务可根据第二实例的部署信息建立以下的对应关系:第二实例的RDMA网口与DCB交换机的对应连接关系。此外,RDMA管控服务将所述对应连接关系存入到对应的关系表中。其中,所述部署镜像存储服务可理解为用于存储部署镜像文件的服务。可以使用进程、应用、虚拟机或者服务器来实现所述部署镜像存储服务。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
在一些可选实施例中,所述方法还包括:所述RDMA管控服务接收实例管控服务基于所述第一实例发送的地址分配请求;所述RDMA管控服务基于所述地址分配请求,查询所述第一实例与所述交换机的对应连接关系。籍此,通过基于接收到的地址分配请求,查询所述第一实例与所述交换机的对应连接关系,能够方便后续构建用于控制同一用户定义的不同的第一实例之间进行访问的访问控制列表。其中,所述实例管控服务可理解为用于管控用户定义的第一实例的服务。可以使用进程、应用、虚拟机或者服务器来实现所述实例管控服务。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
在一个具体的例子中,所述RDMA管控服务基于所述地址分配请求,查询所述第一实例与所述交换机的对应连接关系时,所述RDMA管控服务基于所述地址分配请求携带的所述第一实例的标识信息,查询存储有所述第二实例与所述交换机的对应连接关系的关系表,以获得所述第一实例与所述交换机的对应连接关系。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
在一些可选实施例中,所述RDMA管控服务基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为所述第一实例分配地址段时,所述RDMA管控服务基于所述地址分配请求携带的所述用户信息,以及查询得到的所述第一实例与所述交换机的对应连接关系,调用地址分配服务为所述第一实例分配地址段。籍此,通过调用地址分配服务为第一实例分配地址段,从而有效解决了不同用户访问RDMA网络节点的地址的分配问题。其中,所述地址分配服务可理解为用于分配地址的服务。可以使用进程、应用、虚拟机或者服务器来实现所述地址分配服务。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
在步骤S102中,所述RDMA管控服务基于为所述第一实例分配的所述地址段,构建访问控制列表。
在本申请实施例中,所述访问控制列表用于控制所述用户定义的不同的第一实例之 间进行访问。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
在一个具体的例子中,在构建访问控制列表时,基于分配的所述地址段包括的用户定义的不同的第一实例的地址,构建访问控制列表,使得同一用户定义的不同的第一实例之间进行访问。具体地,允许同一用户定义的不同的第一实例之间进行访问,而禁止不同用户定义的第一实例之间进行访问。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
在一个具体的例子中,用户为了创建具有基于RoCE的RDMA通信功能的第一实例,可通过产品的对外服务的API(application program interface,应用程序接口)或者web控制台创建实例集群的数据结构,实例管控服务返回实例集群的标识信息,用户进一步使用该标识信息选择对应的弹性计算规格族的规格,并根据选择的弹性计算规格族的规格调用API创建具体的实例。实例管控服务根据创建的具体实例向RDMA管控服务请求为该创建的具体实例分配地址,请求携带的参数可包括实例的标识信息。RDMA管控服务根据请求携带的实例的标识信息,查询实例的网口与交换机的对应连接关系,并调用DHCP(Dynamic Host Configuration Protocol,动态主机设置协议)服务为实例的网口分配地址。一般地,为了可靠性,实例的网口对应的两个端口有可能会绑定,因此可根据实际情况分配1个地址或者两个地址。其中,DHCP服务可理解为IP地址分配服务。同时,由于RDMA管控服务在部署阶段已存有所有实例的RDMA网口与DCB交换机的对应连接关系,因此,RDMA管控服务可基于请求携带的实例的标识信息,查询用户定义的实例的RDMA网口与DCB交换机的对应连接关系,并基于用户定义的实例的RDMA网口与DCB交换机的对应连接关系,以及地址分配请求携带的用户的标识信息,为该用户定义的实例创建一个访问控制列表。该访问控制列表通过作用于该用户定义的所有实例的RDMA网口对应连接的DCB交换机上,并通过交换机管控服务配置到各个DCB交换机上,使得同一个用户定义的所有实例的RDMA网口能彼此连通。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
在步骤S103中,所述RDMA管控服务将所述访问控制列表发送至交换机管控服务,使得所述交换机管控服务为所述交换机配置所述访问控制列表。
在本申请实施例中,所述交换机管控服务可理解为用于管控基于RoCE的交换机的服务。可以使用进程、应用、虚拟机或者服务器来实现所述交换机管控服务。所述交换机可为DCB(Data Center Bridge,数据中心桥)交换机。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
在一些可选实施例中,所述RDMA管控服务将所述访问控制列表发送至交换机管控服务之后,所述方法还包括:所述RDMA管控服务向所述实例管控服务返回所述地址分配服务为所述第一实例分配的地址段,使得所述实例管控服务启动所述第一实例从镜像服务获取与所述第一实例的规格匹配的镜像文件,并基于所述镜像文件,配置所述地址分配服务为所述第一实例分配的地址段。其中,所述镜像服务可理解为用于存储镜像文件的服务。可以使用进程、应用、虚拟机或者服务器来实现所述镜像服务。籍此,通过向实例管控服务返回地址分配服务为第一实例分配的地址段,能够使得实例管控服务启动第一实例配置分配的地址段。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
在一个具体的例子中,交换机管控服务为DCB交换机配置好访问控制列表之后,RDMA管控服务向实例管控服务返回地址分配服务为第一实例分配的地址。实例管控服务启动该实例并指定到相应的镜像服务中获取针对该实例的规格的镜像文件。镜像文件被传输到对应的实例并被执行完成之后,该实例开始配置实例管控服务为该实例申请的地址,并配置在实例的RDMA网口。用户开始使用该具有基于RoCE的RDMA通信功能的实例。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
在一些可选实施例中,所述方法还包括:所述RDMA管控服务接收实例管控服务基于用户发送的第一实例释放请求发送的第二实例释放请求;所述RDMA管控服务基于所述第二实例释放请求,回收所述第二实例释放请求携带的实例标识信息对应的待释放实例的地址,并通过交换机管控服务配置与所述待释放实例连接的所述交换机,使得与所述待释放实例连接的所述交换机的网口与其它网口不连通;所述RDMA管控服务向所述实例管控服务返回所述第二实例释放请求所请求的所述待释放实例的释放结果,使得所述实例管控服务将所述待释放实例返回库存,并向用户返回释放成功信息。籍此,通过接收到的第二实例释放请求,能够释放用户请求释放的实例。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
在一个具体的例子中,用户通过API或者控制台向实例管控服务发送实例释放请求。实例管控服务接收到请求,并向RDMA管控服务请求释放实例。RDMA管控服务回收实例的RDMA网口的地址,并通过交换机管控服务配置DCB交换机,将该实例的RDMA网口对应连接的DCB交换机配置为与其它网口不连通,并将实例释放结果返回给实例管控服务。实例管控服务继续释放其他的与该实例有关的资源,并将该实例返回库存,并向用户返回实例释放成功的信息。可以理解的是,以上描述仅为示例性的,本申请实施 例对此不做任何限定。
在一个具体的例子中,当用户通过API或者控制台创建的实例为裸金属实例时,数据访问流程可结合如图1B所示的数据访问系统进行详细说明。首先,对如图1B所示的数据访问系统的结构进行详细介绍。裸金属实例的适配器可实现裸金属实例与弹性计算管控的对接,其中还有两个双上联的网口连接以太网交换机,同时还有管理通道连接到机器部署管控服务上。另外,该裸金属实例还具有两个基于增强型以太网的RDMA网口,双上联连接到DCB交换机上,同时DCB交换机进一步双上联连接到DCB汇聚交换机上,以避免单点故障。同时,数据访问系统存在高可用的机器部署管控服务,通过管理通道连接到裸金属实例上和RDMA管控服务上。RDMA管控服务亦为高可用配置,以避免单台服务器故障引起系统不可用,其与机器部署管控服务连接并且和交换机管控服务连接控制DCB交换机的配置。此外,数据访问系统还包含弹性裸金属ECS(Elastic Compute Service,弹性计算服务)生产管控服务,它通过对外服务API或web控制台向社会公众提供弹性计算服务。其次,对结合如图1B所示的数据访问系统的数据访问流程进行详细介绍。具体地,包括部署阶段、用户使用阶段,以及用户销毁阶段。
其中,部署阶段具体如下:机器部署管控服务通过管理通道控制裸金属实例的适配器,从指定的部署镜像存储服务下载部署镜像文件到裸金属实例。具体地,部署镜像文件可以通过管理通道或者部署镜像存储服务到以太网交换机的路径到达裸金属实例。然后,机器部署管控服务通过管理通道再控制裸金属实例的适配器启动到达裸金属实例的部署镜像文件,使得裸金属实例进行相关的部署。具体地,裸金属实例通过控制RDMA网口的两个端口(port-a和port-b),分别发送携带有该端口信息的LLDP组播报文到DCB交换机,使得该LLDP组播报文被发送至RDMA管控服务。RDMA管控服务收到该LLDP组播报文之后,向机器部署管控服务发送查询请求,以查询裸金属实例的部署信息。机器部署管控服务向RDMA管控服务返回裸金属实例的部署信息。然后,RDMA管控服务可根据裸金属实例的部署信息建立以下的对应关系:裸金属实例的RDMA网口与DCB交换机的对应连接关系。此外,RDMA管控服务将所述对应连接关系存入到对应的关系表中。
其中,用户使用阶段具体如下:用户为了创建具有基于RoCE的RDMA通信功能的裸金属实例,可通过产品的对外服务的API(application program interface,应用程序接口)或者web控制台创建裸金属实例集群的数据结构,裸金属ECS实例管控服务返回裸金属实例集群的标识信息,用户进一步使用该标识信息选择对应的弹性计算规格族的规 格,并根据选择的弹性计算规格族的规格调用API创建具体的裸金属实例。裸金属ECS实例管控服务根据创建的具体的裸金属实例向RDMA管控服务请求为该创建的具体的裸金属实例分配地址,请求携带的参数可包括裸金属实例的标识信息和用户的标识信息。RDMA管控服务根据请求携带的裸金属实例的标识信息,查询裸金属实例的网口与DCB交换机的端口的对应连接关系,并调用DHCP(Dynamic Host Configuration Protocol,动态主机设置协议)服务为裸金属实例的网口分配地址。一般地,为了可靠性,裸金属实例的网口对应的两个端口有可能会绑定,因此可根据实际情况分配1个地址或者两个地址。同时,由于RDMA管控服务在部署阶段已存有裸金属实例的RDMA网口与DCB交换机的对应连接关系,因此,RDMA管控服务可基于用户定义的裸金属实例的标识信息,查询用户定义的裸金属实例的RDMA网口与DCB交换机的对应连接关系,并基于用户定义的裸金属实例的RDMA网口与DCB交换机的对应连接关系,以及地址分配请求携带的用户的标识信息,为该用户定义的裸金属实例创建一个访问控制列表。该访问控制列表通过作用于该用户定义的所有裸金属实例的RDMA网口对应连接的DCB交换机上,并通过交换机管控服务配置到各个DCB交换机上,使得同一个用户定义的所有裸金属实例的RDMA网口能彼此连通。交换机管控服务为DCB交换机配置好访问控制列表之后,RDMA管控服务向裸金属ECS实例管控服务返回地址分配服务为裸金属实例的RDMA网口分配的地址。裸金属ECS实例管控服务启动该裸金属实例并指定到相应的镜像服务中获取针对该裸金属实例的规格的镜像文件。镜像文件被传输到对应的裸金属实例并被执行完成之后,该裸金属实例开始配置裸金属ECS实例管控服务为该裸金属实例申请的IP地址,并配置在裸金属实例的RDMA网口。用户开始使用该具有基于RoCE的RDMA通信功能的裸金属实例。
其中,用户销毁阶段具体如下:用户通过API或者控制台向ECS实例管控服务发送裸金属实例释放请求。ECS实例管控服务接收到请求,并向RDMA管控服务请求释放裸金属实例,RDMA管控服务回收裸金属实例的RDMA网口的地址,并通过交换机管控服务配置DCB交换机,将该裸金属实例的RDMA网口对应连接的DCB交换机配置为与其它网口不连通,并将裸金属实例释放结果返回给ECS实例管控服务。ECS实例管控服务继续释放其他的与该裸金属实例有关的资源,并将裸金属实例返回库存,并向用户返回裸金属实例释放成功的信息。其中,所述裸金属实例可理解为仅有一组相应的CPU、内存、系统盘和运行的操作系统配置的服务器。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
通过本申请实施例提供的数据访问方法,RDMA管控服务基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为所述第一实例分配地址段,并基于为所述第一实例分配的所述地址段,构建访问控制列表,所述访问控制列表用于控制所述用户定义的不同的第一实例之间进行访问,再将所述访问控制列表发送至交换机管控服务,使得交换机管控服务为交换机配置访问控制列表,与现有的其它方式相比,通过为交换机配置构建得到的访问控制列表,能够有效控制同一用户定义的不同实例之间进行访问,从而有效解决了不同用户访问RDMA网络节点的访问隔离的问题。
本实施例的数据访问方法可以由任意适当的具有数据处理能力的设备执行,包括但不限于:摄像头、终端、移动终端、PC机、服务器、车载设备、娱乐设备、广告设备、个人数码助理(PDA)、平板电脑、笔记本电脑、掌上游戏机、智能眼镜、智能手表、可穿戴设备、虚拟显示设备或显示增强设备(如Google Glass、Oculus Rift、Hololens、Gear VR)等。
参照图2A,示出了本申请实施例二的数据访问方法的步骤流程图。
具体地,本实施例的数据访问方法包括以下步骤:
在步骤S201中,RDMA管控服务基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为所述第一实例分配地址段。
由于该步骤S201与上述步骤S101类似,在此不再赘述。
在步骤S202中,所述RDMA管控服务接收实例管控服务基于所述第一实例发送的地址分配请求。
在本实施例中,所述地址分配请求携带的信息包括以下中的至少一者:所述用户的标识信息、所述用户定义的实例集群的标识信息,以及实例的标识信息。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
在步骤S203中,所述RDMA管控服务基于所述地址分配请求携带的所述第一实例所属的集群的标识信息,及为所述第一实例分配的所述地址段,构建所述访问控制列表。
在本实施例中,所述访问控制列表用于控制属于同一集群的不同的第一实例之间进行访问。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
在一个具体的例子中,在构建访问控制列表时,所述RDMA管控服务基于所述地址分配请求携带的所述第一实例所属的集群的标识信息,对分配的所述地址段包括的用户定义的不同的第一实例的地址执行筛选操作,以获得属于同一集群的不同的第一实例的 地址,并基于属于同一集群的不同的第一实例的地址,构建访问控制列表,使得同一用户定义的属于同一集群的不同的第一实例之间进行访问。具体地,允许同一用户定义的属于同一集群的不同的第一实例之间进行访问,而禁止不同用户定义的第一实例之间进行访问,以及禁止同一用户定义的属于不同集群的第一实例之间进行访问。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
在步骤S204中,所述RDMA管控服务将所述访问控制列表发送至交换机管控服务,使得所述交换机管控服务为所述交换机配置所述访问控制列表。
由于该步骤S204与上述步骤S103类似,在此不再赘述。
在一个具体的例子中,当用户通过API或者控制台创建的实例为虚拟机实例时,数据访问流程可结合如图2B所示的数据访问系统进行详细说明。由于如图2B所示的数据访问系统的结构与如图1B所示的数据访问系统的结构类似,在此不再赘述。由于结合如图2B所示的数据访问系统的数据访问流程与结合如图1B所示的数据访问系统的数据访问流程大致类似,在此不再赘述。虚拟机实例的数据访问流程与裸金属实例的数据访问流程的区别在于,虚拟机实例运行虚拟化监视器(virtual machine monitor或hypervisor)。此外,在创建虚拟机实例时,虚拟机实例的基于增强型以太网的RDMA网口直通给虚拟机实例的虚拟机,并将虚拟机实例的基于增强型以太网的RDMA网口配置在虚拟机实例的虚拟机上。直通方式包括但不限于PF(physical function)直通或者使用SRIOV技术使用VF(virtual function)直通或者其他模拟方案。所述虚拟机实例可理解为ECS(Elastic Compute Service,弹性计算服务)产品最核心的部分,由相应的虚拟CPU和虚拟内存配置的服务器。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
通过本申请实施例提供的数据访问方法,RDMA管控服务基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为所述第一实例分配地址段,并接收实例管控服务基于所述第一实例发送的地址分配请求,再基于地址分配请求携带的用户定义的第一实例所属的集群的标识信息,及为第一实例分配的地址段,构建访问控制列表,所述访问控制列表用于控制属于同一集群的不同的第一实例之间进行访问,再将所述访问控制列表发送至交换机管控服务,使得交换机管控服务为交换机配置所述访问控制列表,与现有的其它方式相比,通过为交换机配置构建得到的访问控制列表,能够有效控制同一集群的不同的第一实例之间进行访问,从而有效解决了同一用户的不同实例集群之间访问RDMA网络节点的访问隔离的问题。
本实施例的数据访问方法可以由任意适当的具有数据处理能力的设备执行,包括但不限于:摄像头、终端、移动终端、PC机、服务器、车载设备、娱乐设备、广告设备、个人数码助理(PDA)、平板电脑、笔记本电脑、掌上游戏机、智能眼镜、智能手表、可穿戴设备、虚拟显示设备或显示增强设备(如Google Glass、Oculus Rift、Hololens、Gear VR)等。
参照图3A,示出了本申请实施例三中数据访问系统的结构示意图。
本实施例提供的数据访问系统包括:RDMA管控服务301,用于基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为所述第一实例分配地址段,并基于为所述第一实例分配的所述地址段,构建访问控制列表,所述访问控制列表用于控制所述用户定义的不同的第一实例之间进行访问,再将所述访问控制列表发送至交换机管控服务;所述交换机管控服务302,用于根据接收到的所述访问控制列表,为所述交换机配置所述访问控制列表。
在一些可选实施例中,所述第一实例包括适配器,并且所述适配器集成有网口。其中,所述网口为基于增强型以太网的RDMA网口。籍此,通过将实例的基于增强型以太网的RDMA网口集成于实例的适配器,能够省掉与实例连接的两个以太网交换机。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
在一个具体的例子中,当用户通过API或者控制台创建的实例为裸金属实例时,如图3B所示,裸金属实例的适配器集成有裸金属实例的基于增强型以太网的RDMA网口,这样便可省去两个上联的以太网交换机,裸金属实例的基于增强型以太网的RDMA网口既作为基于增强型以太网的RDMA的传输通道,同时又作为普通以太网的传输通道。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
在一个具体的例子中,当用户通过API或者控制台创建的实例为虚拟机实例时,如图3C所示,虚拟机实例的适配器集成有虚拟机实例的基于增强型以太网的RDMA网口,适配器集成的RDMA网口直通给虚拟机实例的虚拟机。这样便可省去两个上联的以太网交换机,虚拟机实例的基于增强型以太网的RDMA网口既作为基于增强型以太网的RDMA的传输通道,同时又作为普通以太网的传输通道。可以理解的是,以上描述仅为示例性的,本申请实施例对此不做任何限定。
本实施例的数据访问系统用于实现前述多个方法实施例中相应的数据访问方法,并具有相应的方法实施例的有益效果,在此不再赘述。
参照图4,示出了本申请实施例四中数据访问装置的结构示意图。
本实施例的数据访问装置包括:分配模块401,用于基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为所述第一实例分配地址段;构建模块402,用于基于为所述第一实例分配的所述地址段,构建访问控制列表,所述访问控制列表用于控制所述用户定义的不同的第一实例之间进行访问;第一发送模块403,用于将所述访问控制列表发送至交换机管控服务,使得所述交换机管控服务为所述交换机配置所述访问控制列表。
本实施例的数据访问装置用于实现前述多个方法实施例中相应的数据访问方法,并具有相应的方法实施例的有益效果,在此不再赘述。
参照图5,示出了本申请实施例五中数据访问装置的结构示意图。
本实施例的数据访问装置包括:分配模块505,用于基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为所述第一实例分配地址段;构建模块508,用于基于为所述第一实例分配的所述地址段,构建访问控制列表,所述访问控制列表用于控制所述用户定义的不同的第一实例之间进行访问;第一发送模块509,用于将所述访问控制列表发送至交换机管控服务,使得所述交换机管控服务为所述交换机配置所述访问控制列表。
可选地,所述分配模块505之前,所述装置还包括:第一接收模块501,用于接收第二实例通过自身的网口发送的携带有所述网口的信息的组播报文;第二发送模块502,用于基于所述组播报文中携带的所述网口的信息,向机器部署管控服务发送查询请求,以查询所述第二实例的部署信息;确定模块503,用于接收所述机器部署管控服务基于所述查询请求返回的所述部署信息,并基于所述部署信息,确定所述第二实例与所述交换机的对应连接关系。
可选地,所述装置还包括:存储模块504,用于将所述第二实例与所述交换机的对应连接关系存储至关系表中。
可选地,所述装置还包括:第二接收模块506,用于接收实例管控服务基于所述第一实例发送的地址分配请求;查询模块507,用于基于所述地址分配请求,查询所述第一实例与所述交换机的对应连接关系。
可选地,所述分配模块505,具体用于:基于所述地址分配请求携带的所述用户信 息,以及查询得到的所述第一实例与所述交换机的对应连接关系,调用地址分配服务为所述第一实例分配地址段。
可选地,所述查询模块507,具体用于:基于所述地址分配请求携带的所述第一实例的标识信息,查询存储有所述第二实例与所述交换机的对应连接关系的关系表,以获得所述第一实例与所述交换机的对应连接关系。
可选地,所述构建模块508,具体用于:基于所述地址分配请求携带的所述第一实例所属的集群的标识信息,及为所述第一实例分配的所述地址段,构建所述访问控制列表,所述访问控制列表用于控制属于同一集群的不同的第一实例之间进行访问。
可选地,所述第一发送模块509之后,所述装置还包括:第一返回模块510,用于向所述实例管控服务返回所述地址分配服务为所述第一实例分配的地址段,使得所述实例管控服务启动所述第一实例从镜像服务获取与所述第一实例的规格匹配的镜像文件,并基于所述镜像文件,配置所述地址分配服务为所述第一实例分配的地址段。
可选地,所述装置还包括:第二接收模块511,用于接收实例管控服务基于用户发送的第一实例释放请求发送的第二实例释放请求;释放模块512,用于基于所述第二实例释放请求,回收所述第二实例释放请求携带的实例标识信息对应的待释放实例的地址,并通过交换机管控服务配置与所述待释放实例连接的所述交换机,使得与所述待释放实例连接的所述交换机的网口与其它网口不连通;第二返回模块513,用于向所述实例管控服务返回所述第二实例释放请求所请求的所述待释放实例的释放结果,使得所述实例管控服务将所述待释放实例返回库存,并向用户返回释放成功信息。
本实施例的数据访问装置用于实现前述多个方法实施例中相应的数据访问方法,并具有相应的方法实施例的有益效果,在此不再赘述。
图6为本申请实施例六中电子设备的结构示意图;该电子设备可以包括:
一个或多个处理器601;
计算机可读介质602,可以配置为存储一个或多个程序,
当所述一个或多个程序被所述一个或多个处理器执行,使得所述一个或多个处理器实现如上述实施例一或实施例二所述的数据访问方法。
图7为本申请实施例七中电子设备的硬件结构;如图7所示,该电子设备的硬件结构可以包括:处理器701,通信接口702,计算机可读介质703和通信总线704;
其中处理器701、通信接口702、计算机可读介质703通过通信总线704完成相互间的通信;
可选地,通信接口702可以为通信模块的接口,如GSM模块的接口;
其中,处理器701具体可以配置为:RDMA管控服务基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为所述第一实例分配地址段;所述RDMA管控服务基于为所述第一实例分配的所述地址段,构建访问控制列表,所述访问控制列表用于控制所述用户定义的不同的第一实例之间进行访问;所述RDMA管控服务将所述访问控制列表发送至交换机管控服务,使得所述交换机管控服务为所述交换机配置所述访问控制列表。
处理器701可以是通用处理器,包括中央处理器(Central Processing Unit,简称CPU)、网络处理器(Network Processor,简称NP)等;还可以是数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
计算机可读介质703可以是,但不限于,随机存取存储介质(Random Access Memory,RAM),只读存储介质(Read Only Memory,ROM),可编程只读存储介质(Programmable Read-Only Memory,PROM),可擦除只读存储介质(Erasable Programmable Read-Only Memory,EPROM),电可擦除只读存储介质(Electric Erasable Programmable Read-Only Memory,EEPROM)等。
特别地,根据本公开的实施例,上文参考流程图描述的过程可以被实现为计算机软件程序。例如,本公开的实施例包括一种计算机程序产品,其包括承载在计算机可读介质上的计算机程序,该计算机程序包含配置为执行流程图所示的方法的程序代码。在这样的实施例中,该计算机程序可以通过通信部分从网络上被下载和安装,和/或从可拆卸介质被安装。在该计算机程序被中央处理单元(CPU)执行时,执行本申请的方法中限定的上述功能。需要说明的是,本申请所述的计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质或者是上述两者的任意组合。计算机可读介质例如可以但不限于是电、磁、光、电磁、红外线、或半导体的系统、装置或器件,或者任意以上的组合。计算机可读存储介质的更具体的例子可以包括但不限于:具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机访问存储介质(RAM)、只读存储介质(ROM)、可擦式可编程只读存储介质(EPROM或闪存)、光纤、便携式紧凑磁盘只读存储介质 (CD-ROM)、光存储介质件、磁存储介质件、或者上述的任意合适的组合。在本申请中,计算机可读存储介质可以是任何包含或存储程序的有形介质,该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。而在本申请中,计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号,其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式,包括但不限于电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的任何计算机可读介质,该计算机可读介质可以发送、传播或者传输配置为由指令执行系统、装置或者器件使用或者与其结合使用的程序。计算机可读介质上包含的程序代码可以用任何适当的介质传输,包括但不限于:无线、电线、光缆、RF等等,或者上述的任意合适的组合。
可以以一种或多种程序设计语言或其组合来编写配置为执行本申请的操作的计算机程序代码,所述程序设计语言包括面向对象的程序设计语言—诸如Java、Smalltalk、C++,还包括常规的过程式程序设计语言—诸如”C”语言或类似的程序设计语言。程序代码可以完全地在用户计算机上执行、部分地在用户计算机上执行、作为一个独立的软件包执行、部分在用户计算机上部分在远程计算机上执行、或者完全在远程计算机或服务器上执行。在涉及远程计算机的情形中,远程计算机可以通过任意种类的网络:包括局域网(LAN)或广域网(WAN)—连接到用户计算机,或者,可以连接到外部计算机(例如利用因特网服务提供商来通过因特网连接)。
附图中的流程图和框图,图示了按照本申请各种实施例的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上,流程图或框图中的每个方框可以代表一个模块、程序段、或代码的一部分,该模块、程序段、或代码的一部分包含一个或多个配置为实现规定的逻辑功能的可执行指令。上述具体实施例中有特定先后关系,但这些先后关系只是示例性的,在具体实现的时候,这些步骤可能会更少、更多或执行顺序有调整。即在有些作为替换的实现中,方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如,两个接连地表示的方框实际上可以基本并行地执行,它们有时也可以按相反的顺序执行,这依所涉及的功能而定。也要注意的是,框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合,可以用执行规定的功能或操作的专用的基于硬件的系统来实现,或者可以用专用硬件与计算机指令的组合来实现。
描述于本申请实施例中所涉及到的模块可以通过软件的方式实现,也可以通过硬件的方式来实现。所描述的模块也可以设置在处理器中,例如,可以描述为:一种处理器 包括分配模块、构建模块和第一发送模块。其中,这些模块的名称在某种情况下并不构成对该模块本身的限定,例如,分配模块还可以被描述为“基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为所述第一实例分配地址段的模块”。
作为另一方面,本申请还提供了一种计算机可读介质,其上存储有计算机程序,该程序被处理器执行时实现如上述实施例一或实施例二所描述的数据访问方法。
作为另一方面,本申请还提供了一种计算机可读介质,该计算机可读介质可以是上述实施例中描述的装置中所包含的;也可以是单独存在,而未装配入该装置中。上述计算机可读介质承载有一个或者多个程序,当上述一个或者多个程序被该装置执行时,使得该装置:RDMA管控服务基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为所述第一实例分配地址段;所述RDMA管控服务基于为所述第一实例分配的所述地址段,构建访问控制列表,所述访问控制列表用于控制所述用户定义的不同的第一实例之间进行访问;所述RDMA管控服务将所述访问控制列表发送至交换机管控服务,使得所述交换机管控服务为所述交换机配置所述访问控制列表。
在本公开的各种实施方式中所使用的表述“第一”、“第二”、“所述第一”或“所述第二”可修饰各种部件而与顺序和/或重要性无关,但是这些表述不限制相应部件。以上表述仅配置为将元件与其它元件区分开的目的。例如,第一用户设备和第二用户设备表示不同的用户设备,虽然两者均是用户设备。例如,在不背离本公开的范围的前提下,第一元件可称作第二元件,类似地,第二元件可称作第一元件。
当一个元件(例如,第一元件)称为与另一元件(例如,第二元件)“(可操作地或可通信地)联接”或“(可操作地或可通信地)联接至”另一元件(例如,第二元件)或“连接至”另一元件(例如,第二元件)时,应理解为该一个元件直接连接至该另一元件或者该一个元件经由又一个元件(例如,第三元件)间接连接至该另一个元件。相反,可理解,当元件(例如,第一元件)称为“直接连接”或“直接联接”至另一元件(第二元件)时,则没有元件(例如,第三元件)插入在这两者之间。
以上描述仅为本申请的较佳实施例以及对所运用技术原理的说明。本领域技术人员应当理解,本申请中所涉及的发明范围,并不限于上述技术特征的特定组合而成的技术方案,同时也应涵盖在不脱离上述发明构思的情况下,由上述技术特征或其等同特征进行任意组合而形成的其它技术方案。例如上述特征与本申请中公开的(但不限于)具有类似功能的技术特征进行互相替换而形成的技术方案。

Claims (22)

  1. 一种数据访问方法,其特征在于,所述方法包括:
    RDMA管控服务基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为所述第一实例分配地址段;
    所述RDMA管控服务基于为所述第一实例分配的所述地址段,构建访问控制列表,所述访问控制列表用于控制所述用户定义的不同的第一实例之间进行访问;
    所述RDMA管控服务将所述访问控制列表发送至交换机管控服务,使得所述交换机管控服务为所述交换机配置所述访问控制列表。
  2. 根据权利要求1所述的方法,其特征在于,所述RDMA管控服务为所述第一实例分配地址段之前,所述方法还包括:
    所述RDMA管控服务接收第二实例通过自身的网口发送的携带有所述网口的信息的组播报文;
    所述RDMA管控服务基于所述组播报文中携带的所述网口的信息,向机器部署管控服务发送查询请求,以查询所述第二实例的部署信息;
    所述RDMA管控服务接收所述机器部署管控服务基于所述查询请求返回的所述部署信息,并基于所述部署信息,确定所述第二实例与所述交换机的对应连接关系。
  3. 根据权利要求2所述的方法,其特征在于,所述方法还包括:
    所述RDMA管控服务将所述第二实例与所述交换机的对应连接关系存储至关系表中。
  4. 根据权利要求3所述的方法,其特征在于,所述方法还包括:
    所述RDMA管控服务接收实例管控服务基于所述第一实例发送的地址分配请求;
    所述RDMA管控服务基于所述地址分配请求,查询所述第一实例与所述交换机的对应连接关系。
  5. 根据权利要求4所述的方法,其特征在于,所述RDMA管控服务基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为所述第一实例分配地址段,包括:
    所述RDMA管控服务基于所述地址分配请求携带的所述用户信息,以及查询得到的所述第一实例与所述交换机的对应连接关系,调用地址分配服务为所述第一实例分配地址段。
  6. 根据权利要求4所述的方法,其特征在于,所述RDMA管控服务基于所述地址分配请求,查询所述第一实例与所述交换机的对应连接关系,包括:
    所述RDMA管控服务基于所述地址分配请求携带的所述第一实例的标识信息,查询存储有所述第二实例与所述交换机的对应连接关系的关系表,以获得所述第一实例与所述交换机的对应连接关系。
  7. 根据权利要求4所述的方法,其特征在于,所述RDMA管控服务基于为所述第一实例分配的所述地址段,构建访问控制列表,包括:
    所述RDMA管控服务基于所述地址分配请求携带的所述第一实例所属的集群的标识信息,及为所述第一实例分配的所述地址段,构建所述访问控制列表,所述访问控制列表用于控制属于同一集群的不同的第一实例之间进行访问。
  8. 根据权利要求4所述的方法,其特征在于,所述RDMA管控服务将所述访问控制列表发送至交换机管控服务之后,所述方法还包括:
    所述RDMA管控服务向所述实例管控服务返回所述地址分配服务为所述第一实例分配的地址段,使得所述实例管控服务启动所述第一实例从镜像服务获取与所述第一实例的规格匹配的镜像文件,并基于所述镜像文件,配置所述地址分配服务为所述第一实例分配的地址段。
  9. 根据权利要求1所述的方法,其特征在于,所述方法还包括:
    所述RDMA管控服务接收实例管控服务基于用户发送的第一实例释放请求发送的第二实例释放请求;
    所述RDMA管控服务基于所述第二实例释放请求,回收所述第二实例释放请求携带的实例标识信息对应的待释放实例的地址,并通过交换机管控服务配置与所述待释放实例连接的所述交换机,使得与所述待释放实例连接的所述交换机的网口与其它网口不连通;
    所述RDMA管控服务向所述实例管控服务返回所述第二实例释放请求所请求的所述待释放实例的释放结果,使得所述实例管控服务将所述待释放实例返回库存,并向用户返回释放成功信息。
  10. 一种数据访问装置,其特征在于,所述装置包括:
    分配模块,用于基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为所述第一实例分配地址段;
    构建模块,用于基于为所述第一实例分配的所述地址段,构建访问控制列表,所述访问控制列表用于控制所述用户定义的不同的第一实例之间进行访问;
    第一发送模块,用于将所述访问控制列表发送至交换机管控服务,使得所述交换机 管控服务为所述交换机配置所述访问控制列表。
  11. 根据权利要求10所述的装置,其特征在于,所述分配模块之前,所述装置还包括:
    第一接收模块,用于接收第二实例通过自身的网口发送的携带有所述网口的信息的组播报文;
    第二发送模块,用于基于所述组播报文中携带的所述网口的信息,向机器部署管控服务发送查询请求,以查询所述第二实例的部署信息;
    确定模块,用于接收所述机器部署管控服务基于所述查询请求返回的所述部署信息,并基于所述部署信息,确定所述第二实例与所述交换机的对应连接关系。
  12. 根据权利要求11所述的装置,其特征在于,所述装置还包括:
    存储模块,用于将所述第二实例与所述交换机的对应连接关系存储至关系表中。
  13. 根据权利要求12所述的装置,其特征在于,所述装置还包括:
    第二接收模块,用于接收实例管控服务基于所述第一实例发送的地址分配请求;
    查询模块,用于基于所述地址分配请求,查询所述第一实例与所述交换机的对应连接关系。
  14. 根据权利要求13所述的装置,其特征在于,所述分配模块,具体用于:
    基于所述地址分配请求携带的所述用户信息,以及查询得到的所述第一实例与所述交换机的对应连接关系,调用地址分配服务为所述第一实例分配地址段。
  15. 根据权利要求13所述的装置,其特征在于,所述查询模块,具体用于:
    基于所述地址分配请求携带的所述第一实例的标识信息,查询存储有所述第二实例与所述交换机的对应连接关系的关系表,以获得所述第一实例与所述交换机的对应连接关系。
  16. 根据权利要求13所述的装置,其特征在于,所述构建模块,具体用于:
    基于所述地址分配请求携带的所述第一实例所属的集群的标识信息,及为所述第一实例分配的所述地址段,构建所述访问控制列表,所述访问控制列表用于控制属于同一集群的不同的第一实例之间进行访问。
  17. 根据权利要求13所述的装置,其特征在于,所述第一发送模块之后,所述装置还包括:
    第一返回模块,用于向所述实例管控服务返回所述地址分配服务为所述第一实例分配的地址段,使得所述实例管控服务启动所述第一实例从镜像服务获取与所述第一实例 的规格匹配的镜像文件,并基于所述镜像文件,配置所述地址分配服务为所述第一实例分配的地址段。
  18. 根据权利要求10所述的装置,其特征在于,所述装置还包括:
    第二接收模块,用于接收实例管控服务基于用户发送的第一实例释放请求发送的第二实例释放请求;
    释放模块,用于基于所述第二实例释放请求,回收所述第二实例释放请求携带的实例标识信息对应的待释放实例的地址,并通过交换机管控服务配置与所述待释放实例连接的所述交换机,使得与所述待释放实例连接的所述交换机的网口与其它网口不连通;
    第二返回模块,用于向所述实例管控服务返回所述第二实例释放请求所请求的所述待释放实例的释放结果,使得所述实例管控服务将所述待释放实例返回库存,并向用户返回释放成功信息。
  19. 一种数据访问系统,其特征在于,所述系统包括:
    RDMA管控服务,用于基于用户信息,以及用户定义的第一实例与交换机的对应连接关系,为所述第一实例分配地址段,并基于为所述第一实例分配的所述地址段,构建访问控制列表,所述访问控制列表用于控制所述用户定义的不同的第一实例之间进行访问,再将所述访问控制列表发送至交换机管控服务;
    所述交换机管控服务,用于根据接收到的所述访问控制列表,为所述交换机配置所述访问控制列表。
  20. 根据权利要求19所述的系统,其特征在于,所述第一实例包括适配器,并且所述适配器集成有网口,其中,所述网口为基于增强型以太网的RDMA网口。
  21. 一种电子设备,包括:
    一个或多个处理器;
    计算机可读介质,配置为存储一个或多个程序,
    当所述一个或多个程序被所述一个或多个处理器执行,使得所述一个或多个处理器实现如权利要求1-9中任意一项权利要求所述的数据访问方法。
  22. 一种计算机可读介质,其上存储有计算机程序,其特征在于,该程序被处理器执行时实现如权利要求1-9中任意一项权利要求所述的数据访问方法。
PCT/CN2020/116466 2019-09-25 2020-09-21 数据访问方法、装置、系统、电子设备及计算机可读介质 WO2021057650A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US17/763,609 US11863520B2 (en) 2019-09-25 2020-09-21 Data access methods and systems
EP20867551.2A EP4037276A4 (en) 2019-09-25 2020-09-21 DATA ACCESS METHOD, DEVICE, SYSTEM, ELECTRONIC DEVICE AND COMPUTER READABLE MEDIA

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910912110.8A CN112565158B (zh) 2019-09-25 2019-09-25 数据访问方法、装置、系统、电子设备及计算机可读介质
CN201910912110.8 2019-09-25

Publications (1)

Publication Number Publication Date
WO2021057650A1 true WO2021057650A1 (zh) 2021-04-01

Family

ID=75029336

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/116466 WO2021057650A1 (zh) 2019-09-25 2020-09-21 数据访问方法、装置、系统、电子设备及计算机可读介质

Country Status (4)

Country Link
US (1) US11863520B2 (zh)
EP (1) EP4037276A4 (zh)
CN (1) CN112565158B (zh)
WO (1) WO2021057650A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101056178A (zh) * 2007-05-28 2007-10-17 中兴通讯股份有限公司 一种控制用户网络访问权限的方法和系统
US20140269290A1 (en) * 2013-03-13 2014-09-18 International Business Machines Corporation Metrics and Forwarding Actions on Logical Switch Partitions in a Distributed Network Switch
CN105393239A (zh) * 2013-09-05 2016-03-09 谷歌公司 隔离分布式存储系统的客户端
WO2019055100A1 (en) * 2017-09-14 2019-03-21 Microsoft Technology Licensing, Llc DIRECT ACCESS TO REMOTE MEMORY IN COMPUTER SYSTEMS
CN109656467A (zh) * 2017-10-11 2019-04-19 阿里巴巴集团控股有限公司 云网络的数据传输系统、数据交互方法、装置及电子设备

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1761209A (zh) * 2004-04-27 2006-04-19 微软公司 提供网络隔离的系统和方法
US8589481B2 (en) * 2011-09-14 2013-11-19 Microsoft Corporation Multi tenant access to applications
US9027087B2 (en) * 2013-03-14 2015-05-05 Rackspace Us, Inc. Method and system for identity-based authentication of virtual machines
EP3069462A4 (en) * 2013-11-14 2017-05-03 Intralinks, Inc. Litigation support in cloud-hosted file sharing and collaboration
CN105323282B (zh) * 2014-07-28 2018-12-04 神州数码信息系统有限公司 一种面向多租户的企业应用部署与管理系统
US9723008B2 (en) * 2014-09-09 2017-08-01 Oracle International Corporation System and method for providing an integrated firewall for secure network communication in a multi-tenant environment
US10104017B2 (en) * 2015-05-12 2018-10-16 Jeda Networks, Inc. Methods, systems and apparatus for the virtualization of high performance networks
CN105376303B (zh) * 2015-10-23 2018-11-06 深圳前海达闼云端智能科技有限公司 一种Docker实现系统及其通信方法
US9836397B2 (en) * 2015-11-20 2017-12-05 International Business Machines Corporation Direct memory access of dynamically allocated memory
CN107332812B (zh) * 2016-04-29 2020-07-07 新华三技术有限公司 网络访问控制的实现方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101056178A (zh) * 2007-05-28 2007-10-17 中兴通讯股份有限公司 一种控制用户网络访问权限的方法和系统
US20140269290A1 (en) * 2013-03-13 2014-09-18 International Business Machines Corporation Metrics and Forwarding Actions on Logical Switch Partitions in a Distributed Network Switch
CN105393239A (zh) * 2013-09-05 2016-03-09 谷歌公司 隔离分布式存储系统的客户端
WO2019055100A1 (en) * 2017-09-14 2019-03-21 Microsoft Technology Licensing, Llc DIRECT ACCESS TO REMOTE MEMORY IN COMPUTER SYSTEMS
CN109656467A (zh) * 2017-10-11 2019-04-19 阿里巴巴集团控股有限公司 云网络的数据传输系统、数据交互方法、装置及电子设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4037276A4

Also Published As

Publication number Publication date
US11863520B2 (en) 2024-01-02
CN112565158B (zh) 2022-10-04
EP4037276A4 (en) 2023-04-19
EP4037276A1 (en) 2022-08-03
CN112565158A (zh) 2021-03-26
US20220337548A1 (en) 2022-10-20

Similar Documents

Publication Publication Date Title
US10541877B2 (en) Dynamic reservation protocol for 5G network slicing
CN109561171B (zh) 虚拟私有云服务的配置方法和装置
EP2922238B1 (en) Resource allocation method
US9244817B2 (en) Remote debugging in a cloud computing environment
US9628290B2 (en) Traffic migration acceleration for overlay virtual environments
US9588807B2 (en) Live logical partition migration with stateful offload connections using context extraction and insertion
US8830870B2 (en) Network adapter hardware state migration discovery in a stateful environment
WO2016155394A1 (zh) 一种虚拟网络功能间链路建立方法及装置
JP2019528005A (ja) クラウドコンピューティングシステムにおいて仮想マシンが物理サーバにアクセスするための方法、装置、およびシステム
US9753786B2 (en) Client server communication system
US20170026306A1 (en) Systems and methods for autonomous resource discovery, management, and stitching
US10361970B2 (en) Automated instantiation of wireless virtual private networks
WO2017161562A1 (zh) 网络功能虚拟化环境下应用的管理方法和装置
WO2019100266A1 (zh) 移动边缘主机服务通知方法和装置
JP2016116184A (ja) 網監視装置および仮想ネットワーク管理方法
CN109857464B (zh) 用于平台部署与操作移动操作系统的系统及其方法
US9760412B2 (en) Client server communication system
WO2016101639A1 (zh) 负载均衡器的连接方法、业务的实例化部署方法及装置
WO2023221990A1 (zh) Udp报文的分发方法、设备及可读存储介质
US10592221B2 (en) Parallel distribution of application services to virtual nodes
WO2021057650A1 (zh) 数据访问方法、装置、系统、电子设备及计算机可读介质
KR20170047747A (ko) 화면 압축 서비스 방법 및 그 방법을 수행하는 가상 네트워크 장치
US11909624B2 (en) Communication method, apparatus, device, system, and computer-readable storage medium
JP7212158B2 (ja) プロバイダネットワークサービス拡張
CN113127145B (zh) 信息处理方法、装置以及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20867551

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020867551

Country of ref document: EP

Effective date: 20220425