The agent-proxy stuff can be tested by:
* Using a password protected ssh key to access the node (the key must be added
to the ssh-agent in advance, otherwise jclouds won't be able to authenticate as
the key is encrypted).
* Or installing the key (password protected or not) in the node and
IIRC there is a command in karaf to run a script on a node. Don't know the
details of how it is used but it should allow us to test the agent-proxy stuff.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/43#issuecomment-40929189
Closed #81.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/81
IIRC there is a command in karaf to run a script on a node. Don't know the
details of how it is used
but it should allow us to test the agent-proxy stuff.
OK, I'll give that a try. Thanks, @nacx!
---
Reply to this email directly or view it on GitHub:
@everett-toews @zack-shoylev @jdaggett: Any chance you could check whether this
change helps? Thoughts on
[JCLOUDS-538](https://issues.apache.org/jira/browse/JCLOUDS-538) generally
would also be great...thanks!
---
Reply to this email directly or view it on GitHub:
[
https://issues.apache.org/jira/browse/JCLOUDS-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13975607#comment-13975607
]
Sandeep Bazar commented on JCLOUDS-538:
---
Used the following command line to invoke
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-site logging-https
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/84
-- Commit Summary --
* How to use a proxy with jclouds
-- File Changes
[jclouds-site-pull-requests
#262](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/262/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/84#issuecomment-40941846
Go to
http://1363a66267acad804e25-83e3c1d6c235f1462c0f63349c8103c3.r31.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/84#issuecomment-40942006
@@ -7,6 +7,7 @@ permalink: /reference/logging/
1. [Install](#install)
1. [Configure](#configure)
1. [Enable](#enable)
+1. [Proxy](#proxy)
Call this HTTP(S) Proxy? jclouds also supports proxying other socket
connections, and the JSch driver at least should honour that (see comment
Closed #41.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/41
Superseded by https://github.com/jclouds/jclouds-site/pull/84, I guess?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/41#issuecomment-40949066
[
https://issues.apache.org/jira/browse/JCLOUDS-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett reassigned JCLOUDS-524:
--
Assignee: Jeremy Daggett
Standardize Major OpenStack API Versions
Trying to fix this without knowing the root-cause does seems like a bad idea to
me. We may just hit this again in some other environment and/or in some other
circumstances and then this change simply lands up being dead code.
---
Reply to this email directly or view it on GitHub:
+1. Proxy Proxy Settings SSL tab
+1. Check Enable SSL Proxying
+1. Add Locations. e.g.
+1. *.rackspacecloud.com
+1. *.clouddrive.com
+
+jclouds also requires some configuration to use a proxy.
+
+{% highlight java %}
+import static org.jclouds.Constants.*;
+
+// snip
+
@@ -7,6 +7,7 @@ permalink: /reference/logging/
1. [Install](#install)
1. [Configure](#configure)
1. [Enable](#enable)
+1. [Proxy](#proxy)
I'll change it to HTTP(S) Proxy.
---
Reply to this email directly or view it on GitHub:
[jclouds-site-pull-requests
#263](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/263/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/84#issuecomment-40965622
Go to
http://1b1ab759be71c4d3c389-2c59777b65bf68d70ba619aad1263803.r79.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/84#issuecomment-40965813
[jclouds-pull-requests
#766](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/766/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/349#issuecomment-40968239
[jclouds-java-7-pull-requests
#1236](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1236/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/349#issuecomment-40968532
[jclouds » jclouds
#1041](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1041/) UNSTABLE
Looks like there's a problem with this pull request
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1041/changes
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-site openstack-up
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/85
-- Commit Summary --
* Update to latest version of jclouds
-- File
[jclouds-site-pull-requests
#264](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/264/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/85#issuecomment-40984646
Squashed and merged.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/45#issuecomment-40984787
Closed #45.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/45
[
https://issues.apache.org/jira/browse/JCLOUDS-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13976128#comment-13976128
]
ASF subversion and git services commented on JCLOUDS-346:
-
Commit
Go to
http://61720819329ac451e552-887d2402f8ff160766036f7c93a9a532.r82.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/85#issuecomment-40984802
Don't forget to squash first!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-40984853
[
https://issues.apache.org/jira/browse/JCLOUDS-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Everett Toews updated JCLOUDS-526:
--
Fix Version/s: 1.7.3
Remove QuotaClassApi in Nova
@nacx I'm not sure I understand your question -- if I let the image variable
be null, the very next line (`builder.imageId(image.getId());`) causes a NPE.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/58#issuecomment-40999874
I meant to not assign the imageId and operatingSystem if the image is null.
Could you try that?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/58#issuecomment-41005747
@nacx I see what you mean -- yes I can try that. I'll report back after I've
given it a whirl.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/58#issuecomment-41006274
33 matches
Mail list logo
