Battle Scars from OpenStack Deployments
This is the first liveblog from day 2 of the OpenStack Summit in Sydney, Australia. The title of the session is “Battle Scars from OpenStack Deployments.” The speakers are Anupriya Ramraj, Rick Mathot, and Farhad Sayeed (two vendors and an end-user, respectively, if my information is correct). I’m hoping for some useful, practical, real-world information out of this session.
Ramraj starts the session, introducing the speakers and setting some context for the presentation. Ramraj and Mathot are with DXC, a managed services provider. Ramraj starts with a quick review of some of the tough battles in OpenStack deployments:
- Months to deploy OpenStack at scale
- Chaos during incidents due to lack of OpenStack skills and knowledge
- Customers spend lengthy periods with support for troubleshooting basic issues
- Applications do not get onboarded to OpenStack
- Marooned on earlier version of OpenStack
- OpenStack skills are hard to recruit and retain
Ramraj recommends using an OpenStack distribution versus “pure” upstream OpenStack, and recommends using new-ish hardware as opposed to older hardware. Given the last bullet, this complicates rolling out OpenStack and resolving OpenStack issues. A lack of DevOps skills and a lack of understanding around OpenStack APIs can impede the process of porting applications Continue reading
Much of the technology comes from recent cloud security acquisitions.
Kubernetes is the top container platform of OpenStack users.
Security and familiarity were cited as tipping the choice in favor of VMs.
Juniper realigns workforce; Dell EMC and Nutanix fight for No. 1 HCI spot; Cisco's $1.9B purchase.
If accepted, it would create a WiFi, automotive, and location chip powerhouse.
The technology comes from HPE's $275 million SGI acquisition last year.