Minutes (please refactor!):
Minutes
cshields:
why are we here
OSDL rackview
inventory.o.o
giem:
search by OS? what applications (Java)
kirsten:
contact question
andy:
delegate entering of information
cshields:
ports lighting
less that we have to do
andy:
don't want to maintain all this much
kirsten:
we would be able to see what's been done, who's the contact
cshield:
if hit by bus
claym:
maintain: module to integrate this (but no external api) get the email from maintain for the inventory app – pushing hard though ... cron job
—
designing paradigm
wiki:
perl (from rackview)
better searching?
query builder
not only way to make queries, though
giem:
query for who is plugged in to what port
kirsten:
right tool?
claym:
not bad idea
Alex and I: modular
kirsten:
existing
giem:
expensive! used them
claym:
next level out
flag a rack
andy:
inventory is buckets
hard is visual
claym:
yes
tom:
could generate table easily?
giem:
storage bin view
claym:
why modular
make a `storage room' module
emsearcy:
not just buckets
claym:
modular means that module can define what it can do
virtual machines?
cshields:
yes
andy:
what do we want to track?
giem:
layers: physical, logical (virt machine)
kirsten
link for documentation from servers
tom:
opennms
kirsten:
not just docu, URLs
cshields:
what we need: info
andy:
child relationships
otherwise: attributes
Tangent?: ITIL
so modular that you could tie in external services
kirsten: guest view
emsearcy:
not just a link: imbedded content
cshields:
start with nms
claym:
solid base so that the platform can support whatever modules we need it to
cshields:
split functionality
cacti: console vs. usage
emsearcy:
cfengine
claym:
want we want to do
coho -> rackview
cshields:
drupal: remove modularity
contact database (mysql -> ldap -> civiccrm)
what do we want rackview to look like
claym:
start with uploading static images, then selectable regions (flickr), then dynamic
andy:
grid
cshield:
grid first, image map next
andy:
sarcastic: google earth integration
winds down ...
alex: thanks all
