GeoModelTaskServer

Introduction

Task server for geographical modeling, including Master server and Task IO server.

1. Master server is the task server which has many children computing nodes for sharing several same model services.
2. Task IO server is a sever which is used to receive and dispatch tasks for model users and model computer.

Framework

Overview

Local network version :

Internet version :

Database

table server : for geo-service container

table task : for computing task record

Note 1 Array data paradigm

{
	"StateName": "RUNSTATE",
	"Event": "LOADDATASET",
	"Url": "http://127.0.0.1:8062/data/5c49a1e6b4941b0a5023f3ae",
	"Tag": "FDSDemo"
}

table dataexserver : for data exchange server

Function logic

Container register : Local network

Container register : Internet

Task subscription

API

Data Exchange Server Register

• URL : /dxserver
• Method : POST
• Form :

{
	"port": 8062  // Port
}

• Response :

{
	"result": "suc",
	"code": 1,
	"message": "",
	"data": ""
}

Model Service Container Register

• URL : /server
• Method : POST
• Form :

{
	"mac": "00-01-6C-06-A6-29", // MAC address
	"port": 8060  // Port
}

• Response :

{
	"result": "suc",
	"code": 1,
	"message": "",
	"data": ""
}

Model Service Check

• URL : /server?pid=PID
• Method : GET
• Response :

{
	"result": "suc",
	"code": 1,
	"message": "",
	"data": ""
}

If model service existing, the result is suc and code is 1.

Task Subscription

• URL : /task
• Method : POST
• Form :

{
	"inputs": [], // input data configration
	"username": "[Unknown]",  // usrname 
	"pid": "15ea8a5740fdcfa951eea30579a33c4d"  // PID of model service
}

Each item in inputs see table task, note 1

• Response :

{
	"result": "suc",
	"code": 1,
	"message": "",
	"data": ""
}

If model service existing, the result is suc and code is 1.

Install

Construction ...

Usage

All the functions can be invoked by URL, but we recommend do it by SDK.

Task Usage Workflow

The usage workflow of task shows in the picture below, orange step means it can be used by URL, blue means it can be used by SDK API, and green means both:

The workflow consists of following steps:

Check model service

Check model service existing by model service PID (Model Service Package ID). See [ModelServiceAPI](#/Model Service Check)

Create task

Create a task to run. This task just build in local, and it would request the server. SDK API provides an interface to organize it.

Get data exchange server

Get an available data exchange server from task server. See GeoDataExchangeServer.

Upload data

Updata data exchange to data exchange server. See GeoDataExchangeServer.

Configure data

Configure data with target model service by StateName and Event. The data should be organized by Array, and each item referring to Database, table task, note 1.

Subscribe task

Subscribe a task in task server.

API see Task Subscription

Check status

Check the task status.

• Inited: The task has inited but not started.
• Started: The task has been invoked.
• Finished: The task has been finished and user can download the data.
• Error: Some error happened in task running.

Download data

Download data when it is finished.

Contributors

Founder

Min Chen (chenmin0902@163.com)

Yongning Wen (wenyn@msn.com)

Songshan Yue (yss123yss@126.com)

Fengyuan Zhang (franklinzhang@foxmail.com)

Coder

Fengyuan Zhang (franklinzhang@foxmail.com)

Ming Wang (wangminggis@163.com)

All codes are used in OpenGMS platform