Using CycleCloud

Step 1:

Cycle LifeCycle 1

To provision a compute environment, the user begins by selecting a cluster template that specifies the composition of the infrastructure (instance type, storage and network configuration), the software configuration (role-based service deployment), and the dynamic behavior of the environment in the cloud (provisioning behaviors, optimizations, resiliency, cost profiles). Using this template, CycleCloud uses the cloud provider API to instantiate the infrastructure, configure the software stack, and prepare for use.

Step 2:

Cycle LifeCycle 2

Users access the cloud-based cluster over secure applications such as ssh or RDP over a VPN connection. The initial state of the cluster is determined by the cluster template selected in Step 1 and typically consists of a master node, a shared filer/storage and any unique configurations required by the specific workload. CycleCloud monitors the cluster job queue and, based on auto-scaling parameters in the template, dynamically provisions fully configured execute nodes.

Additionally, depending on the template rules, CycleCloud can automatically bid for resources at different price to take advantage of potential cost savings associated with spot markets. This can significantly lower computational costs.

Step 3:

Cycle LifeCycle 3

As the user’s jobs complete, CycleCloud verifies the job completion, manages final data placement and tears down cluster resources on billing boundaries to help control costs. This behavior is configurable and helps ensure that you only pay for what you need, when you need it.

With today’s complicated workflows, increasing system demands, and rapidly changing marketplace for cloud offerings, having an orchestration suite that is designed from the ground up as a single control point is critical. Cycle Computing’s CycleCloud software suite delivers this ability with its leading cloud orchestration, provisioning, and data management platform for Big Compute, Big Data, and large technical computing applications running on any public, private, or internal environment.

View our documentation for additional technical background

 

Download:      CycleCloud Solutions Brief

 

3241