OpenStack Image Management (Glance)
5835b30cc2
Define multiple pipelines in glace-api.conf to reflect the various supported deployment flavors (minimal, with caching, with cache management, with keystone-based auth etc.). Add an optional paste_deploy.flavor config variable to allow the user select the appropriate pipeline without having to edit the paste config (i.e. uncommenting lines as before). For example in glance-api.conf, a setting of: [paste_deploy] flavor = keystone+caching identifies the following pipeline in glace-api-paste.ini: [pipeline:glance-api-keystone+caching] pipeline = versionnegotiation authtoken auth-context cache apiv1app the advantage being that the user need not be concerned with the precise sequence of filters required to realize the QoS they desire. Modify the functional tests that patch configuration (i.e. the keystone and caching tests) to use the new deployment_flavor mechanism. Extend the TestConfigOpts to support option groups. Change-Id: Ide843ada11bce115b7dc650440397853c6409b03 |
||
---|---|---|
bin | ||
doc/source | ||
etc | ||
glance | ||
tools | ||
.bzrignore | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
Authors | ||
LICENSE | ||
MANIFEST.in | ||
pylintrc | ||
README | ||
run_tests.py | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
tox.ini |
====== Glance ====== Glance is a project that defines services for discovering, registering, retrieving and storing virtual machine images. The discovery and registration responsibilities are handled by the `glance-registry` component while the retrieval and storage responsiblities are handled by the `glance-api` component. Quick Start ----------- If you'd like to run trunk, you can clone the git repo: git clone git@github.com:openstack/glance.git Install Glance by running:: python setup.py build sudo python setup.py install By default, `glance-registry` will use a SQLite database. If you'd like to use MySQL, or make other adjustments, you can modify the glance.cnf file (see documentation for more details). Now that Glance is installed, you can start the service. The easiest way to do that is by using the `glance-control` utility which runs both the `glance-api` and `glance-registry` services:: glance-control all start Once both services are running, you can now use the `glance` tool to register new images in Glance. glance add name="My Image" < /path/to/my/image With an image registered, you can now configure your IAAS provider to use Glance as its image service and begin spinning up instances from your newly registered images.