Skip to content

Commit c058aa1

Browse files
authored
Update 360 SaaS content (#4424)
* Update 360 SaaS content Signed-off-by: Ian Maddaus <[email protected]> * Update chef/samples content Signed-off-by: Ian Maddaus <[email protected]> --------- Signed-off-by: Ian Maddaus <[email protected]>
1 parent 349d92d commit c058aa1

21 files changed

+277
-412
lines changed

_vendor/github.com/chef/samples/cohorts/skill-assembly.json

Lines changed: 4 additions & 4 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

_vendor/github.com/chef/samples/sample.text

Lines changed: 1 addition & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

_vendor/modules.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@
1414
# github.com/chef/compliance-profiles/docs-chef-io v0.0.0-20250424114557-297ae97f62c2
1515
# github.com/chef/compliance-remediation-2022/docs-chef-io v0.0.0-20250506081430-c04163aa35a9
1616
# github.com/chef/license-service/docs-chef-io v0.0.0-20250120051510-ae1de80f4621
17-
# github.com/chef/samples v0.0.0-20250304162216-b7bf3710b07e
17+
# github.com/chef/samples v0.0.0-20250424163637-3393187e624c
1818
# github.com/chef/chef-docs-theme v0.0.0-20250217213320-727f9bce8258
1919
# github.com/FortAwesome/Font-Awesome v0.0.0-20240108205627-a1232e345536
2020
# github.com/cowboy/jquery-hashchange v0.0.0-20100902193700-0310f3847f90

content/360/saas/get_started/_index.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -9,29 +9,29 @@ parent = "chef_cloud/360/get_started"
99
weight = 10
1010
+++
1111

12-
This section provides quickstart guides for getting started with Chef 360 SaaS and its tools.
12+
This section is a quickstart guide to using Chef 360 SaaS and its tools.
1313

14-
## Get started guides
14+
## How Chef 360 SaaS works
1515

16-
Before you begin with these guides, [review the system requirements]({{< relref "system_requirements" >}}).
16+
Chef 360 SaaS consists of three main components:
1717

18-
Chef 360 SaaS guides:
18+
- **Chef 360 SaaS CLIs**: Users use the CLIs to define and invoke Chef Courier jobs, and configure user accounts, tenants, organizations, and nodes.
19+
- **Chef 360 SaaS**: Manages users, organizations, and tenants, schedules and distributes Courier jobs, and monitors nodes and job results.
20+
- **Chef skills**: Chef 360 SaaS installs skills on each node that manage the node, execute jobs, and report to Chef 360 SaaS.
1921

20-
- [Set up Chef 360 SaaS]({{< relref "set_up" >}})
22+
## What this guide covers
2123

22-
Chef 360 Platform CLI guides:
24+
This guide walks you through the following steps:
2325

24-
- [Install and register the Chef 360 Platform CLIs]({{< relref "install_cli" >}})
26+
1. Installing Chef 360 SaaS in a single-node Kubernetes cluster.
27+
1. Installing Chef 360 SaaS CLIs on a local workstation and registering it with Chef 360 SaaS.
28+
1. Enrolling a node with Chef 360 SaaS. Nodes can be enrolled using a Chef 360 SaaS CLI or by uploading a Chef Infra cookbook if Chef Infra Client is already installed on the node.
29+
1. Defining and running a basic job on a node, and reviewing the job's execution details and the results of each step.
2530

26-
Chef Node Management guides:
31+
## Before you begin
2732

28-
- [Register the Node Management agent]({{< relref "register_node_agent" >}})
29-
- [Define skills]({{< relref "define_skills" >}})
30-
- [Create a skill assembly]({{< relref "create_skill_assembly" >}})
31-
- [Create override settings]({{< relref "override_settings" >}})
32-
- [Create a node cohort]({{< relref "node_cohort" >}})
33-
- [Enroll nodes]({{< relref "enroll_nodes" >}})
33+
- Review the [Chef 360 SaaS system requirements]({{< relref "/360/saas/system_requirements.md" >}}).
3434

35-
Chef Courier job guides:
35+
## Next steps
3636

37-
- [Run jobs with Chef Courier]({{< relref "jobs" >}})
37+
- [Set up Chef 360 SaaS]({{< relref "/360/saas/get_started/set_up.md" >}}).

content/360/saas/get_started/create_skill_assembly.md

Lines changed: 0 additions & 33 deletions
This file was deleted.

content/360/saas/get_started/define_skills.md

Lines changed: 0 additions & 131 deletions
This file was deleted.

content/360/saas/get_started/enroll_nodes.md

Lines changed: 24 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -8,31 +8,47 @@ parent = "chef_cloud/360/get_started"
88
weight = 100
99
+++
1010

11-
Node enrollment brings nodes under management by Chef 360 SaaS.
11+
When you enroll a node into a node cohort, Chef 360 Platform installs the Chef skills and skill settings that are defined for all nodes in that cohort.
12+
These skills allow Chef 360 Platform to manage the node, execute Chef Courier jobs, and report back to Chef 360 Platform.
13+
14+
Chef 360 Platform installs the following skills in the default skill assembly:
15+
16+
- **Chef Infra Client interpreter skill**: Executes Chef Infra Client runs.
17+
- **Courier Runner skill**: Interprets and executes Chef Courier jobs.
18+
- **Gohai skill**: Reports node attribute data to Chef 360 Platform.
19+
- **Inspec interpreter skill**: Executes Chef InSpec audits.
20+
- **Node Management agent**: Manages and installs other skills on the node.
21+
- **Restart interpreter skill**: Restarts nodes.
22+
- **Shell interpreter skill**: Executes shell scripts.
23+
24+
For more information, see the [Chef 360 skills](https://docs.chef.io/360/1.3/node_management/skills/) documentation.
25+
26+
## Node enrollment methods
1227

1328
This document demonstrates two different methods of node enrollment:
1429

1530
- cookbook-based enrollment
1631
- single-node enrollment
1732

33+
For more information, see the [node enrollment documentation](https://docs.chef.io/360/1.3/node_management/enroll_nodes/).
34+
1835
{{< note >}}
1936

20-
This version of Chef 360 SaaS doesn't support node re-enrollment.
37+
Chef 360 Platform doesn't support node re-enrollment.
2138

2239
{{< /note >}}
2340

24-
## Prerequisites
41+
## Role requirements
2542

26-
- [A node cohort has been created]({{< relref "node_cohort" >}}).
43+
To enroll nodes, use a profile with the [node-manager role](https://docs.chef.io/360/1.3/administration/system_roles/).
2744

28-
## Requirements
45+
## Before you begin
2946

30-
Review the [node requirements]({{< relref "system_requirements#node-requirements" >}}) before enrolling nodes.
47+
- Review the [node requirements]({{< relref "/360/saas/system_requirements#node-requirements" >}}).
3148

3249
## Single-node enrollment
3350

34-
Single-node enrollment enrolls nodes from the server side.
35-
With this method, you define connection and configuration details and push them up to Chef 360 SaaS, which connects to each node and installs Chef Habitat, Chef Node Management, and any skills or agents assigned to a node cohort.
51+
Single-node enrollment allows you to enroll nodes directly from the server side. With this method, you specify the connection and configuration details for each node and upload them to Chef 360 Platform. Chef 360 Platform then connects to each node, installs Chef Habitat, Chef Node Management, and any skills or agents associated with the node's cohort.
3652

3753
### Enroll Linux nodes
3854

content/360/saas/get_started/install_cli.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,11 @@ parent = "chef_cloud/360/get_started"
1010
weight = 40
1111
+++
1212

13-
This page documents how to download and install the Chef 360 Platform CLIs and register your workstation with your Chef 360 SaaS deployment.
13+
This page documents how to download and install the Chef 360 SaaS CLIs and register your workstation with your Chef 360 SaaS deployment.
1414

1515
## Prerequisites
1616

17-
- [Chef 360 SaaS configured]({{< relref "set_up" >}}).
17+
- [Chef 360 SaaS is configured]({{< relref "set_up" >}}).
1818
- `/usr/local/bin` is present in the PATH environment variable.
1919

2020
## Install CLIs
@@ -142,7 +142,7 @@ To create a profile, follow these steps:
142142
143143
1. Optional: Set your new profile as the default profile.
144144
145-
The Chef 360 Platform CLIs use a default profile automatically in any command that accepts the `--profile` argument.
145+
The Chef 360 SaaS CLIs use a default profile automatically in any command that accepts the `--profile` argument.
146146
If you don't set a default profile, you will have to specify it in each command with `--profile <PROFILE_NAME>`.
147147

148148
Set a default profile:
@@ -155,10 +155,11 @@ To create a profile, follow these steps:
155155

156156
1. Repeat this procedure so that you have separate profiles for the Node Manager and Courier Operator roles.
157157

158-
## Additional information
158+
## More information
159159

160-
- [Chef 360 CLI reference documentation](https://docs.chef.io/360/1.3/reference/cli/)
160+
- [Chef 360 Platform CLI reference documentation](https://docs.chef.io/360/1.3/reference/cli).
161+
- [Chef 360 Platform roles documentation](https://docs.chef.io/360/1.3/administration/system_roles/)
161162

162163
## Next step
163164

164-
- [Register the Node Management agent]({{< relref "register_node_agent.md" >}}).
165+
- [Review the node management settings]({{< relref "node_management_settings" >}})

0 commit comments

Comments
 (0)