rrect me, if I am wrong, I
> just try to figure how it works.
>
> But what if the swift endpoint is different from CloudStack mgt server?
> Take Aws console as an example, the aws console is console.aws.amazon.com,
> but the S3 endpoint is s3-console-us-standard.console.aws.amazon.com
h 13, 2014 7:16 PM
> To: Edison Su
> Cc: dev@cloudstack.apache.org; David Nalley (da...@gnsa.us)
> Subject: Re: [REVIEW] OpenStack Swift as Object Storage Service
>
> Lets say that we have the following setup to help clarify how this all works.
>
> CloudStack Managemen
[mailto:williamstev...@gmail.com] On Behalf Of
Will Stevens
Sent: Thursday, March 13, 2014 7:16 PM
To: Edison Su
Cc: dev@cloudstack.apache.org; David Nalley (da...@gnsa.us)
Subject: Re: [REVIEW] OpenStack Swift as Object Storage Service
Lets say that we have the following setup to help clarify how
Su
> *Cc:* dev@cloudstack.apache.org; David Nalley (
> da...@gnsa.us)
> *Subject:* Re: [REVIEW] OpenStack Swift as Object Storage Service
>
>
>
> What are you referring to as the 'v1.0 url hack'? Bypassing the
> cloudstack management server is an intentional d
13, 2014 5:52 PM
To: Edison Su
Cc: dev@cloudstack.apache.org; David Nalley (da...@gnsa.us)
Subject: Re: [REVIEW] OpenStack Swift as Object Storage Service
What are you referring to as the 'v1.0 url hack'? Bypassing the cloudstack
management server is an intentional design decision to
What are you referring to as the 'v1.0 url hack'? Bypassing the cloudstack
management server is an intentional design decision to improve performance.
The introduction of a load balancer in front of the two distinct services
to maintain separation of their traffic is a good thing.
I will review
Hi Will:
This looks interesting; and I am thrilled to see it.
PLUpload is GPLv2 - which likely at best limits us to noredist
inclusion. I haven't yet looked at this in-depth, just got that far in
reading the spec.
--David
On Wed, Mar 12, 2014 at 1:24 PM, Will Stevens wrote:
> Hello Everyone,
>
