BACKGROUND
Generally described, computing devices utilize a communication network, or a series of communication networks, to exchange data. Companies and organizations operate computer networks that interconnect a number of computing devices to support operations or provide services to third parties. The computing systems can be located in a single geographic location or located in multiple, distinct geographic locations (e.g., interconnected via private or public communication networks). Specifically, data centers or data processing centers, herein generally referred to as “data centers,” may include a number of interconnected computing systems to provide computing resources to users of the data center. The data centers may be private data centers operated on behalf of an organization or public data centers operated on behalf, or for the benefit, of the general public.
To facilitate increased utilization of data center resources, virtualization technologies allow a single physical computing device to host one or more instances of a virtual machine, which virtual machine instance appears to a user of a data center as an independent computing device. With virtualization, the host computing device can create, maintain, delete, or otherwise manage virtual machines instances in a dynamic manner. In turn, users can request computing resources from the data center, including single computing devices or a configuration of networked computing devices, and be provided with virtual machine instances that provide the requested computing resources.
An instance of a virtual machine may be configured to provide specific functionality. For example, a virtual machine instance may be associated with different combinations of software applications and operating systems or operating system configurations to enable a virtual machine to provide different desired functionalities, or to provide similar functionalities more efficiently. One or more virtual machine instance configurations are often contained within a service image, which a host computing device may execute in order to implement the desired specific functionality of the virtual machine instance.
In one embodiment, the service image, when executed by virtual machine instance, provides a network accessible service (a.k.a. Web service) corresponding to the software applications/configurations included in the service image. A network accessible service provides specific functionality to other applications and computing resources via a network through application programming interfaces (APIs), which APIs can also be considered a network accessible service or Web service. For example, a service image, when executed, may provide a network accessible database or mass storage service. Once a service image is created, it can be provided to users interested in utilizing computing resources available from a data center for specific purposes.
BRIEF DESCRIPTION OF THE DRAWINGS
The foregoing aspects and many of the attendant advantages will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
FIG. 1 is a block diagram depicting an illustrative operating environment in which an electronic service image marketplace enables customers to browse and acquire service images made available in the marketplace by third party providers and the operator of the electronic marketplace;
FIG. 2 is a block diagram depicting a provider computing device submitting a service image for inclusion in the service image marketplace shown in FIG. 1;
FIG. 3 depicts an illustrative user interface displayed on a provider computing device that enables a provider to submit a service image for inclusion in the service image marketplace shown in FIG. 1;
FIG. 4 is a block diagram depicting a customer computing device querying the service image marketplace shown in FIG. 1 for service images of interest;
FIGS. 5A, 5B, and 5C depict illustrative user interfaces displayed on a customer computing device that present information associated with a service image available via the service image marketplace shown in FIG. 1;
FIG. 6 depicts an illustrative user interface displayed on a customer computing device that enables a customer to configure a service image being acquired from the service image marketplace shown in FIG. 1;
FIGS. 7A and 7B are block diagrams depicting the acquisition of a service image by the customer and launching of the acquired service image on a hosted computing environment associated with the service image marketplace shown in FIG. 1;
FIG. 8 depicts an illustrative user interface displayed on a customer computing device that presents details regarding one or more hosted service images acquired by the customer from the service image marketplace shown in FIG. 1; and
FIG. 9 depicts an illustrative user interface displayed on a provider computing device that presents details regarding one or more service images submitted by the provider to the service image marketplace shown in FIG. 1.
DETAILED DESCRIPTION
Generally described, aspects of the present disclosure relate to providing an electronic marketplace for service images. More specifically, an electronic service image marketplace is disclosed that enables customers to browse and acquire a large variety of service images. The service images may be submitted to, and made available from, the electronic service image marketplace, by third party providers or may be submitted to the marketplace by the operator of the marketplace itself. Once acquired through the marketplace, a service image may be launched on a hosted computing environment maintained by the third party provider of the service image or on a hosted computing environment associated with the marketplace.
The electronic service image marketplace provides an environment with which both providers and customers of service images can interact via a network. In one embodiment, a provider may submit a service image to the service image marketplace for inclusion in a service image catalog. The provider may submit additional information corresponding to the service image that would be useful to a customer, such as pricing information, usage conditions, a location of a provider hosted computing environment on which the service image can be hosted, or other information. Customers may browse the service image catalog by interaction with various user interfaces generated by the service image marketplace as described in more detail below. Upon identifying a service image of interest, the customer may view details of each service image in the service image catalog, such as the information submitted by the provider of the service image. In some embodiments, a customer may view further information associated with a service image, such as usage statistics by other marketplace customers of the service image, reviews by other customers, or recommendations for similar or complementary service images. Accordingly, service images may be surfaced to customers in a variety of ways by the electronic service image marketplace, such as by navigation through a browse tree of services organized by function, type, size, etc. or through recommendations, reviews, etc.
Once a customer selects a service image, the customer may purchase or otherwise acquire the service from the service image marketplace. In some embodiments, the customer may be required to submit payment information for the service image prior to launch of the service image. After acquisition of the service image by the customer, the service image may be launched and executed by one or more hosted computing environments. The hosted computing environment may be provided by an operator of the service image marketplace or may be otherwise associated with the electronic service image marketplace. In some embodiments, the third party provider of the acquired service image may provide a hosted computing environment for the service image acquired by the customer via the electronic service image marketplace.
Once the service image is launched and running on a hosted computing environment, the electronic service image marketplace can monitor the usage of functionality or services provided by service image and bill the customer/pay the provider accordingly. Moreover, the electronic service image marketplace may provide the customer with tools to manage, monitor, modify, etc. the service image.
Embodiments discussed below may refer to the users of an electronic marketplace for service images as customers. However, it may be understood that users are not limited to customers but may include owners, administrators, end users and providers of service images purchased from the electronic marketplace. While specific embodiments and example applications of the present disclosure will now be described with reference to the drawings, these embodiments and example applications are intended to illustrate, and not limit, the present disclosure.
FIG. 1 is a block diagram depicting an illustrative operating environment in which an electronic service image marketplace 100 enables customers to browse and acquire service images made available in the marketplace by third party providers or the operator of the electronic marketplace. As illustrated in FIG. 1, the operating environment includes one or more provider computing devices 150 and one or more customer computing devices 140 in communication with an electronic service image marketplace 100 via a network 130. A third party provider, using a provider computing device 150, may submit via the network 130 a service image for a specific type of functionality to the electronic service image marketplace 100. The electronic service image marketplace 100 may then make the submitted service image, as well as other service images submitted to the marketplace, available to customers. Accordingly, a customer, using a computing device 140, may browse the service images available from the electronic service image marketplace 100, acquire a desired service image, and launch the acquired service image in a marketplace hosted computing environment 120 operated, maintained, provided or otherwise associated with the operator of the electronic service image marketplace 100. In some cases, where the acquired service image was submitted to the electronic service image marketplace 100 by a third party provider, the acquired service image may be launched in a provider hosted computing environment 152 that is operated, maintained, provided or otherwise associated with the third party provider. A hosted computing environment may include a collection of rapidly provisioned and released computing resources hosted in connection with the marketplace or a third party provider. The computing resources may include a number of computing, networking and storage devices in communication with one another. In some embodiments, the computing devices may correspond to physical computing devices. In other embodiments, the computing devices may correspond to virtual machine instances implemented by one or more physical computing devices. In still other embodiments, computing devices may correspond to both virtual computing devices and physical computing devices. One example of a hosted computing environment is given in U.S. Pat. No. 7,865,586, issued on Jan. 4, 2011 and entitled “Configuring Communications Between Computing Nodes” which is hereby incorporated by reference in its entirety. A hosted computing environment may also be referred to as a cloud computing environment.
Though described herein with reference to hosted computing environments associated with a provider of a service image and with the electronic service image marketplace 100, in some embodiments, additional hosted computing environments may be utilized. For example, a customer computing device 140 may provide a customer hosted computing environment (not shown), or a third party may provide a third party hosted computing environment (not shown). Any or all of these additional hosted computing environments may be accessible to the electronic service image marketplace 100, and may be utilized to host service images available from the electronic service image marketplace 100. For purposes of brevity, such additional hosted computing environments may also be referred to herein as “provider hosted computing environments.”
The provider computing devices 150 and the customer computing devices 140 may communicate with the electronic service image marketplace 100 via a network 130. A provider computing device 150 or customer computing device 140 may be any computing device, such as a laptop or tablet computer, personal computer, server, personal digital assistant (PDA), hybrid PDA/mobile phone, mobile phone, electronic book reader, set-top box, camera, digital media player, and the like. Those skilled in the art will appreciate that the network 130 may be any wired network, wireless network or combination thereof. In addition, the network 130 may be a personal area network, local area network, wide area network, cable network, satellite network, cellular telephone network, or combination thereof. In the illustrated embodiment, the network 130 is the Internet. Protocols and components for communicating via the Internet or any of the other aforementioned types of communication networks are well known to those skilled in the art of computer communications and thus, need not be described in more detail herein.
In the illustrated embodiment, the electronic service image marketplace 100 is illustrated as a computer environment including several computer systems that are interconnected using one or more networks. More specifically, the service image marketplace may include a marketplace server 112, a usage monitoring server 114, an electronic catalog 116, and a billing server 118. Each of these will be described in more detail below. However, it will be appreciated by those skilled in the art that the electronic service image marketplace 100 could have fewer or greater components than are illustrated in FIG. 1. In addition, the electronic service image marketplace 100 could include various Web services and/or peer-to-peer network configurations. Thus, the depiction of the electronic service image marketplace 100 in FIG. 1 should be taken as illustrative and not limiting to the present disclosure.
The marketplace server 112 facilitates network submission by third party providers, and browsing and acquisition by customers, of service images in the electronic service image marketplace 100. Accordingly, a provider, utilizing a provider computing device 150, may submit on or more service images to the electronic service image marketplace 100 via the marketplace server 112. The submitted service images may then be included in an electronic catalog 116. The process by which a provider, utilizing a provider computing device 150, submits a service image to the electronic service image marketplace 100 will be described in more detail with respect to FIGS. 2 and 3, below.
The electronic catalog 116 includes information on service images available from a plurality of providers and on service images made available by the operator of the electronic service image marketplace 100. Accordingly, the marketplace server 112 may obtain service image information for service images offered by a plurality of providers and the marketplace and make the service images available to a customer from a single network resource, such as a Web site. A customer may then acquire the service image from the service image marketplace and launch the service image in a hosted computing environment (e.g., the marketplace hosted computing environment 120 or a provider hosted computing environment 152) in a single interaction or order placed with the service image marketplace. This eliminates the need for the customer to develop his or her own service image; or research, search or otherwise investigate multiple different providers or other sources for the service image. The electronic catalog may be a catalog containing information regarding both items (such as goods and services) and service images, or may be separate catalogs, with one catalog containing information regarding items and the other catalog containing information regarding services images, without departing from the scope of the present disclosure.
Illustratively, marketplace server 112 may generate one or more user interfaces through which a customer, utilizing a customer computing device 140, may browse service images, submit queries for matching service images and view information and details regarding specific service images. An illustrative process by which a customer computing device 140 may query the electronic service image marketplace 100, and by which the marketplace server 112 generates a user interface, will be described in more detail with respect to FIGS. 4-5B, below.
After the customer selects a desired service image from the electronic service image marketplace 100, the marketplace server 112 may facilitate the configuration and acquisition of the service image and cause the launching of the service image on a hosted computing environment. In this regard, the marketplace server 112 may receive payment information from the customer computing device 140, as well as information specifying how the service image should be implemented by a hosted computing environment. In some embodiments, the customer may select a specific hosted computing environment to host the selected service image. The specific hosted computing environment may correspond, for example, to the marketplace hosted computing environment 120 associated with the electronic service image marketplace 100, or to a provider hosted computing environment 152 which is associated with the provider of the service image.
Once the service image is launched and running on a hosted computing environment, the electronic service image marketplace 100 can monitor the usage of functionality or services provided by service image and bill the customer/pay the provider accordingly via the usage monitoring server 114 and the billing server 118, respectively. Moreover, the service image marketplace may provide the customer with tools to manage, monitor, modify, etc. the service image. In the illustrated example, the usage monitoring server 114 is in communication with the marketplace hosted computing environment 120, and is operable to track a usage of the functionality (e.g., Web service) provided by the executed service image. This may be required, for example, where pricing of the service image is dependent on usage of the Web services produced by the service image when executed.
The billing server 118, on the other hand, may be provided to process payments from customers and, in some embodiments, provide payment to the providers of acquired service images. The billing server 118 may receive and provide payment information via interaction with the marketplace server 112. In some embodiments, the billing server 118 may alternatively receive and provide payment information via other processes, such as via an additional server, via telephonic interaction, or other mechanisms.
With reference to FIG. 2, an illustrative interaction for allowing a provider computing device 150 to submit a service image to the electronic service image marketplace 100 will be described. As depicted in FIG. 2, the provider computing device 150 submits a service image and information corresponding to that service image to the electronic service image marketplace 100 where the submission is processed by the marketplace server 112. The provider, utilizing the provider computing device 150, may submit information such as the name of a service image, the entity which generated the service image, software contained within the service image, or a description of the service image or software contained therein. The entity or provider may submit pricing information corresponding to the service image or use of the service image. Such pricing information may, by way of example, correspond to a one-time price for acquisition of the service image, to a monthly subscription fee associated with the service image, or to a usage fee associated with a time period of use of the service image. For example, the submitted pricing information may reflect a monthly subscription fee for acquisition of the service image in addition to an hourly usage fee for use of the service image. A provider computing device 150 may optionally submit usage restrictions associated with a provided service image, such as required acceptance of an end user license agreement (“EULA”), maximum usage restrictions, or type of usage restrictions, such as limitations allowing only non-commercial use.
Subsequent to submission of the service image and any corresponding information received from the provider computing device 150, the marketplace server 112 may interact with the electronic catalog 116 in order to store the service image and the corresponding information. The electronic catalog 116 may be implemented as a comprehensive catalog of service images that are available to a customer via the electronic service image marketplace 100. Though depicted here as a single service image catalog, the marketplace server 112 may interact with a number of distinct service image catalogs in order to store submitted service images and corresponding information. In one embodiment, the electronic catalog 116 is a conventional database stored in one or more memory storage devices. In other embodiments the electronic catalog 116 is associated with a catalog server (not shown) that is responsible for maintaining the comprehensive catalog stored therein. The electronic catalog 116 and/or associated catalog server may be in communication with other servers and databases also storing catalog information for service images available via the electronic service image marketplace 100. For example, such servers and databases may be operated by different providers and thus, may include various catalog information for service images offered by those providers.
In some embodiments, submission of a service image may not necessarily result in inclusion of the service image in the electronic catalog 116. For example, the electronic service image marketplace 100 may have automated or manual oversight routines for reviewing a service image before inclusion into the electronic catalog 116. Such a review of a service image may result in further communication between the electronic service image marketplace 100 and the provider (not shown) prior to adding the service image to the electronic catalog 116, or may result in not including the service image in the electronic catalog 116.
Though described above with reference to a service image, in some embodiments, the provider may, instead of providing a service image, provide one or more service image components. Such a service image component may correspond to, for example, an application that may be contained within a service image. In these embodiments, service image components may be stored within the electronic catalog 116, and selectable by customers of the electronic service image marketplace 100 for purchase. The electronic service image marketplace 100 may be configured to create a service image in response to a selection to one or more service image components by a customer.
With reference to FIG. 3, one example of a user interface 300 for provider submission of service images is displayed. As shown in FIG. 3, the user interface 300 enables a provider utilizing a provider computing device, such as provider computing device 150 of FIG. 1, to submit a service image to the electronic service image marketplace 100. Illustratively, the user interface 300 may be generated by the marketplace server 112 of the electronic service image marketplace 100 and presented on the provider computing device 150 by an application, such as a browser application, on the provider computing device 150. In this example, the user interface 300 contains a title reference 302 to the electronic service image marketplace 100, i.e., the “Hosted Web Services Catalog,” as well as a salutation 304 to the provider currently visiting the electronic service image marketplace 100. In the illustrated example, the provider is identified as “Paul Provider.” The user interface 300 further contains a navigation panel 310, which directs the provider to various other features offered by the electronic service image marketplace 100. Illustratively, units of text within the navigation panel 310 may correspond to interactive links, which modify or change the user interface when selected. In the current example, Paul Provider, has selected link 312, “Upload a Service Image.” Based on this selection, the marketplace server 112 has returned the content for user interface 300.
Through the user interface 300 the provider may submit information associated with a service image to the electronic service image marketplace 100. The provider, utilizing a provider computing device 150 may submit, via input box 320, an identifier of the service image to be used by the electronic service image marketplace 100. This may be the name displayed to customers of the electronic service image marketplace 100 when they view, browse, or search the electronic service image marketplace 100. The provider may submit additional information, such as a file location (e.g., a file name or address), and pricing information via inputs 324-330. Input box 324 allows the provider to specify the device image that is to be submitted, and that may thereafter be hosted by a hosted computing environment on behalf of a customer. In the illustrated example, the service image location is a location on the provider computing device 150, as is displayed in FIG. 3. In other embodiments, the service image file may be located on another computing device, such as a computing device within a provider hosted computing environment 152, or a computing device within the marketplace hosted computing environment 120 associated with the electronic service image marketplace 100.
In some embodiments, the electronic service image marketplace 100 may create a service image on behalf of the provider. For example, the provider may, instead of providing a location of a service image via input box 324, specify the location of a computing device. The electronic service image marketplace 100 may then locate the specified computing device, and create a service image reflecting the current software running on and/or current configuration of the computing device. Such functionality may be helpful in situations where the provider wishes to provide a service image of the current state of a computing device which exists within the marketplace hosted computing environment 120.
In the illustrated example, input boxes 326-330 enable a provider to specify pricing information associated with the submitted service image. For example, input box 326 enables the provider to specify a pricing structure associated with a service image such as a pricing structure requiring a monthly subscription rate as well as an hourly usage fee. However, as described above, other or additional pricing structures may be used. By way of non-limiting example, a pricing structure may correspond to a one-time fee, a subscription of any duration of time (e.g., years, months, weeks, etc.) that is required regardless of usage, a usage fee charged only for the time a service image is actually used, a per-use or per-access fee such as a fee associated with every time a service image is loaded, or any other pricing structure. In some embodiments, a service image may be provided free of charge. In other embodiments, pricing information may be dependent on the use of a service image. For example, a higher price may be collected for use of a service image in a commercial environment than would be collected for use of the same service image in a non-commercial or educational environment. As another example, pricing information may specify tiered pricing, such that heavy users of a service image may be charged a lower per-use fee. In still more embodiments, a provider may negotiate individual pricing information to be used for specific customers of a service image or service images. For example, individual contracts may exist or be created between a provider and each customer. One skilled in the art will appreciate that various implementations may accommodate such individualized contracts. For example, the provider may modify pricing information on a per customer basis (such as allowing a specified customer to access unlimited instances without fee).
A provider may further specify parameters for a pricing structure via input boxes 328 and 330, such as the amount of the monthly subscription rate and the hourly usage fee. In some embodiments, input boxes 328 and 330 may only appear when the input of input box 326 indicates they are required. Where input box 326 indicates that different or additional pricing information is required, alternate input boxes may appear. In some embodiments, one or more of the above inputs may not be required. In other embodiments, additional input information may be provided. For example, a provider may specify a graphic which should be associated with the provided service image. After all necessary information has been input, submission may be completed by selecting the input control 332. Accordingly, the provider may activate the input control 332 to cause the provider computing device 150 to transmit the service image and corresponding information to the marketplace server 112. As discussed above, the marketplace server 112 may then submit the received information to the electronic catalog 116.
With reference to FIG. 4, FIG. 4 is a block diagram depicting a customer computing device 140 querying the service image marketplace shown in FIG. 1 for service images of interest. As depicted in FIG. 4, the customer computing device 140, on behalf of a customer, submits a query for service images to the electronic service image marketplace 100 that is processed by the marketplace server 112. Illustratively, such a query could be submitted via a user interface, such as via an application on the customer computing device 140 which interacts with the marketplace server 112. The search query may correspond to any aspect of a desired service image, such as the functionality of the service image, the name of the service image, the name of the service image provider, pricing details of the service image, platforms on which the service image may be executed, or any other information that could be related to a service image. Submission and handling of search queries is well known in the art, and therefore will not be discussed in more detail herein.
With continued reference to FIG. 4, after submission of a search query by the customer computing device 140, the marketplace server 112 submits a request to the electronic catalog 116 for service images matching the customer submitted query. In response, the electronic catalog 116 retrieves and returns information corresponding to service images which match the customer submitted query. Details of these matching service images are then transmitted to the customer computing device 140. A customer computing device 140 may select any returned service image to view more details about the selected service image.
FIGS. 5A and 5B depict an illustrative user interface 500 displayed on a customer computing device that presents information associated with a service image available via the electronic service image marketplace 100. In one embodiment, user interface 500 is generated by marketplace server 112 as a result of navigation by the customer or as a result of selection of a search result returned by the marketplace server 112. While depicted in two figures, one skilled in the art will appreciate that the user interface 500 may be a single user interface and that the customer may view different portions of the interface by use of an interface input, such as scroll bar 506. As shown in FIG. 5A, the user interface 300 provides information retrieved from the electronic service image marketplace 100, i.e., the Hosted Web Service Catalog” 302 to “Chris Customer” 304, an illustrative customer accessing the “Hosted Web Services Catalog.” Because the customer is viewing details regarding a specific offered service image, and may wish to browse to other service images, navigation pane 510 is displayed. Navigation pane 510 contains links that enable a customer to browse and select other service images available via the service images marketplace 100. Currently, the user interface 500 depicts information for the service image “Paul's Database,” which corresponds to the service image uploaded by user Paul Provider, discussed previously with reference to FIG. 3. Display features 512-526 display information corresponding to the service image. Display feature 512, for example, is a graphic associated with the service image. The graphic may correspond to a logo associated with the service image or with the service image provider. Display features 514 and 516 depict the name of the service image and the provider of the service image, respectively. Display features 520-522 depict pricing information associated with the service image, as discussed previously with respect to FIG. 3. Display feature 524 depicts reviews given to the service image by users of the “Hosted Web Services Catalog.” As depicted, display feature 524 reflects that “Paul's Database” has been given, on average, a three star rating by users of the “Hosted Web Services Catalog.” As will be appreciated by those skilled in the art, various other methods of displaying a rating of a service image may be employed. Display feature 526 depicts a version number of the service image; in the current example, version 1.0. In some embodiments, display feature 526 may be selectable to view alternative versions of the selected service image that are available. This may be desirable, for example, where previous versions have different desired characteristics, such as different pricings, features, compatibility, or ratings. Input box 530 may be utilized by the customer to specify a number of instances of the selected service image that the customer desires. Generally speaking, an instance refers to an individual computing device—virtual or physical—which has executed, loaded, or launched the selected service image. A customer may wish to specify multiple instances, for example, where the customer wishes to distribute processing or load access across multiple instances. In other examples, multiple instances may be functional to interact, or to provide different functionality via the same service image. The number of instances in input box 530 may optionally be associated with a default value, such that the customer is not required to select a number of instances. After inputting the desired number of instances (if necessary), the customer may activate input button 532 to further configure and launch the viewed service image. One example of a user interface used to further configure and launch a service image will be discussed with respect to FIG. 6, below.
With reference to FIG. 5B, an additional portion of user interface 500 regarding the “Paul's Database” service image is displayed. As discussed above, the customer may view this additional portion of the user interface by interacting with the user interface 500, such as by moving the scroll bar 506. FIG. 5B depicts additional information regarding the “Paul's Database” service image via display features 534-540. Display feature 534 depicts information regarding other service images which are similar in some fashion to “Paul's Database.” In the current example, “Other DB” is an alternative service image available via the electronic service image marketplace 100 which competes with and offers similar functionality to “Paul's Database.” Such service images may be identified, for example, by analyzing which database customers ultimately purchase after viewing a service image, or by categorizing service images and displaying images within the same category. Various other mechanisms by which similar service images may be identified are well known in the art. Similar to display feature 534, display feature 536 displays service images which are commonly purchased in conjunction with “Paul's Database.” In this example, customers who launched at least one instance of “Paul's Database” have frequently also launched an instance of the “Web Server” service image. Both display features 534 and 536 have additional information regarding their relevant service images, such as graphical and pricing information. Input buttons may be provided along with display features 534 and 536 to allow a customer to select the relevant service image for configuration and launch.
Illustrative display features 538 and 540 depict still more information regarding the “Paul's Database” service image. Display feature 538 depicts statistical information related to current or previously launched instances of “Paul's Database,” including the number of installations of the service image which have occurred, the average uptime of the installed service images (which may correspond with a reliability of the service image), the typical type of computing device on which the service image is launched, and the typical number of instances of the service image which are launched by a customer. Display feature 540 depicts individual reviews generated by users of the service image marketplace regarding “Paul's Database.” Each review may have information such as a rating of the service image on a given scale, and an authored comment portion regarding the service image. In some embodiments, additional or alternative display features may be depicted regarding a service image.
With reference to FIG. 5C, an additional portion of user interface 500 regarding the “Paul's Database” service image is displayed. As discussed above, the customer may view this additional portion of the user interface by interacting with user interface 500, such as by moving the scroll bar 506.
FIG. 5C depicts additional information regarding the“Paul's Database” service image by way of display features 542 and 544. Display feature 544 depicts information regarding options available to customers for executing the displayed service image. In the current example, display feature 544 reflects other versions of “Paul's Database” available, the locations of hosted computing environments which may execute “Paul's Database,” and types of computing devices available to execute “Paul's Database.” As shown by display feature 544, each configuration option is associated with a modification of the pricing of the service image. Display feature 544 reflects sample configurations for the execution of the service image provided by the electronic service image marketplace 100. As shown by display feature 544, two configurations (reflecting the various options shown by display feature 542) are shown, each resulting in a different estimated cost to the customer. Illustratively, the cost associated with average use may be determined based on the usage of the service image by other customers, while the “24/7” cost may be determined by calculating the cost to execute the service image continuously for a month. In this illustrative example, the configurations reflect a single instance of a service image. However, some configurations may reflect multiple instances, or allow a customer to specify multiple instances of a configuration for launch. Additionally, the configuration options displayed may be customized based on customer information of the present customer. For example, if Chris Customer is accessing the electronic service image marketplace 100 from the western United States, the “Hosted Web Services Catalog—US (West)” option may be pre-selected for display feature 544. Conversely, if Chris accesses the electronic service image marketplace 100 from the United Kingdom, the option for hosting on “Hosted Web Service Catalog—UK” may be pre-selected.
Though described above with reference to a service image, in some embodiments, the user interface 500 may describe details regarding service image components. These components may correspond to applications which can be included within a customized service image. In these embodiments, the electronic service image marketplace 100 may be configured to receive, from a customer, a selection of one or more service image components, and create a service image containing the selected components for execution on a selected hosted computing environment.
With reference to FIG. 6, an illustrative user interface 600 displayed on a customer computing device that enables a customer to configure a service image being acquired from the electronic service image marketplace 100 is depicted. The user interface 600 may enable a customer to configure, subscribe to, and launch a service image. The depicted user interface 600 may be displayed, for example, by selecting the input button 532 of FIG. 5A, discussed above. As discussed above, the user interface 600 gives access to the electronic service image marketplace 100 known as the “Hosted Web Services Catalog” 302. The current user is Chris Customer 304. Display feature 602 reflects the requested service image, as well as the number of instances desired. As shown in FIG. 6, display feature 602 reflects that Chris Customer has requested that one instance of the service image “Paul's Database” be launched. Input boxes 604-608 depict various inputs through which a customer may configure the service image that is to be launched. Input box 604, for example, reflects that the customer may select a hosted computing environment on which the service image is to be launched and hosted. A hosted computing environment can correspond to a marketplace hosted computing environment 120 associated with the electronic service image marketplace 100, with a hosted computing environment provided by the provider of the service image, such as provider hosted computing environment 152, or with another hosted computing environment accessible to the electronic service image marketplace 100. In the current user interface, input box 604 reflects that Chris Customer has selected that “Paul's Database” be launched on the hosted computing environment associated with the “Hosted Web Services Catalog” and located in the western United States. For the purposes of this example, this hosted computing environment corresponds to marketplace hosted computing environment 120 associated with the electronic service image marketplace 100.
Input box 606 enables the customer to select a version of the service image that is to be launched. Multiple versions of the same service image may be provided for various reasons, such as cost, reliability, or interoperability. In some embodiments, only a single version of a service image may be available. In such embodiments, the customer may not be able to alter input box 606, or input box 606 may not be displayed. Input box 608 enables the customer to configure and select the type of instance on which the service image is to be launched. In the current example, the selected hosting environment, “Hosted Web Services Catalog—US (WEST),” allows both large and small instances to be launched. For the purposes of example, a large instance may correspond to a computing device or virtual machine with more processing power, more random access memory, or more data storage. A small instance may, conversely, have a smaller amount of processing power, memory, or storage. As such, a small instance may correspond to a lower hourly usage fee than the large instance. As will be appreciated by one skilled in the art, a variety of types of instances may be presented to the user. In some embodiments, only a single instance type may be available, and the user may not be presented with a selection. In still more embodiments, instance types may vary based on the selected hosted computing environment, and as such, the input box 608 may be substituted for alternative input boxes reflecting the instance types available on a selected hosted computing environment.
With continued reference to FIG. 6, display feature 610 reflects pricing information associated with the currently selected configuration. In the current example, a single instance of the service image “Paul's Database” is associated with a monthly subscription fee of fifty dollars (as discussed with respect to FIG. 3, above). This fifty dollar monthly subscription rate is reflected by display feature 612. Illustratively, a monthly subscription rate may be assessed for each month that instances exist, regardless of usage of that instance. In addition, a single instance of the service image “Paul's Database” is further associated with an hourly usage cost of eighty five cents per hour. This hourly usage cost is reflected by display feature 618. In addition to pricing information associated with the service image, the electronic service image marketplace 100 may also assess fees related to the instance type a customer has selected. As discussed above, Chris Customer has selected a large instance on which to load the service image. In the current example, a large instance is associated with a fee rate of fifteen cents per hour of use, and no subscription fee. This hourly rate is reflected in display feature 616. The total hourly rate associated with the customer selected configuration is then depicted in display feature 614. In the current example, one instance of “Paul's Database” running on a large instance of the hosting environment “Hosted Web Services Catalog—US (West)” is one dollar per hour. As discussed above, various pricing information may be associated with various service images, and as such, additional or alternate display features may be depicted in order to reflect the pricing information of each service image and configuration. After configuring the parameters for launching an instance of the service image via input boxes 604-608, the customer may activate input button 620 to subscribe to and launch the selected instance. The process by which a service image is subscribed to and launched is discussed in more detail below.
With respect to FIGS. 7A and 7B, illustrative interactions for acquiring and launching a service image will be described. With respect to FIG. 7A, an illustrative interaction is shown for acquiring and launching a service image on a hosted computing environment 112 associated with a electronic service image marketplace 100 is depicted. With respect to FIG. 7B, an illustrative interaction to acquire and launch the same service image is depicted, however, the service image is to be launched on a provider hosted computing environment 152. As the illustrative interactions depict the acquisition and launch the same service image via the same service image retail environment 110, reference will be made generally to both figures, with specific references to each as required when the depicted interactions differ.
FIGS. 7A and 7B are block diagrams depicting the acquisition of a service image by the customer and launching of the acquired service image on a hosted computing environment associated with the electronic service image marketplace 100. In this regard, a customer, utilizing a customer computing device 140, may request to acquire a service image the customer has found and selected from the electronic service image marketplace 100. The request may be created, for example, by selecting input button 620 of FIG. 6, described above and processed by the Web service 112 of the service image retail environment 110. After receiving the request to acquire access to the service image, the marketplace server 112 may transmit a command which causes the launch of the service image on a hosted computing environment. For the purposes of illustration, this command is depicted as transmitted from the marketplace server 112. As will be appreciated by one skilled in the art, one or more intermediary servers in the electronic service image marketplace 100 may be required in order to transmit the command to launch the service image. Further, in some embodiments, the marketplace server 112 may interact with the electronic catalog 116 to acquire the selected service image before transmitted the command to launch. In these embodiments, the marketplace server 112 may further transmit the selected service image to the selected hosted computing environment.
With respect to FIG. 7A, the selected hosted computing environment is the marketplace hosted computing environment 120. With respect to FIG. 7B, the selected hosted computing environment is a provider computing environment 152, which has been made available for hosting the service image by the provider of the service image. As will be appreciated by one skilled in the art, the command transmitted may vary depending on the destination hosted computing environment. For example, where the hosted computing environment is associated with the electronic service image marketplace 100, the commands may be known to the service image retail environment 110. With respect to a provider hosted computing environment 152, a provider may be required to register the provider hosted computing environment 152 with the electronic service image marketplace 100, such as by specifying the location of the provider hosted computing environment 152 and any commands necessary to launch service images on the provider hosted computing environment 152. In some embodiments, the selected hosted computing environment may transmit a confirmation to the service image retail environment 110 that the service image has been launched. Subsequent to launching the customer selected service image, the marketplace server 112 transmits a confirmation to the customer computing device 140, as well as information regarding the hosted service image. Such information may include the location of the computing device hosting the service image and any access information required to access the computing device hosting the service image. Subsequent to receiving confirmation of launch and relevant hosting information, the customer computing device 140 may access the computing device hosting the service image, and therefore may access any Web services implemented by the computing device hosting the service image. With respect to FIG. 7A, the customer computing device 140 may communicate with the marketplace hosted computing environment 120 in order to access the Web services. With respect to FIG. 7B, the customer computing device 140 may communicate with the provider hosted computing environment 152.
Though not depicted in FIGS. 7A and 7B, after the launch of the selected service image, the usage monitoring server 114 may communicate with the selected hosted computing environment to monitor usage of the computing device hosting the service image. As discussed above, the customer may access the Web services implemented by the computing device hosting the service image, and may allow others to access the Web services. The usage monitoring server 114 may monitor access to the Web services by both the acquiring customer and by other users. In some embodiments, the usage monitoring server 114 may be operable to differentiate between accesses by different users. The billing server 118 may utilize information provided by the usage monitoring server 114, as well as information from the marketplace server 112 or the electronic catalog 116, to create billing information for the customer, as well as payment information for the provider generated from the customer's use. The billing server may further process payments from the customer, and provide payment to the provider of the service image.
With reference to FIG. 8, one example of a user interface 800 for providing information regarding acquired service images is displayed. As shown in FIG. 8, the user interface 800 enables a customer to receive information regarding services images acquired via the electronic service image marketplace 100, i.e., the “Hosted Web Services Catalog,” 302. The current user of the “Hosted Web Services Catalog” is Chris Customer 304. A navigation panel 310 directs the customer to various other features offered by the electronic service image marketplace 100. In this illustrative example, Chris Customer has selected the “My Instances” link 802. The resultant user interface 800 gives Chris Customer access to information regarding instances of service images launched via the electronic service image marketplace 100. Display features 804A and 804B reflect the titles of service images which Chris Customer has previously acquired. In this example, Chris Customer has acquired service images titled both “Paul's Database” and “Web Server.” For the purposes of illustration, only the instance reflected by display feature 804A will be discussed further. It will be appreciated by one skilled in the art that information regarding multiple additional service image titles may be displayed via the same or a similar user interface. Display features 806 and 808 reflect the current status of instances of the “Paul's Database” service image. As shown in display feature 806, one instance of the service image is currently “active,” or being executed by a computing device within the selected hosted computing environment. Display feature 808 reflects that zero instances are currently inactive; having been created but not currently being executed by a computing device. In some embodiments, a hosted computing environment may be operable to load and unload instances of a service image as usage of the service image is needed. This may be desirable, for example, where an hourly fee is assessed for use of a service image. In this manner, a service may be made inactive, and the hourly fee would not be assessed during this period. Function links 812-816 enable a customer to modify the configuration of an acquired service image. Link 812 may be selected by a customer to create an additional instance of the service image to which the link 812 corresponds. In the current example, Chris Customer can select link 812 in order to create a new instance of the service image “Paul's Database.” Selecting the link may lead to a user interface which allows configuring the new instance. One example of such a user interface is discussed above with respect to FIG. 6. In some embodiments, the user interface that is displayed for acquisition of a new service image may differ from the user interface displayed when creating a new instance of an already acquired service image. For example, a subscription fee may not be assessed when adding a new instance of an already acquired service image. Function link 814 enables a customer to contact the provider of the service image. Such contact may be facilitated by sending a message through the electronic service image marketplace 100 or by sending a message outside of the electronic service image marketplace 100, such as by electronic mail or posting to an external network accessible site associated with the provider. In some embodiments, the provider of a service image may specify how they wish to be contacted, and the function link 814 may implement functionality corresponding to the provider's specification. Function link 816 may be selected by a customer in order to cancel acquisition of a service image. Illustratively, this function may serve to inactivate or remove any instances of the service image. In some embodiments, this function may not be available to a customer unless all currently active instances are inactivated.
In the current example, each instance of a service image is identified by a unique instance identifier 810. These instance identifiers may be unique across all instances associated with a customer, across all instances hosted by a selected hosted computing environment, or across all instances launched via the service image marketplace. Function links 818 and 820 enable a customer to manage or access a specific instance of a service image. In the current example, function link 818 enables Chris Customer to manage instance “0000001” 810. Link 818 is selectable by Chris Customer to display management functions associated with the instance. For example, Chris Customer may activate or deactivate an instance of a service image, modify the type of computing device which is hosting the service image, or change other functions or features associated with the instance. Chris Customer can select link 820 in order to access the corresponding instance. In some embodiments, this access may be granted via an interface which allows API calls to be made to the instance. In other embodiments, a command terminal interface or graphical user interface may be provided in order to access the instance. One skilled in the art will appreciate that access to an instance of a hosted service image may be given in various additional ways. Display feature 822 depicts the current charges associated with usage of the service image. In the current example, Chris Customer has been assessed fees of $115.25 for use of the service image “Paul's Database.” These charges are reflective of all instances of the associated service image. In some embodiments, charges may reflect only fees associated with a particular instance of a service image (such that each instance displays individual charges). In still more embodiments, charges may reflect fees associated with all service images acquired by a customer. Chris Customer may select function link 824 to view details associated with the current charges, such as a detailed billing report. Such a detailed report may include, for example, timing of usage associated with the charges or assessed subscription fees.
With reference to FIG. 9, an illustrative user interface 900 displayed on a customer computing device and detailing information regarding provided service images is depicted. As shown in FIG. 9, the user interface 900 enables a provider to receive information regarding service images provided to the electronic service image marketplace 100, i.e., the “Hosted Web Services Catalog”. The current user of the “Hosted Web Services Catalog” is Paul Provider 304. As discussed above with respect to FIG. 3, Paul Provider has provided the service image “Paul's Database” to the electronic service image marketplace 100. To reflect that Paul has provided this service image, the navigation panel 310 now displays a link 902 under the heading “My Images” which is selectable by a customer to view information about the provided service image. The user interface 900 is reflective of Paul Provider's selection of link 902. Display features 903-914 depict information regarding the corresponding service image. Display feature 903 displays the title of the service image. Display feature 904 reflects the current number of customers which have acquired the instance via the electronic service image marketplace 100, while display feature 906 depicts the number of hours the service image has been used for the current month. Display feature 908 depicts an estimated number of total hours the service image will be used during the month, based on the current usage. Display feature 910 depicts the hourly rate associated with usage of the service image, as set by the Paul Provider. Display features 912 and 914 reflect both current and estimated monthly accruals associated with usage of the service image by customers. In some embodiments, accruals due to the provider for use of a service image may be used to offset amounts owed to the electronic service image marketplace 100 by the provider. For example, Paul Provider may also be a customer of the service image marketplace, and therefore have fees or charges assessed based on usage of the electronic service image marketplace 100. Input button 916 is selectable by the provider in order to modify options associated with a service image. For example, Paul Provider may modify the hourly rate, subscription fee, or other options associated with “Paul's Database.”
All of the processes described herein may be embodied in, and fully automated via, software code modules executed by one or more general purpose computers or processors. The code modules may be stored in any type of computer-readable medium or other computer storage device. Some or all the methods may alternatively be embodied in specialized computer hardware. In addition, the components referred to herein may be implemented in hardware, software, firmware or a combination thereof.
Conditional language such as, among others, “can,” “could,” “might” or “may,” unless specifically stated otherwise, are otherwise understood within the context as used in general to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
Conjunctive language such as the phrase “at least one of X, Y and Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to convey that an item, term, etc. may be either X, Y or Z. Thus, such conjunctive language is not generally intended to imply that certain embodiments require at least one of X, at least one of Y and at least one of Z to each be present.
Any process descriptions, elements or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or elements in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown, or discussed, including substantially concurrently or in reverse order, depending on the functionality involved as would be understood by those skilled in the art.
It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.
Patent Application
20190228445
