3 ms·

> (I don't really know what Amazon does under the hood to their Linux distro, but it does show) If it's on AWS hardware I assume they've extremely trimmed down

> (I don't really know what Amazon does under the hood to their Linux distro, but it does show) If it's on AWS hardware I assume they've extremely trimmed down any and all kernel gubbins that isn't related to the hardware they run on? As for our migration plans... Well luckily we're on CentOS 7, so I have a year or so more to figure that one out and see what way the wind blows. Timings good enough to do a hardware refresh at the same time. Kinda worried for Ansible to be completely honest. I've grown to love it for automating a bunch of sysadmin tasks and managing some stuff at work and my own kit, It's been a nice way to spin up dev boxes w/o going down the whole Kube/Container stack when a VM suffices. Don't really trust RedHat anymore with it if IBM is pushing it's corporate culture down on them.

InvaderFizz 5y ago
I'm sure it trims many things down to a general VM baseline, but they can't trim all the different hypervisor hardware support. Unbeknownst to many, you can run AmazonLinux on-prem[0], AWS distributes their image on a public pages (we use this to allow developers to have the same image locally and on the cloud). Additionally, you can export any AMI to a S3 bucket[1] and download that for local use. 0: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-linux-2-virtual-machine.html https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-l... 1: https://docs.aws.amazon.com/vm-import/latest/userguide/vmexport_image.html https://docs.aws.amazon.com/vm-import/latest/userguide/vmexp...
- stewartesmith 5y ago
  For Amazon Linux, the recipes are slightly different for the AMI versus on-Prem. For the AMI we cut out a bunch of things from the initramfs that you don’t typically need in a cloud environment saving a further second (ish) of launch time. This config is in the Dracula-config-ec2 package. For on-Prem you may actually use this, so we don’t build it in there.

InvaderFizz 5y ago

I'm sure it trims many things down to a general VM baseline, but they can't trim all the different hypervisor hardware support. Unbeknownst to many, you can run AmazonLinux on-prem[0], AWS distributes their image on a public pages (we use this to allow developers to have the same image locally and on the cloud). Additionally, you can export any AMI to a S3 bucket[1] and download that for local use. 0: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-linux-2-virtual-machine.html https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-l... 1: https://docs.aws.amazon.com/vm-import/latest/userguide/vmexport_image.html https://docs.aws.amazon.com/vm-import/latest/userguide/vmexp...

stewartesmith 5y ago
For Amazon Linux, the recipes are slightly different for the AMI versus on-Prem. For the AMI we cut out a bunch of things from the initramfs that you don’t typically need in a cloud environment saving a further second (ish) of launch time. This config is in the Dracula-config-ec2 package. For on-Prem you may actually use this, so we don’t build it in there.