openstack team mailing list archive

[Clay Gerrard <clay.gerrard@xxxxxxxxxxxxx>]

Hey Jon,

Specially regarding "expanding the ring" - one of the Cloud Files ops wrote some tips in a lp answer awhile back:
https://answers.launchpad.net/swift/+question/152024

Clay Gerrard
Software Developer
Rackspace


> -----Original Message-----
> From: openstack-bounces+clay.gerrard=rackspace.com@xxxxxxxxxxxxxxxxxxx
> [mailto:openstack-
> bounces+clay.gerrard=rackspace.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> Jon Slenk
> Sent: Tuesday, May 17, 2011 5:34 PM
> To: openstack@xxxxxxxxxxxxxxxxxxx
> Subject: [Openstack] testing and deploying swift?
> 
> hi,
> 
> So what are people's processes for tracking Swift releases, on
> production systems?
> 
> I'm guessing Rackspace is probably the most serious deployment to
> date. If anybody there could comment on what release of Swift is being
> run and how you expect to deploy newer versions, that would be fun and
> educational to hear about and mull over.
> 
> If anybody working on core Swift could comment on which parts of the
> system are more vs. less dangerous to muck with, that would be great,
> too. For one example, we're still trying to grok the implications of
> significantly changing the Rings (expanding them, usually). Like, what
> even qualifies as "significant" vs. not.
> 
> thanks for sharing any experiences,
> -Jon.
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp


Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is prohibited.
If you receive this transmission in error, please notify us immediately by e-mail
at abuse@xxxxxxxxxxxxx, and delete the original message.
Your cooperation is appreciated.