![]() That may only be an issue on the free version and not the pro version. It takes a lot of time and we cannot transfer the VMware from one machine or directly from one server to another. ![]() That is downloading the virtual machines and uploading the virtual machines. I want to be able to use OpenStack, however, I can't do that without vCenter, and it's so cost-prohibitive for us, it's become a problem. They should work to make the licensing more affordable. We just started the company, which makes it hard to explore the solution the way we want to with the amount of cost involved to do so. The solution is too expensive for us and we don't have any funds to direct towards it. They can produce something to improve that aspect slightly. You do get something called host profiles, which they've also improved slightly, however, I still think it's a bit clunky in terms of the way you can manage it. That's caused a number of issues already. That's one of the key things that I need really, from a support perspective. I would say for me personally, the management aspect with large memory and in-memory databases for the motions and stuff like that is what it needs. We are always sort of one or two versions behind. VMware doesn't really cater to it, however, Nutanix to some degree does cater for. That's a big pain point that the firmware management of the underlying hardware should handle. That said, one of the problems is that when we're sort of behind big memory servers and the databases in them if you migrate it, it potentially breaks the system off. They have embedded some of this in 7.1, however, I haven't tested it or seen it in action as yet. If you have to do firmware upgrades, it's organizing downtime and all sorts of things, which normally in a VMS space isn't an issue. It's an in-memory database and that can sometimes cause issues. The biggest thing is the firmware upgrades and other items at the backend. The biggest pain point is probably the firmware management of the underlying hardware. VMware should spend more time resolving the problems in the GUI. Some of the options do not appear well in the browser. They should also improve the vCenter GUI because it is currently not compatible, and there are a lot of problems. It would be good if VMware can offer specific applications for mobiles to enable us to control the management of all servers by mobile. In earlier versions, such as vSphere 6 or 6.5, we didn't have any such problems. We are facing issues with restarting the host. We updated our existing version to vSphere 7 in a private environment, but it seems that this version is not very stable. ESXi cannot detect different kinds of storage, and they should improve this. We face different problems when we install vSphere on an ESXi server and have different drivers on the storage. They can offer a special image to match different servers. I need to download different drivers and install them manually, which can be improved by VMware. For example, if I want to install vSphere on an HPE server, the driver is really different from a Dell server or a Fujitsu server. The biggest problem in this solution is the incompatibility of some of the features with some of the drivers installed on servers. With this, there are so many different pieces to connect. It's a product you deploy and you're good to go. There are competitors, Cloud Management Platform or Morpheus, for example. From a management center, particularly referring to the private cloud stack, I would prefer for it to be a lot more seamless. It gets a little tedious doing all those workflows at times. When you do the entire stack scenario unless you're doing something like VMware Cloud Foundation on VxRail, wherein it becomes a much more seamless solution where you are using discrete hardware, you're creating the entire cloud platform. vSphere is as stable as the word stable gets. There are times where you really begin to think, "I got this." Not, " it should be much easier than this." I can't think of anybody on the planet who would actually have issues with vSphere. ![]() By the time you're done, you begin to feel, "do you really need so many different pieces that you need to connect? Could it not just be a single, unified product?" I'm not saying the integration is difficult. When you deploy it as a complete stack, from vSphere to vCenter to the vRealize Operations, Orchestrator, all the way up, you're into your NSX login site, the entire cloud stack. I'm a big fan of vSphere I have used it since the days of 3.5, all the way up to now.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |