| 96 | | When deploying OS errata, it is not always convenient to deploy them on all nodes at once. In this case, during the errata deployment, you need to temporarily disable profile cloning on the nodes you don't want to upgrade at the same time as the reference profile. This is done by defining in the node profile: |
| 97 | | {{{ |
| 98 | | variable USE_DUMMY ?= false; |
| 99 | | }}} |
| | 96 | When deploying OS errata, it is not always convenient to deploy them on all nodes at once. In this case, during the errata deployment, you need to temporarily disable profile cloning on the nodes you don't want to upgrade at the same time as the reference profile. This can be done by defining variable `USE_DUMMY` to `false` in the profile of the nodes you don't want to clone temporarily. But this can be a significant amount of work if you have many profiles to modify. An alternative is to use variable `WN_DUMMY_DISABLED` which is an nlist where: |
| | 97 | * The key is the string following `PROFILE_PREFIX` in the profile name. The string must be escaped. |
| | 98 | * The value must be `true` in order to desactive profile cloning. |
