CN114844744A - 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 PDF

Info

Publication number
CN114844744A
CN114844744A CN202210210307.9A CN202210210307A CN114844744A CN 114844744 A CN114844744 A CN 114844744A CN 202210210307 A CN202210210307 A CN 202210210307A CN 114844744 A CN114844744 A CN 114844744A
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.)
Granted
Application number
CN202210210307.9A
Other languages
Chinese (zh)
Other versions
CN114844744B (en
Inventor
李志宇
魏宇平
杨晨光
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba China Co Ltd
Original Assignee
Alibaba China Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alibaba China Co Ltd filed Critical Alibaba China Co Ltd
Priority to CN202210210307.9A priority Critical patent/CN114844744B/en
Publication of CN114844744A publication Critical patent/CN114844744A/en
Application granted granted Critical
Publication of CN114844744B publication Critical patent/CN114844744B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

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

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: in response to creating a virtual private cloud for a user, receiving a joining instruction for the user to join the virtual private cloud to a first network; determining a virtual machine instance suitable for 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 a 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 specified 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 influenced.

Description

Virtual private cloud network configuration method and device, electronic equipment and computer-readable storage medium
Technical Field
The present application relates to the field of cloud computing technologies, and in particular, to a method and an apparatus for configuring a virtual private cloud network, 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 the cloud computing services, the cloud desktop enables a user to access a virtual host established based on the cloud computing services through the internet without using a traditional computer, particularly the appearance of the cloud desktop, so that the data of the user can be stored in a cloud server, and the dependence on the specification of physical equipment is also eliminated, namely, the user only needs to use a terminal capable of accessing the internet, such as a mobile phone, a tablet computer and other terminal equipment, and can use the cloud desktop for work and life at any time and any place through the network.
At present, due to the advantages of cloud desktops in terms of resource utilization rate, data security and the like, more and more enterprise users also select cloud desktop products based on virtual private cloud for daily work. However, since enterprise users usually need to manage the existing offline physical machines by using domain control services such as Active Directory (Active Directory) services, for the enterprise users, such cloud desktop products based on virtual private cloud also need to join the existing AD domain of the enterprise users, so that the enterprise users using the cloud desktop products can use various applications and services in the AD domain of the enterprise.
Disclosure of Invention
The embodiment of the application provides a method and a device for configuring a virtual private cloud network, an electronic device and a computer-readable storage medium, so as to solve the defect that the cost for adding a network to the virtual private cloud network is high in the prior art.
In order to achieve the above object, 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 to the first network;
determining a virtual machine instance suitable for 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 and the virtual private cloud, and the second virtual network card is used for connecting the virtual machine instance and a specified first network.
An embodiment of the present application further provides a virtual private cloud network configuration apparatus, including:
the receiving module is used for receiving a joining instruction for joining the virtual private cloud to the first network;
a determining module, configured to determine, according to the join instruction, a virtual machine instance applicable to the virtual private cloud, where the virtual machine instance at least includes a pair of virtual network cards created for other virtual private clouds;
and 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 specified first network.
An embodiment of the present application further provides an electronic device, including:
a memory for storing a program;
and the processor is used for operating the program stored in the memory, and the program executes the virtual private cloud network configuration method provided by the embodiment of the application when running.
The embodiment of the present application further provides a computer-readable storage medium, on which a computer program executable by a processor is stored, where the program, when executed by the processor, implements the virtual private cloud network configuration method provided in the embodiment of the present application.
According to the virtual private cloud network configuration method and device, the electronic device and the computer readable storage medium provided by the embodiment of the application, the existing virtual machine instance suitable for the virtual private cloud is found according to the received instruction for adding the virtual private cloud to the specified first network, so that two virtual network cards for the virtual private cloud are set in the found virtual machine instance, one virtual network card is used for connecting the virtual machine instance and the virtual private cloud, and the other virtual network card is used for connecting the virtual machine instance and the specified first network of the user, so that the virtual private cloud can be added to the specified network by using the existing virtual machine instances created for other virtual private clouds, and a plurality of pairs of virtual network cards are set in one virtual machine instance to enable the plurality of virtual private clouds to share one virtual machine instance, so that the experience of the user using the virtual private cloud is not influenced, the cost of the user using the virtual machine instance and the cost of managing and maintaining the virtual machine instance are reduced.
The foregoing description is only an overview of the technical solutions of the present application, and the present application can be implemented according to the content of the description in order to make the technical means of the present application more clearly understood, and the following detailed description of the present application is given in order to make the above and other objects, features, and advantages of the present application more clearly understandable.
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 refer to like parts throughout the drawings. In the drawings:
fig. 1 is a schematic view of an application scenario of a virtual private cloud network configuration scheme according to an embodiment of the present application;
fig. 2 is a flowchart of an embodiment of a virtual private cloud network configuration method provided in the present application;
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 virtual private cloud network configuration apparatus 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 one
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, and the like. Fig. 1 is a schematic view of an application scenario 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 rapidly developing, users have been able to perform a wide variety of tasks using internet-based cloud computing products. In the cloud computing services, the cloud desktop enables a user to access a virtual host established based on the cloud computing services through the internet without using a traditional computer, particularly the appearance of the cloud desktop, so that the data of the user can be stored in a cloud server, and the dependence on the specification of physical equipment is also eliminated, namely, the user only needs to use a terminal capable of accessing the internet, such as a mobile phone, a tablet computer and other terminal equipment, and can use the cloud desktop for work and life at any time and any place through the network.
In an enterprise network environment, a domain control service of an Active Directory (Active Directory) service has also been widely used, and an enterprise may use the domain control service to create one or more networks inside the enterprise, so that employees can conveniently manage the use of computers inside the enterprise and access network resources inside the enterprise through the control of the networks.
Therefore, although more and more enterprise users select cloud desktop products for daily work due to the advantages of cloud desktop in terms of resource utilization rate, data security, and the like, a network managed by a domain control service of an original Active Directory (Active Directory) service is indispensable for the enterprise users, and particularly, daily work of each employee inside an enterprise company still needs to be performed in the network. Therefore, after an enterprise user generally purchases a cloud desktop product, the cloud desktop product needs to be able to join the existing AD network of the enterprise user, so that the enterprise user using the cloud desktop product can also use various resources and services in the enterprise AD domain.
Therefore, in the prior art, it has been proposed to create a corresponding connector for each cloud desktop for connecting the cloud desktop created by the user and the network specified by the user. By creating a domain connector for each customer using a separate instance, a virtual machine corresponding to the cloud desktop is connected to a network designated by the user, so that the user can use the cloud desktop as if using a computer in a general network. However, in such a case, as the number of users increases, the cost of the instances is high, and the cost of management and maintenance is also high.
For example, as shown in fig. 1, fig. 1 is an example of an application scenario illustrating 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 to create a cloud desktop product for a cloud service provider by accessing its website. For example, a cloud desktop product may be a virtual private cloud generated for a cloud service provider using its cloud computing resources. In other words, a cloud desktop product may be some cloud computing resources that are divided by a cloud service provider providing public cloud services for the enterprise user on its assumption on a public cloud on a public network, at the request of the enterprise user. Thus, in embodiments of the present application, a cloud desktop product may be a collection of dedicated cloud computing resources that are allocated to a user by a cloud service provider. 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 for a user using the virtual machine.
For example, according to a request of a user to create a virtual private cloud, corresponding computing resources, such as processors and memory space, and storage space on a storage server, etc., may be allocated for the virtual private cloud of the user. And then, running a virtual machine by using the allocated processor and the allocated memory space, wherein the virtual machine can be used as a virtual computer on the cloud of the user to execute various instructions issued by the user through an input device locally, and return a calculation result to a display device local to the user, so that the user can use a special private cloud allocated on a public cloud to execute personal tasks like operating a computer local to the user, and can store various data on a cloud server, so that the user can access a website portal of a provider of the cloud desktop product anytime and anywhere and enter a cloud desktop on the own virtual private cloud by logging in.
As described above, enterprise users typically also need to add cloud desktop products of the virtual private cloud to the network they have created in order to use various resources and services in the network. Thus, as shown in fig. 1, in the prior art, a virtual machine instance is created for the user and used as a network to connect the virtual private cloud created for the user as described above and the enterprise user needs to join. In other words, as shown in fig. 1, one virtual machine instance may be created between the cloud desktop based on the virtual private cloud and the enterprise network that the user actually uses, and the virtual machine instance may be used as a connector, so that the virtual private cloud and the network are connected through a pair of virtual network cards arranged at two ends of the connector. Thus, for the management server of the user's network, it can be considered as one physical device in the network based on the virtual network card of the virtual machine instance connected to the network. As an example of a virtual machine connecting the virtual private cloud and the network, the traffic between the network and the virtual private cloud can be analyzed and the flow direction can be determined by using two virtual network cards at both ends, so that the virtual private cloud can be used as a traffic forwarder. Thus, it is achieved for the user to use a virtual private cloud product that is actually located on the public network in the network.
However, as described above, in the prior art, although a channel for a user to join a network can be created for a virtual private cloud product on a public cloud through a virtual machine instance, in the prior art, one connector needs to be created for each cloud desktop of the user respectively so that the cloud desktop product can join a specified network. Modules such as a DNS proxy, a TCP proxy, and a UDP proxy are required to be arranged in each virtual machine instance connector, and these modules are certainly required to be implemented by using cloud computing resources of a cloud service provider, and therefore, a user also needs to pay a large amount of extra resource cost and management cost for the virtual machine instance connectors used by the user.
In the present embodiment, therefore, in the scenario shown in fig. 1, after the cloud desktop product of the virtual private cloud is created for the user, according to the instruction of adding the virtual private cloud into the appointed network further issued by the user, two virtual network cards are arranged in the existing virtual machine instance to connect the virtual private cloud and the network, therefore, the multiplexing of the existing virtual machine instances is realized, so that the requirement that a user adds the created cloud desktop into a specified network can be met, on the other hand, since the virtual machine instance that has been created is used as a connector for connecting the virtual private cloud with the specified network by multiplexing it, therefore, a virtual machine instance does not need to be created for each cloud desktop, so that the creation expense of the instance is greatly saved, and various management expenses of daily use of a user can be saved.
For example, in the scenario shown in fig. 1, a cloud desktop product of three virtual private clouds has been created for three users by dividing the virtual private clouds at the cloud service provider, and accordingly one virtual machine instance is created when creating the virtual private cloud product for a first user, for example, and two virtual network cards 1 and a are created in the virtual machine instance, where the virtual network card 1 is used to connect the virtual machine instance and the virtual private cloud product created for the first user, and the virtual network card a is used to connect the virtual machine instance and the first user specified to join the enterprise AD network DomainA na. 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 routing instance created for the network DomainA.
Thereafter, when a second user also requests to create a cloud desktop product, unlike the prior art, it may first be found whether there is a virtual machine instance already created after a virtual private cloud is created for it, and specifically, it may be found that a virtual machine instance available for the second user's virtual private cloud to join another enterprise AD network DomainB. For example, typically, a virtual machine instance is limited in its specification, and thus there is an upper limit to the number of virtual network cards that it can mount. Therefore, in the embodiment of the present application, when searching for an available virtual machine instance for the virtual private cloud of the second user, the number of mounted virtual network cards in the created virtual machine instance may not reach the upper limit yet, and specifically, a virtual machine instance with more than two virtual network cards may also be mounted as the available virtual machine instance.
Therefore, the virtual machine instance created for the first user's virtual private cloud as above can be used for the second user's virtual private cloud to join the network because only two virtual network cards are mounted. After the virtual machine instance is determined to be used, a pair of virtual network cards 2 and B can be further set in the virtual machine instance, wherein the virtual network card 2 can be used for connecting a virtual private cloud created for a second user and the virtual machine instance, and the virtual network card B is used for connecting the virtual machine instance and a forwarding routing instance B of a network to be joined designated by the second user, so that two virtual network cards can be further set in the virtual machine instance created for the first virtual private cloud to respectively connect the second virtual private cloud and the network to be joined by the second virtual private cloud (for example, the forwarding routing instance where the network is located), thereby realizing multiplexing of the virtual machine instances and saving the cost of using a cloud desktop product joined to an enterprise network by the two users.
Furthermore, in the embodiment of the present application, it may also occur that the same enterprise user may own two or more AD networks, for example, one enterprise user may have two branch companies at two different locations 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 belonging to one enterprise user, and thus, in the embodiment of the present application, these two networks may belong to the same forwarding routing instance. In this case, as shown in fig. 1, when the enterprise user creates a cloud desktop product first and requests to join the network DomainB, as in the scheme of 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 routing instance B to which the network DomainB belongs, respectively. Another user of the enterprise may then additionally apply for creating a cloud desktop product and request 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 routing instance, that is, the forwarding routing instance B, at this time, similarly to the manner of joining the network DomianB, the virtual machine instance may be continuously multiplexed under the permission of the specification of the virtual machine instance, and the virtual network card 3 is set in the virtual machine instance to connect the cloud desktop product created for the user, and since the network C and the network B are both in the same forwarding routing instance, in this embodiment, it is not necessary to set a new virtual network card for the forwarding routing instance of the network C, but the virtual network card B set for the network B before may be directly multiplexed, because the virtual network card B has already connected the virtual machine instance and the forwarding routing 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. Therefore, the cost for setting a new virtual network card for the 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 a created virtual private cloud is added to a specified network according to a user, one of the two virtual network cards is used for connecting the virtual machine instance and the virtual private cloud created for the user, and the other is used for connecting the virtual machine instance and the first network specified by the user, so that the virtual private cloud can be added to the specified network by using the existing virtual machine instances created for other virtual private clouds, the multiplexing and sharing of the virtual machine instance are realized, and the cost for the user to use the virtual machine instance and the cost for managing and maintaining the virtual machine instance are reduced under the condition that the experience of the user to use the virtual private cloud is not influenced.
The above embodiments are illustrations of technical principles and exemplary application frameworks of the embodiments of the present application, and specific technical solutions of the embodiments of the present application are further described in detail below through a plurality of embodiments.
Example two
Fig. 2 is a flowchart of an embodiment of a virtual private cloud network configuration method provided in the present application, where an execution subject of the method may be various terminal or server devices with network configuration capability, or may be a device or chip integrated on these devices. As shown in fig. 2, the network configuration method includes the following steps:
s201, receiving a joining instruction for joining the virtual private cloud to 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 to a specified network may be further received. In the embodiment of the present application, although a virtual private cloud has been created for a user so that the user can use, for example, a cloud desktop product, it is more urgent for an enterprise user to use the cloud desktop product or a cloud virtual machine product in an enterprise network (AD) that has been created. In particular, enterprises can provide various resources for employee users in their own network (AD) and can also uniformly manage the computers of employees participating in the network through the network. Therefore, 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 of the network that the user wants to join, so that the network configuration method according to the embodiment of the present application may access the network according to the information.
S202, determining a virtual machine instance suitable for the virtual private cloud according to the adding 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 for the user, the virtual private cloud created for the user and the network specified by the user through the join instruction in step S201 may be connected by multiplexing or sharing the virtual machine instance. In particular, in the embodiment of the present application, since the virtual machine instance is generally limited by its specification, there is an upper limit to the number of virtual network cards that can be mounted on the virtual machine instance. For example, in the scenario shown in fig. 1, if the specification of a virtual machine instance allows 6 virtual network cards to be mounted when creating the virtual machine instance for the first user's virtual private cloud, then the virtual machine instance can actually only be used for sharing or multiplexing of three virtual private clouds. Therefore, in step S202, all virtual machine instances that have been created may be traversed, and it may be confirmed one by one how much the number of virtual network cards that have been mounted is worse than the upper limit of the specification thereof, and the difference that is the largest may be used as the instance that is determined in step S202 and is suitable for the virtual private cloud, for example.
Of course, in the embodiment of the present application, an example in which the difference between the number of the first found virtual network cards that can be mounted and the upper limit of the specification of the first found virtual network card is greater than two virtual network cards may also be used as the available example 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 in the available virtual machine instance determined by the lookup in step S202. Of the two virtual network cards, the first virtual network card may be used to connect the virtual machine instance with the virtual private cloud in step S201, and the 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. Therefore, by 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 forwarded by the virtual machine instance, so that the user can use the virtual private cloud product that has been created for it in step S201 as in the network.
The method for configuring the virtual private cloud network provided by the embodiment of the application searches the existing virtual machine instance suitable for the virtual private cloud according to the received instruction for adding the virtual private cloud to the specified first network, so that two virtual network cards for the virtual private cloud are set in the found virtual machine instance, one for connecting the virtual machine instance and the virtual private cloud, and the other for connecting the virtual machine instance and the user-specified first network, so that existing virtual machine instances created for other virtual private clouds can be utilized to join the virtual private cloud to a specified network, multiple virtual private clouds can share one virtual machine instance by arranging multiple pairs of virtual network cards in one virtual machine instance, therefore, 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 influenced.
EXAMPLE III
Fig. 3 is a flowchart of another embodiment of a virtual private cloud network configuration method provided in the present application, where an execution subject of the method may be various terminal or server devices with network configuration capability, or may be a device or 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 provided in the embodiment of the present application may include the following steps:
s301, a joining instruction for joining the virtual private cloud to the first network is received.
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 to a specified network may be further received. In the embodiment of the present application, although a virtual private cloud has been created for a user so that the user can use, for example, a cloud desktop product, it is more urgent for an enterprise user to use the cloud desktop product or a cloud virtual machine product in an enterprise network (AD) that has been created. In particular, it is common that an enterprise can provide various resources for employee users in its own AD network and can also uniformly manage the computers of employees participating in the network through the network. Therefore, 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 of the network that the user wants to join, so that the network configuration method according to the embodiment of the present application may access the network according to the information.
S302, determining a virtual machine instance suitable for the virtual private cloud according to the adding 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, a cloud desktop product of a first virtual private cloud has been created for a first user by dividing the virtual private cloud in step S301, and an available virtual machine instance is found according to an instruction 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 therefore has not created a virtual machine instance before it. Therefore, a virtual machine instance can be created for the first user, and two virtual network cards 1 and a are created in the virtual machine instance, where the virtual network card 1 is used to connect the virtual machine instance and the virtual private cloud product created for the first user, and the virtual network card a is used to connect the virtual machine instance and the enterprise network DomainA specified to be joined by the first user. 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 routing instance a created for the network DomainA.
Therefore, in step S302, when a join instruction issued after the second user requests to create 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 found whether there is a created virtual machine instance, and specifically, it may be found that, in the created virtual machine instance, the number of mounted virtual network cards has not reached the upper limit, and specifically, it is also possible to mount a virtual machine instance of more than two virtual network cards as an available virtual machine instance.
Therefore, as the virtual machine instance created for the first virtual private cloud of the first user only mounts two virtual network cards, the virtual machine instance may be found in step S302, and it may be further confirmed that the number of virtual network cards mounted by the virtual machine instance is different from the upper limit by 4 virtual network cards, so that it may be confirmed that the virtual machine instance is available for the second virtual private cloud of the second user to join the network DomainB specified in the join instruction sent in step S301.
Therefore, in the embodiment of the present application, the virtual private cloud created for the user and the network specified by the user through the join instruction in step S301 are connected by multiplexing or sharing the virtual machine instance. In particular, in the embodiment of the present application, since the virtual machine instance is generally limited by its specification, there is an upper limit to the number of virtual network cards that can be mounted on the virtual machine instance. For example, in the scenario shown in fig. 1, if the specification of a virtual machine instance allows 6 virtual network cards to be mounted when creating the virtual machine instance for the first user's virtual private cloud, then the virtual machine instance can actually only be used for sharing or multiplexing of three virtual private clouds. Therefore, in step S302, all the virtual machine instances that have been created may be traversed, and it may be confirmed one by one how much the number of the virtual network cards that have been mounted is worse than the upper limit of the specification thereof, and the difference that is the largest may be used as the instance that is determined in step S302 and is suitable for the virtual private cloud, for example.
Of course, in the embodiment of the present application, an example in which the difference between the number of the first found virtual network cards that can be mounted and the upper limit of the specification of the first found virtual network card is greater than two virtual network cards may also be used as the available example determined in step S302.
In addition, in this embodiment of the application, in step S302, it may further be considered whether the found virtual machine instance is supported in the area and forwarding routing instance resource 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 in the available virtual machine instance determined by the lookup in step S302. Of the two virtual network cards, the first virtual network card may be used to connect the virtual machine instance with the virtual private cloud in step S301, and the second virtual network card may be used to connect the first network specified in the join instruction received in step S301 through the forwarding routing instance created for the first network.
In particular, in general, the networks specified in the join instruction issued in step S301 by each user applying for creating the virtual private cloud are different, that is, each user applying for creating the virtual private cloud uses different networks. In some cases, however, it may also occur that the same enterprise user may own two or more networks, for example, an enterprise user may have two affiliates at two different locations, a and B, respectively, and thus a 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.
Therefore, in the embodiment of the present application, the two networks may belong to the same forwarding route instance. In this case, as shown in fig. 1, when the enterprise user creates a cloud desktop product first and requests to join the network DomainB, as in the scheme of 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 routing instance B to which the network DomainB belongs, respectively. However, in step S301, if another user of the enterprise additionally applies for creating a cloud desktop product, the user 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, 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, a network list of the virtual machine instance already connected to the AD network confirmed in step S302 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 can be acquired that the virtual machine instance has been connected to two networks, i.e., DomainA and DomainB. Specifically, in general, a forwarding routing instance may be created for each network, so that the virtual machine instance may be connected to the corresponding network by connecting a virtual network card therein to the forwarding routing instance. Therefore, in step S303, after the virtual network card 3 is set, the forwarding routing 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 has a network DomainA set therein, and the second forwarding route instance has a network DomainB set therein. Therefore, in step S303, the network DomainC specified in the joining instruction of the user received in step S301 may be compared with the network information in the network list thus acquired. For example, a comparison may confirm that DomainC and DomainB are actually located in the same second forwarding route instance. Therefore, the virtual network card b connected to the second forwarding routing instance, which was previously set for the DomainB in the virtual machine instance, may be multiplexed to constitute a pair of virtual network cards for the newly created virtual private cloud product together with the newly set virtual network card 3 in step S303. Therefore, the cost for setting a new virtual network card for the users of the same enterprise can be further saved.
And 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 flow 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) proxy 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, a domain name resolution proxy using named service may be set in step S304, so that when a virtual private cloud and a network that connect virtual machine instances have the domain name resolution proxy as a target DNS, so that either party requests an address, the DNS proxy may acquire the address request and send back to the requesting party the address of the other party that it stores as a response, so that the requesting party may 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 transmits data, the DNS proxy may modify an IP field in the DNS data, thereby implementing traffic forwarding.
The method for configuring the virtual private cloud network provided by the embodiment of the application searches the existing virtual machine instance suitable for the virtual private cloud according to the received instruction for adding the virtual private cloud to the specified first network, so that two virtual network cards for the virtual private cloud are set in the found virtual machine instance, one for connecting the virtual machine instance and the virtual private cloud, and the other for connecting the virtual machine instance and the user-specified first network, so that existing virtual machine instances created for other virtual private clouds can be utilized to join the virtual private cloud to a specified network, multiple virtual private clouds can share one virtual machine instance by arranging multiple pairs of virtual network cards in one virtual machine instance, therefore, 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 influenced.
Example four
Fig. 4 is a schematic structural diagram of an embodiment of a virtual private cloud network configuration apparatus provided in the present application, which may be used to execute the virtual private cloud 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 to a specified network. In the embodiment of the present application, although a virtual private cloud has been created for a user so that the user can use, for example, a cloud desktop product, it is more urgent for an enterprise user to use the cloud desktop product or a cloud virtual machine product in an enterprise network (AD) that has been created. In particular, enterprises can provide various resources for employee users in their own network (AD) and can also uniformly manage the computers of employees participating in the network through the network. Therefore, 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 of the network that the user wants to join, so that the network configuration method according to the embodiment of the present application may access the network according to the information.
The determining module 42 may be configured to determine, according to the joining instruction, a virtual machine instance suitable for the virtual private cloud.
The determination module 42 may look for existing virtual machine instances that have been created for other virtual private clouds, for example, according to the join instruction received by the receiving module 41. For example, a cloud desktop product for a first virtual private cloud has been previously created for a first user by partitioning the virtual private cloud, and determination module 42 may look for an available virtual machine instance according to instructions for the user to connect the first virtual private cloud to its designated network. But in this case, the user is the first user and therefore has not created a virtual machine instance before it. Thus, in this case, determination module 42 may determine that there is no virtual machine instance 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 this embodiment of the application, the determining module 42 may find that, in the created virtual machine instances, the number of mounted virtual network cards has not reached the upper limit, and specifically, at least, virtual machine instances that exceed two virtual network cards can also be mounted as available virtual machine instances.
Therefore, in the embodiment of the present application, the virtual private cloud created for the user and the network specified by the user through the join instruction in step S301 are connected by multiplexing or sharing the virtual machine instance. In particular, in the embodiment of the present application, since the virtual machine instance is generally limited by its specification, there is an upper limit to the number of virtual network cards that can be mounted on the virtual machine instance. The determining module 42 may also traverse all the 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 than the upper limit of its specification, and may use the worst difference as the determined instance that is suitable for the virtual private cloud, for example.
Of course, in the embodiment of the present application, an instance in which the difference between the number of the first found virtual network cards that can be mounted and the upper limit of the specification of the first found virtual network card is greater than two virtual network cards may also be used as the determined available instance.
In addition, in this embodiment of the application, the determining module 42 may further consider whether the found virtual machine instance is supported in the region and forwarding routing instance resource 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 the first virtual network card and the second virtual network card in the virtual machine instance.
The virtual network card setting module 43 may set two virtual network cards for the join instruction received by the receiving module 41 in the available virtual machine instance determined by the determining module 42 through the lookup. Of the two virtual network cards, the first virtual network card may be used to connect the virtual machine instance with the virtual private cloud that has been created for the user, and the second virtual network card may be used to connect the first network specified in the join instruction received by the receiving module 41 through the forwarding routing instance created for the first network.
In particular, in general, the networks specified in the join instruction issued by each user applying for creating the virtual private cloud and received by the receiving module 41 are different, that is, each user applying for creating the virtual private cloud uses different networks. In some cases, however, it may also occur that the same enterprise user may own two or more networks, for example, an enterprise user may have two affiliates at two different locations, a and B, respectively, and thus a 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 embodiment of the present application, the two networks may belong to the same forwarding route instance. In this case, as shown in fig. 1, when the enterprise user creates a cloud desktop product first and requests to join the network DomainB, as in the scheme of 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 routing instance B to which the network DomainB belongs, respectively. However, in step S301, if another user of the enterprise additionally applies for creating a cloud desktop product, the user 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 routing instance, that is, the forwarding routing instance B, the virtual network card setting module 43 may set one virtual network card 3 in the virtual machine instance confirmed by the determining module 42, so as to connect to the virtual private cloud and the virtual private cloud created for the user.
Then, the virtual network card setting module 43 may further obtain a network list of the virtual machine instance that is confirmed by the confirmation module 42 to have been connected to the network. For example, as shown in fig. 1, in a case where two pairs of virtual network cards have been created in the virtual machine instance for two users, respectively, it can be acquired that the virtual machine instance has been connected to two networks, i.e., DomainA and DomainB. Specifically, in general, a forwarding routing instance may be created for each network, so that the virtual machine instance may be connected to the corresponding network by connecting a virtual network card therein to the forwarding routing instance.
Therefore, after the virtual network card setting module 43 sets the virtual network card 3, it may further acquire the forwarding routing instance to which the virtual machine instance is connected and the network information set therein, and may compare the network specified in the join instruction of the user received by the receiving module 41 with the network information in the network list thus acquired. For example, the comparison may confirm that the network specified in the instruction received by the receiving module 41 is actually set in the same second forwarding route instance as another network in the acquired network list. Thus, the virtual network card setting module 43 can multiplex the virtual network card connected to the second forwarding routing instance, which was previously set for the other network in the virtual machine instance, to constitute a pair of virtual network cards for the newly created virtual private cloud product together with the newly set virtual network card. Therefore, the cost for setting a new virtual network card for users of the same enterprise can be further saved.
In addition, in this embodiment, a domain name resolution setting module 44 may be further included, and configured to set 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.
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, the domain name resolution setting module 44 may set a domain name resolution proxy using named services, so that when a virtual private cloud and a network connecting virtual machine instances have the domain name resolution proxy as a target DNS, so that either party requests an address, the DNS proxy may acquire the address request and send back to the requesting party the address of the other party stored therein as a response, so that the requesting party may 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 the DNS traffic, so that when any party sends data, the DNS proxy may modify the IP field in the DNS data, thereby forwarding the traffic.
The virtual private cloud network configuration device provided by the embodiment of the application searches the existing virtual machine instance suitable for the virtual private cloud according to the received instruction for adding the virtual private cloud to the specified first network, so that two virtual network cards for the virtual private cloud are set in the found virtual machine instance, one for connecting the virtual machine instance and the virtual private cloud, and the other for connecting the virtual machine instance and a user-specified first network, so that existing virtual machine instances created for other virtual private clouds can be utilized to join the virtual private cloud to a specified network, multiple virtual private clouds can share one virtual machine instance by arranging multiple pairs of virtual network cards in one virtual machine instance, therefore, 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 influenced.
EXAMPLE five
The internal functions and structure of the virtual private cloud network configuration apparatus, which can be implemented as an electronic device, are described above. 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.
The memory 51 stores programs. In addition to the above-described programs, 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 so forth.
The memory 51 may be implemented by any type or combination of volatile or non-volatile memory devices, 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 disks.
The processor 52 is not limited to a processor (CPU), but may be a processing chip such as a Graphic Processing Unit (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 virtual private cloud network configuration method of the second or third embodiment.
Further, as shown in fig. 5, the electronic device may further include: communication components 53, power components 54, audio components 55, display 56, and other components. Only some of the components are schematically shown in fig. 5, and it is not meant that the electronic device comprises only the components shown in fig. 5.
The communication component 53 is configured to facilitate wired or wireless communication between the electronic device and other devices. 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 an 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 an exemplary embodiment, the communication component 53 further comprises a Near Field Communication (NFC) module to facilitate short-range communication. 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 component 54 provides power to the various components of the electronic device. The power components 54 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for an electronic device.
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 further be stored in the memory 51 or transmitted via the communication component 53. In some embodiments, audio assembly 55 also includes 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 an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.

Claims (10)

1. A virtual private cloud network configuration method includes:
receiving a joining instruction for joining the virtual private cloud to the first network;
determining a virtual machine instance suitable for 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 and the virtual private cloud, and the second virtual network card is used for connecting the virtual machine instance and a specified 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 matching 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 said determining that there is a second network in the list of networks that matches the first network comprises:
acquiring forwarding route instance information of forwarding route instances where each network in the network list is located;
and determining a network in the same forwarding route instance as the first network as the second network according to the forwarding route instance information.
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 flow 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 to the first network;
a determining module, configured to determine, according to the join instruction, a virtual machine instance applicable to the virtual private cloud, where the virtual machine instance at least includes a pair of virtual network cards created for other virtual private clouds;
and 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 specified first network.
7. The virtual private cloud network configuration appliance 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 configured to:
acquiring a network list to which the virtual machine instance is connected;
determining that a second network matching 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 executing the program stored in the memory to perform the virtual private cloud network configuration method of any 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.
CN202210210307.9A 2022-03-04 2022-03-04 Virtual private cloud network configuration method and device, electronic equipment and computer readable storage medium Active CN114844744B (en)

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 true CN114844744A (en) 2022-08-02
CN114844744B 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)

Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130036213A1 (en) * 2011-08-02 2013-02-07 Masum Hasan Virtual private clouds
US20130110993A1 (en) * 2011-10-21 2013-05-02 Huawei Technologies Co., Ltd. Method, apparatus and system for accessing virtual private network by virtual private cloud
CN103384255A (en) * 2011-12-31 2013-11-06 华为数字技术（成都）有限公司 Load balancing method, server and system for virtual machine cluster
US20130315242A1 (en) * 2012-05-22 2013-11-28 Huawei Technologies Co., Ltd. Network Communication Method and Device
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

Patent Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130036213A1 (en) * 2011-08-02 2013-02-07 Masum Hasan Virtual private clouds
US20130110993A1 (en) * 2011-10-21 2013-05-02 Huawei Technologies Co., Ltd. Method, apparatus and system for accessing virtual private network by virtual private cloud
CN103384255A (en) * 2011-12-31 2013-11-06 华为数字技术（成都）有限公司 Load balancing method, server and system for virtual machine cluster
US20130315242A1 (en) * 2012-05-22 2013-11-28 Huawei Technologies Co., Ltd. Network Communication Method and Device
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
CN114844744B (en) 2023-07-21

Similar Documents

Publication Publication Date Title
WO2020238751A1 (en) Resource access method under serverless architecture, device, system, and storage medium
CN111614738B (en) Service access method, device, equipment and storage medium based on Kubernetes cluster
US11218421B1 (en) Methods and systems for migrating virtual private cloud (VPC) resources across public cloud environments
CN109150677B (en) Cross-domain access processing method and device and electronic equipment
CN115002769B (en) Flow diversion method, core network element, electronic equipment and medium
CN104866976A (en) Multi-tenant-oriented information managing system
US20160380954A1 (en) Identification of employees on external social media
CN112202744B (en) Multi-system data communication method and device
CN204695386U (en) Towards the management information system of many tenants
CN114124944A (en) Data processing method and device of hybrid cloud and electronic equipment
US9674238B2 (en) Mobile content collaboration with one click multimedia capability
CN109660579B (en) Data processing method and system and electronic equipment
CN105763545A (en) BYOD method and device
CN111432359B (en) Communication system, method, device and storage medium
CN114844744B (en) Virtual private cloud network configuration method and device, electronic equipment and computer readable storage medium
WO2023024800A1 (en) Web-based interaction method and system for multiple terminal devices, and terminal device
CN112445602A (en) Resource scheduling method, device and system and electronic equipment
CN114499935B (en) Cloud platform access method, device, equipment and storage medium
CN112448985B (en) Distributed system, network processing method and device and electronic equipment
Ganchev et al. A cloud-based service recommendation system for use in UCWW
KR101495562B1 (en) Method And Apparatus for Providing Data Analysis Service
CN113923257A (en) Container group instance termination and creation method, device, electronic equipment and storage medium
CN114760360A (en) Request response method and device, electronic equipment and computer readable storage medium
CN112836201A (en) Method, device, equipment and computer readable medium for multi-platform information intercommunication
CN115484316B (en) File sharing method and device

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