CN107357660A

CN107357660A - The distribution method and device of a kind of virtual resource

Info

Publication number: CN107357660A
Application number: CN201710547491.5A
Authority: CN
Inventors: 左攀攀; 赵龙
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-07-06
Filing date: 2017-07-06
Publication date: 2017-11-17
Also published as: WO2019007353A1

Abstract

Embodiments of the invention provide a kind of distribution method and device of virtual resource, and the OpenStack API of unified standard can be provided in the mixed cloud network architecture, improve the compatibility and API request treatment effeciency of mixing cloud network.This method includes：CCS nodes obtain the virtual resource request initiated in the private clound of cascading layers, and the virtual resource asks the virtual resource for asking to be cascaded in the third party cloud of layer；And then, CCS nodes are by calling OpenStack API that virtual resource request is pass-through in the cloud gateway of above-mentioned third party cloud, to cause the cloud gateway that the virtual resource in the third party cloud is allocated into the private clound according to the privately owned API of the above-mentioned virtual resource request call third party cloud.

Description

The distribution method and device of a kind of virtual resource

Technical field

The present embodiments relate to the distribution method and device of communication technical field, more particularly to a kind of virtual resource.

Background technology

Mixed cloud is a kind of combination of public cloud and private clound, for example, some mixed cloud includes private clound 1 and third party The public cloud 2 of offer, then, its data can be stored in the higher private clound 1 of degree of safety by enterprise, meanwhile, it is also available Calculating that public cloud 2 provides, the resource such as storage are that private clound 1 provides service, are saved money and safe purpose so as to reach.

At present, private clound can pass through the injection cloud gateway (Cloud into third party cloud (for example, above-mentioned public cloud 2) Gateway mode) realizes the network architecture of mixed cloud.As shown in figure 1, private clound 11 can pass through adapter (Adapter) Cloud Gateway 13 are injected into one or more third party clouds 12, so, private clound 11 can pass through the cloud net of injection The 13 corresponding third party clouds 12 of management are closed, third party cloud 12 is provided service for it.

In the network architecture of above-mentioned mixed cloud, private clound 11 is receiving the application programming interface of tenant's triggering (Application Programming Interface, API) request in third party cloud 12 (for example, create asking for virtual machine Ask) after, need to be converted into corresponding to third party cloud 12 API request so as to realizing third party's service.And private clound 11 is external Be only tenant provide private clound 11 itself privately owned API, that is to say, that if private clound 11 receive its privately owned API can not During the request of parsing, private clound 11 will be unable to provide corresponding service for tenant, also, when private clound 11 will can not receive When API request is converted to the API request of corresponding third party cloud 12, corresponding service can not be also provided for tenant so that whole The compatibility and API request treatment effeciency for mixing cloud network reduce.

The content of the invention

Embodiments of the invention provide a kind of distribution method and device of virtual resource, can be in the mixed cloud network architecture The OpenStack API of unified standard are provided, improve the compatibility and API request treatment effeciency of mixing cloud network.

To reach above-mentioned purpose, embodiments of the invention adopt the following technical scheme that：

In a first aspect, embodiments of the invention provide a kind of distribution method of virtual resource, including：CCS nodes obtain level Join the virtual resource request initiated in the private clound of layer, the virtual resource is asked for asking to be cascaded in the third party cloud of layer Virtual resource；And then CCS nodes are by calling OpenStack API that virtual resource request is pass-through into above-mentioned third party cloud Cloud gateway in, to cause the cloud gateway according to the privately owned API of the above-mentioned virtual resource request call third party cloud by the 3rd Fang Yunzhong virtual resource is allocated to the private clound.

That is, in this application, it can be cascaded third party cloud as one in above-mentioned private clound OpenStack, which is deployed in, to be cascaded in layer, forms the network architecture of mixed cloud.Now, third party cloud can pass through unified standard OpenStack api interface slitless connection cascading layers private clound, a single OpenStack offer cloud can also be provided Service, the OpenStack API of unified standard are externally internally provided which in the network architecture of mixed cloud, so as to shield not With the API differences between cloud, the compatibility and API request treatment effeciency for mixing cloud network are improved.Meanwhile identical OpenStack API systems, it is ensured that tenant does not have notable difference when selecting the different clouds in mixed cloud to be operated, so as to realize across cloud Smooth interoperability.

In a kind of possible design method, before CCS nodes obtain the virtual resource request initiated in private clound, also Including：Cloud gateway of the CCS nodes into the third party cloud is sent between OpenStack API and the privately owned API of third party cloud Parameter mapping relations during Transfer Parameters.So, can be according to the parameter after cloud gateway receives above-mentioned virtual resource request Mapping relations call the privately owned API of third party cloud that the virtual resource in the third party cloud is allocated into the private clound.

In a kind of possible design method, before CCS nodes obtain the virtual resource request initiated in private clound, also Including：CCS nodes establish vpn tunneling between the third party cloud and the private clound；CCS nodes are created in the third party cloud and held Carry the virtual machine of cloud gateway；CCS nodes dispose the mixing cloud service of cloud gateway offer in the virtual machine, and the cloud gateway is carried The mixing cloud service of confession is registered in the private clound.So, the third party cloud AWS clouds where the cloud gateway of deployment can be used as one The individual OpenStack being cascaded is deployed in being cascaded in layer of private clound, forms the network architecture of mixed cloud.In the mixed cloud In the network architecture, the either private clound of cascading layers is still cascaded the third party cloud of layer, can provide unified standard OpenStack api interfaces, so as to shield the API differences between different clouds, the compatibility and API that improve mixing cloud network please Seek treatment effeciency.

In a kind of possible design method, in CCS nodes by calling OpenStack API to ask the virtual resource It is pass-through in the cloud gateway of the third party cloud, to cause API of the cloud gateway according to the virtual resource request call third party cloud After virtual resource in the third party cloud is allocated into the private clound, in addition to：CCS nodes are updated from this in IP resource pools At least one floating IP address obtained in third party cloud；CCS nodes are synchronous by the floating IP address updated in the IP resource pools Into the cloud gateway of the private clound and the third party cloud.

In a kind of possible design method, CCS nodes obtain the virtual resource request initiated in private clound, including：CCS The virtual resource that node is initiated by calling OpenStack API to obtain in private clound is asked.

Second aspect, embodiments of the invention provide a kind of distribution method of virtual resource, including：Cloud gateway passes through OpenStack API obtain virtual resource request from private clound, and the virtual resource is asked for asking the void in third party cloud Intend resource, the private clound is located at cascading layers, and the third party cloud, which is located at, is cascaded layer；Cloud gateway is converted to virtual resource request Support the privately owned API of third party cloud API request；Cloud gateway is according to the API request by the virtual resource in the third party cloud It is allocated to the private clound.Because OpenStack can be provided, implementation is simple, can extend on a large scale, enrich, the API that standard is unified connects Mouthful, and the private clound and third party cloud in the embodiment of the present application can be interacted by OpenStack API, then, tenant It is consistent with mode of operation in third party cloud and the Consumer's Experience in private clound, so as to shield third party cloud because of api interface not The difference between cloud with caused by.

In a kind of possible design method, virtual resource request is asked for virtual machine creating, and the virtual machine creating please Seek middle the first configuration parameter for carrying virtual machine to be created；Wherein, cloud gateway by virtual resource request be converted to support this The privately owned API of tripartite's cloud API request, including：Cloud gateway is according to preset in the privately owned of OpenStack API and third party cloud Parameter mapping relations between API during Transfer Parameters, search the second configuration parameter corresponding with first configuration parameter；Cloud gateway The first configuration parameter during the virtual machine creating is asked is revised as second configuration parameter, obtains supporting the private of the third party cloud There is API API request.

In a kind of possible design method, virtual resource request is virtual volume request to create, and the virtual volume creates please Seek middle carrying first volume type parameter；Wherein, virtual resource request is converted to and supports the privately owned of the third party cloud by cloud gateway API API request, including：Cloud gateway transmits according to preset between OpenStack API and the privately owned API of third party cloud Parameter mapping relations during parameter, search volume Two type parameter corresponding with the first volume type parameter；Cloud gateway is by the void The first volume type parameter intended in volume request to create is revised as the volume Two type parameter, obtains supporting the privately owned of the third party cloud API API request.

In a kind of possible design method, virtual resource request is converted in cloud gateway and supports the third party cloud Before privately owned API API request, in addition to：Cloud gateway receive that CCS nodes in the private clound send in OpenStack API Parameter mapping relations between the privately owned API of third party cloud during Transfer Parameters.

The third aspect, embodiments of the invention provide a kind of CCS nodes, including：Acquiring unit, it is used for：Obtain private clound The virtual resource request of middle initiation, the virtual resource are asked for asking the virtual resource in third party cloud, and the private clound is located at Cascading layers, the third party cloud, which is located at, is cascaded layer；Transmitting element, it is used for：By calling OpenStack API by the virtual resource Request is pass-through in the cloud gateway of the third party cloud, to cause cloud gateway according to the virtual resource request call third party cloud Virtual resource in the third party cloud is allocated to the private clound by API.

In a kind of possible design method, the transmitting element, it is additionally operable to：Cloud gateway into the third party cloud is sent in Parameter mapping relations between OpenStack API and the privately owned API of third party cloud during Transfer Parameters.

In a kind of possible design method, CCS nodes also include：Creating unit, it is used for：In the third party cloud and the private Have and establish vpn tunneling between cloud；The virtual machine of carrying cloud gateway is created in the third party cloud；Cloud net is disposed in the virtual machine The mixing cloud service provided is closed, and the mixing cloud service that the cloud gateway is provided is registered in the private clound.

In a kind of possible design method, CCS nodes also include：Updating block, it is used for：In IP resource pools renewal from At least one floating IP address obtained in the third party cloud；The floating IP address updated in the IP resource pools is synchronized to the private In the cloud gateway for having cloud and the third party cloud.

In a kind of possible design method, the acquiring unit, it is specifically used for：By calling OpenStack API to obtain The virtual resource request initiated in private clound.

Fourth aspect, embodiments of the invention provide a kind of cloud gateway, including：Acquiring unit, it is used for：Pass through OpenStack API obtain virtual resource request from private clound, and the virtual resource is asked for asking the void in third party cloud Intend resource, the private clound is located at cascading layers, and the third party cloud, which is located at, is cascaded layer；Converting unit, it is used for：Please by the virtual resource Seek the API request for being converted to the privately owned API for supporting the third party cloud；Execution unit, it is used for：According to the API request by the 3rd Fang Yunzhong virtual resource is allocated to the private clound.

In a kind of possible design method, virtual resource request is asked for virtual machine creating, and the virtual machine creating please Seek middle the first configuration parameter for carrying virtual machine to be created；The converting unit, is specifically used for：According to preset in OpenStack Parameter mapping relations between API and the privately owned API of third party cloud during Transfer Parameters, search corresponding with first configuration parameter Second configuration parameter；The first configuration parameter during the virtual machine creating is asked is revised as second configuration parameter, is supported The privately owned API of third party cloud API request.

In a kind of possible design method, virtual resource request is virtual volume request to create, and the virtual volume creates please Seek middle carrying first volume type parameter；The converting unit, is specifically used for：According to preset in OpenStack API and third party Parameter mapping relations between the privately owned API of cloud during Transfer Parameters, search volume Two class corresponding with the first volume type parameter Shape parameter；First volume type parameter in the virtual volume request to create is revised as the volume Two type parameter, obtains supporting to be somebody's turn to do The privately owned API of third party cloud API request.

In a kind of possible design method, the acquiring unit, it is additionally operable to：Receive what CCS nodes in the private clound were sent Parameter mapping relations between OpenStack API and the privately owned API of third party cloud during Transfer Parameters.

5th aspect, embodiments of the invention provide a kind of OpenStack cascade systems, and the system includes being arranged on cascade The private clound of layer, and the third party cloud for being cascaded layer is arranged on, the CCS nodes in the private clound are by using OpenStack API and the cloud gateway communication in the third party cloud.

6th aspect, the embodiment of the present invention provide a kind of computer-readable recording medium, the computer-readable recording medium In be stored with instruction, when the instruction is being run on any of the above-described CCS nodes so that it is empty that CCS nodes perform any of the above-described Intend the distribution method of resource.

7th aspect, the embodiment of the present invention provide a kind of computer-readable recording medium, the computer-readable recording medium In be stored with instruction, when the instruction is being run on any of the above-described cloud gateway so that cloud gateway perform any of the above-described it is virtual The distribution method of resource.

Eighth aspect, the embodiment of the present invention provides a kind of computer program product for including instruction, when it is any of the above-described When being run on item CCS nodes so that CCS nodes perform the distribution method of any of the above-described virtual resource.

9th aspect, the embodiment of the present invention provides a kind of computer program product for including instruction, when it is any of the above-described When being run on item cloud gateway so that cloud gateway performs the distribution method of any of the above-described virtual resource.

In embodiments of the invention, above-mentioned UE and radio reception device name do not form restriction in itself to equipment, in reality During border is realized, these equipment can occur with other titles.As long as the function of each equipment is similar with embodiments of the invention, i.e., Belong within the scope of the claims in the present invention and its equivalent technologies.

In addition, second aspect technique effect caused by any design method into the 9th aspect can be found in above-mentioned first Technique effect caused by different designs method in aspect, here is omitted.

Brief description of the drawings

Fig. 1 is the configuration diagram for mixing cloud network in the prior art；

Fig. 2 is a kind of configuration diagram one for mixing cloud network provided in an embodiment of the present invention；

Fig. 3 is a kind of configuration diagram two for mixing cloud network provided in an embodiment of the present invention；

Fig. 4 is a kind of interaction schematic diagram one of the distribution method of virtual resource provided in an embodiment of the present invention；

Fig. 5 is a kind of interaction schematic diagram two of the distribution method of virtual resource provided in an embodiment of the present invention；

Fig. 6 is a kind of configuration diagram three for mixing cloud network provided in an embodiment of the present invention；

Fig. 7 is a kind of interaction schematic diagram three of the distribution method of virtual resource provided in an embodiment of the present invention；

Fig. 8 is a kind of configuration diagram four for mixing cloud network provided in an embodiment of the present invention；

Fig. 9 is a kind of structural representation of CCS nodes provided in an embodiment of the present invention；

Figure 10 is a kind of structural representation of cloud gateway provided in an embodiment of the present invention；

Figure 11 is a kind of structural representation of physical host provided in an embodiment of the present invention.

Embodiment

Hereinafter, term " first ", " second " are only used for describing purpose, and it is not intended that instruction or hint relative importance Or the implicit quantity for indicating indicated technical characteristic.Thus, define " first ", the feature of " second " can be expressed or Implicitly include one or more this feature.In the description of the embodiment of the present invention, unless otherwise indicated, " multiples' " contains Justice is two or more.

For fairly set out embodiments of the invention offer virtual resource distribution method, explain first on OpenStack related content.

OpenStack is the cloud computing increased income a management platform project, is got up by several main service component assemblies Complete specific works.It is exemplary, specifically may include in an OpenStack system Nova, Swift, Keystone, The serviced components such as Neutron and Cinder.

Wherein, Nova serviced components, for the whole Life Cycle for unique user or using management and group virtual machine instance Phase, corresponding Virtual Service can be provided according to user's request.For example, be responsible for virtual machine creating, start, shutdown, hang-up, pause, The information specification such as operation, configuration CPU, internal memory such as adjust, migrate, restarting, destroying.

Swift serviced components, it is a set of be used in extensive expansible system by built-in redundancy and high fault tolerant mechanism The system for realizing object storage, it is allowed to stored or retrieval file.

Keystone serviced components, other services it can provide authentication, service regulation and service order for OpenStack The function of board.

Neutron serviced components, it is possible to provide the network virtualization technology of cloud computing, other services provide for OpenStack Network connection service.Interface, configuration DHCP (Dynamic Host can also be provided the user Configuration Protocol, DHCP), domain name system (Domain Name System, DNS), load balancing, L3 clothes Business, network support GRE, VLAN (Virtual Local Area Network, VLAN) etc..

Cinder serviced components, available for stable data block storage service is provided, its plug-in unit driving framework is advantageous to The establishment and management of block device, such as create and roll up, delete volume, carry and unloading volume on example.

Certainly, can also be serviced in OpenStack systems including Horizon, Ceilometer, Heat and Trove etc. Component, the embodiment of the present invention are not intended to be limited in any to this.

Specifically, OpenStack each serviced component is provided with is based on OpenStack api interfaces accordingly, such as Nova-API, Swift-API etc..Using these API user can be allowed to carry out a series of operation in OpenStack clouds, e.g., Start service host, create mirror image, metadata is set to main frame and mirror image, creates container and object etc..OpenStack supports several All types of cloud environments, therefore, OpenStack can provide implement it is simple, can on a large scale extend, enrich, standard is unified Cloud computing management platform.

Embodiments of the invention provide a kind of distribution method of virtual resource, can be applicable to OpenStack as shown in Figure 2 In cascade system, the network architecture of mixed cloud is realized.

It is exemplary, as shown in Fig. 2 private clound 201 can based on OpenStack cascade systems framework carry out portion Administration, wherein, the private clound 201 includes cascading layers 21 and is cascaded layer 22, and cascade (Cascading) is provided with cascading layers 21 OpenStack, is cascaded in layer 22 to be provided with and is cascaded (Cascaded) OpenStack.Cascading layers 21 are as unified entrance The dependent instruction (for example, API request) that tenant or keeper issue can be received, and then, cascading layers 21 send out the instruction received Corresponding Cascaded OpenStack are given in cascading layers 22 to perform the instruction.Wherein, cascading layers 21 and it is cascaded layer 22 It is provided which unified OpenStack API.

In this application, still as shown in Fig. 2 can using third party cloud 202 as one in above-mentioned private clound 201 by level Connection OpenStack, which is deployed in, to be cascaded in layer 22, forms the network architecture of mixed cloud.

So, for tenant, the unified entrance of above-mentioned mixed cloud is the OpenStack api interfaces of cascading layers 21.That , when tenant initiates API request, the cascade OpenStack of cascading layers 21 can be by unified OpenStackAPI interfaces, will The API request is transparent in the third party cloud 202 being cascaded, by inside third party cloud 202 by based on OpenStack API's API request is converted to the API request based on third party cloud 202, and the final API for calling third party cloud performs the API that tenant initiates Request.

That is, third party cloud 202 is cascaded OpenStack as one of private clound 201, unification can be both passed through The private clound 201 of the OpenStack api interface slitless connections cascading layers 21 of standard, one can also be used as individually OpenStack provides cloud service, and the OpenStack of unified standard is externally internally provided which in the network architecture of mixed cloud API, so as to shield the API differences between different clouds, improve the compatibility and API request treatment effeciency of mixing cloud network.

Meanwhile identical OpenStack API systems, it is ensured that tenant selects the different clouds in mixed cloud to be operated When there is no notable difference, so as to realize the smooth interoperability across cloud.

It should be noted that the third party cloud 202 being related in the embodiment of the present application can be public cloud, for example, Spain Telecommunication opening cloud (Telefonica Open Cloud, TOC) or private clound, for example, Huawei FS (FusionSphere) cloud operating system.Also, third party cloud 202 can be the isomorphism cloud of private clound 201 or privately owned The isomery cloud of cloud 201, the embodiment of the present invention are not intended to be limited in any to this.

Further, can be with portion in private clound 201 as shown in figure 3, the network architecture based on the mixed cloud shown in Fig. 2 Affix one's name to cloud configuration service (Cloud Configuration Service, CCS) node, virtual proprietary network (Virtual Private Cloud, VPC) node, elastic calculation service (Elastic Compute Service, ECS) node and cloud connect Connect the service modules such as device (Cloud Connector).

Wherein, CCS modules can call the interface of third party cloud 202, and cloud gateway (Cloud is created in third party cloud 202 Gateway) 203, the cloud gateway 203 can be deployed in third party cloud 202 in the form of virtual machine.And then cloud connector can Further on cloud gateway 203 install cloud API adapters (Cloud API Adapter, CAA), database (Data Base, The service such as DB), and by these service registrys into private clound 201 so that private clound 201 initiates the corresponding tenant got It can be forwarded to after API request in the third party cloud 202 being cascaded, that is, cause what third party cloud 202 was cascaded as one What OpenStack was deployed in private clound 201 is cascaded layer 22.

And in the third party cloud 202 being cascaded, tenant in cloud gateway 203 can be managed by the cloud gateway 203 created and is created The each tenant's virtual machine (tenant VM) built.Third party cloud 202 can externally provide the OpenStackAPI of unified standard, right It is interior to support the API of itself of third party cloud 202, with AWS (Amazon Web Service, the publicly-owned cloud computing that Amazon provides Service) cloud as third party cloud 202 exemplified by, AWS clouds can pass through OpenStack API receive tenant or cascade OpenStack The API request of transmission, and the API request is converted to the API request for supporting AWS clouds, and then please using the API of support AWS clouds Ask and realize related service in third party cloud 202.

Hereinafter, illustrated using AWS clouds as above-mentioned third party cloud 202, elaborate a kind of deployment that the present invention implements to provide The method of cloud gateway, as shown in figure 4, this method includes：

401st, keeper registered user on AWS clouds.

Before the related service provided using AWS clouds (i.e. third party cloud), keeper, which needs to register on AWS clouds, to be used Family.The user of registration can have specific authority and resource quota, can create cloud gateway (CloudGateway) and Tenant's virtual machine.

Exemplary, the specific authority can include Amazon EC2Full Access, and (Amazon EC2 is serviced complete Access mandate), Amazon S3Full Access (the full access mandate of Amazon S3 services), AWS Import Export Full Access (the full access mandates of Amazon input and output), IAM Read Only Access (award by IAM read-only accesses Power), Amazon RDS Read Only Access (mandate of Amazon RDS read-only accesses), AWS Support Access (branch Hold AWS access mandates), the IAM Self Manage Service Specific Credentials (spies of IAM Self management services It is fixed to authorize) etc., the embodiment of the present invention is not intended to be limited in any to this.

402nd, keeper creates VPC and subnet on AWS clouds.

After an account used on AWS clouds is obtained, keeper can use the account at AWS clouds (third party cloud) In some region (region), for example, creating VPC in the region such as the Soul of AWS clouds, Tokyo so that tenant is subsequently in AWS clouds The service of upper deployment can be isolated from the outside and come.

Further, if also needing to further network division inside the VPC created, tenant can also be in establishment One or more subnets are created in VPC, for example, management subnet om_net and tenant's subnet ext_net.

403rd, keeper configures VPN (Virtual Private Network, VPN) gateway on AWS clouds.

404th, keeper configures vpn gateway on the cascade OpenStack where private clound, to establish private clound and AWS Vpn tunneling between cloud.

In step 403-404, for the cloud realized the cascade OpenStack in private clound with subsequently created in AWS clouds Communication function between gateway, vpn gateway can be configured in AWS clouds and cascade OpenStack, so, pass through network tunnel Road agreement, the vpn tunneling that can be established between private clound and AWS clouds, subsequently, it can be established between private clound and AWS clouds with passing through Vpn tunneling communicated.

So far, by performing step 401-404, can complete to dispose the preparation of cloud gateway in AWS clouds, subsequently, Following step 405-409 can be continued executing with cloud gateway is disposed in AWS clouds.

405th, asked in response to the cloud gateway deployment that keeper triggers on UI (User Interface, user interface), CCS nodes create the secure group of cloud gateway in AWS clouds.

Specifically, keeper can select to create the option of cloud gateway for AWS clouds on the UI interfaces of private clound, then, When detection obtains keeper when triggering creates the option of cloud gateway on UI interfaces, private clound can generate the request of cloud gateway deployment, And cloud gateway deployment request is sent to the CCS nodes of private clound.

CCS nodes create cloud after cloud gateway deployment request is received in the VPC that can create in step 402 first The secure group of gateway, and for subsequently create carrying cloud gateway multiple virtual machines between, cloud gateway with cascade OpenStack it Between and cloud gateway and tenant's virtual machine between secure group rule is set, fire wall is formed, to improve the cloud gateway subsequently established Security.

406th, CCS nodes create the Floating IP address of cloud gateway in AWS clouds.

In a step 406, because the cloud gateway subsequently created and the third party cloud interface in AWS clouds are led to by Floating IP address Letter, therefore, CCS nodes can also create the Floating IP address of cloud gateway in AWS clouds, so, when the cloud gateway in AWS has created Cheng Hou, it can be bound with the Floating IP address of above-mentioned establishment, so as to realize and the third party cloud interface communication in AWS clouds.

407th, CCS nodes create the virtual machine of carrying cloud gateway in AWS clouds.

In step 407, in the management subnet om_net for the VPC that CCS nodes can create in step 402, establishment is held Carry the virtual machine of cloud gateway, i.e., the cloud gateway disposed in the form of virtual machine in AWS nodes, and it is floating by what is created in step 406 Dynamic IP is bound with above-mentioned virtual machine.

Wherein, the virtual machine of above-mentioned carrying cloud gateway can be one or more, and the embodiment of the present invention is not made any to this Limitation.

408th, cloud connector disposes mixing cloud service on the virtual machine of establishment.

409th, cloud connector registers the mixing cloud service of cloud gateway offer in OpenStack is cascaded, to cause AWS clouds to make Achieved a butt joint to be cascaded OpenStack and cascade OpenStack.

In a step 408, after the virtual machine of above-mentioned carrying cloud gateway successfully starts up, the cloud connector in private clound can enter One step disposes the mixing cloud service needed for the mixed cloud network architecture realized shown in Fig. 2 or Fig. 3 on above-mentioned virtual machine, for example, Cloud API adapters (Cloud API Adapter, CAA), database service, Message Agent (rabbitmq) service etc., the present invention Embodiment is not intended to be limited in any to this.

Wherein, the CAA disposed in cloud gateway can provide the OpenStack api interfaces of standard in north orientation, can be carried in south orientation For the api interface (i.e. the privately owned api interface of third party cloud) of AWS clouds.That is, CAA externally can be by calling OpenStack Api interface receives the API request that private clound is sent, and can will pass through OpenStack api interfaces in AWS clouds (third party cloud) The API request received is converted to the API request for the privately owned API for supporting AWS clouds.So, as being cascaded OpenStack's AWS clouds can also use the OpenStackAPI interfaces of unified standard to provide cloud service, so as to shield the API between different clouds Difference, improve the compatibility and API request treatment effeciency of mixing cloud network.

Further, in step 409, after cloud connector disposes mixing cloud service on above-mentioned virtual machine, it is also necessary to Above-mentioned mixing cloud service is registered in cascade OpenStack, so, the cloud that cascade OpenStack can ask tenant to AWS clouds Service is correctly pass-through to the cloud gateway of AWS clouds, related cloud service is provided by cloud gateway management AWS clouds for tenant, so as to realize AWS clouds belonging to cloud gateway are completed to dock as OpenStack is cascaded with cascade OpenStack.

Specifically, cloud connector can register the service endpoint of cloud gateway in OpenStack is cascaded, for example, will Nova serviced components, cinder serviced components, neutron serviced components, CAA in the AWS clouds being cascaded etc. service Endpoint, it is registered in cascade OpenStack keystone services, so that other services are visited by cascading OpenStack Ask the AWS clouds being cascaded.

Further, cloud connector can also dispose proxy services in OpenStack is cascaded, for example, deployment Compute-proxy, network-proxy, blockstorage-proxy, ceilometer-proxy etc. are serviced, each Proxy services are responsible for docking with the cloud gateway in AWS so that cascade OpenStack can forward request of the tenant to AWS clouds To cloud gateway.

In addition, cloud connector can also configure DNS (Domain Name System, domain name system in OpenStack is cascaded System), to ensure that private clound can correctly parse the above-mentioned service endpoint being registered in cascade OpenStack.

So far, by step 401-409, the preparation before deployment cloud gateway is completed, creates the void of carrying cloud gateway Plan machine, and configuration cloud gateway these three processes so that the third party cloud AWS clouds where cloud gateway can be cascaded as one OpenStack be deployed in being cascaded in layer of private clound, form the network architecture of mixed cloud.In the network architecture of the mixed cloud In, the either private clound of cascading layers is still cascaded the AWS clouds of layer, and the OpenStack API that can provide unified standard connect Mouthful, so as to shield the API differences between different clouds, improve the compatibility and API request treatment effeciency of mixing cloud network.

In some embodiments of the present application, after deploying cloud gateway in third party cloud (for example, above-mentioned AWS clouds), rent Family can be to initiate virtual resource request to the AWS clouds for being cascaded layer in the cascade OpenStack of private clound, with use by level The AWS clouds of connection layer are itself to provide related cloud service.

For example, tenant can initiate the request to create of virtual machine on the UI of private clound, then, when virtual in private clound During inadequate resource, the cascade OpenStack in private clound can initiate virtual machine creating request to the AWS clouds for being cascaded layer, from And virtual machine is created in AWS clouds and is used for tenant.

On the other hand, the embodiment of the present invention provides a kind of distribution method of virtual resource, as shown in figure 5, including：

501st, CAA of the CCS nodes into AWS clouds is transmitted between being registered in the privately owned API of OpenStack API and AWS clouds Parameter mapping relations during parameter.

What the privately owned API that the various services provided inside AWS clouds are all based on AWS was realized, and AWS clouds are external, for example, right The OpenStack of cascading layers, exposed interface are the OpenStack API of unified standard.Therefore, it is necessary in advance will Parameter mapping relations between OpenStack API and AWS privately owned API during Transfer Parameters are registered in AWS clouds.

For example, when calling OpenStack API to create a virtual machine, carried in the virtual machine creating request of generation Flavor ID (i.e. the first configuration parameter) are m1.small, and when the flavor ID map to the privately owned API of AWS clouds, should Flavor ID may be changed into t2.small (i.e. the second configuration parameter)；Accordingly, OpenStackAPI is being called to create one During virtual volume, the volume type (i.e. first volume type parameter) carried in the virtual volume request to create of generation are SSD (Solid State Drives, solid state hard disc), and when the volume type map to the privately owned API of AWS clouds, the volume type can Gp2 (i.e. volume Two type parameter) can be changed into.

Therefore, same parameters can be pre-established in the CCS nodes of private clound in OpenStack API and AWS clouds Parameter mapping relations between privately owned API, for example, the parameter mapping relations between above-mentioned m1.small and t2.small, and Parameter mapping relations between above-mentioned SSD and gp2, and the parameter mapping relations are stored in the database of CCS nodes, this When, the mode bit of the parameter mapping relations in database can be arranged to：Unsynced (not synchronous).

And then as shown in fig. 6, CCS nodes can enable the CAA Map Interfaces in thread asynchronous call AWS clouds, will be above-mentioned Parameter mapping relations are synchronized in the CAA of cloud gateway, now, can be set the mode bit of the parameter mapping relations in database For：Syncing (synchronous)；So, if synchronous success, CCS nodes can be by the parameter mapping relations in database Mode bit is arranged to：Synced (synchronous).

In addition, register the parameter between OpenStack API and AWS privately owned API in CAA of the CCS nodes into AWS clouds During mapping relations, in the event of dns resolution failure, network is obstructed or CAA service exceptions when, may result in synchronization Failure.Now, CCS nodes can periodically read the mode bit of the above-mentioned parameter mapping relations recorded in its database, work as state When position is Syncing, CCS can call the CAA in AWS clouds to inquire about Map Interface, inquire about in CAA and closed with the presence or absence of parameter mapping System, if it is present CCS nodes can further update synchronous parameter mapping relations in CAA；Otherwise, CCS nodes can Create the parameter mapping relations in the CAA of cloud gateway, and by the mode bit of the parameter mapping relations in the database of CCS nodes It is arranged to：synced.

502nd, the virtual resource that tenant initiates on cascade OpenStack to AWS clouds is obtained to ask.

Wherein, above-mentioned virtual resource request is specifically as follows the needs such as virtual machine creating request or virtual volume request to create AWS clouds provide the request of cloud service, and the embodiment of the present invention is not intended to be limited in any to this.

Exemplary, in step 502, tenant can initiate virtual machine creating request on the UI of private clound to AWS clouds, The first configuration parameter (flavor ID) of virtual machine to be created is carried in virtual machine creating request, for example, this first is matched somebody with somebody It is m1.small to put parameter.

Or tenant can initiate virtual volume request to create, the virtual volume request to create on the UI of private clound to AWS clouds In carry the first volume type parameter (volume type) of virtual volume to be created, for example, the first volume type parameter is SSD。

Because the northbound interface for cascading OpenStack is OpenStack api interfaces, therefore, cascade OpenStack can lead to Cross and call the OpenStack API of its north orientation to obtain above-mentioned virtual resource request.

503rd, cascade cloud gateways of the OpenStack into AWS clouds and send above-mentioned virtual resource request.

Because the southbound interface for cascading OpenStack is also OpenStack api interfaces, and the cloud gateway in AWS clouds Northbound interface is also OpenStack api interfaces, therefore, still as shown in fig. 6, cascade OpenStack can pass through calling OpenStack api interfaces, the above-mentioned virtual resource request of cloud gateway transparent transmission into AWS clouds.

504th, after cloud gateway receives above-mentioned virtual resource request, the request of above-mentioned virtual resource is converted to and supports AWS clouds Privately owned API API request.

Flavor ID in being asked using above-mentioned virtual resource is m1.small, and volume type illustrate for SSD, in step In 504, after cloud gateway receives the request of above-mentioned virtual resource, still as shown in fig. 6, cloud gateway can be according to recording in its CAA Parameter mapping relations between OpenStack API and AWS privately owned API during Transfer Parameters, the virtual resource that will be received Flavor ID in request are revised as t2.small, and the volumetype intended in resource request is revised as into gp2, are propped up Hold the privately owned API of AWS clouds API request.

505th, cloud gateway calls the privately owned API of AWS clouds by AWS clouds according to the API request for the privately owned API for supporting AWS clouds Virtual resource be allocated to private clound.

So, in step 505, still as shown in fig. 6, cloud gateway can be according to the privately owned API's of above-mentioned support AWS clouds API request, continue to use virtual machine and the specified volume of tenant that prior art creates the specified flavor ID of tenant in AWS clouds Type virtual volume, i.e., the virtual resource in AWS clouds is allocated to private clound and used, realize different clouds in the mixed cloud network architecture Between scheduling of resource.

As can be seen that reflected by the parameter between the API of registration OpenStack API and AWS clouds in the CAA of cloud gateway Penetrate relation so that third party cloud can be interacted by OpenStack API with the private clound of cascading layers, realize virtual resource in difference United Dispatching process between cloud.

Because OpenStack can be provided, implementation is simple, can extend on a large scale, enrich, the api interface that standard is unified, and this Private clound and third party cloud in application embodiment can be interacted by OpenStack API, then, tenant is in third party Cloud and the Consumer's Experience in private clound are consistent with mode of operation, cause so as to shield third party cloud because api interface is different Cloud between difference.

In other embodiments of the application, when tenant creates virtual machine on third party cloud (for example, above-mentioned AWS clouds) After (i.e. tenant's virtual machine, tenant VM), tenant can also be in third party cloud in the cascade OpenStack of private clound Tenant VM bind Floating IP address, and tenant's virtual machine is accessed thereby using the Floating IP address of the binding.

On the other hand, the embodiment of the present invention provides a kind of distribution method of Floating IP address, as shown in fig. 7, comprises：

701st, the Floating IP address in the CCS node application AWS clouds in private clound, and the Floating IP address applied is recorded in IP moneys In the pond of source.

Due to available Floating IP address in AWS clouds can not be known in cascade OpenStack, then, when tenant passes through cascade The unified OpenStack API application Floating IP address provided of OpenStack, during accessing the tenant's virtual machine in AWS clouds, cascade OpenStack possibly can not be the tenant's virtual machine application in AWS clouds to available Floating IP address.

On the other hand, in embodiments of the present invention, the CCS nodes in private clound can apply for Floating IP address from AWS clouds in advance, and The Floating IP address applied is recorded in IP resource pools, the Floating IP address in the real-time servicing IP resource pools, ensures tenant from cascade The Floating IP address applied in OpenStack can use.

Specifically, as shown in figure 8, CCS nodes can call the api interface of AWS clouds, apply for available Floating IP address in AWS clouds, For example, the Floating IP address that CCS node applications are arrived is 52.127.156.112 and 13.50.128.223.And then CCS nodes will be applied To Floating IP address store in the IP resource pools to its database, now, the state for the Floating IP address applied in the IP resource pools For Unsynced (not synchronous).

702nd, the Floating IP address in above-mentioned IP resource pools is synchronized to cascade OpenStack by the CCS nodes in private clound.

Specifically, still as shown in figure 8, CCS nodes can be sent to the neutron serviced components in cascade OpenStack Neutron API requests, the Floating IP address increased newly in above-mentioned IP resource pools is registered in external network by neutron serviced components： 52.127.156.112 and 13.50.128.223.

In addition, when first time is to cascade OpenStack synchronization Floating IP address, OpenStack neutron service groups are cascaded After part receives the neutron API requests of CCS nodes transmission, entitled hybrid_cloud_ { cloud_ can be first created Type } _ the external network of { cloud_region }.

And then because each Floating IP address has CIDR (the Classless Inter of its subordinate DomainRouting, CIDR), then, CCS nodes can be according to the CIDR for the Floating IP address applied, in said external network Create subnet, and the Floating IP address that increase has just been applied in the IP resource pools (for example, allocation_pools) of the subnet so that Floating IP address in IP resource pools is synchronized to cascade OpenStack.

Optionally, CCS nodes can also register tenant network in internal layer EIP networks, for example, the tenant network registered as 172.100.16.0/24, the IP address can use in cascade OpenStack Intranet.

703rd, the Floating IP address in above-mentioned IP resource pools is synchronized to the cloud gateway in AWS clouds by the CCS nodes in private clound.

In step 703, the CCS nodes in private clound can also be to the neutron serviced components in AWS cloud medium cloud gateways Neutron API requests are sent, by neutron serviced components in external network (for example, entitled external_relay_ Network external network) in the Floating IP address that increases newly in the above-mentioned IP resource pools of registration：52.127.156.112 and 13.50.128.223。

Similar, when first time is to AWS cloud synchronization Floating IP address, the neutron serviced components in cloud gateway receive CCS After the neutron API requests that node is sent, entitled above-mentioned external_relay_network extranets can be first created Network, and then the Floating IP address in above-mentioned IP resource pools is registered in the external network.

In addition, if CCS nodes have registered tenant network in internal layer EIP networks in a step 702, then in cloud gateway The tenant network can also be synchronized to entitled external_relay_network outside in the lump by neutron serviced components In network.

704th, cascade OpenStack and receive the Floating IP address request that tenant initiates, the Floating IP address asks to be used to ask Floating IP address Access the tenant's virtual machine in AWS clouds.

705th, cascade OpenStack and distribute a target float IP from above-mentioned IP resource pools for the tenant's virtual machine, with So that tenant accesses the tenant's virtual machine by target float IP.

In step 704-705, the Floating IP address of some tenant's virtual machine please in tenant initiates to AWS clouds in cascading layers When asking, cascade OpenStack can be that the tenant's virtual machine in AWS clouds distributes a mesh from above-mentioned synchronous IP resource pools Floating IP address is marked, and target float IP is tied in the tenant's virtual machine in AWS so that tenant can pass through the target float IP is able to access that the tenant's virtual machine.

Further, after the tenant's virtual machine target float IP in above-mentioned IP resource pools being tied in AWS, the mesh Mark Floating IP address is occupied, can be by above-mentioned IP resource pools subsequently when cascade OpenStack receives new Floating IP address request In unappropriated Floating IP address distribute to tenant.

In addition, discharge some Floating IP address (such as above-mentioned target float IP) when keeper issues into cascade OpenStack Request when, CCS nodes can delete target float IP in above-mentioned IP resource pools, and call cascade OpenStack Neutron interfaces, target float IP is deleted in the external network and EIP internal networks of cascading layers；Also, CCS nodes are also The neutron interfaces being cascaded in stratus gateway can be called, target float IP is deleted in the external network of cloud gateway, from And ensure the Floating IP address that user applies from the IP resource pools of cascading layers and can use.

So far, by disposing cloud gateway in third party cloud in the embodiment of the present invention so that third party cloud can be used as quilt Cascade OpenStack docks with the cascade OpenStack of private clound, so as to provide towards the unified standard of a variety of mixed clouds OpenStack api interfaces.Tenant can be by being realized in private clound and third party cloud by the OpenStack api interfaces Indifference operating experience, that is, shield the API differences between different clouds, so as to improve mixing cloud network compatibility and API please Seek treatment effeciency.

It is above-mentioned that mainly scheme provided in an embodiment of the present invention is described from the angle of interaction between each network element.Can With understanding, above-mentioned UE, radio reception device etc. are in order to realize above-mentioned function, and it comprises performing, each function is hard accordingly Part structure and/or software module.Those skilled in the art should be readily appreciated that, be retouched with reference to the embodiments described herein The unit and algorithm steps for each example stated, the embodiment of the present invention can be with the combining forms of hardware or hardware and computer software To realize.Some functions is performed in a manner of hardware or computer software driving hardware actually, depending on technical scheme Application-specific and design constraint.Professional and technical personnel can to each specific application come using distinct methods to realize The function of description, but this realize it is not considered that scope beyond the embodiment of the present invention.

The embodiment of the present invention can carry out functional module according to above method example to above-mentioned CCS nodes, cloud gateway etc. Division, for example, can correspond to each function divides each functional module, two or more functions can also be integrated in In one processing module.Above-mentioned integrated module can both be realized in the form of hardware, can also use software function module Form realize.It should be noted that the division in the embodiment of the present invention to module is schematical, only a kind of logic work( It can divide, can there is other dividing mode when actually realizing.

In the case where dividing each functional module using corresponding each function, Fig. 9 shows involved in above-described embodiment And CCS nodes a kind of possible structural representation, the CCS nodes include：Acquiring unit 1101, transmitting element 1102, wound Build unit 1103 and updating block 1104.

Wherein, acquiring unit 1101, it is used for：The virtual resource request initiated in private clound is obtained, the virtual resource please Ask for asking the virtual resource in third party cloud, the private clound is located at cascading layers, and the third party cloud, which is located at, is cascaded layer；

Transmitting element 1102, is used for：By calling OpenStack API that virtual resource request is pass-through into described the In the cloud gateway of tripartite's cloud, to cause the API of cloud gateway third party cloud according to the virtual resource request call will Virtual resource in the third party cloud is allocated to the private clound.

Further, the transmitting element 1102, is additionally operable to：Cloud gateway into the third party cloud is sent in Parameter mapping relations between OpenStack API and the privately owned API of third party cloud during Transfer Parameters.

Further, creating unit 1103, it is used for：Vpn tunneling is established between the third party cloud and the private clound； The virtual machine of carrying cloud gateway is created in the third party cloud；The mixing that the cloud gateway provides is disposed in the virtual machine Cloud service, and the mixing cloud service that the cloud gateway is provided is registered in the private clound.

Further, updating block 1104, it is used for：Update in IP resource pools and obtained at least from the third party cloud One floating IP address；The floating IP address updated in the IP resource pools is synchronized to the private clound and the third party In the cloud gateway of cloud.

Further, the acquiring unit 1101, is specifically used for：By calling OpenStack API to obtain in private clound The virtual resource request of initiation.

In the case where dividing each functional module using corresponding each function, Figure 10 shows involved in above-described embodiment And cloud gateway a kind of possible structural representation, the cloud gateway includes：Acquiring unit 1201, converting unit 1202 and hold Row unit 1203.

Wherein, acquiring unit 1201, it is used for：Virtual resource request, institute are obtained from private clound by OpenStack API State virtual resource to ask for asking the virtual resource in third party cloud, the private clound is located at cascading layers, the third party cloud Positioned at being cascaded layer；

Converting unit 1202, is used for：The virtual resource is asked to be converted to the privately owned API's for supporting the third party cloud API request；

Execution unit 1203, is used for：The virtual resource in the third party cloud is allocated to according to the API request described Private clound.

Further, the virtual resource request is asked for virtual machine creating, is carried and is treated in the virtual machine creating request Create the first configuration parameter of virtual machine；The converting unit 1202, is specifically used for：According to it is preset OpenStackAPI with Parameter mapping relations between the privately owned API of third party cloud during Transfer Parameters, search corresponding with first configuration parameter the Two configuration parameters；The first configuration parameter during the virtual machine creating is asked is revised as second configuration parameter, is propped up Hold the privately owned API of third party cloud API request.

Further, virtual resource request is virtual volume request to create, and the is carried in the virtual volume request to create A roll of type parameter；The converting unit 1102, is specifically used for：According to preset in OpenStack API and third party cloud Parameter mapping relations between privately owned API during Transfer Parameters, search volume Two type corresponding with the first volume type parameter Parameter；First volume type parameter in the virtual volume request to create is revised as the volume Two type parameter, supported The privately owned API of third party cloud API request.

Further, the acquiring unit 1101, is additionally operable to：Receive that CCS nodes in the private clound send Parameter mapping relations between OpenStack API and the privately owned API of third party cloud during Transfer Parameters.

Wherein, all related contents for each step that above method embodiment is related to can quote corresponding function module Function description, will not be repeated here.

Further, above-mentioned CCS nodes and cloud gateway can be deployed in respectively by the form of virtual machine OpenStack cascading layers and OpenStack are cascaded layer.

Wherein, virtual machine (VM), refer to by software virtual machine can be simulated on a physical host one or More virtual computers, and these virtual machines are operated just as real computer, and behaviour can be installed on virtual machine Make system and application program, virtual machine may also access Internet resources.For the application program run in virtual machine, virtually Machine is like to be operated in real computer.

Specifically, shown in Figure 11, above-mentioned virtual machine can be deployed in physical host 100.

The physical host 100 includes hardware layer, the Host 1001 operated on the hardware layer and operated in At least one virtual machine VM 1002 on the Host 1001, and the hardware layer include network interface card 1003, processor 1004 and internal memory 1005 etc..

Wherein, hardware layer refers to the hardware platform of virtualized environment operation.Wherein, hardware layer may include multiple hardwares, example Hardware layer such as certain physical host may include processor (such as CPU) and internal memory, can also include network interface card (such as RDMA network interface cards), The input/output of memory etc. high speed/low speed (I/O, Input/Output) equipment, and set with the other of particular procedure function It is standby.

Host (Host)：As management level, to complete the management of hardware resource, distribution；Presented for virtual machine virtual Hardware platform；Realize the scheduling and isolation of virtual machine.Wherein, Host is probably monitor of virtual machine (VMM)；In addition, VMM sometimes Coordinate with 1 privileged virtual machine, both combine composition Host.Wherein, virtual hardware platform is to each virtual machine for running thereon Various hardware resources are provided, virtual processor (such as VCPU), virtual memory, virtual disk, Microsoft Loopback Adapter are such as provided.Its In, the virtual disk can correspond to Host a file or a logic block device.Virtual machine operates in Host and prepared for it Virtual hardware platform on, one or more virtual machines are run on Host.

It should be understood that the embodiment of the present invention can apply in xen virtual machine platforms, can also be applied to can apply to appoint Needed during one migration virtual machine of meaning in the virtual platform that is mapped virutal machine memory；The embodiment of the present invention is not entered to this Row limitation.

In the above-described embodiments, can be come in fact by software, hardware, firmware or its any combination with all or part of It is existing.When being realized using software program, can occur in the form of a computer program product whole or in part.The computer Program product includes one or more computer instructions.When loading on computers and performing the computer program instructions, entirely Portion is partly produced according to the flow or function described in the embodiment of the present invention.The computer can be all-purpose computer, specially With computer, computer network or other programmable devices.The computer instruction can be stored in computer-readable storage In medium, or the transmission from a computer-readable recording medium to another computer-readable recording medium, for example, the meter Calculation machine instruction can from a web-site, computer, server or data center by it is wired (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave etc.) mode to another web-site, computer, service Device or data center's transmission.The computer-readable recording medium can be any usable medium that computer can access or It is the data storage devices such as server, the data center integrated comprising one or more usable mediums.The usable medium can be Magnetic medium, (for example, floppy disk, hard disk, tape), optical medium (for example, DVD) or semiconductor medium (such as solid state hard disc Solid State Disk (SSD)) etc..

Described above, the only embodiment of the application, but the protection domain of the application is not limited thereto is any Change or replacement in the technical scope that the application discloses, should all cover within the protection domain of the application.Therefore, this Shen Protection domain please should be based on the protection scope of the described claims.

Claims

A kind of 1. distribution method of virtual resource, it is characterised in that including：

Cloud configuration service CCS nodes obtain the virtual resource request initiated in private clound, and the virtual resource asks to be used to ask Virtual resource in third party cloud, the private clound are located at cascading layers, and the third party cloud, which is located at, is cascaded layer；

The CCS nodes are by calling OpenStack application programming interfaces API that virtual resource request is pass-through into institute In the cloud gateway for stating third party cloud, to cause cloud gateway third party cloud according to the virtual resource request call Virtual resource in the third party cloud is allocated to the private clound by API.
2. according to the method for claim 1, it is characterised in that initiated in the CCS nodes obtain private clound virtual Before resource request, in addition to：

Cloud gateway of the CCS nodes into the third party cloud is sent in the privately owned API of OpenStack API and third party cloud Between Transfer Parameters when parameter mapping relations.
3. method according to claim 1 or 2, it is characterised in that the void initiated in private clound is obtained in the CCS nodes Before intending resource request, in addition to：

The CCS nodes establish VPN vpn tunneling between the third party cloud and the private clound；

The CCS nodes create the virtual machine of carrying cloud gateway in the third party cloud；

The CCS nodes dispose the mixing cloud service that the cloud gateway provides in the virtual machine, and by the cloud net The mixing cloud service provided is closed to be registered in the private clound.
4. according to the method any one of claim 1-3, it is characterised in that pass through calling in the CCS nodes Virtual resource request is pass-through in the cloud gateway of the third party cloud by OpenStack API, to cause the cloud gateway Described according to the API of third party cloud described in the virtual resource request call, the virtual resource in the third party cloud is allocated to After private clound, in addition to：

The CCS nodes update at least one floating IP address obtained from the third party cloud in IP resource pools；

The floating IP address updated in the IP resource pools is synchronized to the private clound and the third party by the CCS nodes In the cloud gateway of cloud.
5. according to the method any one of claim 1-4, it is characterised in that the CCS nodes obtain to be sent out in private clound The virtual resource request risen, including：

The virtual resource that the CCS nodes are initiated by calling OpenStack API to obtain in private clound is asked.
A kind of 6. distribution method of virtual resource, it is characterised in that including：

Cloud gateway obtains virtual resource request by OpenStack API from private clound, and the virtual resource asks to be used to ask The virtual resource in third party cloud is sought, the private clound is located at cascading layers, and the third party cloud, which is located at, is cascaded layer；

The cloud gateway is converted to the virtual resource request API request for the privately owned API for supporting the third party cloud；

Virtual resource in the third party cloud is allocated to the private clound by the cloud gateway according to the API request.
7. according to the method for claim 6, it is characterised in that the virtual resource request is asked for virtual machine creating, institute State the first configuration parameter that virtual machine to be created is carried in virtual machine creating request；

Wherein, the virtual resource is asked the API for being converted to the privately owned API for supporting the third party cloud please by the cloud gateway Ask, including：

The cloud gateway is according to ginseng during the preset Transfer Parameters between OpenStack API and the privately owned API of third party cloud Number mapping relations, search the second configuration parameter corresponding with first configuration parameter；

The first configuration parameter during the cloud gateway asks the virtual machine creating is revised as second configuration parameter, obtains Support the privately owned API of third party cloud API request.
8. according to the method for claim 6, it is characterised in that virtual resource request is virtual volume request to create, institute State carrying first volume type parameter in virtual volume request to create；

Wherein, the virtual resource is asked the API for being converted to the privately owned API for supporting the third party cloud please by the cloud gateway Ask, including：

The cloud gateway is according to ginseng during the preset Transfer Parameters between OpenStack API and the privately owned API of third party cloud Number mapping relations, search volume Two type parameter corresponding with the first volume type parameter；

First volume type parameter in the virtual volume request to create is revised as the volume Two type parameter by the cloud gateway, Obtain supporting the privately owned API of third party cloud API request.
9. according to the method any one of claim 6-8, it is characterised in that in the cloud gateway by the virtual resource Before request is converted to the API request for the privately owned API for supporting the third party cloud, in addition to：

The cloud gateway receive that CCS nodes in the private clound send in OpenStack API and the privately owned API of third party cloud Between Transfer Parameters when parameter mapping relations.
A kind of 10. cloud configuration service CCS nodes, it is characterised in that including：

Acquiring unit, it is used for：The virtual resource request initiated in private clound is obtained, the virtual resource asks to be used to ask the 3rd Fang Yunzhong virtual resource, the private clound are located at cascading layers, and the third party cloud, which is located at, is cascaded layer；

Transmitting element, it is used for：By calling OpenStack application programming interfaces API that the virtual resource is asked into transparent transmission Into the cloud gateway of the third party cloud, to cause cloud gateway third party cloud according to the virtual resource request call API the virtual resource in the third party cloud is allocated to the private clound.
11. CCS nodes according to claim 10, it is characterised in that

The transmitting element, is additionally operable to：Cloud gateway into the third party cloud is sent in OpenStack API and third party cloud Privately owned API between Transfer Parameters when parameter mapping relations.
12. the CCS nodes according to claim 10 or 11, it is characterised in that the CCS nodes also include：

Creating unit, it is used for：VPN vpn tunneling is established between the third party cloud and the private clound；Institute State the virtual machine that carrying cloud gateway is created in third party cloud；The mixed cloud clothes that the cloud gateway provides are disposed in the virtual machine Business, and the mixing cloud service that the cloud gateway is provided is registered in the private clound.
13. the CCS nodes according to any one of claim 10-12, it is characterised in that the CCS nodes also include：

Updating block, it is used for：At least one floating IP address obtained from the third party cloud is updated in IP resource pools；Will The floating IP address updated in the IP resource pools is synchronized in the cloud gateway of the private clound and the third party cloud.
14. the CCS nodes according to any one of claim 10-13, it is characterised in that

The acquiring unit, is specifically used for：Please by calling OpenStack API to obtain the virtual resource initiated in private clound Ask.
A kind of 15. cloud gateway, it is characterised in that including：

Acquiring unit, it is used for：Virtual resource request is obtained from private clound by OpenStack API, the virtual resource please Ask for asking the virtual resource in third party cloud, the private clound is located at cascading layers, and the third party cloud, which is located at, is cascaded layer；

Converting unit, it is used for：Virtual resource request is converted to the API request for the privately owned API for supporting the third party cloud；

Execution unit, it is used for：The virtual resource in the third party cloud is allocated to the private clound according to the API request.
16. cloud gateway according to claim 15, it is characterised in that the virtual resource request please for virtual machine creating Ask, the first configuration parameter of virtual machine to be created is carried in the virtual machine creating request；

The converting unit, is specifically used for：Passed according to preset between OpenStack API and the privately owned API of third party cloud Parameter mapping relations during parameter are passed, search the second configuration parameter corresponding with first configuration parameter；By the virtual machine The first configuration parameter in request to create is revised as second configuration parameter, obtains supporting the privately owned API of the third party cloud API request.
17. cloud gateway according to claim 15, it is characterised in that the virtual resource request creates for virtual volume please Ask, first volume type parameter is carried in the virtual volume request to create；

The converting unit, is specifically used for：Passed according to preset between OpenStack API and the privately owned API of third party cloud Parameter mapping relations during parameter are passed, search volume Two type parameter corresponding with the first volume type parameter；By the void The first volume type parameter intended in volume request to create is revised as the volume Two type parameter, obtains supporting the third party cloud Privately owned API API request.
18. the cloud gateway according to any one of claim 15-17, it is characterised in that

The acquiring unit, is additionally operable to：Receive that CCS nodes in the private clound send in OpenStack API and third party Parameter mapping relations between the privately owned API of cloud during Transfer Parameters.
A kind of 19. OpenStack cascade systems, it is characterised in that the system includes the private clound for being arranged on cascading layers, and It is arranged on the third party cloud for being cascaded layer, the CCS nodes in the private clound are by using OpenStack application programming interfaces API and the cloud gateway communication in the third party cloud.
20. a kind of computer-readable recording medium, instruction is stored with the computer-readable recording medium, it is characterised in that When the instruction is being run on cloud configuration service CCS nodes so that the CCS nodes are performed as any in claim 1-5 The distribution method of virtual resource described in.
21. a kind of computer-readable recording medium, instruction is stored with the computer-readable recording medium, it is characterised in that When the instruction is being run on cloud gateway so that the cloud gateway performs virtual as any one of claim 6-9 The distribution method of resource.
22. a kind of computer program product for including instruction, it is characterised in that taken when the computer program product configures in cloud When being run on business CCS nodes so that the CCS nodes perform point of the virtual resource as any one of claim 1-5 Method of completing the square.
23. a kind of computer program product for including instruction, it is characterised in that when the computer program product is on cloud gateway During operation so that the cloud gateway performs the distribution method of the virtual resource as any one of claim 6-9.