Chapter 10. Setting up cross-site replication

Procedure

1. Log in to an OpenShift cluster.

2. Create a service account.

   For example, create a service account at LON:

   $ oc create sa lon
   serviceaccount/lon created

3. Add the view role to the service account with the following command:

   $ oc policy add-role-to-user view system:serviceaccount:<namespace>:lon

4. If you use a node port service to expose Data Grid clusters on the network, you must also add the cluster-reader role to the service account:

   $ oc adm policy add-cluster-role-to-user cluster-reader -z <service-account-name> -n <namespace>

5. Repeat the preceding steps on your other OpenShift clusters.

Procedure

1. Log in to an OpenShift cluster.

2. Add the service account token for a backup location with the following command:

   $ oc create secret generic <token-name> --from-literal=token=<token>

   For example, log in to the OpenShift cluster at NYC and create a lon-token secret as follows:

   $ oc create secret generic lon-token --from-literal=token=eyJhbGciOiJSUzI1NiIsImtpZCI6IiJ9...

3. Repeat the preceding steps on your other OpenShift clusters.

Procedure

1. Create an Infinispan CR for each Data Grid cluster.
2. Specify the name of the local site with spec.service.sites.local.name.
3. Set the value of the spec.service.sites.local.expose.type field to either NodePort or LoadBalancer.

4. Optionally configure ports with the following fields:

   • spec.service.sites.local.expose.nodePort if you use NodePort.
   • spec.service.sites.local.expose.port if you use LoadBalancer.
5. Provide the name, URL, and secret for each Data Grid cluster that acts as a backup location with spec.service.sites.locations.

6. If Data Grid cluster names or namespaces at the remote site do not match the local site, specify those values with the clusterName and namespace fields.

   The following are example Infinispan CR definitions for LON and NYC:

   • LON

     apiVersion: infinispan.org/v1
     kind: Infinispan
     metadata:
       name: example-infinispan
     spec:
       replicas: 3
       service:
         type: DataGrid
         sites:
           local:
             name: LON
             expose:
               type: LoadBalancer
               port: 65535
           locations:
             - name: NYC
               clusterName: <nyc_cluster_name>
               namespace: <nyc_cluster_namespace>
               url: openshift://api.rhdg-nyc.openshift-aws.myhost.com:6443
               secretName: nyc-token
       logging:
         categories:
           org.jgroups.protocols.TCP: error
           org.jgroups.protocols.relay.RELAY2: error

   • NYC

     apiVersion: infinispan.org/v1
     kind: Infinispan
     metadata:
       name: nyc-cluster
     spec:
       replicas: 2
       service:
         type: DataGrid
         sites:
           local:
             name: NYC
             expose:
               type: LoadBalancer
               port: 65535
           locations:
             - name: LON
               clusterName: example-infinispan
               namespace: rhdg-namespace
               url: openshift://api.rhdg-lon.openshift-aws.myhost.com:6443
               secretName: lon-token
       logging:
         categories:
           org.jgroups.protocols.TCP: error
           org.jgroups.protocols.relay.RELAY2: error

     Important

     Be sure to adjust logging categories in your Infinispan CR to decrease log levels for JGroups TCP and RELAY2 protocols. This prevents a large number of log files from uses container storage.

     spec:
       logging:
         categories:
           org.jgroups.protocols.TCP: error
           org.jgroups.protocols.relay.RELAY2: error

7. Configure your Infinispan CRs with any other Data Grid service resources and then apply the changes.

8. Verify that Data Grid clusters form a cross-site view.

   1. Retrieve the Infinispan CR.

      $ oc get infinispan -o yaml

   2. Check for the type: CrossSiteViewFormed condition.