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

Consider removing the orchestrator for provisioning Apps #254

Open
mebster opened this issue Aug 2, 2017 · 1 comment
Open

Consider removing the orchestrator for provisioning Apps #254

mebster opened this issue Aug 2, 2017 · 1 comment
Assignees
@mebster
Labels
S02 Top of Backlog

Comments

@mebster
Copy link
Contributor

mebster commented Aug 2, 2017

Related to the reduction of supported connectors (#253)

What about build image?
@mebster mebster self-assigned this Aug 2, 2017
@konstan
Copy link
Member

konstan commented Aug 3, 2017

  • SS starts VM with node executor (NE)
  • NE does the needful to produce the increment
  • NE does a minimal local cleanup
  • NE declares done to SS and asks to persist the increment
  • SS calls IaaS to produce new image
  • SS recovers the new image ID and sets it on the module for the cloud

SS "takes" the role of the orchestrator: provision VM, create image on IaaS, recover image ID and set on the module.
NE runs 1.-3. App Workflow steps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mebster mebster

Labels
S02 Top of Backlog
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@konstan @mebster