Sync Modules

    The Multisite functionality of RGW introduced in Jewel allowed the ability tocreate multiple zones and mirror data and metadata between them. are built atop of the multisite framework that allows for forwarding data andmetadata to a different external tier. A sync module allows for a set of actionsto be performed whenever a change in data occurs (metadata ops like bucket oruser creation etc. are also regarded as changes in data). As the rgw multisitechanges are eventually consistent at remote sites, changes are propagatedasynchronously. This would allow for unlocking use cases such as backing up theobject storage to an external cloud cluster or a custom backup solution usingtape drives, indexing metadata in ElasticSearch etc.

    A sync module configuration is local to a zone. The sync module determineswhether the zone exports data or can only consume data that was modified inanother zone. As of luminous the supported sync plugins are ,rgw, which is the default sync plugin that synchronises data between thezones and which is a trivial sync plugin that logs the metadataoperation that happens in the remote zones. The following docs are written withthe example of a zone using elasticsearch sync module, the process would be similarfor configuring any sync plugin

    Configuring Sync Modules

    Create the third zone similar to the Multisite docs, for example

    A sync module can be configured for this zone via the following

    For the various supported tier-config options refer to the docs

    Finally update the period