Cluster: test-cli

Checking AWS environment settings
AWS config
  IAM Profile: .+ \[default\]
  EC2 Key pair \(head & workers\): .+ \[default\]
  VPC Subnets \(head & workers\): subnet-.+ \[default\]
  EC2 Security groups \(head & workers\): sg-.+ \[default\]
  EC2 AMI \(head & workers\): 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
  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\] Initalizing 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

Useful commands
  Monitor autoscaling with
    ray exec .+ 'tail -n 100 -f /tmp/ray/session_latest/logs/monitor\*'
  Connect to a terminal on the cluster head:
    ray attach .+
  Get a remote shell to the cluster manually:
    ssh .+
