Uploaded image for project: 'SEBA'
  1. SEBA
  2. SEBA-462

Handle service removal

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Resolved (View Workflow)
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: February
    • Component/s: NEM
    • Labels:
      None

      Description

      When a service is removed, its data needs to be deleted from the core. This may involve running delete steps in the synchronizer. Therefore it's not sufficient to destroy a synchronizer container and assume the models can be deleted afterward – some coordination needs to take place to ensure the models are cleaned up before the synchronizer container can exit.

      • The core should not honor a service removal request while service models exist.
      • A tool or API call should be provided that initiates destruction of all service models. Either the operator can use this tool prior to initiating service removal (proactively cleaning up the models), or the core can initiate the tool on demand.
      • Once models are cleaned up, the synchronizer can exit.

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            Assignee:
            scottb Scott Baker
            Reporter:
            scottb Scott Baker
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: