MMCloud has several components that interact with cloud services to ensure mobility for submitted jobs so that, for example, jobs run to completion on Spot Instances.

To use MMCloud, you need an account with a Cloud Service Provider.

Containers provide a standardized and repeatable way to package, deploy, and manage applications in the cloud.

MMCloud includes a job scheduler for running batch jobs in the cloud.

The OpCenter provides a web interface to activate the license and to submit and manage jobs.

The web interface provides a form that you complete to submit a job.

Use the MMCloud CLI to submit a job.

The Memory Machine Cloud web interface and CLI have a rich set of options that allow you to customize the container runtime environment.

A job that generates file system I/O requires a definition for one or more file systems.

The selection of virtual machine types can be restricted by using an allow list or a deny list (or both).

Service templates simplify the procedure for submitting jobs that include many options.

Use filters to limit a command to a subset of all jobs, hosts, or gateways.

The error policy determines how job failures are handled.

If a later version of OpCenter software is available, an OpCenter instance can be upgraded even if jobs are currently running.

SpotSurfer removes the risk of running stateful applications on Spot Instances while reducing costs significantly.

When enabled, WaveRider allows OpCenter to optimize cloud resources by moving jobs as the resource demands change.

SurfZone is a cost management feature that helps limit the amount spent on cloud computing each month.

The gateway service provides a reverse proxy so that a job can migrate from one host to another without interrupting client connections.

WaveWatcher displays real-time resource utilization graphs on a per job basis.

Use the float CLI commands to interact with the OpCenter; for example, to submit and manage jobs.

Configurable parameters control the behavior of the OpCenter.