README.md

pkg - Component (Container, HCD, Assembly) Packaging

This project deals with the packaging of components, such as Containers, HCDs and Assemblies.

See OSW TN009 - "TMT CSW PACKAGING SOFTWARE DESIGN DOCUMENT" for the background information.

Containers and their components can be created from a configuration file (in HOCON format) by calling ContainerComponent.create(config) and passing it the Config object for the file.

Alternatively, you can pass a ContainerInfo object describing the container to the create() method.

Components are controlled by a Supervisor actor that handles lifecycle messages to determine the state of the component (Components that are not in the Running state, do not receive commands, for example).

A demo/test can be found in the multi-jvm directory and run with: sbt "project pkg" multi-jvm:test

Container Config Files

Here is an example of a config file for creating a container with the name Container-1 that contains one assembly (named Assembly-1) and depends on the services of two HCDs (HCD-2A and HCD-2B). The assembly is implemented by the given class TestAssembly. A Supervisor actor will be created to manage the assembly, which includes registering it with the location service, using the given name and prefix. The prefix can be used to distribute parts of the configurations to different HCDs. HCDs register themselves with the Location Service and specify a unique prefix that can be used for this purpose.

container {
  name = Container-1
  components {
    Assembly-1 {
      type = Assembly
      class = csw.services.pkg.TestAssembly
      prefix = tcs.base.assembly1
      connectionType: [akka]
      connections = [
        // Component connections used by this component
        {
          name: HCD-2A
          type: HCD
          connectionType: [akka]
        }
        {
          name: HCD-2B
          type: HCD
          connectionType: [akka]
        }
      ]
    }
  }
}

Below is an example config file for the container with the HCDs referenced in the above example. In this case, HCD-2A and HCD-2B are both implemented by the TestHcd class.

container {
  name = "Container-2"
  components {
    HCD-2A {
      type = HCD
      class = csw.services.pkg.TestHcd
      prefix = tcs.base.pos
      connectionType: [akka]
      rate = 1 second
    }
    HCD-2B {
      type = HCD
      class = csw.services.pkg.TestHcd
      prefix = tcs.ao.pos.one
      connectionType: [akka]
      rate = 1 second
    }
  }
}

HCDs publish their status by calling the notifySubscribers() method. Any actor that wishes to be notified about an HCDs status can subscribe to these messages. An Assembly can subscribe to it's HCD's status by overriding the allResolved() method (allResolved() is called once the locations of all the assembly's connections have been resolved):

  /**
   * Called when all HCD locations are resolved.
   * Overridden here to subscribe to status values from the HCDs.
   */
  override protected def allResolved(locations: Set[Location]): Unit = {
    subscribe(locations)
  }

The HCDs can publish their current state by calling notifySubscribers() with a CurrentState object, or by receiving a CurrentState actor message (from a worker actor), which is automatically handled by the parent trait.

For examples, see the TestAssembly in the multi-jvm test and the csw-pkg-demo project or the Java based javacsw-pkg-demo project.