Skip to content

Trade Study Use Case 1 DAP2 with CF

Jump to bottom
kyang2014 edited this page Nov 14, 2016 · 1 revision

Use Case Name

Access the CF-enabled DAP2 Hyrax DDS, DAS and Data responses of NASA sample HDF5 products 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

  • All NASA sample HDF5 products are 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 one 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 DAP2 under the configuration of the CF option the HDF5 handler

  • DDS, DAS output from all sample NASA HDF5 files 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 one 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.

$curl -s http://localhost:8080/s3/dap/cloudydap/airs/AIRS.2015.01.01.L3.RetStd_IR001.v6.0.11.0.G15013155825.nc.h5.das -o airs_local.das $curl -s http://localhost:8080/s3/dap/cloudydap/airs/AIRS.2015.01.01.L3.RetStd_IR001.v6.0.11.0.G15013155825.nc.h5.dds -o airs_local.dds $curl -s http://localhost:8080/s3/dap/cloudydap/airs/AIRS.2015.01.01.L3.RetStd_IR001.v6.0.11.0.G15013155825.nc.h5.dods\?Latitude,Longitude,Topography -o airs_local_d2_ll.bin $curl -s -g http://localhost:8080/s3/dap/cloudydap/airs/AIRS.2015.01.01.L3.RetStd_IR001.v6.0.11.0.G15013155825.nc.h5.dods\?Topography\[0:20:179\]\[0:20:359\] -o airs_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.

```

$curl -s http://52.55.197.86:8080/s3/dap/cloudydap/airs/AIRS.2015.01.01.L3.RetStd_IR001.v6.0.11.0.G15013155825.nc.h5.das -o airs.das $curl -s http://52.55.197.86:8080/s3/dap/cloudydap/airs/AIRS.2015.01.01.L3.RetStd_IR001.v6.0.11.0.G15013155825.nc.h5.dds -o airs.dds $curl -s http://52.55.197.86:8080/s3/dap/cloudydap/airs/AIRS.2015.01.01.L3.RetStd_IR001.v6.0.11.0.G15013155825.nc.h5.dods\?Latitude,Longitude,Topography -o airs_d2_ll.bin $curl -s -g http://52.55.197.86:8080/s3/dap/cloudydap/airs/AIRS.2015.01.01.L3.RetStd_IR001.v6.0.11.0.G15013155825.nc.h5.dods\?Topography\[0:20:179\]\[0:20:359\] -o airs_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 airs_local.das airs.das $diff airs_local.dds airs.dds $diff airs_local_d2_ll.bin airs_d2_ll.bin $diff airs_local_d2_ss.bin airs_d2_ss.bin

Clone this wiki locally