Quote:
Originally Posted by vadim s. sabinich
why? It different products. And customer may not used ISPmanager, but have access into VDSmanager for rebooting, reinstalling and viewing statistics for your VDS.
|
What a short-sided reply.
1) Because your competitors offer such a feature (i.e., Plesk integrates with Virtuozzo so that the user can restart their VPS/VDS from within Plesk). If you expect to compete in the marketplace, your products need equal or exceed those of your competitors. If you don't, your product loses.
2) Users don't like having to log into multiple "systems" to facilitate common functionality.
Given the fact you already have a "Reboot" feature in ISPmanager (a topic for which you failed to reply in my initial inquiry), you obviously felt the need that users would want to reboot their server (which is the case as I clearly outlined); however, that functionality only works if ISPmanager is installed on a dedicated server. If it is installed on a VDS, that link still appears, but it *doesn't work*. Your app doesn't recognize that it is installed on OpenVZ and all it can do is shutdown the VDS, not restart it. If it recognized it was on OpenVZ, you should have it communicate back with VDSmanager for that VDS and perform a true "reboot". If you can't do that right now, at least tell us how to remove the "Reboot" link in ISPmanager so customers won't complain.
We're making a decision on what we are going to replace our current Parallels infrastructure with at the end of this week. If all we keep getting are answers such as "why would we want to do that", then your products simply aren't going to meet our needs (and you might as well remove the entire content of your "About Us" page as you are *not* customer focused; you seem to want to develop a product how *you* see fit, not based on what your customers actually want/need, and your view of what is needed is very skewed from the rest of the marketplace).