[racktables-users] Re: Adding 'reserved' status to a rack

[...]
> Not necessarily mask it, but show it as reserved. Our 3rd parties
> mainly use it to find out where equipment is located, and if they see
> more than needed, that's ok. We use the same 3rd parties for
> basically everything so sooner or later they'll have to look at
> everything anyway.
[...]

If existing rackspace state diagram isn't going to change much (IOW, to
mount something onto reserved rackspace, one will first have to "free"
it up), implementing a new "R" state should be an easy hack. Are there
other people, who agree, that this extra complexity is necessary? I
don't have a clear opinion on this at the moment.

-- 
    DO4-UANIC

Other related posts: