What is our primary use case?
Our whole company uses it. We have VxRail in our solution center, which designs software and hardware solutions for our customers' new opportunities. For example, recently, we were asked to develop a Kubernetes environment that the customer wanted to use and researched several different organizations, such as Red Hat's OpenShift.
We wanted to test capabilities on Tanzu, and VxRail was a great home for that, so we brought all the software into the VxRail and showed the inner workings of the data flows for this new capability to the customer. In the end, they didn't necessarily need a VxRail, but that's the beauty of it. It's a vanilla platform to reside modernized software on.
What is most valuable?
The VxRail is built on two specific platforms that have been in the industry for the last 15 to 20 years: the 1-U socket and the 2-U socket platforms from Dell. They're in their sixteenth generation of those platforms, I believe, so they're very stable.
What needs improvement?
VxRail is in its third generation, I think, and I know there are consistent updates to that material on nearly a monthly basis. Most of my customers are federally focused, which means some of this material comes into an environment where few people will have access to that environment.
I would like to see Dell take a crack at simplifying the process of moving from a node to a cluster and assembling everything into the appliance. It would be great if Dell could provide a pathway where a customer could actually install it without the certifications. Of course, I can't say how you would dumb down something so complex. That's a challenge, but it would be valuable.
It would also be helpful if they added some warnings to prevent users from making mistakes when upgrading stuff with VMware, like a notification that says, "Hey, this upgrade should be done through the VxRail manager." Those could steer customers off the path of decoupling that cluster or pulling a node offline when it doesn't need to be.
These things have room to grow in the industry. As more organizations look to develop what they currently have, Dell could provide a pathway to taking integrating the older hardware with the new hardware. I think that would be valuable, too. There are a couple of things that I'd also like to see them improve upon. One could be to actually deliver a cluster to the customer from their manufacturing facility that is already put together. That might be a good opportunity for them.
What do I think about the stability of the solution?
The VxRail platform is stable. Anytime you're dealing with technologies, you'll find a bug somewhere. There's always a challenge that must be overcome, but once the initial cluster has been stood up, we find it's one of the most stable platforms today.
What do I think about the scalability of the solution?
If you want to scale VxRail, you buy another node and add it to the cluster. That process is straightforward. It will re-image the new node, give it the same firmware, and provide the same orchestration as the rest of the node. Scalability is probably one of the biggest reasons people choose VxRail.
How are customer service and support?
I've contacted Dell tech support on many occasions for VxRail. I always put in a case with Dell on all the service tags of the nodes before taking on any support mechanism. I recommend starting that process early. One of the main reasons we put in a case is to do some maintenance or make some changes.
We always consult with Dell on best practices initially. It helps to provide them with as much information as possible about the health and wellness of that initial cluster. It generally depends on the service agreement you get from Dell, but we'll get a response in five or 10 minutes after putting in that initial case.
I've never had problems with Dell support, but I always recommend pro support from my customers and organization. Depending on the size of your organization and how much Dell hardware you have, they'll assign a technical account manager to your team or to the Dell team, so you always have a consistent point of contact if things don't go as planned. That's helpful if you have a technical account manager assigned to your organization.
How was the initial setup?
VxRail is a hyper-converged system that's automated and consists of nodes. Those nodes are one or two U-servers depending on the requirement. Bringing the VMware automation and lifecycle management platform together is difficult, so we recommend having a certification to do that assemblage.
It assembles these servers into nodes in an appliance. Once the appliance is set up, it's simple to manage the solution and the box. However, assembly and automation are complex. You want to make sure that the firmware is all the same between the nodes.
We've seen situations where we had a five-node cluster, and one firmware was not mapped to the others. We recommend working with Dell on those challenges, but our architects are also really well versed in those nuances. And if you want to deep dive into a technical requirement, I have several that have done that for a living.
What other advice do I have?
I rate VxRail eight out of 10. I would say it is the go-to solution for hyper-converged infrastructure.
The scripts that bring all of those servers into a node and cluster situation are proprietary to Dell. Anytime you're using that proprietary stuff, you need to be trained on it. Let's say, for example, you are in one of those systems, and you're working with some software that may not be acting like it should. Or it may have a feature that you want in a new generation. In some cases, there may be some dependencies on vCenter, vSAN, or Vsphere, which are all part of that integration.
One might be tempted to start to upgrade it outside of the lifecycle management that's inherent to the VMware platform. I've seen architects go ahead and update it right from the VMware console when they should be using the VxRail manager. Knowing how to do those upgrades is very important to getting the clusters to see the proper nodes together.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner