Skip to content

A tool to help sync glance images between two or more glance-api nodes where local file stores are being used for images

Notifications You must be signed in to change notification settings

rcbops/glance-image-sync

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

39 Commits
 
 
 
 
 
 

Repository files navigation

glance-image-sync

glance-image-sync is a tool to help sync glance images between two or more glance-api nodes using default_store of file (no shared storage). The tool is intended to be run via cron on each glance-api node and requires glance-api to be configured with:

notifier_strategy = rabbit

When run, glance-image-sync will pull messages from the info queue defined by rabbit_notification_topic (default glance_notifications) and then duplicate these messages into queues for each individual glance-api node. The list of glance-api nodes is stored in /etc/glance/glance-image-sync.conf. Once messages have been duplicated, glance-image-sync will pull messages from the node's individual queue. If a message contains an image.update event_type, the image will be copied via rsync from the glance-api node defined by the message's publisher_id. If the message contains an image.delete event_type, the image will simply be removed from the node's local filesystem.

Your /etc/glance/glance-image-sync.conf should look like:

[DEFAULT]
api_nodes = node1,node2,node3,...
rsync_user = someone

API nodes can be specified in /etc/glance/glance-image-sync.conf using a short name or FQDN; both will work as we check for FQDN and then shorten it. However, the glance kombu notifier uses socket.gethostname() for publisher_id, so you will need to ensure that nodes can be accessed by name using short name and FQDN since socket.gethostname() may return short name or FQDN depending on how the system was configured. Additionally, you can optionally specify the ssh user rsync uses to retrieve images. If left unspecified, this will default to the glance user.

When running glance-image-sync, you will need to pass the tool one of the following three arguments:

  • duplicate-notifications
  • sync-images
  • both

duplicate-notifications only connects to the rabbit_notification_topic queue and duplicates messages into queues for each glance-api node defined in /etc/glance/glance-image-sync.conf. sync-images only connects to the node's individual queue and then downloads or deletes images depending on event_type. both is simply a wrapper to both duplicate-notifications and sync-images. Typically, you would cron the job on each glance-api node as follows:

*/5 * * * * /path/to/glance-image-sync.py both

The frequency of the cronjob will need to be adjusted per environment.

About

A tool to help sync glance images between two or more glance-api nodes where local file stores are being used for images

Resources

Stars

Watchers

Forks

Packages

No packages published

Contributors 3

  •  
  •  
  •  

Languages