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/cluster-references/chef-reference.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,10 @@
1
1
---
2
2
title: Chef Orchestration in Azure CycleCloud
3
3
description: Learn about Chef orchestration in Azure CycleCloud. Chef is a configuration management tool that automates the deployment and management of applications and infrastructure.
description: See a reference for cluster-init objects to be used with Azure CycleCloud. A cluster-init object defines the CycleCloud project specifications to run on a node.
4
-
author: adriankjohnson
5
-
ms.date: 06/29/2025
4
+
author: dougclayton
5
+
ms.author: doclayto
6
+
ms.date: 09/23/2025
6
7
ms.update-cycle: 3650-days
7
-
ms.author: adjohnso
8
8
ms.custom: compute-evergreen
9
9
---
10
10
@@ -18,14 +18,13 @@ The section uses a shorthand notation to reference the fully qualified spec:
18
18
[[[cluster-init PROJECT:SPEC:VERSION]]]
19
19
```
20
20
21
-
By default, projects are stored in the [locker](../how-to/projects.md#lockers)defined on the node. To specify a different locker, you can include a locker reference in the `[[[cluster-init]]]` section:
21
+
By default, projects are assumed to stored in the [locker](../how-to/projects.md#lockers)already. However, if you are using a project defined in GitHub, you can indicate that with the `cyclecloud/` prefix:
> For built-in projects that are downloaded from GitHub, use `cyclecloud` as the locker. This will tell CycleCloud to download the project from GitHub and upload them to your locker in a special cache area. Without `cyclecloud/` in the cluster-init reference, CycleCloud will expect the project to be uploaded by you.
27
+
This tells CycleCloud to download the project files from GitHub and upload them to your locker in a special cache area. Without `cyclecloud/` in the cluster-init reference, CycleCloud will expect the project to be uploaded by you.
29
28
30
29
As an example, this cluster template defines one node that uses three specs:
31
30
@@ -50,15 +49,19 @@ Attribute values that start with `$` reference parameters.
50
49
51
50
The CycleCloud project specs run in the order you list them in the Cluster Template File. In this example, `my-proj:default` runs first because it comes from the node defaults. Next, `myproject:my-spec` runs, which comes from the locker named `test-locker`. Finally, `my-proj:my-spec` runs.
52
51
53
-
The `[[[cluster-init LOCKER/PROJECT:SPEC:VERSION]]]` form is a shorthand for the following:
52
+
The `[[[cluster-init PROJECT:SPEC:VERSION]]]` form is a shorthand for the following:
54
53
```ini
55
54
[[[cluster-init]]]
56
55
Project = PROJECT
57
56
Version = VERSION
58
57
Spec = SPEC
59
-
Locker = LOCKER
60
58
```
61
59
60
+
You can also use `[[[cluster-init SOURCE_LOCKER/PROJECT:SPEC:VERSION]]]` to specify a `SourceLocker` for the cluster-init spec. The source locker is optional. Without it, CycleCloud assumes the locker already has the files staged. If set to the special name `cyclecloud`, it uses a built-in project defined in CycleCloud whose contents are stored in GitHub. Otherwise, if set to a different locker, it stages the files from that locker to the target locker before starting the node. This is useful for custom cluster-init projects and multi-region deployments, because you only have to manually stage the files to a single locker, which you can use as a source locker for nodes in a different region.
61
+
62
+
[!NOTE]
63
+
> Projects that are staged automatically are put in a special cache directory of the target locker so that they don't conflict with projects you stage manually.
64
+
62
65
## Attribute reference
63
66
64
67
Attribute | Type | Definition
@@ -67,5 +70,6 @@ Project | String | Name of the CycleCloud project.
67
70
Version | String | Version of the CycleCloud project specification.
68
71
Spec | String | Name of the CycleCloud project specification.
69
72
Locker | String | Name of the locker to download the project specification from.
73
+
SourceLocker | String | Optional. Name of another locker that should be used to stage files from. If set to the special name _cyclecloud_, it uses a built-in project defined in CycleCloud whose contents are stored in GitHub.
70
74
Order | Integer | Optional integer that you can use to override the order of the specs. The default starts at 1000 and goes up by one for each spec.
Copy file name to clipboardExpand all lines: articles/cyclecloud/how-to/cluster-templates.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
---
2
2
title: Cluster Templates
3
3
description: Use or build cluster templates within Azure CycleCloud. See configuration notation, cluster template parameters, machine types, spot virtual machines, and more.
@@ -94,7 +94,7 @@ If you add more than one locker, you can set your default locker with `cycleclou
94
94
> [!NOTE]
95
95
> Default lockers are stored in the CycleCloud config file, usually located in _~/.cycle/config.ini_ and not the _project.ini_ file. This setup allows version control for _project.ini_.
96
96
97
-
When you upload your project contents, CycleCloud syncs the cluster-init contents to your target locker, at `(locker)/projects/(project)/(version)/(spec_name)/cluster-init`.
97
+
When you upload your project contents, CycleCloud syncs the cluster-init contents to your target locker, at `projects/(project)/(version)/(spec_name)/cluster-init`.
Copy file name to clipboardExpand all lines: articles/cyclecloud/how-to/storage-blobs.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
---
2
2
title: Storage - Blobs and Lockers
3
3
description: In this article, learn how to use project blobs and user blobs for storage within Azure CycleCloud. Also learn about blob downloading and lockers.
Copy file name to clipboardExpand all lines: articles/cyclecloud/jetpack.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
---
2
2
title: Jetpack Reference
3
3
description: Read reference information about the Jetpack tool in Azure CycleCloud. Jetpack provides node configuration, distributed synchronization, and HealthCheck.
0 commit comments