Skip to content

Trade Study Use Case 5 FileOut netCDF output

Jump to bottom
H. Joe Lee edited this page Jan 11, 2017 · 1 revision

Use Case Name

Output netCDF-4 files with the CF-enabled DAP2 Hyrax FileOut netCDF 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 

  • netCDF-4 is installed at Amazon EC2 and non-cloud Linux server successfully

Minimal Guarantee

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

  • The output netCDF-4 file generated by the Hyrax filenetCDF module from one sample NASA HDF5 file on EC2+S3 is the same as the netCDF-4 file generated by the Hyrax service on a non-cloud Linux server

Success Guarantee

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

  • The output netCDF-4 files generated by the Hyrax filenetCDF module from all sample NASA HDF5 files on EC2+S3 are the same as the netCDF-4 files generated by the Hyrax service on a non-cloud Linux server

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

Trigger

When a user checks the filenetCDF output 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 netCDF-4 files via the Hyrax filenetCDF module from the sample NASA HDF5 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.nc4 -o airs_local.nc4

```

  1. 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.nc4 -o airs.nc4

3. The netCDF4 file obtained from the EC2+S3 should be the same as the netCDF4 file obtained from the non-cloud Hyrax server.

$h5diff airs_local.nc4 airs.nc4

Clone this wiki locally