Embed Size (px)
Citation preview
MELISSA PALMER
So You Want to Convince the Boss to Run OpenStack?
Introducing OpenStack to the Enterprise
About:You
You’ve had OpenStack running on your laptop or in the lab for a while
You’re comfortable sitting down with someone and giving them a tour of OpenStack
You’re comfortable talking about the different OpenStack programs
You think OpenStack would be a good fit for your organization, and you want to go further
You have an understanding of your organization’s business requirements and how they relate to IT
Getting Ready for “The Talk”
Focus on a business problem What are you trying to solve? What benefit will it bring to the organization?
Talk to other groups who will ultimately be involved Know your developers Know your ops teams Know your infrastructure teams Know your business stakeholders
Having “The Talk”
Start Small Don’t try to boil the ocean
Anticipate objections What would your issues be if you were in your boss’
shoesDon’t get discouraged
This project may not be the one
Example: Alice the Infrastructure Architect
XYZ Corp is looking to deploy a new internal web application for time tracking, which will be constantly updated with new features based on employee feedback
Alice thinks this is a great application to pilot OpenStack with Internal, and low risk Alice used to work on the development team, and
knows them very well Alice believes OpenStack will allow the development
team to spin up their environments much quicker, and the QA team can also benefit from this
Example: Alice Talks to Her Boss, Bob
Bob objects because he believes “OpenStack will be too difficult to install and update” Alice proposes using an OpenStack distribution to
streamline both the deployment and update processesBob is worried this will impact the multi-
hypervisor strategy XYZ corp has been looking to implement Alice assures Bob OpenStack can work with either of the
organization’s hypervisors and may even help them further enable this strategy
Bob is still weary Alice proposes deploying the application in parallel on
OpenStack as well as using their existing process.
Dealing with a StackBlocker
No one uses OpenStack Plenty of big organizations do (think keynote) Lots of “everyday enterprises do too” (think Superuser awards) Over 50% of OpenStack workloads are production (Superuser
survery)Don’t touch my infrastructure!
OpenStack can operate side by side with your existing infrastructure
No rip and replace neededWe don’t do science experiments here!
NASA used to be a science experiment, now SpaceX Innovation is NOT a bad thing, tie it to business requirements
Alice’s Next Steps
Alice holds meetings with the dev, ops, and business teams before bringing them all together before kickoff Alice converses with each team, and provides
information in order to address any fears and concerns, Ops has the most concerns
Alice works with the Ops team to pick an OpenStack distribution that fits their organization, in order to further ease concerns
In the end, OpenStack is preferred to the organization's traditional methods!
Key Takeaways
Have a problem to solve with OpenStack Technology is cool, but we aren’t likely to get budget
to deploy new technology for the sake of deploying new technology
Be ready to have many discussions throughout the organization Things are most successful when everyone is onboard Chances are there will be many who don’t understand
what OpenStack isSeek continuous feedback throughout the
process If someone isn’t happy, no one will be happy
Community
Don’t forget the OpenStack community! We’re here to help!
