diff --git a/common/configuration/main.tf b/common/configuration/main.tf index fd9d87ba..c8c544cd 100644 --- a/common/configuration/main.tf +++ b/common/configuration/main.tf @@ -125,7 +125,6 @@ locals { public = tls_private_key.ed25519[values.prefix].public_key_openssh } } - mig = lookup(values.specs, "mig", null) } ) } diff --git a/common/configuration/puppet.yaml b/common/configuration/puppet.yaml index 63d0c98c..c33b7e2b 100644 --- a/common/configuration/puppet.yaml +++ b/common/configuration/puppet.yaml @@ -122,12 +122,6 @@ runcmd: - "(tar xf aws-efa-installer-latest.tar.gz && cd aws-efa-installer && ./efa_installer.sh --yes --minimal)" - rm -fr aws-efa-installer aws-efa-installer-latest.tar.gz %{ endif } -%{ if mig != null } -# Install nvidia-mig-manager to enable MIG without NVIDIA drivers installed - - yum -y install https://github.com/NVIDIA/mig-parted/releases/download/v0.5.5/nvidia-mig-manager-0.5.5-1.x86_64.rpm -# It does not matter which config is selected, the goal here is to enable MIG before reboot - - nvidia-mig-parted apply -f /etc/nvidia-mig-manager/config.yaml -c all-1g.5gb --mode-only -%{ endif } %{ if cloud_provider == "gcp" } # Google Cloud user-data fact generates a warning because its size is greater than what is allowed (<4096 bytes). # We have no use for it, so we remove startup-script, user-data and user-data-encoding when running in GCE. diff --git a/docs/README.md b/docs/README.md index 23f57451..c0cfe108 100644 --- a/docs/README.md +++ b/docs/README.md @@ -868,8 +868,14 @@ if previously instantiated. **default_value** = `false` -Determines whether the base image packages will be upgraded during the first boot or not. By default, -all packages are upgraded. If `skip_upgrade` set to `true`, no package will be upgraded on first boot. +If true, the base image packages will not be upgraded during the first boot. By default, +all packages are upgraded. + +**Note 1**: Do not skip package upgrade if the infrastructure includes instances +with specialized hardware like a GPU or an Infiniband adapter. These devices generally +require the compilation of dynamic kernel modules ([DKMS](https://en.wikipedia.org/wiki/Dynamic_Kernel_Module_Support)), +with the latest kernel headers. + **Post build modification effect**: No effect on currently built instances. Ones created after the modification will take into consideration the new value of the parameter to determine