[ https://ovirt-jira.atlassian.net/browse/OVIRT-636?page=com.atlassian.jira... ] Barak Korren commented on OVIRT-636: ------------------------------------ We can also create the zram drive and do the mounts in the job code... I think its best to let the job create and destroy things because that will ensure things get cleaned. But - we need to ensure we keep cache directories around, so maybe we need both - move caches to RAM on host startup and write them back to disk periodically and on shut-down. And have the job workspaces be put on ram and destroyed after every run. IIRC /var/lib/lago is the local cache directory that is bind-mounted into the Mock chroot, so that need to me moved to RAM on boot and synced back to disk. The rest of the job I/O seems to indeed happen in /var/lib/mock and /home/jenkins so we can consider placing a ram drive there each time the job starts. But /home/jenkins might be tricky because it may be used for other stuff (the slave binary for example), so we should probably just dynamically create a ram-drive for $WORKSPACE at the job level. One way to move things into RAM at boot time is to use '/etc/sysconfig/readonly-root' and '/etc/rwtab', this has the benefit of making the hosts mostly stateless, but may also make changing configuration a little tricky. -- This message was sent by Atlassian JIRA (v1000.148.3#100005)