Changeset View
Changeset View
Standalone View
Standalone View
release/tools/ec2.conf
Show All 15 Lines | |||||
# aarch64, so we have to be selective about when we install it. | # aarch64, so we have to be selective about when we install it. | ||||
if [ "${TARGET_ARCH}" = "amd64" ]; then | if [ "${TARGET_ARCH}" = "amd64" ]; then | ||||
export VM_EXTRA_PACKAGES="${VM_EXTRA_PACKAGES} amazon-ssm-agent" | export VM_EXTRA_PACKAGES="${VM_EXTRA_PACKAGES} amazon-ssm-agent" | ||||
fi | fi | ||||
# Set to a list of third-party software to enable in rc.conf(5). | # Set to a list of third-party software to enable in rc.conf(5). | ||||
export VM_RC_LIST="ec2_configinit ec2_fetchkey ec2_loghostkey firstboot_freebsd_update firstboot_pkgs ntpd dev_aws_disk ec2_ephemeral_swap" | export VM_RC_LIST="ec2_configinit ec2_fetchkey ec2_loghostkey firstboot_freebsd_update firstboot_pkgs ntpd dev_aws_disk ec2_ephemeral_swap" | ||||
# Build with a 4.9 GB UFS partition; the growfs rc.d script will expand | # Build with a 4.9 GB partition; the growfs rc.d script will expand | ||||
imp: growfs expands ZFS now? I think rewording this comment requires more thought.
| |||||
Done Inline ActionsThe growfs rc.d script does, yes, though this patch also sets the autoexpand pool property for good measure. markj: The growfs rc.d script does, yes, though this patch also sets the autoexpand pool property for… | |||||
# the partition to fill the root disk after the EC2 instance is launched. | # the partition to fill the root disk after the EC2 instance is launched. | ||||
# Note that if this is set to <N>G, we will end up with an <N+1> GB disk | # Note that if this is set to <N>G, we will end up with an <N+1> GB disk | ||||
# image since VMSIZE is the size of the UFS partition, not the disk which | # image since VMSIZE is the size of the filesystem partition, not the disk | ||||
Not Done Inline ActionsAside, curious why it is an extra 1GB? emaste: Aside, curious why it is an extra 1GB? | |||||
Done Inline ActionsNot totally certain, but it looks like bsdec2-image-upload posts the image size in multiples of GB, so if the filesystem size is a multiple of 1GB then we have to round up to accommodate other partitions. In other words, I think it's a constraint of EC2/EBS? markj: Not totally certain, but it looks like bsdec2-image-upload posts the image size in multiples of… | |||||
# it resides within. | # which it resides within. | ||||
export VMSIZE=5000m | export VMSIZE=5000m | ||||
# No swap space; the ec2_ephemeralswap rc.d script will allocate swap | # No swap space; the ec2_ephemeralswap rc.d script will allocate swap | ||||
# space on EC2 ephemeral disks. (If they exist -- the T2 low-cost instances | # space on EC2 ephemeral disks. (If they exist -- the T2 low-cost instances | ||||
# and the C4 compute-optimized instances don't have ephemeral disks. But | # and the C4 compute-optimized instances don't have ephemeral disks. But | ||||
# it would be silly to bloat the image and increase costs for every instance | # it would be silly to bloat the image and increase costs for every instance | ||||
# just for those two families, especially since instances ranging in size | # just for those two families, especially since instances ranging in size | ||||
# from 1 GB of RAM to 60 GB of RAM would need different sizes of swap space | # from 1 GB of RAM to 60 GB of RAM would need different sizes of swap space | ||||
▲ Show 20 Lines • Show All 142 Lines • Show Last 20 Lines |
growfs expands ZFS now? I think rewording this comment requires more thought.