Unified Map to Define Job Interface

Registered by Elise Gafford on 2015-01-02

This blueprint proposes the addition of an "interface" map to the API for
job creation, such that the operator registering a job can define a unified,
human-readable way to pass in all arguments, parameters, and configurations
that the execution of that job may require or accept. This will allow
platform-agnostic wizarding at the job execution phase and allows users to
document use of their own jobs once in a persistent, standardized format.

Blueprint information

Status:
Complete
Approver:
Sergey Lukjanov
Priority:
Medium
Drafter:
Elise Gafford
Direction:
Approved
Assignee:
Elise Gafford
Definition:
Approved
Series goal:
Accepted for liberty
Implementation:
Implemented
Milestone target:
milestone icon 3.0.0
Started by
Sergey Lukjanov on 2015-03-11
Completed by
Sergey Lukjanov on 2015-07-28

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/unified-job-interface-map,n,z

Addressed by: https://review.openstack.org/144802
    Unified Map to Define Job Interface

Addressed by: https://review.openstack.org/175486
    Add data source subtypes to unified job interface map spec

Addressed by: https://review.openstack.org/187809
    [WIP][EDP] Unified Map to Define Job Interface

Addressed by: https://review.openstack.org/188047
    Removing JobExecutionArgument Table

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.