choria/choria

The Choria Orchestrator

A modern Orchestration Engine with roots in The Marionette Collective. Please review the Official Documentation for installation guidance.

Usage

Package Repo and Basic Installation

At present RHEL 5 - 7, Debian Stretch and Ubuntu 16.04 LTS (Xenial Xerus) are supported, the repository also include packages for other tools like our Stream Replicator etc.

It's best configured using Hiera, to install the YUM Repository and install a particular version with some basic adjustments this will be enough.

choria::manage_package_repo: true
choria::version: 0.0.7-1.el%{facts.os.release.major}
choria::srvdomain: prod.example.net
choria::log_level: warn

include choria

Configuring the Choria Server

The Choria Server is a Beta release of what will eventually replace mcollectived, please review the Beta Guide if you wish to test this.

On all your nodes where you wish to run the new service:

choria::server: true
choria::manage_package_repo: true
mcollective::service_ensure: stopped
mcollective::service_enable: false

On all nodes including those that are pure MCollective and your clients:

mcollective_choria::config:
  security.serializer: "json"

Configuring the Choria Broker

In all cases below you need to ensure the choria::broker class is used:

include choria::broker

Configuration for the various scenarios are shown via Hiera, you can run all scenarios on the same instance.

Configure a Standalone Choria Broker

We can now configure a standalone Choria Broker, it will listen on ports 4222, 4223 and 8222 on ::, these are configurable via other properties of choria::broker

Please review the Choria Network Broker documentation for full details.

choria::broker::network_broker: true

Configure a Choria Broker Cluster

To configure a Broker Cluster over port 4223 you can add this data:

choria::broker::network_peers:
  - nats://choria1.example.net:4223
  - nats://choria2.example.net:4223
  - nats://choria3.example.net:4223

This will build a TLs secures Choria Broker Cluster

Configure Federation Brokers

To Federate a network - london - into a Federated Collective you'd run a Federation Broker in the london LAN with the following configuration:

Please review the Federations of Collectives documentation for full details.

choria::broker::federation_broker: true
choria::broker::federation_cluster: london

This will use the SRV domain configured in choria::srvdomain to find the brokers to connect to as per the documentation.

You can configure custom addresses to connec to:

choria::broker::federation_middleware_hosts:
  - choria1.central.example.net:4222
  - choria2.central.example.net:4222
  - choria3.central.example.net:4222
choria::broker::collective_middleware_hosts:
  - choria1.london.example.net:4222
  - choria2.london.example.net:4222
  - choria3.london.example.net:4222

Configure a NATS Streaming Adapter

Given a NATS Stream server with a cluster id prod_stream this will adapt Registration messages received in the Collective to the NATS Stream for processing using Stream Processing patterns.

Please review the Data Adapters documentation for full details.

choria::broker::adapters:
  discover:
    stream:
      type: "natsstream"
      clusterid: prod_stream
      topic: discovery
      workers: 10
      servers:
        - stan1.example.net:4222
        - stan2.example.net:4222
        - stan3.example.net:4222
    ingest:
      topic: mcollective.broadcast.agent.discovery
      protocol: request
      workers: 10