Airflow/WPS-T integration

[mike-gangl]

Airflow/WPS-T integration

Integrate airflow and the WPS-T process spec

Will allow for deploy, undeploy, execute, status from a WPS-T frontend

Acceptance Criteria

Acceptance criteria required to implement the epic

• OGC processes model updated to include POST/DELETE on /processes endpoint
• Deploy App Pacakge (deploy process) to airflow
• Undeploy App Pacakge (undeploy process) from airflow
• Execute App Pacakge (execute process) within airlfow
• Status app run (process status) within airflow
• Deployed process has its own DAG defined in airflow for tracking of metrics
• inputs are passed form WPS request into CWL execution
  • naming convention and mapping probably matters here?

Work Tickets

Link to work tickets required to implement the epic

• [ ] TBC (to be created)

Dependencies

Other epics or outside tickets required for this to work

• [ ] TBC

Associated Risks

links to risk issues associated with this epic

• [ ] TBC

[rtapella]

• https://github.com/unity-sds/unity-sps/issues/47
• https://github.com/unity-sds/unity-sps/issues/48
• https://github.com/unity-sds/unity-sps/issues/61
• https://github.com/unity-sds/unity-sps/issues/62

[mike-gangl]

Register work of a generic CWL file will push this into 24.3. This won't require a user to write a DAG to get the system working.