Consider removing the orchestrator for provisioning Apps #254

Activity

1. mebster

   self-assigned this

   on Aug 2, 2017
2. mebster

   added

   S04 Proposed for Sprint

   on Aug 2, 2017
3. konstan commented on Aug 3, 2017

   

   konstan

   on Aug 3, 2017

   Member

   More actions

   • 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.
4. mebster

   added

   S02 Top of Backlog

   and removed

   S04 Proposed for Sprint

   on Jul 25, 2018