From: Pete Zaitcev <zaitcev@redhat.com>
To: Project Hail List <hail-devel@vger.kernel.org>
Cc: zaitcev@redhat.com
Subject: Hailcam (webcam for S3)
Date: Fri, 21 May 2010 14:43:57 -0600 [thread overview]
Message-ID: <20100521144357.4d2b11dc@redhat.com> (raw)
Since we do not have many users for tabled (well, just one: Darcy's ImStore),
and I want test it, I have to make one up. So, I came up with an idea to
keep a webcam stream in S3. The camera box just snaps it and uploads
every frame into tabled's store, then a backgroud packer processes the
stream (e.g. adds thumbnails or makes a stop-motion video), and a client
access it. Voila, a real-life test that can be left run forever, scales
up with the number of clients, and can be verified by eye instantly.
So far it's a couple of sripts, hailcamsnap.py and hailcampack.py,
and a spec for the key namespace, so that new clients, packers, and
webcams can be added easily. I threw them at this page:
http://people.redhat.com/zaitcev/linux/
I don't expect this be useful right away, but in case anyone wants to
run a collection of webcams tied with an S3 back-end, here it is.
Stranger things happened.
-- Pete
reply other threads:[~2010-05-21 20:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100521144357.4d2b11dc@redhat.com \
--to=zaitcev@redhat.com \
--cc=hail-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).