You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cyclecloud/how-to/configure-autoscaling.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,39 +2,39 @@
2
2
title: Configuring Autoscaling
3
3
description: Learn how to configure autoscaling on Azure CycleCloud clusters. Scaling lets you easily increase or decrease a resource to accommodate heavier or lighter loads.
4
4
author: adriankjohnson
5
-
ms.date: 01/14/2020
5
+
ms.date: 07/01/2025
6
6
ms.author: adjohnso
7
7
---
8
8
9
-
# AutoScale Your Clusters
9
+
# AutoScale your clusters
10
10
11
-
*Scaling*is the ability to easily increase or decrease a resource to accommodate heavier or lighter loads. In Azure CycleCloud, jobs can be easily scaled up when the load increases, or scaled down to conserve cost. This can be done automatically or manually.
11
+
*Scaling*means you can easily increase or decrease a resource to handle heavier or lighter loads. In Azure CycleCloud, you can easily scale up jobs when the load increases or scale down jobs to save costs. You can set up scaling to happen automatically or do it manually.
12
12
13
-
## Auto-Scaling
13
+
## Auto-scaling
14
14
15
-
When creating a new cluster via the GUI, the **Compute Backend** tab allows you to choose to auto-scale your cluster and add execute hosts as required. Check the box to allow CycleCloud to start and stop execute nodes as required, and set the number of initial and maximum cores allowed.
15
+
When you create a new cluster through the GUI, the **Compute Backend** tab gives you the option to auto-scale your cluster and add execute hosts as needed. Select the check box to let CycleCloud start and stop execute nodes as needed. Set the number of initial and maximum cores.
16
16
17
17
::: moniker range="=cyclecloud-7"
18
-
18
+
19
19
::: moniker-end
20
20
21
21
::: moniker range=">=cyclecloud-8"
22
-
22
+
23
23
::: moniker-end
24
24
25
-
Setting a **Max Cores** number will limit the number of nodes started to ensure your workload does not run unfetted. You can also set up an [usage alert](~/articles/cyclecloud/concepts/usage-tracking.md) when submitting your job to ensure a budget is not exceeded.
25
+
Setting a **Max Cores** number limits the number of nodes that start, so your workload doesn't run unchecked. You can also set up an [usage alert](~/articles/cyclecloud/concepts/usage-tracking.md) when you submit your job to make sure you don't go over budget.
26
26
27
-
## Auto-Scaling in Cluster Template
27
+
## Auto-scaling in cluster template
28
28
29
-
By default, auto-scaling is disabled for all new clusters. To enable it, add the following to your [cluster template](cluster-templates.md):
29
+
By default, new clusters have auto-scaling turned off. To turn on auto-scaling, add the following code to your [cluster template](cluster-templates.md):
30
30
31
31
```ini
32
32
Autoscale = true
33
33
...
34
34
MaxCoreCount = xx
35
35
```
36
36
37
-
## Further Reading
37
+
## More information
38
38
39
39
* Create a [Cluster Template](cluster-templates.md)
Copy file name to clipboardExpand all lines: articles/cyclecloud/how-to/connect-to-node.md
+29-30Lines changed: 29 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,93 +2,93 @@
2
2
title: Connecting to a Cluster Node
3
3
description: Use the CycleCloud web interface or CycleCloud CLI to log into a cluster node
4
4
author: adriankjohnson
5
-
ms.date: 03/25/2020
5
+
ms.date: 07/01/2025
6
6
ms.author: jechia
7
7
---
8
8
9
-
# Connecting into Cluster Nodes
9
+
# Connecting to cluster nodes
10
10
11
-
You can remotely access a cluster node using SSH for Linux nodes, and RDP for Windows nodes.
11
+
You can remotely access a cluster node using SSH for Linux nodes and RDP for Windows nodes.
12
12
13
13
::: moniker range="=cyclecloud-7"
14
-
The **Connect** button in the cluster management pane provides a connection string for accessing the node. For example, to access a cluster head node, select the master node in the cluster management pane and click the **Connect** button:
14
+
The **Connect** button in the cluster management pane provides a connection string for accessing the node. For example, to access a cluster head node, select the primary node in the cluster management pane and select **Connect**:
Copy the appropriate connectionstring and use either your SSH client or the CycleCloud CLI to connect to the master node.
22
+
Copy the appropriate connection string and use either your SSH client or the CycleCloud CLI to connect to the primary node.
23
23
::: moniker-end
24
24
25
25
::: moniker range=">=cyclecloud-8"
26
-
The **Connect** button in the cluster management pane provides a connection string for accessing the node. For example, to access a cluster head node, select the scheduler node in the cluster management pane and click the **Connect** button:
26
+
The **Connect** button in the cluster management pane gives you a connection string to access the node. For example, to access a cluster head node, select the scheduler node in the cluster management pane and select the **Connect** button:
Copy the appropriate connectionstring and use either your SSH client or the CycleCloud CLI to connect to the master node.
34
+
Copy the connection string and use either your SSH client or the CycleCloud CLI to connect to the primary node.
35
35
::: moniker-end
36
36
37
37
38
38
## Accessing cluster nodes in a private subnet
39
39
40
-
You can use either `cyclecloud connect` or raw SSH client commands to access nodes that are within a private subnet of your VNET. These instructions assume you are using SSH with public-key authentication. This is typical for Linux nodes. For Windows, you can use this method to set up an RDP tunnel.
40
+
To access nodes within a private subnet of your virtual network, use either `cyclecloud connect` or raw SSH client commands. These instructions assume you're using SSH with public-key authentication, which is typical for Linux nodes. For Windows nodes, you can use this method to set up an RDP tunnel.
41
41
42
42
First, make the private key accessible to the target node. The simplest way is to run an SSH agent on your personal machine.
43
43
44
44
> [!WARNING]
45
-
> The private key should never leave your personal machine! In the
46
-
> following examples your private key never leaves your machine. The agent uses
47
-
> this to respond to authentication challenges sent by the remote node.
45
+
> Never share your private key outside your personal machine. In the
46
+
> following examples, your private key stays on your machine. The agent uses
47
+
> your private key to respond to authentication challenges sent by the remote node.
48
48
49
49
From your local machine, start the agent with the `ssh-agent` command:
50
50
51
51
```script
52
52
exec ssh-agent bash
53
53
```
54
54
55
-
If the private key is not your default private key (*~/.ssh/id_rsa* or _~/.ssh/identity_), add it to the agent:
55
+
If the private key isn't your default key (`~/.ssh/id_rsa` or `~/.ssh/identity`), add it to the agent:
56
56
57
57
```script
58
58
ssh-add PATH_TO_KEYPAIR
59
59
```
60
60
61
-
Those commands only need to be run once (or after you reboot).
61
+
You only need to run these commands once (or after you reboot).
62
62
63
63
### Using `cyclecloud connect`
64
64
65
-
You can connect to an node via a bastion server by specifying the IP address on the command line:
65
+
You can connect to a node through a bastion server by specifying the IP address on the command line:
The above command assumes`cyclecloud` as the username, `22` as the port, and loads your default SSH key. To customize these values, see the `--bastion-*` help options for the [`cyclecloud` CLI command](~/articles/cyclecloud/cli.md#cyclecloud-connect).
71
+
This command uses`cyclecloud` as the username, `22` as the port, and loads your default SSH key. To customize these values, see the `--bastion-*` help options for the [`cyclecloud` CLI command](~/articles/cyclecloud/cli.md#cyclecloud-connect).
72
72
73
-
Alternately, the CycleCloud CLI can detect the bastion host for you if you add the following directive to your `~/.cycle/config.ini`:
73
+
Alternatively, the CycleCloud CLI can detect the bastion host for you if you add the following directive to your `~/.cycle/config.ini`:
74
74
75
75
```ini
76
76
[cyclecloud]
77
77
bastion_auto_detect = true
78
78
```
79
79
80
-
With the above directive, you can run `cyclecloud connect htcondor-scheduler` without specifying any details about the bastion server.
80
+
With this directive, you can run `cyclecloud connect htcondor-scheduler` without specifying any details about the bastion server.
81
81
82
-
You can also use `cyclecloud connect` to connect a Windows VM. Executing the following command will create an RDP connection over an SSH tunnel. Additionally, it will launch the Microsoft RDP client on OSX and Windows:
82
+
You can also use `cyclecloud connect` to connect a Windows VM. When you run the following command, it creates an RDP connection over an SSH tunnel. It also starts the Microsoft RDP client on macOS and Windows:
83
83
84
84
```CLI
85
85
cyclecloud connect windows-execute-1
86
86
```
87
87
88
88
> [!NOTE]
89
-
> CycleCloud chooses an unused ephemeral port for the tunnel to the Windows VM.
89
+
> CycleCloud picks an unused ephemeral port for the tunnel to the Windows VM.
90
90
91
-
You can configure the `cyclecloud` command to use a single bastion host for all your connections:
91
+
You can set up the `cyclecloud` command to use one bastion host for all your connections with this command:
You can connect to a private server via the bastion server using agent forwarding:
103
+
You can connect to a private server through the bastion server by using agent forwarding:
104
104
105
105
```CLI
106
106
ssh -A -t cyclecloud@BASTION_SERVER_IP ssh -A cyclecloud@TARGET_SERVER_IP
107
107
```
108
108
109
-
This connects to the bastion and then immediately runs SSH again, so you get a terminal on the target VM. You may need to specify a user other than
110
-
`cyclecloud` on the VM if your cluster is configured differently. The `-A` argument forwards the agent connection so your private key on your local machine is used automatically. Note that agent forwarding is a chain, so the second SSH command also includes `-A`so that any subsequent SSH connections initiated from the target VM also use your local private key.
109
+
This command connects to the bastion server and then immediately runs SSH again, so you get a terminal on the target VM. You might need to specify a user other than
110
+
`cyclecloud` on the VM if you configured your cluster differently. The `-A` argument forwards the agent connection so your private key on your local machine is used automatically. Agent forwarding works as a chain, so the second SSH command also includes `-A`to ensure that any subsequent SSH connections initiated from the target VM also use your local private key.
111
111
112
-
### Connecting to Services on the Target VM
113
-
114
-
You can use the SSH connection to connect to services on the target VM, such as a Remote Desktop, a database, etc. For example, if the target VM is Windows, you can create a Remote Desktop tunnel by connecting to the target VM with a similar SSH command from above, using the `-L` argument:
112
+
### Connecting to services on the target VM
115
113
114
+
You can use the SSH connection to connect to services on the target VM, such as a Remote Desktop, a database, and more. For example, if the target VM is Windows, you can create a Remote Desktop tunnel by connecting to the target VM with an SSH command similar to the following example, using the `-L` argument:
116
115
117
116
```CLI
118
117
ssh -A -t cyclecloud@BASTION_SERVER_IP -L 33890:TARGET:3389 ssh -A cyclecloud@TARGET_SERVER_IP
119
118
```
120
119
121
-
This will tunnel port 3389 on target to 33890 on your local machine. Then if you connect to `localhost:33890` you will actually be connected to the target VM.
120
+
This command tunnels port 3389 on the target to port 33890 on your local machine. When you connect to `localhost:33890`, you actually connect to the target VM.
0 commit comments