You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 8
Next »
This file provides information on how to upgrade from VCL 2.1 to VCL 2.2. Please note it only applies for the upgrade from 2.1 to 2.2, this may or may not work for other versions.
- Download and Extract 2.2 code
- Shutdown httpd and vcld services
- Create backup of vcl database
- Update mysql schema
- Update Web code, create a backup, copy in new, make changes
- Update Management node vcl code, create a backup, copy in new, make changes
- Restart httpd and vcld services
Download and Extract 2.2 code
download to /root/vcl_2.2
Shutdown services
Shutdown the httpd and vcld services
service httpd stop or /etc/init.d/httpd stop
service vcld stop or /etc/init.d/vcld stop
Create a backup of vcl database
We will create a backup of the vcl database. This will provide a restore point if necessary.
Update mysql schema
This step updates the mysql schema.
cd to vcl2.2 source directory
cd /<path to vcl 2.2 source>
mysql vcl < mysql/update-2.2.sql
Update web code
This step we will move the 2.1 web directory out of the way, so we can copy in the new web code base. After copying in the new code, we will migrate any of your configuration changes, etc.
- cd <your vcl web root> i.e. cd /var/www/html
- copy your 2.1 config files
cp vcl_2.1_web/.ht-inc/conf.php vcl/.ht-inc/conf.php
....
Update management node code
This step will move the 2.1 vcl code base out of the way, so we can cleanly copy in the new management node(MN) code.
- Copy 2.1 code base to a backup location
cd <your vcl MN code root path>
ie. cd /usr/local/
mv vcl vcl_2.1_management_node
- Copy 2.2 code base to /usr/local
cp -r /root/vcl_2.2 /usr/local/vcl
- Make changes related to vcld.conf settings
Open VCL web interface (assumes httpd has been restarted)
Go to Management Nodes
Select Edit Management Node Information
Select Edit.
Set any relevant fields:
SysAdmin Email Address(es) - comma delimited list of vcl admin email addresses
Address for Shadow Emails - a shared mail box, optional it receives email of all notifications
Public NIC configuration method - Defines what type of NIC configuration is used, options are dynamic DHCP, Manual DHCP, or static
End Node SSH Identity Key Files