VDS manager - whats the difference? - Page 2

slava · 06-10-2009, 08:51 PM

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

VN-Ken · 06-10-2009, 08:54 PM

Quote:

Originally Posted by slava

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.

nokoya · 06-11-2009, 05:24 AM

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

Rocket-Jay · 06-11-2009, 06:44 AM

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

slava · 06-11-2009, 08:55 AM

Quote:

Originally Posted by nokoya

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

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

slava · 06-11-2009, 08:58 AM

Quote:

Your control panel uses the IP address of the physical server where the vps is located

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

psybox · 06-11-2009, 10:11 AM

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?

Rocket-Jay · 06-11-2009, 05:12 PM

Quote:

Originally Posted by slava

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

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

xxx/ and it doesn't matter on which physical node the VPS is located - VPS owner always uses VPS IP to access the Power Panel.

psybox · 06-11-2009, 05:43 PM

Quote:

Originally Posted by slava

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

Code:

wget http://download.ispsystem.com/Linux-cc6/i686/VDSmanager-Linux/install.tgz

or

Code:

wget http://download.ispsystem.com/Linux-cc6/x86_64/VDSmanager-Linux/install.tgz

for 64bit operation system

2. Extract install.tgz to /usr/local/ispmgr/ folder

Code:

tar xzvf install.tgz -C /usr/local/ispmgr/

3. You need running Apache with SSL configured on the server node and add to apache config this line

Code:

Include /usr/local/ispmgr/etc/ispmgr.inc

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

Code:

cd /usr/local/ispmgr/lib/apache/
ln -s mod_ispmgr.2.2.0.so mod_ispmgr.so

5. Create VDSmanager-Linux config and edit this file

Code:

vim /usr/local/ispmgr/etc/vdsmgr.conf

You need add lines for example

Code:

Virtualization openvz
User admin $1$CP4kKfwb$Z5lge0MUKu1ba1d/OcbNs1

$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

Code:

LogLevel 9

to vdsmgr.conf (after then restart vdsmgr by killall vdsmgr command and see extended log in the /usr/local/ispmgr/var/vdsmgr.log file.

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

slava · 06-11-2009, 07:26 PM

Quote:

Originally Posted by Rocket-Jay

The VPS owner's control panel is accessible at https://vps-ip

xxx/ and it doesn't matter on which physical node the VPS is located - VPS owner always uses VPS IP to access the Power Panel.

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.