This change contains minor version bump to Images API to
indicate latest changes to the API.
Also has config file sync for for M3 release.
These two are combined for saving some gating time due to
busy infra at Train milestone 3 deadline.
Change-Id: I13133c32734751d43cc3afed9b68d015cebd5b6b
The documentation references the section DEFUALT
instead of DEFAULT. As this is most likely a
spelling error which will cause confusion, it is
better if we fix it.
This patch corrects the config option information
and includes an updated set of sample config files
generated from the current code including the fix.
Change-Id: If3c5e334aa1fa2ff5a28f52c00330d42cb9bcf9d
In preparation for the last Ocata beta milestone, let's update our
configuration files. This will also allow for other folks who are
updating config files to create much smaller diffs.
Change-Id: Id644879bb9e93a291c7935eaeacf664bbf46efc2
There's a bug in glance_store ( bug 1619487 ) that results in a
reordering of the store related configurations everytime the tool to
autogenerate configs is used.
This commit generates the Newton config in the deterministic way by
using the suggested solution described on the bug.
For more information and background discussions see change
Iea2c538b37182191445cc5c1f8b2d9dceed06343
Related-Change: I3146b8597a5d89da49b84d6653edacc3067c2c71
Change-Id: Idbea98865ccfc14563ab4357764383e1e7021542
During the release many config options are changed or updated. The
sample config files provided in tree (under etc/*) need to be updated
using the autogeneration tool as these files are being used in different
places. Some examples are devstack gates, downstream packagers shipping
with the same (or using defaults from these files), etc.
Hence, before we cut a release we need to refresh the config files
shipped with tree to match the changes done in the source code during
the release cycle.
This commit is intended to refresh the entire set of config files for
Newton. They include:
* glance api and registry related configs
* scrubber, cache and manage utilities' configs
* any other configs coming from downstream like oslo libraries,
glance_store, etc.
* belonging to affiliated code base like glare.
Change-Id: Iea2c538b37182191445cc5c1f8b2d9dceed06343
Co-Authored-By: Nikhil Komawar <nik.komawar@gmail.com>
Co-Authored-By: Hemanth Makkapati <hemanth.makkapati@rackspace.com>
Change IDs I123be151fdda8037e62ba21600e63c45fdc90c8d and
Ie332236d6e11e0cb63114bc1c68c3a8691f1f1ae fix adding some missing config
options to be included as a part of the sample configs. We need to
refresh the configs to include those to be part of the latest sample
set. This commit refreshes some of the config for that purpose.
This change has been inspired while writing release notes here
If0b8b731c2a1a1c41fc612d506c350073d832efa . It was observed that the
bugs mentioned missing config opts in the sample files and have been
marked fixed. However, in order to make the release notes consistent
with that claim and to mention, as a part of the release notes, that
those bugs have been fixed, refreshing this has become important.
Change-Id: I534a0dc2d9f82ab70517cde12bfd40d4f5ae69e2
Related-Bug: 1568723
Related-Bug: 1568894
The option was used to enable experimental Artifacts API
that was moved to glance-glare service. This config option
does not do anything and is removed to avoid confusion.
Removed apropriate sections from example config files as well.
Change-Id: Ie84f3f65ec88fd30197758ac319ef5b2f4c313e2
Closes-bug: 1556050
This should be the last time reordering happening by the
configgenerator. In future we should see only actual changes but to get
there we need to do this massive change once more.
Closes-Bug: 1553330
Change-Id: Icca0a94a40ba640ca75e01b5cd0d061dacd334ff
EXPERIMENTAL Glance v3 API has been removed in favor of standalone API
(EXPERIMENTAL Artifacts API of v0.1).
This patch introduces a new process entry point to run on a different
port (9494 by default), with its own configuration file and a paste
config.
A controller stub for old /v3 api remains in the glnace.api package for
the compatibility with existing paste configuration which may reference
it. This stub returns a 301 redirects to glare endpoint if it is present
or 410 errors otherwise.
To reuse the existing version_negotiation middleware some refactoring
has been made.
Implements blueprint: move-v3-to-glare
Change-Id: I5b7bd4cdcc5f2a40fc4a5f74bcc422fd700c4fb0
Adding taskflow_executor_opts into the opts so they will be included.
Closes-bug: #1496012
Depends-On: I52ebf810f4699826baa2bdf91d28e24d902cf950
Change-Id: I9c0988a70f691482258f5f3ba9a5cf5601a81ddf
This change:
- Adds oslo.policy to the requirements list
- Accounts for changes in Enforcer initialization
- Accounts for changes to config options
- Removes incubated version of oslo.policy
- Updates the in-tree etc/config files
UpgradeImpact
Partially Implements Blueprint: graduate-policy
Change-Id: I5acb1e0f809098991f05ca3b6d78d4d88d98f2db
The description of 'image_cache_max_size' was ambiguous. There was not
the certainty that the 'image_cache_max_size' parameter was about the
aggregate size of the cache or a per image limit.
The 'image_cache_max_size' is an upper limit beyond which pruner,
if running, starts cleaning the images cache.
Hence added detail description of 'image_cache_max_size' in document
and configuration file.
Bug: #1411813
Change-Id: Ide8e087db544aeea1990bac92c97cb9ca9f0b522
The snet option forces the deployer to name the desired endpoint after
the public endpoint. In order to switch between multiple internal
networks, names have to be changed. Instead of constructing a URL with a
prefix from what is returned by auth, specify the URL via configuration.
DocImpact
UpgradeImpact
bp replace-snet-config-with-endpoint-config
Change-Id: I7b7e14d7da082ae37a9737d2078017b04c19b87b
Change I5b356170ec82d033204e22f79c862201400a0a31 introduced a new
swift_store configuration option. Prior to accepting that, it was
determined that we needed to add it to the relevant configuration files
and document the option.
DocImpact
Closes-bug: 1375857
Change-Id: I4cbfae3c1ac84d6c85875d34a58dd2a87ae85d6f
1. Sync glance.openstack.common.policy up to latest
version from oslo-inc.
2. Clean useless modules which depended by policy
module and pinned gettextutils module there. For
latter one, we are going to use glance.i18n instead.
* jsonutils
* strutils
docImpact
Closes-bug: #1288178
Closes-bug: #1387973
Partial-bug: #1381870
Change-Id: I84511ab1ee600e618985448dfbfbdc26cb130370
Signed-off-by: Zhi Yan Liu <zhiyanl@cn.ibm.com>
Changing the default value for s3_store_host parameter from
127.0.0.1:8080 to s3.amazonaws.com in glance-api.conf and
glance-cache.conf.
DocImpact: The following parameter is changed in glance-api.conf
and glance-cache.conf.
-s3_store_host = 127.0.0.1:8080
+s3_store_host = s3.amazonaws.com
Change-Id: I39f5bca280b83853021f379c1b7ebe29cff182b9
For s3 endpoints, url-path is not necessary to define and it's
something like just "s3.amazonaws.com" for Amazon s3 or
"s3.compatibleserver.com:8080" for S3 thirdparty compatible server
that is listening on 8080. So the current default value with '/v1.0/'
of s3_store_host is confusing.
s3_store_host = 127.0.0.1:8080/v1.0/
DocImpact: The following parameter is changed in glance-api.conf
and glance-cache.conf.
-s3_store_host = 127.0.0.1:8080/v1.0/
+s3_store_host = 127.0.0.1:8080
Change-Id: I3b103121e46f58fda339530c62c71b65a69e5dc5
Customers using a VMware environment with OpenStack should be able to
store their Glance images in VMware datastores. This is a first step to solve
the problem where Nova needs to copy the bits over the network
from Glance to the datastore when spawning an instance.
Also, this give the ability to provide some optimizations for specific
image formats in the future (fast cloning for example).
This patch contains a 'glance/store/vmware/' folder with the code
to manage the connection with vCenter or an ESX(i) host.
This code will go away as soon as it is merged to Olso:
see review https://review.openstack.org/#/c/65075/
The current implementation give this ability to specify the vCenter or
ESX(i) IP. In case of a vCenter IP, there is no optimization to reduce
the datapath (no host selected).
Consequently, it is recommended to specify an ESX IP if the ESX host
API endpoint is accessible from Glance.
docImpact
Implements bp vmware-datastore-storage-backend
Change-Id: I3837912e0d1614b9c31a689f71c2e34d453e2dc3
"image_cache_invalid_entry_grace_period" option is unused
in *.py, but the option is used in glance-cache.conf.
I removed "image_cache_invalid_entry_grace_period" option
from glance-cache.conf.
Change-Id: Id235945f9cc89219118e4a3ec077f0e887a3b3ef
Closes-Bug: #1249949
It's not immediately obvious where log output will go if the 'log_file' and
'use_syslog' directives are either missing or commented out. This patch updates
the documentation in the config files to mention the stdout default. This
should help remove any confusion when configuring logging for glance.
Change-Id: I36f2a9d30bdee1949e60f413b7f181631c564ed5
Closes-Bug: #1248292
Add space in "known_stores" block in etc/glance-cache.conf,
and keep glance code tidy and pleasing.
Change-Id: If112db41bfbce9f78013fe33229043f0f626f3f9
This change allows Glance drive Cinder as a block storage backend to
store image data.
Before this we already use swift as an object storage backend to save
image.
Currently the patch is a partial implementation, after Cinder expose
'brick' library, 'host-volume-attaching' and 'multiple-attaching'
enhancement ready, the store will support ADD/GET/DELETE interface
finally.
blueprint: glance-cinder-driver
Change-Id: I4cdeccdb518972c0280e59c984ed6b001dafe243
Signed-off-by: Zhi Yan Liu <zhiyanl@cn.ibm.com>
Sheepdog is a distributed block storage. This patch enables Sheepdog cluster
as a backend store for glance.
Test:
You can set up a simulated 3 node cluster on the local machine with
following script:
$ sudo apt-get install liburcu-dev
$ git clone git://github.com/collie/sheepdog.git
$ cd sheepdog
$ ./autogen.sh; ./configure --disable-corosync
$ make; sudo make install
$ for i in 0 1 2; do sheep /tmp/store$i -n -c local -z $i -p 700$i;done
$ collie cluster format
Then change the default store in glance-api.conf as sheepdog
blueprint: add-sheepdog-support
Change-Id: I99907bbfc2e131146de9dd1a39f94a73cd2585e9