You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Adrian Cole (Created) (JIRA)" <ji...@apache.org> on 2011/10/30 09:09:32 UTC
[jira] [Created] (WHIRR-417) Allow users to choose their own
jclouds modules with properties
Allow users to choose their own jclouds modules with properties
---------------------------------------------------------------
Key: WHIRR-417
URL: https://issues.apache.org/jira/browse/WHIRR-417
Project: Whirr
Issue Type: Improvement
Reporter: Adrian Cole
Currently, we add jclouds modules in a hard-coded way. This implies that the patches to jclouds, which ssh driver we use, etc. cannot be changed without a code release or patching Whirr. jclouds has a property: "jclouds.modules" which when specified overrides the wiring that we would use.
I believe that except in the case of dry run, we need the following property so that we can stop hard-coding the list:
jclouds.modules=org.jclouds.logging.slf4j.config.SLF4JLoggingModule,org.jclouds.enterprise.config.EnterpriseConfigurationModule,org.jclouds.sshj.config.SshjSshClientModule,org.apache.whirr.service.jclouds.BindLoginCredentialsPatchForEC2
With this in place, people can feel free to use jsch or sshj, for example, and also remove or update patches we make to jclouds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WHIRR-417) Allow users to choose their own
jclouds modules with properties
Posted by "Adrian Cole (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13139577#comment-13139577 ]
Adrian Cole commented on WHIRR-417:
-----------------------------------
tested several times with cloudservers-uk (as I'm testing from brussels)
> Allow users to choose their own jclouds modules with properties
> ---------------------------------------------------------------
>
> Key: WHIRR-417
> URL: https://issues.apache.org/jira/browse/WHIRR-417
> Project: Whirr
> Issue Type: Improvement
> Affects Versions: 0.6.0
> Reporter: Adrian Cole
> Assignee: Adrian Cole
> Fix For: 0.7.0
>
> Attachments: WHIRR-417.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Currently, we add jclouds modules in a hard-coded way. This implies that the patches to jclouds, which ssh driver we use, etc. cannot be changed without a code release or patching Whirr. jclouds has a property: "jclouds.modules" which when specified overrides the wiring that we would use.
> I believe that except in the case of dry run, we need the following property so that we can stop hard-coding the list:
> jclouds.modules=org.jclouds.logging.slf4j.config.SLF4JLoggingModule,org.jclouds.enterprise.config.EnterpriseConfigurationModule,org.jclouds.sshj.config.SshjSshClientModule,org.apache.whirr.service.jclouds.BindLoginCredentialsPatchForEC2
> With this in place, people can feel free to use jsch or sshj, for example, and also remove or update patches we make to jclouds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (WHIRR-417) Allow users to choose their own
jclouds modules with properties
Posted by "Adrian Cole (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrian Cole reassigned WHIRR-417:
---------------------------------
Assignee: Adrian Cole
> Allow users to choose their own jclouds modules with properties
> ---------------------------------------------------------------
>
> Key: WHIRR-417
> URL: https://issues.apache.org/jira/browse/WHIRR-417
> Project: Whirr
> Issue Type: Improvement
> Reporter: Adrian Cole
> Assignee: Adrian Cole
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Currently, we add jclouds modules in a hard-coded way. This implies that the patches to jclouds, which ssh driver we use, etc. cannot be changed without a code release or patching Whirr. jclouds has a property: "jclouds.modules" which when specified overrides the wiring that we would use.
> I believe that except in the case of dry run, we need the following property so that we can stop hard-coding the list:
> jclouds.modules=org.jclouds.logging.slf4j.config.SLF4JLoggingModule,org.jclouds.enterprise.config.EnterpriseConfigurationModule,org.jclouds.sshj.config.SshjSshClientModule,org.apache.whirr.service.jclouds.BindLoginCredentialsPatchForEC2
> With this in place, people can feel free to use jsch or sshj, for example, and also remove or update patches we make to jclouds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (WHIRR-417) Allow users to choose
their own jclouds modules with properties
Posted by "Adrian Cole (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13139568#comment-13139568 ]
Adrian Cole edited comment on WHIRR-417 at 10/30/11 9:28 AM:
-------------------------------------------------------------
if you'd like to try this wrt changing modules, add the jclouds maven dependency org.jclouds.driver/jclouds-jsch and set the following:
jclouds.modules=org.jclouds.logging.slf4j.config.SLF4JLoggingModule,org.jclouds.enterprise.config.EnterpriseConfigurationModule,org.jclouds.ssh.jsch.config.JschSshClientModule,org.apache.whirr.service.jclouds.BindLoginCredentialsPatchForEC2
was (Author: adrian@jclouds.org):
if you'd like to try this wrt changing modules, add the jclouds maven dependency org.jclouds.driver/jclouds-jsch and set the following:
jclouds.modules=org.jclouds.ssh.jsch.config.JschSshClientModule,org.jclouds.enterprise.config.EnterpriseConfigurationModule,org.jclouds.sshj.config.SshjSshClientModule,org.apache.whirr.service.jclouds.BindLoginCredentialsPatchForEC2
> Allow users to choose their own jclouds modules with properties
> ---------------------------------------------------------------
>
> Key: WHIRR-417
> URL: https://issues.apache.org/jira/browse/WHIRR-417
> Project: Whirr
> Issue Type: Improvement
> Affects Versions: 0.6.0
> Reporter: Adrian Cole
> Assignee: Adrian Cole
> Fix For: 0.7.0
>
> Attachments: WHIRR-417.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Currently, we add jclouds modules in a hard-coded way. This implies that the patches to jclouds, which ssh driver we use, etc. cannot be changed without a code release or patching Whirr. jclouds has a property: "jclouds.modules" which when specified overrides the wiring that we would use.
> I believe that except in the case of dry run, we need the following property so that we can stop hard-coding the list:
> jclouds.modules=org.jclouds.logging.slf4j.config.SLF4JLoggingModule,org.jclouds.enterprise.config.EnterpriseConfigurationModule,org.jclouds.sshj.config.SshjSshClientModule,org.apache.whirr.service.jclouds.BindLoginCredentialsPatchForEC2
> With this in place, people can feel free to use jsch or sshj, for example, and also remove or update patches we make to jclouds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WHIRR-417) Allow users to choose their own
jclouds modules with properties
Posted by "Adrian Cole (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13139568#comment-13139568 ]
Adrian Cole commented on WHIRR-417:
-----------------------------------
if you'd like to try this wrt changing modules, add the jclouds maven dependency org.jclouds.driver/jclouds-jsch and set the following:
jclouds.modules=org.jclouds.ssh.jsch.config.JschSshClientModule,org.jclouds.enterprise.config.EnterpriseConfigurationModule,org.jclouds.sshj.config.SshjSshClientModule,org.apache.whirr.service.jclouds.BindLoginCredentialsPatchForEC2
> Allow users to choose their own jclouds modules with properties
> ---------------------------------------------------------------
>
> Key: WHIRR-417
> URL: https://issues.apache.org/jira/browse/WHIRR-417
> Project: Whirr
> Issue Type: Improvement
> Affects Versions: 0.6.0
> Reporter: Adrian Cole
> Assignee: Adrian Cole
> Fix For: 0.7.0
>
> Attachments: WHIRR-417.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Currently, we add jclouds modules in a hard-coded way. This implies that the patches to jclouds, which ssh driver we use, etc. cannot be changed without a code release or patching Whirr. jclouds has a property: "jclouds.modules" which when specified overrides the wiring that we would use.
> I believe that except in the case of dry run, we need the following property so that we can stop hard-coding the list:
> jclouds.modules=org.jclouds.logging.slf4j.config.SLF4JLoggingModule,org.jclouds.enterprise.config.EnterpriseConfigurationModule,org.jclouds.sshj.config.SshjSshClientModule,org.apache.whirr.service.jclouds.BindLoginCredentialsPatchForEC2
> With this in place, people can feel free to use jsch or sshj, for example, and also remove or update patches we make to jclouds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WHIRR-417) Allow users to choose their own
jclouds modules with properties
Posted by "Adrian Cole (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrian Cole updated WHIRR-417:
------------------------------
Attachment: WHIRR-417.patch
> Allow users to choose their own jclouds modules with properties
> ---------------------------------------------------------------
>
> Key: WHIRR-417
> URL: https://issues.apache.org/jira/browse/WHIRR-417
> Project: Whirr
> Issue Type: Improvement
> Affects Versions: 0.6.0
> Reporter: Adrian Cole
> Assignee: Adrian Cole
> Fix For: 0.7.0
>
> Attachments: WHIRR-417.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Currently, we add jclouds modules in a hard-coded way. This implies that the patches to jclouds, which ssh driver we use, etc. cannot be changed without a code release or patching Whirr. jclouds has a property: "jclouds.modules" which when specified overrides the wiring that we would use.
> I believe that except in the case of dry run, we need the following property so that we can stop hard-coding the list:
> jclouds.modules=org.jclouds.logging.slf4j.config.SLF4JLoggingModule,org.jclouds.enterprise.config.EnterpriseConfigurationModule,org.jclouds.sshj.config.SshjSshClientModule,org.apache.whirr.service.jclouds.BindLoginCredentialsPatchForEC2
> With this in place, people can feel free to use jsch or sshj, for example, and also remove or update patches we make to jclouds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WHIRR-417) Allow users to choose their own
jclouds modules with properties
Posted by "Andrei Savu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145778#comment-13145778 ]
Andrei Savu commented on WHIRR-417:
-----------------------------------
+1 tested on aws-ec2 using the hbase integration tests (fixed a typo)
> Allow users to choose their own jclouds modules with properties
> ---------------------------------------------------------------
>
> Key: WHIRR-417
> URL: https://issues.apache.org/jira/browse/WHIRR-417
> Project: Whirr
> Issue Type: Improvement
> Affects Versions: 0.6.0
> Reporter: Adrian Cole
> Assignee: Adrian Cole
> Fix For: 0.7.0
>
> Attachments: WHIRR-417.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Currently, we add jclouds modules in a hard-coded way. This implies that the patches to jclouds, which ssh driver we use, etc. cannot be changed without a code release or patching Whirr. jclouds has a property: "jclouds.modules" which when specified overrides the wiring that we would use.
> I believe that except in the case of dry run, we need the following property so that we can stop hard-coding the list:
> jclouds.modules=org.jclouds.logging.slf4j.config.SLF4JLoggingModule,org.jclouds.enterprise.config.EnterpriseConfigurationModule,org.jclouds.sshj.config.SshjSshClientModule,org.apache.whirr.service.jclouds.BindLoginCredentialsPatchForEC2
> With this in place, people can feel free to use jsch or sshj, for example, and also remove or update patches we make to jclouds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira