12012-12-09 07:20:12ClintonEbadivaguely useful documentation of our use of kvmAs is the fashion, HCoop is now using KVM managed by Libvirt to make managing our systems much easier. This document represents the state of things, not any best practices. In particular, management of nodes and our network bridging setup probably need work

Some information: We are currently using a single bridge br0 that works atop the primary ethernet. Each kvm is then given a sub-device named br0:$hostname. ClintonEbadi suspects there is something wrong with this. If any network wizards know better, please mail hcoop-sysadmin and let us know.

Account clinton_admin is in the libvirt group on fritz This permits ClintonEbadi to manage kvms as his user remotely using virt-manager. We only have one virtualization node now, and soon will have but two. Therefore adding admins who are permitted to manage libvirt to the groups file on each node isn't the worst thing. We probably should use a config package, domtool, or centralized groups database to make it cleaner. CategorySystemAdministration CategoryNeedsWork