What is our primary use case?
VMWare Tanzu CloudHealth is used primarily to provide users with a seamless working environment without losing connectivity by offering a solution that virtualizes their computing environment. It is used for cloud and virtualization computing, allowing multiple virtual machines based on different servers, with each acting as an independent machine with its own operating system. It consolidates hardware and helps in reducing IT costs.
Most people are going for a SaaS solution with VMWare Tanzu CloudHealth, but in some cases, such as one petroleum institution, they had regulatory binding that prevented them from deploying their data on SaaS, so they created the entire setup on-premises. It depends on the client itself and the requirement. If it is a banking institution, most of them are now on SaaS and don't have a problem. Very few insist on keeping it on-premises because data is normally secure whether it is hosted here or there.
What is most valuable?
Customers do utilize a security and compliance framework with VMWare Tanzu CloudHealth because larger institutions won't move forward without it. They choose VMware to ensure a tested and foolproof secure environment. They comply with regulatory standards that go along with it, such as VMware Cloud Foundation, which is a significant product with trust policies and all, making it quite good.
The CloudHealth Unified Dashboard helps streamline cloud management practices by allowing the IT team to manage the environment effectively. It shows if updates are done, whether there is downtime, or if there is a delay, indicating the reason for it. Dashboards are essential; without them, you are sitting in a mirage, not knowing what is happening. With the dashboard, you can quickly identify issues, such as red points and different types of curves indicating problems. This allows us to act on the problem at the very initial stage rather than waiting for the entire system to stop.
What needs improvement?
The weak points of VMWare Tanzu CloudHealth are that while the product is quite capable, cost can be an issue at times. The learning curve is steep because people like to take their own time to understand and roll out things, which creates an overhead in getting people to understand the system. There are also bottlenecks within operations where we face challenges that can lead to delays in implementation.
For how long have I used the solution?
I have been familiar with VMWare Tanzu CloudHealth for almost two years, while there were people who have been using it for definitely six, seven years or more.
How are customer service and support?
Technical support from VMware, or better to say Broadcom, is usually quick and prompt. I don't encounter significant issues since they provide 24/7 support based on the SLA with the client, ensuring the response times are matched accordingly. If the agreement is for four hours, eight hours, or the next business day, responses usually come. We don't typically face situations where institutions are halted from working. Broadcom often comes up with quick rollbacks or informs us if something requires a patch or updates, and usually problems won't happen until instigated by local issues. If local engineers cannot solve the problem, they log a case for assistance from Broadcom or Omnica.
What about the implementation team?
From my side, we needed only a team of three people to deploy VMWare Tanzu CloudHealth in such a large banking environment facing around 100 different departments. The rollout was similar; they had different clusters in the bank, and within those clusters, there were different branches and different zones. We started doing one by one, and we completed all of them. The first one was difficult, and then we began training the users with a train the trainer type of concept. We trained the key members of the team to help us out. There was a project management team from our side and a project management team on the other side working together. We had a steering committee and standard meetings, so it went fine.
What other advice do I have?
This project initially started with a 16-week timeframe, but it ended up taking nine months to complete. The initial four months were dedicated to discussions and getting approval. We had only planned 15 days for UAT, but it took two months to complete. There was significant delay in that one. They wanted to close the project and quickly roll it out, so we had an urgency to finish things faster. Now that the solution is live, they have customized reports, dashboards, and other things, matching the regulatory bank's reporting requirements. We are trying to align the system's attributes with the required reports from the State Bank. It was time-consuming, but eventually, we were successful in completing the project with a certain delay.
There are different departments that get involved in the requirements for VMWare Tanzu CloudHealth, and as we go for the implementation, we have to seek permissions from them. We have to get some ports opened up for accessibility. However, SaaS is an elegant solution because it is available and always updated. On-premises requires newer updates to be installed manually. SaaS is always a better solution; newer versions or new insights or new features come in automatically. You don't have to wait for a newer version for getting the new things. Most institutions are now going for SaaS, and it is faster and less difficult to implement. You just roll it out and do configurations, and that's it. Very few customizations are done on SaaS. If you go on-premises and people are old school, they will go for a lot of customization, new screens, additional forms, and additional reports. That will clutter a lot of things, and getting newer upgrades becomes a problem since it won't work until you port everything to the new version. Things get delayed, so SaaS is much easier. The rollout is easier if you have a large institution base; for example, we were doing an implementation of an ITSM software for a bank with 33,000 users. We went with SaaS and it went perfectly.
Policy-driven management is part of the implementation of VMWare Tanzu CloudHealth. The audit and security team will not let you move forward until it conforms to both their requirements and compliance.
I measure the effectiveness of VMWare Tanzu CloudHealth resource optimization using various metrics, including the framework where the entire VMware Cloud Foundation and VMware vSphere Foundation are working. Both platforms have interoperability metrics which conform to the standard requirements and suggested guidelines from VMware and Broadcom, and we follow the same.
I have given this review a rating of 9 out of 10.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other