1 / 9

LP DAAC Subsetter Status

LP DAAC Subsetter Status. July 11, 02. HEW Subsetting Appliance Status. Installed V1.07, V1.08, V1.08 Patches for Ralph & Fetch Currently testing with HSA V1.09 Installed for about 2 weeks Subsetter is working okay Input and output directories are being populated, PDR created

Download Presentation

LP DAAC Subsetter Status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. LP DAAC Subsetter Status July 11, 02

  2. HEW Subsetting Appliance Status • Installed V1.07, V1.08, V1.08 Patches for Ralph & Fetch • Currently testing with HSA V1.09 • Installed for about 2 weeks • Subsetter is working okay • Input and output directories are being populated, PDR created • SAM is communicating • EPD is not establishing contact with subsetter • PAN is not delivered from SDSRV; java errors • Intermittent machine errors on temporary subsetter box (signal 11) • Subsetter box e0dus01 will be delivered next week • SPOT will be added to new box, run for MODIS data types, and passing data types will be added to Registry • Will establish an ECS account for Matt and Bruce to expedite troubleshooting

  3. HEW Subsetting Appliance Status (cont.) • Troubleshoot EPD and establish PDR distribution • Compare subsetted products with original products for various data types • Obtain a version of HSA with a HEW interfaces for HEG integration, OR obtain HSA source code and create an interface. • PDS interface will be required for subsetted media products (development required)

  4. e0dus01 BOM Input from BOM Quote: Configuration: A30-WRF4-08GQF A30-WRF4-08GQF Sun Fire V880 Server 4 @ 750 MHz, 8 GB memory, 6 - 36.4 GB, 1.0", 10,000 RPM, FC-AL disks, DVD, 3 (N+1 redundant) power supplies and redundant cooling fan trays. Standard Configuration X311L Localized Power Cord Kit North American/Asian X3768A PGX64 24-bit Color Frame Buffer, Software on CD, Video adapter cable Solaris 2.5.1, .6, 7 & Solaris 8 (PCI systems only) X6541A Dual-channel differential UltraSCSI host adapter, PCI; includes two 2m SCSI cables X6727A PCI Dual FC Network Adapter with internal FC interface. 100MB/s per channel with optical interface. SLS9S-120-W9YM Solaris PC NetLink 1.2 For all new Enterprise servers. no license required, Unlimited Client Access, Media Kit, Documentation in HTML. English and Localized Solaris 2.6, 7 and 8  VVMGS-999-W999 VERITAS Volume Manager License on Solaris, for Desktop and Workgroup Server Class, RTU Only  VXVMS-320-9999 VERITAS Volume Manager 3.2 on Solaris, Media Kit and Documentation  X3538A Type 6 Country Kit includes keyboard for US Unix/Unix Universal /European Unix layout for systems with USB interface. Power cables, USB mouse, and mouse pads are included.  X6751A Sun Fire V880 Expansion Disk Backplane with 6 - 36.4 GB, 1.0", 10,000 RPM FC-AL disks and required cables - NOT ENOUGH DISK !!  X7143A 17-inch Entry color monitor, 15.7" diagonal viewable area, .28mm dot pitch, 1152x900 @ 66/76Hz, 1024x768 @ 60/77Hz, 30-75kHz, MPR-II, TCO'99, DDC1/2B, VESA DPMS, digital OSD, universal power supply ww agency compliances Standard version  X311L Localized Power Cord Kit North American/Asian  X6755A Sun Fire V880 Cable to connect the (X)6727A - PCI to dual FC-AL host bus adapter with one internal connector - to the second/alternate FC-AL loop of the internal storage array.

  5. EDC Issues/Concerns • DAAC Requires Operation scenarios to be demonstrated by system – will ESS require additional Ops staff? • Capacity, performance, error handling/recovery, usability, operability • Previous PDS experience suggests this is a large task!!! • Media distribution is currently not part of the plan – only FTP • Need interface to PDS oracle Dbase? – load granules at “ECS Received” state • Utilization/Sharing of staging disk may be an issue • Use ESS Raid as storage area for PDS media creation – who cleans up? • Raid to small?? • Schedule has been slipping • Science is pushing for this capability

  6. EDC Issues/Concerns • ECS Distribution approach is unacceptable? • Impact on B&A – will DDIST send 2nd email to DORRAN? • Level of effort require to add an additional subsetter to the UAH control layer; i.e., how much effort to add MRT or HEG? • Is this being provided? • ESDIS and DAAC Metrics • Input granule orders vs. End user orders will be direct • How will input orders be “Tagged” to separate from customer in ECS dbases? • EDGRS reporting scripts will need to be updated (external vs. from archive) • Reporting of subsetter use, patterns, size, user choices, etc…. • ECS – ODL ordering convention for Product Request (multi datasets) • Single granule on single line item convention • Multiple Granules in a single product request ODL is not compliant to ODL ICD. • ECS – Spatial Subscriptions will they work with ESS? • No subscriptions available at this time

  7. EDC Issues/Concerns • ESDIS ECHO “Expectations Management” from NASA • ECHO looking for “true” external subsetter independent from the data provider • as-is architecture will not support this • Site Acceptance – how managed • Formal Site Acceptance plan required? • Integration Test – installation exercise, checkout testing • Site Acceptance – Functional, e-t-e, off nominal • Operational Readiness Exercise – ops run in • Formal Science “Quality” checkout • Will products be “Science Quality”

  8. EDC Issues/Concerns • CM Baseline Management – OSS Process • UAH delivers to NSIDC for Integration Period Integration • ECS CM Baselines NSIDC Public Release Version Initial Version • UAH COTS package delivery to ECS CM Patches • ECS CM Deploys to DAACs with new versions Delivery • Utilize existing CM process for TT/NCRs • ECS forwards NCRs to UAH development team • DAAC SOW and funding availability ? • Set-up, integration, testing, operations of new system • DAACs DUE development for additional appliances • Who pays for development on PDS integration

  9. EDC Issues/Concerns

More Related