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

Denis Ovsienko wrote:

Hello.
We've integrated racktables to our HP ServiceDesk (great work on racktables btw!) and we currently import it into the RackSpace (I 
think, guessing from my memory here) table. However, we're in the


That's cool! Could you consider writing a wikipage to show people, how
two systems make together?
Well, certainly, when I get the time to do so I don't mind making some sort of wiki to show how we've done it and what we did. 
planning of a lot of new racks and we would like a way to flag
rackspace as 'reserved'. We have a lot of 3rd parties that use our
racktables installation for lookups and sometimes they wonder why
there is 20 empty racks, while they are actually reserved for other
usage.


Well, do I get it right, that the goal is masking the whole picture
from 3rd party, letting them see necessary information about their own
assets? Is the following approach sufficient then?
http://racktables.org/trac/ticket/41
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.
Currently we have 19 empty racks, but most of them is already reserved (we're in the middle of a data center move process here). Unfortunately it (the space allocation) doesn't show up in racktables before it has an assigned IP and the necessary information in our Service Desk, hence my question about the possibility to set it as reserved. So in one way it is to help planning, by seeing how much free space we got, and in another way to show my CEO that we don't really have 19 empty racks (cost planning he tells me all the time :-p ) 


BTW, I hope the next "big" feature (tags) to help sorting
many authorization/ownership design shortcomings out in a more natural
way.


Sounds cool!
Oh and btw, I already came up with the idea that we could mark it as 'problem' since we don't currently use that feature, but my CEO 
didn't like the idea (well, actually he didn't like the color).

Any ideas how this could easily be implemented?


We'll have half the answer after couching the question the right way.


Hope I've answered your questions :-)
Another question though, we're still running 14.6, has there been any significant database changes in the mean time? (worried about our integration here) 

There have been some adjustments in SQL schema since 0.14.6, all of them
can be found in upgrade.php file. I'd suggest making a full backup and
then reloading it into independent DB. After the latest code version
upgrades the copy, you'll get an approximate answer without ruining the
production DB down. Can't tell more without knowing the nature of
DB/code changes done. (This is more or less the same for most of
such cases, not only this one)
Ah, doesn't sound to bad, if I remember correct the only manual sql work we do is inserting into RackSpace (couldn't find a function / method for it ) 


--
Erik

Other related posts: