Cluster: test-cli Checking AWS environment settings AWS config IAM Profile: .+ \[default\] EC2 Key pair \(all available node types\): .+ \[default\] VPC Subnets \(all available node types\): subnet-.+ \[default\] EC2 Security groups \(all available node types\): sg-.+ \[default\] EC2 AMI \(all available node types\): ami-.+ \[dlami\] No head node found\. Launching a new cluster\. Confirm \[y/N\]: y \[automatic, due to --yes\] Acquiring an up-to-date head node Launched 1 nodes \[subnet_id=subnet-.+\] Launched instance i-.+ \[state=pending, info=pending\] Launched a new head node Fetching the new head node <1/1> Setting up head node Prepared bootstrap config Autoscaler v2 is now enabled by default.+ New status: waiting-for-ssh \[1/7\] Waiting for SSH to become available Running `uptime` as a test\. Fetched IP: .+ Success\. Updating cluster configuration\. \[hash=.+\] New status: syncing-files \[2/7\] Processing file mounts ~/tests/ from ./ \[3/7\] No worker file mounts to sync New status: setting-up \[4/7\] Running initialization commands \[5/7\] Initializing command runner \[6/7\] Running setup commands \(0/4\) echo a \(1/4\) echo b \(2/4\) echo \${echo hi} \(3/4\) echo head \[7/7\] Starting the Ray runtime New status: up-to-date -{60} Note: The output above is from the head node \(via `ray start`\)\. Commands shown in 'Next steps' may only work from the head node or from within the cluster network\. Useful commands for your local machine: To terminate the cluster: ray down .+ To retrieve the IP address of the cluster head: ray get-head-ip .+ To port-forward the cluster's Ray Dashboard to the local machine: ray dashboard .+ To submit a job to the cluster, port-forward the Ray Dashboard in another terminal and run: ray job submit --address .+ To connect to a terminal on the cluster head for debugging: ray attach .+ To monitor autoscaling: ray exec .+ 'tail -n 100 -f /tmp/ray/session_latest/logs/monitor\*'