OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|1 month ago|
|actions||1 year ago|
|charmhelpers||1 month ago|
|hooks||3 months ago|
|lib||1 year ago|
|scripts||3 months ago|
|templates||4 months ago|
|tests||1 month ago|
|unit_tests||3 months ago|
|.gitignore||1 year ago|
|.gitreview||1 month ago|
|.stestr.conf||2 months ago|
|.zuul.yaml||2 months ago|
|LICENSE||1 year ago|
|Makefile||7 months ago|
|README.md||4 months ago|
|charm-helpers-hooks.yaml||2 months ago|
|config.yaml||4 months ago|
|copyright||1 year ago|
|metadata.yaml||1 month ago|
|requirements.txt||7 months ago|
|setup.cfg||2 years ago|
|test-requirements.txt||2 months ago|
|tox.ini||2 months ago|
This charm provides a service that syncs your OpenStack cloud’s available OS images in OpenStack Glance with the available images from a set of simplestreams mirrors, by default using cloud-images.ubuntu.com.
It will create a user named ‘image-stream’ in the ‘services’ tenant. If swift is enabled, glance will store its images in swift using the image-stream username.
It can optionally also store simplestreams metadata into Swift for future use by juju. If enabled, it publishes the URL for that metadata as the endpoints of a new OpenStack service called ‘product-streams’. If using Swift is not enabled, the product-streams service will still exist, but nothing will respond to requests to its endpoints.
The charm installs a cron job that repeatedly checks the status of related services and begins syncing image data from your configured mirrors as soon as all services are in place.
It can be deployed at any time, and upon deploy (or changing the ‘run’ config setting), it will attempt to contact keystone and glance and start a sync every minute until a successful sync occurs.
This charm requires a relation to keystone. It also requires a running glance instance, but not a direct relation to glance. It connects to glance via its endpoint as published in keystone.
juju deploy glance-simplestreams-sync [--config optional-config.yaml] juju add-relation keystone glance-simplestreams-sync
The charm has the following configuration variables:
run is a boolean that enables or disables the sync cron script. It
is True by default, and changing it from False to True will schedule
an immediate attempt to sync images.
use_swift is a boolean that determines whether or not to store data
in swift and publish the path to product metadata via the
NOTE Changing the value will only affect the next sync, and does not currently remove an existing product-streams service or delete potentially stale product data.
frequency is a string, and must be one of ‘hourly’, ‘daily’,
‘weekly’. It controls how often the sync cron job is run - it is used
to link the script into
region is the OpenStack region in which the product-streams endpoint
will be created.
mirror_list is a yaml-formatted list of options to be passed to
Simplestreams. It defaults to settings for downloading images from
cloud-images.ubuntu.com, and is not yet tested with other mirror
locations. If you have set up your own Simplestreams mirror, you
should be able to set the necessary configuration values.
This is used, optionally, to verify the certificates when in ssl mode for keystone and glance. This should be provided as a base64 encoded PEM certificate.