Hi guys, hereinafter some useful packages and/or use flag to apply on sabayon server release and on sabayon desktop release for improve :
1) currently sabayon release doesn't provide package about mariadb -galera (an enhancement of mariadb database with support to galera plugin that permit manage of cluster of database with innodb engine). I think that currently mariadb-galera is the best cluster solution for Mysql database and it is an error doesn't provide package about this on sabayon repository above all on sabayon server release. 2) Module app-emulation/qemu doesn't include these use flags: +glusterfs (for add support on directly use glusterfs library for integ ration to glusterfs filesystem. Else it use fuse feature with bad performance) +nfs (add NFS support) +rbd (add support to ceph block filesystem) On openstack platform currenctly I use qemu with gluster and nfs. 3) on sabayon release automatically zfs module is installed inside /usr/lib/modules-load.d/zfs.conf. I think that this is not useful on sabayon-desktop where often zfs filesystem is not used and also inside sabayon vm. Also, I think that could be correct avoid install of zfs.conf file inside /usr/lib/modules-load/ directory on every upgrade of the syste. Every time I upgrade sabayon vm I need remember to remove or rename zfs.conf to avoid load of zfs kernel module. Same thing for xen modules. Best solution is handle these files under modules-load.d directory through eselect but this require a develop of eselect extension and related ebuild. As first solution could be fine remove automatic install of zfs.conf file. 4) Module app-emulation/libvirt doesn't include these use flags: +glusterfs (support of gluster filesystem) +lxc (support to linux container) +rbd (support to ceph block filesystem) +virtualbox (support to virtualbox) +fuse (support to fuse... this with less priority) I use these flags with openstack platform and on sabayon-server release colud 4) Avoid automatic activation of cronyd daemon. On my sabayon vm I configured systemd-timesyncd or ntpd daemon for time sync but on upgrade vm I see that cronyd is been automatically activated as a service. This avoid then that previous configuration of systemd -timesyncd and ntpd works correctly. Do you think that is correct activate automatically this service on upgrade of the system ? 5) Journald configuration: Default installation of systemd (from gentoo portage) doesn't provide any smart configuration of systemd-journald service because doesn't configure systemd-journald to handle log rotate or something like this. So, if a user doesn't reconfigure this file after some days will optain a disk full. This, is a problem on ebuild but fwik systemd ebuild is been overwrite from sabayon release, so could be fine correct this file at least 6) I could be fine add kernel options: - ipset modules (I currently use ipset with iptables) - nfsv4.1 support - enable CONFIG_NET_CLS_CGROUP For now it is all. Thanks My cent. G.
