Chapter 12. Planning a Swift Deployment

Martin Lanner

Amanda Plimpton

The previous chapter covered the individual hardware requirements and general networking needs of a cluster. This chapter aims to help you build out the requirements and specifications for your own deployment of Swift. In the end, we hope you’ll be able to take advantage of Swift’s flexibility to tailor a deployment that best meets your needs.

When planning an OpenStack Swift deployment, the first step is to define your workload and functional requirements. We will first look at some of the criteria that will help you think through your workload, requirements, and constraints. The rest of the chapter will then focus on system design and networking. System design will look at how many nodes will be needed, how services will be tiered, and what logical grouping of the nodes will best serve the needs of the cluster and take best advantage of Swift’s features. Networking will focus on the different network segments that a Swift cluster might use.

Your Use Case

Every organization has its own intended usage and specifications for its Swift deployment. Influencing factors include storage capacity, access patterns, and geographic location.

Consider the following use cases for a Swift deployment:

  • Software-as-a-service (SaaS) provider, storing application data and serving it with high availability to enterprise customers or end users worldwide
  • General-purpose website, designed to support high-traffic loads
  • Financial service, ...

Get OpenStack Swift now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.