Skip to content

Trade Study Use Case 8 DAP responses for a NASA HDF5 file with contiguous storage

Jump to bottom
kyang2014 edited this page Dec 21, 2016 · 1 revision

Use Case Name

Access the CF-enabled DAP Hyrax DDS, DAS,DMR and Data responses of a NASA HDF5 file with contiguous storage stored at S3

Scope

Hyrax framework installed at Amazon cloud system(EC2+S3)

Level

sub-function

Primary Actor

A NASA Earth Science researcher who would like to access the HDF5 products stored in cloud via the Hyrax OPeNDAP server

Stakeholders and Interests

General public who are interested in retrieving information of NASA HDF5 products via Hyrax, NASA ESDIS and Raytheon BEDI2 project managers

Preconditions

  • Apache Tomcat is installed successfully at EC2  

  • Hyrax is also installed at Amazon EC2 successfully

  • The NASA sample HDF5 file that uses only contiguous storage(One GSSTF file) is put at S3 successfully

  • A Hyrax server is installed at a non-cloud (i.e., local) Linux server and NASA sample HDF5 products should also be put under the non-cloud  (i.e., local) Linux server

  • The HDF5 handler is configured to use the EnableCF option for the Hyrax servers installed at Amazon EC2 and non-cloud Linux server

Minimal Guarantee

For DAP2 under the configuration of the CF option of the HDF5 handler

  •  DDS and DAS output of the sample NASA HDF5 file from EC2+S3 are the same as those obtained from the Hyrax service on a non-cloud Linux server

  •  The binary output of Data response (including both with and without expression constraint) from chosen variables of one sample NASA HDF5 file are the same as those obtained from the Hyrax service on a non-cloud Linux server

Success Guarantee

For both DAP2 and DAP4 under the configuration of the CF option the HDF5 handler

  • DDS, DAS output from the sample NASA HDF5 file from EC2+S3 are the same as those obtained from the Hyrax service on a non-cloud Linux server

  • The binary output of DAP2 Data response (including both with and without expression constraint) from chosen variables of the sample NASA HDF5 file are the same as those obtained from the Hyrax service on a non-cloud Linux server

  • DMR output from the sample NASA HDF5 file from EC2+S3 are the same as those obtained from the Hyrax service on a non-cloud Linux server

  • The binary output of DAP4 Data response (including both with and without expression constraint) from chosen variables of the sample NASA HDF5 file are the same as those obtained from the Hyrax service on a non-cloud Linux server

  • The time and the expense of a DAP response from cloud can be measured

Trigger

When a user checks the DAP responses from EC2+S3 with a curl script at a Linux or MacOS machine that serves as a client.

Main Success Scenario

Using Curl

  1. Obtain the DDS,DAS and data values from the examined variables of the sample NASA files with the curl command from the non-cloud Hyrax server.

time curl -s http://localhost:8081/opendap/s3/dap/cloudydap/samples/GSSTFYC.3.Year.1988_2008.he5.das -o gsstf_local.das time curl -s http://localhost:8081/opendap/s3/dap/cloudydap/samples/GSSTFYC.3.Year.1988_2008.he5.dds -o gsstf_local.dds time curl -s http://localhost:8081/opendap/s3/dap/cloudydap/samples/GSSTFYC.3.Year.1988_2008.he5.dods\?lon,lat,NCEP_SST -o gsstf_local_d2_ll.bin time curl -s -g http://localhost:8081/opendap/s3/dap/cloudydap/samples/GSSTFYC.3.Year.1988_2008.he5.dods\?lat\[0:100:719\],lon\[0:100:1339\],NCEP_SST\[0:100:719\]\[0:100:1339\] -o gsstf_local_d2_ss.bin ``` 2. Run the curl scripts on a linux or MacOS client machine that check the sample NASA files for the Hyrax server installed on the EC2+S3.

```

time curl -s http://52.55.197.86:8080/s3/dap/cloudydap/samples/GSSTFYC.3.Year.1988_2008.he5.das -o gsstf.das time curl -s http://52.55.197.86:8080/s3/dap/cloudydap/samples/GSSTFYC.3.Year.1988_2008.he5.dds -o gsstf.dds time curl -s http://52.55.197.86:8080/s3/dap/cloudydap/samples/GSSTFYC.3.Year.1988_2008.he5.dods\?lon,lat,NCEP_SST -o gsstf_d2_ll.bin time curl -s -g http://52.55.197.86:8080/s3/dap/cloudydap/samples/GSSTFYC.3.Year.1988_2008.he5.dods\?lat\[0:100:719\],lon\[0:100:1339\],NCEP_SST\[0:100:719\]\[0:100:1339\] -o gsstf_d2_ss.bin

3. The curl output from the EC2+S3 should be the same as the curl output from the non-cloud Hyrax server.

$diff gsstf_local.das gsstf.das $diff gsstf_local.dds gsstf.dds $diff gsstf_local_d2_ll.bin gsstf_d2_ll.bin $diff gsstf_local_d2_ss.bin gsstf_d2_ss.bin

Clone this wiki locally