Considerations for Teracloud® Streams development and test environments

If you do not need high availability with automatic recovery from failures, a development or test environment might be your preferred option.

Development or test environment

  • A non-root user installs Teracloud® Streams on each resource or uses a shared file system.

    • If Teracloud® Streams is installed on each resource, you can use either of the following options:
      • Install the main installation package on at least one resource and the domain host installation package on all additional resources.
      • Install the main installation package on all resources.
      The main installation package includes all of the product files. The domain host installation package contains a subset of the product files.

    • If a shared file system such as NFS or GPFS is used, install Teracloud® Streams in a shared directory that is accessible from each resource.

  • Set up the domain controller service on all resources. For more information, see Options for setting up the domain controller service on Teracloud Streams resources.

  • Set up an Apache ZooKeeper server and your user authentication method before you create a Teracloud® Streams enterprise domain.
    • For managing and storing configuration information, Teracloud® Streams requires a ZooKeeper server.
    • For high availability, you can use a Lightweight Directory Access Protocol (LDAP) server or Pluggable Authentication Module (PAM) with the LDAP backend for default user authentication. After creating the domain, you can use the following additional options to customize user authentication:
      • Login module authentication
      • Client certificate authentication