The readme currently states that a compute node in a multi-node setup
requires the glance-api service to be enabled. But actually
the glance-api service is only required on the controller node where
glance-registry is running.
Running the glance-api service on a node without glance-registry will
even lead to a failure of glance-api, as the glance cache directory
will not be created without enabling glance-registry.
Reviewed: https:/ /review. openstack. org/171239 /git.openstack. org/cgit/ openstack- dev/devstack/ commit/ ?id=e53e1584514 4533debc48b3262 0d420d9f0ece4e
Committed: https:/
Submitter: Jenkins
Branch: master
commit e53e15845144533 debc48b32620d42 0d9f0ece4e
Author: Daniel Gonzalez <email address hidden>
Date: Tue Apr 7 16:44:54 2015 +0200
Fix readme for multi-node setup
The readme currently states that a compute node in a multi-node setup
requires the glance-api service to be enabled. But actually
the glance-api service is only required on the controller node where
glance-registry is running.
Running the glance-api service on a node without glance-registry will
even lead to a failure of glance-api, as the glance cache directory
will not be created without enabling glance-registry.
Change-Id: Ie92533f3333f3f e3e2d747762e60f 2f42a233e79
Closes-bug: #1441198