Skip to content

Commit

Permalink
CASMCMS-9128: Updates to reflect recent BOS changes (#5352)
Browse files Browse the repository at this point in the history
* CASMCMS-9128: Updates to reflect recent BOS changes

(cherry picked from commit 34793bf)
(cherry picked from commit 5105eeb)

* Update operations/boot_orchestration/Session_Templates.md

Signed-off-by: Mitch Harding <mitchell.harding@hpe.com>
(cherry picked from commit 2ee7ac8)

* Additional linting

* reformat table

---------

Co-authored-by: Russell Bunch <doomslayer@hpe.com>
  • Loading branch information
mharding-hpe and rustydb authored Sep 4, 2024
1 parent 1319e43 commit 2f981a1
Show file tree
Hide file tree
Showing 2 changed files with 55 additions and 52 deletions.
30 changes: 16 additions & 14 deletions operations/boot_orchestration/Session_Templates.md
Original file line number Diff line number Diff line change
Expand Up @@ -160,10 +160,12 @@ root=<Protocol>:<Root FS location>:<Etag>:<RootFS-provider-passthrough parameter
```

BOS fills in the protocol based on the value provided in `rootfs_provider`. If BOS does not know the `rootfs_provider`, then it omits the protocol field.
Currently, BOS only recognizes the `rootfs_provider` `cpss3`.
BOS finds the `rootfs_provider` and `Etag` values in the manifest file in the session template in the boot set.
BOS finds the `rootfs_provider` and `etag` values in the manifest file in the session template in the boot set.
The `rootfs_provider_passthrough` parameters are appended to the `root` parameter without modification. They are "passed through", as the name implies.

Currently, the only `rootfs` provider that BOS recognizes is `cpss3`.
For more information on `cpss3`, see [Create a Session Template to Boot Compute Nodes with CPS](Create_a_Session_Template_to_Boot_Compute_Nodes_with_CPS.md).

#### `root` kernel parameter example

```text
Expand All @@ -172,21 +174,21 @@ root=craycps-s3:s3://boot-images/b9caaf66-c0b4-4231-aba7-a45f6282b21d/rootfs:f04

The following table explains the different pieces in the preceding example.

|Field|Example Value|Explanation|
|-----|-------------|-----------|
|Protocol|`craycps-s3`|The protocol used to mount the root file system, using CPS in this example.|
|`rootfs_provider` location|`s3://boot-images/b9caaf66-c0b4-4231-aba7-a45f6282b21d/rootfs`|The `rootfs_provider` location is a SquashFS image stored in S3.|
|`Etag`|`f040d70bd6fabaf91838fe4e484563cf-211`|The `Etag` (entity tag) is the identifier of the SquashFS image in S3.|
|`rootfs_provider` passthrough parameters|`dvs:api-gw-service-nmn.local:300:nmn0`|These are additional parameters passed through to CPS in this example, which it uses to properly mount the file system.|
| Field | Example Value | Explanation |
|------------------------------------------|----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|
| Protocol | `craycps-s3` | The protocol used to mount the root file system, using CPS in this example. |
| `rootfs_provider` location | `s3://boot-images/b9caaf66-c0b4-4231-aba7-a45f6282b21d/rootfs` | The `rootfs_provider` location is a SquashFS image stored in S3. |
| `etag` | `f040d70bd6fabaf91838fe4e484563cf-211` | The `Etag` (entity tag) is the identifier of the SquashFS image in S3. |
| `rootfs_provider` passthrough parameters | `dvs:api-gw-service-nmn.local:300:nmn0` | These are additional parameters passed through to CPS in this example, which it uses to properly mount the file system. |

The `rootfs_provider_passthrough` parameters are explained in the following table.

|Parameter|Example|Explanation|
|---|---|---|
|Transport|`dvs`|Use DVS to project the SquashFS image down to the node.|
|Gateway|`api-gw-service-nmn.local`|This is the URL that identifies the gateway where the DVS servers are located.|
|Time-out|`300`|The number of seconds to wait to establish a contact.|
|Interface|`nmn0`|The IP interface on the node to use to contact the DVS server; This interface must be up to continue booting.|
| Parameter | Example | Explanation |
|-----------|----------------------------|---------------------------------------------------------------------------------------------------------------|
| Transport | `dvs` | Use DVS to project the SquashFS image down to the node. |
| Gateway | `api-gw-service-nmn.local` | This is the URL that identifies the gateway where the DVS servers are located. |
| Time-out | `300` | The number of seconds to wait to establish a contact. |
| Interface | `nmn0` | The IP interface on the node to use to contact the DVS server; This interface must be up to continue booting. |

Regarding the interface to use for contacting DVS, the possible values are:

Expand Down
77 changes: 39 additions & 38 deletions operations/power_management/Set_the_Turbo_Boost_Limit.md
Original file line number Diff line number Diff line change
@@ -1,54 +1,55 @@
# Set the Turbo Boost Limit

Turbo boost limiting is supported on the Intel® and AMD® processors. Because processors have a high degree of variability in the amount of turbo boost each processor can supply, limiting the amount of turbo boost can reduce performance variability and reduce power consumption.
Turbo boost limiting is supported on the Intel® and AMD® processors. Because processors have a high degree of variability in the amount of turbo boost each processor can supply, limiting the amount
of turbo boost can reduce performance variability and reduce power consumption.

Turbo boost can be limited by setting the `turbo_boost_limit` kernel parameter to one of these values:

- 0 - Disable turbo boost
- 999 - \(default\) No limit is applied.
- 0 - Disable turbo boost
- 999 - \(default\) No limit is applied.

The following values are not supported in COS v1.4:

- 100 - Limits turbo boost to 100 MHz
- 200 - Limits turbo boost to 200 MHz
- 300 - Limits turbo boost to 300 MHz
- 400 - Limits turbo boost to 400 MHz
- 100 - Limits turbo boost to 100 MHz
- 200 - Limits turbo boost to 200 MHz
- 300 - Limits turbo boost to 300 MHz
- 400 - Limits turbo boost to 400 MHz

The limit applies only when a high number of cores are active. On an N-core processor, the limit is in effect when the active core count is N, N-1, N-2, or N-3. For example, on a 12-core processor, the limit is in effect when 12, 11, 10, or 9 cores are active.
The limit applies only when a high number of cores are active. On a processor with `N` cores, the limit is in effect when the active core count is `N`, `N-1`, `N-2`, or `N-3`.
For example, on a 12-core processor, the limit is in effect when 12, 11, 10, or 9 cores are active.

## Set or Change the Turbo Boost Limit Parameter
## Set or change the turbo boost limit parameter

Modify the Boot Orchestration Service \(BOS\) template for the node\(s\). This example below disables turbo boost. The default setting is 999 \(no limit\).

```screen
```json
{
"boot_sets": {
"boot_set61": {
"boot_ordinal": "0",
"ims_image_id": "efdfe6fc-af3f-40f0-9053-dd1ad6c359d3",
"kernel_parameters": "console=tty0 console=ttyS0,115200n8 root=crayfs imagename=/SLES15 selinux=0 rd.shell rd.net.timeout.carrier=40 rd.retry=40 ip=dhcp rd.neednet=1 crashkernel=256M turbo_boost_limit=0",
"network": "nmn",
"node_groups": [
"group1",
"group2"
],
"node_list": [
"x0c0s28b0n0",
"node2",
"node3"
],
"node_roles_groups": [
"compute"
],
"rootfs_provider": "",
"rootfs_provider_passthrough": ""
},
},
"cfs_branch": "my-test-branch",
"cfs_url": "https://api-gw-service-nmn.local/vcs/cray/config-management.git",
"enable_cfs": "true",
"name": "st6",
"partition": "p1"
"boot_sets": {
"boot_set61": {
"boot_ordinal": "0",
"ims_image_id": "efdfe6fc-af3f-40f0-9053-dd1ad6c359d3",
"kernel_parameters": "console=tty0 console=ttyS0,115200n8 root=crayfs imagename=/SLES15 selinux=0 rd.shell rd.net.timeout.carrier=40 rd.retry=40 ip=dhcp rd.neednet=1 crashkernel=256M turbo_boost_limit=0",
"network": "nmn",
"node_groups": [
"group1",
"group2"
],
"node_list": [
"x0c0s28b0n0",
"node2",
"node3"
],
"node_roles_groups": [
"compute"
],
"rootfs_provider": "cpss3",
"rootfs_provider_passthrough": "dvs:api-gw-service-nmn.local:300:nmn0"
},
},
"cfs_branch": "my-test-branch",
"cfs_url": "https://api-gw-service-nmn.local/vcs/cray/config-management.git",
"enable_cfs": "true",
"name": "st6",
"partition": "p1"
}
```

0 comments on commit 2f981a1

Please sign in to comment.