20.0 Virtual Private Clusters
Virtual Private Clusters Overview
Within any organization, resources sometimes need to be set aside and configured for special projects or daily workflows. Requests may come from many different departments, each with its own needs and timetables. Set aside resources might include servers, databases, networks, or specialized hardware. Administrators can configure Moab to automatically service these requests, including configuration and provisioning, through Virtual Private Clusters (VPCs).
VPCs allow sites to group resources as a named package, which allows users to select the name of the package they need instead of requesting each resource individually. When a user requests a package, Moab schedules all of the resources required and lets the user know when the package is available for use.
Resources such as network, data, and security objects can be packaged together as a single VPC. Users must then just request the primary resource needed, such as a compute node, and other pre-configured resources such as storage and network are automatically added.
Additional setup and teardown steps can also be added to the VPC. Moab runs these extra steps automatically without the need for administrator action. Users request a package, wait for notification that the package is ready, and start using it while Moab, behind the scenes, takes care of scheduling, configuration and provisioning.
Administrators can place limits on profiles and restrict who is allowed to use them. Charging and accounting policies can also be configured to allow for automated billing.
Searches Moab documentation only
|© 2001-2010 Adaptive Computing Enterprises, Inc.|