2.7.2 Provide User Interface

Moab can support both automatic and manual allocation of utility computing resources. Each model applies to different customers and different needs although some customers may be interested in the ability to use both manually and automatically allocated resources.

Regardless of the model used, customers usually must register with the hosting service. This can be a manual, semi-automated, or fully-automated process. Regardless, the process of registration should collect user profile information and establish basic usage constraints such as service levels authorized, billing rates, and so forth. This process should also establish default customer authentication techniques to securely identify future customer requests. This information can be directly configured within Moab, or Moab can be set up to extract this information directly from an allocation management or identity management system, or a relational database.

Using these systems, Moab is able to control on a per customer basis, authentication management, resource access policies, customer user lists, service level agreements, and other factors. In the example configuration that follows, Moab imports all relevant customer information directly from a relational database.

IDCFG[customerdata] SERVER=sql://customerdata?moab

The user interface presents the available utility resources to the customer. To be successful, the interface must be simple, distilling the options to a minimal, yet complete set of needed resource options. To be scalable, it will need to empower customer self-service. Depending on customer base and usage needs, this interface may operate in any of the following models:

• May provide detailed information regarding resources that can be made available
• May provide per-customer views of available resources where users only see resources available to them or to their class of service
• May provide no general information regarding resource availability and rather only replies to the availability of resources for explicit requests

As part of Moab Utility Computing Suite, Cluster Resources provides an easily skinned utility computing portal that supports any of these models and allows customers to modify their user profile, request utility computing resources, view status of current resource allocations, and view statistics, account balances, and other historical information.

As a service, Cluster Resources can completely create and customize the user portal, or site administrators can choose to modify the provided portal or create their own using the Moab command line, C-API, or Java API interface.

2.7.2.1 Self-Service Web Portals

The customer self-service portal should be secure requiring either password or token based authentication. It is often desirable to have the portal obtain customer profile information from the Moab server to limit the service and resource access options to only those specifically subscribed to by the customer during the registration. At a minimum, the portal should also allow the customer to create, monitor, modify, and cancel existing resource allocations. This includes a utility computing overview page wherein customers can see all of their currently active allocations with associated access information such as IP address, login and password.

There is further value in enabling additional self-service options including direct manipulation of customer contact information and default resource requirement templates. Other potential options include direct subscription to new services, policy and general usage documentation, access to statistical reports, and account usage and balance information.

2.7.2.2 Enabling Email Notifications and Alerts

In addition to the Web-based utility computing overview page, customers may also receive email notifications when a requested allocation is about to become available or when hardware or system failures have resulted in adjustments to the original allocation start date. Further email notifications are also often desirable to notify customers when an allocation is about to expire or if an option to extend the allocation exists.