VDS manager - whats the difference?
 

Hi

Whats the difference between the three versions?

- vds manager
- vds manager SMP
- vds manager linux

We run quad core servers (linux) and I'm confused as to how the licensing costs differ.

thanks

VDSmanager and VDSmanager-SMP are for FreeBSD 6.3 i386 system only. SMP - for Symmetric Multiprocessing hardware. (Core Duo, Core Quard proccessors for example). It uses our own virtualization technology and own system kernel modified by ISPsystem.

VDSmanager Linux is a graphical interface for popular virtualization technology, such as OpenVZ, VServer and Xen.
We recommend you to use OpenVZ.

For VDSmanager-Linux you need server with minimal installation CentOS Linux 5.3 (base system and yum packet manager) and after run install.sh script choose OpenVZ.
Disk partition table before installation you need create as / - 4-8Gb and /vz - other system for VPS files and disk template or one (/ partition).

After installation you can manage VPS servers via graphical web-interface and install other Linux guest operation systems from templates (CentOS, Debian, Gentoo, etc ...) into VPS.

thanks - currently we use hypervm for this. Can I acheive the following?

- install vdsmanager-linux in a VPS (so we and clients can access it at http://xyz.com)
- transfer current hypervm VPS into the vdsmanager linux? (allopenvz but running as hypervm slaves)

For VDSmanager Linux you need dedicated server with clear installation CentOS Linux.
See my last message.
For transfer data from old server you need create VPSes in the new system and move data.
Users can login to https://main-node/manager/vdsmgr with login as primary ip-address and root user password for manage own servers (such as reboot or reinstall).
For own system users can login by ssh or other tools.

More information about the migration from HyperVM to VDSmanager-Linux. You can install VDSmanager-Linux manually for work with OpenVZ VPSes which have been already created.

It have six simple steps for OpenVZ system and running VPSes:

1. Download VDSmanager-Linux for your operation system architecture
or
for 64bit operation system

2. Extract install.tgz to /usr/local/ispmgr/ folder
3. You need running Apache with SSL configured on the server node and add to apache config this line
Note: If you have no running apache with SSL (https://your-server-ipaddress/ must work) you need install and configure it.

4. In the /usr/local/lib/apache/ folder you need create symbol link to module for your apache version, for example you have apache 2.2 running in this node

5. Create VDSmanager-Linux config and edit this file

You need add lines for example

$1$CP4kKfwb$Z5lge0MUKu1ba1d/OcbNs1 - this is blowfish crypted password 'admin'

6. After then restart apache and try to access VDSmanager by opening following URL in your web-browser:

https://server-ip/manager/vdsmgr

When you open this URL proccess vdsmgr will run through apache

VDSmanager Linux must get information about VE and show this in own interface, we have not tested this, but everything should work correctly, let me know what the result.

Also you can add first line to vdsmgr.conf (after then restart vdsmgr by killall vdsmgr command and see extended log in the /usr/local/ispmgr/var/vdsmgr.log file.

Is Xen fully supported? I know that you recommend OpenVZ, and I believe that some time ago you said that Xen has problems. Is it supported now?

I just want to confirm - so even if a system has dual or quad core processors, but is on openvz, we would still use VDSmanager-Linux - correct?

Xen support is currently being developed, we do not recommend you to use it, it will have full support during 1-2 months.

Yes, correct, VDSmanager-Linux is only web-interface control panel, it uses OpenVZ system installation from system repository, best way for installation VDSmanager-Linux - Linux CentOS 5.3 (minimal+yum packet manager) and choose OpenVZ virtualization type when you run our install.sh script.

Thank you. I saw a previous post saying that your software can be installed on an existing node. I will take that route. It seems to have been used by other companies and they have had success with it.

Our nodes have CentOS 5, 5.1-2 and maybe one node with 5.3. Would this have a large impact on anything?

You can use any CentOS 5, but if it possible we recommend software update, because new OpenVZ kernels much better.

Ok, thank you so much for your replies. I hope that your company prospers during these troubled times for HyperVM victims.

is it possible to create linux vps inside freebsd node or freebsd vps inside linux node ?

Been digging around as we're testing for a new project. Your control panel uses the IP address of the physical server where the vps is located. For our use this presents a problem. Any plans to change this so it uses the IP assigned to it from within the physical server? Binding the control panel to the IP of the physical server simply won't work for us. You would get nice business if you change this.. Let me know.

Thanks,
Jay

If you use XEN virtualization it will be possible to run other systems inside Linux node.

This quetion about license policy? You can change license IP
once a month over our billing system without any problem if you need it.

ok - I have this installed on one of our openvz servers. I can access the panel fine. How do I go about "showing" the vps that exist on that server?

The question wasn't about licensing but about the URL used by the VPS user to login to the control panel. User's control panel can be accessed at https://node-ip/manager/vdsmgr which could work fine as long as VPS remains on the one node all the time however in real world VPSs are being migrated between nodes to balance the load, resource consumption, etc. So, if say, VPS will be moved to node1 to node2 this would change the URL used by the VPS owner to access the control panel. Is there any way to avoid this? I.e.
The VPS owner's control panel is accessible at https://vps-ip:xxxx/ and it doesn't matter on which physical node the VPS is located - VPS owner always uses VPS IP to access the Power Panel.

tried this - its running, but shows no vm's ...

License to VDSmanager purchased for the main IP-address of the server node where VDSmanager installed.

Virtual servers have own IP-addresses and does not affect to the VDSmanager license.

Users can use own control panels installed to VPSes (such as ISPmanager or other different software for manage own websites) and login to as https://vps-ip/manager/ispmgr

If user need manage VPS system such as reboot or reinstall - user can login to node by URL https://node-ip/manager/vdsmgr with login as ip-address and root password for this VPS. VDSmanager authorize this login with user rights.

Can you see any errors in the /usr/local/ispmgr/var/vdsmgr.log when you open VDSmanager URL?

Please run command killall vdsmgr and open https://node-ip/manager/vdsmgr and check logfile.

What operation system version and virtualzation you have on this server?

So there is no way a VPS customer can reboot his VPS via his own IP as I asked (listed below from previous post)? This is a big deal for us.

"The VPS owner's control panel is accessible at https://vps-ip:xxxx/ and it doesn't matter on which physical node the VPS is located - VPS owner always uses VPS IP to access the Power Panel."

Virtual servers are completely independent from the node machine and for connect to VPS users use own IP-address.

I understand how VPS's work as we are a large VPS company. My question still hasn't been answered. The GUI tool that each VPS user would get with their VPS to reboot, restart their VPS requires the host node IP's to access it with your software it seems. Is there anyway they can access this GUI tool (not control panel like cPanel) rather VZPP (like Virtuozzo Powerpanel) via their VPS IP not the host node itself? As explained above this is important and if it's not possible please just say it's not possible. The reason this is a problem is simple. If we move a VPS from one server to another then we also need to tell them a new IP to reboot their VPS which is really not necessary and not needed with other Virtualization software. Let me know asap.

slava,

Can you please reply to my PM?

Thanks.

Current version IPmanager work only with DNS zone configuration files and must be installed into server where DNS server allocated. If IP address have no revers record or name like 'free' (it can be changed) - addres is free and can be allocated to new VPS. Also administrator can configure address blocks for different reasons (projects or primary/secondary ip). If our developer team will add additional checks for find free IPaddress it will we written in changelog http://ispsystem.com/software/ipmanager/changelog/

So IPmanager allocates to VPS's based on if an IP has a reverse DNS entry, is that what you're saying? Igor had said that you'll be releasing in 1-2 days (said that two days ago) with the ability to ping the IP address to see if it is available. Can you check and see the status of this release?

is it possible to get someone to log in to our box and see why the openvz are not showing?

sample output

Jun 12 21:39:17 ../../src/tdata.cpp:1322 TRACE RecordSet::Post(insert) rsname='d
isktemplate' key='fedora-9-i386-default'
Jun 12 21:39:17 ../../src/tdata.cpp:1322 TRACE RecordSet::Post(insert) rsname='d
isktemplate' key='gentoo-20060317-i686-stage3'
Jun 12 21:39:17 ../../src/tdata.cpp:1322 TRACE RecordSet::Post(insert) rsname='d
isktemplate' key='centos-5-i386-hostinabox571'
Jun 12 21:39:17 ../../src/openvz.cpp:106 TRACE BuildVdsCache
Jun 12 21:39:17 EXTINFO Load config '/etc/vz/conf/1670.conf'
Jun 12 21:39:17 ../../src/tdata.cpp:1322 TRACE RecordSet::Post(insert) rsname='v
ds' key='ip'
Jun 12 21:39:17 EXTINFO Load config '/etc/vz/conf/1160.conf'
Jun 12 21:39:17 ../../src/tdata.cpp:1322 TRACE RecordSet::Post(insert) rsname='v
ds' key='ip'
Jun 12 21:39:17 EXTINFO Load config '/etc/vz/conf/1570.conf'
Jun 12 21:39:17 ../../src/tdata.cpp:1322 TRACE RecordSet::Post(insert) rsname='v
ds' key='ip'
Jun 12 21:39:17 EXTINFO Load config '/etc/vz/conf/230.conf'
Jun 12 21:39:17 ../../src/tdata.cpp:1322 TRACE RecordSet::Post(insert) rsname='v
ds' key='ip'
Jun 12 21:39:17 EXTINFO Load config '/etc/vz/conf/1370.conf'
Jun 12 21:39:17 ../../src/tdata.cpp:1322 TRACE RecordSet::Post(insert) rsname='v
ds' key='ip'

haha! modified each individual conf with a wrtie command even if no changes made and they now show!

Just reposting hoping for a reply? Please confirm.


Quote:
Originally Posted by slava View Post
Virtual servers are completely independent from the node machine and for connect to VPS users use own IP-address.


I understand how VPS's work as we are a large VPS company. My question still hasn't been answered. The GUI tool that each VPS user would get with their VPS to reboot, restart their VPS requires the host node IP's to access it with your software it seems. Is there anyway they can access this GUI tool (not control panel like cPanel) rather VZPP (like Virtuozzo Powerpanel) via their VPS IP not the host node itself? As explained above this is important and if it's not possible please just say it's not possible. The reason this is a problem is simple. If we move a VPS from one server to another then we also need to tell them a new IP to reboot their VPS which is really not necessary and not needed with other Virtualization software. Let me know asap.

See more information about how to migrate from HyperVM here http://forum.ispsystem.com/en/showthread.php?t=634

Yes, VPS is completely independent from node and users can use any control panel installed in the own server and own IP and any software for remote management.

User can (but is not need for this) login to node with user password (login as IP-address and password - root password for this VPS) for reboot VPS if own software have errors (VPS hangs for example) or for reinstallation VPS by himself. But user no need know it, it is optional service.

So if we have a VPS customer with the unique IP address of 65.222.xxx.xxx and he needs to reboot his VPS because it's not working. The physical server his VPS is hosted on has the IP 65.111.xxx.xxx. What IP would he use to reboot his VPS?

65.222.xxx.xxx and if he can't login to VPS software (VPS hangs), user can login to main node to VDSmanager in IP address 65.111.xxx.xxx.

That is the problem. Is there anyway they can reboot the VPS differently thru a port or something such as 65.222.xxx.xxx:4643 to reboot the VPS? The IP being different then the VPS's IP creates an issue for us which makes your product unusable for us. Please let me know. We'd need this feature to use your product.

VDSmanager have no this feature. You can put links to management panels (VDSmanager) to your billing system/customer zone.

For example, our product BILLmanager have button in the customer zone "Server information (control panel links)" where user can go to VDSmanager by link for example https://node-address/manager/vdsmgr?...132.132.12.112 and ISPmanager by link https://132.132.12.112/manager/ispmgr

Server node information in billing always is actual, because billing system use node for start/stop VPSes / change tarif plans / get information (traffic).

VDSmanager for Linux

VDSmanager for Linux is a web-based control interface designed to support such free popular server virtualization technologies like OpenVZ, Xen, and Vserver. It contains:

I have read just recently that you do not support Xen, but you publicize you do.

so what's the word ?

Any plans to create a WHMCS module for VDSManager ?

Xen in the testing and bugfix stage now, because current version have no good work with Xen (many bugs). Xen will be fully supported soon.