Looking at the image you're using, it seems to be a deprecated one (isn't
it?).
You may want to filter out the deprecated images and avoid using them (I
recall having problems with disks when using some of them).
In the current impl, the deprecated field, when present, is populated in
the
Hi,
In jclouds 1.8.0, I can see support for volume creation using snapshot Id
but not using image id is it supported?
Does the filesystem blobstore provider work on shared folders, with
concurrent clients?
Does the provider handle locking and contention in naming?
- Anthony
Hi, Anthony. There is no synchronized, or mutex code in the current
filesystem implementation. There are also no multithreaded tests to
show it doesn't need that. In other words, I would use it only from a
single thread, and synchronize externally. That said, you can always
raise a pull request to
Hi, Colin.
VirtualBox has been dropped from jclouds labs as of version 1.9 [1].
We've stopped investing time in virtualization providers such as
virtualbox or vsphere as they take inordinate amount of maintenance
which displaces our ability to maintain cloud providers. I would look
into other
Hi Shital,
I’m not sure what you’re trying to accomplish here. AFAIK, you can only create
a volume from empty block storage or from a snapshot. I don’t think creating a
volume from an image is possible.
Exactly what OpenStack operation are you trying to do?
Can you provide an example of doing
Hi Adrian/Andrew,
thank you very much for your replies. This information will be really
helpful to continue my evaluation of jclouds.
Cheers,
Gabriel
2014-11-12 0:34 GMT-08:00 Andrew Gaul g...@apache.org:
On Mon, Nov 10, 2014 at 05:45:10PM -0800, Gabriel Lavoie wrote:
I'm currently
v2_0 is deprecated.
If you are just starting with Neutron, use v2.
Thanks!
-Zack
From: Raj [r...@apache.org]
Sent: Wednesday, November 12, 2014 10:54 AM
To: user@jclouds.apache.org
Subject: Neutron API versions v2 and v2_0
Hi,
Why there two versions(v2 and
