<html>
<head>
<style type="text/css">
<!--
body { margin-bottom: 1px; margin-right: 4px; margin-top: 4px; margin-left: 4px; line-height: normal; font-variant: normal }
p { margin-bottom: 0; margin-top: 0 }
-->
</style>
</head>
<body style="margin-bottom: 1px; margin-right: 4px; margin-top: 4px; margin-left: 4px">
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">We're Linux through and through, sorry on the windows thing, I feel for you.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">Debian is our (currently) preferred poison.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">In between the lines, I'm wondering about providing dedicated device(s) for OSGEO use, could be used, could be new, could be mixed. Does it make some sense to think about it possibly as redundant node(s), that could possibly take over if needed.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">I was wondering about Blades vs separate CPU's as well. You prefer Blades, or anything goes, etc. I would need to figure out how to balance one time setup vs long term support. Preferably, we would setup and forget. Don't have the manpower resources currently to go much beyond this offer right now. Can't really address the admin/VM stuff at all, nor do we want to at this time, but the co-locating is a real possibilty (offsite datacenter and independent vendor, NOT City).</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">What would be desirable based on the descriptions here?</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">Maybe this is not the right time to think about this.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">bobb</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<br>
<br>
>>> Frank Warmerdam <warmerdam@pobox.com> wrote:<br> </p>
<div style="margin-bottom: 0; padding-left: 7px; border-left: solid 1px #050505; margin-top: 0; margin-right: 0; margin-left: 15px; background-color: #f3f3f3">
<p style="margin-bottom: 0; margin-top: 0">
Bob Basques wrote:<br>><br>><br>> All,<br>><br>><br>> So, here I am  . . .<br>><br>><br>> I've got some questions about the OSGEO hardware infrastructure.<br>><br>> Mostly right now, what is it's current state of operation?<br><br>Bob,<br><br>There is some information on the current systems and services<br>available at:<br><br>   <a href="http://wiki.osgeo.org/wiki/SAC_Service_Status">http://wiki.osgeo.org/wiki/SAC_Service_Status</a><br><br>It does not fully reflect damage from the recent blade outage.<br><br>In particular at this time I believe xblades 10, 11, 13 and 14<br>are compromised.  John is trying to re-install 13 which we use<br>as the download server normally.  Most services on 14 should<br>likely be migrated to the Projects VM or elsewhere.<br><br>It is my intention that xblade11 would be re-setup as a buildbot<br>server (build and smoke test).  I'm not sure to what extent we<br>will want to save the buildbot configurations from xblade11 and<br>xblade14.  Mateusz has normally been the lead on buildbot stuff<br>but I get the impression he has limited time available.<br><br>There will be some admin needs for the download server once it<br>is working again. In particular setting up anonymous ftp<br>(for ftp.remotesensing.org), rsync service (for backup/mirroring),<br>webdav services (so the java maven updates work), and perhaps<br>putting the special throttling settings in place.  There has also<br>been a long standing suggestion this server should be doing nightly<br>antivirus scans that would be nice to pursue.<br><br>The above steps are the ones I have hesitated to put in place<br>on the current download "backup server".<br><br>Other outstanding tasks as part of the Peer1 to OSU OSL migration that<br>I don't see having been addressed yet are migration of LDAP, and<br>email service + mailman.<br><br>Some discussion of this migration are available at:<br><br>   <a href="http://wiki.osgeo.org/wiki/Infrastructure_Transition_Plan_2010">http://wiki.osgeo.org/wiki/Infrastructure_Transition_Plan_2010</a><br><br>> Looking to see where I might be able to offer up some help, with<br>> infrastructure stuff, newer hardware, network connection, etc.  I'm not<br>> Admin, but  . . . could possibly have some leads on things if I had a<br>> good idea about the current (future) shortcomings.<br>><br>> Is this all out of scope for the current difficulties?  Would asking<br>> later on be better?<br><br>One item that has come up as desirable but surprisingly hard to address<br>is a decent windows server that can be remotely administered and used<br>for windows build tests, shared build environment, etc.   If you had a<br>dependable reasonable well resourced machine with good network<br>connectivity you were willing to provide in this role (and perhaps<br>provide some admin support for), that would be helpful.<br><br>Best regards,<br>--<br>---------------------------------------+--------------------------------------<br>I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam@pobox.com<br>light and sound - activate the windows | <a href="http://pobox.com/~warmerdam">http://pobox.com/~warmerdam</a><br>and watch the world go round - Rush    | Geospatial Programmer for Rent<br><br>_______________________________________________<br>Sac mailing list<br>Sac@lists.osgeo.org<br><a href="http://lists.osgeo.org/mailman/listinfo/sac">http://lists.osgeo.org/mailman/listinfo/sac</a><br>
</p>
</div>
</body>
</html>