tasks:lab-extras
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| tasks:lab-extras [2026/07/16 15:36] – akraitman | tasks:lab-extras [2026/10/02 19:08] (current) – djgalloway | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| lab-extras is a repo of miscellaneous packages we want testnodes to have access to. | lab-extras is a repo of miscellaneous packages we want testnodes to have access to. | ||
| - | http:// | + | https:// |
| An example of a time we'd want to use this is when a package from CentOS 7.3 has a bugfix we want to test on CentOS 7.2. The RPM can be downloaded from the CentOS 7.2 CM (testing) repo, placed in the CentOS 7 lab-extras repo and installed. | An example of a time we'd want to use this is when a package from CentOS 7.3 has a bugfix we want to test on CentOS 7.2. The RPM can be downloaded from the CentOS 7.2 CM (testing) repo, placed in the CentOS 7 lab-extras repo and installed. | ||
| Line 35: | Line 35: | ||
| - | # Micron NVMe Firmware Management | + | ===== Micron NVMe Firmware Management |
| This page describes how the Micron NVMe firmware used by trial nodes is managed. | This page describes how the Micron NVMe firmware used by trial nodes is managed. | ||
| - | ## Supported firmware | + | ===== Supported firmware |
| - | | Drive family | Target firmware | + | | Drive family |
| - | | ------------ | --------------- | + | | Micron 7450 |
| - | | Micron 7450 | E2MU300 | + | | Micron 7500 |
| - | | Micron 7500 | E3MQ005 | + | |
| The testnode Ansible role automatically detects supported Micron drives and upgrades them when the installed firmware is older than the target version. | The testnode Ansible role automatically detects supported Micron drives and upgrades them when the installed firmware is older than the target version. | ||
| - | ## Firmware directory layout | + | ===== Firmware directory layout |
| Firmware images are stored in the `lab-extras` repository using the following directory structure: | Firmware images are stored in the `lab-extras` repository using the following directory structure: | ||
| - | ```text | + | < |
| micron-nvme-firmware/ | micron-nvme-firmware/ | ||
| ├── 7450/ | ├── 7450/ | ||
| Line 60: | Line 59: | ||
| └── E3MQ005/ | └── E3MQ005/ | ||
| └── Micron_7500_E3MQ005_release.ubi | └── Micron_7500_E3MQ005_release.ubi | ||
| - | ``` | + | </ |
| When adding support for a new firmware release, create a new version directory instead of replacing the existing files. For example: | When adding support for a new firmware release, create a new version directory instead of replacing the existing files. For example: | ||
| - | ```text | + | < |
| 7450/ | 7450/ | ||
| └── E2MU400/ | └── E2MU400/ | ||
| └── Micron_7450_E2MU400_release.ubi | └── Micron_7450_E2MU400_release.ubi | ||
| - | ``` | + | </ |
| - | + | ||
| - | ## Updating the firmware files | + | |
| - | + | ||
| - | Follow the existing **Managing packages in lab-extras** documentation for publishing new files to the lab-extras repository. | + | |
| - | + | ||
| - | *Link:* `docker-mirror: | + | |
| This page intentionally does not duplicate those instructions. | This page intentionally does not duplicate those instructions. | ||
| - | ## Updating the Ansible role | + | ===== Updating the Ansible role ===== |
| When a new firmware version is released: | When a new firmware version is released: | ||
| - | 1. Upload the firmware image to the appropriate directory in `lab-extras`. | + | 1. Upload the firmware image to the appropriate directory in lab-extras. |
| - | 2. Update the target firmware version in `roles/ | + | |
| + | 2. Update the target firmware version in roles/ | ||
| 3. Update the firmware filename if necessary. | 3. Update the firmware filename if necessary. | ||
| + | |||
| 4. Verify on a trial node that the firmware is detected and upgraded successfully. | 4. Verify on a trial node that the firmware is detected and upgraded successfully. | ||
| - | ## Verifying firmware | + | ===== Verifying firmware |
| Check the currently installed firmware: | Check the currently installed firmware: | ||
| - | ```bash | + | < |
| nvme list | nvme list | ||
| - | ``` | + | </ |
| or | or | ||
| - | ```bash | + | < |
| nvme fw-log / | nvme fw-log / | ||
| - | ``` | + | </ |
| Example: | Example: | ||
| - | ```text | + | < |
| Firmware Log for device: | Firmware Log for device: | ||
| frs1 : E2MU300 | frs1 : E2MU300 | ||
| - | ``` | + | </ |
| or | or | ||
| - | ```text | + | < |
| Firmware Log for device: | Firmware Log for device: | ||
| frs1 : E3MQ005 | frs1 : E3MQ005 | ||
| - | ``` | + | </ |
| - | ## Notes | + | ===== Notes ===== |
| * Slot 1 is read-only on supported Micron drives. | * Slot 1 is read-only on supported Micron drives. | ||
| + | |||
| * Firmware is committed to slot 2 using activation action 3. | * Firmware is committed to slot 2 using activation action 3. | ||
| + | |||
| * The Ansible role skips non-Micron NVMe devices automatically. | * The Ansible role skips non-Micron NVMe devices automatically. | ||
tasks/lab-extras.1784216181.txt.gz · Last modified: by akraitman