Contents x
      Managed
      • 25 Jan 2022
      • 1 Minute to read
      • Contributors
      • Print
      • Dark
        Light
      • PDF
      Contents

      Managed

      • Updated on 25 Jan 2022
      • 1 Minute to read
      • Contributors
      • Print
      • Dark
        Light
      • PDF
      Article summary

      Managed Nodes are computationally remote from the EchoStream Cloud, similar to External Nodes.

      Unlike External Nodes, Managed Nodes:

      • Are always implemented as Docker containers.
      • Are strictly defined by a Managed Node Type.
      • Are always run within a Virtual Machine (VMWare, VirtualBox, KVM and Hyper-V are supported).
      • Are fully managed by EchoStream, as is the Managed App that they reside in.

      When you add a Managed Node to a Managed App, EchoStream will automatically create that Node in the Managed App and begin running it.

      Managed Node Type

      Each Managed Node that you create is created using a Managed Node Type. The Managed Node Type can be thought of as a template that you must conform to when creating the Managed Node. Managed Node Types specify the Docker image (with tag) that will excute your Managed Node and the configuration for that Docker image.

      Configuration

      As stated, when you create a Managed Node you must specify a Managed Node Type. Based upon that Managed Node Type you may have to provide the following configuration information.

      AttributeDescription
      configIf your Managed Node Type has a configTemplate, you must provide a config that meets the requirements of that template. The configTemplate is a JSON Schema document, and the config must be a JSON document that can be validated by that Schema.
      mountsDocker containers can use mounts on the host system to store data. These mounts can be single-use and temporal (anonymous mounts) or multi-use and permanent (named mounts). If your Managed Node Type specifies mountRequirements then you must specify mounts that match those requirements.
      portsDocker containers can expose ports that must be mapped to the host system (e.g. - for a server process). If your Managed Node Type specifies portRequirements then you must specify ports that match those requirements.
      What's Next