What is our primary use case?
It replaces our entire server infrastructure. Everything that we do today has now been replaced by GreenLake, as far as our data center is concerned.
I haven't got all my workloads on it yet, so I don't really know how it performs when it's fully loaded. It is certainly looking very positive, but I just don't know yet.
How has it helped my organization?
The performance of our batch workloads with SLAs (for our batch reporting) will start to be met.
It helps with our IT team's productivity, as they can focus on their day-to-day jobs rather than adding the management of the infrastructure into their task list. Thus, they can focus on the more business critical components of their role.
What is most valuable?
We like the way that we can OPEX the service.
Its performance is a significant improvement over the legacy stack that we had.
It sort of lines up with our direction to move to the cloud. By using a hybrid cloud service to get us there, this allows us to run our legacy workloads on-premise. Those which are not really suited to a proper cloud.
It is pretty simple to use. The team is able to pick up OneView pretty fast, and they are extracted away from the underlying working, which is cool for us.
What needs improvement?
It offers flexibility in IT operations, but it hasn't done it yet. We should see this in the future.
We are still managing the VMs in our IT operations.
For how long have I used the solution?
I'm not fully live with all my workloads.
What do I think about the stability of the solution?
We don't have all our workloads on there at the moment. We have had a few little teething issues, but they have been rectified very quickly by the HPE support team. Therefore, it seems okay. We will know more in a year or so.
What do I think about the scalability of the solution?
It certainly appears to scale well beyond what we need it to do.
How are customer service and technical support?
The technical support has been very good and proactive. We have had problems that have been resolved in appropriate timelines.
Which solution did I use previously and why did I switch?
It is replacing an existing, legacy SAN and compute stack. The existing stack, Fujitsu, was coming out of support, and we couldn't get parts for it anymore.
How was the initial setup?
The initial setup was done for us, so it was straightforward from our behalf.
The interconnects were a challenge originally, but they sorted that out, and It was fine. We did have to spend a bit more money, but it wasn't really a problem.
What about the implementation team?
We used a third-party. However, they had to engage HPE, as they weren't able to do the work themselves.
They have some learning to do in relation to the new HPE kit. It is relatively new. There are always problems and challenges with this type of implementation, and the end result has been good. I can only say the outcome has been fine.
What was our ROI?
I don't think we'll know until we get to the end of the contract if the service has saved us money.
Which other solutions did I evaluate?
We also evaluated Fujitsu, IBM, and Dell EMC.
We went with HPE GreenLake because the OPEX model for us just works. It helps us start to align with the company vision for an OPEX, cloud-based service.
We compared this against a pure, public cloud solution, and hands down, this was better for us because of our legacy workloads.
What other advice do I have?
Understand what your compute workloads will be and be really clear on that. Otherwise, you will procure starting up with too much or little. Just make sure you understand what your compute will be so you can get your contract set up the right way.
It is doing what we need it to now, over and above what we had before.
While provisioning is quicker, we are not provisioning much new infrastructure into the kit at this stage.
We expect our capacity will actually go down over time, not up. Though, if we change direction or had an acquisition, it provides flexibility without having to go back for a CAPEX spend to get more infrastructure.
I don't think it has eliminated corporate provisioning. We can provision what we need and get more if we need it. Our intention would be to use less, not more. I don't think we have had to over buy. If we hadn't had gone down the pathway of a traditional SAN, we probably wouldn't have purchased what we are running with the GreenLake kit now, since our stacks would disappear over the next few years due to business transformation.
Disclosure: I am a real user, and this review is based on my own experience and opinions.