Details

    • Type: Sub-task
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Out of Date
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: OSGi
    • Labels:
      None

      Description

      In one deploy cycle, bundles must first get installed and then started.
      It generally needs to be discussed how multiple phase deployments should be handled.

        Gliffy Diagrams

          Activity

          Hide
          dmlloyd David Lloyd added a comment -

          The machinery is already in place for multi-phase deployments. It's just a question of requirements and integrating with this process.

          Show
          dmlloyd David Lloyd added a comment - The machinery is already in place for multi-phase deployments. It's just a question of requirements and integrating with this process.
          Hide
          thomas.diesler Thomas Diesler added a comment -

          05:52:25 PM) tdiesler: dmlloyd, how do I detect that all bundles in one set of deployments got installed before I attempt to start them?
          (05:53:17 PM) dmlloyd: well you'd have to use dependencies if that's the behavior you need
          (05:53:43 PM) dmlloyd: the hard part would be knowing what bundles are in a "set of deployments", which is a concept which does not really exist

          Show
          thomas.diesler Thomas Diesler added a comment - 05:52:25 PM) tdiesler: dmlloyd, how do I detect that all bundles in one set of deployments got installed before I attempt to start them? (05:53:17 PM) dmlloyd: well you'd have to use dependencies if that's the behavior you need (05:53:43 PM) dmlloyd: the hard part would be knowing what bundles are in a "set of deployments", which is a concept which does not really exist
          Hide
          thomas.diesler Thomas Diesler added a comment -

          Brian says

          We talked about instead adding a notion of a DeploymentSet. All updates associated with a DeploymentPlan would be associated with the same DeploymentSet. The DeploymentSet could be attached to the DeploymentUnitContext for each deployment, and a callback triggered when the update for each deployment in the set has been applied.

          This is similar to some things that would happen with ear deployments; it's just that instead of using packaging to determine what comprises a set of deployments, we'd be using the fact that they are in the same DeploymentPlan.

          Show
          thomas.diesler Thomas Diesler added a comment - Brian says We talked about instead adding a notion of a DeploymentSet. All updates associated with a DeploymentPlan would be associated with the same DeploymentSet. The DeploymentSet could be attached to the DeploymentUnitContext for each deployment, and a callback triggered when the update for each deployment in the set has been applied. This is similar to some things that would happen with ear deployments; it's just that instead of using packaging to determine what comprises a set of deployments, we'd be using the fact that they are in the same DeploymentPlan.
          Hide
          thomas.diesler Thomas Diesler added a comment -

          Out of Date

          Show
          thomas.diesler Thomas Diesler added a comment - Out of Date

            People

            • Assignee:
              Unassigned
              Reporter:
              thomas.diesler Thomas Diesler
            • Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development