Presence and IntComm WG

[Jeremy George <>]

  We're going to run the LS (location server) on ser.uits along with 
the proxy/registrar.  We are, to coin a phrase, putting our eggs in one
basket.  This isn't necessarily a bad thing but it does suggest that
we'd be well advised to treat this machine carefully.

  On last Thursday's call Mike suggested we leave the server
in Bloomington rather than submit it to the trip to Indianapolis.
Although this means the server is located at a remote site, which makes
me a little nervous, on balance it does make sense and appears to be
the consensus of the folks I've spoken to.  The only caveat is that we
really need to have someone in Bloomington that we can call on to at
least power cycle the box.

  So, if 1) Mike, you can find someone to do power cycle duty and
2) no one expresses an objection, let's leave ser.uits where it is.

  Following on the theme of treating the box with care I think we ought
to be prepared for disaster recovery.  Suppose we have a hard disk
seize?  We need to be able to build a new ser.uits very quickly.

  Backing up ser.cfg is trivial.  I'll keep a copy on Tracy.  I'll also
backup /var/lib/mysql, I guess at some regular interval.  I'll backup
/usr/local/src and put the tar file on Tracy.  I don't know enough about
the LS software to know what needs to be saved.  Ditto with registration
and calendar related scripts.  Ben, can you do those?  Or tell me what
needs to be saved and I'll keep those files on Tracy.

  What have I missed?

  To make this useful, we have to be able to materialize a machine possibly
in short order.  In a disaster circumstance, can we do this?

- Jeremy

-- 

----------------------------------------------------------------wg-pic-+
For list utilities, archives, subscribe, unsubscribe, etc. please visit the
ListProc web interface at 

    http://archives.internet2.edu/

----------------------------------------------------------------wg-pic--