WO2021135551A1 - 云主机多网卡配置方法、装置、设备及存储介质 - Google Patents

云主机多网卡配置方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2021135551A1
WO2021135551A1 PCT/CN2020/123238 CN2020123238W WO2021135551A1 WO 2021135551 A1 WO2021135551 A1 WO 2021135551A1 CN 2020123238 W CN2020123238 W CN 2020123238W WO 2021135551 A1 WO2021135551 A1 WO 2021135551A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
cloud host
domains
card
domain
Prior art date
Application number
PCT/CN2020/123238
Other languages
English (en)
French (fr)
Inventor
王鹏
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2021135551A1 publication Critical patent/WO2021135551A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0209—Architectural arrangements, e.g. perimeter networks or demilitarized zones
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
    • 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
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers

Definitions

  • This application relates to the field of cloud transmission technology, and in particular to a method, device, device, and storage medium for configuring multiple network cards of a cloud host.
  • Cloud services are the increase, use, and interaction modes of Internet-based related services, which usually involve the provision of dynamic, easily expandable and often virtualized resources through the Internet.
  • Cloud service refers to obtaining required services through the network in an on-demand and easily scalable manner.
  • network cards are an indispensable part of cloud hosts, and cloud hosts connect to the network through network cards.
  • the user cloud host has only one network card, and all the traffic of the cloud host passes through one network card, which exerts pressure on the load of the network card itself. , And cannot achieve flow separation.
  • the present application provides a method, device, device, and storage medium for configuring a cloud host with multiple network cards, which can achieve the purpose of improving application availability, making the cloud host more abundant in application scenarios, and covering various services in the data center.
  • a technical solution adopted in this application is to provide a cloud host multi-network card configuration method, the cloud host includes at least one network card, and the cloud host multi-network card configuration method includes:
  • the network domains include at least one designated IP address, and the IP addresses in different network domains are different;
  • the network cards are configured for the at least two network domains, so that there is one and only one network card in the same network domain.
  • the configuring the network card so that there is and only one of the network cards in the network domain includes:
  • the network card is added to the subnet of the network domain, so that there is one and only one network card in the network domain.
  • the configuring the network card so that there is and only one of the network cards in the network domain includes:
  • Configuring at least one security group for the cloud host the security group including a designated network policy, and the cloud hosts assigned to the security group follow the network policy;
  • the network card is added to the subnet of the network domain, and the security group in the network domain is selected and assigned to the network card, so that there is one and only one network card in the network domain.
  • the subnet with a mask of 22 to 26 digits can be created under each of the network domains.
  • the cloud host supports the creation of at most 3 network domains.
  • the network domain includes one or more of a quarantine area, an internal service area, and a partner area
  • the cloud host located in the quarantine area has access rights to public network products
  • the cloud host located in the internal service area does not have access rights to public network products
  • the cloud host located in the partner area has access rights to use dedicated line services and partners.
  • the cloud host is configured with at most three network cards.
  • a technical solution adopted by this application is to provide a cloud host multi-network card configuration device, including:
  • a network configuration module configured to configure at least two network domains for the cloud host, the network domains include at least one designated IP address, and the IP addresses in different network domains are different;
  • the network card configuration module is used to configure network cards for the at least two network domains, so that there is one and only one network card in the same network domain.
  • a technical solution adopted in this application is to provide a cloud host multi-network card configuration device, the cloud host multi-network card configuration device including a processor and a memory coupled to the processor, wherein ,
  • the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the processor executes the following steps:
  • the network domains include at least one designated IP address, and the IP addresses in different network domains are different;
  • the network cards are configured for the at least two network domains, so that there is one and only one network card in the same network domain.
  • a technical solution adopted by this application is to provide a storage medium storing computer-readable instructions.
  • the computer-readable instructions are executed by one or more processors, one or Multiple processors perform the following steps:
  • the network domains include at least one designated IP address, and the IP addresses in different network domains are different;
  • the network cards are configured for the at least two network domains, so that there is one and only one network card in the same network domain.
  • the method, device, device, and storage medium for configuring multiple network cards of a cloud host proposed in this application implements the configuration of multiple network cards for one cloud host by configuring network domains and configuring multiple network cards to different network domains. Users can freely add multiple network cards according to their own application needs.
  • Block network card from the original single network card to multiple network cards, can realize the distributed horizontal expansion of services and high availability of applications, making the cloud host applicable to more diverse scenarios, covering various services in the data center, and improving user experience And satisfaction.
  • FIG. 1 is a schematic flowchart of a method for configuring multiple network cards of a cloud host according to an embodiment of the present application
  • FIG. 2 is a schematic diagram of the configuration of the first embodiment of the cloud host multi-network card configuration method described in FIG. 1;
  • FIG. 3 is a schematic diagram of the configuration of the second embodiment of the cloud host multi-network card configuration method described in FIG. 1;
  • FIG. 4 is a schematic structural diagram of a cloud host multi-network card configuration device according to an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a cloud host multi-network card configuration device according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a storage medium according to an embodiment of the present application.
  • Figure 1 is a schematic flow chart of a method for configuring multiple network cards for a cloud host according to an embodiment of the present application.
  • the method for configuring multiple network cards for a cloud host can be run on a local server, a remote server, or a remote cloud platform.
  • the server or the remote cloud platform can communicate with the user terminal through a wireless network such as WIFI or a wired network such as Ethernet.
  • the user terminal may be any terminal that can be operated by the user, such as a mobile phone, a tablet computer, a notebook, and the like. It should be noted that if there is substantially the same result, the user can apply to the server for the cloud host through the client terminal.
  • the cloud host is configured with a network card by default.
  • the method of this application is not based on the method shown in Figure 1.
  • the sequence of the processes shown is limited. As shown in Figure 1, the method includes steps:
  • Step S101 Configure at least two network domains for the cloud host, the network domains include at least one designated IP address, and the IP addresses in different network domains are different.
  • the network domain refers to a collection of IP addresses with the same network access authority, and the hosts, computing services, etc. in the network domain all have the same network access authority. Users can configure the network domain according to their own application needs, and specify an IP address for the network domain, and the IP addresses in different network domains are different.
  • the cloud host supports the creation of at most 3 network domains.
  • the network domain includes one or more of a demilitarized zone (DMZ, Demilitarized Zone), an internal service zone (SF, Server Farm Zone), and a partner zone (PTR, Partner Zone), wherein the isolated zone ( DMZ (Demilitarized Zone) is to solve the problem that users from the external network cannot access the internal network server after the firewall is installed, and a buffer between the non-secure system and the security system is established.
  • the buffer is located in the small network area between the internal network and the external network of the enterprise. In this small network area, some server facilities that must be public can be placed, such as corporate Web servers, FTP servers, and forums.
  • the internal service zone (SF, Server Farm Zone) is similar in function to the demilitarized zone (DMZ, Demilitarized Zone).
  • the internal service zone (SF, Server Farm Zone) is a security zone set up, which can be located in the internal network of the enterprise.
  • the cloud host located in the internal service area (SF, Server Farm Zone) does not have access rights for public network products, and can only access the internal network.
  • the partner zone (PTR, Partner Zone) is also a buffer between the non-secure system and the secure system to solve the problem that users from the external network cannot access the internal network server after the firewall is installed.
  • the zone is only for the private line business of partners, and the cloud host located in the partner zone (PTR, Partner Zone) has access rights to use private line services and partners.
  • Step S102 Configure network cards for the at least two network domains, so that there is one and only one network card in the same network domain.
  • the network domain may correspond to the network card one-to-one.
  • one network card may be configured in different network domains, so that the cloud host has and only has one network card in the same network domain. There is a said network card.
  • the cloud host is configured with at most three network cards, and the three network cards respectively correspond to the three network domains.
  • the configuration of network cards for the at least two network domains includes the following steps:
  • Step S1 Divide at least one subnet in each of the network domains.
  • the subnet is to divide the network domain into smaller networks, thereby reducing the waste of IP addresses, saving IP address resources, and optimizing network performance.
  • the subnet with a mask of 22 to 26 digits can be created under each network domain, and the mask is used to indicate which bits of the IP address identify the host
  • the subnet where the host is located, and which bits identify the bit mask of the host, and the relationship between the subnet where the host is located and other networks can be calculated through the subnet mask to enable correct communication. For example, if the subnet mask is 26 bits, the mask is 255.255.255.192.
  • Figure 2 is a schematic diagram of the configuration of the first embodiment of the cloud host multi-NIC configuration method described in Figure 1; the following example illustrates the division of the subnets.
  • the network segment with an IP address of 10.32.26 is designated as a network Domain 1.
  • the subnet mask uses 26 bits, the subnet mask is 255.255.255.192. Therefore, a subnet 1 can be divided under network domain 1. 10.32.26.128/26, divide a subnet 2 under the network domain 2 into 10.33.23.128/26.
  • Step S2 Add the network card to the subnet of the network domain, so that there is one and only one network card in the network domain.
  • the network card of the cloud host may be configured in the subnet under the network domain, and there is only one network card in the network domain.
  • network card 1 when the cloud host needs to configure two network cards: network card 1, network card 2, configure network card 1 to subnet 1: 10.32.26.128/26, and configure the IP address of network card 1 to 10.32. 26.130, configure NIC 2 to subnet 2: 10.33.23.128/26, and configure the IP address of NIC 2 to 10.33.23.130, then the configuration of NIC 1 and NIC 2 can be completed. After completing the configuration of the network card, the network card can be configured in the cloud host, so that the traffic of multiple network cards is separated, which plays a role of traffic separation, cluster construction, failover, heartbeat detection, and the like.
  • the configuring network cards for the at least two network domains includes the following steps:
  • Step S1' Configure at least one security group for the cloud host, the security group including a designated network policy, and the cloud hosts allocated to the security group follow the network policy.
  • the cloud host may be configured with at least one security group, the security group including a specified network policy, and the cloud host assigned to the security group needs to follow the network policy, and then While ensuring the network communication of the cloud host, the network security of the cloud host is further improved.
  • Step S2' Assign the security group to the network domain, and add the network card to the subnet of the network domain, and select the security group in the network domain to be assigned to all
  • the network card is such that there is and only one network card in the network domain.
  • users can select a security group that meets their security requirements while configuring the network card to join, that is, assign the security group to the network domain, and add the network card to all of the network domain.
  • the security group in the network domain is selected and assigned to the network card at the same time, so that there is one and only one network card in the network domain.
  • Figure 3 is a schematic diagram of the configuration of the second embodiment of the cloud host multi-network card configuration method described in Figure 1.
  • the user can configure multiple security groups according to their own business needs, such as Security group 1, security group 2, security group 3, security group 4, etc., each of the security groups corresponds to a different network strategy.
  • network card 1 When the cloud host needs to be configured with two network cards: network card 1, network card 2, set network card 1 Configure to subnet 1: 10.32.26.128/26, and configure the IP address of NIC 1 to 10.32.26.130, specify that NIC 1 belongs to security group 2, and configure NIC 2 to subnet 2: 10.33.23.128/26, And configure the IP address of NIC 2 to 10.33.23.130, and specify that NIC 2 belongs to security group 4, then the configuration of NIC 1 and NIC 2 can be completed. After completing the configuration of the network card, the network card can be configured in the cloud host, so that the traffic of multiple network cards is separated, which plays a role of traffic separation, cluster construction, failover, heartbeat detection, and the like.
  • the method for configuring multiple network cards of a cloud host realizes the configuration of multiple network cards for one cloud host by configuring network domains and configuring multiple network cards to different network domains. Users can freely add multiple network cards according to their own application needs.
  • the original single network card is upgraded to multiple network cards, which can realize distributed horizontal expansion of services and high availability of applications, making cloud host application scenarios more abundant, covering various services in the data center, and improving user experience and satisfaction.
  • the network domain by dividing the network domain into an isolated area, an internal service area, and a partner area, reasonable configuration of network permissions can be realized, and user experience and satisfaction can be further improved.
  • FIG. 4 is a schematic structural diagram of a cloud host multi-network card configuration device 1 according to an embodiment of the present application. As shown in FIG. 4, the cloud host multi-network card configuration device 1 includes a network configuration module 10 and a network card configuration module 11.
  • the network configuration module 10 is configured to configure at least two network domains for the cloud host, the network domain includes at least one designated IP address, and the IP addresses in different network domains are different; wherein, the network domain Refers to a collection of IP addresses with the same network access authority, and hosts, computing services, etc. in the network domain all have the same network access authority. Users can configure the network domain according to their own application needs, and specify an IP address for the network domain, and the IP addresses in different network domains are different.
  • the cloud host supports the creation of at most 3 network domains.
  • the network domain includes one or more of a demilitarized zone (DMZ, Demilitarized Zone), an internal service zone (SF, Server Farm Zone), and a partner zone (PTR, Partner Zone), wherein the isolated zone ( DMZ (Demilitarized Zone) is to solve the problem that users from the external network cannot access the internal network server after the firewall is installed, and a buffer between the non-secure system and the security system is established.
  • the buffer is located in the small network area between the internal network and the external network of the enterprise. In this small network area, some server facilities that must be public can be placed, such as corporate Web servers, FTP servers, and forums.
  • the internal service zone (SF, Server Farm Zone) is similar in function to the demilitarized zone (DMZ, Demilitarized Zone).
  • the internal service zone (SF, Server Farm Zone) is a security zone set up, which can be located in the internal network of the enterprise.
  • the cloud host located in the internal service area (SF, Server Farm Zone) does not have access rights for public network products, and can only access the internal network.
  • the partner zone (PTR, Partner Zone) is also a buffer zone between the non-secure system and the security system to solve the problem that users from the external network cannot access the internal network server after the firewall is installed.
  • the buffer zone is only for the private line business of the partner, and the cloud host located in the partner zone (PTR, Partner Zone) has the access right to use the private line service and the partner.
  • the network card configuration module 11 is configured to configure network cards for the at least two network domains, so that there is one and only one network card in the same network domain. Specifically, different network cards may be configured in different network domains, so that the cloud host has and only one network card in the same network domain. According to an embodiment of the present application, the cloud host is configured with at most three network cards, and the three network cards correspond to the three network domains. Further, the network card configuration module 11 is also used to divide at least one subnet in each of the network domains. The subnet divides the network domain into smaller networks, which can reduce the waste of IP addresses, save IP address resources, and optimize network performance.
  • the subnet with a mask of 22 to 26 digits can be created under each network domain, and the mask is used to indicate which bits of the IP address identify the host The subnet where the host is located, and which bits identify the bit mask of the host, and the relationship between the subnet where the host is located and other networks can be calculated through the subnet mask to enable correct communication.
  • the network card configuration module 11 is configured to configure at least one security group for the cloud host.
  • the security group includes a specified network policy and is assigned to the cloud in the security group.
  • the host complies with the network policy.
  • the cloud host may be configured with at least one security group, the security group including a specified network policy, and the cloud host assigned to the security group needs to follow the network policy, and While further ensuring the network communication of the cloud host, the network security of the cloud host is improved.
  • the security group is assigned to the network domain, and the network card is added to the subnet of the network domain, and the security group in the network domain is selected and assigned to the network card , So that there is one and only one network card in the network domain.
  • users can select a security group that meets their security requirements while configuring the network card to join, that is, assign the security group to the network domain, and add the network card to all of the network domain.
  • the security group in the network domain is selected and assigned to the network card at the same time, so that there is only one network card in the network domain
  • FIG. 5 is a schematic structural diagram of a cloud host multi-network card configuration device 30 according to an embodiment of the present application.
  • the cloud host multi-network card configuration device 30 includes a memory 32, a processor 31, and a computer program stored on the memory 32 and running on the processor 31, and the processor 31 executes
  • the computer program implements the following steps: configure at least two network domains for the cloud host, the network domains include at least one designated IP address, and the IP addresses in different network domains are different; and At least two network domains are configured with network cards, so that there is and only one of the network cards in the same network domain.
  • the configuring the network card so that there is and only one of the network card in the network domain includes: dividing at least one subnet in each of the network domains; and adding the network card to In the subnet to the network domain, there is one and only one network card in the network domain.
  • the configuring the network card so that there is and only one of the network cards in the network domain includes: configuring at least one security group for the cloud host, the security group including a specified network policy , The cloud host assigned to the security group follows the network policy; assigns the security group to the network domain; and adds the network card to the subnet of the network domain, And selecting the security group in the network domain and assigning it to the network card, so that there is one and only one network card in the network domain.
  • the subnet with a mask of 22 to 26 digits can be created under each of the network domains.
  • the cloud host supports the creation of at most 3 network domains.
  • the network domain includes one or more of a quarantine area, an internal service area, and a partner area
  • the cloud host located in the quarantine area has access rights to public network products
  • the cloud host located in the internal service area does not have access rights to public network products
  • the cloud host located in the partner area has access rights to use dedicated line services and partners.
  • the cloud host is configured with at most three network cards.
  • FIG. 6 is a schematic structural diagram of a storage medium according to an embodiment of the present application.
  • a storage medium storing computer-readable instructions 41.
  • the one or more processors When the computer-readable instructions 41 are executed by one or more processors, the one or more processors perform the following steps: configure at least Two network domains, the network domains include at least one designated IP address, and the IP addresses in different network domains are different; and the network cards are configured for the at least two network domains so that there are and There is only one said network card.
  • the storage medium may be non-volatile or volatile.
  • the configuring the network card so that there is and only one of the network card in the network domain includes: dividing at least one subnet in each of the network domains; and adding the network card to In the subnet to the network domain, there is one and only one network card in the network domain.
  • the configuring the network card so that there is and only one of the network cards in the network domain includes: configuring at least one security group for the cloud host, the security group including a specified network policy , The cloud host assigned to the security group follows the network policy; assigns the security group to the network domain; and adds the network card to the subnet of the network domain, And selecting the security group in the network domain and assigning it to the network card, so that there is one and only one network card in the network domain.
  • the subnet with a mask of 22 to 26 digits can be created under each of the network domains.
  • the cloud host supports the creation of at most 3 network domains.
  • the network domain includes one or more of a quarantine area, an internal service area, and a partner area
  • the cloud host located in the quarantine area has access rights to public network products
  • the cloud host located in the internal service area does not have access rights to public network products
  • the cloud host located in the partner area has access rights to use dedicated line services and partners.
  • the cloud host is configured with at most three network cards.
  • the computer program can be stored in a computer readable storage medium, and the program can be stored in a computer readable storage medium. When executed, it may include the procedures of the above-mentioned method embodiments.
  • the aforementioned storage medium may be a magnetic disk, an optical disk, or a read-only storage memory (Read-Only Memory, ROM) and other non-volatile storage media, or random storage memory (Random Access Memory, RAM) etc.

Landscapes

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

Abstract

本申请涉及云计算技术领域，尤其涉及一种云主机多网卡配置方法、装置、设备及存储介质，所述云主机包括至少一张网卡，所述云主机多网卡配置方法包括：为所述云主机配置至少两个网络域，所述网络域包括至少一个指定的IP地址，不同所述网络域中的所述IP地址不同；及为所述至少两个网络域配置网卡，使同一所述网络域内有且仅有一张所述网卡。本申请能够达到提高应用可用性，使得云主机适用场景更丰富，可覆盖到数据中心的各项业务的目的。

Description

云主机多网卡配置方法、装置、设备及存储介质
本申请以2020年7月20日提交的申请号为202010697531.6，发明名称为“云主机多网卡配置方法、装置、设备及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及云传输技术领域，尤其涉及一种云主机多网卡配置方法、装置、设备及存储介质。
 背景技术
云服务是基于互联网的相关服务的增加、使用和交互模式，通常涉及通过互联网来提供动态易扩展且经常是虚拟化的资源。云服务指通过网络以按需、易扩展的方式获得所需服务。随着科技的发展，现在越来越多用户使用更易扩展，成本更低的云主机替代本地计算机，对于云主机而言，网卡是云主机不可或缺的组成部分，云主机通过网卡连接网络。
发明人意识到传统的云主机只能使用一块网卡，当用户的应用需要搭建集群时，用户云主机只有一块网卡，云主机所有的流量都通过一块网卡，在对网卡本身的负载产生压力的同时，也无法做到流量分离。
因此，如何在云主机上配置多张网卡，从而提高应用的高可用性，使得云主机适用场景更丰富，可覆盖到数据中心的各项业务是用户的迫切需求。
 技术问题
本申请提供一种云主机多网卡配置方法、装置、设备及存储介质，能够达到提高应用可用性，使得云主机适用场景更丰富，可覆盖到数据中心的各项业务的目的。
 技术解决方案
为解决上述技术问题，本申请采用的一个技术方案是：提供一种云主机多网卡配置方法，所述云主机包括至少一张网卡，所述云主机多网卡配置方法包括：
为所述云主机配置至少两个网络域，所述网络域包括至少一个指定的IP地址，不同所述网络域中的所述IP地址不同；及
为所述至少两个网络域配置网卡，使同一所述网络域内有且仅有一张所述网卡。
根据本申请的一种实施例，所述配置网卡，使所述网络域内有且仅有一个所述网卡，包括：
在每个所述网络域中划分至少一个子网；及
将所述网卡加入到所述网络域的所述子网中，使所述网络域内有且仅有一个所述网卡。
根据本申请的一种实施例，所述配置网卡，使所述网络域内有且仅有一个所述网卡，包括：
为所述云主机配置至少一个安全组，所述安全组包括指定的网络策略，分配到所述安全组中的所述云主机遵循所述网络策略；
将所述安全组分配到所述网络域中；及
将所述网卡加入到所述网络域的所述子网中，并选择所述网络域中的所述安全组分配给所述网卡，使所述网络域内有且仅有一个所述网卡。
根据本申请的一种实施例，每个所述网络域下可创建22到26位数掩码的所述子网。
根据本申请的一种实施例，所述云主机支持创建至多3个所述网络域。
根据本申请的一种实施例，所述网络域包括隔离区、内部服务区及合作伙伴区中的一个或者多个，位于所述隔离区内的所述云主机拥有公网类产品的访问权限，位于所述内部服务区的所述云主机没有公网类产品的访问权限，位于所述合作伙伴区的所述云主机拥有使用专线服务与合作伙伴的访问权限。
根据本申请的一种实施例，所述云主机至多配置三张网卡。
此外，为解决上述技术问题，本申请还采用的一个技术方案是：提供一种云主机多网卡配置装置，包括：
网络配置模块，用于为所述云主机配置至少两个网络域，所述网络域包括至少一个指定的IP地址，不同所述网络域中的所述IP地址不同；
网卡配置模块，用于为所述至少两个网络域配置网卡，使同一所述网络域内有且仅有一张所述网卡。
此外，为解决上述技术问题，本申请还采用的一个技术方案是：提供一种云主机多网卡配置设备，该云主机多网卡配置设备包括处理器、与所述处理器耦接的存储器，其中，所述存储器中存储有计算机可读指令，所述计算机可读指令被所述处理器执行时，使得所述处理器执行如下步骤：
为所述云主机配置至少两个网络域，所述网络域包括至少一个指定的IP地址，不同所述网络域中的所述IP地址不同；及
为所述至少两个网络域配置网卡，使同一所述网络域内有且仅有一张所述网卡。
此外，为解决上述技术问题，本申请还采用的一个技术方案是：提供一种存储有计算机可读指令的存储介质，所述计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行如下步骤：
为所述云主机配置至少两个网络域，所述网络域包括至少一个指定的IP地址，不同所述网络域中的所述IP地址不同；及
为所述至少两个网络域配置网卡，使同一所述网络域内有且仅有一张所述网卡。
 有益效果
本申请提出的云主机多网卡配置方法、装置、设备及存储介质，通过配置网络域并将多张网卡配置到不同网络域实现一个云主机配置多张网卡，用户可以根据自身应用需要自由添加多块网卡，从原来的单一一块网卡提高为多块网卡，可实现业务的分布式横向扩展及应用的高可用性，使得云主机适用场景更丰富，可覆盖到数据中心的各项业务，提高用户体验和满意度。
 附图说明
图1是本申请一种实施例的云主机多网卡配置方法的流程示意图；
图2是图1所述云主机多网卡配置方法第一种实施例配置示意图；
图3是图1所述云主机多网卡配置方法第二种实施例配置示意图；
图4是本申请一种实施例的云主机多网卡配置装置的结构示意图；
图5是本申请一种实施例的云主机多网卡配置设备的结构示意图；
图6是本申请一种实施例的存储介质的结构示意图。
 本发明的实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅是本申请的一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
在本文中提及“实施例”意味着，结合实施例描述的特定特征、结构或特性可以包含在本申请的至少一个实施例中。在说明书中的各个位置出现该短语并不一定均是指相同的实施例，也不是与其它实施例互斥的独立的或备选的实施例。本领域技术人员显式地和隐式地理解的是，本文所描述的实施例可以与其它实施例相结合。
图1是本申请一种实施例的云主机多网卡配置方法的流程示意图，所述云主机多网卡配置方法可以运行于本地服务器、远程服务器或远程云平台上，所述本地服务器、所述远程服务器或所述远程云平台通过WIFI等无线网络或者以太网等有线网络可以与用户端通信，所述用户端可以是能够提供被用户操作的任意终端，例如为手机、平板电脑、笔记本等。需注意的是，若有实质上相同的结果，用户通过所述用户端可以向所述服务器申请所述云主机，所述云主机默认配置一张网卡，本申请的方法并不以图1所示的流程顺序为限。如图1所示，该方法包括步骤：
步骤S101：为所述云主机配置至少两个网络域，所述网络域包括至少一个指定的IP地址，不同所述网络域中的所述IP地址不同。
其中，所述网络域是指具有相同网络访问权限的IP地址的集合，处于所述网络域中的主机、计算服务等均具有相同的网络访问权限。用户可以根据自身应用需要配置所述网络域，并为所述网络域指定IP地址，不同所述网络域中的所述IP地址不同。
根据本申请的一种实施例，所述云主机支持创建至多3个所述网络域。其中，所述网络域包括隔离区（DMZ，Demilitarized Zone）、内部服务区（SF，Server Farm Zone）及合作伙伴区（PTR，Partner Zone）中的一个或者多个，其中，所述隔离区（DMZ，Demilitarized Zone）是为了解决安装防火墙后外部网络的访问用户不能访问内部网络服务器的问题，而设立的一个非安全***与安全***之间的缓冲区。该缓冲区位于企业内部网络和外部网络之间的小网络区域内。在这个小网络区域内可以放置一些必须公开的服务器设施，如企业Web服务器、FTP服务器和论坛等。另一方面，通过这样一个隔离区（DMZ，Demilitarized Zone），更加有效地保护了内部网络，故位于所述隔离区（DMZ，Demilitarized Zone）内的所述云主机拥有公网类产品的访问权限。所述内部服务区（SF，Server Farm Zone）与所述隔离区（DMZ，Demilitarized Zone）功能相似，内部服务区（SF，Server Farm Zone）是设立的一个安全区域，可以是位于企业内部网络，位于所述内部服务区（SF，Server Farm Zone）的所述云主机没有公网类产品的访问权限，只能访问内部网络。所述合作伙伴区（PTR，Partner Zone）也是为了解决安装防火墙后外部网络的访问用户不能访问内部网络服务器的问题，而设立的一个非安全***与安全***之间的缓冲区，但是所述缓冲区仅针对合作伙伴的专线业务，位于所述合作伙伴区（PTR，Partner Zone）的所述云主机拥有使用专线服务与合作伙伴的访问权限。通过划分网络域可以合理规划网络权限和IP地址划分。
步骤S102：为所述至少两个网络域配置网卡，使同一所述网络域内有且仅有一张所述网卡。
所述网络域可以与所述网卡一一对应，对于一台所述云主机在不同所述网络域中均可以配置一张所述网卡，使所述云主机在同一所述网络域内有且仅有一张所述网卡。根据本申请的一种实施例，所述云主机至多配置三张网卡，三张所述网卡分别对应三个所述网络域。
具体的，所述为所述至少两个网络域配置网卡包括以下步骤：
步骤S1：在每个所述网络域中划分至少一个子网。
所述子网就是把所述网络域划分成更小的网络，从而可以减少IP地址的浪费，节约IP地址资源，优化网络性能。
根据本申请的一种实施例，每个所述网络域下可创建22到26位数掩码的所述子网，所述掩码是一种用来指明IP地址的哪些位标识的是主机所在的子网，以及哪些位标识的是主机的位掩码，通过子网掩码计算出主机所在的子网与其他网络的关系才能进行正确的通信。例如子网掩码为26位，则掩码为255.255.255.192。
请参阅图2，图2是图1所述云主机多网卡配置方法第一种实施例配置示意图；下面举例说明所述子网的划分，例如，指定IP地址为10.32.26.0的网段为网络域1，指定IP地址为10.33.23.0的网段为网络域2，子网掩码采用26位，则子网掩码为255.255.255.192，因此，可以在网络域1下划分一个子网1为10.32.26.128/26，在网络域2下划分一个子网2为10.33.23.128/26。
步骤S2：将所述网卡加入到所述网络域的所述子网中，使所述网络域内有且仅有一个所述网卡。
在步骤S2中，可以将所述云主机的所述网卡配置到所述网络域下的所述子网中，并且使所述网络域内有且仅有一个所述网卡。
接上述实施例举例，当所述云主机需要配置两张网卡：网卡1、网卡2时，将网卡1配置到子网1： 10.32.26.128/26中，并且配置网卡1的IP地址为10.32.26.130，将网卡2配置到子网2：10.33.23.128/26中，并且配置网卡2的IP地址为10.33.23.130，则可以完成网卡1、网卡2的配置。完成所述网卡配置，就可在所述云主机里面对所述网卡进行配置，使得多张所述网卡流量分离，起到流量分离、集群搭建、故障转移、心跳检测等的作用。
根据本申请的另一种实施例，所述为所述至少两个网络域配置网卡包括以下步骤：
步骤S1’： 为所述云主机配置至少一个安全组，所述安全组包括指定的网络策略，分配到所述安全组中的所述云主机遵循所述网络策略。
根据本申请的一种实施例，所述云主机可以配置至少一个安全组，所述安全组包括指定的网络策略，分配到所述安全组中的所述云主机需要遵循所述网络策略，进而可以保证所述云主机网络通信的同时，进一步提升了所述云主机的网络安全。
步骤S2’：将所述安全组分配到所述网络域中，及将所述网卡加入到所述网络域的所述子网中，并选择所述网络域中的所述安全组分配给所述网卡，使所述网络域内有且仅有一个所述网卡。
用户可以通过网络安全需要，在配置所述网卡的同时选择满足其安全需求的安全组加入，即将所述安全组分配到所述网络域中，及将所述网卡加入到所述网络域的所述子网中时，同时选择所述网络域中的所述安全组分配给所述网卡，使所述网络域内有且仅有一个所述网卡。
请参阅图3 ，图3是图1所述云主机多网卡配置方法第二种实施例配置示意图，接上述实施例的举例进行说明，用户可以根据自身业务需求配置多个所述安全组，如安全组1、安全组2、安全组3、安全组4等，每个所述安全组对应的网络策略不同，当所述云主机需要配置两张网卡：网卡1、网卡2时，将网卡1配置到子网1： 10.32.26.128/26中，并且配置网卡1的IP地址为10.32.26.130，同时指定网卡1属于安全组2，将网卡2配置到子网2：10.33.23.128/26中，并且配置网卡2的IP地址为10.33.23.130，同时指定网卡2属于安全组4，则可以完成网卡1、网卡2的配置。完成所述网卡配置，就可在所述云主机里面对所述网卡进行配置，使得多张所述网卡流量分离，起到流量分离、集群搭建、故障转移、心跳检测等的作用。
本申请一种实施例的云主机多网卡配置方法，通过配置网络域并将多张网卡配置到不同网络域实现一个云主机配置多张网卡，用户可以根据自身应用需要自由添加多块网卡，从原来的单一一块网卡提高为多块网卡，可实现业务的分布式横向扩展及应用的高可用性，使得云主机适用场景更丰富，可覆盖到数据中心的各项业务，提高用户体验和满意度。
进一步地，通过在网络域中划分子网、配置安全组等方法实现多网卡配置，提高了网络策略的多样性，用户可以根据实际应用所需的网络策略选择合适的配置，提高用户体验和满意度。
进一步地，通过划分网络域为隔离区、内部服务区及合作伙伴区可以实现网络权限的合理配置，进一步提高用户体验和满意度。
图4是本申请一种实施例的云主机多网卡配置装置1的结构示意图。如图4所示，所述云主机多网卡配置装置1包括网络配置模块10，网卡配置模块11。
网络配置模块10，用于为所述云主机配置至少两个网络域，所述网络域包括至少一个指定的IP地址，不同所述网络域中的所述IP地址不同；其中，所述网络域是指具有相同网络访问权限的IP地址的集合，处于所述网络域中的主机、计算服务等均具有相同的网络访问权限。用户可以根据自身应用需要配置所述网络域，并为所述网络域指定IP地址，不同所述网络域中的所述IP地址不同。
根据本申请的一种实施例，所述云主机支持创建至多3个所述网络域。其中，所述网络域包括隔离区（DMZ，Demilitarized Zone）、内部服务区（SF，Server Farm Zone）及合作伙伴区（PTR，Partner Zone）中的一个或者多个，其中，所述隔离区（DMZ，Demilitarized Zone）是为了解决安装防火墙后外部网络的访问用户不能访问内部网络服务器的问题，而设立的一个非安全***与安全***之间的缓冲区。该缓冲区位于企业内部网络和外部网络之间的小网络区域内。在这个小网络区域内可以放置一些必须公开的服务器设施，如企业Web服务器、FTP服务器和论坛等。另一方面，通过这样一个隔离区（DMZ，Demilitarized Zone），更加有效地保护了内部网络，故位于所述隔离区（DMZ，Demilitarized Zone）内的所述云主机拥有公网类产品的访问权限。所述内部服务区（SF，Server Farm Zone）与所述隔离区（DMZ，Demilitarized Zone）功能相似，内部服务区（SF，Server Farm Zone）是设立的一个安全区域，可以是位于企业内部网络，位于所述内部服务区（SF，Server Farm Zone）的所述云主机没有公网类产品的访问权限，只能访问内部网络。所述合作伙伴区（PTR，Partner Zone）也是为了解决安装防火墙后外部网络的访问用户不能访问内部网络服务器的问题，而设立的一个非安全***与安全***之间的缓冲区。但是所述缓冲区仅针对合作伙伴的专线业务，位于所述合作伙伴区（PTR，Partner Zone）的所述云主机拥有使用专线服务与合作伙伴的访问权限。通过划分网络域可以合理规划网络权限和IP地址划分。
网卡配置模块11，用于为所述至少两个网络域配置网卡，使同一所述网络域内有且仅有一张所述网卡。具体的，不同所述网络域中可以配置不同的所述网卡，使所述云主机在同一所述网络域内有且仅有一张所述网卡。根据本申请的一种实施例，所述云主机至多配置三张网卡，三张所述网卡对应三个所述网络域。进一步地，所述网卡配置模块11还用于在每个所述网络域中划分至少一个子网。所述子网就把所述网络域划分成更小的网络，可以减少IP地址的浪费，节约IP地址资源，优化网络性能。根据本申请的一种实施例，每个所述网络域下可创建22到26位数掩码的所述子网，所述掩码是一种用来指明IP地址的哪些位标识的是主机所在的子网，以及哪些位标识的是主机的位掩码，通过子网掩码计算出主机所在的子网与其他网络的关系才能进行正确的通信。
根据本申请的另一种实施例，所述网卡配置模块11用于为所述云主机配置至少一个安全组，所述安全组包括指定的网络策略，分配到所述安全组中的所述云主机遵循所述网络策略。根据本申请的一种实施例，所述云主机可以配置至少一个安全组，所述安全组包括指定的网络策略，分配到所述安全组中的所述云主机需要遵循所述网络策略，可以进一步保证所述云主机网络通信的同时，提升了所述云主机的网络安全。同时，将所述安全组分配到所述网络域中，及将所述网卡加入到所述网络域的所述子网中，并选择所述网络域中的所述安全组分配给所述网卡，使所述网络域内有且仅有一个所述网卡。用户可以通过网络安全需要，在配置所述网卡的同时选择满足其安全需求的安全组加入，即将所述安全组分配到所述网络域中，及将所述网卡加入到所述网络域的所述子网中时，同时选择所述网络域中的所述安全组分配给所述网卡，使所述网络域内有且仅有一个所述网卡
可以理解的是，上述装置的各模块实现各功能的具体方式可参阅上述实施例对应的具体步骤，故在此不作赘述。
请参阅图5，图5是本申请一种实施例的云主机多网卡配置设备30的结构示意图。如图5所示，所述云主机多网卡配置设备30包括存储器32、处理器31及存储在所述存储器32上并可在所述处理器31上运行的计算机程序，所述处理器31执行所述计算机程序时实现以下步骤：为所述云主机配置至少两个网络域，所述网络域包括至少一个指定的IP地址，不同所述网络域中的所述IP地址不同；及为所述至少两个网络域配置网卡，使同一所述网络域内有且仅有一张所述网卡。
根据本申请的一种实施例，所述配置网卡，使所述网络域内有且仅有一个所述网卡，包括：在每个所述网络域中划分至少一个子网；及将所述网卡加入到所述网络域的所述子网中，使所述网络域内有且仅有一个所述网卡。
根据本申请的一种实施例，所述配置网卡，使所述网络域内有且仅有一个所述网卡，包括：为所述云主机配置至少一个安全组，所述安全组包括指定的网络策略，分配到所述安全组中的所述云主机遵循所述网络策略；将所述安全组分配到所述网络域中；及将所述网卡加入到所述网络域的所述子网中，并选择所述网络域中的所述安全组分配给所述网卡，使所述网络域内有且仅有一个所述网卡。
根据本申请的一种实施例，每个所述网络域下可创建22到26位数掩码的所述子网。
根据本申请的一种实施例，所述云主机支持创建至多3个所述网络域。
根据本申请的一种实施例，所述网络域包括隔离区、内部服务区及合作伙伴区中的一个或者多个，位于所述隔离区内的所述云主机拥有公网类产品的访问权限，位于所述内部服务区的所述云主机没有公网类产品的访问权限，位于所述合作伙伴区的所述云主机拥有使用专线服务与合作伙伴的访问权限。
根据本申请的一种实施例，所述云主机至多配置三张网卡。
参阅图6，图6是本申请一种实施例的存储介质的结构示意图。如图6所示存储有计算机可读指令41的存储介质，该计算机可读指令41被一个或多个处理器执行时，使得一个或多个处理器执行以下步骤：为所述云主机配置至少两个网络域，所述网络域包括至少一个指定的IP地址，不同所述网络域中的所述IP地址不同；及为所述至少两个网络域配置网卡，使同一所述网络域内有且仅有一张所述网卡。所述存储介质可以是非易失性，也可以是易失性。
根据本申请的一种实施例，所述配置网卡，使所述网络域内有且仅有一个所述网卡，包括：在每个所述网络域中划分至少一个子网；及将所述网卡加入到所述网络域的所述子网中，使所述网络域内有且仅有一个所述网卡。
根据本申请的一种实施例，所述配置网卡，使所述网络域内有且仅有一个所述网卡，包括：为所述云主机配置至少一个安全组，所述安全组包括指定的网络策略，分配到所述安全组中的所述云主机遵循所述网络策略；将所述安全组分配到所述网络域中；及将所述网卡加入到所述网络域的所述子网中，并选择所述网络域中的所述安全组分配给所述网卡，使所述网络域内有且仅有一个所述网卡。
根据本申请的一种实施例，每个所述网络域下可创建22到26位数掩码的所述子网。
根据本申请的一种实施例，所述云主机支持创建至多3个所述网络域。
根据本申请的一种实施例，所述网络域包括隔离区、内部服务区及合作伙伴区中的一个或者多个，位于所述隔离区内的所述云主机拥有公网类产品的访问权限，位于所述内部服务区的所述云主机没有公网类产品的访问权限，位于所述合作伙伴区的所述云主机拥有使用专线服务与合作伙伴的访问权限。
根据本申请的一种实施例，所述云主机至多配置三张网卡。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，该计算机程序可存储于一计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，前述的存储介质可为磁碟、光盘、只读存储记忆体（Read-Only Memory，ROM）等非易失性存储介质，或随机存储记忆体（Random Access Memory，RAM）等。
以上所述实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对本申请专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干变形和改进，这些都属于本申请的保护范围。因此，本申请专利的保护范围应以所附权利要求为准。

Claims (20)

1、一种云主机多网卡配置方法，其中，所述云主机包括至少一张网卡，所述云主机多网卡配置方法包括：
为所述云主机配置至少两个网络域，所述网络域包括至少一个指定的IP地址，不同所述网络域中的所述IP地址不同；及
为所述至少两个网络域配置网卡，使同一所述网络域内有且仅有一张所述网卡。
2、根据权利要求1所述云主机多网卡配置方法，其中，所述配置网卡，使所述网络域内有且仅有一个所述网卡，包括：
在每个所述网络域中划分至少一个子网；及
将所述网卡加入到所述网络域的所述子网中，使所述网络域内有且仅有一个所述网卡。
3、根据权利要求2所述云主机多网卡配置方法，其中，所述配置网卡，使所述网络域内有且仅有一个所述网卡，包括：
为所述云主机配置至少一个安全组，所述安全组包括指定的网络策略，分配到所述安全组中的所述云主机遵循所述网络策略；
将所述安全组分配到所述网络域中；及
将所述网卡加入到所述网络域的所述子网中，并选择所述网络域中的所述安全组分配给所述网卡，使所述网络域内有且仅有一个所述网卡。
4、根据权利要求2所述云主机多网卡配置方法，其中，每个所述网络域下可创建22到26位数掩码的所述子网。
5、根据权利要求1所述云主机多网卡配置方法，其中，所述云主机支持创建至多3个所述网络域。
6、根据权利要求5所述云主机多网卡配置方法，其中，所述网络域包括隔离区、内部服务区及合作伙伴区中的一个或者多个，位于所述隔离区内的所述云主机拥有公网类产品的访问权限，位于所述内部服务区的所述云主机没有公网类产品的访问权限，位于所述合作伙伴区的所述云主机拥有使用专线服务与合作伙伴的访问权限。
7、根据权利要求5所述云主机多网卡配置方法，其中，所述云主机至多配置三张网卡。
8、一种云主机多网卡配置装置，其中，包括：
网络配置模块，用于为所述云主机配置至少两个网络域，所述网络域包括至少一个指定的IP地址，不同所述网络域中的所述IP地址不同；
网卡配置模块，用于为所述至少两个网络域配置网卡，使同一所述网络域内有且仅有一张所述网卡。
9、一种云主机多网卡配置设备，其中，所述云主机多网卡配置设备包括处理器、与所述处理器耦接的存储器，其中，
所述存储器中存储有计算机可读指令，所述计算机可读指令被所述处理器执行时，使得所述处理器执行如下步骤：
为所述云主机配置至少两个网络域，所述网络域包括至少一个指定的IP地址，不同所述网络域中的所述IP地址不同；及
为所述至少两个网络域配置网卡，使同一所述网络域内有且仅有一张所述网卡。
10、根据权利要求9所述云主机多网卡配置设备，其中，所述配置网卡，使所述网络域内有且仅有一个所述网卡，包括：
在每个所述网络域中划分至少一个子网；及
将所述网卡加入到所述网络域的所述子网中，使所述网络域内有且仅有一个所述网卡。
11、根据权利要求10所述云主机多网卡配置设备，其中，所述配置网卡，使所述网络域内有且仅有一个所述网卡，包括：
为所述云主机配置至少一个安全组，所述安全组包括指定的网络策略，分配到所述安全组中的所述云主机遵循所述网络策略；
将所述安全组分配到所述网络域中；及
将所述网卡加入到所述网络域的所述子网中，并选择所述网络域中的所述安全组分配给所述网卡，使所述网络域内有且仅有一个所述网卡。
12、根据权利要求10所述云主机多网卡配置设备，其中，每个所述网络域下可创建22到26位数掩码的所述子网。
13、根据权利要求9所述云主机多网卡配置设备，其中，所述云主机支持创建至多3个所述网络域。
14、根据权利要求13所述云主机多网卡配置设备，其中，所述网络域包括隔离区、内部服务区及合作伙伴区中的一个或者多个，位于所述隔离区内的所述云主机拥有公网类产品的访问权限，位于所述内部服务区的所述云主机没有公网类产品的访问权限，位于所述合作伙伴区的所述云主机拥有使用专线服务与合作伙伴的访问权限。
15、一种存储有计算机可读指令的存储介质，所述计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行如下步骤：
为所述云主机配置至少两个网络域，所述网络域包括至少一个指定的IP地址，不同所述网络域中的所述IP地址不同；及
为所述至少两个网络域配置网卡，使同一所述网络域内有且仅有一张所述网卡。
16、根据权利要求15所述存储介质，其中，所述配置网卡，使所述网络域内有且仅有一个所述网卡，包括：
在每个所述网络域中划分至少一个子网；及
将所述网卡加入到所述网络域的所述子网中，使所述网络域内有且仅有一个所述网卡。
17、根据权利要求16所述存储介质，其中，所述配置网卡，使所述网络域内有且仅有一个所述网卡，包括：
为所述云主机配置至少一个安全组，所述安全组包括指定的网络策略，分配到所述安全组中的所述云主机遵循所述网络策略；
将所述安全组分配到所述网络域中；及
将所述网卡加入到所述网络域的所述子网中，并选择所述网络域中的所述安全组分配给所述网卡，使所述网络域内有且仅有一个所述网卡。
18、根据权利要求16所述存储介质，其中，每个所述网络域下可创建22到26位数掩码的所述子网。
19、根据权利要求15所述存储介质，其中，所述云主机支持创建至多3个所述网络域。
20、根据权利要求19所述存储介质，其中，所述网络域包括隔离区、内部服务区及合作伙伴区中的一个或者多个，位于所述隔离区内的所述云主机拥有公网类产品的访问权限，位于所述内部服务区的所述云主机没有公网类产品的访问权限，位于所述合作伙伴区的所述云主机拥有使用专线服务与合作伙伴的访问权限。
PCT/CN2020/123238 2020-07-20 2020-10-23 云主机多网卡配置方法、装置、设备及存储介质 WO2021135551A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010697531.6A CN111885044A (zh) 2020-07-20 2020-07-20 云主机多网卡配置方法、装置、设备及存储介质
CN202010697531.6 2020-07-20

Publications (1)

Publication Number Publication Date
WO2021135551A1 true WO2021135551A1 (zh) 2021-07-08

Family

ID=73155001

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/123238 WO2021135551A1 (zh) 2020-07-20 2020-10-23 云主机多网卡配置方法、装置、设备及存储介质

Country Status (2)

Country Link
CN (1) CN111885044A (zh)
WO (1) WO2021135551A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115277726A (zh) * 2022-05-30 2022-11-01 浪潮软件集团有限公司 一种双网络的集群数据传输方法及***

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113645057B (zh) * 2021-06-25 2023-04-07 济南浪潮数据技术有限公司 一种云平台支持添加网卡模型的方法、装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101064659A (zh) * 2006-04-28 2007-10-31 腾讯科技（深圳）有限公司 一种数据传输***及方法
CN106878204A (zh) * 2016-12-21 2017-06-20 新华三技术有限公司 一种虚拟机的创建方法和装置
CN107592209A (zh) * 2016-07-08 2018-01-16 北京奇虎科技有限公司 一种多网卡服务器自动配置ip地址信息的方法和***
EP3313032A1 (en) * 2015-08-07 2018-04-25 New H3C Technologies Co., Ltd. Cloud platform security realization
CN108347472A (zh) * 2018-01-12 2018-07-31 网宿科技股份有限公司 Ip地址的配置方法、云服务器、云平台及可读存储介质
CN110266718A (zh) * 2019-07-03 2019-09-20 广州非凡信息安全技术有限公司 基于vlan标签的在多个网段部署蜜罐的***及方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104579887A (zh) * 2013-10-16 2015-04-29 宇宙互联有限公司 云网关、云网关创建配置***及方法
CN104468844A (zh) * 2014-12-31 2015-03-25 蓝盾信息安全技术股份有限公司 云计算iaas教育实验平台装置
CN109039771B (zh) * 2018-09-04 2021-07-20 浪潮云信息技术股份公司 一种多网卡绑定配置方法及***
CN110932884B (zh) * 2019-11-08 2022-11-29 苏州浪潮智能科技有限公司 云物理机添加多网络的方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101064659A (zh) * 2006-04-28 2007-10-31 腾讯科技（深圳）有限公司 一种数据传输***及方法
EP3313032A1 (en) * 2015-08-07 2018-04-25 New H3C Technologies Co., Ltd. Cloud platform security realization
CN107592209A (zh) * 2016-07-08 2018-01-16 北京奇虎科技有限公司 一种多网卡服务器自动配置ip地址信息的方法和***
CN106878204A (zh) * 2016-12-21 2017-06-20 新华三技术有限公司 一种虚拟机的创建方法和装置
CN108347472A (zh) * 2018-01-12 2018-07-31 网宿科技股份有限公司 Ip地址的配置方法、云服务器、云平台及可读存储介质
CN110266718A (zh) * 2019-07-03 2019-09-20 广州非凡信息安全技术有限公司 基于vlan标签的在多个网段部署蜜罐的***及方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115277726A (zh) * 2022-05-30 2022-11-01 浪潮软件集团有限公司 一种双网络的集群数据传输方法及***

Also Published As

Publication number Publication date
CN111885044A (zh) 2020-11-03

Similar Documents

Publication Publication Date Title
US10911528B2 (en) Managing replication of computing nodes for provided computer networks
US11409550B2 (en) Low latency connections to workspaces in a cloud computing environment
US11063819B2 (en) Managing use of alternative intermediate destination computing nodes for provided computer networks
US11563681B2 (en) Managing communications using alternative packet addressing
US8218558B2 (en) Data transfer system enabling access to multiple subnets and method thereof
US9794116B2 (en) Managing use of intermediate destination computing nodes for provided computer networks
US8683023B1 (en) Managing communications involving external nodes of provided computer networks
US8488446B1 (en) Managing failure behavior for computing nodes of provided computer networks
US9356860B1 (en) Managing external communications for provided computer networks
US10084851B1 (en) Managing use of intermediate destination hardware devices for provided computer networks
TW201008177A (en) Selectively re-mapping a network topology
US20240015219A1 (en) Distributed network security system providing isolation of customer data
WO2021135551A1 (zh) 云主机多网卡配置方法、装置、设备及存储介质
US10862804B2 (en) Redirecting data packets between overlay network and underlay network
WO2023231982A1 (zh) 一种基于公有云的vpc之间的通信方法及相关产品
KR102595308B1 (ko) 인터넷 망의 사용자 단말이 원격 서비스를 실행하기 위하여 사설망에 접속할 수 있도록 하는 사설망 접속 제어장치 및 그것의 제어 방법
Johansson et al. Supporting user mobility with peer-to-peer-based application mobility in heterogeneous networks
CN117499318B (zh) 云计算虚拟网络***、及其使用方法、装置、设备及介质
CN115987798A (zh) 一种资源管理方法及资源管理***

Legal Events

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

Ref document number: 20909753

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20909753

Country of ref document: EP

Kind code of ref document: A1