Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor Tendrl Jobs system for more performance #162

Open
r0h4n opened this issue Jun 12, 2017 · 1 comment
Open

Refactor Tendrl Jobs system for more performance #162

r0h4n opened this issue Jun 12, 2017 · 1 comment

Comments

@r0h4n
Copy link
Contributor

r0h4n commented Jun 12, 2017

Current:

  • Every job (internal or user created) goes to /queue
  • Every "new" job in /queue is processed by all tendrl-node-agent and integration (ceph, gluster) agents and tendrl-performance-monitoring and tendrl-node-monitoring agents
  • Every job is matched against the above agent's tags (read capabilities) and the
  • Child jobs save a pointer to them in Parent_job.children

Proposed change:

  • Each job is posted at a location in central store calculated on the basis of "tag" defined for the Tendrl Flow on which the job is based or the node_id of the tendrl-node-agent (if targeted towards specific node)
  • Parent jobs should contain child jobs entirely inside :job_id/children/
  • Create an index with job_id: job_location (location as calculated in pt1 above)
  • Differentiate between internal jobs and user created jobs in above index

This impacts the current internal tendrl jobs, user created tendrl jobs (from api), tendrl job processing

spec branch: "spec/refactor_jobs"

@r0h4n r0h4n self-assigned this Jun 12, 2017
@r0h4n
Copy link
Contributor Author

r0h4n commented Jun 12, 2017

cc: @Tendrl/tendrl-core , @Tendrl/tendrl_api

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants