From: Jeff Darcy <jdarcy@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Project Hail <hail-devel@vger.kernel.org>
Subject: Re: a boto-works test for tabled?
Date: Fri, 18 Dec 2009 10:57:45 -0500 [thread overview]
Message-ID: <4B2BA679.9020202@redhat.com> (raw)
In-Reply-To: <4B2B55FA.2070109@garzik.org>
On 12/18/2009 05:14 AM, Jeff Garzik wrote:
> Is there anyone that would be interested in copying (or directly use)
> /usr/lib/python2.6/site-packages/boto/tests/test_s3connection.py as a
> tabled "boto-works" test? According to the boto author, boto should
> accept non-Amazon hostnames, which is the only requirement outside of
> Amazon AWS specifications that tabled has.
Boto can accept non-Amazon hostnames, but there's a bit of a trick to
making it work with tabled. As of September 10, this was the magic formula.
>>> import boto
>>> import logging
>>> boto.set_file_logger("boto","/tmp/boto.out",logging.DEBUG)
>>> from boto.s3 import Connection
>>> x = Connection("foo","bar",host="localhost4",port=18080,is_secure=False,debug=99,calling_format=boto.s3.connection.OrdinaryCallingFormat())
>>> x.get_all_buckets()
The magic is in the calling_format part, which took a little while to
puzzle through. We should probably consider supporting the default
calling format to make use of boto-based tools easier.
next prev parent reply other threads:[~2009-12-18 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 10:14 a boto-works test for tabled? Jeff Garzik
2009-12-18 15:57 ` Jeff Darcy [this message]
2009-12-18 17:09 ` Pete Zaitcev
2009-12-18 17:16 ` Jeff Darcy
2009-12-18 18:47 ` Jeff Garzik
2009-12-18 18:45 ` Jeff Garzik
2009-12-18 17:15 ` Pete Zaitcev
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=4B2BA679.9020202@redhat.com \
--to=jdarcy@redhat.com \
--cc=hail-devel@vger.kernel.org \
--cc=jeff@garzik.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.