Skip to content

Commit

Permalink
Remove mig-manager install from puppet.yaml
Browse files Browse the repository at this point in the history
  • Loading branch information
cmd-ntrf committed Mar 25, 2024
1 parent a50ccda commit 77ee2a8
Show file tree
Hide file tree
Showing 3 changed files with 8 additions and 9 deletions.
1 change: 0 additions & 1 deletion common/configuration/main.tf
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,6 @@ locals {
public = tls_private_key.ed25519[values.prefix].public_key_openssh
}
}
mig = lookup(values.specs, "mig", null)
}
)
}
Expand Down
6 changes: 0 additions & 6 deletions common/configuration/puppet.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
10 changes: 8 additions & 2 deletions docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 77ee2a8

Please sign in to comment.