CN114466011B - Metadata service request method, device, equipment and medium - Google Patents

Abstract

The application discloses a metadata service request method, a device, equipment and a medium, comprising the following steps: and respectively deploying a network-ovn-metadata-agent in each computing node and each network node management network in the cloud platform, creating an ovnmeta network naming space in a service network corresponding to each network node by using the network-ovn-metadata-agent, acquiring a service request message based on metadata service sent by a target host from a preset routing route through the ovnmeta network naming space, forwarding the service request message to the network-ovn-metadata-agent by using preset proxy software in a preset communication mode, and forwarding the service request message to a nova-api by using the network-ovn-metadata-agent so that the nova-api returns metadata based on the service request to the target host. In this way, in the cloud data request process, the invention can enable the cloud host and the cloud physical machine to successfully request the metadata service by deploying the neutron-ovn-metadata-agent in the management network of each computing node and each network node in the cloud platform.

Description

A metadata service request method, device, equipment and medium

technical field

The invention relates to the field of cloud platform distributed services, in particular to a metadata service request method, device, equipment and medium.

Background technique

OpenStack is an open source cloud computing platform management platform project. Nova is a component of OpenStack that provides computing services for cloud platforms, including metadata (metadata) services. The cloud host and cloud physical machine need to request the metadata service to obtain metadata data, but the network between the cloud host, cloud physical machine and nova-api is disconnected. As a result, cloud hosts and cloud physical machines cannot directly access nova-api and request the metadata service to obtain metadata data.

The network solution of the early OpenStack cloud platform adopted a multi-neutron agent architecture: neutron-dhcp-agent is responsible for the dynamic IP allocation of cloud hosts and cloud physical machines; neutron-l3-agent is responsible for three-layer routing and forwarding of cloud hosts and cloud physical machines; neutron-metadata-agent is responsible for forwarding the metadata requests of cloud hosts and cloud physical machines to nova-metadata. At this time, although both the cloud host and the cloud physical machine can request the metadata service, because this architecture is a centralized architecture, when the OpenStack cloud platform cluster becomes larger and larger, performance bottlenecks will occur.

At present, most of the network solutions of the OpenStack cloud platform adopt the ovn architecture, provide dynamic IP allocation and three-layer routing and forwarding functions of cloud hosts and cloud physical machines through the OpenVSwitch flow table, and add neutron-ovn-metadata-agent to the computing nodes , and the network requests of the cloud physical machine are sent on the network nodes, resulting in the metadata request of the cloud physical machine not being able to reach the ovnmeta network namespace of the computing node, and thus unable to request the metadata service and obtain metadata data.

It can be seen from the above that in the process of cloud platform services, how to ensure that both cloud physical machines and cloud hosts can successfully request metadata services is a problem to be solved in this field.

Contents of the invention

In view of this, the purpose of the present invention is to provide a metadata service request method, device, equipment and medium, which can ensure that both the cloud physical machine and the cloud host can successfully request the metadata service. The specific plan is as follows:

In the first aspect, the present application discloses a metadata service request method, including:

Deploy neutron-ovn-metadata-agent in the management network of each computing node and each network node in the cloud platform;

Utilize the neutron-ovn-metadata-agent to create an ovnmeta network namespace in the service network corresponding to each computing node and each network node;

Obtain the service request message based on the metadata service sent by the target host from the preset routing route through the ovnmeta network namespace;

Using preset agent software to forward the service request message to neutron-ovn-metadata-agent through a preset communication method;

Using the neutron-ovn-metadata-agent to forward the service request message to nova-api, so that the nova-api returns metadata based on the service request to the target host.

Optionally, before obtaining the service request message based on the metadata service sent by the target host from the preset routing route through the ovnmeta network namespace, the method further includes:

Create a local port in the ovnmeta network namespace, and set the preset target IP address and the port IP address of the subnet where the target host is located as the IP address of the local port, so that the target host will be routed to the preset The gateway address of the target IP address is set to the IP address of the local port, and after the routing route from the target host to the ovnmeta network namespace is created, the service request based on the metadata service is reported according to the routing route text to send.

Optionally, the sending the service request message based on the metadata service according to the routing route includes:

Encapsulating the destination IP address of the service request message into a preset destination IP address, and encapsulating the destination MAC address into the MAC address of the local port.

Optionally, after obtaining the service request message based on the metadata service sent by the target host from the preset routing route through the ovnmeta network namespace, the method further includes:

Send the message to a preset processing port;

Correspondingly, the use of preset agent software to forward the service request message to neutron-ovn-metadata-agent through a preset communication method further includes:

Use preset proxy software to monitor the preset processing port corresponding to the preset target IP address, so that after listening to the service request message, add a universal unique identification code to the service request message to form the first Encapsulate the message, and forward the first encapsulated message to neutron-ovn-metadata-agent through a preset communication mode.

Forwarding the first encapsulated message to neutron-ovn-metadata-agent through a preset communication mode.

Optionally, using the neutron-ovn-metadata-agent to forward the service request message to nova-api, so that the nova-api returns the metadata based on the service request message to the target host data, including:

Utilize the neutron-ovn-metadata-agent to analyze the first encapsulated message to obtain the UUID, source IP and the service request message, and use the UUID, The source IP obtains the item identification number and the target host identification number, and encapsulates the item identification number and the target host identification number into the service request message to form a second encapsulated message, and the second The encapsulated message is forwarded to nova-api, so that the nova-api returns corresponding metadata to the target host based on the second encapsulated message

Optionally, after using the neutron-ovn-metadata-agent to obtain the project identification number and the target host identification number according to the unique universal identification code and source IP in the service request message, it also includes:

Using the neutron-ovn-metadata-agent to save the item identification number, the target host identification number and the service request message into a preset database.

Optionally, the use of preset agent software to forward the service request message to neutron-ovn-metadata-agent through a preset communication method, including:

Use HAproxy to forward the service request message to neutron-ovn-metadata-agent through unix domian socket.

In a second aspect, the present application discloses a device for requesting a metadata service, including:

The node deployment module is used to respectively deploy neutron-ovn-metadata-agent in the management network of each computing node and each network node in the cloud platform;

A space creation module, for using the neutron-ovn-metadata-agent to create an ovnmeta network namespace in the service network corresponding to each computing node and each network node;

The message acquisition module is used to obtain the service request message based on the metadata service sent by the target host from the preset routing route through the ovnmeta network namespace;

A message forwarding module, configured to forward the service request message to neutron-ovn-metadata-agent through a preset communication mode by using preset agent software;

A data return module, configured to use the neutron-ovn-metadata-agent to forward the service request message to nova-api, so that the nova-api returns metadata based on the service request to the target host.

In a third aspect, the present application discloses an electronic device, comprising:

memory for storing computer programs;

A processor, configured to execute the computer program, so as to implement the aforementioned metadata service request method.

In a fourth aspect, the present application discloses a computer storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the steps of the metadata service request method disclosed above are implemented.

This application first deploys neutron-ovn-metadata-agent respectively in the management network of each computing node and each network node in the cloud platform; Create an ovnmeta network namespace in the business network; obtain the service request message based on the metadata service sent by the target host from the preset routing route through the ovnmeta network namespace; The service request message is forwarded to neutron-ovn-metadata-agent; the service request message is forwarded to nova-api by using the neutron-ovn-metadata-agent, so that the nova-api returns to the target host based on Metadata for the service request. In this way, neutron-ovn-metadata-agent is deployed on each computing node and network node, which not only avoids the performance bottleneck problem of using neutron agent architecture, but also solves the problem of sending data requests on network nodes caused by using ovn architecture The cloud physical machine cannot request the metadata service. On this basis, both the cloud host and the cloud physical machine can successfully request the metadata service.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only It is an embodiment of the present invention, and those skilled in the art can also obtain other drawings according to the provided drawings without creative work.

Fig. 1 is a flow chart of the metadata service request method provided by this application;

FIG. 2 is a flow chart of a specific metadata service request method provided by the present application;

FIG. 3 is a flow chart of a specific metadata service request provided by this application;

FIG. 4 is a schematic structural diagram of a metadata service request device provided by the present application;

FIG. 5 is a structural diagram of an electronic device provided by the present application.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

In the prior art, in the network solution of the cloud platform, performance bottlenecks will occur when using the neutron agent architecture, and the use of the ovn architecture will lead to the problem that the cloud physical machine that sends the data request at the network node cannot request the metadata service. In this application, corresponding deployment is performed on each computing node and network node, so that both the cloud host and the cloud physical machine can successfully request the metadata service.

The embodiment of the present invention discloses a metadata service request method, as described in Fig. 1, the method includes:

Step S11: Deploy neutron-ovn-metadata-agent in the management network of each computing node and each network node in the cloud platform respectively.

In this embodiment, the neutron-ovn-metadata-agent is deployed in both the computing nodes in the cloud platform and the management network in the network nodes.

Step S12: using the neutron-ovn-metadata-agent to create an ovnmeta network namespace in the service network corresponding to each computing node and each network node.

In this embodiment, the neutron-ovn-metadata-agent deployed in the management network is used to create the ovnmeta network namespace in the service network corresponding to the node.

Step S13: Obtain the service request message based on the metadata service sent by the target host from the preset routing route through the ovnmeta network namespace.

In this embodiment, before obtaining the service request message based on the metadata service sent by the target host from the preset routing route through the ovnmeta network namespace, it may also include: creating a local port in the ovnmeta network namespace , and set the preset target IP address and the port IP address of the subnet where the target host is located as the IP address of the local port, so that the target host can set the gateway address routed to the preset target IP address as the The IP address of the local port, and after creating a routing route from the target host to the ovnmeta network namespace, send the service request message based on the metadata service according to the routing route.

It can be understood that the local port (ie, localport port) described in this embodiment is in the ovnmeta network namespace, and is a tap (ie, Test Access Point, optical splitter/splitter) device, and The local port described in this embodiment is a dedicated port set based on the metadata service. When setting the IP address of the local port, the port IP address of the subnet where the target host is located and the preset target IP address are both set as the IP address of the local port, so that the ovnmata network namespace can receive data from the cloud host and cloud physical The metadata of the machine is requested. In this embodiment, the target host includes, but is not limited to, a cloud host working in a computing node service network or a cloud physical machine connected to a network node. The preset target IP address includes but not limited to an IP address of 169.254.169.254.

In this embodiment, because the preset target IP address is not in the subnet where the cloud host and the cloud physical machine are located. If this route is not set, the metadata request sent by the cloud host and cloud physical machine will be sent to the subnet gateway according to the default route, and the metadata service cannot be requested normally. After setting this route, the metadata request sent by the cloud host and cloud physical machine will be sent to the local port according to this route.

In this embodiment, the sending the service request message based on the metadata service according to the routing route may include: encapsulating the destination IP address of the service request message into a preset target IP address, and encapsulating the destination MAC address (ie MediaAccessControl address, media access control address) is encapsulated as the MAC address of the local port.

Because the preset target IP address is not in the same network segment as the cloud host and cloud physical machine, when the cloud host and cloud physical machine send metadata requests, the encapsulated destination MAC address will be encapsulated into the gateway MAC address, that is, the MAC address of the local port. This will cause the metadata request to be sent to the local port when it is forwarded through OVS (that is, OpenVSwitch) on the second layer. After the local port receives the message, it will check that the destination MAC address is the local MAC address, and check that the destination IP address is 169.254. After 169.254 is also the IP address of the machine, it starts to process the data.

Step S14: Using preset agent software to forward the service request message to neutron-ovn-metadata-agent through preset communication mode.

In this embodiment, the use of preset agent software to forward the service request message to neutron-ovn-metadata-agent through a preset communication method may include: using HAproxy to send the service request message through a unix domian socket Forward to neutron-ovn-metadata-agent. The preset proxy software in this embodiment includes but not limited to HAproxy, and the preset communication method in this embodiment includes but not limited to the way of unix domainsocket.

Step S15: Utilize the neutron-ovn-metadata-agent to forward the service request message to nova-api, so that the nova-api returns metadata based on the service request to the target host.

This application first deploys the neutron-ovn-metadata-agent in the management network of each computing node and each network node in the cloud platform, and uses the neutron-ovn-metadata-agent in each computing node and each network node corresponding Create an ovnmeta network namespace in the business network, obtain the service request message based on the metadata service sent by the target host from the preset routing route through the ovnmeta network namespace, and then use the preset proxy software to transfer the service request message based on the metadata service through the preset communication method The service request message is forwarded to neutron-ovn-metadata-agent, and the service request message is forwarded to nova-api by using the neutron-ovn-metadata-agent, so that the nova-api returns to the target host Metadata based on the service request. In this way, neutron-ovn-metadata-agent is deployed on each computing node and network node, which not only avoids the performance bottleneck problem of using neutron agent architecture, but also solves the problem of sending data requests on network nodes caused by using ovn architecture The cloud physical machine cannot request the metadata service. On this basis, both the cloud host and the cloud physical machine can successfully request the metadata service.

FIG. 2 is a flow chart of a specific metadata service request method provided by the embodiment of the present application. Referring to shown in Figure 2, the method includes:

Step S21: Deploy neutron-ovn-metadata-agent in the management network of each computing node and each network node in the cloud platform respectively.

Step S22: Using the neutron-ovn-metadata-agent to create an ovnmeta network namespace in the service network corresponding to each computing node and each network node.

Step S23: Obtain the service request message based on the metadata service sent by the target host from the preset routing route through the ovnmeta network namespace.

Step S24: Send the message to a preset processing port.

In this step, if the preset target IP address is 169.254.169.254, relatively, the preset processing port may be 169.254.169.254:80.

Step S25: Use the default proxy software to monitor the preset processing port corresponding to the preset target IP address, so that after the service request message is monitored, add a universal unique identification code to the service request message to A first encapsulated message is formed, and the first encapsulated message is forwarded to neutron-ovn-metadata-agent through a preset communication mode.

The preset proxy software described in this embodiment includes but is not limited to Haproxy, and in a specific embodiment, the process of this step can be: use Haproxy to monitor 169.254.169.254:80, and the local port receives metadata After the request, Haproxy will receive the metadata request message. Then add the network UUID (Universally Unique Identifier) to the metadata request to form the first encapsulated message.

The preset communication methods described in this embodiment include but are not limited to the method of unix domian socket.

Step S26: Utilize the neutron-ovn-metadata-agent to analyze the first encapsulated message to obtain the UUID, source IP and the service request message, and use the UUID The identification code and the source IP obtain the project identification number and the target host identification number, and encapsulate the project identification number and the target host identification number into the service request message to form a second encapsulated message, and the The second encapsulated message is forwarded to nova-api, so that the nova-api returns corresponding metadata to the target host based on the second encapsulated message.

It can be understood that, in this step, the service request message includes the source IP.

In this step, the neutron-ovn-metadata-agent is used to process the received service request message accordingly, so as to forward it to nova-api, so that the nova-api sends information based on the second encapsulated message The target host returns corresponding metadata.

In this embodiment, after using the neutron-ovn-metadata-agent to obtain the project identification number and the target host identification number according to the unique universal identification code and source IP in the service request message, it may also include: using the The neutron-ovn-metadata-agent saves the item identification number, the target host identification number and the service request message into a preset database. The preset database includes but not limited to ovn-sb-db database.

It should be pointed out that the embodiment of the present invention does not depend on the underlying CPU (i.e. Central Processing Unit, central processing unit) architecture, and can support multiple architectures, such as x86 (i.e. The X86 architecture), arm (Advanced RISC Machine) and other architectures.

In this embodiment, the neutron-ovn-metadata-agent is first deployed in the management network of each computing node and each network node in the cloud platform, and the neutron-ovn-metadata-agent is used in each computing node and each network node Create an ovnmeta network namespace in the corresponding business network, obtain the service request message based on the metadata service sent by the target host from the preset routing route through the ovnmeta network namespace, and send the message to the preset processing port , using the preset proxy software to monitor the preset processing port corresponding to the preset target IP address, so that after the service request message is monitored, a universal unique identification code is added to the service request message to form the first An encapsulated message, forwarding the first encapsulated message to neutron-ovn-metadata-agent through a preset communication method, and using the neutron-ovn-metadata-agent to process the first encapsulated message Parse to obtain the UUID, source IP and the service request message, and use the UUID and source IP to obtain the project identification number and the target host identification number, and combine the project identification number with the The target host identification number is encapsulated into the service request message to form a second encapsulated message, and the second encapsulated message is forwarded to nova-api, so that the nova-api is based on the first 2. After the encapsulated message returns corresponding metadata to the target host. This embodiment shows the detailed process of the metadata service request, and proposes to use Haproxy to monitor 169.254.169.254:80, and encapsulate the metadata request with a universal unique identification code, and finally neutron-ovn-metadata-agent Based on the encapsulation of the project ID and the target host ID, the metadata service request is finally sent to nova-api through the management network. This embodiment expands the metadata service request process in this method in detail, so that both the cloud host and the cloud physical machine can successfully request the metadata service.

Figure 3 is a flow chart of the cloud host and cloud physical machine requesting metadata services. The figure shows that the cloud host or cloud physical machine first sends the metadata request to the ovnmeta network namespace, and adds network_id through haproxy (that is, as described in the embodiment Unique universal identification code), and then forward the metadata request to neutron-ovn-metadata-agent, save the matadata request to the ovn-sb-db database after obtaining project_id and instance_id, and finally project_id and instance_id in the metadata request, and forward to nova-api, and finally return the corresponding metadata data to the cloud host or cloud physical machine.

Referring to Figure 4, the embodiment of the present application discloses a metadata service request device, which may specifically include:

The node deployment module 11 is used to deploy neutron-ovn-metadata-agent in the management network of each computing node and each network node in the cloud platform respectively;

Space creating module 12, for utilizing said neutron-ovn-metadata-agent to create ovnmeta network namespace in the service network corresponding to each computing node and each network node;

The message obtaining module 13 is used to obtain the service request message based on the metadata service sent by the target host from the preset routing route through the ovnmeta network namespace;

The message forwarding module 14 is used to forward the service request message to neutron-ovn-metadata-agent by using the preset agent software through the preset communication mode;

A data return module 15, configured to use the neutron-ovn-metadata-agent to forward the service request message to nova-api, so that the nova-api returns metadata based on the service request to the target host .

This application first deploys neutron-ovn-metadata-agent respectively in the management network of each computing node and each network node in the cloud platform; Create an ovnmeta network namespace in the business network; obtain the service request message based on the metadata service sent by the target host from the preset routing route through the ovnmeta network namespace; The service request message is forwarded to neutron-ovn-metadata-agent; the service request message is forwarded to nova-api by using the neutron-ovn-metadata-agent, so that the nova-api returns to the target host based on Metadata for the service request. In this way, neutron-ovn-metadata-agent is deployed on each computing node and network node, which not only avoids the performance bottleneck problem of using neutron agent architecture, but also solves the problem of sending data requests on network nodes caused by using ovn architecture The cloud physical machine cannot request the metadata service. On this basis, both the cloud host and the cloud physical machine can successfully request the metadata service.

In some specific embodiments, the metadata service requesting device further includes:

The port application unit is used to create a local port in the ovnmeta network namespace, and set the preset target IP address and the port IP address of the subnet where the target host is located as the IP address of the local port, so that the target The host sets the gateway address of the preset target IP address as the IP address of the local port, and after creating a routing route from the target host to the ovnmeta network namespace, the routing route will be based on the meta Send the service request message of the data service.

In some specific embodiments, the port application unit further includes:

An address encapsulation unit, configured to encapsulate the destination IP address of the service request message into a preset target IP address, and encapsulate the destination MAC address into the MAC address of the local port.

In some specific embodiments, the metadata service requesting device further includes:

a port sending unit, configured to send the message to a preset processing port;

Correspondingly, the data return module 15 includes:

The first encapsulation unit is configured to use preset proxy software to monitor the preset processing port corresponding to the preset target IP address, so that after monitoring the service request message, add a universal unique to the service request message An identification code to form a first encapsulated message, and forward the first encapsulated message to neutron-ovn-metadata-agent through a preset communication mode.

A message forwarding unit, configured to forward the first encapsulated message to neutron-ovn-metadata-agent through a preset communication mode.

In some specific embodiments, the data return module 15 includes:

The second encapsulation unit is configured to use the neutron-ovn-metadata-agent to analyze the first encapsulated message to obtain the universal unique identification code, source IP and the service request message, and use Obtaining a project identification number and a target host identification number from the UUID and the source IP, and encapsulating the project identification number and the target host identification number into the service request message to form a second encapsulated message , and forward the second encapsulated message to nova-api, so that the nova-api returns corresponding metadata to the target host based on the second encapsulated message

In some specific embodiments, after using the neutron-ovn-metadata-agent to obtain the project identification number and the target host identification number according to the unique universal identification code and source IP in the service request message, it also includes:

Using the neutron-ovn-metadata-agent to save the item identification number, the target host identification number and the service request message into a preset database.

In some specific embodiments, the message forwarding module 14 includes:

The message forwarding unit is configured to use HAproxy to forward the service request message to neutron-ovn-metadata-agent through unix domian socket.

Further, the embodiment of this application also discloses an electronic device. FIG. 5 is a structural diagram of an electronic device 20 according to an exemplary embodiment, and the content in the figure should not be regarded as any limitation on the application scope of this application.

FIG. 5 is a schematic structural diagram of an electronic device 20 provided in an embodiment of the present application. The electronic device 20 may specifically include: at least one processor 21 , at least one memory 22 , a power supply 23 , a display screen 24 , an input/output interface 25 , a communication interface 26 and a communication bus 27 . Wherein, the memory 22 is used to store a computer program, and the computer program is loaded and executed by the processor 21, so as to implement the relevant steps in the metadata service request method disclosed in any of the foregoing embodiments. In addition, the electronic device 20 in this embodiment may specifically be an electronic computer.

In this embodiment, the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 26 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows is applicable Any communication protocol in the technical solution of the present application is not specifically limited here; the input and output interface 25 is used to obtain external input data or output data to the external, and its specific interface type can be selected according to specific application needs, here Not specifically limited.

In addition, the memory 22, as a resource storage carrier, can be a read-only memory, random access memory, magnetic disk or optical disk, etc., and the resources stored thereon can include operating system 221, computer program 222, etc., and the storage method can be temporary storage or permanent storage. .

Wherein, the operating system 221 is used to manage and control various hardware devices and computer programs 222 on the electronic device 20 , which may be Windows Server, Netware, Unix, Linux, etc. In addition to the computer program 222 that can be used to complete the metadata service request method performed by the electronic device 20 disclosed in any of the foregoing embodiments, the computer program 222 can further include a computer program that can be used to complete other specific tasks.

Furthermore, the present application also discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the aforementioned disclosed metadata service request method is implemented. Regarding the specific steps of the method, reference may be made to the corresponding content disclosed in the foregoing embodiments, and details are not repeated here.

Each embodiment in this specification is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same or similar parts of each embodiment can be referred to each other. As for the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and for relevant details, please refer to the description of the method part. Professionals can further realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, computer software or a combination of the two. In order to clearly illustrate the possible For interchangeability, in the above description, the composition and steps of each example have been generally described according to their functions. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

The steps of the methods or algorithms described in connection with the embodiments disclosed herein may be directly implemented by hardware, software modules executed by a processor, or a combination of both. Software modules can be placed in random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other Any other known storage medium.

Finally, it should also be noted that in this text, relational terms such as first and second etc. are only used to distinguish one entity or operation from another, and do not necessarily require or imply that these entities or operations, any such actual relationship or order exists. Furthermore, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes elements not expressly listed. other elements of or also include elements inherent in such a process, method, article, or device. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

The metadata service request method, device, equipment, and storage medium provided by the present invention have been described above in detail. In this paper, specific examples are used to illustrate the principle and implementation of the present invention. The description of the above embodiments is only for helping Understand the method of the present invention and its core idea; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation and scope of application. In summary, the content of this specification is not It should be understood as a limitation of the present invention.

Claims (10)

1. A metadata service request method, comprising: Deploy neutron-ovn-metadata-agent in the management network of each computing node and each network node in the cloud platform; Utilize the neutron-ovn-metadata-agent to create an ovnmeta network namespace in the service network corresponding to each computing node and each network node; Obtain the service request message based on the metadata service sent by the target host from the preset routing route through the ovnmeta network namespace; Using preset agent software to forward the service request message to neutron-ovn-metadata-agent through a preset communication method; Using the neutron-ovn-metadata-agent to forward the service request message to nova-api, so that the nova-api returns metadata based on the service request to the target host. 2. The metadata service request method according to claim 1, wherein, before obtaining the service request message based on the metadata service sent by the target host from the preset routing route through the ovnmeta network namespace, Also includes: Create a local port in the ovnmeta network namespace, and set the preset target IP address and the port IP address of the subnet where the target host is located as the IP address of the local port, so that the target host will be routed to the preset The gateway address of the target IP address is set to the IP address of the local port, and after the routing route from the target host to the ovnmeta network namespace is created, the service request based on the metadata service is reported according to the routing route text to send. 3. The metadata service request method according to claim 2, wherein the sending of the metadata service-based service request message according to the routing route comprises: Encapsulating the destination IP address of the service request message into a preset destination IP address, and encapsulating the destination MAC address into the MAC address of the local port. 4. The metadata service request method according to claim 1, characterized in that, after obtaining the service request message based on the metadata service sent by the target host from the preset routing route through the ovnmeta network namespace, Also includes: Send the message to a preset processing port; Correspondingly, the use of preset agent software to forward the service request message to neutron-ovn-metadata-agent through a preset communication method further includes: Use preset proxy software to monitor the preset processing port corresponding to the preset target IP address, so that after listening to the service request message, add a universal unique identification code to the service request message to form the first Encapsulate the message, and forward the first encapsulated message to neutron-ovn-metadata-agent through a preset communication mode. 5. The metadata service request method according to claim 4, wherein the service request message is forwarded to nova-api by using the neutron-ovn-metadata-agent, so that the nova-api Returning metadata based on the service request message to the target host, including: Utilize the neutron-ovn-metadata-agent to analyze the first encapsulated message to obtain the UUID, source IP and the service request message, and use the UUID, The source IP obtains the item identification number and the target host identification number, and encapsulates the item identification number and the target host identification number into the service request message to form a second encapsulated message, and the second The encapsulated message is forwarded to nova-api, so that the nova-api returns corresponding metadata to the target host based on the second encapsulated message. 6. The metadata service request method according to claim 5, wherein said neutron-ovn-metadata-agent is used to obtain the item identification according to the unique universal identification code and source IP in the service request message number and the target host identification number, also include: Using the neutron-ovn-metadata-agent to save the item identification number, the target host identification number and the service request message into a preset database. 7. The metadata service request method according to any one of claims 1 to 6, wherein the service request message is forwarded to neutron-ovn-metadata by using preset proxy software through a preset communication method -agents, including: Use HAproxy to forward the service request message to neutron-ovn-metadata-agent through unix domian socket. 8. A metadata service requesting device, comprising: The node deployment module is used to respectively deploy neutron-ovn-metadata-agent in the management network of each computing node and each network node in the cloud platform; A space creation module, for using the neutron-ovn-metadata-agent to create an ovnmeta network namespace in the service network corresponding to each computing node and each network node; The message acquisition module is used to obtain the service request message based on the metadata service sent by the target host from the preset routing route through the ovnmeta network namespace; A message forwarding module, configured to forward the service request message to neutron-ovn-metadata-agent through a preset communication mode by using preset agent software; A data return module, configured to use the neutron-ovn-metadata-agent to forward the service request message to nova-api, so that the nova-api returns metadata based on the service request to the target host. 9. An electronic device, characterized by comprising a processor and a memory; wherein, when the processor executes the computer program stored in the memory, the metadata service request according to any one of claims 1 to 7 is realized method. 10. A computer-readable storage medium, characterized by being used to store a computer program; wherein, when the computer program is executed by a processor, the metadata service request method according to any one of claims 1 to 7 is implemented.