Hello,
While the Cloud SIG is still being established, let's get to actual
work and think of a set of features for a CentOS cloud template.
I am referring here to VMs, not containers (e.g. docker).
This is how I see it so far, please feel free to come with
suggestions/comments/questions.
A - Single partition for simplicity (and lack of good arguments against
it)
- dracut-modules-growroot included so the template partition will
expand to match target, cloud-init in charge of resize2fs
B - To swap or not to swap?
C - "tuned-adm profile virtual-host" which translates to:
- kern.sched_min_granularity_ns 10ms
- kernel.sched_wakeup_granularity_ns 15ms
- vm.dirty_ratio 40%
- vm.swappiness 30
- IO scheduler "deadline"
- fs barriers off
- CPU governor "performance"
- disk readahead 4x
D - tso and gso off on the network interfaces http://s.nux.ro/gsotso
E - network interface remapping (75-persistent-net-generator.rules, BZ
912801)
F - Selinux on. Do we relabel for uniqueness? Seen small VMs run out of
memory while relabelling..
G - PERSISTENT_DHCLIENT="1" (BZ 1011013)
H - Bundle all the paravirt drivers in the ramdisk
(virtio/xen/vmware/hyperv) so the same image can boot everywhere?
I - Per "stack" requirements (e.g. cloudstack relies a lot on root user
and password logins, openstack tends not to, SSH key only logins etc
etc)
That's about all that crosses my mind for now.
Thoughts?
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro