All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@42on.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: PowerDNS backend for Rados Gateway to direct bucket traffic
Date: Sun, 03 Nov 2013 15:15:26 +0100	[thread overview]
Message-ID: <52765A7E.9040306@42on.com> (raw)

Hi,

I'm playing with an idea, but I'm not sure if I'm taking the correct route.

When you create a bucket with Amazon S3 it's always reachable via 
bucketname.s3.amazonaws.com.

Depending on the region you created it in you'll get a different 
response from their DNS servers directing you to the correct HTTP endpoint.

When you use the RGW with multiple regions you get a 301 redirect from a 
region if the bucket is not located there.

This 301 is extra TCP traffic and adds extra latency. You could 
potentially have a developer who is mistaken and directs thousands of 
requests to the wrong region which are all answered with 301 redirects. 
A waste of resources.

I've worked with PowerDNS a lot and it supports various backends and one 
of them is the Pipe or HTTP (new!) backend [0]

It would be rather cool if you could have a global domainname like 
"s3.amazonaws.com", but behind it you have multiple regions, but based 
on the DNS request you do PowerDNS responds with a different CNAME.

global: o.myobject.store
EU:     eu.myobject.store
US:     us.myobject.store

Based on where the bucket is PowerDNS will respond with:

CNAME bucket.eu.myobject.store
or
CNAME bucket.us.myobject.store

Does it sound reasonable what I'm thinking of or am I completely wrong 
about this?

[0]: http://doc.powerdns.com/html/remotebackend.html

-- 
Wido den Hollander
42on B.V.

Phone: +31 (0)20 700 9902
Skype: contact42on

             reply	other threads:[~2013-11-03 14:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-03 14:15 Wido den Hollander [this message]
2013-11-07 21:09 ` PowerDNS backend for Rados Gateway to direct bucket traffic Kyle Bader
2013-11-08  4:37   ` Sage Weil
2013-11-09 15:46     ` Wido den Hollander

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52765A7E.9040306@42on.com \
    --to=wido@42on.com \
    --cc=ceph-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.