Skip to content

Latest commit

 

History

History

agent

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
README.md
README.md
 
 
config.go
config.go
 
 
config.yaml
config.yaml
 
 
http_handler.go
http_handler.go
 
 
server.go
server.go
 
 

README.md

Chorus agent

Serves webhook on port :9673 to receive push notifications from s3. Then converts received s3 bucket notification to chorus replication task and puts it into chorus work queue to be later processed by Chorus worker. Can be used as alternative to Chorus proxy.

Usage

Set proper url, fromStorage, and redis credentials to config and deploy agent to be reachable by source S3 storage.

Important

Make sure that chorus-worker and chorus-agent are using the same Redis instance.

Note

Worker is required to use CLI. Deploy worker and provide worker GRPC api address to CLI.

With CLI:

  • check that agent successfully registered itself and can be listed with CLI: 
    chorctl agent
  • use FROM_STORAGE and PUSH_URL from previous command output to create replication policy:
chorctl repl add --from="<src_storage_name>" --to="<dest_storage_name>" --user="<s3 user>" --bucket="<bucket name>" --agent-url="PUSH_URL"
  • Chorus will automatically configure bucket notifications in source storage for given bucket and URL (tested with AWS S3 and Ceph RGW).
  • Now all changes from the source storage will be propagated to the destination.

See also