Description of problem:
Original oVirt Node when used with the older oVirt Server (written as a Ruby on Rails mgmt application) would grab configuration information dynamically on boot, meaning that we never needed to 'install oVirt Node to a hard disk'
We'd like to bring this stateless mode of operation back to oVirt Node when used in conjunction with vdsm and oVirt Engine.
This will involve having a 'Config Server' that can be accessed by each Node's management interface. Details on this feature will be posted on the wiki and a link posted in this bz.