OpenStack efficiencies can be a two-edged sword. Sure, it can empower developers to invoke well-specified infrastructure services and build more cool stuff faster. But at the same time, the diversity of options and components in your infrastructure you want to deploy as a service means your cloud can get fragmented into messy underlying configurations and spin out of control: goodbye efficiency. And if your developers love your OpenStack cloud? Success is its own punishment.
How can you achieve reliable operation at scale in large distributed deployments, without sacrificing rapid adoption of new features?
Much of the emerging technologies supporting OpenStack deployment and automation focuses on helping build the foundational elements of your OpenStack cloud. At Mirantis, across over 60 customer deployments, we’ve developed a set of pre- and post-flight checks to ensure that your OpenStack cloud can overcome that fragmentation. We’ll review those along with the best practices in deployment, monitoring, management, and maintenance. By taking advantage of this accumulated experience rather than re-inventing the wheel, you can speed the time to benefit for OpenStack. What’s more, once your cloud is up and running, these strategies mean that rather than firefighting, infrastructure teams can design/architect new services that developers and users use to capture value for their organization.