Skip to content

Instantly share code, notes, and snippets.

@krotkiewicz
Created August 30, 2016 16:33
Show Gist options
  • Save krotkiewicz/ca9d86fd94c862c1e40236a824d67f63 to your computer and use it in GitHub Desktop.
Save krotkiewicz/ca9d86fd94c862c1e40236a824d67f63 to your computer and use it in GitHub Desktop.
Workflow Deployment:
1. User deploys with version1
2. Dash generates deploy_id1 and send it to builder to build image, builder reponds with success
3. Dash stores deploy_id1 and version1 for that project
4. Dash returns version1 to user
Workflow Scheduling via Dash:
1. User sends request to dash to schedule spider1
2. Dash sends request to JobQ with version1 and deploy_id1, JobQ responds with success and creates job1 with version1 and deploy_id1
3. When job1 should be run, JobQ sends request to Kumo Scheduler with deploy_id1 and version1
4. Kumo Scheduler obtains image from deploy_id1 and sucessfuly runs the job
Workflow Scheduling via JobQ
**User has only version1**
1. User sends requests to JobQ to schedule spider1 with version1, JobQ responds with success and creates job1 with version1 (?)
2. When job1 should be run, JobQ sends request to Kumo Scheduler with version1
3. Kumo Scheduler obtains deploy_id1 from Dash settings.json endpoint
4. Kumo Scheduler obtains image from deploy_id1 and sucessfuly runs the job
Workflow Scheduling via Dash (no deploy_id yet genereated)
1. User sends request to dash to schedule spider1
2. Dash sends request to JobQ with version1, JobQ responds with success and creates job1 with just version1 (?)
3. When job1 should be run, JobQ sends request to Kumo Scheduler with version1
4. Kumo Scheduler requests deploy_id from Dash settings.json endpoint
5. Dash does not have deploy_id yet so it sends version1 as deploy_id (?)
6. Kumo Scheduler obtains image from deploy_id1 and sucessfuly runs the job
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment