[jira] [Commented] (JCLOUDS-1412) FileSystem BlobStore not compatible with Docker
[ https://issues.apache.org/jira/browse/JCLOUDS-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443215#comment-16443215 ] Andrew Gaul commented on JCLOUDS-1412: -- We will not remove xattr support since this provide blob metadata on non-broken platforms. However, the code should work around the lack of this support. What symptoms do you experience and do you have an exception backtraces? > FileSystem BlobStore not compatible with Docker > --- > > Key: JCLOUDS-1412 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1412 > Project: jclouds > Issue Type: Bug > Components: jclouds-blobstore >Affects Versions: 2.1.0 >Reporter: Russell Klopfer >Priority: Major > Labels: filesystem > > Because of [https://github.com/moby/moby/issues/1070] > JClouds FS BlobStore relies on xattr. This means that it won't work with > docker because docker does not support xattr. > Specifically, I saw this when trying to create directories without using > deprecated methods. > [https://jclouds.apache.org/reference/javadoc/2.1.x/org/jclouds/blobstore/BlobStore.html#createDirectory(java.lang.String,%20java.lang.String)] > [https://jclouds.apache.org/reference/javadoc/2.1.x/org/jclouds/blobstore/BlobStore.html#deleteDirectory(java.lang.String,%20java.lang.String)] > [https://jclouds.apache.org/reference/javadoc/2.1.x/org/jclouds/blobstore/BlobStore.html#directoryExists(java.lang.String,%20java.lang.String)] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (JCLOUDS-1412) FileSystem BlobStore not compatible with Docker
[ https://issues.apache.org/jira/browse/JCLOUDS-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Gaul updated JCLOUDS-1412: - Labels: filesystem (was: ) > FileSystem BlobStore not compatible with Docker > --- > > Key: JCLOUDS-1412 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1412 > Project: jclouds > Issue Type: Bug > Components: jclouds-blobstore >Affects Versions: 2.1.0 >Reporter: Russell Klopfer >Priority: Major > Labels: filesystem > > Because of [https://github.com/moby/moby/issues/1070] > JClouds FS BlobStore relies on xattr. This means that it won't work with > docker because docker does not support xattr. > Specifically, I saw this when trying to create directories without using > deprecated methods. > [https://jclouds.apache.org/reference/javadoc/2.1.x/org/jclouds/blobstore/BlobStore.html#createDirectory(java.lang.String,%20java.lang.String)] > [https://jclouds.apache.org/reference/javadoc/2.1.x/org/jclouds/blobstore/BlobStore.html#deleteDirectory(java.lang.String,%20java.lang.String)] > [https://jclouds.apache.org/reference/javadoc/2.1.x/org/jclouds/blobstore/BlobStore.html#directoryExists(java.lang.String,%20java.lang.String)] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JCLOUDS-1412) FileSystem BlobStore not compatible with Docker
[ https://issues.apache.org/jira/browse/JCLOUDS-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443199#comment-16443199 ] Russell Klopfer commented on JCLOUDS-1412: -- This is where those attributes are written: [https://github.com/jclouds/jclouds/blob/rel/jclouds-2.1.0/apis/filesystem/src/main/java/org/jclouds/filesystem/strategy/internal/FilesystemStorageStrategyImpl.java#L465] This is where they read: [https://github.com/jclouds/jclouds/blob/rel/jclouds-2.1.0/apis/filesystem/src/main/java/org/jclouds/filesystem/strategy/internal/FilesystemStorageStrategyImpl.java#L712] > FileSystem BlobStore not compatible with Docker > --- > > Key: JCLOUDS-1412 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1412 > Project: jclouds > Issue Type: Bug > Components: jclouds-blobstore >Affects Versions: 2.1.0 >Reporter: Russell Klopfer >Priority: Major > > Because of [https://github.com/moby/moby/issues/1070] > JClouds FS BlobStore relies on xattr. This means that it won't work with > docker because docker does not support xattr. > Specifically, I saw this when trying to create directories without using > deprecated methods. > [https://jclouds.apache.org/reference/javadoc/2.1.x/org/jclouds/blobstore/BlobStore.html#createDirectory(java.lang.String,%20java.lang.String)] > [https://jclouds.apache.org/reference/javadoc/2.1.x/org/jclouds/blobstore/BlobStore.html#deleteDirectory(java.lang.String,%20java.lang.String)] > [https://jclouds.apache.org/reference/javadoc/2.1.x/org/jclouds/blobstore/BlobStore.html#directoryExists(java.lang.String,%20java.lang.String)] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (JCLOUDS-1412) FileSystem BlobStore not compatible with Docker
Russell Klopfer created JCLOUDS-1412: Summary: FileSystem BlobStore not compatible with Docker Key: JCLOUDS-1412 URL: https://issues.apache.org/jira/browse/JCLOUDS-1412 Project: jclouds Issue Type: Bug Components: jclouds-blobstore Affects Versions: 2.1.0 Reporter: Russell Klopfer Because of [https://github.com/moby/moby/issues/1070] JClouds FS BlobStore relies on xattr. This means that it won't work with docker because docker does not support xattr. Specifically, I saw this when trying to create directories without using deprecated methods. [https://jclouds.apache.org/reference/javadoc/2.1.x/org/jclouds/blobstore/BlobStore.html#createDirectory(java.lang.String,%20java.lang.String)] [https://jclouds.apache.org/reference/javadoc/2.1.x/org/jclouds/blobstore/BlobStore.html#deleteDirectory(java.lang.String,%20java.lang.String)] [https://jclouds.apache.org/reference/javadoc/2.1.x/org/jclouds/blobstore/BlobStore.html#directoryExists(java.lang.String,%20java.lang.String)] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [jclouds/jclouds-labs] JCLOUDS-1406 - Add default location configuration to dimension data provider (#433)
@trevorflanagan pushed 3 commits. 26724ba JCLOUDS-1406 - Add default location configuration to dimension data provider 1070c18 JCLOUDS-1406 - Add default location configuration to dimension data provider f20b15d JCLOUDS-1406 - Add default location configuration to dimension data provider -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/jclouds/jclouds-labs/pull/433/files/b702c8200b05429d47ba316e728e6825dca34b32..f20b15d04c7f273605b4d2ad45874c12fcdf7406
Re: [jclouds/jclouds-labs] JCLOUDS-1406 - Add default location configuration to dimension data provider (#433)
rebuild please -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/433#issuecomment-382462656
Re: [jclouds/jclouds-labs] JCLOUDS-1407 - Dimensiondata Server API 2.6 support (#434)
@btrishkin pushed 1 commit. 904fcbd Server API 2.6 support -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/jclouds/jclouds-labs/pull/434/files/28a17e29e26ee710272e19c42d2bd9e2a6f5f1ee..904fcbdb9c8c305f7dd119169ce0eededcaf3599
Re: [jclouds/jclouds] JCLOUDS-1333: Require JDK 1.8 (#1197)
I've build jclouds and labs with this change then tried to build jcloud-karaf,
but I get the following error:
```bash
[WARNING] Feature resolution failed for [jclouds-all-blobstore/2.2.0.SNAPSHOT]
Message: Unable to resolve root: missing requirement [root] osgi.identity;
osgi.identity=jclouds-all-blobstore; type=karaf.feature;
version=2.2.0.SNAPSHOT;
filter:="(&(osgi.identity=jclouds-all-blobstore)(type=karaf.feature)(version>=2.2.0.SNAPSHOT))"
[caused by: Unable to resolve jclouds-all-blobstore/2.2.0.SNAPSHOT: missing
requirement [jclouds-all-blobstore/2.2.0.SNAPSHOT] osgi.identity;
osgi.identity=jclouds-api-openstack-swift; type=karaf.feature;
version="[2.2.0.SNAPSHOT,2.2.0.SNAPSHOT]"
[caused by: Unable to resolve jclouds-api-openstack-swift/2.2.0.SNAPSHOT:
missing requirement [jclouds-api-openstack-swift/2.2.0.SNAPSHOT] osgi.identity;
osgi.identity=jclouds-blobstore; type=karaf.feature;
version="[2.2.0.SNAPSHOT,2.2.0.SNAPSHOT]"
[caused by: Unable to resolve jclouds-blobstore/2.2.0.SNAPSHOT: missing
requirement [jclouds-blobstore/2.2.0.SNAPSHOT] osgi.identity;
osgi.identity=jclouds-blobstore; type=osgi.bundle;
version="[2.2.0.SNAPSHOT,2.2.0.SNAPSHOT]"; resolution:=mandatory
[caused by: Unable to resolve jclouds-blobstore/2.2.0.SNAPSHOT: missing
requirement [jclouds-blobstore/2.2.0.SNAPSHOT] osgi.wiring.package;
filter:="(&(osgi.wiring.package=com.google.common.base)(version>=21.0.0)(!(version>=25.0.0)))"
[caused by: Unable to resolve com.google.guava/21.0.0: missing requirement
[com.google.guava/21.0.0] osgi.ee;
filter:="(&(osgi.ee=JavaSE)(version=1.8))"]
```
This is the change I've applied in jclouds-karaf to require Java 8 and Guva
21.0 too:
```diff
diff --git a/pom.xml b/pom.xml
index 768cd0a..89203c2 100644
--- a/pom.xml
+++ b/pom.xml
@@ -102,6 +102,7 @@ limitations under the License.
**/.checkstyle
**/target/**
.repository/**
+.java-version
**/src/main/resources/**/*.txt
@@ -149,8 +150,8 @@ limitations under the License.
maven-compiler-plugin
${maven-compiler-plugin.version}
- 1.6
- 1.6
+ ${jdk.version}
+ ${jdk.version}
@@ -183,14 +184,14 @@ limitations under the License.
-1.7
+1.8
1.0_5
1.51
3.0
1.8.0
2.4.4
2.5
-18.0
+21.0
10.0
3.0
4.3.4
```
it looks like ti cannot resolve the Guava 21 bundle but I can't see what is
missing in the configuration.
@demobox @neykov could you have a look?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1197#issuecomment-382319204
Re: [jclouds/jclouds-labs] JCLOUDS-1406 - Add default location configuration to dimension data provider (#433)
The idea is to make "optional" parameters or filters really optional and have a
clean API. That's the reasoning behind refactoring them into an options object.
With this in mind, the code in your branch looks good, but I'd change the
signatures to:
```java
@Named("server:list")
@GET
@Path("/server")
@ResponseParser(ParseServers.class)
@Fallback(Fallbacks.EmptyIterableWithMarkerOnNotFoundOr404.class)
PaginatedCollection listServers(DatacenterIdListFilters
datacenterIdListFilters);
@Named("server:list")
@GET
@Path("/server")
@Transform(ParseServers.ToPagedIterable.class)
@ResponseParser(ParseServers.class)
@Fallback(Fallbacks.EmptyPagedIterableOnNotFoundOr404.class)
PagedIterable listServers();
```
I mean, if the filter is optional, just provide a method with no arguments (no
filters). If users want to filter they can use the method with the options
parameter. You can then have the function that advances take into account the
presence or absence of the filters parameter:
```java
@Override
protected Function
markerToNextForArg0(final Optional arg0) {
return new Function() {
@Override
public IterableWithMarker apply(Object input) {
DatacenterIdListFilters filters = arg0.isPresent() ?
(DatacenterIdListFilters) input : new DatacenterIdListFilters();
filters.paginationOptions((PaginationFilterOptions) input);
return api.getServerApi().listServers(filters);
}
};
}
```
There is also no need to duplicate the `PaginationOptions` class if it is still
used in other APIs (making it not extend the base options class was just a
suggestion to illustrate it is not a need for a "marker" to the next page).
Let's just remove the new Pagination options class and let the Ddatacenter
filters builder accept the existing one. You can easily add all the pagination
query params to the current filter query parameter map and there won't be
duplicated code.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/433#issuecomment-382283023
Re: [jclouds/jclouds-labs] JCLOUDS-1407 - Dimensiondata Server API 2.6 support (#434)
nacx commented on this pull request.
> @@ -61,7 +61,7 @@
@RequestFilters({ BasicAuthentication.class, OrganisationIdFilter.class })
@Consumes(MediaType.APPLICATION_JSON)
-@Path("/{jclouds.api-version}/server")
+@Path("/2.6/server")
Understood. Let's leave it as-is then for now.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/434#discussion_r182320113
Re: [jclouds/jclouds] Allow jclouds to provision SoftLayer instances with a private image. (#1198)
Not really. We usually release bugfix versions when there is a number of bugs or some critical ones, or when there is user demand, but we don't have hard dates for releases. Starting a discussion about the next bugfix release on the [user mailing list](https://lists.apache.org/list.html?u...@jclouds.apache.org) would be the best way to make things start moving forward :) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/1198#issuecomment-382276606
