You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ace.apache.org by "Paul Bakker (Created) (JIRA)" <ji...@apache.org> on 2011/10/18 23:57:10 UTC
[jira] [Created] (ACE-187) AMIs can't be found because the search
location is incorrect
AMIs can't be found because the search location is incorrect
------------------------------------------------------------
Key: ACE-187
URL: https://issues.apache.org/jira/browse/ACE-187
Project: Ace
Issue Type: Bug
Reporter: Paul Bakker
Attachments: jclouds.patch
While using the Amazon node launcher AMIs that do exist can't be found by Ace. This is because jclouds now searches AMIs that already exist in the list of instances instead of in the general AMI directory. I fixed this by upgrading jclouds to 1.1.1 (it was still on an early beta) and by removing an deprecated and obsolete property where the ComputeServiceContextFactory is created.
--
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] [Resolved] (ACE-187) AMIs can't be found because the search
location is incorrect
Posted by "Marcel Offermans (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Offermans resolved ACE-187.
----------------------------------
Resolution: Fixed
Updated to 1.2.1, Paul, please retest.
> AMIs can't be found because the search location is incorrect
> ------------------------------------------------------------
>
> Key: ACE-187
> URL: https://issues.apache.org/jira/browse/ACE-187
> Project: Ace
> Issue Type: Bug
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: jclouds.patch
>
>
> While using the Amazon node launcher AMIs that do exist can't be found by Ace. This is because jclouds now searches AMIs that already exist in the list of instances instead of in the general AMI directory. I fixed this by upgrading jclouds to 1.1.1 (it was still on an early beta) and by removing an deprecated and obsolete property where the ComputeServiceContextFactory is created.
--
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] [Resolved] (ACE-187) AMIs can't be found because the search
location is incorrect
Posted by "Marcel Offermans (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Offermans resolved ACE-187.
----------------------------------
Resolution: Fixed
Patch applied.
> AMIs can't be found because the search location is incorrect
> ------------------------------------------------------------
>
> Key: ACE-187
> URL: https://issues.apache.org/jira/browse/ACE-187
> Project: Ace
> Issue Type: Bug
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: jclouds.patch
>
>
> While using the Amazon node launcher AMIs that do exist can't be found by Ace. This is because jclouds now searches AMIs that already exist in the list of instances instead of in the general AMI directory. I fixed this by upgrading jclouds to 1.1.1 (it was still on an early beta) and by removing an deprecated and obsolete property where the ComputeServiceContextFactory is created.
--
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] (ACE-187) AMIs can't be found because the search
location is incorrect
Posted by "Marcel Offermans (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Offermans reassigned ACE-187:
------------------------------------
Assignee: Marcel Offermans
> AMIs can't be found because the search location is incorrect
> ------------------------------------------------------------
>
> Key: ACE-187
> URL: https://issues.apache.org/jira/browse/ACE-187
> Project: Ace
> Issue Type: Bug
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: jclouds.patch
>
>
> While using the Amazon node launcher AMIs that do exist can't be found by Ace. This is because jclouds now searches AMIs that already exist in the list of instances instead of in the general AMI directory. I fixed this by upgrading jclouds to 1.1.1 (it was still on an early beta) and by removing an deprecated and obsolete property where the ComputeServiceContextFactory is created.
--
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] (ACE-187) AMIs can't be found because the search
location is incorrect
Posted by "Jean-Baptiste Onofré (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130440#comment-13130440 ]
Jean-Baptiste Onofré commented on ACE-187:
------------------------------------------
Thanks for the tips Adrian ;)
> AMIs can't be found because the search location is incorrect
> ------------------------------------------------------------
>
> Key: ACE-187
> URL: https://issues.apache.org/jira/browse/ACE-187
> Project: Ace
> Issue Type: Bug
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: Added_sl4j_dependency.patch, jclouds.patch
>
>
> While using the Amazon node launcher AMIs that do exist can't be found by Ace. This is because jclouds now searches AMIs that already exist in the list of instances instead of in the general AMI directory. I fixed this by upgrading jclouds to 1.1.1 (it was still on an early beta) and by removing an deprecated and obsolete property where the ComputeServiceContextFactory is created.
--
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] (ACE-187) AMIs can't be found because the search
location is incorrect
Posted by "Adrian Cole (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130074#comment-13130074 ]
Adrian Cole commented on ACE-187:
---------------------------------
P.S. jclouds 1.2.1 is out today, and includes cool new feature for cancelable async ssh commands: Future<ExecResponse> doit = compute.submitScriptOnNode(node.getId(), Statements.exec("/path/to/install"));
Apache Whirr has already shaken this out.
> AMIs can't be found because the search location is incorrect
> ------------------------------------------------------------
>
> Key: ACE-187
> URL: https://issues.apache.org/jira/browse/ACE-187
> Project: Ace
> Issue Type: Bug
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: jclouds.patch
>
>
> While using the Amazon node launcher AMIs that do exist can't be found by Ace. This is because jclouds now searches AMIs that already exist in the list of instances instead of in the general AMI directory. I fixed this by upgrading jclouds to 1.1.1 (it was still on an early beta) and by removing an deprecated and obsolete property where the ComputeServiceContextFactory is created.
--
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] (ACE-187) AMIs can't be found because the search
location is incorrect
Posted by "Adrian Cole (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130439#comment-13130439 ]
Adrian Cole commented on ACE-187:
---------------------------------
fwiw sshj is what has a slf4j dependency. Ex. if you use jsch there is no dep. That said, I don't recommend using jsch :)
That said, the most sane setup for a computeservicecontext includes:
new SshjSshClientModule() [org.jclouds.driver/jclouds-sshj], new EnterpriseConfigurationModule() [org.jclouds.driver/jclouds-enterprise], new Slf4jLoggingModule() [org.jclouds.driver/jclouds-slf4j]
This will result in the most coherent configuration with the most thread-safe libraries.
> AMIs can't be found because the search location is incorrect
> ------------------------------------------------------------
>
> Key: ACE-187
> URL: https://issues.apache.org/jira/browse/ACE-187
> Project: Ace
> Issue Type: Bug
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: Added_sl4j_dependency.patch, jclouds.patch
>
>
> While using the Amazon node launcher AMIs that do exist can't be found by Ace. This is because jclouds now searches AMIs that already exist in the list of instances instead of in the general AMI directory. I fixed this by upgrading jclouds to 1.1.1 (it was still on an early beta) and by removing an deprecated and obsolete property where the ComputeServiceContextFactory is created.
--
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] (ACE-187) AMIs can't be found because the search
location is incorrect
Posted by "Paul Bakker (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Bakker updated ACE-187:
----------------------------
Attachment: Added_sl4j_dependency.patch
> AMIs can't be found because the search location is incorrect
> ------------------------------------------------------------
>
> Key: ACE-187
> URL: https://issues.apache.org/jira/browse/ACE-187
> Project: Ace
> Issue Type: Bug
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: Added_sl4j_dependency.patch, jclouds.patch
>
>
> While using the Amazon node launcher AMIs that do exist can't be found by Ace. This is because jclouds now searches AMIs that already exist in the list of instances instead of in the general AMI directory. I fixed this by upgrading jclouds to 1.1.1 (it was still on an early beta) and by removing an deprecated and obsolete property where the ComputeServiceContextFactory is created.
--
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] (ACE-187) AMIs can't be found because the search
location is incorrect
Posted by "Paul Bakker (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Bakker updated ACE-187:
----------------------------
Attachment: jclouds.patch
> AMIs can't be found because the search location is incorrect
> ------------------------------------------------------------
>
> Key: ACE-187
> URL: https://issues.apache.org/jira/browse/ACE-187
> Project: Ace
> Issue Type: Bug
> Reporter: Paul Bakker
> Attachments: jclouds.patch
>
>
> While using the Amazon node launcher AMIs that do exist can't be found by Ace. This is because jclouds now searches AMIs that already exist in the list of instances instead of in the general AMI directory. I fixed this by upgrading jclouds to 1.1.1 (it was still on an early beta) and by removing an deprecated and obsolete property where the ComputeServiceContextFactory is created.
--
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] [Reopened] (ACE-187) AMIs can't be found because the search
location is incorrect
Posted by "Marcel Offermans (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Offermans reopened ACE-187:
----------------------------------
Going to upgrade to jclouds 1.2.1 in stead.
> AMIs can't be found because the search location is incorrect
> ------------------------------------------------------------
>
> Key: ACE-187
> URL: https://issues.apache.org/jira/browse/ACE-187
> Project: Ace
> Issue Type: Bug
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: jclouds.patch
>
>
> While using the Amazon node launcher AMIs that do exist can't be found by Ace. This is because jclouds now searches AMIs that already exist in the list of instances instead of in the general AMI directory. I fixed this by upgrading jclouds to 1.1.1 (it was still on an early beta) and by removing an deprecated and obsolete property where the ComputeServiceContextFactory is created.
--
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] [Reopened] (ACE-187) AMIs can't be found because the search
location is incorrect
Posted by "Paul Bakker (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Bakker reopened ACE-187:
-----------------------------
jclouds 1.2.1 has a dependency on sl4j. I added this to the pom (see patch). With sl4j it works again.
> AMIs can't be found because the search location is incorrect
> ------------------------------------------------------------
>
> Key: ACE-187
> URL: https://issues.apache.org/jira/browse/ACE-187
> Project: Ace
> Issue Type: Bug
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: jclouds.patch
>
>
> While using the Amazon node launcher AMIs that do exist can't be found by Ace. This is because jclouds now searches AMIs that already exist in the list of instances instead of in the general AMI directory. I fixed this by upgrading jclouds to 1.1.1 (it was still on an early beta) and by removing an deprecated and obsolete property where the ComputeServiceContextFactory is created.
--
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