You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Tom White (JIRA)" <ji...@apache.org> on 2010/11/09 06:53:22 UTC

[jira] Created: (WHIRR-137) Allow use of an arbitrary AMI on EC2

Allow use of an arbitrary AMI on EC2
------------------------------------

                 Key: WHIRR-137
                 URL: https://issues.apache.org/jira/browse/WHIRR-137
             Project: Whirr
          Issue Type: Bug
          Components: core
            Reporter: Tom White


jclouds restricts AMI owners to Amazon, Alestic, Canonical, and Rightscale to avoid slow image ID listings. This can be changed (to pick up your own AMIs) by setting jclouds.ec2.ami-owners to a comma-separated list of owner IDs.

ComputeServiceContextBuilder needs to construct a ComputeServiceContext which passes a properties file with this property from the Whirr configuration. In fact, it should probably pass all properties that start with "jclouds." to ComputeServiceContextBuilder.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (WHIRR-137) Allow use of an arbitrary AMI on EC2

Posted by "Tom White (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WHIRR-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom White resolved WHIRR-137.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 0.3.0

I've just committed this.

> Allow use of an arbitrary AMI on EC2
> ------------------------------------
>
>                 Key: WHIRR-137
>                 URL: https://issues.apache.org/jira/browse/WHIRR-137
>             Project: Whirr
>          Issue Type: Bug
>          Components: core
>            Reporter: Tom White
>            Assignee: Tom White
>             Fix For: 0.3.0
>
>         Attachments: WHIRR-137.patch
>
>
> jclouds restricts AMI owners to Amazon, Alestic, Canonical, and Rightscale to avoid slow image ID listings. This can be changed (to pick up your own AMIs) by setting jclouds.ec2.ami-owners to a comma-separated list of owner IDs.
> ComputeServiceContextBuilder needs to construct a ComputeServiceContext which passes a properties file with this property from the Whirr configuration. In fact, it should probably pass all properties that start with "jclouds." to ComputeServiceContextBuilder.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (WHIRR-137) Allow use of an arbitrary AMI on EC2

Posted by "Tom White (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WHIRR-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom White reassigned WHIRR-137:
-------------------------------

    Assignee: Tom White

> Allow use of an arbitrary AMI on EC2
> ------------------------------------
>
>                 Key: WHIRR-137
>                 URL: https://issues.apache.org/jira/browse/WHIRR-137
>             Project: Whirr
>          Issue Type: Bug
>          Components: core
>            Reporter: Tom White
>            Assignee: Tom White
>         Attachments: WHIRR-137.patch
>
>
> jclouds restricts AMI owners to Amazon, Alestic, Canonical, and Rightscale to avoid slow image ID listings. This can be changed (to pick up your own AMIs) by setting jclouds.ec2.ami-owners to a comma-separated list of owner IDs.
> ComputeServiceContextBuilder needs to construct a ComputeServiceContext which passes a properties file with this property from the Whirr configuration. In fact, it should probably pass all properties that start with "jclouds." to ComputeServiceContextBuilder.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (WHIRR-137) Allow use of an arbitrary AMI on EC2

Posted by "Tom White (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WHIRR-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom White updated WHIRR-137:
----------------------------

    Attachment: WHIRR-137.patch

Here's a patch with a fix.

> Allow use of an arbitrary AMI on EC2
> ------------------------------------
>
>                 Key: WHIRR-137
>                 URL: https://issues.apache.org/jira/browse/WHIRR-137
>             Project: Whirr
>          Issue Type: Bug
>          Components: core
>            Reporter: Tom White
>         Attachments: WHIRR-137.patch
>
>
> jclouds restricts AMI owners to Amazon, Alestic, Canonical, and Rightscale to avoid slow image ID listings. This can be changed (to pick up your own AMIs) by setting jclouds.ec2.ami-owners to a comma-separated list of owner IDs.
> ComputeServiceContextBuilder needs to construct a ComputeServiceContext which passes a properties file with this property from the Whirr configuration. In fact, it should probably pass all properties that start with "jclouds." to ComputeServiceContextBuilder.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.