[jira] [Created] (JCLOUDS-1544) Unable to build javadoc with JDK >= 8

Fritz Elfert created JCLOUDS-1544: - Summary: Unable to build javadoc with JDK >= 8 Key: JCLOUDS-1544 URL: https://issues.apache.org/jira/browse/JCLOUDS-1544 Project: jclouds Issue Type:

[jira] [Commented] (JCLOUDS-1300) Unable to launch gce in jenkins

[ https://issues.apache.org/jira/browse/JCLOUDS-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16022434#comment-16022434 ] Fritz Elfert commented on JCLOUDS-1300: --- Will that be some new member of TemplateOptions resp

[jira] [Commented] (JCLOUDS-1300) Unable to launch gce in jenkins

[ https://issues.apache.org/jira/browse/JCLOUDS-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16022425#comment-16022425 ] Fritz Elfert commented on JCLOUDS-1300: --- Further info at https://issues.jenkins-ci.org/browse

Re: [jclouds/jclouds] Handle gzipped userdata in logging (#1062)

@felfert pushed 2 commits. c3d9a68 Conform to apache jclouds coding standards 5e7139b Added unit test for CreateServerOptions.toString() behavior -- You are receiving this because you are subscribed to this thread. View it on GitHub:

Re: [jclouds/jclouds] Handle gzipped userdata in logging (#1061)

@felfert pushed 2 commits. 3dc075e Conform to apache jclouds coding standards 21d247c Added unit test for CreateServerOptions.toString() behavior -- You are receiving this because you are subscribed to this thread. View it on GitHub:

Re: [jclouds/jclouds] Handle gzipped userdata in logging (#1061)

Will do. -Fritz Am 15. Februar 2017 11:11:28 MEZ schrieb Ignasi Barrera : >Thanks @felfert! Could you add a simple unit test that verifies the >behaviour of that method with normal and gzipped inputs? This way we >won't break this unintentionally in the future. > >--

[jira] [Updated] (JCLOUDS-1239) Gzipped userdata not handled in openstack-nova debug logging

[ https://issues.apache.org/jira/browse/JCLOUDS-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fritz Elfert updated JCLOUDS-1239: -- Labels: openstack-nova (was: ) > Gzipped userdata not handled in openstack-nova de

[jira] [Updated] (JCLOUDS-1239) Gzipped userdata not handled in openstack-nova debug logging

[ https://issues.apache.org/jira/browse/JCLOUDS-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fritz Elfert updated JCLOUDS-1239: -- Description: It is very common to gzip userdata on openstack to preserve space (when using

[jira] [Updated] (JCLOUDS-1239) Gzipped userdata not handled in openstack-nova debug logging

[ https://issues.apache.org/jira/browse/JCLOUDS-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fritz Elfert updated JCLOUDS-1239: -- Description: It is very common to gzip userdata on openstack to preserve space (when using

[jclouds/jclouds] Handle gzipped userdata in logging (#1062)

Like #1061 , only against the 2.0.x branch. Fixes: JCLOUDS-1239 You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds/pull/1062 -- Commit Summary -- * Handle gzipped userdata in logging -- File Changes -- M

[jclouds/jclouds] Handle gzipped userdata in logging (#1061)

This PR replaces gzipped binary "garbage" in openstack-nova debug-logging of userData Fixes: JCLOUDS-1239 You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds/pull/1061 -- Commit Summary -- * Handle gzipped userdata in logging -- File Changes

[jira] [Updated] (JCLOUDS-1239) Gzipped userdata not handled in openstack-nova debug logging

[ https://issues.apache.org/jira/browse/JCLOUDS-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fritz Elfert updated JCLOUDS-1239: -- Description: It is very common to gzip userdata on openstack to preserve space (when using

[jira] [Created] (JCLOUDS-1239) Gzipped userdata not handled in openstack-nova debug logging

Fritz Elfert created JCLOUDS-1239: - Summary: Gzipped userdata not handled in openstack-nova debug logging Key: JCLOUDS-1239 URL: https://issues.apache.org/jira/browse/JCLOUDS-1239 Project: jclouds

Re: [jclouds/jclouds] Fixes JCLOUDS-1206 (#1042)

> Right. I think the use of user metadata here is wrong. It is meant for > providers like OpenStack that support key value pairs in the metadata, but > not for this. Mind changing it and add the userData field to the > DigitalOceanTemplateOptions, and also this comment to properly indicate user

Re: [jclouds/jclouds] Fixes JCLOUDS-1206 (#1042)

@felfert pushed 1 commit. ec39127 Added byte[] userData according to code review -- You are receiving this because you are subscribed to this thread. View it on GitHub:

Re: [jclouds/jclouds-site] Update index.md (#191)

Looks just like your image here (index of various javadocs shown), but if I click on **any** of those links, I get the following message: Web Listing Disabled The owner of this web site has disabled web listing. If you are the owner of this web site, you can enable web listing by setting

Re: [jclouds/jclouds-site] Update index.md (#191)

> Go to > http://db28c6e508cc7c000f84-4fe8c41c25aa7c42c77a072c81d57bea.r78.cf5.rackcdn.com/ > to review your changes. That link does not work at all?! (Index shown, but nothing else) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on

[jclouds/jclouds-site] Update index.md (#191)

Add missing link to 2.0.x javadoc You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds-site/pull/191 -- Commit Summary -- * Update index.md -- File Changes -- M reference/javadoc/index.md (1) -- Patch Links --

Re: [jclouds/jclouds] Fixes JCLOUDS-1206 (#1042)

@felfert pushed 1 commit. 730cecd Simplified code according to code review -- You are receiving this because you are subscribed to this thread. View it on GitHub:

Re: [jclouds/jclouds] Fixes JCLOUDS-1206 (#1042)

Later: Just realized, that the tags are a Set and associated with a node so: Of course that makes sense :) -- 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/1042#issuecomment-263073020

Re: [jclouds/jclouds] Fixes JCLOUDS-1206 (#1042)

@nacx I looked into the tag api documentation and I think, it does **not** fit the jclouds semantic. In jclouds, those are `Map`, but in DigitalOcean they have Map where Object is currently always a droplet. (Most likely, it's an Integer-Id, just like with their

[jira] [Commented] (JCLOUDS-1206) Handling of user_data in digitalocean2 provider is broken

[ https://issues.apache.org/jira/browse/JCLOUDS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15697770#comment-15697770 ] Fritz Elfert commented on JCLOUDS-1206: --- This pull request on github fixes the issue. (Tested

[jclouds/jclouds] Fixes JCLOUDS-1206 (#1042)

You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds/pull/1042 -- Commit Summary -- * Fixes JCLOUDS-1206 -- File Changes -- M providers/digitalocean2/src/main/java/org/jclouds/digitalocean2/compute/DigitalOcean2ComputeServiceAdapter.java

[jira] [Created] (JCLOUDS-1206) Handling of user_data in digitalocean2 provider is broken

Fritz Elfert created JCLOUDS-1206: - Summary: Handling of user_data in digitalocean2 provider is broken Key: JCLOUDS-1206 URL: https://issues.apache.org/jira/browse/JCLOUDS-1206 Project: jclouds