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

What is the plan for the orchestrator to setup job; start data transfer; change rate? #11

Open
TonyWang123 opened this issue Nov 13, 2017 · 3 comments
Assignees

Comments

@TonyWang123
Copy link
Contributor

I am going to review the current FdtClient to see whether it satisfies all the requirements from the orchestrator.

@fno2010
Copy link
Member

fno2010 commented Nov 13, 2017

Each scheduling result item should cover <flow, src_dtn_management_ip, dst_dtn_management_ip, bw> to start the data transfer and update rate limiting.

@LovingYoung We still need to track the job status after scheduling to update whether the file size (and maybe the job is finished [optional]).

@fno2010
Copy link
Member

fno2010 commented Nov 13, 2017

[2017-11-13 11:45:12,988] [orchestrator] [DEBUG] Applying (job: 0) transfer 10.10.14.6 -> 10.10.14.7 to dtn 131.215.207.190 with rate 99999609

If should work in the simple case now.

@fno2010
Copy link
Member

fno2010 commented Nov 13, 2017

I guess flow.job_id does not point to the real job_id. Let me check it.

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

No branches or pull requests

3 participants