Yesterday, I had the pleasure of chatting with Simon Seagrave all about EVO:RAIL. I’ve known Simon now for a few years, and think we first met through the London VMUG User Group. He works at EMC currently, but he’s probably as well known for his blog TechHead.co. Like many in our community Simon’s a big fan of home labs, and like me we are both work-at-homers. Despite having access to remote labs from our respective employers – we both feel maintaining a home lab is still important – not least because you have cart blance freedom to configure things however you like with access too all the settings. Simon’s blog is well-known for special homelab deals as well as reviews of new gear – to be honest I’m jealous he has such good access!
Simon has been responsible for a number of podcast in the past and currently – sadly both his podcast & blog output has been rather curtailed by recent illness. But I’m so pleased to see him back on his feet, and getting back in the ring. Welcome back to the community, Simon. We’ve missed ya!
Anyway, back to the podcast – you can here it over here. In the podcast Simon asked me the following questions…
- What is EVO:RAIL?
- What is a Hyper-Converged Infrastructure?
- How is EVO:RAIL easy to install, configure and manage?
- What parts of the EVO:RAIL solution does VMware provide & which components/parts do EVO partners provide in the overall solution?
- What are some of the differentiators between EVO partner’s offerings? eg: is it just the hardware it runs on? Also, is there the ability for them to include additional functionality/value-add to the solution at the software layer?
- Typical/planned EVO:RAIL use cases
- How does EVO:RAIL differ from EVO:RACK?
- How to find out more about EVO:RAIL