Companies new to OpenStack will often go through an initial time period to build a proof-of-concept cloud. If the team building it succeeds and is given the green light to bring OpenStack to the enterprise, they may find themselves in a situation where they have to build out OpenStack as quickly as possible, put it into production and support the users who are using it. What does it take to run an OpenStack environment? Some of the topics to be discussed include:
- What is operations and how do you operationalize what you have?
- Defining the support model, tooling and knowledge management
- Monitoring and who gets the alerts; building the escalation model
- Lifecycle management; reclaiming resources, maintenances, upgrades
- Capacity planning and should you overcommit resources?
- Who are the “customers” and how do they interact with the team?
Attendies should learn from the experiences of two support professionals who have been instrumental in "operationalizing" platforms for multiple shops. The main takeaways should be the proper mindset and managerial buy-in needed, the support model options, tooling required or suggested, such as ticketing, monitoring, integration, and knowledge management, and how to define the scope for the operational support.