OAM Hardware Conference Call
6 May 2010
- David Bitner
- Don Brutzman
- Mifan Careem
- Kate Chapman
- John Crowley
- Schuyler Erle
- Jeff Johnson
- Mark Prutsalis
- Don McGregor
- Travis Pinney
- Zach Rouse
- Gavin Treadgold
- Andrew Zaborowski
Two uses of OAM
- Store and serve tiles
- Storage of raw imagery
Debate over Operating System: Solaris or Linux distro
- Solaris: provides ZFS which can support billions of files and easy to scale storage. Reduces the number of people who contribute to administration of the system.
- Linux: easier to develop on and admister, but has file system issues (corruption) with large numbers of files.
- 1 Week: Have a Linux box up for development
- 1 Month: attach a Solaris ZFS storage server. No one will have administration rights to this storage outside NPS, with aid/advice from Jeff and Travis.
- What we want as an OAM Initial Software Stack
- OSSIM, Map Server? We need to bring these issues to the public list.
Initial Data Sets For now, we will focus on quality, georectified imagery. We will look at kites and hobbyist imagery in the future. We will serve a developer community that wishes to use tiles in their applications. We have to document provenance of data, and our documentation has to be provable against a challenge.
- Landsat Imagery
- NAIP Imagery. Public Domain. The cost (cost recovery issues) are being investigated.
- Legal advice on how to make the data policy bulletproof.
Opportunities to Learn
- NPS will abide by decisions of the group. Only veto power is the information security team at NPS, which can pull the plug.
- DISA has standards for OpenSolaris. Travis had to handle this issue, Don McGregor is now facing it.
- Ask Sun Microsystems/Oracle about building out a network of OpenSolaris experts who can help with configuration and architecture.