Site A host_inventory changes
This set up process creates two host_inventory files, one each for sites A and B. Unique values from the Site B file are copied to the Site A file, but prepended with a string (pair_site_) to identify them as belonging to Site B. Similarly, unique values from the Site A file are copied to the Site B file and there also prepended with "pair_site_". At the end of this process, you will have two host_inventory files, each containing its own site's unique values as well as the unique values for the other site.
- Copy the SingleStore groups and hosts from your Site B host_inventory file.
- Edit your Site A Insight Viewshost_inventory file to add groups and hosts copied from the Site B host_inventory file.
- Rename the groups as shown in the example.
NOTE: The groups MUST be prepended with pair_site_ to avoid
interfering with the existing SingleStore groups and hosts in your Site A file. The
Site B SingleStore nodes must be named exactly how they are in the Site B file and
must be reachable from the Ansible server.
Example:
########################################################
### FAILOVER Singlestore CLUSTER NODES ################
#
# NOTE: MUST BE USED WITH "HTAP_MULTI_DC"
# VARIABLES IN SITE_VARS
#
[pair_site_htap_master]
[siteB-masterNodeHostname]
########################################################Site B host_inventory changes
- Copy the SingleStore groups and hosts from your Site A host_inventory file.
- Edit your Site B Insight Viewshost_inventory file to add groups and hosts copied from the Site A host_inventory file.
- Rename the groups as shown in the example.
NOTE: The groups MUST be prepended with pair_site_ to avoid
interfering with the existing SingleStore groups and hosts in your Site B file. The
Site A SingleStore nodes must be named exactly how they are in the Site A file and
must be reachable from the Ansible server.
Example:
########################################################
### FAILOVER Singlestore CLUSTER NODES ################
#
# NOTE: MUST BE USED WITH "HTAP_MULTI_DC"
# VARIABLES IN SITE_VARS
#
[pair_site_htap_master]
[siteA-masterNodeHostname]
########################################################