CN114844744B - Virtual private cloud network configuration method and device, electronic equipment and computer readable storage medium - Google Patents
Virtual private cloud network configuration method and device, electronic equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN114844744B CN114844744B CN202210210307.9A CN202210210307A CN114844744B CN 114844744 B CN114844744 B CN 114844744B CN 202210210307 A CN202210210307 A CN 202210210307A CN 114844744 B CN114844744 B CN 114844744B
- Authority
- CN
- China
- Prior art keywords
- virtual
- network
- private cloud
- machine instance
- virtual machine
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application discloses a virtual private cloud network configuration method and device, electronic equipment and a computer readable storage medium. The method comprises the following steps: responding to creating a virtual private cloud for a user, and receiving a joining instruction of joining the virtual private cloud into a first network by the user; determining a virtual machine instance applicable to the virtual private cloud according to the joining instruction, wherein the virtual machine instance at least comprises a pair of virtual network cards created for other virtual private clouds; and setting a first virtual network card and a second virtual network card in the virtual machine instance, wherein the first virtual network card is used for connecting the virtual machine instance with the virtual private cloud created for the user, and the second virtual network card is used for connecting the virtual machine instance with the first network appointed by the user. According to the embodiment of the application, the cost of using the virtual machine instance by the user and the cost of managing and maintaining the virtual machine instance are reduced under the condition that the experience of using the virtual private cloud by the user is not affected.
Description
Technical Field
The present disclosure relates to the field of cloud computing technologies, and in particular, to a virtual private cloud network configuration method and apparatus, an electronic device, and a computer readable storage medium.
Background
With the development of internet technology, users have been able to perform a wide variety of tasks using internet-based cloud computing products. In these cloud computing services, the cloud desktop can enable a user to access a virtual host built based on the cloud computing service through the internet without using a traditional computer, particularly the cloud desktop appears, so that data of the user can be stored in a cloud server, and the dependence on the specification of physical equipment is eliminated, namely, the user can work and live by using the cloud desktop at any time and any place through the network by only using a terminal capable of accessing the internet, such as a mobile phone, a tablet computer and other terminal equipment.
Currently, due to the advantages of cloud desktops in terms of resource utilization rate, data security and the like, more and more enterprise users select cloud desktop products based on virtual private clouds for daily work. However, since the enterprise user also typically needs to manage the existing offline physical machine using a domain control service such as an Active Directory (Active Directory) service, such a cloud desktop product based on the virtual private cloud is also required for the enterprise user to join the existing AD domain of the enterprise user, so that the enterprise user using the cloud desktop product can use various applications and services in the AD domain of the enterprise.
Disclosure of Invention
The embodiment of the application provides a virtual private cloud network configuration method and device, electronic equipment and a computer readable storage medium, so as to solve the defect that network adding cost for a virtual private cloud network is high in the prior art.
To achieve the above objective, an embodiment of the present application provides a method for configuring a virtual private cloud network, including:
receiving a joining instruction for joining the virtual private cloud into the first network;
determining a virtual machine instance applicable to the virtual private cloud according to the joining instruction, wherein the virtual machine instance at least comprises a pair of virtual network cards created for other virtual private clouds;
a first virtual network card and a second virtual network card are arranged in the virtual machine instance, wherein the first virtual network card is used for connecting the virtual machine instance and the virtual private cloud, and the second virtual network card is used for connecting the virtual machine instance and a designated first network.
The embodiment of the application also provides a virtual private cloud network configuration device, which comprises:
the receiving module is used for receiving a joining instruction for joining the virtual private cloud into the first network;
the determining module is used for determining a virtual machine instance applicable to the virtual private cloud according to the joining instruction, wherein the virtual machine instance at least comprises a pair of virtual network cards created for other virtual private clouds;
The virtual network card setting module is used for setting a first virtual network card and a second virtual network card in the virtual machine instance, wherein the first virtual network card is used for connecting the virtual machine instance and the virtual private cloud, and the second virtual network card is used for connecting the virtual machine instance and the appointed first network.
The embodiment of the application also provides electronic equipment, which comprises:
a memory for storing a program;
and the processor is used for running the program stored in the memory, and executing the virtual private cloud network configuration method provided by the embodiment of the application when the program runs.
The embodiment of the application also provides a computer readable storage medium, on which a computer program executable by a processor is stored, wherein the program, when being executed by the processor, realizes the virtual private cloud network configuration method as provided by the embodiment of the application.
According to the virtual private cloud network configuration method and device, the electronic equipment and the computer readable storage medium, the existing virtual machine instance suitable for the virtual private cloud is found according to the received instruction for adding the virtual private cloud into the appointed first network, so that two virtual network cards used for the virtual private cloud are arranged in the found virtual machine instance, one virtual network card is used for connecting the virtual machine instance and the virtual private cloud, the other virtual network card is used for connecting the virtual machine instance and the appointed first network of a user, the virtual private cloud can be added into the appointed network by utilizing the existing virtual machine instance created for other virtual private cloud, and the virtual machine instance can be shared by a plurality of virtual private clouds by arranging a plurality of pairs of virtual network cards in one virtual machine instance, so that the cost of using the virtual machine instance by the user and the cost of managing and maintaining the virtual machine instance are reduced under the condition that the experience of using the virtual private cloud by the user is not affected.
The foregoing description is only an overview of the technical solutions of the present application, and may be implemented according to the content of the specification in order to make the technical means of the present application more clearly understood, and in order to make the above-mentioned and other objects, features and advantages of the present application more clearly understood, the following detailed description of the present application will be given.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the application. Also, like reference numerals are used to designate like parts throughout the figures. In the drawings:
fig. 1 is an application scenario schematic diagram of a virtual private cloud network configuration scheme provided in an embodiment of the present application;
FIG. 2 is a flowchart of one embodiment of a VPN configuration method provided herein;
fig. 3 is a flowchart of another embodiment of a virtual private cloud network configuration method provided in the present application;
fig. 4 is a schematic structural diagram of an embodiment of a vpn configuration device provided in the present application;
fig. 5 is a schematic structural diagram of an embodiment of an electronic device provided in the present application.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Example 1
The scheme provided by the embodiment of the application can be applied to any system with cloud resource management capability, such as a server system comprising a chip with cloud resource management function and related components. Fig. 1 is an application scenario schematic diagram of a virtual private cloud network configuration scheme provided in an embodiment of the present application, and the scenario shown in fig. 1 is only one example to which the technical scheme of the present application is applicable.
At the present time when cloud computing services are evolving very rapidly, users have been able to perform a wide variety of tasks using internet-based cloud computing products. In these cloud computing services, the cloud desktop can enable a user to access a virtual host built based on the cloud computing service through the internet without using a traditional computer, particularly the cloud desktop appears, so that data of the user can be stored in a cloud server, and the dependence on the specification of physical equipment is eliminated, namely, the user can work and live by using the cloud desktop at any time and any place through the network by only using a terminal capable of accessing the internet, such as a mobile phone, a tablet computer and other terminal equipment.
In the network environment of an enterprise, a domain control service of an Active Directory (Active Directory) service is also widely used, and the enterprise can use the domain control service to create one or more networks inside the enterprise, so that staff can use computers inside the enterprise and access network resources inside the enterprise through control over the networks.
Therefore, while cloud desktops have advantages in terms of resource utilization and data security, more and more enterprise users select cloud desktop products for daily work, networks managed by domain control services of Active Directory (Active Directory) services are also indispensable for enterprise users, and in particular, daily work of each employee inside an enterprise company still needs to be performed in the networks. Thus, after an enterprise user typically purchases a cloud desktop product, it is desirable that the cloud desktop product also be able to join the enterprise user's existing AD network, so that the enterprise user using the cloud desktop product is also able to use various resources and services in the enterprise AD domain.
Thus, in the prior art, it has been proposed to create one corresponding connector for each cloud desktop for the connection of the user-created cloud desktop and the user-specified network. By creating a domain connector for each customer using an independent instance, the virtual machine corresponding to the cloud desktop is connected into the network specified by the user, so that the user can use the cloud desktop as if using a computer in a normal network. In such a case, however, as the number of users increases, the cost of the instance is high, and the cost of management and maintenance is also high.
For example, as shown in fig. 1, fig. 1 is an example showing an application scenario of a virtual private cloud network configuration scheme according to an embodiment of the present application. In the scenario shown in fig. 1, an enterprise user may request that a cloud desktop product be created for it by accessing a cloud service provider's website. For example, a cloud desktop product may be a virtual private cloud for which a cloud service provider generates using its cloud computing resources. In other words, a cloud desktop product may be some cloud computing resources that are partitioned by a cloud service provider providing public cloud services for private use by the enterprise user according to their requests on a public cloud that it assumes on a public network. Thus, in embodiments of the present application, a cloud desktop product may be a collection of dedicated cloud computing resources that a cloud service provider allocates to a user. For example, a virtual machine may be run on cloud resources of the virtual private cloud to configure the virtual machine on the virtual private cloud using computing resources, such as processors, memory, and storage space, of the virtual private cloud and to provide cloud desktop services to users using the virtual machine.
For example, the user's virtual private cloud may be allocated corresponding computing resources, such as processors and memory space, storage space on a storage server, and so forth, according to the user's request to create the virtual private cloud. And then, running the virtual machine with the allocated processor and memory space, wherein the virtual machine can be used as a virtual computer of a user on the cloud to execute various instructions issued by the user locally through an input device, and return calculation results to a display device of the user locally, so that the user can use a private cloud allocated on a public cloud to execute personal tasks like operating the local computer of the user, and can store various data on a cloud server, and the user can enter a cloud desktop on the virtual private cloud of the user by accessing a website portal of a provider of the cloud desktop product at any time and any place and logging in.
As described above, enterprise users will also typically need to add the cloud desktop product of the virtual private cloud to the network they have created in order to use the various resources and services in the network. Thus, as shown in FIG. 1, in the prior art, a virtual machine instance would be created for the user and used as a network to connect to the virtual private cloud created for the user as above and to which the enterprise user needs to join. In other words, as shown in fig. 1, one virtual machine instance may be created between the user applying for the virtual private cloud-based cloud desktop and the enterprise network that the user has actually used as above, and used as a connector, so as to be connected to the virtual private cloud and the network, respectively, through a pair of virtual network cards provided at both ends of the connector. So that for the management server of the user's network, it can be regarded as one physical device in the network based on the virtual network card of the virtual machine instance connected to the network. As a virtual machine instance connecting the virtual private cloud and the network, the two virtual network cards at both ends can be used for analyzing and judging the flow direction of the traffic between the network and the virtual private cloud, so that the virtual private cloud can be used as a traffic repeater. Thus, use of virtual private cloud products in the network that are actually located on the public network is achieved for the user.
However, as described above, in the prior art, although a channel for joining a network can be created for a virtual private cloud product of a user on a public cloud through a virtual machine instance, in the prior art, it is necessary to create one such connector for each cloud desktop of the user, respectively, so that the cloud desktop product can join a specified network. While each such virtual machine instance connector requires the provision of modules such as DNS proxy, TCP proxy, and UDP proxy, these modules are certainly implemented using cloud computing resources of the cloud service provider, and thus, the user also requires a significant additional resource and management cost for the virtual machine instance connectors that they use.
Therefore, in the embodiment of the present application, in the scenario shown in fig. 1, after a cloud desktop product of a virtual private cloud is created for a user, according to an instruction further issued by the user to join the virtual private cloud to a specified network, two virtual network cards are set in an existing virtual machine instance to connect the virtual private cloud and the network, so as to implement multiplexing of the existing virtual machine instance, so that on one hand, the requirement that the user joins the created cloud desktop to the specified network can be met, and on the other hand, since the virtual machine instance which has been created by multiplexing is used as a connector for connecting the virtual private cloud and the specified network, there is no need to create one virtual machine instance for each cloud desktop, so that the creation cost of the instance is greatly saved, and various management costs of the user in daily use can be saved.
For example, in the scenario shown in fig. 1, three virtual private cloud desktop products have been created at the cloud service provider for three users by partitioning the virtual private cloud, and accordingly one virtual machine instance is created when, for example, a virtual private cloud product is created for a first user, and two virtual network cards 1 and a are created in the virtual machine instance, wherein virtual network card 1 is used to connect the virtual machine instance and the virtual private cloud product created for the first user, and virtual network card a is used to connect the virtual machine instance and the first user specifying the enterprise AD network DomainA to be joined. Specifically, as shown in fig. 1, in the embodiment of the present application, the virtual network card a may be connected to the network DomainA through a forwarding route instance created for the network DomainA.
Thereafter, when the second user also requests creation of the cloud desktop product, unlike the prior art, it may be first searched for whether there is a virtual machine instance created after the virtual private cloud is created for it, and specifically, a virtual machine instance in which the virtual private cloud available to the second user joins another enterprise AD network DomainB may be searched for. For example, typically, virtual machine instances are limited to their specifications, so there is an upper limit to the number of virtual network cards that they can mount. Therefore, in the embodiment of the application, when searching for an available virtual machine instance for the virtual private cloud of the second user, the number of the mounted virtual network cards in the created virtual machine instance may not reach the upper limit yet, and in particular, more than two virtual machine instances of the virtual network cards may also be mounted as the available virtual machine instances.
Thus, the virtual machine instance created for the first user's virtual private cloud as above is available to the second user's virtual private cloud to join the network because only two virtual network cards are mounted. After determining to use the virtual machine instance, a pair of virtual network cards 2 and B may be further set in the virtual machine instance, where the virtual network card 2 may be used to connect a virtual private cloud created for a second user with the virtual machine instance, and the virtual network card B is used to connect the virtual machine instance with a forwarding route instance B of a network that the second user designates to join, so that two virtual network cards may be further set in the virtual machine instance that has been created for the first virtual private cloud to connect the second virtual private cloud with a network that the second virtual private cloud needs to join (e.g., a forwarding route instance where the network is located), so that multiplexing of the virtual machine instance is achieved, and cost of using cloud desktop products that join into an enterprise network by the two users is saved.
Furthermore, in the embodiment of the present application, it may also occur that the same enterprise user may have two or more AD networks, for example, one enterprise user may have two branches at two different sites a and B, respectively, and thus one AD network may be created for each company, respectively. For example, in the scenario shown in fig. 1, there may be two networks DomainB and DomainC that belong to one enterprise user, and thus, in the embodiment of the present application, these two networks may belong together to the same forwarding routing instance. In this case, as shown in fig. 1, when the enterprise user first creates a cloud desktop product and requests to join in the network DomainB, as in the solution according to the embodiment of the present application, two virtual network cards 2 and B may be further set in the virtual machine instance by multiplexing the virtual machine instance to connect the virtual private cloud product and the forwarding route instance B to which the network DomainB belongs, respectively. Thereafter, another user of the enterprise may additionally apply for creating a cloud desktop product and require joining the network DomainC. At this time, since it is known in advance that the network DomainC and the network DomainB belong to the same forwarding route instance, that is, the forwarding route instance B, at this time, similarly to the manner of joining the network DomainB, the virtual machine instance can be continuously multiplexed under the condition that the specification of the virtual machine instance allows, and the virtual network card 3 is set therein to connect to the cloud desktop product created for the user, and since the network C and the network B are both in the same forwarding route instance, in the embodiment of the present application, there is no need to set a new virtual network card for the forwarding route instance of the network C, but instead, the virtual network card B set for the network B before can be directly multiplexed because the virtual network card B has been connected to the virtual machine instance and the forwarding route instance B. Therefore, in the embodiment of the present application, the virtual network card b may be directly used to form a virtual network card for the newly created cloud desktop product together with the newly set virtual network card 3. Thus, the cost for setting a new virtual network card for users of the same enterprise can be further saved.
Therefore, according to the configuration scheme of the virtual private cloud network provided by the embodiment of the application, when the created virtual private cloud is added to the designated network according to the user, by multiplexing the created virtual machine instance and setting two virtual network cards for the virtual private cloud in the virtual private cloud, one virtual network card is used for connecting the virtual machine instance and the virtual private cloud created for the user, and the other virtual network card is used for connecting the virtual machine instance and the first network designated by the user, so that the virtual private cloud can be added to the designated network by using the existing virtual machine instance created for other virtual private cloud, multiplexing and sharing of the virtual machine instance are realized, and the cost of using the virtual machine instance by the user and the cost of managing and maintaining the virtual machine instance are reduced under the condition that the experience of using the virtual private cloud by the user is not affected.
The foregoing embodiments are illustrative of the technical principles and exemplary application frameworks of the embodiments of the present application, and the detailed description of specific technical solutions of the embodiments of the present application will be further described below by means of a plurality of embodiments.
Example two
Fig. 2 is a flowchart of an embodiment of a method for configuring a virtual private cloud network, where the method may be implemented by various terminals or server devices with network configuration capabilities, or may be an apparatus or a chip integrated on these devices. As shown in fig. 2, the network configuration method includes the steps of:
S201, receiving a joining instruction for joining the virtual private cloud into the first network.
In step S201, after the virtual private cloud is created for the user, a join instruction issued by the user to join the virtual private cloud into the specified network may be further received. In the present embodiment, while a virtual private cloud has been created for a user to enable the user to use, for example, a cloud desktop product, it is a more urgent need for an enterprise user to use the cloud desktop product or cloud virtual machine product in an already created enterprise network (AD). In particular, in general, enterprises can provide staff users with various resources in their own networks (AD) and can also uniformly manage computers of staff joining in the networks through the networks. Accordingly, in step S201, a join instruction for the user to join the specified first network may be further received after the virtual private cloud product is created for the user. For example, the instruction may include various information about the network that the user wants to join, so that the network configuration method according to the embodiment of the application may access the network according to the information.
S202, determining a virtual machine instance suitable for the virtual private cloud according to the joining instruction.
In step S202, existing virtual machine instances that have been created for, for example, other virtual private clouds may be found according to the join instruction in step S201. In particular, in the embodiment of the present application, in order to improve the utilization rate of the virtual machine instance and reduce the cost of adding the cloud desktop product to the network by the user, the virtual private cloud created for the user by multiplexing or sharing the virtual machine instance and the network specified by the user through the addition instruction in step S201 may be used as the connection. In particular, in the embodiment of the present application, since the virtual machine instance is generally limited to its specification, there is an upper limit to the number of virtual network cards that can be mounted. For example, in the scenario as shown in fig. 1, if the specification of a virtual machine instance allows 6 virtual network cards to be mounted when the virtual machine instance is created for the first user's virtual private cloud, the virtual machine instance can only actually be used for sharing or multiplexing of three virtual private clouds. Thus, in step S202, all virtual machine instances that have been created may be traversed and the number of virtual network cards that have been mounted thereof is confirmed one by how much worse from the upper limit of its specification, and for example, the most distant instance may be used as the instance that is suitable for the virtual private cloud determined in step S202.
Of course, in the embodiment of the present application, the first instance of the first found number of virtual network cards that can be mounted and the upper limit of the specification of the first instance of the first found number of virtual network cards are larger than two virtual network cards, which is the available instance determined in step S202.
S203, setting a first virtual network card and a second virtual network card in the virtual machine instance.
In step S203, two virtual network cards may be set for the join instruction received in step S201 among the available virtual machine instances determined by the lookup in step S202. Of the two virtual network cards, a first virtual network card may be used to connect the virtual machine instance with the virtual private cloud that was in step S201, and a second virtual network card may be used to connect the virtual machine instance with the first network specified in the join instruction received in step S201. Thus, with the two virtual network cards set in the virtual machine instance in step S203, traffic between the virtual private cloud and the network specified by the user in step S201 can be both made to be forwarded through the virtual machine instance, so the user can use the virtual private cloud product that has been created for it in step S201 as in the network.
According to the virtual private cloud network configuration method, the existing virtual machine instance suitable for the virtual private cloud is found according to the received instruction for adding the virtual private cloud into the specified first network, so that two virtual network cards used for the virtual private cloud are arranged in the found virtual machine instance, one virtual network card is used for connecting the virtual machine instance and the virtual private cloud, the other virtual network card is used for connecting the virtual machine instance and the first network specified by a user, the virtual private cloud can be added into the specified network by using the existing virtual machine instance created for other virtual private clouds, and a plurality of virtual network cards are arranged in one virtual machine instance to enable the virtual private clouds to share one virtual machine instance, so that the cost of using the virtual machine instance by the user and the cost of managing and maintaining the virtual machine instance are reduced under the condition that the experience of using the virtual private cloud by the user is not affected.
Example III
Fig. 3 is a flowchart of another embodiment of a method for configuring a vpn network, where the method may be implemented by various terminals or server devices with network configuration capabilities, or may be an apparatus or a chip integrated on these devices. As shown in fig. 3, on the basis of the embodiment shown in fig. 2, the method for configuring a virtual private cloud network according to the embodiment of the present application may include the following steps:
s301, receiving a joining instruction for joining the virtual private cloud into the first network.
In step S301, after the virtual private cloud is created for the user, a join instruction issued by the user to join the virtual private cloud into the specified network may be further received. In the present embodiment, while a virtual private cloud has been created for a user to enable the user to use, for example, a cloud desktop product, it is a more urgent need for an enterprise user to use the cloud desktop product or cloud virtual machine product in an already created enterprise network (AD). In particular, in general, an enterprise can provide staff users with various resources in its AD network and can also uniformly manage computers of staff added to the network through the network. Accordingly, in step S301, a join instruction for the user to join the specified first network may be further received after the virtual private cloud product is created for the user. For example, the instruction may include various information about the network that the user wants to join, so that the network configuration method according to the embodiment of the application may access the network according to the information.
S302, determining a virtual machine instance suitable for the virtual private cloud according to the joining instruction.
In step S302, existing virtual machine instances that have been created for, for example, other virtual private clouds may be found according to the join instruction in step S301. For example, in the scenario shown in fig. 1, the cloud desktop product of the first virtual private cloud has been previously created for the first user by partitioning the virtual private cloud in step S301, and the available virtual machine instances are found according to the instructions of the user to connect the first virtual private cloud to their designated network. But in this case the user is the first user and thus the virtual machine instance has not been created before. Thus, a virtual machine instance may be created for the first user, and two virtual network cards 1 and a are created in the virtual machine instance, wherein virtual network card 1 is used to connect the virtual machine instance and the virtual private cloud product created for the first user, and virtual network card a is used to connect the virtual machine instance and the first user to specify an enterprise network DomainA to be joined. Specifically, as shown in fig. 1, in the embodiment of the present application, the virtual network card a may be connected to the network DomainA through a forwarding route instance a created for the network DomainA.
Thus, in step S302, when a join instruction issued after the second user requests creation of the virtual private cloud product is received in step S301, the join instruction may instruct to join the second virtual private cloud to DomainB, in step S303, it may be searched whether there is a created virtual machine instance, and in particular, it may be searched whether the number of virtual network cards mounted has not reached an upper limit yet, in particular, it may also be able to mount virtual machine instances of more than two virtual network cards as available virtual machine instances.
Therefore, since only two virtual network cards are mounted on the virtual machine instance created for the first virtual private cloud of the first user, the virtual machine instance can be found in step S302, and it can be further confirmed that the number of virtual network cards mounted on the virtual machine instance is different by 4 virtual network cards from the upper limit thereof, so that it can be confirmed that the second virtual private cloud of the second user can be used for the virtual machine instance to join the network DomainB specified in the joining instruction sent in step S301.
Thus, in the embodiment of the present application, the virtual private cloud created for the user is used as a connector to connect to the network specified by the user through the join instruction in step S301 by multiplexing or otherwise sharing the virtual machine instance. In particular, in the embodiment of the present application, since the virtual machine instance is generally limited to its specification, there is an upper limit to the number of virtual network cards that can be mounted. For example, in the scenario as shown in fig. 1, if the specification of a virtual machine instance allows 6 virtual network cards to be mounted when the virtual machine instance is created for the first user's virtual private cloud, the virtual machine instance can only actually be used for sharing or multiplexing of three virtual private clouds. Thus, in step S302, all virtual machine instances that have been created may be traversed and the number of virtual network cards that have been mounted thereof may be confirmed one by how much worse from the upper limit of its specification, and the most distant instance may be used as the instance that is suitable for the virtual private cloud determined in step S302, for example.
Of course, in the embodiment of the present application, the first instance of the first found number of mountable virtual network cards and the upper limit of the specification of the first instance of the first found number of mountable virtual network cards is greater than two virtual network cards, which is the available instance determined in step S302.
In addition, in the embodiment of the present application, in step S302, it may be further considered whether the found virtual machine instance is supported in the region and forwarding route instance resources specified in the join instruction of the user received in step S301.
S303, setting a first virtual network card and a second virtual network card in the virtual machine instance.
In step S303, two virtual network cards may be set for the join instruction received in step S301 among the available virtual machine instances determined by the lookup in step S302. Of the two virtual network cards, a first virtual network card may be used to connect a virtual machine instance with the virtual private cloud in step S301, and a second virtual network card may be used to connect the first network specified in the join instruction received in step S301 through the forwarding route instance created for the first network.
In particular, in general, the network specified in the join instruction issued in step S301 is different for each user applying for creating a virtual private cloud, that is, each user applying for creating a virtual private cloud uses a different network, respectively. In some cases it may also occur that the same enterprise user may have two or more networks, for example, one enterprise user may have two branches at two different sites a and B, respectively, so that one network may be created for each company, respectively. Thus, in the scenario shown in fig. 1, there may be two networks DomainB and DomainC that belong to the same enterprise user.
Thus, in the embodiments of the present application, the two networks may share the same forwarding routing instance. In this case, as shown in fig. 1, when the enterprise user first creates a cloud desktop product and requests to join in the network DomainB, as in the solution according to the embodiment of the present application, two virtual network cards 2 and B may be further set in the virtual machine instance by multiplexing the virtual machine instance to connect the virtual private cloud product and the forwarding route instance B to which the network DomainB belongs, respectively. However, in step S301, if another user of the enterprise additionally applies to create a cloud desktop product, and requests to join the network DomainC. At this time, since it is known in advance that the network domain c and the network domain B belong to the same forwarding route instance, that is, forwarding route instance B, in step S303, a virtual network card 3 may be set in the virtual machine instance confirmed in step S302 to connect to the virtual private cloud created for the user.
Then, in step S303, the network list that the virtual machine instance confirmed in step S302 has been connected to the AD network may be further acquired. For example, as shown in fig. 1, in the case where two pairs of virtual network cards have been created in the virtual machine instance for two users, respectively, in step S303, it may be acquired that the virtual machine instance has been connected to two networks, i.e., domainA and DomainB. In particular, typically, one forwarding route instance may be created for each network, so that a virtual machine instance may connect to the corresponding network by connecting a virtual network card therein to the forwarding route instance. Therefore, in step S303, after the virtual network card 3 is set, the forwarding route instance to which the virtual machine instance is connected and the network information set therein may be further acquired. For example, in the scenario shown in fig. 1, it may be acquired that the virtual machine instance confirmed in step S302 has connected two forwarding route instances, and the first forwarding route instance is provided with a network DomainA, and the second forwarding route instance is provided with a network DomainB. Accordingly, in step S303, the network DomainC specified in the user' S join instruction received in step S301 can be compared with the network information in the network list thus acquired. For example, by comparing, it may be confirmed that DomainC and DomainB are actually disposed in the same second forwarding routing instance. Thus, the virtual network card b previously set for the DomainB in the virtual machine instance and connected to the second forwarding routing instance may be multiplexed in step S303 to form a pair of virtual network cards for the newly created virtual private cloud product together with the newly set virtual network card 3. Thus, the cost for setting a new virtual network card for users of the same enterprise can be further saved.
S304, setting a domain name resolution agent according to the virtual network card information of the first virtual network card and the second virtual network card, so that the traffic between the virtual private cloud and the first network is forwarded through the domain name resolution agent.
In step S304, a domain name resolution (DNS) agent may be further set in the virtual machine instance confirmed in step S302 according to the virtual network card information of the first virtual network card and the second virtual network card set in step S303. For example, in step S304, a domain name resolution agent using the name service may be set so that when a virtual private cloud and a network that connects virtual machine instances take the domain name resolution agent as a target DNS, so that any party requests an address, the DNS agent may obtain the address request and send the address of the other party stored therein back to the requesting party as a response, so that the requesting party can establish communication with the other party.
In addition, in step S304, the DNS proxy may also be configured to use the UDP53 port to forward DNS traffic, so that when any party sends data, the DNS proxy may modify an IP field in DNS data, thereby forwarding traffic.
According to the virtual private cloud network configuration method, the existing virtual machine instance suitable for the virtual private cloud is found according to the received instruction for adding the virtual private cloud into the specified first network, so that two virtual network cards used for the virtual private cloud are arranged in the found virtual machine instance, one virtual network card is used for connecting the virtual machine instance and the virtual private cloud, the other virtual network card is used for connecting the virtual machine instance and the first network specified by a user, the virtual private cloud can be added into the specified network by using the existing virtual machine instance created for other virtual private clouds, and a plurality of virtual network cards are arranged in one virtual machine instance to enable the virtual private clouds to share one virtual machine instance, so that the cost of using the virtual machine instance by the user and the cost of managing and maintaining the virtual machine instance are reduced under the condition that the experience of using the virtual private cloud by the user is not affected.
Example IV
Fig. 4 is a schematic structural diagram of an embodiment of a vpn network configuration device provided in the present application, which may be used to perform the vpn network configuration method shown in fig. 2 or fig. 3. As shown in fig. 4, the virtual private cloud network configuration apparatus may include: a receiving module 41, a determining module 42 and a virtual network card setting module 43.
The receiving module 41 may be configured to receive a join instruction to join the virtual private cloud to the first network.
After creating the virtual private cloud for the user, the receiving module 41 may receive a join instruction issued by the user to join the virtual private cloud into the specified network. In the present embodiment, while a virtual private cloud has been created for a user to enable the user to use, for example, a cloud desktop product, it is a more urgent need for an enterprise user to use the cloud desktop product or cloud virtual machine product in an already created enterprise network (AD). In particular, in general, enterprises can provide staff users with various resources in their own networks (AD) and can also uniformly manage computers of staff joining in the networks through the networks. Accordingly, the receiving module 41 may further receive a join instruction for the user to join the specified first network after the virtual private cloud product is created for the user. For example, the instruction may include various information about the network that the user wants to join, so that the network configuration method according to the embodiment of the application may access the network according to the information.
The determining module 42 may be configured to determine, according to the join instruction, a virtual machine instance applicable to the virtual private cloud.
Determination module 42 may find existing virtual machine instances that have been created for, for example, other virtual private clouds based on the join instruction received by reception module 41. For example, a cloud desktop product of a first virtual private cloud has been previously created for a first user by partitioning the virtual private cloud, and determination module 42 may find available virtual machine instances according to instructions of the user to connect the first virtual private cloud to its designated network. But in this case the user is the first user and thus the virtual machine instance has not been created before. Thus, in this case, determination module 42 may determine that there are no virtual machine instances available for the first user. Where a virtual machine instance has been previously created for the first user, determination module 42 may determine the virtual machine instance as an available virtual machine instance.
For example, in the embodiment of the present application, the determining module 42 may find that, among created virtual machine instances, the number of virtual network cards mounted has not reached the upper limit, and specifically, at least virtual machine instances with more than two virtual network cards can also be mounted as available virtual machine instances.
Thus, in the embodiment of the present application, the virtual private cloud created for the user is used as a connector to connect to the network specified by the user through the join instruction in step S301 by multiplexing or otherwise sharing the virtual machine instance. In particular, in the embodiment of the present application, since the virtual machine instance is generally limited to its specification, there is an upper limit to the number of virtual network cards that can be mounted. The determination module 42 may also traverse all virtual machine instances that have been created and confirm, one by one, how much the number of virtual network cards that it has mounted is worse from its upper specification limit, and may use the largest difference as a determined instance for the virtual private cloud, for example.
In this embodiment of the present application, of course, the first instance where the difference between the number of the found mountable virtual network cards and the upper limit of the specification is greater than two virtual network cards may also be used as the determined available instance.
In addition, in the embodiment of the present application, the determining module 42 may further consider whether the found virtual machine instance is supported in the region and forwarding route instance resources specified in the join instruction of the user received by the receiving module 41.
The virtual network card setting module 43 may be configured to set a first virtual network card and a second virtual network card in the virtual machine instance.
The virtual network card setting module 43 may set two virtual network cards for the joining instruction received by the receiving module 41 in the available virtual machine instance determined by the determining module 42 through the lookup. Of these two virtual network cards, a first virtual network card may be used to connect a virtual machine instance with a virtual private cloud that has been created for the user, and a second virtual network card may be used to connect the first network specified in the join instruction received by the receiving module 41 through a forwarding route instance created for the first network.
In particular, in general, the network specified in the join instruction issued by each user applying for creating a virtual private cloud received by the receiving module 41 is different, that is, each user applying for creating a virtual private cloud uses a different network. In some cases it may also occur that the same enterprise user may have two or more networks, for example, one enterprise user may have two branches at two different sites a and B, respectively, so that one network may be created for each company, respectively. Thus, in the scenario shown in fig. 1, there may be two networks DomainB and DomainC that belong to the same enterprise user.
In particular, in the embodiments of the present application, the two networks may belong together to the same forwarding routing instance. In this case, as shown in fig. 1, when the enterprise user first creates a cloud desktop product and requests to join in the network DomainB, as in the solution according to the embodiment of the present application, two virtual network cards 2 and B may be further set in the virtual machine instance by multiplexing the virtual machine instance to connect the virtual private cloud product and the forwarding route instance B to which the network DomainB belongs, respectively. However, in step S301, if another user of the enterprise additionally applies to create a cloud desktop product, and requests to join the network DomainC. At this time, since it is known in advance that the network DomainC and the network DomainB belong to the same forwarding route instance, that is, the forwarding route instance B, the virtual network card setting module 43 may set a virtual network card 3 in the virtual machine instance confirmed by the determining module 42 to connect to the virtual private cloud created for the user.
Then, the virtual network card setting module 43 may further acquire a network list of the virtual machine instance that has been confirmed by the confirmation module 42 to be connected to the network. For example, as shown in fig. 1, in the case where two pairs of virtual network cards have been created in the virtual machine instance for two users, respectively, it is possible to acquire that the virtual machine instance has been connected to two networks, i.e., domainA and DomainB. In particular, typically, one forwarding route instance may be created for each network, so that a virtual machine instance may connect to the corresponding network by connecting a virtual network card therein to the forwarding route instance.
Accordingly, the virtual network card setting module 43, after setting the virtual network card 3, can further acquire the forwarding route instance to which the virtual machine instance is connected and the network information set therein, and can compare the network specified in the joining instruction of the user received by the receiving module 41 with the network information in the network list thus acquired. For example, it may be confirmed by comparison that the network specified in the instruction received by the receiving module 41 is actually provided in the same second forwarding route instance as another network in the acquired network list. Thus, the virtual network card setting module 43 may multiplex the virtual network card previously set for the other network in the virtual machine instance that is connected to the second forwarding routing instance to make it together with the newly set virtual network card constitute a pair of virtual network cards for the newly created virtual private cloud product. Thus, the cost for setting a new virtual network card for users of the same enterprise can be further saved.
In addition, in the embodiment of the present application, a domain name resolution setting module 44 may be further included, which may be configured to set a domain name resolution proxy according to the virtual network card information of the first virtual network card and the second virtual network card, so that the traffic between the virtual private cloud and the first network is forwarded through the domain name resolution proxy.
The domain name resolution setting module 44 may further set a domain name resolution (DNS) proxy in the virtual machine instance confirmed by the confirmation module 42 according to the virtual network card information of the first virtual network card and the second virtual network card set by the virtual network card setting module 43. For example, domain name resolution setting module 44 may set a domain name resolution agent using the name service so that when a virtual private cloud and network that connects virtual machine instances take the domain name resolution agent as a target DNS, so that either party requests an address, the DNS agent may obtain the address request and send back the address of the other party it stores to the requesting party as a response so that the requesting party can establish communication with the other party.
In addition, the domain name resolution setting module 44 may also set the DNS proxy to use the UDP53 port to forward DNS traffic, so that when any party sends data, the DNS proxy may modify the IP field in the DNS data, so as to implement forwarding of traffic.
According to the virtual private cloud network configuration device, the existing virtual machine instance suitable for the virtual private cloud is found according to the received instruction for adding the virtual private cloud into the appointed first network, so that two virtual network cards used for the virtual private cloud are arranged in the found virtual machine instance, one virtual network card is used for connecting the virtual machine instance and the virtual private cloud, the other virtual network card is used for connecting the virtual machine instance and the user-appointed first network, the virtual private cloud can be added into the appointed network by using the existing virtual machine instance created for other virtual private clouds, multiple pairs of virtual network cards are arranged in one virtual machine instance, and therefore the virtual machine instance can be shared by multiple virtual private clouds, and the cost of using the virtual machine instance by a user and the cost of managing and maintaining the virtual machine instance are reduced under the condition that the experience of using the virtual private cloud by the user is not affected.
Example five
The internal functions and structures of a virtual private cloud network configuration apparatus are described above, which may be implemented as an electronic device. Fig. 5 is a schematic structural diagram of an embodiment of an electronic device provided in the present application. As shown in fig. 5, the electronic device includes a memory 51 and a processor 52.
A memory 51 for storing a program. In addition to the programs described above, the memory 51 may also be configured to store other various data to support operations on the electronic device. Examples of such data include instructions for any application or method operating on the electronic device, contact data, phonebook data, messages, pictures, videos, and the like.
The memory 51 may be implemented by any type of volatile or non-volatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
The processor 52 is not limited to a processor (CPU), but may be a processing chip such as a Graphics Processor (GPU), a Field Programmable Gate Array (FPGA), an embedded neural Network Processor (NPU), or an Artificial Intelligence (AI) chip. The processor 52 is coupled to the memory 51, and executes the program stored in the memory 51 to perform the vpn network configuration method according to the second or third embodiment.
Further, as shown in fig. 5, the electronic device may further include: communication component 53, power component 54, audio component 55, display 56, and other components. Only some of the components are schematically shown in fig. 5, which does not mean that the electronic device only comprises the components shown in fig. 5.
The communication component 53 is configured to facilitate communication between the electronic device and other devices, either wired or wireless. The electronic device may access a wireless network based on a communication standard, such as WiFi, 3G, 4G, or 5G, or a combination thereof. In one exemplary embodiment, the communication component 53 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 53 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.
A power supply assembly 54 provides power to the various components of the electronic device. The power supply components 54 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for electronic devices.
The audio component 55 is configured to output and/or input audio signals. For example, the audio component 55 includes a Microphone (MIC) configured to receive external audio signals when the electronic device is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may be further stored in the memory 51 or transmitted via the communication component 53. In some embodiments, the audio assembly 55 further comprises a speaker for outputting audio signals.
The display 56 includes a screen, which may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or slide action, but also the duration and pressure associated with the touch or slide operation.
Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the method embodiments described above may be performed by hardware associated with program instructions. The foregoing program may be stored in a computer readable storage medium. The program, when executed, performs steps including the method embodiments described above; and the aforementioned storage medium includes: various media that can store program code, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the invention.
Claims (10)
1. A virtual private cloud network configuration method, comprising:
receiving a joining instruction for joining the virtual private cloud into the first network;
determining a virtual machine instance applicable to the virtual private cloud according to the joining instruction, wherein the virtual machine instance at least comprises a pair of virtual network cards created for other virtual private clouds;
a first virtual network card and a second virtual network card are arranged in the virtual machine instance, wherein the first virtual network card is used for connecting the virtual machine instance and the virtual private cloud, and the second virtual network card is used for connecting the virtual machine instance and a designated first network.
2. The virtual private cloud network configuration method of claim 1, wherein the second virtual network card is connected to the first network through a forwarding routing instance created for the first network.
3. The virtual private cloud network configuration method of claim 1, wherein said setting a first virtual network card and a second virtual network card in the virtual machine instance further comprises:
acquiring a network list to which the virtual machine instance is connected;
determining that a second network matched with the first network exists in the network list;
and using a third virtual network card connected with the second network in the virtual machine instance as the second virtual network card.
4. The virtual private cloud network configuration method of claim 3, wherein the determining that there is a second network in the network list that matches the first network comprises:
acquiring forwarding route instance information of forwarding route instances where all networks are located in the network list;
and according to the forwarding route instance information, determining the network in the same forwarding route instance as the first network as the second network.
5. The virtual private cloud network configuration method of claim 1, wherein the method further comprises:
And setting a domain name resolution agent according to the virtual network card information of the first virtual network card and the second virtual network card, so that the traffic between the virtual private cloud and the first network is forwarded through the domain name resolution agent.
6. A virtual private cloud network configuration apparatus, comprising:
the receiving module is used for receiving a joining instruction for joining the virtual private cloud into the first network;
the determining module is used for determining a virtual machine instance applicable to the virtual private cloud according to the joining instruction, wherein the virtual machine instance at least comprises a pair of virtual network cards created for other virtual private clouds;
the virtual network card setting module is used for setting a first virtual network card and a second virtual network card in the virtual machine instance, wherein the first virtual network card is used for connecting the virtual machine instance and the virtual private cloud, and the second virtual network card is used for connecting the virtual machine instance and the appointed first network.
7. The virtual private cloud network configuration apparatus of claim 6, wherein the second virtual network card is connected to the first network through a forwarding routing instance created for the first network.
8. The virtual private cloud network configuration apparatus of claim 6, wherein the virtual network card setting module is further to:
acquiring a network list to which the virtual machine instance is connected;
determining that a second network matched with the first network exists in the network list;
and using a third virtual network card connected with the second network in the virtual machine instance as the second virtual network card.
9. An electronic device, comprising:
a memory for storing a program;
a processor for running the program stored in the memory to perform the virtual private cloud network configuration method according to any one of claims 1 to 5.
10. A computer readable storage medium having stored thereon a computer program executable by a processor, wherein the program when executed by the processor implements the virtual private cloud network configuration method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210210307.9A CN114844744B (en) | 2022-03-04 | 2022-03-04 | Virtual private cloud network configuration method and device, electronic equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210210307.9A CN114844744B (en) | 2022-03-04 | 2022-03-04 | Virtual private cloud network configuration method and device, electronic equipment and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114844744A CN114844744A (en) | 2022-08-02 |
| CN114844744B true CN114844744B (en) | 2023-07-21 |
Family
ID=82562599
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210210307.9A Active CN114844744B (en) | 2022-03-04 | 2022-03-04 | Virtual private cloud network configuration method and device, electronic equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114844744B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115665026A (en) * | 2022-09-26 | 2023-01-31 | 京东科技信息技术有限公司 | Cluster networking method and device |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103384255A (en) * | 2011-12-31 | 2013-11-06 | 华为数字技术（成都）有限公司 | Load balancing method, server and system for virtual machine cluster |
| CN104639372A (en) * | 2015-02-13 | 2015-05-20 | 中国联合网络通信集团有限公司 | Correlation method and system for overlay network based on SDN (Software Defined Network) and physical network |
| WO2017125016A1 (en) * | 2016-01-18 | 2017-07-27 | 中兴通讯股份有限公司 | Method, apparatus and system for modifying configuration information of virtual network card |
| CN107800743A (en) * | 2016-09-06 | 2018-03-13 | 中国电信股份有限公司 | Cloud desktop system, cloud management system and relevant device |
| CN109768871A (en) * | 2017-11-09 | 2019-05-17 | 阿里巴巴集团控股有限公司 | Configure method, host and the storage medium of multiple Microsoft Loopback Adapters |
| CN110752937A (en) * | 2018-07-23 | 2020-02-04 | 中兴通讯股份有限公司 | Physical function multiplexing method and device and computer storage medium |
| CN111124659A (en) * | 2018-11-01 | 2020-05-08 | 深信服科技股份有限公司 | Heterogeneous cloud network intercommunication system and method |
| CN111130973A (en) * | 2018-11-01 | 2020-05-08 | 深信服科技股份有限公司 | Heterogeneous cloud network intercommunication system and method |
| CN111510310A (en) * | 2019-01-30 | 2020-08-07 | 顺丰科技有限公司 | Network mode implementation method and device under public cloud architecture |
| CN113285983A (en) * | 2021-04-26 | 2021-08-20 | 北京科东电力控制系统有限责任公司 | Virtual experiment system supporting multiple virtualized security devices to share single encryption card |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130036213A1 (en) * | 2011-08-02 | 2013-02-07 | Masum Hasan | Virtual private clouds |
| CN102387061B (en) * | 2011-10-21 | 2014-05-07 | 华为技术有限公司 | Method, device and system for accessing VPC (virtual private cloud) to VPN (virtual private network) |
| CN103621046B (en) * | 2012-05-22 | 2016-08-24 | 华为技术有限公司 | Network communication method and device |
-
2022
- 2022-03-04 CN CN202210210307.9A patent/CN114844744B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103384255A (en) * | 2011-12-31 | 2013-11-06 | 华为数字技术（成都）有限公司 | Load balancing method, server and system for virtual machine cluster |
| CN104639372A (en) * | 2015-02-13 | 2015-05-20 | 中国联合网络通信集团有限公司 | Correlation method and system for overlay network based on SDN (Software Defined Network) and physical network |
| WO2017125016A1 (en) * | 2016-01-18 | 2017-07-27 | 中兴通讯股份有限公司 | Method, apparatus and system for modifying configuration information of virtual network card |
| CN107800743A (en) * | 2016-09-06 | 2018-03-13 | 中国电信股份有限公司 | Cloud desktop system, cloud management system and relevant device |
| CN109768871A (en) * | 2017-11-09 | 2019-05-17 | 阿里巴巴集团控股有限公司 | Configure method, host and the storage medium of multiple Microsoft Loopback Adapters |
| CN110752937A (en) * | 2018-07-23 | 2020-02-04 | 中兴通讯股份有限公司 | Physical function multiplexing method and device and computer storage medium |
| CN111124659A (en) * | 2018-11-01 | 2020-05-08 | 深信服科技股份有限公司 | Heterogeneous cloud network intercommunication system and method |
| CN111130973A (en) * | 2018-11-01 | 2020-05-08 | 深信服科技股份有限公司 | Heterogeneous cloud network intercommunication system and method |
| CN111510310A (en) * | 2019-01-30 | 2020-08-07 | 顺丰科技有限公司 | Network mode implementation method and device under public cloud architecture |
| CN113285983A (en) * | 2021-04-26 | 2021-08-20 | 北京科东电力控制系统有限责任公司 | Virtual experiment system supporting multiple virtualized security devices to share single encryption card |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114844744A (en) | 2022-08-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111431956B (en) | Cross-network service access method, device, system and storage medium | |
| CN110489192B (en) | Remote communication method and device and electronic equipment | |
| CN109150677B (en) | Cross-domain access processing method and device and electronic equipment | |
| CN113905030B (en) | Intranet and extranet communication method and device, intranet terminal, proxy server and storage medium | |
| CN115002769B (en) | Flow diversion method, core network element, electronic equipment and medium | |
| CN114281263B (en) | Storage resource processing method, system and equipment of container cluster management system | |
| CN114666306B (en) | WebRTC network connection establishment method, server, electronic device and computer readable storage medium | |
| CN112202744B (en) | Multi-system data communication method and device | |
| CN114844744B (en) | Virtual private cloud network configuration method and device, electronic equipment and computer readable storage medium | |
| CN114124944A (en) | Data processing method and device of hybrid cloud and electronic equipment | |
| US20190273785A1 (en) | Independent internet connection generation | |
| US9674238B2 (en) | Mobile content collaboration with one click multimedia capability | |
| CN112995005B (en) | Virtual network data exchange method and device | |
| CN111953718B (en) | Page debugging method and device | |
| KR102492793B1 (en) | System for providing virtual desktop service and method for the same | |
| CN114760360B (en) | Request response method, request response device, electronic equipment and computer readable storage medium | |
| CN113612643A (en) | Network configuration method, device, equipment and storage medium of cloud mobile phone | |
| CN111104575B (en) | Data grabbing method and device and electronic equipment | |
| KR101495562B1 (en) | Method And Apparatus for Providing Data Analysis Service | |
| CN107948232B (en) | Hook API-based proxy implementation method, data transmission method, device and system | |
| Ganchev et al. | A cloud-based service recommendation system for use in UCWW | |
| CN114788393A (en) | Inter-device communication method, apparatus, and storage medium | |
| CN115484316B (en) | File sharing method and device | |
| US11947971B2 (en) | Remote resource configuration mechanism | |
| CN115484149B (en) | Network switching method, network switching device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |