Chapter 6. Configuring the address space for message routing

1. Start editing the Interconnect Custom Resource YAML file that describes the router deployment.

   $ oc edit -f router-mesh.yaml

2. In the spec section, define the semantics to be applied to addresses.

   Sample router-mesh.yaml file

   apiVersion: interconnectedcloud.github.io/v1alpha1
   kind: Interconnect
   metadata:
     name: router-mesh
   spec:
     ...
     addresses:
     - pattern: */orders  1
       distribution: multicast

   1

   Messages sent to any address that ends with “orders” will be distributed in a multicast pattern.

   The Operator applies the changes to the router network and restarts each Pod.

3. If you have additional router deployment Custom Resources that define routers in the router network, repeat this procedure for each CR.

   Each router in the router network must have the same address configuration.

Procedure

1. Start editing the Interconnect Custom Resource YAML file that describes the router deployment.

   $ oc edit -f router-mesh.yaml

2. In the spec section, add a connector to connect to the broker, a waypoint address to point to the broker queue, and autolinks to create the links to the queue.

   Sample router-mesh.yaml file

   apiVersion: interconnectedcloud.github.io/v1alpha1
   kind: Interconnect
   metadata:
     name: router-mesh
   spec:
     ...
     addresses:
     - prefix: my-queue  1
       waypoint: true
     autoLinks:  2
     - prefix: my-queue
       direction: in
       connection: my-broker
     - prefix: my-queue
       direction: out
       connection: my-broker
     connectors:  3
     - name: my-broker
       host: broker
       port: 5672
       routeContainer: true

   1

   The address (or set of addresses) for which messages should be stored on a broker queue.

   2

   The autolink configuration. It defines the incoming and outgoing links and connection to be used to send and receive the messages on the broker.

   3

   The connection to be used to connect the routers to the message broker.

   The Operator applies the changes to the router network and restarts each Pod.

3. Verify that the router has established the autolinks to the message broker.

   $ oc exec router-mesh-6d6dccb57f-x5cqf -it -- qdstat --autolinks
   AutoLinks
     addr      dir  phs  extAddr  link  status  lastErr
     ====================================================
     my-queue  in   1             26    active
     my-queue  out  0             27    active

4. If you have additional router deployment Custom Resources that define routers in the router network, repeat this procedure for each CR.

   Each router in the router network must have the same address configuration.