Support arbitrary endpoints

[Duncan McGreggor]

txAWS currently has Amazon endpoints hard-coded. If it's going to support non-Amazon, EC2-compatible services, we need to make some changes. For example, developers should be able to set the port, schema, url, endpoint, etc.

[Robert Collins (lifeless)]

I'd like to be able to define a friendly name/object for services, and
then pass that in as an optional parameter when getting an api handle

-Rob

[Duncan McGreggor (oubiwann)]

Rob +1 on that. Was thinking about it last night and was wondering how long it'd be before we felt the need for that.

[Duncan McGreggor (oubiwann)]

Merged 416109-arbitrary-endpoints [r=therve,jkakar] [f=416109].

The primary change of this branch is support of arbitrary endpoints (needed for
the support of Eucalyptus). In addition, the following was also performed:
 * Added a parse utility function from Twisted
 * Created a testing subpackage for use by txAWS unit tests
 * Created a service module for abstracting regions and associated
   serices/credentials

[Robert Collins (lifeless)]

On Tue, 2009-09-22 at 16:03 +0000, Andreas Hasenack wrote:
> ** Tags added: needs-testing

What does this really mean? {I'm wearing my community contributor hat
here, to avoid any confusion}.

The code was written reviewed, integrated into the GUI such as we have
and landed in trunk. I don't think we have a release scheduled planned
for txaws, and even if we did, the unit tests for this are more than
sufficient.

-Rob

[Duncan McGreggor (oubiwann)]

Hey Rob,

Sorry about the confusion! This ticket was linked as affecting the
Landscape project, and every milestone we label all tickets for the
milestone as needs-testing and then go through them all in
production-like environments and run them through a QA process.

d

P.S. I'm still not back at work :-) One more day of moving crap into
the "new" house, getting internet, and setting up the network...

On Tue, Sep 22, 2009 at 4:40 PM, Robert Collins
<email address hidden> wrote:
> On Tue, 2009-09-22 at 16:03 +0000, Andreas Hasenack wrote:
>> ** Tags added: needs-testing
>
> What does this really mean? {I'm wearing my community contributor hat
> here, to avoid any confusion}.
>
> The code was written reviewed, integrated into the GUI such as we have
> and landed in trunk. I don't think we have a release scheduled planned
> for txaws, and even if we did, the unit tests for this are more than
> sufficient.
>
> -Rob
>
> --
> Support arbitrary endpoints
> https://bugs.launchpad.net/bugs/416109
> You received this bug notification because you are a member of txAWS
> Administration, which is the registrant for txAWS.
>
> Status in Landscape Server: Fix Committed
> Status in txAWS: Twisted Amazon: Fix Committed
>
> Bug description:
> txAWS currently has Amazon endpoints hard-coded. If it's going to support non-Amazon, EC2-compatible services, we need to make some changes. For example, developers should be able to  set the port, schema, url, endpoint, etc.
>