GEP training
15
Geohazards Exploitation Platform (GEP) 2015-04-10 New EO Service Development (Scenario 2) Training session Francesco Barchetta, Terradue
Transcript of GEP training
Geohazards Exploitation Platform (GEP)
2015-04-10
New EO Service Development (Scenario 2) Training session Francesco Barchetta, Terradue
1. Why the Geohazards Exploitation Platform ? § Data and Processing discovery : the geobrowser service § Cloud infrastructure access : the cloud dashboard service
2. How to build my first App ready made for GEP § Using Application templates § Designing my Application workflow § Application Descriptor & Run Executables
3. Delivering my processor to users on GEP § Install and test the processor as-a-Service § Sharing processing jobs on the Platform
Processor integration Training contents
WHY THE GEOHAZARDS EXPLOITATION PLATFORM ? "
Ø A platform to support the exploitation of satellite earth observations for geohazards
Ø A community portal helping you to access and exploit geohazards related data and processors
Ø A social place where to share your work
Ø A platform to integrate and run your own processing service
Geohazards Exploitation Platform Mission
The geobrowser is composed of:
Ø The Map, where the user can make search queries and see results
Ø The Contexts areas, to organize views on results
Ø The Results panel, and the user Basket panel
Ø The Processing services panel
Platform services The geobrowser
The Cloud dashboard allows to:
Ø Browse the Virtual Machines created on GEP
Ø Create a new Virtual Machine Ø Create a new ESA Cloud Toolbox for a Data Analysis
Ø Create a new Developer Cloud Sandbox for the Portal integration tools
Platform services The cloud dashboard
HOW TO BUILD MY FIRST APP READY MADE FOR GEP"
Small GitHub survival guide:
Ø Import an application template from GitHub
Ø Change the GitHub remote reference
Ø Commit your work
Ø Synchronise to repository
Settings Working with a Developer Cloud Sandbox
Define your application as a Directed Acyclic Graph
Ø Define inputs type, outputs and transactions
Ø Number of nodes vs Number of inputs
My application The workflow
Ø Job templates
Ø Executable scripts types
Ø Workflow instance
Ø Scope of sources and parameters: exploiting the WPS interface
My application Workflow descriptor
Ø Preparing the environment
Ø Reading the inputs
Ø Calling the processor binaries
Ø Staging out the results
My application Run executables
DELIVERING MY PROCESSOR TO USERS ON GEP"
Ø Installing the Application
Ø Using the ciop-run command
Ø Testing from the Cloud Sandbox Dashboard Ø Web Processing Service (WPS) interface
Ø Finally, ready to be used on GEP
Platform integration Testing the workflow
User operations:
Ø Fill the form with inputs from a Data Package
Ø Run a job with a public visibility
Ø View/download the job results
Platform integration Sharing processing jobs
