HPE OneView Review

You can manage rack mount servers, blades, and blade chassis from one single pane of glass.


What is most valuable?

The single pane-of-glass and unified API allows you to handle everything from one single interface. The best thing about OneView is that you can manage rack mount servers, blades, and blade chassis, all from one single pane of glass.

How has it helped my organization?

It's helped in terms of monitoring, deployments, and being able to know what we have out there. We can actually integrate some of those features to manage things from afar, even from outside the data centers, as long as we have our onboard administrators configured correctly.

It works really well for basic day-to-day administrator functions without having to go into every single iLO, or every single detail for configuration.

It's really neat to be able to just slide in a new blade server, throw a blade profile on it through OneView, and that is all of the configuration that you need.

What needs improvement?

I can't think of anything off the top of my head for the next release. I think some of the stuff that's coming with Synergy is already going to be included there, like a lot of the OS integrations.

You can do some of that with Image Streamer and a Synergy chassis. A lot of those things go through OneView, which acts as its own Synergy composer, that takes you to the Image Streamer appliance. Those are their own OneView instances, so to speak.

The coming features I heard about at a recent conference are probably what I would have suggested anyway.

What do I think about the stability of the solution?

It's been stable so far. Once we got it up and running, we haven't had really any problems with it. We have a single-sign-on implementation for it. Once we got it hooked into our active directory, it has been very stable.

What do I think about the scalability of the solution?

We actually have four, separate, isolated OneView instances with one master OneView on top of it. It's scaled very well so far, even from our initial smaller implementation. We have since scaled that, have experienced the scale, and it has worked really well.

How are customer service and technical support?

I have not used technical support. I believe one of my cohorts has.

Which solution did I use previously and why did I switch?

We knew that we needed to go to OneView when we started investing in the BladeSystem infrastructure. That's the best way to go when you're doing anything BladeSystem related.

How was the initial setup?

I was not involved in the setup. My cohort was.

Which other solutions did I evaluate?

We did not look at other vendors.

When looking at vendors, I look at ease-of-use. Cost is always an important factor, as well as how it integrates with our environment and meets our regulatory requirements.

What other advice do I have?

It is definitely worth it. You can have a single, unified instance to manage everything. It's great from a system admin's perspective. It's worth it.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest
Sign Up with Email