Administering a multi-region object deployment environment

Use the following information to administer a multi-region object deployment environment.

A multi-region environment consists of several independent storage clusters linked together to provided unified object access. Configuration changes in one cluster which affect the multi-region environment are not automatically distributed to all clusters. The cluster which made the configuration change must export the relevant multi-region data and then the other regions must import that data to sync the multi-region configuration. Changes which affect multi-region are:

Changes to the CES IP pool, such as adding or deleting addresses, which affect the ring layout.
Changes to the object services ports used for the account, container, and object servers (ports 6200-6202).
Creation, deletion, or modification of storage policies.
Changes to the swift.conf configuration file

Use the following commands to manage the configuration of the multi-region environment:

To export the data for the current region so that it can be integrated into other regions, use the following command. The RegionData file created can be used to update other regions:
```
mmobj multiregion export --region-file RegionData
```
The RegionData file is created and it contains the updated multi-region information.
To import the multi-region data to sync the configuration, use the following command. The RegionData must be the file created from the mmobj multiregion export command:
```
mmobj multiregion import --region-file RegionData
```

As part of the export/import commands, a region checksum is printed. This checksum can be used to ensure that the regions are in sync. If the checksums match, then the multi-region configuration of the clusters match. In some cases, the checksums do not match after import. This is because the cluster performing the import had local configuration changes which had not been synced with the other regions. For example, a storage policy was created but the multi-region configuration was not synced with the other regions. When this happens the import command prints a message that the regions are not fully in sync because of the local configuration and that the region data must be exported and imported to the other regions. Once all regions have matching checksums, the multi-region environment is in sync.

An existing region can be completely removed from the multi-region environment. This action permanently removes the region configuration, and the associated cluster cannot rejoin the multi-region environment.

The cluster of the removed region needs to disable object services since it will not be usable as a standalone object deployment.

To remove a previously defined region from the configuration, use the following command:
```
mmobj multiregion remove --remove-region-number RegionNumber
```
The remove command must be run from a different region than the one being removed. The cluster associated with the removed region must cleanup object services as appropriate with the mmces service disable OBJ -a command to uninstall object services.
You can display the current multi-region information using the following command:
```
mmobj multiregion list
```