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.

Sign up for GitHub

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

Jump to bottom

[#3149] Job Submission from Tosca to Chronos/Mesos #34

Closed
7 tasks done
lorenzo-biava opened this issue May 10, 2016 · 2 comments
Closed
7 tasks done

[#3149] Job Submission from Tosca to Chronos/Mesos #34

lorenzo-biava opened this issue May 10, 2016 · 2 comments
Assignees
@lorenzo-biava
Labels
1 priority feature
Milestone
1.0

Comments

@lorenzo-biava
Copy link
Contributor

lorenzo-biava commented May 10, 2016 •
edited
Loading

https://project.indigo-datacloud.eu/work_packages/3149

  • Minimal creation WF (create jobs and wait for completion or error)
  • Minimal deletion WF (delete jobs from an existing deployment)
  • INDIGO 'tosca.nodes.indigo.Container.Application.Docker.Chronos' node properties, image artifact, host requirement support
  • Jobs dependencies (as TOSCA nodes dependencies)
  • Inputs replacement in TOSCA
  • [ ] Output replacement in TOSCA ? Not required for now
  • Jobs status
  • OneData properties replacement (hard-coded + from properties file)
  • [ ] OneData properties replacement (hard-coded + from site choice) See [#3164] Support for the Data Location Scheduling (OneData) #55
  • [ ] Unit tests See Increase unit & integration tests coverage #56
@lorenzo-biava lorenzo-biava added this to the 1st release milestone May 10, 2016
@lorenzo-biava lorenzo-biava self-assigned this May 10, 2016
lorenzo-biava added a commit that referenced this issue May 13, 2016
@lorenzo-biava
Import 'chronos-client' dependency in POM
dc461eb 
See #34
lorenzo-biava added a commit that referenced this issue May 18, 2016
@lorenzo-biava
[WIP] Add basic support for Chronos jobs submission from TOSCA
7201b70 
Beware that a lot of thing are hard-coded (e.g. the jobs dependencies)
and stubs for prototyping purpose.

See #34
lorenzo-biava added a commit that referenced this issue May 19, 2016
@lorenzo-biava
Disabled Chronos deployment update (not supported)
6bb3dbb 
See #34
lorenzo-biava added a commit that referenced this issue May 19, 2016
@lorenzo-biava
Add template hard-coded OneData params replacement
8e3c6c8 
OneData properties are temporarily loaded from properties file

See #34
@lorenzo-biava
Copy link
Contributor Author

lorenzo-biava commented May 19, 2016 •
edited
Loading

Future improvement: get Mesos task status and stdout + stderr (e.g. contact Mesos directly and look for task with name=ChronosTask:<chronos-task-name>

lorenzo-biava added a commit that referenced this issue May 19, 2016
@lorenzo-biava
Add non-existent jobs Chronos deployment failure
e8a3875 
See #34
@lorenzo-biava
Copy link
Contributor Author

Also see #41

lorenzo-biava added a commit that referenced this issue May 23, 2016
@lorenzo-biava
Add Chronos jobs dependencies through 'parent_job' capability
66f2ca3 
See #34
lorenzo-biava added a commit that referenced this issue May 23, 2016
@lorenzo-biava
Add single Chronos jobs status update
4b2ecb7 
See #34
lorenzo-biava added a commit that referenced this issue May 24, 2016
@lorenzo-biava
Merge pull request #40 from indigo-dc/feat/chronos
bad9a25 
[WIP] Implements [#3149] Job Submission from Tosca to Chronos/Mesos #34
lorenzo-biava added a commit that referenced this issue May 25, 2016
@lorenzo-biava
Fix Chronos job deletion (don't fail if the job doesn't exist)
7b35d92 
See #34
@lorenzo-biava lorenzo-biava mentioned this issue May 31, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lorenzo-biava lorenzo-biava

Labels
1 priority feature
Projects
None yet
Milestone
1.0
Development

No branches or pull requests
1 participant
@lorenzo-biava