Re: [openstack-dev] [savanna] why swift-internal:// ?

2014-01-28 Thread Sergey Lukjanov
Matt, thanks for catching this. BTW That's an interesting idea of supporting different tenants. On Fri, Jan 24, 2014 at 11:04 PM, Matthew Farrellee m...@redhat.com wrote: thanks for all the feedback folks.. i've registered a bp for this...

Re: [openstack-dev] [savanna] why swift-internal:// ?

2014-01-24 Thread Matthew Farrellee
andrew, what about having swift:// which defaults to the configured tenant and auth url for what we now call swift-internal, and we allow for user input to change tenant and auth url for what would be swift-external? in fact, we may need to add the tenant selection in icehouse. it's a

Re: [openstack-dev] [savanna] why swift-internal:// ?

2014-01-24 Thread Erik Bergenholtz
On Jan 24, 2014, at 7:50 AM, Matthew Farrellee m...@redhat.com wrote: andrew, what about having swift:// which defaults to the configured tenant and auth url for what we now call swift-internal, and we allow for user input to change tenant and auth url for what would be swift-external? I

Re: [openstack-dev] [savanna] why swift-internal:// ?

2014-01-24 Thread Andrew Lazarev
what about having swift:// which defaults to the configured tenant and auth url for what we now call swift-internal, and we allow for user input to change tenant and auth url for what would be swift-external? I like the proposal. Andrew. On Fri, Jan 24, 2014 at 4:50 AM, Matthew Farrellee

Re: [openstack-dev] [savanna] why swift-internal:// ?

2014-01-24 Thread Trevor McKay
Matt et al, Yes, swift-internal was meant as a marker to distinguish it from swift-external someday. I agree, this could be indicated by setting other fields. Little bit of implementation detail for scope: In the current EDP implementation, SWIFT_INTERNAL_PREFIX shows up in essentially two

Re: [openstack-dev] [savanna] why swift-internal:// ?

2014-01-24 Thread Sergey Lukjanov
Looks like we need to review prefixes and cleanup them. After the first look I'd like the idea of using common prefix for swift data. On Fri, Jan 24, 2014 at 7:05 PM, Trevor McKay tmc...@redhat.com wrote: Matt et al, Yes, swift-internal was meant as a marker to distinguish it from

Re: [openstack-dev] [savanna] why swift-internal:// ?

2014-01-24 Thread Matthew Farrellee
thanks for all the feedback folks.. i've registered a bp for this... https://blueprints.launchpad.net/savanna/+spec/swift-url-proto-cleanup On 01/24/2014 11:30 AM, Sergey Lukjanov wrote: Looks like we need to review prefixes and cleanup them. After the first look I'd like the idea of using

Re: [openstack-dev] [savanna] why swift-internal:// ?

2014-01-23 Thread Andrew Lazarev
Matt, I can easily imagine situation when job binaries are stored in external HDFS or external SWIFT (like data sources). Internal and external swifts are different since we need additional credentials. Thanks, Andrew. On Thu, Jan 23, 2014 at 5:30 PM, Matthew Farrellee m...@redhat.com wrote:

Re: [openstack-dev] [savanna] why swift-internal:// ?

2014-01-23 Thread Matthew Farrellee
what makes it internal vs external? swift-internal needs user pass swift-external needs user pass ?auth url? best, matt On 01/23/2014 08:43 PM, Andrew Lazarev wrote: Matt, I can easily imagine situation when job binaries are stored in external HDFS or external SWIFT (like data