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

Brian Gallew wrote:

Denis Ovsienko wrote:

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.
I tried doing a quick hack by adding the appropriate css records (in index.php and the render rack file), but it shows up without any additional info like name etc. Could you quickly direct me as to where I would continue hacking?
For my own purposes, if I had to reserve rack space, I'd just create a 42U blank and insert it into the rack. Or two 21U blanks. Or whatever. Add appropriate device notes to say, "Reserved for customer <X> expansion anticipated June '08" or something.
Certainly doable for small scale but we're migrating some data centers and would like a better overview. However, it's not a big deal and if it turns out to be a big puzzle to solve we'll manage without. 


--
Erik

Other related posts: