Open Stack

Jon,


When dealing with software migrations setting up a staging environment
is a must.   Set up your staging environment with as many production
configs as possible and install the current code then add data.   Be
sure you can add data that represents your actual use cases.  Once
that's done upgrade the machines on one zone and run your tests.   At
that point, you should be able to determine the functional impact.

Some important things to test:
Are there problems with objects or containers replicating from old
code vs new code
Are old accounts, containers, and objects working well on using the new code.

The dispersion-report is a great tool for production monitoring but it
can be very useful for testing too.


Production upgrades.    Depending on your use case you can shutdown
all backend processes for a short time, upgrade the machines, then
restart them.    Another things to keep in mind is that with a cluster
of more four zones a single zone can be updated and watched to
determine the impact and them either pull it out of the ring and reset
it or continue upgrading the next zone.


--J

On Wed, May 18, 2011 at 10:14 AM, Clay Gerrard
<clay.gerrard at rackspace.com> wrote:
> 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 at lists.launchpad.net
>> [mailto:openstack-
>> bounces+clay.gerrard=rackspace.com at lists.launchpad.net] On Behalf Of
>> Jon Slenk
>> Sent: Tuesday, May 17, 2011 5:34 PM
>> To: openstack at lists.launchpad.net
>> 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 at lists.launchpad.net
>> 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 at rackspace.com, and delete the original message.
> Your cooperation is appreciated.
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>