Hi Srujana,
From looking at the source I think 'file' is disallowed only for image
uploads using the mechanisms where you specify either a location or copy_from
(ie where you do not include the image bytes in your request). This is
to prevent users accessing arbitrary files on the glance server
Hi Srujana,
If setting location for file were re-enabled and someone did this for example:
glance image-create --name= --is-public=true
--container-format= --disk-format=qcow2
--location=file://etc/glance/glance-api.conf
they would subsequently be able to download the glance configuration f
On Mon, 30 Mar 2015, Haïkel wrote:
I'd say using a shared storage driver:
* rbd works ok
* sheepdog (never used but got good feedback)
* swift (remember that 5GB is the limit for large objects in Swift)
In case it's not clear from this, Glance can store images greater than
5GB when using Swi
Are you using SSL (https)?
On Thu, 2 Apr 2015, Shrinand Javadekar wrote:
Top shows the CPUs pegged at ~100%. Writes are done by a tool built
in-house which is similar in functionality to other object store
benchmarking tools. As I mentioned, there are 256 parallel object
writes (PUTS), each of
If anyone is running v1, and doesn't want to disable it, it should be
possible to use the 'modify_member' policy to prevent this loophole
being taken advantage of.
-Stuart
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Glance allows sharing of images between projects without consumer
project ap
This is not supported - image data is immutable.
On Wed, 26 Mar 2014, Christian Berendt wrote:
On 03/26/2014 02:16 PM, Dmitry Guryanov wrote:
Is it possible to update image data in Glance? For example you have created an
image, used it for some time. Then you've updated software in it and wan
Hi Mark,
I have some changes up for review which enable SSL by default in the overcloud
(in case they're helpful to you):
https://review.openstack.org/#/c/85098
https://review.openstack.org/#/c/85099
https://review.openstack.org/#/c/85100
-Stuart
On Tue, 22 Apr 2014, Robert Collins wrote:
On
Hi Sam,
We're just starting to look at v2.
We did see some really slow listing behaviour, backporting
Ie7458044edbe1ef64871bcf5ef4996ed3cc0f957 helped a lot -- but you'll
probably have that change already if you're using more recent code.
Even with that it does seem slower in some cases, eg dev
Hi Mike,
Does it work if you put this at the very bottom of the file?
[.*]
create = @
read = @
update = @
delete = @
-Stuart
On Thu, 28 Aug 2014, Michael Turek wrote:
Hello,
I was wondering if the following behavior that I'm seeing with protected
properties is intended.
My setup is a ubu
You can control the maximum size of swift objects that glance creates
using the following glance-api.conf parameters:
swift_store_large_object_chunk_size = 200
swift_store_large_object_size = 5120
see glance-api.conf for a description.
On Tue, 25 Nov 2014, Kuvaja, Erno wrote:
Hi Subbareddy,
Hi Martinx,
Thanks for your feedback. You're not the only person to have been affected.
The (lack of) backwards compatibilty of the v2 CLI is captured here:
https://wiki.openstack.org/wiki/Glance-v2-v1-client-compatability
A small number of these incompatabilities are due to unmaskable differe
To prevent this kind of thing recurring you can upload the image bytes
into Glance rather than relying on the third party url always being
available, eg:
curl
http://uec-images.ubuntu.com/releases/16.04/release/ubuntu-16.04-server-cloudimg-amd64-disk1.img
| glance image-create --name "Ubuntu 1
12 matches
Mail list logo
