Switching software products to package-based installation
This articles describes a new installation method (via OS package manager) that is now used instead of the old one (via COREmanager).
Only CentOS-6 and Debian-7 COREmanager 5.21 are currently supported.
First you need to update your product to the latest version available (note the release version - beta or stable).
Run the command
/usr/local/mgr5/sbin/mgrctl -m ispmgr software
Make sure correct version is specified for all the products (e.g. version=nginx-full-1.2.1-2.2+wheezy3) and their status is state=configured
Download the script convert.py
Make sure Python is installed on the server to run the script. Otherwise execute the following commands to install it:
yum install python
apt-get update && apt-get install python
chmod +x convert.py && ./convert.py
This script only displays the logs. If you want to keep them:
python convert.py 2>&1| tee -a convert.log
If you want to update to a certain version (rather than to the last one), run the installation script with the --release parameter, e.g.:
python convert.py --release 5.60
where 5.60 is a desired version.
The script completes the following steps:
- Connects the repository, if needed
- Locates the list of products installed. 
- Locates the list of packages to be installed. 
- Creates a backup copy of the /usr/local/mgr5 directory into the /root/isp_backup.tgz file
- Installs the ISPCONVERT=yes environment variable.
- Runs the installation process 
- Performs a number of specific operations once the installation is complete. 
If a package version does not support something (e.g. NSD), the corresponding package won't be installed, however the software product will continue running as its settings are not affected.
The password to afterlogic will be changed upon conversion. You can view it in the /usr/local/mgr5/www/webmail-afterlogic/webmail/data/settings/settings.xml file.
A list of packages to be installed is defined by the software in the "Software" module. Make sure the software is configured correctly.
Conversion will be perfromed only on the master node. Once the package is installed, the afterupdate ispconvert=yes function is called to start the conversion process on the nodes. In the "Notificications" module you can keep track of errors that might occur.
manager vemini in the /usr/local/mgr5/etc/mgrlist.conf file indicates that the master node is used as the processing node. If not, the vmmanager-ovz-vemini package won't be installed.
The vmmanager-kvm-vmnode is always installed on the master node. It does not require any dependenices, and the master node should not be the processing node.
- Only if the /usr/local/mgr5/tmp/.mgr_list file is not present. Otherwise, the list of packages will be taken from this file (in pickle format ). Once getting the list, the script will create that file.
- Only if the /usr/local/mgr5/tmp/.pkg_list file is not present. Otherwise, the list of packages will be taken from this file (in pickle format ). Once getting the list, the script will create that file.
- Only if the /usr/local/mgr5/tmp/.pkg_installed file is not present. Otherwise, this step will be skipped. Once the installation is complete, the file will be created.
- Only if the /usr/local/mgr5/tmp/.post_run_ok file is not present. Otherwise, this step will be skipped. Once the installation is complete, the file will be created.
We can not identify you and respond to your message.