U.S. patent application number 12/324758 was filed with the patent office on 2010-05-27 for systems and methods for multiple cloud marketplace aggregation.
Invention is credited to James Michael Ferris.
Application Number | 20100131624 12/324758 |
Document ID | / |
Family ID | 42197368 |
Filed Date | 2010-05-27 |
United States Patent
Application |
20100131624 |
Kind Code |
A1 |
Ferris; James Michael |
May 27, 2010 |
SYSTEMS AND METHODS FOR MULTIPLE CLOUD MARKETPLACE AGGREGATION
Abstract
Embodiments relate to systems and methods for multiple cloud
marketplace aggregation. An aggregation engine communicates with a
set of multiple cloud marketplaces, each of which communicates with
an associated set of clouds. A requesting entity, such as a user
requesting the instantiation of a set of virtual machines, can
transmit a resource request to the aggregation engine. The
aggregation engine can fan out or distribute a replicated request
to the set of multiple cloud marketplaces. Each cloud marketplace
can receive the request and respond to indicate available resources
that can be produced from their respect set of clouds. The
aggregation engine can collect the responses of the various
marketplaces, and can generate one or more selections based on
selection logic such as best match, cost factors, or other
criteria. In embodiments, a user can manually select the desired
marketplace(s) to instantiate or update their virtual machine or
other target objects.
Inventors: |
Ferris; James Michael;
(Cary, NC) |
Correspondence
Address: |
MH2 TECHNOLOGY LAW GROUP (Cust. No. w/Red Hat)
1951 KIDWELL DRIVE, SUITE 550
TYSONS CORNER
VA
22182
US
|
Family ID: |
42197368 |
Appl. No.: |
12/324758 |
Filed: |
November 26, 2008 |
Current U.S.
Class: |
709/221 |
Current CPC
Class: |
G06F 8/65 20130101; G06F
9/5072 20130101; H04L 47/76 20130101; G06F 2209/5015 20130101; G06F
9/5027 20130101; H04L 67/10 20130101; G06Q 30/06 20130101 |
Class at
Publication: |
709/221 |
International
Class: |
G06F 15/177 20060101
G06F015/177 |
Claims
1. A method of generating resources in a cloud-based network,
comprising: receiving a request for cloud-based resources from a
requesting entity; receiving the request for cloud-based resources
in an aggregation engine; transmitting a set of replicated requests
based on the request for cloud-based resources from the aggregation
engine to a set of marketplace systems, each of the set of
marketplace systems communicating with at least one respective set
of cloud-based networks; receiving a set of resource offerings from
the set of marketplace systems based on the set of replicated
requests; and identifying a set of selected cloud-based resources
from the set of resource offerings made by the set of marketplace
systems to satisfy the request for cloud-based resources from the
requesting entity.
2. The method of claim 1, wherein the requesting entity comprises
at least one a virtual machine, an application, and a software
appliance.
3. The method of claim 1, wherein the request for cloud-based
resources comprises at least one of an instantiation request and an
update request.
4. The method of claim 1, wherein the request for cloud-based
resources comprises a request for at least one of processor
resources, memory resources, input/output (I/O) resources,
application resources, operating system resources, and service
levels represented by a service level agreement.
5. The method of claim 1, wherein the set of marketplace systems
comprises multiple marketplace systems configured in at least one
of a parallel configuration, a serial configuration, a mixed
parallel/serial configuration, and a multiple layer
configuration.
6. The method of claim 1, further comprising receiving an updated
request for cloud-based resources from the requesting entity.
7. The method of claim 6, further comprising receiving a set of
updated resource offerings from the set of marketplace systems
based on the updated request.
8. The method of claim 1, further comprising providing the set of
selected cloud-based resources to the requesting entity.
9. A system for generating cloud-based resources, comprising: a
first interface to a requesting entity; a second interface to a set
of marketplace systems, each of the set of marketplace systems
communicating with at least one respective set of cloud-based
networks; and an aggregation engine, communicating with the
requesting entity via the first interface and the set of
marketplace systems via the second interface, the aggregation
engine being configured to receive a request for cloud-based
resources from the requesting entity, transmit a set of replicated
requests based on the request for cloud-based resources from the
aggregation engine to the set of marketplace systems, receive a set
of resource offerings from the set of marketplace systems based on
the set of replicated requests, and identify a set of selected
cloud-based resources from the set of resource offerings made by
the set of marketplace systems to satisfy the request for
cloud-based resources from the requesting entity.
10. The system of claim 9, wherein the requesting entity comprises
at least one a virtual machine, an application, and a software
appliance.
11. The system of claim 9, wherein the request for cloud-based
resources comprises at least one of an instantiation request and an
update request.
12. The system of claim 11, wherein the request for cloud-based
resources comprises a request for at least one of processor
resources, memory resources, input/output (I/O) resources,
application resources, operating system resources, and service
levels represented by a service level agreement.
13. The system of claim 9, wherein the set of marketplace systems
comprises multiple marketplace systems configured in at least one
of a parallel configuration, a serial configuration, a mixed
parallel/serial configuration, and a multiple layer
configuration.
14. The system of claim 9, wherein the aggregation engine is
further configured to receive an updated request for cloud-based
resources from the requesting entity.
15. The system of claim 14, wherein the aggregation engine is
further configured to receive a set of updated resource offerings
from the set of marketplace systems based on the updated
request.
16. The system of claim 9, wherein the aggregation engine is
further configured to provide the set of selected cloud-based
resources to the requesting entity.
17. An instantiated object, the instantiated object being
instantiated or updated according to a method comprising: receiving
a request for cloud-based resources from a requesting entity;
receiving the request for cloud-based resources in an aggregation
engine; transmitting a set of replicated requests based on the
request for cloud-based resources from the aggregation engine to a
set of marketplace systems, each of the set of marketplace systems
communicating with at least one respective set of cloud-based
networks; receiving a set of resource offerings from the set of
marketplace systems based on the set of replicated requests; and
identifying a set of selected cloud-based resources from the set of
resource offerings made by the set of marketplace systems to
satisfy the request for cloud-based resources from the requesting
entity.
18. The instantiated object of claim 17, wherein the requesting
entity comprises at least one a virtual machine, an application,
and a software appliance.
19. The instantiated object of claim 17, wherein the request for
cloud-based resources comprises at least one of an instantiation
request and an update request.
20. The instantiated object of claim 17, wherein the request for
cloud-based resources comprises a request for at least one of
processor resources, memory resources, input/output (I/O)
resources, application resources, operating system resources, and
service levels represented by a service level agreement.
Description
FIELD
[0001] The present teachings relate to systems and methods for
multiple cloud marketplace aggregation, and more particularly to
platforms and techniques for generating responses to resource
requests from a collective set of cloud-based marketplaces and
selecting from those combined offerings to instantiate or update a
virtual machine or other entity.
BACKGROUND OF RELATED ART
[0002] The advent of cloud-based computing architectures has opened
new possibilities for the rapid and scalable deployment of virtual
Web stores, media outlets, and other on-line sites or services. In
general, a cloud-based architecture deploys a set of hosted
resources such as processors, operating systems, software and other
components that can be combined or strung together to form virtual
machines. A user or customer can request the instantiation of a
virtual machine or set of machines from those resources from a
central server or management system to perform intended tasks or
applications. For example, a user may wish to set up and
instantiate a virtual server from the cloud to create a storefront
to market products or services on a temporary basis, for instance,
to sell tickets to an upcoming sports or musical performance. The
user can lease or subscribe to the set of resources needed to build
and run the set of instantiated virtual machines on a comparatively
short-term basis, such as hours or days, for their intended
application. Another type of software entity that has found certain
application in certain spaces is software appliances, which
generally speaking can represent relatively self-contained software
installations including full or customized partial operating system
installations, combined with selected applications in a single
installation or update package.
[0003] Currently, when a user desires to can lease or subscribe to
the set of resources, the user may request the set of resources
based on their service level requirements and then receive a price
for the request from a cloud marketplace system. Currently, no
mechanism exists to permit those resource requests to be
distributed to multiple cloud marketplace systems, to widen the
range of available options or create the opportunity for redundancy
in the sources for those requested resources. Thus, there is a need
in the art for methods and systems that provide an ability to
distribute or fan out a resource request to multiple cloud
marketplace systems or platforms, and aggregate the resulting
resource offerings to select a set of sources best suited to the
requesting entity's needs.
DESCRIPTION OF THE DRAWINGS
[0004] The accompanying drawings, which are incorporated in and
constitute a part of this specification, illustrate embodiments of
the present teachings and together with the description, serve to
explain the principles of the present teachings. In the
figures:
[0005] FIG. 1 illustrates an overall cloud system architecture in
which various embodiments of the present teachings can be
practiced;
[0006] FIG. 2 illustrates an overall cloud system architecture in
which various embodiments of the present teachings can be practiced
in another regard including multiple cloud arrangements, according
to various embodiments;
[0007] FIG. 3 illustrates an overall marketplace environment in
which systems and methods for multiple cloud marketplace
aggregation can operate, according to various embodiments;
[0008] FIG. 4 illustrates an overall marketplace environment in
which systems and methods for multiple cloud marketplace
aggregation can operate including request distribution and resource
aggregation, according to various embodiments;
[0009] FIG. 5 illustrates an exemplary hardware implementation of a
marketplace system, according to various embodiments; and
[0010] FIG. 6 illustrates a flowchart of overall processing for
multiple cloud marketplace aggregation, according to various
embodiments.
DESCRIPTION OF EMBODIMENTS
[0011] Embodiments of the present teachings relate to systems and
methods for multiple cloud marketplace aggregation. More
particularly, embodiments relate to platforms and techniques for
multiple marketplace aggregation in which a request for resources
to instantiate or update a requesting entity can be transmitted to
an aggregation engine. The aggregation engine can be configured to
receive the resource request and replicate or transmit that request
to a set of marketplace systems or platforms. The multiple
marketplace systems can each communicate with a set of clouds from
which processor, memory, software, or other resources can be
requested and extracted. In embodiments, the aggregation engine can
comprise a separate server, or, in embodiments, can be incorporated
in a marketplace system.
[0012] The set of marketplace systems can respond to the replicated
resource request with an indication of the resources that one or
more of their constituent clouds are prepared to offer and deliver
to the requesting virtual machine, or other requesting entity. In
embodiments, the aggregation engine can employ selection logic to
select one or more resource offerings from the set of marketplace
systems, and provide those resources to the requesting virtual
machine or other entity. In embodiments, a systems administrator or
other user can manually select the desired marketplace sources from
amongst the competing offerings. The aggregation engine can, in
embodiments, select multiple more than one marketplace system to
satisfy the request for resources, for instance to stagger the
marketplace systems from which resources will be drawn at different
times.
[0013] Embodiments of the present teachings thereby relate to
systems and methods which operate in a marketplace environment
based on cloud computing networks. More particularly, embodiments
relate to platforms and techniques in which a cloud marketplace
system provides details on the resources and services provided by
the cloud computing environments, to allow users to evaluate the
resources and services provided by the cloud computing environments
in relation to the specific requirements of desired applications
and/or software appliances.
[0014] According to embodiments, in general, the overall cloud
marketplace system can be configured to communicate with multiple
cloud computing environments in order to ascertain the details for
the resources and services provided by the cloud computing
environments. In particular, the cloud marketplace system can be
configured to retrieve, from the cloud computing environments,
resource and service data which describes the capabilities,
services, status, and cost of the cloud computing environment. The
resource and service data can include computing resources and
services provided by the cloud computing environments, computing
resources and services available in the cloud computing
environments at particular time periods, cost data for computing
resources and services provided by the cloud computing
environments, and status data for the cloud computing environments
at particular time periods.
[0015] In embodiments, in order to acquire the resource and service
data, the cloud marketplace system can be configured to request the
resource and service data from cloud management systems located in
the cloud computing environments. Likewise, the cloud marketplace
system can be configured to communicate with the resources of the
cloud computing environments directly in order to obtain the
resource and service data.
[0016] In embodiments, the cloud marketplace system can be
configured to maintain a repository for the resource and service
data in order to provide the marketplace for the cloud computing
environments. The cloud marketplace system can be configured to
update the repository periodically to maintain current resource and
service data for the cloud computing environments. Likewise, when
providing the marketplace, the cloud marketplace system can obtain
the resource and service data, on-demand, and directly from the
cloud computing environments.
[0017] In embodiments, to provide the marketplace, the cloud
marketplace system can be configured receive a request for
information pertaining to the resources or services provided by or
available in the cloud computing environments. The cloud
marketplace system can be configured to search the repository for
resource and service data relating to the request. Likewise, the
cloud marketplace system can be configured to obtain the resource
and service data directly from the cloud computing environments.
Once located, the cloud marketplace system can be configured to
generate a marketplace report detailing the resource and service
data matching the request. The cloud marketplace system can be
configured to provide the report to initiator of the request.
[0018] In embodiments, the cloud marketplace system can be
configured to utilize the resource and service data to provide
migration services for virtual machines initiated in the cloud
computing environments. In particular, for a particular virtual
machine or machines, the cloud marketplace system can be configured
to receive a request to monitor the resource and service data of
the cloud computing environments for the occurrence of a particular
event. The event can occur when a portion of the resource and
service data reaches a threshold value received in the request to
migrate. The cloud marketplace system can be configured to monitor
the cloud computing environments in order to determine when the
resources or services data indicates the occurrence of the event.
Upon occurrence of the event, the cloud marketplace system can be
configured to migrate the virtual machine or machines to a new
cloud computing environment with the resources and services data
matching the event.
[0019] By providing a marketplace for the services and resources of
cloud computing environments, users can perform efficient
cost-accounting for, shopping for, and migrations of existing and
planned workloads to the best possible cloud computing environment.
As such, the user can locate and find the best priced and best
quality service for their intended applications and/or software
appliances. Reference will now be made in detail to exemplary
embodiments of the present teachings, which are illustrated in the
accompanying drawings. Where possible the same reference numbers
will be used throughout the drawings to refer to the same or like
parts.
[0020] FIG. 1 illustrates an overall cloud computing environment,
in which systems and methods for multiple cloud marketplace
aggregation can operate, according to embodiments of the present
teachings. Embodiments described herein can be implemented in or
supported by a cloud network architecture. As used herein, a
"cloud" can comprise a collection of resources that can be invoked
to instantiate a virtual machine, process, or other resource for a
limited or defined duration. As shown for example in FIG. 1, the
collection of resources supporting a cloud 102 can comprise a set
of resource servers 108 configured to deliver computing components
needed to instantiate a virtual machine, process, or other
resource. For example, one group of resource servers can host and
serve an operating system or components thereof to deliver to and
instantiate a virtual machine. Another group of resource servers
can accept requests to host computing cycles or processor time, to
supply a defined level of processing power for a virtual machine. A
further group of resource servers can host and serve applications
to load on an instantiation of a virtual machine, such as an email
client, a browser application, a messaging application, or other
applications or software. Other types of resource servers are
possible.
[0021] In embodiments, the entire set of resource servers 108 or
other hardware or software resources used to support the cloud 102
along with its instantiated virtual machines is managed by a cloud
management system 104. The cloud management system 104 can comprise
a dedicated or centralized server and/or other software, hardware,
and network tools that communicate via one or more networks 106
such as the Internet or other public or private network with all
sets of resource servers to manage the cloud 102 and its operation.
To instantiate a new set of virtual machines, a user can transmit
an instantiation request to the cloud management system 104 for the
particular type of virtual machine they wish to invoke for their
intended application. A user can for instance make a request to
instantiate a set of virtual machines configured for email,
messaging or other applications from the cloud 102. The request can
be received and processed by the cloud management system 104, which
identifies the type of virtual machine, process, or other resource
being requested. The cloud management system 104 can then identify
the collection of resources necessary to instantiate that machine
or resource. In embodiments, the set of instantiated virtual
machines or other resources can for example comprise virtual
transaction servers used to support Web storefronts, or other
transaction sites.
[0022] In embodiments, the user's instantiation request can specify
a variety of parameters defining the operation of the set of
virtual machines to be invoked. The instantiation request, for
example, can specify a defined period of time for which the
instantiated machine or process is needed. The period of time can
be, for example, an hour, a day, or other increment of time. In
embodiments, the user's instantiation request can specify the
instantiation of a set of virtual machines or processes on a task
basis, rather than for a predetermined amount of time. For
instance, a user could request resources until a software update is
completed. The user's instantiation request can specify other
parameters that define the configuration and operation of the set
of virtual machines or other instantiated resources. For example,
the request can specify an amount of processing power or
input/output (I/O) throughput the user wishes to be available to
each instance of the virtual machine or other resource. In
embodiments, the requesting user can for instance specify a service
level agreement (SLA) acceptable for their application. Other
parameters and settings can be used. One skilled in the art will
realize that the user's request can likewise include combinations
of the foregoing exemplary parameters, and others.
[0023] When the request to instantiate a set of virtual machines or
other resources has been received and the necessary resources to
build that machine or resource have been identified, the cloud
management system 104 can communicate with one or more set of
resource servers 108 to locate resources to supply the required
components. The cloud management system 104 can select providers
from the diverse set of resource servers 108 to assemble the
various components needed to build the requested set of virtual
machines or other resources. It may be noted that in some
embodiments, permanent storage such as hard disk arrays may not be
included or located within the set of resource servers 108
available to the cloud management system 104, since the set of
instantiated virtual machines or other resources may be intended to
operate on a purely transient or temporary basis. In embodiments,
other hardware, software or other resources not strictly located or
hosted in the cloud can be leveraged as needed. For example, other
software services that are provided outside of the cloud 102 and
hosted by third parties can be invoked by in-cloud virtual
machines. For further example, other non-cloud hardware and/or
storage services can be utilized as an extension to the cloud 102,
either on an on-demand or subscribed or decided basis.
[0024] With the resource requirements identified, the cloud
management system 104 can extract and build the set of virtual
machines or other resources on a dynamic or on-demand basis. For
example, one set of resource servers 108 can respond to an
instantiation request for a given quantity of processor cycles with
an offer to deliver that computational power immediately and
guaranteed for the next hour. A further set of resource servers 108
can offer to immediately supply communication bandwidth, for
example on a guaranteed minimum or best-efforts basis. In other
embodiments, the set of virtual machines or other resources can be
built on a batch basis or at a particular future time. For example,
a set of resource servers 108 can respond to a request for
instantiation at a programmed time with an offer to deliver the
specified quantity of processor cycles within a specific amount of
time, such as the next 12 hours.
[0025] The cloud management system 104 can select group of servers
in the set of resource servers 108 that match or best match the
instantiation request for each component needed to build the
virtual machine or other resource. The cloud management system 104
can then coordinate the integration of the completed group of
servers from the set of resource servers 108, to build and launch
the requested set of virtual machines or other resources. The cloud
management system 104 can track the combined group of servers
selected from the set of resource servers 108, or other distributed
resources that are dynamically or temporarily combined, to produce
and manage the requested virtual machine population or other
resources.
[0026] In embodiments, the cloud management system 104 can generate
a resource aggregation table that identifies the various sets of
resource servers that will be used to supply the components of the
virtual machine or process. The sets of resource servers can be
identified by unique identifiers such as, for instance, Internet
Protocol (IP) addresses or other addresses. The cloud management
system 104 can register the finalized group of servers in the set
resource servers 108 contributing to an instantiated machine or
process.
[0027] The cloud management system 104 can then set up and launch
the initiation process for the virtual machines, processes, or
other resources to be delivered from the cloud. The cloud
management system 104 can for instance transmit an instantiation
command or instruction to the registered group of servers in set of
resource servers 108. The cloud management system 104 can receive a
confirmation message back from each participating server in set of
resource servers 108 indicating a status regarding the provisioning
of their respective resources. Various sets of resource servers can
confirm, for example, the availability of a dedicated amount of
processor cycles, amounts of electronic memory, communications
bandwidth, or applications or other software prepared to be
served.
[0028] As shown for example in FIG. 2, the cloud management system
104 can then instantiate one or more than one set of virtual
machines 116, or other processes based on the resources supplied by
the registered set of resource servers 108. In embodiments, the
cloud management system 104 can instantiate a given number, for
example, 10, 500, 1000, or other numbers of virtual machines to be
made available to users on a network 114, such as the Internet or
other public or private network. Each virtual machine can be
assigned an instantiated machine ID that can be stored in the
resource aggregation table, or other record or image of the
instantiated population. Additionally, the cloud management system
104 can store the duration of each virtual machine and the
collection of resources utilized by the complete set of
instantiated virtual machines 116.
[0029] In embodiments, the cloud management system 104 can further
store, track and manage a user's identity and associated set of
rights or entitlements to software, hardware, and other resources.
Each user that populates a set of virtual machines in the cloud can
have specific rights and resources assigned and made available to
them. The cloud management system 104 can track and configure
specific actions that a user can perform, such as provision a set
of virtual machines with software applications or other resources,
configure a set of virtual machines to desired specifications,
submit jobs to the set of virtual machines or other host, manage
other users of the set of instantiated virtual machines 116 or
other resources, and other privileges or actions. The cloud
management system 104 can further generate records of the usage of
instantiated virtual machines to permit tracking, billing, and
auditing of the services consumed by the user. In embodiments, the
cloud management system 104 can for example meter the usage and/or
duration of the set of instantiated virtual machines 116, to
generate subscription billing records for a user that has launched
those machines. Other billing or value arrangements are
possible.
[0030] The cloud management system 104 can configure each virtual
machine to be made available to users of the one or more networks
106 via a browser interface, or other interface or mechanism. Each
instantiated virtual machine can communicate with the cloud
management system 104 and the underlying registered set of resource
servers 108 via a standard Web application programming interface
(API), or via other calls or interfaces. The set of instantiated
virtual machines 116 can likewise communicate with each other, as
well as other sites, servers, locations, and resources available
via the Internet or other public or private networks, whether
within a given cloud 102 or between clouds.
[0031] It may be noted that while a browser interface or other
front-end can be used to view and operate the set of instantiated
virtual machines 116 from a client or terminal, the processing,
memory, communications, storage, and other hardware as well as
software resources required to be combined to build the virtual
machines or other resources are all hosted remotely in the cloud
102. In embodiments, the set of virtual machines 116 or other
resources may not depend on or require the user's own on-premise
hardware or other resources. In embodiments, a user can therefore
request and instantiate a set of virtual machines or other
resources on a purely off-premise basis, for instance to build and
launch a virtual storefront or other application.
[0032] Because the cloud management system 104 in one regard
specifies, builds, operates and manages the set of instantiated
virtual machines 116 on a logical level, the user can request and
receive different sets of virtual machines and other resources on a
real-time or near real-time basis, without a need to specify or
install any particular hardware. The user's set of instantiated
virtual machines 116, processes, or other resources can be scaled
up or down immediately or virtually immediately on an on-demand
basis, if desired. In embodiments, the various sets of resource
servers that are accessed by the cloud management system 104 to
support a set of instantiated virtual machines 116 or processes can
change or be substituted, over time. The type and operating
characteristics of the set of instantiated virtual machines 116 can
nevertheless remain constant or virtually constant, since instances
are assembled from abstracted resources that can be selected and
maintained from diverse sources based on uniform
specifications.
[0033] In terms of network management of the set of instantiated
virtual machines 116 that have been successfully configured and
instantiated, the cloud management system 104 can perform various
network management tasks including security, maintenance, and
metering for billing or subscription purposes. The cloud management
system 104 of a given cloud 102 can, for example, install or
terminate applications or appliances on individual machines. The
cloud management system 104 can monitor operating virtual machines
to detect any virus or other rogue process on individual machines,
and for instance terminate the infected application or virtual
machine. The cloud management system 104 can likewise manage an
entire set of instantiated virtual machines 116 or other resources
on a collective basis, for instance, to push or delivery a software
upgrade to all active virtual machines. Other management processes
are possible.
[0034] In embodiments, more than one set of virtual machines can be
instantiated in a given cloud at the same, overlapping or
successive times. The cloud management system 104 can, in such
implementations, build, launch and manage multiple sets of virtual
machines based on the same or different underlying set of resource
servers 108, with populations of different sets of instantiated
virtual machines 116 such as may be requested by different users.
The cloud management system 104 can institute and enforce security
protocols in a cloud 102 hosting multiple sets of virtual machines.
Each of the individual sets of virtual machines can be hosted in a
respective partition or sub-cloud of the resources of the cloud
102. The cloud management system 104 of a cloud can for example
deploy services specific to isolated or defined sub-clouds, or
isolate individual workloads/processes within the cloud to a
specific sub-cloud. The subdivision of the cloud 102 into distinct
transient sub-clouds or other sub-components which have assured
security and isolation features can assist in establishing a
multiple user or multi-tenant cloud arrangement. In a multiple user
scenario, each of the multiple users can use the cloud platform as
a common utility while retaining the assurance that their
information is secure from other users of the overall cloud system.
In further embodiments, sub-clouds can nevertheless be configured
to share resources, if desired.
[0035] In embodiments, and as also shown in FIG. 2, the set of
instantiated virtual machines 116 generated in a first cloud 102
can also interact with a set of instantiated virtual machines or
processes generated in a second, third or further cloud 102. The
cloud management system 104 of a first cloud 102 can interface with
the cloud management system 104 of a second cloud 102, to
coordinate those domains and operate the clouds and/or virtual
machines or processes on a combined basis. The cloud management
system 104 of a given cloud 102 can track and manage individual
virtual machines or other resources instantiated in that cloud, as
well as the set of instantiated virtual machines or other resources
in other clouds.
[0036] In the foregoing and other embodiments, the user making an
instantiation request or otherwise accessing or utilizing the cloud
network can be a person, customer, subscriber, administrator,
corporation, organization, or other entity. In embodiments, the
user can be or include another virtual machine, application or
process. In further embodiments, multiple users or entities can
share the use of a set of virtual machines or other resources.
[0037] FIG. 3 illustrates aspects of a cloud marketplace system 200
and its interaction with various clouds 102, according to various
embodiments. In embodiments, the cloud marketplace system 200
provides a marketplace for the services provided by clouds 102. In
embodiments as shown, the cloud marketplace system 200 can comprise
a marketplace engine 205, a migration engine 210, a marketplace
store 215, and an application programming interface (API) 220. The
marketplace engine 205 can be configured to contain control logic
for performing the marketplace processes and for communicating with
the clouds 102, API 220, and marketplace store 215. In embodiments
as shown, the cloud marketplace system 200 provides a marketplace
for the services provided by clouds 102.
[0038] In embodiments, the cloud marketplace system 200 can be
configured to communicate with the clouds 102 in order to ascertain
the details for the resources and services provided by the clouds
102. In particular, the cloud marketplace system 200 can be
configured to retrieve, from the clouds 102, resource and service
data 225 which describes the capabilities, services, status, and
cost of the clouds 102. The resource and service data 225 can
include data detailing computing resources and services provided by
the clouds 102, computing resources and services available in the
clouds 102 at particular time periods, cost for the services
provided by the clouds 102, and status for the clouds 102 at
particular time periods.
[0039] In embodiments, the data detailing the computing resources
and services provided by the clouds 102 can include resource data
specifying the sets of resources servers 108 contained in the
clouds 102 and the computing resources provided by the sets of
resources servers 108 (computing cycles, bandwidth, memory,
storage). Additionally, the data detailing the computing resources
and services provided by the clouds 102 can include service data
specifying particular services provided by the clouds 102 such as
identity management services, cloud management services,
application and appliance building services, and the like.
[0040] In embodiments, the data detailing the computing resources
and services available in the clouds 102 at particular time periods
can include data specifying computing resources and services
available in the clouds 102 current or at some future time.
Additionally, the data detailing the computing resources and
services available in the clouds 102 at particular time periods can
include data specifying service level agreements for the cloud 102
for a period of time.
[0041] In embodiments, the data detailing the cost for the
resources and services provided by the clouds 102 can include data
such as the cost for subscription to the clouds 102, the cost for
usage of the resources and services of the clouds 102, and
discounts of the costs based on the usage. For example, the cost
for usage can include the cost for the resources consumed to
support the virtual machines and can include the cost for the
utilization of the virtual machines by the user or third parties.
These can include the cost for the instantiated time of the virtual
machines, the computing resource consumed by the virtual machines
(computing cycles, bandwidth), the time frame of the computing
resource consumption (peak time, off-peak time), and combinations
thereof. The cost data can include cost data for a current time or
cost data for resources and services in the future.
[0042] In embodiments, the data detailing the status for the clouds
102 at particular time periods can include data specifying the
resources and services current being utilized in the clouds 102.
For example, the status data can include virtual machines currently
instantiated in the clouds 102 and the computing resources of the
sets of resources servers 108 (computing cycles, bandwidth, memory,
storage) currently utilized.
[0043] In embodiments, in order to acquire the resource and service
data 225, the cloud marketplace system 200 can be configured to
request the resource and service data 225 from cloud management
systems 104 located in the clouds 102. Likewise, the cloud
marketplace system 200 can be configured to communicate with the
set of resource servers 108 directly in order to obtain the
resource and service data 225. The cloud marketplace system 200 can
be configured to communicate with the clouds 102 via network 106 or
any other available public or private network. In particular,
marketplace engine 205 can be configured to communicate with the
clouds 102.
[0044] In embodiments, the cloud marketplace system 200 can be
configured to maintain a repository 230 for the resource and
service data 225 in order to provide the marketplace for the clouds
102. In particular, the marketplace engine 205 can be configured to
maintain the repository 230. The repository 230 can be configured
in any format to allow the resource and service data 225 to be
stored and retrieved. For example, the repository can be configured
in any type of proprietary or open-source database format. The
repository 230 can include a record for each cloud 102 that
includes various searchable data fields for storing the resource
and service data 225 for that particular cloud.
[0045] The cloud marketplace system 200 can be configured to update
the repository 230 periodically to maintain current resource and
service data 225 for the clouds 102. Likewise, when providing the
marketplace, the cloud marketplace system 200 can be configured to
obtain the resource and service data 225, on-demand, and directly
from the clouds 102.
[0046] In embodiments, to provide the marketplace, the cloud
marketplace system 200 can be configured receive a request for
information pertaining to the resources or services provided by or
available in the clouds 102. For example, a initiator may request
information on clouds 102 that can provide a certain level of
computing resources at a specific cost during a specific time
period. The initiator of the request the information in order to
see all available resources of the clouds 102 that may meet the
initiators requirements. As such, the request can include the
information regarding the resources desired by the initiator. This
can include the desired computing resources, the time period for
the resources, the duration of the resources, the cost of the
resources, services provided by the cloud, the availability of the
resources, and the like.
[0047] In particular, the marketplace engine 205 can be configured
to communicate with the initiator of the request via API 220. API
220 can be configured to generate GUIs, e.g. dialog boxes, web
pages, as required by marketplace engine 205 and to provide an
interface for receiving requests. The initiator of the request can
be a user desiring utilization of the clouds 102 or the cloud
management systems 104 of the clouds 102.
[0048] Once the request is received, the cloud marketplace system
200 can be configured to search the repository 230 for resource and
service data 225 relating to the request. In particular, the
marketplace engine 205 can be configured to access the repository
230 stored in marketplace store 215 and search the repository 230
for resource and service data 225 matching the request. Likewise,
the cloud marketplace system 200 can be configured to obtain the
resource and service data 225 directly from the clouds 102.
[0049] Once located, the cloud marketplace system 200 can be
configured to generate a marketplace report 235 detailing the
resource and service data 225 matching the request. For example,
the marketplace report 235 can include a list of clouds 102
matching the request alone with the data detailing computing
resources and services provided by the matching clouds 102,
computing resources and services available in the matching clouds
102 at particular time periods specified in the request, cost for
the services and resources requested, and status for the matching
clouds 102 at particular time periods specified in the request.
[0050] In particular, the marketplace engine 205 can be configured
to extract the matching resource and service data from repository
230. Marketplace engine 205 can be configured to arrange the
matching resource and service data 225 in marketplace report
235.
[0051] After generating the marketplace report 235, the cloud
marketplace system 200 can be configured to provide the marketplace
report 235 to the initiator of the request. In particular, the
marketplace engine 205 can be configured to provide the marketplace
report 235 via API 220.
[0052] Once the report is received, the initiator or the user can
make a determination on which resources of the clouds 102 to
utilize. This can include utilizing resources from a single cloud
102 or resources from multiple clouds 102. For example, the
initiator can select one or more cloud 102 with which to
instantiate a virtual machine or machines. The initiator can make a
request for the resources directly to the clouds 102. Likewise, the
cloud marketplace system 200 can be configured to receive the
initiator's requests for resources and forward the request to the
clouds 102, or reserve the resources directly.
[0053] In embodiments, the cloud marketplace system 200 can be
configured to utilize the resource and service data to provide
automatic migration services for virtual machines initiated in the
clouds 102. In particular, the migration engine 210 can be
configured to contain control logic for performing the migration
processes and for communicating with the clouds 102, API 220, and
marketplace store 215.
[0054] In embodiments, for a particular virtual machine or machines
instantiated in one of the clouds 102, the cloud marketplace system
200 can be configured to receive a request to monitor the resource
and service data 225 of the clouds 102 for the occurrence of a
particular event. The event can be the occurrence of a particular
resource or service becoming available in a cloud 102. The event
can be occur when a portion of the resource and service data 225
reaches a threshold value received in the request to migrate. For
example, a user can request that the cloud marketplace system 200
migrate a virtual machine or machines when a particular computing
resources at a specified cost becomes available in one of the
clouds 102.
[0055] In particular, the migration engine 210 can be configured to
communicate with the user or the initiator of the request via API
220. API 220 can be configured to generate GUIs, e.g. dialog boxes,
web pages, as required by migration engine 210 and to provide an
interface for receiving requests.
[0056] To migrate the virtual machine or machines, the cloud
marketplace system 200 can be configured to monitor the clouds 102
in order to determine when the resources or services data 225
indicates the occurrence of the event. In particular, the migration
engine 210 can be configured to periodically search the repository
230 for the resources and services data 225 matching event.
Likewise, the migration engine 210 can be configured to obtain the
resource and service data 225, periodically, directly from the
clouds 102.
[0057] Upon occurrence of the event, the cloud marketplace system
200 can be configured to migrate the virtual machine or machines to
a new cloud 102 with the resources and services data matching the
event. For example, the cloud marketplace system 200 can determine
that a new cloud 102 has resources or services available that match
the user's request and can migrate the virtual machines to the new
cloud 102. In particular, the migration engine 210 can be
configured send an instruction, to the cloud 102 currently
instantiating the virtual machine or machines, to migrate the
virtual machine or machines to the new cloud 102. The instruction
can include an identification of the virtual machine or machines
and an identification of the new cloud 102. Likewise, the migration
engine 210 can be configured to retrieve the virtual machine or
machines from the cloud 102 currently instantiating the virtual
machine or machines and pass the virtual machine or machines to the
new cloud 102 for instantiation.
[0058] Once migrated, the cloud marketplace system 200 can be
configured to notify the user or initiator of the migration. In
particular, migration engine 210 can be configured to notify the
user or initiator via API 220.
[0059] FIG. 4 illustrates an overall system 300, consistent with
systems and methods for multiple cloud marketplace aggregation,
according to various embodiments. In embodiments as shown, a set of
requesting entities 308 can communicate with an aggregation engine
360, to transmit a resource request 312 to aggregation engine 360.
In embodiments, the resource request 312 can contain or encode a
request for a set of specified resources from cloud sources. In
embodiments, the requested resources can include, for instance,
processor cycles, memory allocation, installed applications,
operating systems, service levels under a service level agreement
(SLA), and/or other hardware, software, network, input/output
(I/O), and/or other resources.
[0060] The aggregation engine 360 can receive the resource request
312 and decode that request to determine the corresponding,
hardware, software, network, input/output (I/O), and/or other
resources necessary to satisfy the request. Aggregation engine 360
can in turn transmit a set of replicated requests 364 to
marketplace systems 200 within a set of multiple cloud marketplaces
362. In embodiments as shown, each individual marketplace system
200 can likewise in turn communicate with a set of clouds 302 to
identify resources available with those cloud networks to
potentially satisfy the resource request 312. After interrogating
associated clouds in set of clouds 302, each individual marketplace
system 200 can generate a set of resource offerings 366
representing the hardware, software, network, input/output, and/or
other resources that particular marketplace system 200 along with
its associated set of clouds 302 is prepared to delivery to the
requesting entity. Each marketplace system 200 can transmit the set
of resource offerings to aggregation engine 360. It may be noted
that although a configuration is illustrated in FIG. 4 in which
aggregation engine 360 communicates with set of multiple cloud
marketplaces 362 in a generally parallel configuration, in various
embodiments, the individual marketplace systems 200 can be arranged
in a serial configuration, in a mixed serial/parallel
configuration, or in other configurations. In embodiments, the
individual marketplace systems 200 can be configured in multiple
layers or levels, likewise in various parallel, serial, mixed
serial/parallel, and/or other configurations.
[0061] Aggregation engine 360 can receive the various sets of
resource offerings 366, and examine that information to determine
which marketplace system(s) 200 and associated set(s) of clouds 302
will be utilized to supply the resources specified in the resource
request 312. Aggregation engine 360 can host selection logic 368 to
select between the various sets of resource offerings 366.
Selection logic 368 can, for example, identify resources most
closely matching a requested service level agreement (SLA), or
other hardware, software, network, input/output (I/O) and/or other
resources or factors. Selection logic 368 can incorporate selection
based on cost factors. Selection logic 368 can likewise base
selection of resources on scheduled resource availability, and can,
for example, sequence or stagger individual marketplace systems 200
to supply different resources at different times. Other selection
criteria are possible.
[0062] After identifying the marketplace system(s) 200 from set of
multiple marketplace systems 362, aggregation engine 360 can manage
the instantiation and/or delivery of the constituent resources to
the requesting entity(ies) in set of requesting entities 308. For
example, aggregation engine 360 and/or other logic can instantiate,
access, transmit, or otherwise provide hardware, software, network,
input/output (I/O) and/or resources to the requesting entity. The
result of the resource delivery can be, for example, the
instantiation or updating of a virtual machine, including for
example virtual clients and/or software appliances, as well as the
installation of one or more software applications, the delivery of
data, the provisioning of service level agreements (SLAs), or other
cloud activity.
[0063] FIG. 5 illustrates an exemplary diagram of hardware and
other resources that can be incorporated in a cloud marketplace
system 200 configured to communicate with instantiated clouds 102,
set of clouds 302, and users or initiators via one or more networks
106, according to embodiments. In embodiments as shown, the cloud
marketplace system 200 can comprise a processor 320 communicating
with memory 322, such as electronic random access memory, operating
under control of or in conjunction with operating system 326.
Operating system 326 can be, for example, a distribution of the
Linux.TM. operating system, the Unix.TM. operating system, or other
open-source or proprietary operating system or platform. Processor
320 also communicates with the marketplace store 215, such as a
database stored on a local hard drive. Processor 320 further
communicates with network interface 324, such as an Ethernet or
wireless data connection, which in turn communicates with one or
more networks 106, such as the Internet or other public or private
networks. Processor 320 also communicates with marketplace store
215 and the marketplace engine 205, to execute control logic and
perform the marketplace process described herein. Additionally,
processor 320 also communicates with marketplace store 215 and the
migration engine 210, to execute control logic and perform the
migration process described above. Other configurations of the
cloud marketplace system 200, associated network connections, and
other hardware and software resources are possible.
[0064] While FIG. 5 illustrates the cloud marketplace system 200 as
a standalone system comprises a combination of hardware and
software, the cloud marketplace system 200 can also be implemented
as a software application or program capable of being executed by a
convention computer platform. Likewise, the cloud marketplace
system 200 can also be implemented as a software module or program
module capable of being incorporated in other software applications
and programs. In either case, the cloud marketplace system 200 can
be implemented in any type of conventional proprietary or
open-source computer language.
[0065] Additionally, as illustrated in FIG. 5, the cloud
marketplace system 200 can be a standalone system capable of being
access by or controlled by a user or initiator of the marketplace
and migration processes. Likewise, the cloud marketplace system 200
can be integrated into one or more of the clouds 102. Additionally,
the cloud marketplace system 200 can be integrated into one or more
of the systems of the clouds 102 such as the cloud management
systems.
[0066] FIG. 6 illustrates a flowchart of processing for multiple
cloud marketplace aggregation, according to various embodiments. In
602, processing can begin. In 604, at least one of a set of
requesting entities can generate a resource request 312. For
example, a resource request 312 can be generated for a set of
messaging, browser, or other applications that a user or resource
wishes to install in or from a cloud. In 606, the resource request
312 can be transmitted to an aggregation engine 360. In 608, the
resource request 312 can be decoded in aggregation engine 360. In
embodiments, for example, a request to install an operating system
in a virtual machine can be decoded to identify a version of
operating system, and minimum necessary processor cycles, memory,
and/or other resources.
[0067] In 610, the aggregation engine 360 can generate and transmit
a set of replicated resource requests 364 to a set of multiple
cloud marketplaces 362. In embodiments, set of multiple cloud
marketplaces 362 can contain multiple marketplace systems 200,
which in embodiments can be of similar or diverse type, capability,
and/or location. In 612, the marketplace systems 200 can of the set
of multiple cloud marketplaces 362 can generate a set of resource
offerings 366, and transmit those offerings to aggregation engine
360. In 614, the aggregation engine 360 can apply selection logic
368 to the set of resource offerings 366 to identify the resources
and marketplace(s) that will be invoked to satisfy the resource
request 312. In embodiments, selection logic 368 can examine set of
resource offerings 366 to select resources, marketplace(s), and/or
cloud(s) based on criteria such as subscription or other cost,
processing performance, service availability under a service level
agreement (SLA), and/or other factors. In embodiments, in addition
to or instead of selection logic 368, a user can supply input to
select from among the set of resource offerings 366.
[0068] In 616, the selected resources can be transmitted from
and/or instantiated via aggregation engine 360 and associated cloud
resources to the one or more requesting entities in set of
requesting entities 308. In 618, the selected marketplace(s),
cloud(s), and/or other resources can be updated, as appropriate,
for example as a result of a change in one or more marketplace
systems 200, and/or receipt of a new or updated resource request
312. In 630, as understood by persons skilled in the art,
processing can repeat, return to a prior processing point, jump to
a further processing point, or end. The foregoing description is
illustrative, and variations in configuration and implementation
may occur to persons skilled in the art. For example, while
embodiments have been described in which a single aggregation
engine 360 supports the resource requests of a set of requesting
entities 308, in embodiments, multiple aggregation engines,
servers, or logic can communicate with the set of requesting
entities 308 to build virtual machines or other objects from
resources produced by the set of multiple cloud marketplaces 362.
Other resources described as singular or integrated can in
embodiments be plural or distributed, and resources described as
multiple or distributed can in embodiments be combined. The scope
of the present teachings is accordingly intended to be limited only
by the following claims.
* * * * *