[Openstack] Contribute to the PyCon talk on OpenStack!
Ewan.Mellor at eu.citrix.com
Tue Feb 15 15:15:34 UTC 2011
No, I'm not going to PyCon, and I wasn't involved in the decision, so I couldn't possibly do that talk. I'd love to see it though, because I'd be very interested in a post-mortem.
From: annegentle at justwriteclick.com [mailto:annegentle at justwriteclick.com] On Behalf Of Anne Gentle
Sent: 15 February 2011 15:11
To: Ewan Mellor; Ed Leafe
Cc: openstack at lists.launchpad.net
Subject: Re: [Openstack] Contribute to the PyCon talk on OpenStack!
On Mon, Feb 14, 2011 at 9:45 AM, Ewan Mellor <Ewan.Mellor at eu.citrix.com<mailto:Ewan.Mellor at eu.citrix.com>> wrote:
Is twisted vs eventlet vs threads vs processes vs Tornado vs Django too much of a sore wound? We've only been around 9 months and we've already tried all of them!
Looks like going Twisted > Eventlet is precisely what the abstract for the talk describes. :)
Ewan, are you going to PyCon and want to talk about the trials associated with asynchronous messaging? Sounds like it's right on topic. Ed, I'd hate to see you give up the slot.
I'd think people would be interested in large-scale issues. Tell a story when all hell broke loose, those are always interesting. Any additional fanatical Pythonistas going to PyCon? Cough, Swift, cough. ;)
anne at openstack.org<mailto:anne at openstack.org>
my blog<http://justwriteclick.com/> | my book<http://xmlpress.net/publications/conversation-community/> | LinkedIn<http://www.linkedin.com/in/annegentle> | Delicious<http://del.icio.us/annegentle> | Twitter<http://twitter.com/annegentle>
> -----Original Message-----
> From: openstack-bounces+ewan.mellor=citrix.com<http://citrix.com>@lists.launchpad.net<http://lists.launchpad.net>
> On Behalf Of Ed Leafe
> Sent: 14 February 2011 14:14
> To: openstack at lists.launchpad.net<mailto:openstack at lists.launchpad.net>
> Subject: [Openstack] Contribute to the PyCon talk on OpenStack!
> As some of you know, I agreed to propose, prepare and give a talk
> at next month's US PyCon in Atlanta. I felt that it would be a missed
> opportunity to have one of the biggest and most significant open source
> project in Python not represented at the largest Python conference. The
> talk was accepted, and it's entitled "Dealing with Concurrency in
> Large-Scale Systems".
> I've spoken at PyCon and other conferences before, but always on
> topics that I knew inside and out. When I proposed the talk, I still
> hadn't begun working on OpenStack code yet, and relied on Soren and
> Eric to get to a point where I could write a cogent proposal. So I'm at
> a bit of a disadvantage when it comes to deciding what to focus on.
> That's why I'm writing this: I need those of you who know the
> code base best to identify the stuff that you've worked on that would
> be the most interesting to include in the talk. Remember, the audience
> will be a bunch of experienced Python geeks who will eat up cool or
> unusual approaches to solving technical issues.
> So what is "interesting"? I see several categories:
> 1) Scaling issues: what sort of design decisions were made to
> accommodate the large-scale demands of OpenStack? And what sort of
> atypical implementations were created to make these designs possible?
> 2) New techniques: stuff that if you had heard someone talk about at,
> say, last year's PyCon, you would have been impressed by. Sure, you're
> familiar with it now, after having worked on the OpenStack code base
> for a while, but try to remember the effort of creating that solution
> (if you were the one who did so), or the reaction when you first
> understood someone else's awesome work.
> 3) The unexpected. What did you run into that did not appear as an
> obvious choke point that ended up requiring a bit of work to overcome?
> These types of battle stories always resonate with fellow devs.
> Of course, I will give full credit for any suggestions I use in
> my talk. My goal is to get people who don't know much (or anything)
> about OpenStack to come away from the talk impressed by the incredible
> work being done to make this project happen. I can't do this by myself.
> -- Ed Leafe
> Mailing list: https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack>
> Post to : openstack at lists.launchpad.net<mailto:openstack at lists.launchpad.net>
> Unsubscribe : https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack>
> More help : https://help.launchpad.net/ListHelp
Mailing list: https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack>
Post to : openstack at lists.launchpad.net<mailto:openstack at lists.launchpad.net>
Unsubscribe : https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack>
More help : https://help.launchpad.net/ListHelp
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openstack