You should launch a build so you can verify that your Cluster Manager cloud setup is properly launching instances and do any troubleshooting if needed.
Launch a build by invoking eMake with a command such as:
emake --emake-cm=<cluster_manager_public_DNS> --emake-resource=<resource_name> --emake-root=<root_dir>
You can limit the number of launched instances. To do so, include the
--emake-maxagents=N eMake option, where
N is the number of agents.
When you start the build, the instances are launched. The build might require several minutes to begin. A
No agents available message might appear while the instances are launching.
When the first instance is up, the build proceeds. When the build finishes, the agents become idle and available for a subsequent build for 15 minutes (by default) until their instances are terminated. You can configure this timeout period by using the Instance Idle Timeout (minutes) setting when you create or edit a resource in the Cluster Manager. For details, see Resources - Create or Edit a Resource.
After at least one build is currently running, navigate to the Cloud > Status subtab in the Cluster Manager web UI to see that your setup works. Launched instances appear in the Current Instances section on this subtab. For details about the information in the Cloud > Status subtab, see Current Instance Status.
To troubleshoot your agent cloud bursting setup, on the Cluster Manager machine:
See the state of the instances in the Cloud > Cloud Burst Status subtab in the Cluster Manager web UI.
This subtab contains status for Kubernetes, Azure Services Platform, Amazon EC2, or Google Cloud Platform instances that are active (that is, instances that are running builds). If no instances are active, this page is blank. For details, see Current Instance Status.
See the Cloud > Cloud Messages subtab in the Cluster Manager web UI.
This subtab contains messages about agent on-demand request processing (actions performed) on the cloud platform. For details, see Cloud Messages.