Cloud services system

A cloud services system includes an access services layer, a cloud service manager, and a service platform layer. The access services layer provides front-end functionality for users and service providers to order and manage cloud services, including software applications provided for use by the users. The cloud manager exposes services provided by the cloud services system to the users, and orchestrates delivery of the services and provisioning of resources for the services. The service platform layer activates virtual machines and virtual desktops to provide the services.

BACKGROUND

Cloud computing typically involves using remote computing resources on a pay-per-use basis, where the remote computing resources may be used alone or in conjunction with internal computing resources. For example, processing resources and storage resources of a cloud service provider, such as Amazon Web Services, Microsoft Azure, or Rackspace Cloud Servers, can be requested and used on-demand in a scalable fashion. Cloud computing can be used to provide applications and information to end user devices, such as laptops, personal computers, thin clients, mobile devices, etc. Cloud computing can be used for applications with varying or unpredictable demand like year-end financials or tax-return preparation. Additionally, computationally-intensive processing, such as Monte Carlo simulations or protein folding, can be performed using cloud computing resources.

Given the variation in applications, variations in demand, variations in hosting platforms, and variations in end user devices, it can be difficult for a service provider to set up and implement cloud computing services. A cloud service provider should have skills and resources to provision (e.g., to define, make ready for use, setup, etc.), use and manage computing resources and applications. However, in many instances, a service provider planning to set up cloud services for the first time may lack familiarity with the provisioning and management of resources for cloud services. Also, the service provider may have a limited budget for the provisioning. As a result, it can be difficult, time consuming and cost prohibitive for a service provider to set up and provide cloud services.

SUMMARY

According to an embodiment, a cloud services system includes an access services layer, a cloud service manager, and a service platform layer. The access services layer provides front-end functionality for users and service providers to order and manage cloud services, including software applications provided for use by the users. The cloud manager exposes services provided by the cloud services system to the users, and orchestrates delivery of the services and provisioning of resources for the services. The service platform layer interacts with infrastructure in order to activate virtual machines and virtual desktops to provide the services.

The cloud services system may be implemented on a computer platform including a data storage and a processor. Methods may be performed by the cloud services system to provide cloud services to users. The methods may be embodied as machine readable instructions stored on a non-transitory computer readable medium and executable by a processor.

DETAILED DESCRIPTION

According to an embodiment, a cloud services system is provided that may be implemented by a service provider or another entity. In one example, the cloud services system may be implemented by a telecommunications provider that may have the “pipes” for providing cloud services. “Pipes” includes the network infrastructure for providing the cloud services. The cloud services system may be implemented by entities other than a telecommunications provider.

FIG. 1illustrates a system architecture for a cloud services system100, according to an embodiment. The architecture includes software components110and hardware components150. The software components110may include an access services layer120, a cloud service manager130and a service platform layer140.

The access services layer120provides the front-end functionality for users and service providers. The access services layer120may include a commercial portal121, a user dashboard122, an administrator portal123, user console124and cloud designer125.FIGS. 2A-Cshow aspects of the commercial portal121, the user dashboard122and the administrator portal123. The commercial portal121, the user dashboard122and the administrator portal123may include a graphical user interface (GUI) that allows users to view and enter information.FIG. 2Ashows some functions of the commercial portal121. The commercial portal121, for example, allows users of the cloud services system100to view service catalogs, perform self-ordering, receive quotations, request submissions and view invoice. The commercial portal121also provides order status tracking, an activated service view and functions for change request management. The commercial portal121may be used by large enterprises and small and medium enterprises or other types of users to access these functions provided by the cloud services system100. The commercial portal121could be used for either internal (private) cloud or public cloud services.

FIG. 2Bshows some functions of the user dashboard122. The user dashboard122, for example, allows the user to access service details, manage orders for cloud services, open and review ticket status, and review customer invoicing. The user dashboard122may be used by end user consumers, small businesses or other entities to perform these actions.

FIG. 2Cshows some functions of the administrator portal123. The administrator portal123may be used by the service provider implementing the cloud services system100. The administrator portal123, for example, allows an administrator or other user with appropriate access privileges to monitor and manage services, and perform trouble shooting. The administrator, via the administrator portal123, may monitor and manage services, which may include monitoring orders and evaluating technical feasibility. The administrator portal123also allows the administrator to view and manage service configurations and usage.

FIGS. 2D-Gshow examples of screenshots that may be generated via the commercial portal121, the user dashboard122, and/or the administrator portal123.FIG. 2Dshows a screen shot of service board and modifying resources for ordered services.FIG. 2Dalso shows screen shots of usage information for resources.FIG. 2Eshows screenshots for identifying resources for designing the cloud services system and for designing cloud services to be administered by the cloud services system. The architecture design screenshot shows selecting servers, virtual servers and virtual desktops to provide cloud services. The service configuration screenshots show options for creating cloud services. Generally, the cloud design screenshots show that users can order and manage complex infrastructure architecture (virtual data center) or an administrator can create, validate and deliver custom services for an “ad hoc” initiative. The user console screenshots generally show that a user may manage its services through self-management interfaces with functionalities made available through the access services layer120.

The cloud service manager130shown inFIG. 1exposes the services provided by the cloud services system100to the users, and orchestrates service delivery, technical provisioning and other management functions. The cloud service manager130may include a common services integration layer131, a core132, and a service platform integration layer133. The common services integration layer131, the core132, and the service platform integration layer133are further described with respect toFIGS. 3A-C.

FIG. 3Ashows the common services integration layer131integrating the functions of the cloud service manager130with the service provider and the user applications. For example, the common services integration layer131may comprise a service bus to provide services to external applications, which may include applications of the user and applications of the service provider.FIG. 3Ashows the service bus connecting functions and an integrated repository of the cloud service manager130with user applications and service provider applications. For example, the functions of the cloud service manager130may include orchestration of services, access services, metering, and information technology (IT) service management integration. The service bus connects the functions of the cloud service manager130to an IT service management application of the service provider and a customer resource management and billing application of the service provider. The service bus also connects the functions with the enterprise applications of the user.

The integrated repository shown inFIG. 3Amay include a central data repository containing a commercial and technical service catalog and hierarchy structure, service order information including service order data, progress status and service composition, and service configuration information including service configurations, usage and related open tickets for services.

The IT service management integration shown inFIG. 3Amay include an application program interface integrating the IT service management application of the service provider with the cloud service manager130. The IT service management application of the service provider may monitor hardware resources.

The metering function shown inFIG. 3Amay include collection of resource usage data and applying charging rules based on the types of services being provided to the user. For example, the metering function may collect resource data information on virtual machine (VM) “active” status. The metering function may apply pay-per-use charging rules (e.g., flat fee per VM daily active status). The usage and charging data may be stored in the integrated repository.

The core132orchestrates service delivery and management.FIG. 3Bshows some of the functions performed by the core132to orchestrate service delivery and management. The core132, for example, contains workflow logic for provisioning, metering and accounting, and ticket processing. The core132may perform automated tasks for providing resources on demand, usage data collection, data retrieval and storing into the integrated repository, customer and service configuration, and usage data communication to external applications for billing. The core132also facilitates tasks for assessing technical feasibility to provide services, design of services, and ticket management.

FIG. 3Cshows the service platform integration layer133integrating the cloud service manager130with the service platform layer140. The service platform integration layer133, for example, operates as an internal service bus connecting components of the cloud service manager130with the service platform layer140. For example,FIG. 3Cshows the service platform integration layer133operating as an internal service bus connecting the cloud service manager130with a cloud stack for VM activation and with a virtual desktop administrator of the service platform layer140.

FIG. 1shows the server platforms140including a virtual server/cloud stack141and virtual desktop administrator142. The cloud stack provides capabilities to activate infrastructure as a service, including VMs , operating systems, firewalls, software applications, and hypervisors.FIG. 4Ashows the virtual server/cloud stack141managing clusters in pods. The clusters may include physical hosts, each with its assigned storage. The host can run the hypervisor. The storage can be local or shared storage. Pods are groups of clusters.

FIG. 4Bshows the virtual desktop administrator142which may create and manage virtual desktops. The virtual desktop administrator142may allow the user to customize virtual desktops.

The hardware components150shown inFIG. 1may be provided by the service provider or another entity. The hardware components150may include servers151and storage152. The hardware components150are the hardware resources operating as platforms for the services delivered to users. The hardware components150host the VMs and virtual desktops.

FIG. 5shows an example of using the cloud services system100to provide services to different types of users, including end users/small businesses, large enterprises and internal users. Also, the cloud services system100may be implemented via a public cloud or an internal cloud for an organization and its users.

The cloud services system100may be extended to include software as a service (SaaS) and platform as a service (PaaS) services. Also, different business models may be used for the cloud services system100. Some business models may include provide cloud services to users, such as small businesses, end users, and large enterprises, in a pay-per-use arrangement. Other models may include providing cloud services to wholesalers, extend cloud services through partners, include additional services from federated cloud providers, or provide cloud services via brokering services.

FIG. 6shows a flow chart of a method that may be implemented by the cloud services system100. At601, the layers of the cloud services system100are installed on a computing platform and executed, for example, by a telecommunications provider. At602, the access services layer provides users with access to order services. At603, the cloud service manager130facilitates provisioning of the ordered service. At604, the service platform layer140provisions virtual servers and virtual desktops for the ordered services.

Some or all of the methods and operations and functions described above may be provided as machine readable instructions, such as computer programs, stored on a computer readable storage medium, which may be non-transitory such as hardware storage devices or other types of storage devices. For example, they may exist as program(s) comprised of program instructions in source code, object code, executable code or other formats. An example of computer readable storage media includes a RAM, ROM, EPROM, EEPROM, hard drivers, etc.

Referring toFIG. 7, there is shown a computer system700that may be a computer platform for executing the cloud services system100. It is understood that the illustration of the computer system700is a generalized illustration and that the computer system700may include additional components and that some of the components described may be removed and/or modified.

The computer system700includes processor(s)701, such as a central processing unit, ASIC or other type of processing circuit; I/O devices702, such as a monitor and/or keyboard; a network interface703, such as a network interface to a Local Area Network (LAN), a wireless 802.11x LAN, a 3G or 4G mobile WAN or a WiMax WAN; and a computer-readable medium704. Each of these components may be operatively coupled to a bus708. A computer readable medium (CRM), such as CRM704may be any suitable medium which participates in providing instructions to the processor(s)701for execution. For example, the CRM704may be non-transitory or non-volatile media, such as a magnetic disk or solid-state non-volatile memory or volatile media such as RAM. The instructions stored on the CRM704may include machine readable instructions executed by the processor701to perform the methods and functions of the cloud services system100.

While the embodiments have been described with reference to examples, those skilled in the art will be able to make various modifications to the described embodiments without departing from the scope of the claimed embodiments.