Since we are in ocata lets remove all old parameters in api
to configure the keystone_authtoken section
Change-Id: I4dc0bd544f91fd52ad437b4c3ebbd16a43895726
It's possible for glance-api to get stuck in a loop starting when
the backend is swift, and python-swiftclient is not present on
the system.
Depends-On: I65fb0736e9fa9e68c3c7877cf6caf228c49eb82d
Change-Id: I1eeb9f12cf82961ae820067ad8fe91d096d1d6e1
Closes-bug: #1632143
We need options to be able to set the user and project domain
when using keystone v3 credentials for the swift backend. Without
these options keystone v3 swift will fail.
Change-Id: Id384b0eca750e0946b42cb8ccb60a7f9ed64d21a
This patch adds posibility to configure backend settings for Glare
service.
Since Glare service is experimental feature, it can be usually disabled
for deployment. Hence was added a optional parameter 'glare_enabled' for
each backend manifest. So, if Glare is enabled glance glare config
will (and should) have same backend options as main glance api config.
Change-Id: I112a332f490d2e57eef5fa7d41d465c0eb89da04
Related-bug: #1555697
This change updates the glance tests to use rspec-puppet-facts to test
multiple operating systems.
Change-Id: I75fd8970ba8335cb4ffa09a7d600415056e9f889
This commit explicitly sets default protocol to http in
swift_store_auth_address variable for Swift backend, because without
any specified protocol it will use https by default. That's not
consistent with other default values for protocols in auth addresses.
Change-Id: I232536d179db92d82f1c7459a0f13e5ca5576f42
For working with Swift backend, Glance needs authentication parameters,
which are supplied to Swift when making calls to its storage system.
Glance will use information from the file specified under parameter
swift_store_config_file. When this parameter is set to the same file
(glance-api.conf), we have lot of non-critical errors in glance-api
log, because of 'Invalid format of swift store config'.
The same problem, when we have RadosGW.
Change-Id: I18ee8f68f7ce793d2580685e79ed636556c57ddd
Related-bug: #1540890
The swift_store_config_file option is being set in the DEFAULT
group instead of the glance_store group where it is actually
defined in Glance. This causes configuration of the Swift store
backend to fail because the configuration is not found by the
check here:
https://github.com/openstack/glance_store/blob/master/glance_store/_drivers/swift/utils.py#L66
Moving the option to glance_store makes the Swift backend work again.
Change-Id: I3af198e5015df1d626c4a5aaccb3b4e5781f56b8
Closes-Bug: 1532352
This change adds possibility to use the os_service_default
fact for configuration options that default to '<SERVICE DEFAULT>'.
this change is done by analogy with cinder
commit 667e6c0850672dbbf99381eb92468f95e5591913
Change-Id: Ie5c8909bcc1c9a6a7a9ab1b59eec4637751ffd74
Currently, when Glance uses Swift as backend, all references to
images saved in database with credentials, like:
swift+http://services%3Aglance:EF3tluYM@192.168.0.2:5000/v2.0/glance/049cd701-77
The problem is that when we want to change Glance credentials we can't use
old images anymore, because new credentials and creds in database are
different. For resolving this issue was implemented patch in Glance [1]
and couple of patches in Glance_Store [2,3]. The main goal is using
separate section (file with such section) for providing credentials
for access to Swift and do not place reference with credentials to
database.
All changes above are covered in docs for configuring Swift backend [4].
Also glance_cache_config now is not using for configuring Swift backend,
hence all related parameters for this config removed.
[1] https://review.openstack.org/#/c/98722/
[2] https://review.openstack.org/#/c/193422/
[3] https://review.openstack.org/#/c/108036/
[4] https://review.openstack.org/#/c/242583/
Change-Id: Iaf0c1c6f2188c84267e41d2d4f9bda0dbf3dccad
Related-bug: #1499754
This patch aim to update our specs test in order to work with the rspec-puppet release
2.0.0, in the mean time, we update rspec syntax in order to be prepared
for rspec 3.x move.
In details:
* Use shared_examples "a Puppet::Error" for puppet::error tests
* Convert 'should' keyword to 'is_expected.to' (prepare rspec 3.x)
* Fix spec tests for rspec-puppet 2.0.0
* Upgrade and pin rspec-puppet from 1.0.1 to 2.0.0
* Clean Gemfile (remove over-specificication of runtime deps of puppetlabs_spec_helper)
Change-Id: Ibd0333dc3c0959e846edfbad51fb48e8dfb8fbe9
Card: https://trello.com/c/eHXc1Ryd/4-investigate-the-necessary-change-to-be-rspec-puppet-2-0-0-compliant
New parameter is 'swift_store_large_object_size'.
Sometimes default value (5G) doesn't work when user attempts to
make a snapshots with size > 300 Mb. So it may be usefull to have
a possibity to adjust this parameter to your needs.
Change-Id: I08336b91b0cd294a86326605fb6c28653e8eedb8
glance::backend::swift was not properly configuring
swift_store_* in /etc/glance/glance-cache.conf
when using swift backend.
Change-Id: I7b46dd2bd1ff050759b11cbc9c3c7068e4c3e01e
Updates the glance swift backend to support configuring the
swift_store_auth_version setting. The default value for this is '2'
(which matches the glance config file defaults).
As part of this change I am also updating the default value
for swift_store_auth_address to use 127.0.0.1:5000/v2.0/ (keystone).
This makes sense because the previous value would have required
us to set swift_store_auth_version by default to 1.
Change-Id: I865712914dd0506b2722ab8da3e1c56d7d9f433a
using RI's version of the concat module.
It introduces a custom fact concat_basedir that can determine
where the vardir is for a particular agent.
This commits adds that fact to unit tests that are validating
the resuling fragment files.
I had previously checked in some broken tests that
resulted from the updating the concat fragments names
to ensure uniqueness between services (eg, choosing
fragment names like HEADER were causing
duplicate resource errors, these have been prefixed
with the service name glance-api to ensure uniqueness)
This commit updates the tests so that they work for
this previous commit (oops!)
This commit resolves failing tests from
glance::api and glance::registry related to recent
refactors.
It also adds tests for all of the new api fragment
classes/defines.
