Skip to content
This repository has been archived by the owner on Nov 15, 2019. It is now read-only.

[WIP] [COMMENTS?] [Edgent-112] cleanup JobMonitorApp #299

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

dlaboss
Copy link
Member

@dlaboss dlaboss commented Mar 15, 2017

As noted in the JIRA there are other issues with the class as well.

  • migrate submitApplication() and closeJob() to new utils.ExecutionMgmt
    • not sure about the new api:utils for this class. Originally had it in a runtime.utils but that didn't seem right (logically it's just convenience over some api defined services), then moved it to api:execution.utils but that introduced circular dependency, so created api:utils and put it there. Is the new api:utils OK?
  • change ApplicationServiceMXBean.submit to return the created job's id
  • add JobMonitorApp.createAndRegister (the idiom used elsewhere)
  • adjust IotProvider to use both of the above...
    • and then remove IotProvider's addition of JobMonitorProvider. See commentary in IotProvider and EDGENT-397
  • some other general cleanup

As noted in the JIRA there are other issues with the class as well.

- migrate submitApplication() and closeJob() to new
runtime.utils.TopologyMgmt
- related, change ApplicationServiceMXBean.submit to return the created
job's id
- add JobMonitorApp.createAndRegister (the idiom used elsewhere)
- adjust IotProvider to use both of the above
- remove JobMonitorApp.submit() and adjust things
- some other general cleanup
execution.utils.ExecutionMgmt created a circular dependency created with
topology
- do early detection of JobManagerApp usage requirements
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant