Deployment Models in OpenStack
Last Updated :
30 Mar, 2023
Pre-requisite: OpenStack
OpenStack has a set of software tools for providing various cloud computing platforms for public and private clouds. OpenStack is managed by the OpenStack Foundation, a non-profit that oversees both development and community-building around that project. OpenStack is the future of cloud computing backed by some of the biggest companies.
The deployment models of OpenStack are as follows:
- On-Premises Distribution
- OpenStack-Based Public Cloud
- Hosted OpenStack Private Cloud
- OpenStack-As-A-Service
- Application Based OpenStack
On-Premises Distribution:
An OpenStack distribution is downloaded and installed by a customer in this model on their internal network. It is implemented in a do-it-yourself (DIY) manner using Homebrew or utilizing a particular vendor’s OpenStack distribution. Here the data center lies in the company(on-premise). They are your servers and then you can lay out a layer of OpenStack on top of your data centers.
Advantages:
- Security: Your data cannot go beyond the network perimeter.
- Customizable: OpenStack can be customized to suit an organization’s requirements.
- Hardware independence: We can utilize hardware from various Cloud vendors
Disadvantages:
- High operational costs: There are high costs associated with activities like configuring, monitoring, backing up, and upgrading OpenStack, which is aggravated by the cost associated with the limited skilled OpenStack staff available on the market.
- Time to value: Homebrew projects are prone to stall due to technical challenges and a lack of skilled staff; implementation with a vendor-supported distribution has the same challenges, but a packaged distribution can help somewhat.
- Creates pits: Having different OpenStack deployments across multiple parts of the world can create infrastructure pits. It’s possible but challengin