技术领域technical field
本发明实施例涉及通信技术领域，尤其涉及一种虚拟资源的分配方法及装置。The embodiments of the present invention relate to the field of communication technologies, and in particular, to a method and device for allocating virtual resources.
背景技术Background technique
混合云是一种公共云和私有云的组合，例如，某个混合云中包括私有云1和第三方提供的公共云2，那么，企业可以将其数据存放在安全度较高的私有云1中，同时，还可利用公共云2提供的计算、存储等资源为私有云1提供服务，从而达到省钱又安全的目的。Hybrid cloud is a combination of public cloud and private cloud. For example, a hybrid cloud includes private cloud 1 and public cloud 2 provided by a third party. Then, enterprises can store their data in private cloud 1 with a higher degree of security. At the same time, the computing, storage and other resources provided by the public cloud 2 can also be used to provide services for the private cloud 1, so as to achieve the purpose of saving money and security.
目前，私有云可以通过向第三方云(例如，上述公有云2)中注入云网关(CloudGateway)的方式实现混合云的网络架构。如图1所示，私有云11可以通过适配器(Adapter)向一个或多个第三方云12中注入Cloud Gateway 13，这样，私有云11可以通过注入的云网关13管理相应的第三方云12，使第三方云12为其提供服务。Currently, a private cloud can implement a network architecture of a hybrid cloud by injecting a cloud gateway (CloudGateway) into a third-party cloud (for example, the public cloud 2 above). As shown in Figure 1, private cloud 11 can inject Cloud Gateway 13 in one or more third-party clouds 12 through adapter (Adapter), like this, private cloud 11 can manage corresponding third-party cloud 12 through the cloud gateway 13 of injection, Make the third-party cloud 12 provide services for it.
在上述混合云的网络架构中，私有云11在接收到租户触发的应用程序编程接口(Application Programming Interface，API)请求(例如，在第三方云12中创建虚拟机的请求)后，需将其转换为对应的第三方云12的API请求从而实现第三方服务。而私有云11对外只能为租户提供私有云11自身的私有API，也就是说，如果私有云11接收到其私有API不能解析的请求时，私有云11将无法为租户提供相应的服务，并且，当私有云11无法将接收到的API请求转换为对应的第三方云12的API请求时，也无法为租户提供相应的服务，使得整个混合云网络的兼容性和API请求处理效率降低。In the above hybrid cloud network architecture, after the private cloud 11 receives an application programming interface (Application Programming Interface, API) request triggered by a tenant (for example, a request to create a virtual machine in the third-party cloud 12), it needs to It is converted into an API request of the corresponding third-party cloud 12 so as to realize third-party services. And the private cloud 11 can only provide the private API of the private cloud 11 itself for the tenant externally, that is to say, if the private cloud 11 receives a request that its private API cannot resolve, the private cloud 11 will not be able to provide the corresponding service for the tenant, and , when the private cloud 11 cannot convert the received API request into the API request of the corresponding third-party cloud 12, it also cannot provide corresponding services for the tenants, which reduces the compatibility of the entire hybrid cloud network and the API request processing efficiency.
发明内容Contents of the invention
本发明的实施例提供一种虚拟资源的分配方法及装置，可以在混合云网络架构中提供统一标准的OpenStack API，提高混合云网络的兼容性和API请求处理效率。Embodiments of the present invention provide a method and device for allocating virtual resources, which can provide a unified standard OpenStack API in a hybrid cloud network architecture, and improve compatibility of the hybrid cloud network and API request processing efficiency.
为达到上述目的，本发明的实施例采用如下技术方案：In order to achieve the above object, embodiments of the present invention adopt the following technical solutions:
第一方面，本发明的实施例提供一种虚拟资源的分配方法，包括：CCS节点获取级联层的私有云中发起的虚拟资源请求，该虚拟资源请求用于请求被级联层的第三方云中的虚拟资源；进而，CCS节点通过调用OpenStack API将该虚拟资源请求透传至上述第三方云的云网关中，以使得该云网关根据上述虚拟资源请求调用该第三方云的私有API将该第三方云中的虚拟资源划分给该私有云。In the first aspect, the embodiment of the present invention provides a method for allocating virtual resources, including: the CCS node obtains the virtual resource request initiated in the private cloud of the cascaded layer, and the virtual resource request is used to request the third party of the cascaded layer virtual resources in the cloud; furthermore, the CCS node transparently transmits the virtual resource request to the cloud gateway of the above-mentioned third-party cloud by calling the OpenStack API, so that the cloud gateway calls the private API of the third-party cloud according to the above-mentioned virtual resource request. The virtual resources in the third-party cloud are assigned to the private cloud.
也就是说，在本申请中，可以将第三方云作为上述私有云中的一个被级联OpenStack部署在被级联层中，形成混合云的网络架构。此时，第三方云可以通过统一标准的OpenStack API接口无缝对接级联层的私有云，也可以作为一个单独的OpenStack提供云服务，在混合云的网络架构中对外对内均提供统一标准的OpenStack API，从而可以屏蔽不同云间的API差异，提高混合云网络的兼容性和API请求处理效率。同时，相同的OpenStackAPI体系，可以保证租户选择混合云中的不同云进行操作时没有明显差异，从而实现跨云的平滑互操作。That is to say, in this application, the third-party cloud can be deployed as a cascaded OpenStack in the cascaded layer in the above-mentioned private cloud to form a hybrid cloud network architecture. At this time, the third-party cloud can seamlessly connect to the private cloud at the cascade layer through the unified standard OpenStack API interface, or provide cloud services as a separate OpenStack, and provide unified standard internally and externally in the hybrid cloud network architecture. OpenStack API, so that API differences between different clouds can be shielded, and the compatibility of the hybrid cloud network and the processing efficiency of API requests can be improved. At the same time, the same OpenStack API system can ensure that there is no obvious difference when tenants choose different clouds in the hybrid cloud to operate, so as to achieve smooth interoperability across clouds.
在一种可能的设计方法中，在CCS节点获取私有云中发起的虚拟资源请求之前，还包括：CCS节点向该第三方云中的云网关发送在OpenStack API与第三方云的私有API之间传递参数时的参数映射关系。这样，当云网关接收到上述虚拟资源请求后，可以根据该参数映射关系调用第三方云的私有API将该第三方云中的虚拟资源划分给该私有云。In a possible design method, before the CCS node obtains the virtual resource request initiated in the private cloud, it also includes: the CCS node sends the request between the OpenStack API and the private API of the third-party cloud to the cloud gateway in the third-party cloud The parameter mapping relationship when passing parameters. In this way, after the cloud gateway receives the virtual resource request, it can call the private API of the third-party cloud according to the parameter mapping relationship to divide the virtual resources in the third-party cloud to the private cloud.
在一种可能的设计方法中，在CCS节点获取私有云中发起的虚拟资源请求之前，还包括：CCS节点在该第三方云和该私有云之间建立VPN隧道；CCS节点在该第三方云中创建承载云网关的虚拟机；CCS节点在该虚拟机中部署云网关提供的混合云服务，并将该云网关提供的混合云服务注册在该私有云中。这样，部署的云网关所在的第三方云AWS云可以作为一个被级联的OpenStack部署在私有云的被级联层中，形成混合云的网络架构。在该混合云的网络架构中，无论是级联层的私有云，还是被级联层的第三方云，均可提供统一标准的OpenStack API接口，从而可以屏蔽不同云间的API差异，提高混合云网络的兼容性和API请求处理效率。In a possible design method, before the CCS node obtains the virtual resource request initiated in the private cloud, it also includes: the CCS node establishes a VPN tunnel between the third-party cloud and the private cloud; Create a virtual machine hosting the cloud gateway in the virtual machine; the CCS node deploys the hybrid cloud service provided by the cloud gateway in the virtual machine, and registers the hybrid cloud service provided by the cloud gateway in the private cloud. In this way, the third-party cloud AWS cloud where the deployed cloud gateway is located can be deployed as a cascaded OpenStack in the cascaded layer of the private cloud to form a hybrid cloud network architecture. In the hybrid cloud network architecture, both the private cloud at the cascaded layer and the third-party cloud at the cascaded layer can provide a unified standard OpenStack API interface, which can shield API differences between different clouds and improve hybrid Cloud network compatibility and API request processing efficiency.
在一种可能的设计方法中，在CCS节点通过调用OpenStack API将该虚拟资源请求透传至该第三方云的云网关中，以使得云网关根据该虚拟资源请求调用该第三方云的API将该第三方云中的虚拟资源划分给该私有云之后，还包括：CCS节点在IP资源池中更新从该第三方云中获取的至少一个浮动IP地址；CCS节点将该IP资源池中更新的浮动IP地址同步至该私有云以及该第三方云的云网关中。In a possible design method, the CCS node transparently transmits the virtual resource request to the cloud gateway of the third-party cloud by calling the OpenStack API, so that the cloud gateway calls the API of the third-party cloud according to the virtual resource request. After the virtual resources in the third-party cloud are allocated to the private cloud, it also includes: the CCS node updates at least one floating IP address obtained from the third-party cloud in the IP resource pool; the CCS node updates the IP resource pool in the IP resource pool The floating IP address is synchronized to the cloud gateway of the private cloud and the third-party cloud.
在一种可能的设计方法中，CCS节点获取私有云中发起的虚拟资源请求，包括：CCS节点通过调用OpenStack API获取私有云中发起的虚拟资源请求。In a possible design method, the CCS node obtains the virtual resource request initiated in the private cloud, including: the CCS node obtains the virtual resource request initiated in the private cloud by calling an OpenStack API.
第二方面，本发明的实施例提供一种虚拟资源的分配方法，包括：云网关通过OpenStack API从私有云中获取虚拟资源请求，该虚拟资源请求用于请求第三方云中的虚拟资源，该私有云位于级联层，该第三方云位于被级联层；云网关将该虚拟资源请求转换为支持该第三方云的私有API的API请求；云网关按照该API请求将该第三方云中的虚拟资源划分给该私有云。由于OpenStack可提供实施简单、可大规模扩展、丰富、标准统一的API接口，而本申请实施例中的私有云和第三方云均可通过OpenStack API进行交互，那么，租户在第三方云和在私有云上的用户体验和操作方式一致，从而屏蔽了第三方云因API接口不同而导致的云间差异。In a second aspect, embodiments of the present invention provide a method for allocating virtual resources, including: the cloud gateway obtains a virtual resource request from a private cloud through an OpenStack API, and the virtual resource request is used to request a virtual resource in a third-party cloud, the The private cloud is located at the cascaded layer, and the third-party cloud is located at the cascaded layer; the cloud gateway converts the virtual resource request into an API request supporting the private API of the third-party cloud; The virtual resources of the private cloud are allocated to the private cloud. Because OpenStack can provide simple implementation, large-scale scalability, rich, unified standard API interface, and the private cloud and the third-party cloud in the embodiment of this application can interact through the OpenStack API, then, the tenants in the third-party cloud and in the The user experience and operation mode on the private cloud are consistent, thus shielding the differences between clouds caused by the different API interfaces of third-party clouds.
在一种可能的设计方法中，该虚拟资源请求为虚拟机创建请求，该虚拟机创建请求中携带待创建虚拟机的第一配置参数；其中，云网关将该虚拟资源请求转换为支持该第三方云的私有API的API请求，包括：云网关根据预置的在OpenStack API与第三方云的私有API之间传递参数时的参数映射关系，查找与该第一配置参数对应的第二配置参数；云网关将该虚拟机创建请求中的第一配置参数修改为该第二配置参数，得到支持该第三方云的私有API的API请求。In a possible design method, the virtual resource request is a virtual machine creation request, and the virtual machine creation request carries the first configuration parameter of the virtual machine to be created; wherein, the cloud gateway converts the virtual resource request to support the first The API request of the private API of the third-party cloud includes: the cloud gateway searches for the second configuration parameter corresponding to the first configuration parameter according to the preset parameter mapping relationship when passing parameters between the OpenStack API and the private API of the third-party cloud ; The cloud gateway modifies the first configuration parameter in the virtual machine creation request to the second configuration parameter, and obtains an API request supporting the private API of the third-party cloud.
在一种可能的设计方法中，该虚拟资源请求为虚拟卷创建请求，该虚拟卷创建请求中携带第一卷类型参数；其中，云网关将该虚拟资源请求转换为支持该第三方云的私有API的API请求，包括：云网关根据预置的在OpenStack API与第三方云的私有API之间传递参数时的参数映射关系，查找与该第一卷类型参数对应的第二卷类型参数；云网关将该虚拟卷创建请求中的第一卷类型参数修改为该第二卷类型参数，得到支持该第三方云的私有API的API请求。In a possible design method, the virtual resource request is a virtual volume creation request, and the virtual volume creation request carries the first volume type parameter; wherein, the cloud gateway converts the virtual resource request into a private The API request of the API includes: the cloud gateway searches for the second volume type parameter corresponding to the first volume type parameter according to the preset parameter mapping relationship when passing parameters between the OpenStack API and the private API of the third-party cloud; The gateway modifies the first volume type parameter in the virtual volume creation request to the second volume type parameter, and obtains an API request supporting the private API of the third-party cloud.
在一种可能的设计方法中，在云网关将该虚拟资源请求转换为支持该第三方云的私有API的API请求之前，还包括：云网关接收该私有云中CCS节点发送的在OpenStack API与第三方云的私有API之间传递参数时的参数映射关系。In a possible design method, before the cloud gateway converts the virtual resource request into an API request supporting the private API of the third-party cloud, it further includes: the cloud gateway receives the OpenStack API and Parameter mapping relationship when passing parameters between private APIs of third-party clouds.
第三方面，本发明的实施例提供一种CCS节点，包括：获取单元，用于：获取私有云中发起的虚拟资源请求，该虚拟资源请求用于请求第三方云中的虚拟资源，该私有云位于级联层，该第三方云位于被级联层；发送单元，用于：通过调用OpenStack API将该虚拟资源请求透传至该第三方云的云网关中，以使得云网关根据该虚拟资源请求调用该第三方云的API将该第三方云中的虚拟资源划分给该私有云。In a third aspect, an embodiment of the present invention provides a CCS node, including: an acquisition unit, configured to: acquire a virtual resource request initiated in a private cloud, the virtual resource request is used to request a virtual resource in a third-party cloud, the private The cloud is located at the cascaded layer, and the third-party cloud is located at the cascaded layer; the sending unit is used to transparently transmit the virtual resource request to the cloud gateway of the third-party cloud by calling the OpenStack API, so that the cloud gateway according to the virtual The resource request calls the API of the third-party cloud to assign virtual resources in the third-party cloud to the private cloud.
在一种可能的设计方法中，该发送单元，还用于：向该第三方云中的云网关发送在OpenStack API与第三方云的私有API之间传递参数时的参数映射关系。In a possible design method, the sending unit is further configured to: send the parameter mapping relationship when transferring parameters between the OpenStack API and the private API of the third-party cloud to the cloud gateway in the third-party cloud.
在一种可能的设计方法中，CCS节点还包括：创建单元，用于：在该第三方云和该私有云之间建立VPN隧道；在该第三方云中创建承载云网关的虚拟机；在该虚拟机中部署云网关提供的混合云服务，并将该云网关提供的混合云服务注册在该私有云中。In a possible design method, the CCS node also includes: a creating unit, configured to: establish a VPN tunnel between the third-party cloud and the private cloud; create a virtual machine carrying a cloud gateway in the third-party cloud; The hybrid cloud service provided by the cloud gateway is deployed in the virtual machine, and the hybrid cloud service provided by the cloud gateway is registered in the private cloud.
在一种可能的设计方法中，CCS节点还包括：更新单元，用于：在IP资源池中更新从该第三方云中获取的至少一个浮动IP地址；将该IP资源池中更新的浮动IP地址同步至该私有云以及该第三方云的云网关中。In a possible design method, the CCS node also includes: an update unit, configured to: update at least one floating IP address obtained from the third-party cloud in the IP resource pool; update the floating IP address in the IP resource pool The address is synchronized to the cloud gateway of the private cloud and the third-party cloud.
在一种可能的设计方法中，该获取单元，具体用于：通过调用OpenStack API获取私有云中发起的虚拟资源请求。In a possible design method, the acquiring unit is specifically configured to: acquire a virtual resource request initiated in a private cloud by calling an OpenStack API.
第四方面，本发明的实施例提供一种云网关，包括：获取单元，用于：通过OpenStack API从私有云中获取虚拟资源请求，该虚拟资源请求用于请求第三方云中的虚拟资源，该私有云位于级联层，该第三方云位于被级联层；转换单元，用于：将该虚拟资源请求转换为支持该第三方云的私有API的API请求；执行单元，用于：按照该API请求将该第三方云中的虚拟资源划分给该私有云。In a fourth aspect, an embodiment of the present invention provides a cloud gateway, including: an acquisition unit, configured to: acquire a virtual resource request from a private cloud through an OpenStack API, and the virtual resource request is used to request a virtual resource in a third-party cloud, The private cloud is located at the cascaded layer, and the third-party cloud is located at the cascaded layer; the conversion unit is used to: convert the virtual resource request into an API request supporting the private API of the third-party cloud; the execution unit is used to: according to The API requests to allocate virtual resources in the third-party cloud to the private cloud.
在一种可能的设计方法中，该虚拟资源请求为虚拟机创建请求，该虚拟机创建请求中携带待创建虚拟机的第一配置参数；该转换单元，具体用于：根据预置的在OpenStackAPI与第三方云的私有API之间传递参数时的参数映射关系，查找与该第一配置参数对应的第二配置参数；将该虚拟机创建请求中的第一配置参数修改为该第二配置参数，得到支持该第三方云的私有API的API请求。In a possible design method, the virtual resource request is a virtual machine creation request, and the virtual machine creation request carries the first configuration parameter of the virtual machine to be created; the conversion unit is specifically used for: according to the preset OpenStack API The parameter mapping relationship when transferring parameters with the private API of the third-party cloud, searching for the second configuration parameter corresponding to the first configuration parameter; modifying the first configuration parameter in the virtual machine creation request to the second configuration parameter , get an API request that supports the private API of the third-party cloud.
在一种可能的设计方法中，该虚拟资源请求为虚拟卷创建请求，该虚拟卷创建请求中携带第一卷类型参数；该转换单元，具体用于：根据预置的在OpenStack API与第三方云的私有API之间传递参数时的参数映射关系，查找与该第一卷类型参数对应的第二卷类型参数；将该虚拟卷创建请求中的第一卷类型参数修改为该第二卷类型参数，得到支持该第三方云的私有API的API请求。In a possible design method, the virtual resource request is a virtual volume creation request, and the virtual volume creation request carries the first volume type parameter; the conversion unit is specifically used for: according to the preset OpenStack API and third-party Parameter mapping relationship when passing parameters between cloud private APIs, find the second volume type parameter corresponding to the first volume type parameter; modify the first volume type parameter in the virtual volume creation request to the second volume type parameter to get the API request that supports the private API of the third-party cloud.
在一种可能的设计方法中，该获取单元，还用于：接收该私有云中CCS节点发送的在OpenStack API与第三方云的私有API之间传递参数时的参数映射关系。In a possible design method, the obtaining unit is further configured to: receive the parameter mapping relationship sent by the CCS node in the private cloud when transferring parameters between the OpenStack API and the private API of the third-party cloud.
第五方面，本发明的实施例提供一种OpenStack级联系统，该系统包括设置在级联层的私有云，以及设置在被级联层的第三方云，该私有云中的CCS节点通过用OpenStackAPI与该第三方云中的云网关通信。In the fifth aspect, the embodiments of the present invention provide an OpenStack cascading system, the system includes a private cloud set at the cascaded layer, and a third-party cloud set at the cascaded layer, and the CCS nodes in the private cloud use The OpenStack API communicates with the cloud gateway in this third-party cloud.
第六方面，本发明实施例提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该指令在上述任一项CCS节点上运行时，使得CCS节点执行上述任一项虚拟资源的分配方法。In the sixth aspect, the embodiment of the present invention provides a computer-readable storage medium, the computer-readable storage medium stores an instruction, and when the instruction is run on any of the above-mentioned CCS nodes, the CCS node is made to perform any of the above-mentioned Allocation method of virtual resources.
第七方面，本发明实施例提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该指令在上述任一项云网关上运行时，使得云网关执行上述任一项虚拟资源的分配方法。In the seventh aspect, the embodiment of the present invention provides a computer-readable storage medium, the computer-readable storage medium stores instructions, and when the instructions are run on any of the above-mentioned cloud gateways, the cloud gateway is made to perform any of the above-mentioned Allocation method of virtual resources.
第八方面，本发明实施例提供一种包含指令的计算机程序产品，当其在上述任一项CCS节点上运行时，使得CCS节点执行上述任一项虚拟资源的分配方法。In an eighth aspect, an embodiment of the present invention provides a computer program product containing instructions, which, when running on any one of the above CCS nodes, causes the CCS node to execute any one of the above methods for allocating virtual resources.
第九方面，本发明实施例提供一种包含指令的计算机程序产品，当其在上述任一项云网关上运行时，使得云网关执行上述任一项虚拟资源的分配方法。In a ninth aspect, an embodiment of the present invention provides a computer program product containing instructions, which, when running on any of the above cloud gateways, causes the cloud gateway to execute any of the above methods for allocating virtual resources.
本发明的实施例中，上述UE和无线接入设备的名字对设备本身不构成限定，在实际实现中，这些设备可以以其他名称出现。只要各个设备的功能和本发明的实施例类似，即属于本发明权利要求及其等同技术的范围之内。In the embodiments of the present invention, the names of the UE and the wireless access device do not limit the device itself, and these devices may appear with other names in actual implementation. As long as the functions of each device are similar to the embodiments of the present invention, it falls within the scope of the claims of the present invention and equivalent technologies thereof.
另外，第二方面至第九方面中任一种设计方式所带来的技术效果可参见上述第一方面中不同设计方法所带来的技术效果，此处不再赘述。In addition, the technical effects brought about by any one of the design methods from the second aspect to the ninth aspect can be referred to the technical effects brought about by the different design methods in the first aspect above, and will not be repeated here.
附图说明Description of drawings
图1为现有技术中混合云网络的架构示意图；FIG. 1 is a schematic diagram of an architecture of a hybrid cloud network in the prior art;
图2为本发明实施例提供的一种混合云网络的架构示意图一；FIG. 2 is a first schematic diagram of a hybrid cloud network architecture provided by an embodiment of the present invention;
图3为本发明实施例提供的一种混合云网络的架构示意图二；FIG. 3 is a schematic diagram 2 of a hybrid cloud network architecture provided by an embodiment of the present invention;
图4为本发明实施例提供的一种虚拟资源的分配方法的交互示意图一；FIG. 4 is an interactive schematic diagram 1 of a method for allocating virtual resources provided by an embodiment of the present invention;
图5为本发明实施例提供的一种虚拟资源的分配方法的交互示意图二；FIG. 5 is a second interactive schematic diagram of a method for allocating virtual resources provided by an embodiment of the present invention;
图6为本发明实施例提供的一种混合云网络的架构示意图三；FIG. 6 is a third schematic diagram of a hybrid cloud network architecture provided by an embodiment of the present invention;
图7为本发明实施例提供的一种虚拟资源的分配方法的交互示意图三；FIG. 7 is a third interactive schematic diagram of a method for allocating virtual resources provided by an embodiment of the present invention;
图8为本发明实施例提供的一种混合云网络的架构示意图四；FIG. 8 is a schematic diagram 4 of a hybrid cloud network architecture provided by an embodiment of the present invention;
图9为本发明实施例提供的一种CCS节点的结构示意图；FIG. 9 is a schematic structural diagram of a CCS node provided by an embodiment of the present invention;
图10为本发明实施例提供的一种云网关的结构示意图；FIG. 10 is a schematic structural diagram of a cloud gateway provided by an embodiment of the present invention;
图11为本发明实施例提供的一种物理主机的结构示意图。FIG. 11 is a schematic structural diagram of a physical host provided by an embodiment of the present invention.
具体实施方式detailed description
以下，术语“第一”、“第二”仅用于描述目的，而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括一个或者更多个该特征。在本发明实施例的描述中，除非另有说明，“多个”的含义是两个或两个以上。Hereinafter, the terms "first" and "second" are used for descriptive purposes only, and cannot be understood as indicating or implying relative importance or implicitly specifying the quantity of indicated technical features. Thus, a feature defined as "first" and "second" may explicitly or implicitly include one or more of these features. In the description of the embodiments of the present invention, unless otherwise specified, "plurality" means two or more.
为清楚阐述本发明的实施例提供的虚拟资源的分配方法，首先解释关于OpenStack的相关内容。In order to clearly illustrate the method for allocating virtual resources provided by the embodiments of the present invention, the related content about OpenStack is explained first.
OpenStack是一个开源的云计算管理平台项目，由几个主要的服务组件组合起来完成具体工作。示例性的，在一个OpenStack系统中具体可包括Nova、Swift、Keystone、Neutron、以及Cinder等服务组件。OpenStack is an open source cloud computing management platform project, which is composed of several main service components to complete specific work. Exemplarily, an OpenStack system may specifically include service components such as Nova, Swift, Keystone, Neutron, and Cinder.
其中，Nova服务组件，用于为单个用户或使用群组管理虚拟机实例的整个生命周期，可根据用户需求提供相应的虚拟服务。例如，负责虚拟机创建、开机、关机、挂起、暂停、调整、迁移、重启、销毁等操作，配置CPU、内存等信息规格。Among them, the Nova service component is used to manage the entire life cycle of a virtual machine instance for a single user or a group, and can provide corresponding virtual services according to user needs. For example, it is responsible for creating, starting, shutting down, suspending, suspending, adjusting, migrating, restarting, and destroying virtual machines, and configuring information specifications such as CPU and memory.
Swift服务组件，是一套用于在大规模可扩展系统中通过内置冗余及高容错机制实现对象存储的系统，允许进行存储或者检索文件。Swift service component is a system for implementing object storage through built-in redundancy and high fault tolerance mechanism in a large-scale scalable system, allowing to store or retrieve files.
Keystone服务组件，可为OpenStack其他服务提供身份验证、服务规则以及服务令牌的功能。The Keystone service component can provide authentication, service rules, and service token functions for other OpenStack services.
Neutron服务组件，可提供云计算的网络虚拟化技术，为OpenStack其他服务提供网络连接服务。还可以为用户提供接口，配置动态主机配置协议(Dynamic HostConfiguration Protocol，DHCP)、域名系统(Domain Name System，DNS)、负载均衡、L3服务，网络支持GRE、虚拟局域网(Virtual Local Area Network，VLAN)等。The Neutron service component can provide cloud computing network virtualization technology and provide network connection services for other OpenStack services. It can also provide users with interfaces, configure Dynamic Host Configuration Protocol (Dynamic Host Configuration Protocol, DHCP), Domain Name System (Domain Name System, DNS), load balancing, L3 services, and the network supports GRE and virtual local area network (Virtual Local Area Network, VLAN) Wait.
Cinder服务组件，可用于提供稳定的数据块存储服务，它的插件驱动架构有利于块设备的创建和管理，如创建卷、删除卷，在实例上挂载和卸载卷。The Cinder service component can be used to provide stable data block storage services. Its plug-in driver architecture facilitates the creation and management of block devices, such as creating volumes, deleting volumes, and mounting and unmounting volumes on instances.
当然，OpenStack系统中还可以包括Horizon、Ceilometer、Heat以及Trove等服务组件，本发明实施例对此不作任何限制。Of course, the OpenStack system may also include service components such as Horizon, Ceilometer, Heat, and Trove, which are not limited in this embodiment of the present invention.
具体的，OpenStack的各个服务组件都提供有相应的基于OpenStack API接口，如Nova-API，Swift-API等。使用这些API可以让用户在OpenStack云中进行一系列的操作，如，启动服务主机，创建镜像，给主机和镜像设置元数据，创建容器和对象等。OpenStack支持几乎所有类型的云环境，因此，OpenStack可提供实施简单、可大规模扩展、丰富、标准统一的云计算管理平台。Specifically, each service component of OpenStack provides a corresponding OpenStack API-based interface, such as Nova-API, Swift-API, and so on. Using these APIs allows users to perform a series of operations in the OpenStack cloud, such as starting service hosts, creating images, setting metadata for hosts and images, creating containers and objects, and so on. OpenStack supports almost all types of cloud environments. Therefore, OpenStack can provide a cloud computing management platform that is simple to implement, scalable, rich, and standardized.
本发明的实施例提供一种虚拟资源的分配方法，可应用在如图2所示的OpenStack级联系统内，实现混合云的网络架构。Embodiments of the present invention provide a method for allocating virtual resources, which can be applied in the OpenStack cascade system shown in FIG. 2 to realize a hybrid cloud network architecture.
示例性的，如图2所示，私有云201可以以OpenStack级联系统为基础架构进行部署，其中，该私有云201中包括级联层21和被级联层22，级联层21中设置有级联(Cascading)OpenStack，被级联层22中设置有被级联(Cascaded)OpenStack。级联层21作为统一的入口可接收租户或管理员下发的相关指令(例如，API请求)，进而，级联层21将接收到的指令发送给级联层22中相应的Cascaded OpenStack来执行该指令。其中，级联层21和被级联层22均提供统一的OpenStack API。Exemplarily, as shown in FIG. 2, the private cloud 201 can be deployed based on the OpenStack cascading system, wherein, the private cloud 201 includes a cascading layer 21 and a cascaded layer 22, and the cascading layer 21 is set to There is a cascaded (Cascaded) OpenStack, and the cascaded (Cascaded) OpenStack is provided in the cascaded layer 22 . As a unified entrance, the cascading layer 21 can receive relevant instructions (for example, API requests) issued by tenants or administrators, and then, the cascading layer 21 sends the received instructions to the corresponding Cascaded OpenStack in the cascading layer 22 for execution the instruction. Wherein, both the cascading layer 21 and the cascaded layer 22 provide a unified OpenStack API.
在本申请中，仍如图2所示，可以将第三方云202作为上述私有云201中的一个被级联OpenStack部署在被级联层22中，形成混合云的网络架构。In this application, as shown in FIG. 2 , the third-party cloud 202 can be deployed in the cascaded layer 22 as a cascaded OpenStack in the above-mentioned private cloud 201 to form a hybrid cloud network architecture.
这样，对租户而言，上述混合云的统一入口为级联层21的OpenStack API接口。那么，当租户发起API请求时，级联层21的级联OpenStack可通过统一的OpenStackAPI接口，将该API请求透传到被级联的第三方云202中，由第三方云202内部将基于OpenStack API的API请求转换为基于第三方云202的API请求，最终调用第三方云的API执行租户发起的API请求。In this way, for tenants, the unified entrance of the hybrid cloud is the OpenStack API interface of the cascading layer 21 . Then, when a tenant initiates an API request, the cascaded OpenStack of the cascaded layer 21 can transparently transmit the API request to the cascaded third-party cloud 202 through the unified OpenStack API interface, and the third-party cloud 202 will internally transmit the API request based on OpenStack The API request of the API is converted into an API request based on the third-party cloud 202, and finally the API of the third-party cloud is called to execute the API request initiated by the tenant.
也就是说，第三方云202作为私有云201的一个被级联OpenStack，既可以通过统一标准的OpenStack API接口无缝对接级联层21的私有云201，也可以作为一个单独的OpenStack提供云服务，在混合云的网络架构中对外对内均提供统一标准的OpenStackAPI，从而可以屏蔽不同云间的API差异，提高混合云网络的兼容性和API请求处理效率。That is to say, the third-party cloud 202, as a cascaded OpenStack of the private cloud 201, can seamlessly connect to the private cloud 201 of the cascaded layer 21 through a unified standard OpenStack API interface, or provide cloud services as a separate OpenStack , in the network architecture of the hybrid cloud, a unified standard OpenStack API is provided both externally and internally, so that API differences between different clouds can be shielded, and the compatibility of the hybrid cloud network and the processing efficiency of API requests can be improved.
同时，相同的OpenStack API体系，可以保证租户选择混合云中的不同云进行操作时没有明显差异，从而实现跨云的平滑互操作。At the same time, the same OpenStack API system can ensure that there is no obvious difference when tenants choose different clouds in the hybrid cloud to operate, so as to achieve smooth interoperability across clouds.
需要说明的是，本申请实施例中涉及的第三方云202可以是公有云，例如，西班牙电信开放云(Telefonica Open Cloud，TOC)，也可以是私有云，例如，华为FS(FusionSphere)云操作系统。并且，第三方云202可以是私有云201的同构云，也可以是私有云201的异构云，本发明实施例对此不作任何限制。It should be noted that the third-party cloud 202 involved in the embodiment of the present application may be a public cloud, for example, Telefónica Open Cloud (TOC), or a private cloud, for example, Huawei FS (FusionSphere) cloud operation system. Moreover, the third-party cloud 202 may be a homogeneous cloud of the private cloud 201 or a heterogeneous cloud of the private cloud 201, which is not limited in this embodiment of the present invention.
进一步地，如图3所示，基于图2所示的混合云的网络架构，私有云201中还可以部署云配置服务(Cloud Configuration Service，CCS)节点，虚拟专有网络(VirtualPrivate Cloud，VPC)节点，弹性计算服务(Elastic Compute Service，ECS)节点以及云连接器(Cloud Connector)等服务模块。Further, as shown in FIG. 3, based on the network architecture of the hybrid cloud shown in FIG. Node, elastic computing service (Elastic Compute Service, ECS) node and cloud connector (Cloud Connector) and other service modules.
其中，CCS模块可以调用第三方云202的接口，在第三方云202内创建云网关(CloudGateway)203，该云网关203可以以虚拟机的形式部署在第三方云202中。进而，云连接器可进一步在云网关203上安装云API适配器(Cloud API Adapter，CAA)、数据库(Data Base，DB)等服务，并将这些服务注册到私有云201中，使得私有云201将获取到的相应租户发起的API请求后能够转发至被级联的第三方云202中，即使得第三方云202作为一个被级联的OpenStack部署在私有云201的被级联层22。Wherein, the CCS module can call the interface of the third-party cloud 202 to create a cloud gateway (CloudGateway) 203 in the third-party cloud 202, and the cloud gateway 203 can be deployed in the third-party cloud 202 in the form of a virtual machine. Furthermore, the cloud connector can further install cloud API adapter (Cloud API Adapter, CAA), database (Data Base, DB) and other services on the cloud gateway 203, and register these services in the private cloud 201, so that the private cloud 201 will The acquired API request initiated by the corresponding tenant can be forwarded to the cascaded third-party cloud 202 , that is, the third-party cloud 202 is deployed on the cascaded layer 22 of the private cloud 201 as a cascaded OpenStack.
而在被级联的第三方云202中，可以由创建的云网关203管理云网关203内租户创建的各个租户虚拟机(tenant VM)。第三方云202对外可提供统一标准的OpenStackAPI，对内可支持第三方云202自身的API，以AWS(Amazon Web Service，亚马逊提供的公有云计算服务)云作为第三方云202为例，AWS云可以通过OpenStack API接收租户或级联OpenStack发送的API请求，并将该API请求转换为支持AWS云的API请求，进而使用支持AWS云的API请求在第三方云202中实现相关服务。In the cascaded third-party cloud 202, the created cloud gateway 203 can manage each tenant virtual machine (tenant VM) created by the tenant in the cloud gateway 203 . The third-party cloud 202 can provide a unified standard OpenStack API externally, and can support the API of the third-party cloud 202 internally. Taking AWS (Amazon Web Service, a public cloud computing service provided by Amazon) cloud as the third-party cloud 202 as an example, the AWS cloud The API request sent by the tenant or the cascaded OpenStack can be received through the OpenStack API, and the API request can be converted into an API request supporting the AWS cloud, and then related services can be implemented in the third-party cloud 202 by using the API request supporting the AWS cloud.
以下，以AWS云作为上述第三方云202举例，详细阐述本发明实施提供的一种部署云网关的方法，如图4所示，该方法包括：Hereinafter, taking AWS cloud as the above-mentioned third-party cloud 202 as an example, a method for deploying a cloud gateway provided by the implementation of the present invention is described in detail, as shown in FIG. 4 , the method includes:
401、管理员在AWS云上注册用户。401. The administrator registers a user on the AWS cloud.
在使用AWS云(即第三方云)提供的相关服务之前，管理员需要在AWS云上注册用户。注册的用户可以具有特定的权限与资源配额，使其能够创建云网关(CloudGateway)和租户虚拟机。Before using related services provided by the AWS cloud (that is, third-party clouds), administrators need to register users on the AWS cloud. Registered users can have specific permissions and resource quotas, enabling them to create cloud gateways (CloudGateway) and tenant virtual machines.
示例性的，该特定的权限可以包括Amazon EC2Full Access(亚马逊EC2服务的全访问授权)，Amazon S3Full Access(亚马逊S3服务的全访问授权)，AWS Import ExportFull Access(亚马逊输入输出的全访问授权)，IAM Read Only Access(IAM只读访问授权)，Amazon RDS Read Only Access(亚马逊RDS只读访问授权)，AWS Support Access(支持AWS访问授权)，IAM Self Manage Service Specific Credentials(IAM自管理服务的特定授权)等，本发明实施例对此不作任何限制。Exemplarily, the specific permission may include Amazon EC2Full Access (full access authorization of Amazon EC2 service), Amazon S3Full Access (full access authorization of Amazon S3 service), AWS Import ExportFull Access (full access authorization of Amazon input and output), IAM Read Only Access (IAM read-only access authorization), Amazon RDS Read Only Access (Amazon RDS read-only access authorization), AWS Support Access (support AWS access authorization), IAM Self Manage Service Specific Credentials (IAM self-management service specific authorization ), etc., the embodiment of the present invention does not make any limitation on this.
402、管理员在AWS云上创建VPC及子网。402. The administrator creates a VPC and a subnet on the AWS cloud.
在得到一个在AWS云上使用的账号后，管理员可以使用该账号在AWS云(第三方云)中某个区域(region)，例如，AWS云的首尔、东京等region中创建VPC，使得租户后续在AWS云上部署的服务可以与外界隔离开来。After getting an account used on the AWS cloud, the administrator can use the account to create a VPC in a certain region (region) in the AWS cloud (third-party cloud), for example, Seoul, Tokyo and other regions of the AWS cloud, so that tenants Subsequent services deployed on the AWS cloud can be isolated from the outside world.
进一步地，如果创建的VPC内部还需要进一步的网络划分，租户还可以在创建的VPC内创建一个或多个子网，例如，管理子网om_net和租户子网ext_net。Furthermore, if further network division is required within the created VPC, the tenant can also create one or more subnets in the created VPC, for example, the management subnet om_net and the tenant subnet ext_net.
403、管理员在AWS云上配置VPN(Virtual Private Network，虚拟专用网络)网关。403. The administrator configures a VPN (Virtual Private Network, virtual private network) gateway on the AWS cloud.
404、管理员在私有云所在的级联OpenStack上配置VPN网关，以建立私有云与AWS云之间的VPN隧道。404. The administrator configures a VPN gateway on the cascaded OpenStack where the private cloud is located, so as to establish a VPN tunnel between the private cloud and the AWS cloud.
在步骤403-404中，为了实现私有云中的级联OpenStack与AWS云内后续创建的云网关之间的通信功能，可以在AWS云和级联OpenStack中均配置VPN网关，这样，通过网络隧道协议，可建立私有云与AWS云之间的VPN隧道，后续，私有云与AWS云之间便可以通过建立的VPN隧道进行通信。In steps 403-404, in order to realize the communication function between the cascaded OpenStack in the private cloud and the cloud gateway created subsequently in the AWS cloud, VPN gateways can be configured in both the AWS cloud and the cascaded OpenStack, so that through the network tunnel The protocol can establish a VPN tunnel between the private cloud and the AWS cloud, and subsequently, the private cloud and the AWS cloud can communicate through the established VPN tunnel.
至此，通过执行步骤401-404，便可完成在AWS云内部署云网关的准备工作，后续，可继续执行下述步骤405-409在AWS云内部署云网关。So far, by performing steps 401-404, the preparations for deploying the cloud gateway in the AWS cloud can be completed, and subsequently, the following steps 405-409 can be performed to deploy the cloud gateway in the AWS cloud.
405、响应于管理员在UI(User Interface，用户界面)上触发的云网关部署请求，CCS节点在AWS云内创建云网关的安全组。405. In response to a cloud gateway deployment request triggered by an administrator on a UI (User Interface, user interface), the CCS node creates a cloud gateway security group in the AWS cloud.
具体的，管理员可以在私有云的UI界面上选择为AWS云创建云网关的选项，那么，当检测得到管理员在UI界面上触发创建云网关的选项时，私有云可生成云网关部署请求，并将该云网关部署请求发送给私有云的CCS节点。Specifically, the administrator can select the option to create a cloud gateway for the AWS cloud on the UI interface of the private cloud. Then, when the administrator triggers the option to create a cloud gateway on the UI interface, the private cloud can generate a cloud gateway deployment request. , and send the cloud gateway deployment request to the CCS node of the private cloud.
CCS节点在接收到该云网关部署请求后，首先会在步骤402中创建的VPC内创建云网关的安全组，并为后续创建的承载云网关的多个虚拟机之间、云网关与级联OpenStack之间以及云网关与租户虚拟机之间设置安全组规则，形成防火墙，以提高后续建立的云网关的安全性。After receiving the cloud gateway deployment request, the CCS node will first create a security group for the cloud gateway in the VPC created in step 402, and create a security group for the subsequently created multiple virtual machines carrying the cloud gateway, the cloud gateway and the cascading Security group rules are set between OpenStack and between the cloud gateway and tenant virtual machines to form a firewall to improve the security of the subsequently established cloud gateway.
406、CCS节点在AWS云内创建云网关的浮动IP。406. The CCS node creates a floating IP of the cloud gateway in the AWS cloud.
在步骤406中，由于后续创建的云网关与AWS云内的第三方云接口是通过浮动IP通信的，因此，CCS节点还可以在AWS云内创建云网关的浮动IP，这样，当AWS内的云网关创建完成后，可以与上述创建的浮动IP绑定，从而实现与AWS云内的第三方云接口通信。In step 406, since the subsequently created cloud gateway communicates with the third-party cloud interface in the AWS cloud through a floating IP, the CCS node can also create a floating IP of the cloud gateway in the AWS cloud. After the cloud gateway is created, it can be bound to the floating IP created above to realize communication with the third-party cloud interface in the AWS cloud.
407、CCS节点在AWS云内创建承载云网关的虚拟机。407. The CCS node creates a virtual machine carrying the cloud gateway in the AWS cloud.
在步骤407中，CCS节点可以在步骤402中创建的VPC的管理子网om_net中，创建承载云网关的虚拟机，即以虚拟机的形式部署AWS节点内的云网关，并将步骤406中创建的浮动IP与上述虚拟机绑定。In step 407, the CCS node can create a virtual machine carrying the cloud gateway in the management subnet om_net of the VPC created in step 402, that is, deploy the cloud gateway in the AWS node in the form of a virtual machine, and The floating IP is bound to the above virtual machine.
其中，上述承载云网关的虚拟机可以为一个或多个，本发明实施例对此不作任何限制。Wherein, there may be one or more virtual machines carrying the cloud gateway, which is not limited in this embodiment of the present invention.
408、云连接器在创建的虚拟机上部署混合云服务。408. The cloud connector deploys the hybrid cloud service on the created virtual machine.
409、云连接器在级联OpenStack中注册云网关提供的混合云服务，以使得AWS云作为被级联OpenStack与级联OpenStack实现对接。409. The cloud connector registers the hybrid cloud service provided by the cloud gateway in the cascaded OpenStack, so that the AWS cloud as the cascaded OpenStack realizes interconnection with the cascaded OpenStack.
在步骤408中，当上述承载云网关的虚拟机成功启动后，私有云中的云连接器可进一步在上述虚拟机上部署实现图2或图3所示的混合云网络架构所需的混合云服务，例如，云API适配器(Cloud API Adapter，CAA)、数据库服务、消息代理(rabbitmq)服务等，本发明实施例对此不作任何限制。In step 408, after the virtual machine carrying the cloud gateway is successfully started, the cloud connector in the private cloud can further deploy the hybrid cloud required to realize the hybrid cloud network architecture shown in Figure 2 or Figure 3 on the virtual machine Services, such as cloud API adapter (Cloud API Adapter, CAA), database service, message broker (rabbitmq) service, etc., are not limited in this embodiment of the present invention.
其中，云网关中部署的CAA在北向可提供标准的OpenStack API接口，在南向可提供AWS云的API接口(即第三方云的私有API接口)。也就是说，CAA对外可通过调用OpenStackAPI接口接收私有云发送的API请求，在AWS云(第三方云)内可将将通过OpenStack API接口接收到的API请求转换为支持AWS云的私有API的API请求。这样，作为被级联OpenStack的AWS云也可以使用统一标准的OpenStackAPI接口提供云服务，从而可以屏蔽不同云间的API差异，提高混合云网络的兼容性和API请求处理效率。Among them, the CAA deployed in the cloud gateway can provide the standard OpenStack API interface in the north, and the API interface of the AWS cloud (that is, the private API interface of the third-party cloud) in the south. That is to say, CAA can externally receive API requests sent by the private cloud by calling the OpenStack API interface, and in the AWS cloud (third-party cloud) can convert the API requests received through the OpenStack API interface into APIs that support the private API of the AWS cloud ask. In this way, the AWS cloud as a cascaded OpenStack can also use the unified standard OpenStack API interface to provide cloud services, so that API differences between different clouds can be shielded, and the compatibility of the hybrid cloud network and the processing efficiency of API requests can be improved.
进一步地，在步骤409中，云连接器在上述虚拟机上部署混合云服务后，还需要在级联OpenStack中注册上述混合云服务，这样，级联OpenStack能够将租户向AWS云请求的云服务正确的透传至AWS云的云网关，由云网关管理AWS云为租户提供相关云服务，从而实现云网关所属的AWS云作为被级联OpenStack与级联OpenStack完成对接。Further, in step 409, after the cloud connector deploys the hybrid cloud service on the above-mentioned virtual machine, it also needs to register the above-mentioned hybrid cloud service in the cascaded OpenStack, so that the cascaded OpenStack can transfer the cloud service requested by the tenant to the AWS cloud Correct transparent transmission to the cloud gateway of the AWS cloud, and the cloud gateway manages the AWS cloud to provide tenants with related cloud services, so that the AWS cloud to which the cloud gateway belongs can be connected with the cascaded OpenStack as the cascaded OpenStack.
具体的，云连接器可以在级联OpenStack中注册云网关的服务endpoint，例如，将被级联的AWS云中的nova服务组件、cinder服务组件、neutron服务组件、CAA等服务endpoint，注册在级联OpenStack的keystone服务中，以供其他服务通过级联OpenStack访问被级联的AWS云。Specifically, the cloud connector can register the service endpoint of the cloud gateway in the cascaded OpenStack. For example, service endpoints such as nova service components, cinder service components, neutron service components, and CAA in the cascaded AWS cloud will be registered at the level In the keystone service of cascaded OpenStack, other services can access the cascaded AWS cloud through cascaded OpenStack.
进一步地，云连接器还可以在级联OpenStack中部署proxy服务，例如，部署compute-proxy、network-proxy、blockstorage-proxy、ceilometer-proxy等服务，各个proxy服务负责与AWS中的云网关对接，使得级联OpenStack可以将租户向AWS云的请求转发至云网关。Further, the cloud connector can also deploy proxy services in the cascaded OpenStack, for example, deploy compute-proxy, network-proxy, blockstorage-proxy, ceilometer-proxy and other services, each proxy service is responsible for docking with the cloud gateway in AWS, This enables cascaded OpenStack to forward tenant requests to the AWS cloud to the cloud gateway.
另外，云连接器还可以在级联OpenStack中配置DNS(Domain Name System，域名系统)，以保证私有云能够正确解析上述注册在级联OpenStack中的服务endpoint。In addition, the cloud connector can also configure DNS (Domain Name System, domain name system) in the cascaded OpenStack to ensure that the private cloud can correctly resolve the above-mentioned service endpoints registered in the cascaded OpenStack.
至此，通过步骤401-409，完成了部署云网关前的准备工作，创建承载云网关的虚拟机，以及配置云网关这三个过程，使得云网关所在的第三方云AWS云可以作为一个被级联的OpenStack部署在私有云的被级联层中，形成混合云的网络架构。在该混合云的网络架构中，无论是级联层的私有云，还是被级联层的AWS云，均可提供统一标准的OpenStack API接口，从而可以屏蔽不同云间的API差异，提高混合云网络的兼容性和API请求处理效率。So far, through steps 401-409, the preparatory work before deploying the cloud gateway has been completed, the three processes of creating a virtual machine to host the cloud gateway, and configuring the cloud gateway, so that the third-party cloud AWS cloud where the cloud gateway is located can be used as a The connected OpenStack is deployed in the cascaded layer of the private cloud to form a hybrid cloud network architecture. In the network architecture of this hybrid cloud, both the private cloud at the cascaded layer and the AWS cloud at the cascaded layer can provide a unified standard OpenStack API interface, which can shield the API differences between different clouds and improve the performance of the hybrid cloud. Network compatibility and API request processing efficiency.
在本申请的一些实施例中，在第三方云(例如，上述AWS云)中部署了云网关后，租户便可以在私有云的级联OpenStack中向被级联层的AWS云发起虚拟资源请求，以使用被级联层的AWS云为自身提供相关的云服务。In some embodiments of the present application, after a cloud gateway is deployed in a third-party cloud (for example, the aforementioned AWS cloud), the tenant can initiate a virtual resource request to the cascaded AWS cloud in the cascaded OpenStack of the private cloud , to use the AWS cloud of the cascaded layer to provide related cloud services for itself.
例如，租户可以在私有云的UI上发起虚拟机的创建请求，那么，当私有云中的虚拟资源不足时，私有云中的级联OpenStack可以向被级联层的AWS云发起虚拟机创建请求，从而在AWS云内创建虚拟机供租户使用。For example, a tenant can initiate a virtual machine creation request on the private cloud UI. Then, when the virtual resources in the private cloud are insufficient, the cascaded OpenStack in the private cloud can initiate a virtual machine creation request to the cascaded AWS cloud , so as to create virtual machines in the AWS cloud for tenants to use.
对此，本发明实施例提供一种虚拟资源的分配方法，如图5所示，包括：In this regard, an embodiment of the present invention provides a method for allocating virtual resources, as shown in FIG. 5 , including:
501、CCS节点向AWS云中的CAA注册在OpenStack API与AWS云的私有API之间传递参数时的参数映射关系。501. The CCS node registers with the CAA in the AWS cloud the parameter mapping relationship when passing parameters between the OpenStack API and the private API of the AWS cloud.
AWS云内部提供的各种服务都是基于AWS的私有API实现的，而AWS云对外，例如，对级联层的OpenStack，暴露的接口为统一标准的OpenStack API。因此，需要预先将OpenStack API与AWS的私有API之间传递参数时的参数映射关系注册到AWS云中。The various services provided by the AWS cloud are implemented based on AWS's private API, and the external interface of the AWS cloud, for example, for OpenStack at the cascading layer, is the unified standard OpenStack API. Therefore, the parameter mapping relationship when passing parameters between the OpenStack API and the private API of AWS needs to be registered in the AWS cloud in advance.
例如，在调用OpenStack API创建一个虚拟机时，生成的虚拟机创建请求中携带的flavor ID(即第一配置参数)为m1.small，而该flavor ID映射至AWS云的私有API时，该flavor ID可能转变为t2.small(即第二配置参数)；相应的，在调用OpenStackAPI创建一个虚拟卷时，生成的虚拟卷创建请求中携带的volume type(即第一卷类型参数)为SSD(SolidState Drives，固态硬盘)，而该volume type映射至AWS云的私有API时，该volume type可能转变为gp2(即第二卷类型参数)。For example, when calling the OpenStack API to create a virtual machine, the flavor ID (that is, the first configuration parameter) carried in the generated virtual machine creation request is m1.small, and when the flavor ID is mapped to the private API of the AWS cloud, the flavor The ID may change to t2.small (that is, the second configuration parameter); correspondingly, when calling OpenStackAPI to create a virtual volume, the volume type (that is, the first volume type parameter) carried in the generated virtual volume creation request is SSD (SolidState Drives, solid-state disk), and when the volume type is mapped to the private API of the AWS cloud, the volume type may be changed to gp2 (that is, the second volume type parameter).
因此，可以在私有云的CCS节点中预先建立同一参数在OpenStack API与AWS云的私有API之间的参数映射关系，例如，上述m1.small与t2.small之间的参数映射关系，以及上述SSD与gp2之间的参数映射关系，并将该参数映射关系存储在CCS节点的数据库中，此时，可将数据库中该参数映射关系的状态位设置为：Unsynced(未同步)。Therefore, the parameter mapping relationship between the OpenStack API and the private API of the AWS cloud for the same parameter can be pre-established in the CCS node of the private cloud, for example, the parameter mapping relationship between the above-mentioned m1.small and t2.small, and the above-mentioned SSD and the parameter mapping relationship between gp2, and store the parameter mapping relationship in the database of the CCS node. At this time, the status bit of the parameter mapping relationship in the database can be set as: Unsynced (unsynchronized).
进而，如图6所示，CCS节点可以启用线程异步调用AWS云中的CAA映射接口，将上述参数映射关系同步至云网关的CAA中，此时，可将数据库中该参数映射关系的状态位设置为：Syncing(正在同步)；那么，如果同步成功，则CCS节点可将数据库中该参数映射关系的状态位设置为：synced(已同步)。Furthermore, as shown in Figure 6, the CCS node can enable the thread to asynchronously call the CAA mapping interface in the AWS cloud, and synchronize the above parameter mapping relationship to the CAA of the cloud gateway. At this time, the status bit of the parameter mapping relationship in the database can be set to Set to: Syncing (synchronizing); then, if the synchronization is successful, the CCS node can set the status bit of the parameter mapping relationship in the database to: synced (synchronized).
另外，在CCS节点向AWS云中的CAA注册OpenStack API与AWS的私有API之间的参数映射关系时，如果发生DNS解析失败、网络不通或者CAA服务异常等情况时，可能会导致同步失败。此时，CCS节点可以定期读取其数据库中记录的上述参数映射关系的状态位，当状态位为Syncing时，CCS可调用AWS云中的CAA查询映射接口，查询CAA中是否存在该参数映射关系，如果存在，则CCS节点可进一步更新CAA中的已同步的该参数映射关系；否则，CCS节点可在云网关的CAA中创建该参数映射关系，并将CCS节点的数据库中该参数映射关系的状态位设置为：synced。In addition, when the CCS node registers the parameter mapping relationship between the OpenStack API and the private API of AWS with the CAA in the AWS cloud, if DNS resolution fails, the network is disconnected, or the CAA service is abnormal, the synchronization may fail. At this time, the CCS node can regularly read the status bit of the above parameter mapping relationship recorded in its database. When the status bit is Syncing, CCS can call the CAA query mapping interface in the AWS cloud to query whether the parameter mapping relationship exists in CAA , if it exists, the CCS node can further update the synchronized parameter mapping relationship in the CAA; otherwise, the CCS node can create the parameter mapping relationship in the CAA of the cloud gateway, and update the parameter mapping relationship in the database of the CCS node The status bit is set to: synced.
502、获取租户在级联OpenStack上向AWS云发起的虚拟资源请求。502. Obtain a virtual resource request initiated by a tenant to the AWS cloud on the cascaded OpenStack.
其中，上述虚拟资源请求具体可以为虚拟机创建请求或者虚拟卷创建请求等需要AWS云提供云服务的请求，本发明实施例对此不作任何限制。Wherein, the above-mentioned virtual resource request may specifically be a virtual machine creation request or a virtual volume creation request, which requires the AWS cloud to provide cloud services, which is not limited in this embodiment of the present invention.
示例性的，在步骤502中，租户可以在私有云的UI上向AWS云发起虚拟机创建请求，该虚拟机创建请求中携带了待创建的虚拟机的第一配置参数(flavor ID)，例如，该第一配置参数为m1.small。Exemplarily, in step 502, the tenant can initiate a virtual machine creation request to the AWS cloud on the UI of the private cloud, and the virtual machine creation request carries the first configuration parameter (flavor ID) of the virtual machine to be created, for example , the first configuration parameter is m1.small.
或者，租户可以在私有云的UI上向AWS云发起虚拟卷创建请求，该虚拟卷创建请求中携带了待创建的虚拟卷的第一卷类型参数(volume type)，例如，该第一卷类型参数为SSD。Alternatively, the tenant can initiate a virtual volume creation request to the AWS cloud on the UI of the private cloud, and the virtual volume creation request carries the first volume type parameter (volume type) of the virtual volume to be created, for example, the first volume type The parameter is SSD.
由于级联OpenStack的北向接口为OpenStack API接口，因此，级联OpenStack可通过调用其北向的OpenStack API获取上述虚拟资源请求。Since the northbound interface of the cascaded OpenStack is an OpenStack API interface, the cascaded OpenStack can obtain the above virtual resource request by calling its northbound OpenStack API.
503、级联OpenStack向AWS云中的云网关发送上述虚拟资源请求。503. The cascaded OpenStack sends the virtual resource request to the cloud gateway in the AWS cloud.
由于级联OpenStack的南向接口也为OpenStack API接口，且AWS云中的云网关的北向接口也为OpenStack API接口，因此，仍如图6所示，级联OpenStack可以通过调用OpenStack API接口，向AWS云中的云网关透传上述虚拟资源请求。Since the southbound interface of the cascaded OpenStack is also an OpenStack API interface, and the northbound interface of the cloud gateway in the AWS cloud is also an OpenStack API interface, as shown in Figure 6, the cascaded OpenStack can call the OpenStack API interface to The cloud gateway in the AWS cloud transparently transmits the above virtual resource requests.
504、云网关接收到上述虚拟资源请求后，将上述虚拟资源请求转换为支持AWS云的私有API的API请求。504. After receiving the virtual resource request, the cloud gateway converts the virtual resource request into an API request supporting a private API of the AWS cloud.
以上述虚拟资源请求中的flavor ID为m1.small，volume type为SSD举例，在步骤504中，云网关接收到上述虚拟资源请求后，仍如图6所示，云网关可以根据其CAA中记录的在OpenStack API与AWS的私有API之间传递参数时的参数映射关系，将接收到的虚拟资源请求中的flavor ID修改为t2.small，并将拟资源请求中的volumetype修改为gp2，得到支持AWS云的私有API的API请求。Taking the flavor ID in the above virtual resource request as m1.small and the volume type as SSD as an example, in step 504, after the cloud gateway receives the above virtual resource request, as shown in Figure 6, the cloud gateway can record The parameter mapping relationship when passing parameters between OpenStack API and AWS private API, modify the flavor ID in the received virtual resource request to t2.small, and modify the volumetype in the virtual resource request to gp2, which is supported API requests for private APIs of the AWS cloud.
505、云网关根据支持AWS云的私有API的API请求，调用AWS云的私有API将AWS云中的虚拟资源划分给私有云。505. The cloud gateway calls the private API of the AWS cloud to divide the virtual resources in the AWS cloud to the private cloud according to the API request supporting the private API of the AWS cloud.
这样，在步骤505中，仍如图6所示，云网关可以根据上述支持AWS云的私有API的API请求，沿用现有技术在AWS云中创建租户指定flavor ID的虚拟机和租户指定volumetype的虚拟卷，即将AWS云中的虚拟资源划分给私有云使用，实现混合云网络架构中不同云间的资源调度。In this way, in step 505, as shown in Figure 6, the cloud gateway can follow the existing technology to create a virtual machine with a tenant-specified flavor ID and a tenant-specified volumetype in the AWS cloud according to the above-mentioned API request supporting the private API of the AWS cloud. Virtual volumes, which divide virtual resources in the AWS cloud to private clouds, realize resource scheduling between different clouds in the hybrid cloud network architecture.
可以看出，通过在云网关的CAA中注册OpenStack API与AWS云的API之间的参数映射关系，使得第三方云可通过OpenStack API与级联层的私有云交互，实现虚拟资源在不同云之间的统一调度过程。It can be seen that by registering the parameter mapping relationship between the OpenStack API and the API of the AWS cloud in the CAA of the cloud gateway, the third-party cloud can interact with the private cloud of the cascaded layer through the OpenStack API, so that virtual resources can be distributed among different clouds. The unified scheduling process among them.
由于OpenStack可提供实施简单、可大规模扩展、丰富、标准统一的API接口，而本申请实施例中的私有云和第三方云均可通过OpenStack API进行交互，那么，租户在第三方云和在私有云上的用户体验和操作方式一致，从而屏蔽了第三方云因API接口不同而导致的云间差异。Because OpenStack can provide simple implementation, large-scale scalability, rich, unified standard API interface, and the private cloud and the third-party cloud in the embodiment of this application can interact through the OpenStack API, then, the tenants in the third-party cloud and in the The user experience and operation mode on the private cloud are consistent, thus shielding the differences between clouds caused by the different API interfaces of third-party clouds.
在本申请的另一些实施例中，当租户在第三方云(例如，上述AWS云)上创建虚拟机(即租户虚拟机，tenant VM)后，租户还可以在私有云的级联OpenStack中为第三方云中的tenant VM绑定浮动IP，从而使用该绑定的浮动IP访问租户虚拟机。In some other embodiments of the present application, after the tenant creates a virtual machine (that is, a tenant virtual machine, tenant VM) on a third-party cloud (for example, the above-mentioned AWS cloud), the tenant can also create a virtual machine in the cascaded OpenStack of the private cloud for The tenant VM in the third-party cloud is bound to a floating IP, so that the tenant VM can be accessed using the bound floating IP.
对此，本发明实施例提供一种浮动IP的分配方法，如图7所示，包括：In this regard, the embodiment of the present invention provides a floating IP allocation method, as shown in Figure 7, including:
701、私有云中的CCS节点申请AWS云中的浮动IP，并将申请到的浮动IP记录在IP资源池中。701. The CCS node in the private cloud applies for a floating IP in the AWS cloud, and records the applied floating IP in the IP resource pool.
由于级联OpenStack中并不能获知AWS云中可用的浮动IP，那么，当租户通过级联OpenStack统一提供的OpenStack API申请浮动IP，以访问AWS云中的租户虚拟机时，级联OpenStack可能无法为AWS云中的租户虚拟机申请到可用的浮动IP。Since the cascaded OpenStack cannot know the floating IP available in the AWS cloud, when the tenant applies for a floating IP through the OpenStack API provided by the cascaded OpenStack to access the tenant virtual machine in the AWS cloud, the cascaded OpenStack may not be able to provide Tenant VMs in the AWS cloud apply for available floating IPs.
对此，在本发明实施例中，私有云中的CCS节点可以预先从AWS云中申请浮动IP，并将申请到的浮动IP记录在IP资源池中，实时维护该IP资源池内的浮动IP，保证租户从级联OpenStack中申请到的浮动IP可用。For this, in the embodiment of the present invention, the CCS node in the private cloud can apply for a floating IP from the AWS cloud in advance, and record the applied floating IP in the IP resource pool, and maintain the floating IP in the IP resource pool in real time, Ensure that the floating IPs that tenants apply for from the cascaded OpenStack are available.
具体的，如图8所示，CCS节点可调用AWS云的API接口，申请AWS云中可用的浮动IP，例如，CCS节点申请到的浮动IP为52.127.156.112和13.50.128.223。进而，CCS节点将申请到的浮动IP存储至其数据库内的IP资源池中，此时，该IP资源池中申请到的浮动IP的状态为Unsynced(未同步)。Specifically, as shown in Figure 8, the CCS node can call the API interface of the AWS cloud to apply for a floating IP available in the AWS cloud. For example, the floating IPs applied for by the CCS node are 52.127.156.112 and 13.50.128.223. Furthermore, the CCS node stores the applied floating IP into the IP resource pool in its database, and at this time, the state of the applied floating IP in the IP resource pool is Unsynced (unsynchronized).
702、私有云中的CCS节点将上述IP资源池中的浮动IP同步至级联OpenStack。702. The CCS node in the private cloud synchronizes the floating IP in the IP resource pool to the cascaded OpenStack.
具体的，仍如图8所示，CCS节点可以向级联OpenStack中的neutron服务组件发送neutron API请求，由neutron服务组件在外部网络中注册上述IP资源池中新增的浮动IP：52.127.156.112和13.50.128.223。Specifically, as shown in Figure 8, the CCS node can send a neutron API request to the neutron service component in the cascaded OpenStack, and the neutron service component will register the new floating IP in the above IP resource pool in the external network: 52.127.156.112 and 13.50.128.223.
另外，在第一次向级联OpenStack同步浮动IP时，级联OpenStack的neutron服务组件接收到CCS节点发送的neutron API请求后，可先创建名称为hybrid_cloud_{cloud_type}_{cloud_region}的外部网络。In addition, when the floating IP is synchronized to the cascaded OpenStack for the first time, the neutron service component of the cascaded OpenStack can create an external network named hybrid_cloud_{cloud_type}_{cloud_region} after receiving the neutron API request sent by the CCS node.
进而，由于每个浮动IP都有其从属的无类别域间路由(Classless InterDomainRouting，CIDR)，那么，CCS节点可以按照申请到的浮动IP的CIDR，在上述外部网络中创建子网，并在该子网的IP资源池(例如，allocation_pools)中增加刚申请的浮动IP，使得IP资源池中的浮动IP同步至级联OpenStack。Furthermore, since each floating IP has its subordinate Classless InterDomainRouting (CIDR), then, the CCS node can create a subnet in the above-mentioned external network according to the CIDR of the floating IP applied for, and in this Add the newly applied floating IP to the IP resource pool (for example, allocation_pools) of the subnet, so that the floating IP in the IP resource pool is synchronized to the cascaded OpenStack.
可选的，CCS节点还可以在内层EIP网络中注册租户网络，例如，注册的租户网络为172.100.16.0/24，该IP地址可在级联OpenStack的内网中使用。Optionally, the CCS node can also register a tenant network in the internal EIP network. For example, the registered tenant network is 172.100.16.0/24, and this IP address can be used in the internal network of the cascaded OpenStack.
703、私有云中的CCS节点将上述IP资源池中的浮动IP同步至AWS云中的云网关。703. The CCS node in the private cloud synchronizes the floating IP in the IP resource pool to the cloud gateway in the AWS cloud.
在步骤703中，私有云中的CCS节点还可以向AWS云中云网关内的neutron服务组件发送neutron API请求，由neutron服务组件在外部网络(例如，名称为external_relay_network的外部网络)中注册上述IP资源池中新增的浮动IP：52.127.156.112和13.50.128.223。In step 703, the CCS node in the private cloud can also send a neutron API request to the neutron service component in the cloud gateway in the AWS cloud, and the above-mentioned IP is registered in the external network (for example, the external network named external_relay_network) by the neutron service component Newly added floating IPs in the resource pool: 52.127.156.112 and 13.50.128.223.
类似的，在第一次向AWS云同步浮动IP时，云网关中的neutron服务组件接收到CCS节点发送的neutron API请求后，可先创建名称为上述external_relay_network的外部网络，进而将上述IP资源池中的浮动IP注册至该外部网络中。Similarly, when synchronizing the floating IP to the AWS cloud for the first time, the neutron service component in the cloud gateway can first create the external network named external_relay_network after receiving the neutron API request sent by the CCS node, and then transfer the above IP resource pool to Register the floating IP in the external network.
另外，如果在步骤702中CCS节点在内层EIP网络中注册了租户网络，则云网关中的neutron服务组件还可以将该租户网络一并同步至名称为external_relay_network的外部网络中。In addition, if the CCS node has registered the tenant network in the inner EIP network in step 702, the neutron service component in the cloud gateway can also synchronize the tenant network to the external network named external_relay_network.
704、级联OpenStack接收租户发起的浮动IP请求，该浮动IP请求用于请求浮动IP访问AWS云中的租户虚拟机。704. The cascaded OpenStack receives a floating IP request initiated by the tenant, where the floating IP request is used to request the floating IP to access the tenant virtual machine in the AWS cloud.
705、级联OpenStack从上述IP资源池中为该租户虚拟机分配一个目标浮动IP，以使得租户通过该目标浮动IP访问该租户虚拟机。705. The cascaded OpenStack allocates a target floating IP to the tenant virtual machine from the IP resource pool, so that the tenant accesses the tenant virtual machine through the target floating IP.
在步骤704-705中，当租户在级联层上发起对AWS云中某个租户虚拟机的浮动IP请求时，级联OpenStack可以从上述已同步的IP资源池中为AWS云中的租户虚拟机分配一个目标浮动IP，并将该目标浮动IP绑定至AWS中的租户虚拟机上，使得租户可以通过该目标浮动IP能够访问该租户虚拟机。In steps 704-705, when the tenant initiates a floating IP request for a tenant virtual machine in the AWS cloud on the cascading layer, the cascading OpenStack can provide the tenant virtual machine in the AWS cloud from the above-mentioned synchronized IP resource pool. The machine allocates a target floating IP, and binds the target floating IP to the tenant virtual machine in AWS, so that the tenant can access the tenant virtual machine through the target floating IP.
进一步地，将上述IP资源池中的目标浮动IP绑定至AWS中的租户虚拟机之后，该目标浮动IP已经被占用，后续当级联OpenStack接收新的浮动IP请求时，可以将上述IP资源池中未占用的浮动IP分配给租户。Further, after the target floating IP in the above IP resource pool is bound to the tenant virtual machine in AWS, the target floating IP has been occupied, and when the cascaded OpenStack receives a new floating IP request, the above IP resource can be Unoccupied floating IPs in the pool are assigned to tenants.
另外，当管理员向级联OpenStack中下发释放某个浮动IP(例如上述目标浮动IP)的请求时，CCS节点可以在上述IP资源池中删除该目标浮动IP，并调用级联OpenStack的neutron接口，在级联层的外部网络和EIP内部网络中删除该目标浮动IP；并且，CCS节点还可以调用被级联层云网关中的neutron接口，在云网关的外部网络中删除该目标浮动IP，从而保证用户从级联层的IP资源池中申请到的浮动IP可用。In addition, when the administrator sends a request to release a certain floating IP (such as the above-mentioned target floating IP) to the cascaded OpenStack, the CCS node can delete the target floating IP in the above-mentioned IP resource pool, and call the neutron of the cascaded OpenStack Interface, delete the target floating IP in the external network of the cascaded layer and the EIP internal network; and, the CCS node can also call the neutron interface in the cloud gateway of the cascaded layer to delete the target floating IP in the external network of the cloud gateway , so as to ensure that the floating IP that the user applies for from the IP resource pool of the cascading layer is available.
至此，本发明实施例中通过在第三方云中部署云网关，使得第三方云可以作为被级联OpenStack与私有云的级联OpenStack对接，从而提供了面向多种混合云的统一标准的OpenStack API接口。租户可以通过通过该OpenStack API接口实现在私有云和第三方云上的无差别操作体验，即屏蔽了不同云间的API差异，从而提高混合云网络的兼容性和API请求处理效率。So far, in the embodiment of the present invention, by deploying the cloud gateway in the third-party cloud, the third-party cloud can be connected with the cascaded OpenStack of the private cloud as the cascaded OpenStack, thereby providing a unified standard OpenStack API for multiple hybrid clouds interface. Tenants can use the OpenStack API interface to achieve an undifferentiated operating experience on private clouds and third-party clouds, that is, to shield API differences between different clouds, thereby improving the compatibility of hybrid cloud networks and the efficiency of API request processing.
上述主要从各个网元之间交互的角度对本发明实施例提供的方案进行了介绍。可以理解的是，上述UE、无线接入设备等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明实施例的范围。The foregoing mainly introduces the solutions provided by the embodiments of the present invention from the perspective of interaction between various network elements. It can be understood that, in order to realize the above functions, the foregoing UE, wireless access device, etc. include corresponding hardware structures and/or software modules for performing various functions. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the embodiments of the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the embodiments of the present invention.
本发明实施例可以根据上述方法示例对上述CCS节点、云网关等进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本发明实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。The embodiments of the present invention can divide the above-mentioned CCS nodes, cloud gateways, etc. into functional modules according to the above-mentioned method examples. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. middle. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present invention is schematic, and is only a logical function division, and there may be another division manner in actual implementation.
在采用对应各个功能划分各个功能模块的情况下，图9示出了上述实施例中所涉及的CCS节点的一种可能的结构示意图，该CCS节点包括：获取单元1101、发送单元1102、创建单元1103以及更新单元1104。In the case of dividing each functional module corresponding to each function, FIG. 9 shows a possible structural diagram of the CCS node involved in the above embodiment, and the CCS node includes: an acquisition unit 1101, a sending unit 1102, and a creation unit 1103 and an updating unit 1104.
其中，获取单元1101，用于：获取私有云中发起的虚拟资源请求，所述虚拟资源请求用于请求第三方云中的虚拟资源，所述私有云位于级联层，所述第三方云位于被级联层；Wherein, the obtaining unit 1101 is configured to: obtain a virtual resource request initiated in a private cloud, the virtual resource request is used to request a virtual resource in a third-party cloud, the private cloud is located at the cascade layer, and the third-party cloud is located at Cascaded layer;
发送单元1102，用于：通过调用OpenStack API将所述虚拟资源请求透传至所述第三方云的云网关中，以使得所述云网关根据所述虚拟资源请求调用所述第三方云的API将所述第三方云中的虚拟资源划分给所述私有云。The sending unit 1102 is configured to transparently transmit the virtual resource request to the cloud gateway of the third-party cloud by calling an OpenStack API, so that the cloud gateway calls the API of the third-party cloud according to the virtual resource request Allocating virtual resources in the third-party cloud to the private cloud.
进一步地，所述发送单元1102，还用于：向所述第三方云中的云网关发送在OpenStack API与第三方云的私有API之间传递参数时的参数映射关系。Further, the sending unit 1102 is further configured to: send the parameter mapping relationship when transferring parameters between the OpenStack API and the private API of the third-party cloud to the cloud gateway in the third-party cloud.
进一步地，创建单元1103，用于：在所述第三方云和所述私有云之间建立VPN隧道；在所述第三方云中创建承载云网关的虚拟机；在所述虚拟机中部署所述云网关提供的混合云服务，并将所述所述云网关提供的混合云服务注册在所述私有云中。Further, the creating unit 1103 is configured to: establish a VPN tunnel between the third-party cloud and the private cloud; create a virtual machine carrying a cloud gateway in the third-party cloud; deploy the virtual machine in the virtual machine the hybrid cloud service provided by the cloud gateway, and register the hybrid cloud service provided by the cloud gateway in the private cloud.
进一步地，更新单元1104，用于：在IP资源池中更新从所述第三方云中获取的至少一个浮动IP地址；将所述IP资源池中更新的浮动IP地址同步至所述私有云以及所述第三方云的云网关中。Further, the update unit 1104 is configured to: update at least one floating IP address obtained from the third-party cloud in the IP resource pool; synchronize the updated floating IP address in the IP resource pool to the private cloud; In the cloud gateway of the third-party cloud.
进一步地，所述获取单元1101，具体用于：通过调用OpenStack API获取私有云中发起的虚拟资源请求。Further, the acquiring unit 1101 is specifically configured to: acquire the virtual resource request initiated in the private cloud by calling the OpenStack API.
在采用对应各个功能划分各个功能模块的情况下，图10示出了上述实施例中所涉及的云网关的一种可能的结构示意图，该云网关包括：获取单元1201、转换单元1202以及执行单元1203。In the case of dividing each functional module corresponding to each function, FIG. 10 shows a possible structural diagram of the cloud gateway involved in the above embodiment, and the cloud gateway includes: an acquisition unit 1201, a conversion unit 1202 and an execution unit 1203.
其中，获取单元1201，用于：通过OpenStack API从私有云中获取虚拟资源请求，所述虚拟资源请求用于请求第三方云中的虚拟资源，所述私有云位于级联层，所述第三方云位于被级联层；Wherein, the obtaining unit 1201 is configured to: obtain a virtual resource request from a private cloud through an OpenStack API, the virtual resource request is used to request a virtual resource in a third-party cloud, the private cloud is located at the cascade layer, and the third-party The cloud is located in the cascaded layer;
转换单元1202，用于：将所述虚拟资源请求转换为支持所述第三方云的私有API的API请求；A conversion unit 1202, configured to: convert the virtual resource request into an API request supporting the private API of the third-party cloud;
执行单元1203，用于：按照所述API请求将所述第三方云中的虚拟资源划分给所述私有云。The executing unit 1203 is configured to: divide the virtual resource in the third-party cloud to the private cloud according to the API request.
进一步的，所述虚拟资源请求为虚拟机创建请求，所述虚拟机创建请求中携带待创建虚拟机的第一配置参数；所述转换单元1202，具体用于：根据预置的在OpenStackAPI与第三方云的私有API之间传递参数时的参数映射关系，查找与所述第一配置参数对应的第二配置参数；将所述虚拟机创建请求中的第一配置参数修改为所述第二配置参数，得到支持所述第三方云的私有API的API请求。Further, the virtual resource request is a virtual machine creation request, and the virtual machine creation request carries the first configuration parameter of the virtual machine to be created; the converting unit 1202 is specifically configured to: The parameter mapping relationship when passing parameters between the private APIs of the three-party cloud, searching for the second configuration parameter corresponding to the first configuration parameter; modifying the first configuration parameter in the virtual machine creation request to the second configuration Parameters to obtain an API request that supports the private API of the third-party cloud.
进一步的，所述虚拟资源请求为虚拟卷创建请求，所述虚拟卷创建请求中携带第一卷类型参数；所述转换单元1102，具体用于：根据预置的在OpenStack API与第三方云的私有API之间传递参数时的参数映射关系，查找与所述第一卷类型参数对应的第二卷类型参数；将所述虚拟卷创建请求中的第一卷类型参数修改为所述第二卷类型参数，得到支持所述第三方云的私有API的API请求。Further, the virtual resource request is a virtual volume creation request, and the virtual volume creation request carries a first volume type parameter; the conversion unit 1102 is specifically configured to: according to the preset OpenStack API and third-party cloud The parameter mapping relationship when passing parameters between private APIs, searching for the second volume type parameter corresponding to the first volume type parameter; modifying the first volume type parameter in the virtual volume creation request to the second volume The type parameter is used to obtain an API request that supports the private API of the third-party cloud.
进一步的，所述获取单元1101，还用于：接收所述私有云中CCS节点发送的在OpenStack API与第三方云的私有API之间传递参数时的参数映射关系。Further, the obtaining unit 1101 is further configured to: receive the parameter mapping relationship sent by the CCS node in the private cloud when transferring parameters between the OpenStack API and the private API of the third-party cloud.
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。Wherein, all relevant content of each step involved in the above-mentioned method embodiment can be referred to the function description of the corresponding function module, and will not be repeated here.
进一步地，上述CCS节点以及云网关均可以通过虚拟机的形式分别部署在OpenStack级联层和OpenStack被级联层。Further, the above-mentioned CCS nodes and cloud gateways can be respectively deployed in the OpenStack cascading layer and the OpenStack cascaded layer in the form of virtual machines.
其中，虚拟机(VM)，是指通过虚拟机软件可以在一台物理主机上模拟出一台或者多台虚拟的计算机，而这些虚拟机就像真正的计算机那样进行工作，虚拟机上可以安装操作系统和应用程序，虚拟机还可访问网络资源。对于在虚拟机中运行的应用程序而言，虚拟机就像是在真正的计算机中进行工作。Among them, a virtual machine (VM) refers to one or more virtual computers that can be simulated on a physical host through virtual machine software, and these virtual machines work like real computers. Operating systems and applications, virtual machines can also access network resources. To the applications running in the virtual machine, the virtual machine looks like working on a real computer.
具体的，参见图11所示，上述虚拟机可以部署在物理主机100中。Specifically, as shown in FIG. 11 , the aforementioned virtual machine may be deployed on a physical host 100 .
该该物理主机100包含硬件层、运行在所述硬件层之上的Host 1001、以及运行在所述Host 1001之上的至少一个虚拟机VM 1002，以及所述硬件层包括网卡1003，处理器1004和内存1005等。This physical host 100 includes a hardware layer, a Host 1001 running on the hardware layer, and at least one virtual machine VM 1002 running on the Host 1001, and the hardware layer includes a network card 1003, a processor 1004 and memory 1005 etc.
其中，硬件层是指虚拟化环境运行的硬件平台。其中，硬件层可包括多种硬件，例如某物理主机的硬件层可包括处理器(例如CPU)和内存，还可以包括网卡(例如RDMA网卡)、存储器等等高速/低速输入/输出(I/O，Input/Output)设备，及具有特定处理功能的其它设备。Wherein, the hardware layer refers to a hardware platform running in a virtualization environment. Wherein, the hardware layer may include multiple hardware, for example, the hardware layer of a physical host may include a processor (such as CPU) and memory, and may also include high-speed/low-speed input/output (I/O) such as network card (such as RDMA network card), memory, etc. O, Input/Output) equipment, and other equipment with specific processing functions.
宿主机(Host)：作为管理层，用以完成硬件资源的管理、分配；为虚拟机呈现虚拟硬件平台；实现虚拟机的调度和隔离。其中，Host可能是虚拟机监控器(VMM)；此外，有时VMM和1个特权虚拟机配合，两者结合组成Host。其中，虚拟硬件平台对其上运行的各个虚拟机提供各种硬件资源，如提供虚拟处理器(如VCPU)、虚拟内存、虚拟磁盘、虚拟网卡等等。其中，该虚拟磁盘可对应Host的一个文件或者一个逻辑块设备。虚拟机运行在Host为其准备的虚拟硬件平台上，Host上运行一个或多个虚拟机。Host: As a management layer, it is used to complete the management and allocation of hardware resources; present a virtual hardware platform for virtual machines; realize the scheduling and isolation of virtual machines. Among them, the Host may be a virtual machine monitor (VMM); in addition, sometimes the VMM cooperates with a privileged virtual machine, and the combination of the two forms the Host. Wherein, the virtual hardware platform provides various hardware resources for each virtual machine running on it, such as virtual processor (such as VCPU), virtual memory, virtual disk, virtual network card and so on. Wherein, the virtual disk may correspond to a file or a logical block device of the Host. The virtual machine runs on the virtual hardware platform prepared by the host, and one or more virtual machines run on the host.
应理解，本发明实施例可以应用于xen虚拟机平台中，也可以应用于可以应用于任意一个迁移虚拟机时需要将虚拟机内存进行映射的虚拟化平台中；本发明实施例对此不进行限制。It should be understood that the embodiment of the present invention can be applied to the xen virtual machine platform, and can also be applied to any virtualization platform that needs to map the memory of the virtual machine when migrating the virtual machine; the embodiment of the present invention does not discuss this limit.
在上述实施例中，可以全部或部分的通过软件，硬件，固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式出现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。该可用介质可以是磁性介质，(例如，软盘，硬盘、磁带)、光介质(例如，DVD)或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。In the above embodiments, all or part of the implementation may be implemented by software, hardware, firmware or any combination thereof. When implemented using a software program, it may appear in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present invention will be generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media. The available medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a Solid State Disk (SSD)).
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。The above is only a specific implementation of the application, but the protection scope of the application is not limited thereto, and any changes or replacements within the technical scope disclosed in the application should be covered within the protection scope of the application . Therefore, the protection scope of the present application should be determined by the protection scope of the claims.
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710547491.5ACN107357660A (en) | 2017-07-06 | 2017-07-06 | The distribution method and device of a kind of virtual resource |
| PCT/CN2018/094424WO2019007353A1 (en) | 2017-07-06 | 2018-07-04 | Method and device for allocating virtual resources |
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710547491.5ACN107357660A (en) | 2017-07-06 | 2017-07-06 | The distribution method and device of a kind of virtual resource |
| Publication Number | Publication Date |
|---|---|
| CN107357660Atrue CN107357660A (en) | 2017-11-17 |
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710547491.5APendingCN107357660A (en) | 2017-07-06 | 2017-07-06 | The distribution method and device of a kind of virtual resource |
| Country | Link |
|---|---|
| CN (1) | CN107357660A (en) |
| WO (1) | WO2019007353A1 (en) |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108512692A (en)* | 2018-02-24 | 2018-09-07 | 国家计算机网络与信息安全管理中心 | A kind of resource integrated method and device |
| CN109067903A (en)* | 2018-08-29 | 2018-12-21 | 郑州云海信息技术有限公司 | A kind of cloud platform cascade system |
| WO2019007353A1 (en)* | 2017-07-06 | 2019-01-10 | 华为技术有限公司 | Method and device for allocating virtual resources |
| CN109819061A (en)* | 2018-09-11 | 2019-05-28 | 华为技术有限公司 | A method, apparatus and device for processing cloud services in a cloud system |
| CN109818998A (en)* | 2017-11-22 | 2019-05-28 | 中国电信股份有限公司 | Information synchronization method and device |
| WO2019101408A1 (en)* | 2017-11-27 | 2019-05-31 | Endress+Hauser Process Solutions Ag | Interface apparatus for a data interchange between a field bus network and a cloud |
| CN109873872A (en)* | 2019-03-15 | 2019-06-11 | 浪潮通用软件有限公司 | A kind of cloud electrical connector and method for supporting mixing cloud mode |
| CN110557433A (en)* | 2019-07-26 | 2019-12-10 | 华云超融合科技有限公司 | Resource management method, platform, cloud gateway, system and storage medium |
| CN110610069A (en)* | 2019-09-09 | 2019-12-24 | 苏州浪潮智能科技有限公司 | A method and device for calling a REST interface in a web system |
| CN110633900A (en)* | 2019-08-30 | 2019-12-31 | 中国人民财产保险股份有限公司 | Virtual resource allocation method and device and electronic equipment |
| CN110730154A (en)* | 2018-07-17 | 2020-01-24 | 视联动力信息技术股份有限公司 | Service processing method and device for video network |
| CN110865881A (en)* | 2018-08-27 | 2020-03-06 | 中移(苏州)软件技术有限公司 | Method and device for resource scheduling |
| CN110912934A (en)* | 2019-12-17 | 2020-03-24 | 杭州安恒信息技术股份有限公司 | Cloud security product opening control system, method, equipment and medium |
| CN110995545A (en)* | 2019-12-19 | 2020-04-10 | 腾讯科技（深圳）有限公司 | Cloud network configuration testing method and device |
| CN111083213A (en)* | 2019-12-09 | 2020-04-28 | 苏宁云计算有限公司 | A communication method and system |
| CN111193653A (en)* | 2019-12-31 | 2020-05-22 | 腾讯科技（深圳）有限公司 | Data transmission method, device, equipment and storage medium |
| CN111416792A (en)* | 2019-01-08 | 2020-07-14 | 杭州海康威视数字技术股份有限公司 | Internal authentication-free method of embedded equipment and embedded equipment |
| CN111556047A (en)* | 2020-04-24 | 2020-08-18 | 杭州安恒信息技术股份有限公司 | Deployment method of security service in private cloud environment |
| CN111698249A (en)* | 2020-06-11 | 2020-09-22 | 深信服科技股份有限公司 | Virtual security management and control equipment deployment method and component, communication method and system |
| CN112243046A (en)* | 2019-07-19 | 2021-01-19 | 华为技术有限公司 | Communication method and network card |
| CN112311646A (en)* | 2020-09-27 | 2021-02-02 | 新华三大数据技术有限公司 | Hybrid cloud based on super-fusion system and deployment method |
| CN112350982A (en)* | 2019-09-06 | 2021-02-09 | 北京京东尚科信息技术有限公司 | Resource authentication method and device |
| CN112910995A (en)* | 2021-01-29 | 2021-06-04 | 北京千方科技股份有限公司 | Resource allocation method and device based on multi-cloud environment, electronic equipment and medium |
| CN112968823A (en)* | 2021-03-03 | 2021-06-15 | 浪潮云信息技术股份公司 | VPN service realizing method |
| CN113472799A (en)* | 2021-07-07 | 2021-10-01 | 新华三大数据技术有限公司 | Interconnection management method, device and equipment based on cloud platform |
| CN113691575A (en)* | 2020-05-18 | 2021-11-23 | 华为技术有限公司 | Communication method, device and system |
| CN114422160A (en)* | 2020-10-28 | 2022-04-29 | 中移(苏州)软件技术有限公司 | Method and device for setting virtual firewall, electronic equipment and storage medium |
| CN114510353A (en)* | 2022-02-18 | 2022-05-17 | 数字广东网络建设有限公司 | Government affair cloud adaptation system, electronic equipment and storage medium |
| CN114726773A (en)* | 2022-03-23 | 2022-07-08 | 阿里云计算有限公司 | Cloud network system, message forwarding method, chip and cloud gateway equipment |
| CN116049136A (en)* | 2022-12-21 | 2023-05-02 | 广东天耘科技有限公司 | Cloud computing platform-based MySQL cluster deployment method and system |
| CN118656038A (en)* | 2024-08-21 | 2024-09-17 | 苏州元脑智能科技有限公司 | Metadata synchronization method, device and storage system |
| WO2024208053A1 (en)* | 2023-04-06 | 2024-10-10 | 深圳竹云科技股份有限公司 | Cross-cloud data internetwork communication method, apparatus and system |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110808853B (en)* | 2019-10-24 | 2022-09-06 | 浙江大华技术股份有限公司 | Cloud computing product-oriented unified operation and maintenance method |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104902005A (en)* | 2015-04-13 | 2015-09-09 | 中国联合网络通信集团有限公司 | Method and system for resource scheduling in hybrid cloud, and private cloud |
| CN103051710B (en)* | 2012-12-20 | 2016-04-13 | 中国科学院深圳先进技术研究院 | A kind of virtual cloud platform management system |
| CN106101258A (en)* | 2016-07-08 | 2016-11-09 | 腾讯科技（深圳）有限公司 | A kind of interface interchange method of mixed cloud, Apparatus and system |
| WO2017010976A1 (en)* | 2015-07-10 | 2017-01-19 | Hewlett Packard Enterprise Development Lp | Hybrid cloud management |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9203784B2 (en)* | 2012-04-24 | 2015-12-01 | Cisco Technology, Inc. | Distributed virtual switch architecture for a hybrid cloud |
| US9846589B2 (en)* | 2015-06-04 | 2017-12-19 | Cisco Technology, Inc. | Virtual machine placement optimization with generalized organizational scenarios |
| CN105302636A (en)* | 2015-07-24 | 2016-02-03 | 北京汉柏科技有限公司 | Integration method and device for private cloud platform and Open Stack |
| CN105721306B (en)* | 2016-02-04 | 2019-03-15 | 杭州数梦工场科技有限公司 | A kind of transmission method and device of configuration information |
| CN107357660A (en)* | 2017-07-06 | 2017-11-17 | 华为技术有限公司 | The distribution method and device of a kind of virtual resource |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103051710B (en)* | 2012-12-20 | 2016-04-13 | 中国科学院深圳先进技术研究院 | A kind of virtual cloud platform management system |
| CN104902005A (en)* | 2015-04-13 | 2015-09-09 | 中国联合网络通信集团有限公司 | Method and system for resource scheduling in hybrid cloud, and private cloud |
| WO2017010976A1 (en)* | 2015-07-10 | 2017-01-19 | Hewlett Packard Enterprise Development Lp | Hybrid cloud management |
| CN106101258A (en)* | 2016-07-08 | 2016-11-09 | 腾讯科技（深圳）有限公司 | A kind of interface interchange method of mixed cloud, Apparatus and system |
| Title |
|---|
| JOEHUANG,: "OpenStack cascading solution", 《HTTPS://WIKI.OPENSTACK.ORG/WIKI/OPENSTACK_CASCADING_SOLUTION》* |
| 罗斌: "基于OpenStack的混合云负载均衡方法研究与实现", 《中国优秀硕士学位论文全文数据库信息科技辑（月刊）》* |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2019007353A1 (en)* | 2017-07-06 | 2019-01-10 | 华为技术有限公司 | Method and device for allocating virtual resources |
| CN109818998A (en)* | 2017-11-22 | 2019-05-28 | 中国电信股份有限公司 | Information synchronization method and device |
| US11438409B2 (en) | 2017-11-27 | 2022-09-06 | Endress+Hauser Process Solutions Ag | Interface apparatus for a data interchange between a field bus network and a cloud |
| CN111373702B (en)* | 2017-11-27 | 2022-04-22 | 恩德莱斯和豪瑟尔过程解决方案股份公司 | Interface device for data exchange between a fieldbus network and a cloud |
| WO2019101408A1 (en)* | 2017-11-27 | 2019-05-31 | Endress+Hauser Process Solutions Ag | Interface apparatus for a data interchange between a field bus network and a cloud |
| CN111373702A (en)* | 2017-11-27 | 2020-07-03 | 恩德莱斯和豪瑟尔过程解决方案股份公司 | Interface device for data exchange between a fieldbus network and a cloud |
| CN108512692A (en)* | 2018-02-24 | 2018-09-07 | 国家计算机网络与信息安全管理中心 | A kind of resource integrated method and device |
| CN110730154B (en)* | 2018-07-17 | 2021-08-06 | 视联动力信息技术股份有限公司 | Service processing method and device for video network |
| CN110730154A (en)* | 2018-07-17 | 2020-01-24 | 视联动力信息技术股份有限公司 | Service processing method and device for video network |
| CN110865881A (en)* | 2018-08-27 | 2020-03-06 | 中移(苏州)软件技术有限公司 | Method and device for resource scheduling |
| CN109067903A (en)* | 2018-08-29 | 2018-12-21 | 郑州云海信息技术有限公司 | A kind of cloud platform cascade system |
| CN109067903B (en)* | 2018-08-29 | 2021-06-29 | 郑州云海信息技术有限公司 | A cloud platform cascade system |
| US11811722B2 (en) | 2018-09-11 | 2023-11-07 | Huawei Cloud Computing Technologies Co., Ltd. | Method for processing cloud service in cloud system, apparatus, and device |
| WO2020052271A1 (en)* | 2018-09-11 | 2020-03-19 | 华为技术有限公司 | Method, device, and apparatus for processing cloud service in cloud system |
| CN109819061B (en)* | 2018-09-11 | 2021-09-21 | 华为技术有限公司 | Method, device and equipment for processing cloud service in cloud system |
| US11431670B2 (en) | 2018-09-11 | 2022-08-30 | Huawei Cloud Computing Technologies Co., Ltd. | Method for processing cloud service in cloud system, apparatus, and device |
| CN109819061A (en)* | 2018-09-11 | 2019-05-28 | 华为技术有限公司 | A method, apparatus and device for processing cloud services in a cloud system |
| CN111416792A (en)* | 2019-01-08 | 2020-07-14 | 杭州海康威视数字技术股份有限公司 | Internal authentication-free method of embedded equipment and embedded equipment |
| CN109873872A (en)* | 2019-03-15 | 2019-06-11 | 浪潮通用软件有限公司 | A kind of cloud electrical connector and method for supporting mixing cloud mode |
| US11431624B2 (en) | 2019-07-19 | 2022-08-30 | Huawei Technologies Co., Ltd. | Communication method and network interface card |
| CN112243046A (en)* | 2019-07-19 | 2021-01-19 | 华为技术有限公司 | Communication method and network card |
| CN110557433B (en)* | 2019-07-26 | 2021-02-26 | 华云超融合科技有限公司 | Resource management method, platform, cloud gateway, system and storage medium |
| CN110557433A (en)* | 2019-07-26 | 2019-12-10 | 华云超融合科技有限公司 | Resource management method, platform, cloud gateway, system and storage medium |
| CN110633900A (en)* | 2019-08-30 | 2019-12-31 | 中国人民财产保险股份有限公司 | Virtual resource allocation method and device and electronic equipment |
| CN112350982A (en)* | 2019-09-06 | 2021-02-09 | 北京京东尚科信息技术有限公司 | Resource authentication method and device |
| CN110610069A (en)* | 2019-09-09 | 2019-12-24 | 苏州浪潮智能科技有限公司 | A method and device for calling a REST interface in a web system |
| CN111083213A (en)* | 2019-12-09 | 2020-04-28 | 苏宁云计算有限公司 | A communication method and system |
| CN110912934A (en)* | 2019-12-17 | 2020-03-24 | 杭州安恒信息技术股份有限公司 | Cloud security product opening control system, method, equipment and medium |
| CN110995545B (en)* | 2019-12-19 | 2022-03-08 | 腾讯科技（深圳）有限公司 | Cloud network configuration testing method and device |
| CN110995545A (en)* | 2019-12-19 | 2020-04-10 | 腾讯科技（深圳）有限公司 | Cloud network configuration testing method and device |
| US12047287B2 (en) | 2019-12-31 | 2024-07-23 | Tencent Technology (Shenzhen) Company Limited | Data transmission method and apparatus, network adapter, and storage medium |
| CN111193653B (en)* | 2019-12-31 | 2021-08-06 | 腾讯科技（深圳）有限公司 | Data transmission method, device, equipment and storage medium |
| CN111193653A (en)* | 2019-12-31 | 2020-05-22 | 腾讯科技（深圳）有限公司 | Data transmission method, device, equipment and storage medium |
| CN111556047A (en)* | 2020-04-24 | 2020-08-18 | 杭州安恒信息技术股份有限公司 | Deployment method of security service in private cloud environment |
| CN113691575A (en)* | 2020-05-18 | 2021-11-23 | 华为技术有限公司 | Communication method, device and system |
| CN113691575B (en)* | 2020-05-18 | 2024-07-26 | 华为云计算技术有限公司 | Communication method, device and system |
| CN111698249A (en)* | 2020-06-11 | 2020-09-22 | 深信服科技股份有限公司 | Virtual security management and control equipment deployment method and component, communication method and system |
| CN112311646A (en)* | 2020-09-27 | 2021-02-02 | 新华三大数据技术有限公司 | Hybrid cloud based on super-fusion system and deployment method |
| CN114422160A (en)* | 2020-10-28 | 2022-04-29 | 中移(苏州)软件技术有限公司 | Method and device for setting virtual firewall, electronic equipment and storage medium |
| CN114422160B (en)* | 2020-10-28 | 2024-01-30 | 中移(苏州)软件技术有限公司 | Virtual firewall setting method and device, electronic equipment and storage medium |
| CN112910995A (en)* | 2021-01-29 | 2021-06-04 | 北京千方科技股份有限公司 | Resource allocation method and device based on multi-cloud environment, electronic equipment and medium |
| CN112968823A (en)* | 2021-03-03 | 2021-06-15 | 浪潮云信息技术股份公司 | VPN service realizing method |
| CN113472799A (en)* | 2021-07-07 | 2021-10-01 | 新华三大数据技术有限公司 | Interconnection management method, device and equipment based on cloud platform |
| CN113472799B (en)* | 2021-07-07 | 2023-04-07 | 新华三大数据技术有限公司 | Interconnection management method, device and equipment based on cloud platform |
| CN114510353A (en)* | 2022-02-18 | 2022-05-17 | 数字广东网络建设有限公司 | Government affair cloud adaptation system, electronic equipment and storage medium |
| CN114726773A (en)* | 2022-03-23 | 2022-07-08 | 阿里云计算有限公司 | Cloud network system, message forwarding method, chip and cloud gateway equipment |
| CN114726773B (en)* | 2022-03-23 | 2024-07-02 | 阿里云计算有限公司 | Cloud network system, message forwarding method, chip and cloud gateway equipment |
| CN116049136B (en)* | 2022-12-21 | 2023-07-28 | 广东天耘科技有限公司 | Cloud computing platform-based MySQL cluster deployment method and system |
| CN116049136A (en)* | 2022-12-21 | 2023-05-02 | 广东天耘科技有限公司 | Cloud computing platform-based MySQL cluster deployment method and system |
| WO2024208053A1 (en)* | 2023-04-06 | 2024-10-10 | 深圳竹云科技股份有限公司 | Cross-cloud data internetwork communication method, apparatus and system |
| CN118656038A (en)* | 2024-08-21 | 2024-09-17 | 苏州元脑智能科技有限公司 | Metadata synchronization method, device and storage system |
| Publication number | Publication date |
|---|---|
| WO2019007353A1 (en) | 2019-01-10 |
| Publication | Publication Date | Title |
|---|---|---|
| CN107357660A (en) | The distribution method and device of a kind of virtual resource | |
| US11425054B1 (en) | User-configured multi-location service deployment and scaling | |
| US10469314B2 (en) | API gateway for network policy and configuration management with public cloud | |
| CN107947961B (en) | SDN-based Kubernetes network management system and method | |
| CN103491144B (en) | A Construction Method of Wide Area Network Virtual Platform | |
| CN109194502B (en) | Management method of multi-tenant container cloud computing system | |
| CA2914802C (en) | Distributed lock management in a cloud computing environment | |
| US10740145B2 (en) | Method and system for migration of virtual machines and virtual applications between cloud-computing facilities | |
| US10148736B1 (en) | Executing parallel jobs with message passing on compute clusters | |
| US9329894B2 (en) | Method and apparatus for extending local area networks between clouds and permanently migrating virtual machines using static network addresses | |
| US9430256B2 (en) | Method and apparatus for migrating virtual machines between cloud computing facilities using multiple extended local virtual networks and static network addresses | |
| US11765244B1 (en) | Latency-based service discovery and routing for multi-location service-oriented applications | |
| RU2653292C2 (en) | Service migration across cluster boundaries | |
| US11625280B2 (en) | Cloud-native proxy gateway to cloud resources | |
| US20120290703A1 (en) | Distributed Policy Service | |
| US20130086200A1 (en) | Live Logical Partition Migration with Stateful Offload Connections Using Context Extraction and Insertion | |
| US20120297384A1 (en) | Virtual Managed Network | |
| CN106031116A (en) | A method, device and system for associating NS and VNF | |
| US10678657B1 (en) | Reversion operations for virtual computing environments | |
| CN114500450B (en) | Domain name resolution method, equipment and computer-readable storage medium | |
| JP2023038906A (en) | Computer implemented method, system, and computer program product (new container storage system in remote pods in kubernetes) | |
| WO2017066931A1 (en) | Method and device for managing certificate in network function virtualization architecture | |
| CN104317639B (en) | The method of the existing virtual machines of computer cloud platform adapter vCenter | |
| CN104281484A (en) | VM (virtual machine) migration method and device | |
| US10171292B1 (en) | Deploying a cloud infrastructure in a remote site |
| 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 | ||
| RJ01 | Rejection of invention patent application after publication | Application publication date:20171117 | |
| RJ01 | Rejection of invention patent application after publication |