Our friend Matt posts some interesting pointers for openQRM deployments. This could make your competitors turn green with envy! I have already proposed openQRM to our international project and we are making good progress there.
Check out Matt's post.
1. Server consolidation
With its automated provisioning technics openQRM takes server consolidation to the next level. By abstracting the data-center services into virtual environments including their hard- and software-profile plus deployment parameters such as number of systems, cpu/memory requirements, high-availability and eventual service-level agreements openQRM assists the system-administrator to find unused and/or under-utilized resources to either power them down or to migrate their services to other servers.
2. Service consolidation
openQRM supports to automatically consolidate critical services in a high-available way. In an active/passive setup openQRM will automatically fail-over its server-services so that services integrated within openQRM via a plugin automatically gain high-availability.
Let's have an example with the following critical services in a data-center :
dhcpd-server for ip-address assignment
tftp-server for network booting
puppet-server for configuration management
nagios-server for enhanced monitoring
linuxcoe-server for automatic installations
Normally a system-administrator would setup 5 dedicated servers plus 5 hot-standbys to provide high-availability in active/passive mode.
Check out Matt's post.
Comments
Post a Comment