Hi Carsten, what about the idea to give classes only usable for disk layouts??
Regards, \sh On Thu, 25 Jun 2009 18:19:08 +0200 Carsten Aulbert <[email protected]> wrote: > Hi, > > I have the following problem. Imagine I have about 20 machines which > are defined in under classes as (with case $(hostname) around it): > > > group*) > echo "CLASS_A CLASS_B CLASS_C CLASS_D" > > Then I have a few nodes out of these which need to get a differnt disk > layout, but apart from this, they they should be exactly the same, > thus I put this before the line above: > > group*4) > echo "CLASS_A CLASS_B CLASS_C CLASS_D CLASS_E" > > Hoever, now I have the problem that there are conflicting disk > configurations: > > disk_config/CLASS_D as well as disk_config/CLASS_E > > I have not found the place yet where this is decided, since the first > time I tested this on one box, it just worked and I never made it work > on another box. > > Right now I only see two ways out here: > > (1) use the hostname as the disk_config/NAME as this seems to be a > high priority class > (2) create a disk_config for each group, e.g. > > disk_config/GROUP_STANDARD and disk_config/GROUP_SPECIAL > > and edit the files defiening the classes to refelct this. > > However, it would be nice to give priorities to classes, is this > possible somehow? > > Cheers > > Carsten -- | Stephan '\sh' Hermann | OSS Dev / SysAdmin | | JID: [email protected] | http://www.sourcecode.de/ | | GPG ID: 0xC098EFA8 | http://leonov.tv/ | | FP: 3D8B 5138 0852 DA7A B83F DCCB C189 E733 C098 EFA8 |
