4 ms·
My team at a Very Large Software Company runs CoreOS for two main reasons: 1. Reduced attack surface due to a very slim OS with no package manager. 2. CoreOS
by dharmab 7y ago
My team at a Very Large Software Company runs CoreOS for two main reasons:
1. Reduced attack surface due to a very slim OS with no package manager.
2. CoreOS Ignition, a killer app OS provisioning/customization tool. No weird barely-documented kickstart scripts, and no long build and upload times for OS images. We can make changes/customizations to our OS and have them deployed in a cloud within literally minutes. We consider this a competitive advantage.
- m4rtink 7y agoI think kickstart is quite well documented, both upstream and in RHEL: https://pykickstart.readthedocs.io/en/latest/https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/sect-kickstart-syntax https://pykickstart.readthedocs.io/en/latest/https://access.... Any concrete examples of stuff the existing docs do not cover ?
- dharmab 7y agoI've maintained both kickstart and ignition professionally. The documentation and readability of Ignition is absolutely way better than kickstart. A simple example would be downloading a binary file and checking it's hash during boot, with retries if the connection is flaky. Three lines of declarative state in Ignition vs complex scripting in kickstart.
- m4rtink 7y agoIdeally one uses mainly kickstart commands to configure the system during the installation - then the installer (Anaconda) takes care for everything for you. If you use custom scripts with kickstart, you are pretty much on your own, like with any other custom script. BTW, maybe open an RFE to include a helper script in the installation environment for easy & robust file downloading ?