![HPE Eucalyptus [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_100/13qmgl48si6583z3hdyvbfnigz48.jpeg?_a=BACAGSGT)
![Cisco Intersight vs HPE Eucalyptus [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_30/0dra2w8zbx5vrvwmhkdswx9l90ys.jpg?_a=BACAGSGT){kind=small}
The most valuable aspect of the solution is the interface on the console.
We do not use most of the features because we have a static environment. We are monitoring most of the applications on those shells.
Good interface, and an easy initial setup with good community support on the free version
What is most valuable?
What needs improvement?
The customization should be improved.
We should be able to diversify the machine for AWS. When we get involved with that right now, it becomes very bad. Some areas of configuration didn't work for us.
The solution should offer more speed and should be able to stabilize the database environment. We've tried to do this, but it hasn't been solid. Sometimes it works, sometimes it doesn't.
If we want to do an interceptor, what we need is a really high level of TT programming or a specific configuration to be able to scale it out. It works to some extent, but it's not strong. When it does not implement in our center we have to go and manually fix it.
The solution should be able to better scale the number of users, especially when you're using the cloud.
The solution should extend better into the Microsoft community and companies should be able to run it on Azure Cloud.
For how long have I used the solution?
I've been using the solution for five years.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
The solution is scalable. If you're running in a smaller environment it's fine. However, if you're using the freeware version, scalability is limited. We do have to have a number of entries to get the scale of it right. We have the freeware version and it's not scalable to what we ultimately want. We'll need to secure physical boxes and run everything in an Oracle environment to get to where we need to be.
We have around five to ten developers working on the solution. They have their own project environments. Mostly, it's just development engineers that have access to the solution. There's one to three development engineers that screen the machine and then it's handed over to the developers and the development team.
How are customer service and technical support?
We only use community support resources as we're using the freeware version of the solution. We've been satisfied with the level of support available to us through this means.
How was the initial setup?
The initial setup of the solution is straightforward. We are using the community version, and even with that, you need an expert in the Linux environment. You need to use Linux, so you need to have people well versed in Linux.
What about the implementation team?
Right now, we have freeware for HPE Eucalyptus' support. The actual support was expensive and not in our budget, so we deployed the solution ourselves and used the online community resources to assist us.
What's my experience with pricing, setup cost, and licensing?
The version of the solution we use is free. That means we don't pay for anything, including support. If you need help, there are online community resources you have access to that are free to use.
What other advice do I have?
Currently, we're using the latest version but we are now migrating to the VS platform, another application content manager.
We are in financial software development, and we do not scale very well. We have the setup we are running now on multi-level Supermicro connectivity servers. We are running on those boxes and we have a freeware storage box.
We do not use the solution extensively. We don't even use it for our primary storage; we have the fixed storage where the environment base is pretty static.
We had a plan in 2019 to move to Cloud in our production environment and right now we just want to move out in order to test our environment. That's what we are focused on right now.
I'd recommend others to (before the implementation goes ahead) do some POV's to see that the applications can be run. It's not likely to be easy. You are going to have to work with limited resources. You may have to assimilate storage.
If you want to run big applications, you have to be careful. If you are running with other applications (JAVA, PHP) while it's perfectly all right, it's important to test things with a POV first.
I'd rate the solution eight out of ten.
