Author: jfthomps
Date: Tue Mar 19 16:24:40 2013
New Revision: 1458384
URL: http://svn.apache.org/r1458384
Log:
updated for 2.2.2
Modified:
vcl/branches/vcl-2.2-bugfixes/CHANGELOG
vcl/branches/vcl-2.2-bugfixes/INSTALLATION
vcl/branches/vcl-2.2-bugfixes/NOTICE
vcl/branches/vcl-2.2-bugfixes/RELEASE_NOTES
vcl/branches/vcl-2.2-bugfixes/UPGRADE
Modified: vcl/branches/vcl-2.2-bugfixes/CHANGELOG
URL:
http://svn.apache.org/viewvc/vcl/branches/vcl-2.2-bugfixes/CHANGELOG?rev=1458384&r1=1458383&r2=1458384&view=diff
==============================================================================
--- vcl/branches/vcl-2.2-bugfixes/CHANGELOG (original)
+++ vcl/branches/vcl-2.2-bugfixes/CHANGELOG Tue Mar 19 16:24:40 2013
@@ -1,4 +1,43 @@
-ASF VCL 2.2
+ASF VCL 2.2.2
+
+Dependency changes:
+
+No dependency changes for any components in this release.
+
+Release Notes - VCL - Version 2.2.2
+
+** Bug
+ * [VCL-328] - shibboleth sp logout URL not using SSL
+ * [VCL-342] - problem selecting image revision id when making a cluster
reservation with identical subimages
+ * [VCL-348] - Setting privileges in web gui -- Slightly broken
+ * [VCL-400] - virtual hosts page shows all unassigned vms instead of
checking which ones the user can access
+ * [VCL-433] - new revisions can be captured of kickstart images
+ * [VCL-447] - Notice: Uninitialized string offset: 0 in
.../vcl/.ht-inc/utils.php on line 3206
+ * [VCL-456] - groupwasnone variable is not properly initialized
+ * [VCL-458] - $virtual undefined in utils.php line 3678
+ * [VCL-467] - Members of a group from one affiliation have access to
groups with the same name from other affiliations
+ * [VCL-473] - query in findManagementNode in utils.php doesn't have
conditional to join tables
+ * [VCL-475] - addShibUser in shibauth.php returns an array when it should
be returning a user id
+ * [VCL-476] - manage block allocation page may show incorrect next start
time
+ * [VCL-480] - XMLRPCproccessBlockTime can throw an error about VMhostCheck
table already existing
+ * [VCL-482] - scheduler does not order VMs properly when no VMs are
preloaded with the selected image
+ * [VCL-486] - Measures against cross site scripting on the Login form
+ * [VCL-487] - Problem in screen transition after successful login
authentication
+ * [VCL-492] - edit computer info for VM in maintenance state
+ * [VCL-494] - Typo in testsetup.php
+ * [VCL-507] - Deleted VMs appear in the list of unassigned VMs
+ * [VCL-509] - error when adding computer with no groups selected
+ * [VCL-510] - insert correct architecture in image table when adding new
entry
+ * [VCL-533] - error when trying to download dhcp data when private IP
address was not entered
+ * [VCL-547] - removing site maintenance entry from .ht-inc/maintenance
directory doesn't fully remove site from maintenance
+ * [VCL-549] - AJAX error when creating a new schedule
+ * [VCL-556] - edit schedule groups code not doing permissions correctly
+ * [VCL-674] - problem adding a user group to the privilege with cascade
checked
+ * [VCL-675] - deleting a hierarchy of 3 or more privilege nodes throws an
error
+
+================================================================================
+
+ASF VCL 2.2.1
Dependency changes:
Modified: vcl/branches/vcl-2.2-bugfixes/INSTALLATION
URL:
http://svn.apache.org/viewvc/vcl/branches/vcl-2.2-bugfixes/INSTALLATION?rev=1458384&r1=1458383&r2=1458384&view=diff
==============================================================================
--- vcl/branches/vcl-2.2-bugfixes/INSTALLATION (original)
+++ vcl/branches/vcl-2.2-bugfixes/INSTALLATION Tue Mar 19 16:24:40 2013
@@ -1,4 +1,4 @@
-Installing VCL 2.2.1
+Installing VCL 2.2.2
Install & Configure:
I. Database
@@ -13,11 +13,11 @@ I. Install & Configure the Database
a. If you have not already done so, download and the Apache VCL source to
the database server:
- wget
http://www.apache.org/dist/incubator/vcl/apache-VCL-2.2.1-incubating.tar.bz2
+ wget --trust-server-names
http://vcl.apache.org/downloads/download.cgi?action=download&filename=%2Fvcl%2Fapache-VCL-2.2.2.tar.bz2
b. Extract the files:
- tar -jxvf apache-VCL-2.2.1-incubating.tar.bz2
+ tar -jxvf apache-VCL-2.2.2.tar.bz2
2. Install MySQL Server
a. Install MySQL Server 5.x:
@@ -32,12 +32,24 @@ I. Install & Configure the Database
/sbin/service mysqld start
- d. Make sure the firewall on the database server is configured to allow
- traffic from the web server and management node servers to connect to
- the MySQL daemon TCP port: 3306. See the firewall documentation for
- more information.
+ d. If the iptables firewall is being used and the web server and
+ management nodes will be on different machines, port 3306 should be
+ opend up
- man iptables
+ Note the following rules are for Red Hat based distros.
+
+ vi /etc/sysconfig/iptables
+
+ Insert the following under the RH-Firewall-1-INPUT chain, changing
+ <web server IP> and <management node IP> to match your configuration.
+
+ -A RH-Firewall-1-INPUT -m state --state NEW -s <web server IP> -p tcp
--dport 3306 -j ACCEPT
+ -A RH-Firewall-1-INPUT -m state --state NEW -s <management node IP>
-p tcp --dport 3306 -j ACCEPT
+ service iptables restart
+
+ For more info on iptables:
+
+ man iptables
3. Create the VCL Database
a. Run the MySQL command-line client:
@@ -51,12 +63,11 @@ I. Install & Configure the Database
c. Create a user with SELECT, INSERT, UPDATE, DELETE, and
CREATE TEMPORARY TABLES privileges on the database you just created:
- GRANT SELECT,INSERT,UPDATE,DELETE,CREATE TEMPORARY TABLES ON vcl.* \
- TO 'vcluser'@'localhost' IDENTIFIED BY 'vcluserpassword';
+ Replace vcluser and vcluserpassword in the SQL statement with that of
+ the user you want to use to connect to the database. The GRANT command
+ will automatically create the user if it doesn't already exist.
- NOTE: Replace vcluser and vcluserpassword with that of the user you
- want to use to connect to the database. The GRANT command will
- automatically create the user if it doesn't already exist.
+ GRANT SELECT,INSERT,UPDATE,DELETE,CREATE TEMPORARY TABLES ON vcl.* TO
'vcluser'@'localhost' IDENTIFIED BY 'vcluserpassword';
d. Exit the MySQL command-line client:
@@ -64,20 +75,11 @@ I. Install & Configure the Database
e. Import the vcl.sql file into the database:
- mysql vcl < apache-VCL-2.2.1-incubating/mysql/vcl.sql
+ mysql vcl < apache-VCL-2.2.2/mysql/vcl.sql
The vcl.sql file is included in the mysql directory within the Apache
VCL source code
- 4. Install & Configure phpMyAdmin (Optional):
- phpMyAdmin is a free and optional tool which allows MySQL to be
- administered using a web browser. It makes administering the VCL
database
- easier. This tool can be installed on the VCL web server. To install
- phpMyAdmin, follow the instructions on:
-
- VCL 2.2.1 phpMyAdmin Installation & Configuration
-
http://cwiki.apache.org/VCL/vcl-221-phpmyadmin-installation-configuration.html
-
--------------------------------------------------------------------------------
II. Install & Configure the Web Components
@@ -85,7 +87,7 @@ II. Install & Configure the Web Componen
Prerequisites:
The following instructions assume these tasks have previously been
completed:
- * Apache VCL 2.2.1 has been downloaded
+ * Apache VCL 2.2.2 has been downloaded
* VCL database has been installed and configured
Web Server:
@@ -94,10 +96,10 @@ II. Install & Configure the Web Componen
The VCL web frontend may run under other web server platforms capable of
running PHP code, but has only been tested to work with Apache HTTP
Server
- Required Linux Packages:
+ Required Linux Packages(See II.1 section below on installing)
* libmcrypt - Encryption algorithms library
- Required PHP Modules:
+ Required PHP Modules(See II.1 section below on installing):
(Some of these may already be included with your PHP distribution)
* php-gd
* php-json (required if your PHP version is 5.2 or later)
@@ -108,21 +110,24 @@ II. Install & Configure the Web Componen
* php-xml
* php-xmlrpc
* php-ldap (if you will be using LDAP authentication)
+ * php-process (for RHEL/CentOS 6)
1. Install the Required Linux Packages & PHP Modules
a. If your web server is running a Red Hat-based OS, the required
components can be installed with:
- yum install httpd mod_ssl php-gd php-mcrypt php-mysql php-xml \
- php-xmlrpc php-ldap -y
+ For RHEL / CentOS 5
+
+ yum install httpd mod_ssl php php-gd php-mcrypt php-mysql php-xml
php-xmlrpc php-ldap -y
+
+ For RHEL / CentOS 6
- * If you will be using a self-signed certificate for SSL, this is a
- great HOWTO explaining how to set it up on CentOS:
+ yum install httpd mod_ssl php php-gd php-mcrypt php-mysql php-xml
php-xmlrpc php-ldap php-process -y
- http://wiki.centos.org/HowTos/Https
+ Note: You may need the optional server rpm repository for the
+ php-process package; to add this run the following command:
- * It is useful to configure the server to be able to send debugging
- emails
+ rhn-channel --add --channel=rhel-x86_64-server-optional-6
b. Configure the web server daemon (httpd) to start automatically:
@@ -137,11 +142,21 @@ II. Install & Configure the Web Componen
/usr/sbin/setsebool -P httpd_can_network_connect=1
+ e. If the iptables firewall is being used, port 80 and 443 should be
+ opened up:
+
+ vi /etc/sysconfig/iptables
+
+ Insert the following lines.
+ -A RH-Firewall-1-INPUT -m state --state NEW -p tcp --dport 80 -j
ACCEPT
+ -A RH-Firewall-1-INPUT -m state --state NEW -p tcp --dport 443 -j
ACCEPT
+ service iptables restart
+
2. Install the VCL Frontend Web Code
a. Copy the web directory to a location under the web root of your web
server and navigate to the destination .ht-inc subdirectory:
- cp -r apache-VCL-2.2.1-incubating/web/ /var/www/html/vcl
+ cp -r apache-VCL-2.2.2/web/ /var/www/html/vcl
cd /var/www/html/vcl/.ht-inc
b. Copy secrets-default.php to secrets.php:
@@ -200,6 +215,7 @@ II. Install & Configure the Web Componen
* Enter the current password: adminVc1passw0rd
* Enter a new password
* Click Submit Changes
+
4. Add a Management Node to the Database
a. Click the Management Nodes link
* Enter the hostname and IP address of your management node
@@ -230,6 +246,15 @@ II. Install & Configure the Web Componen
* Select the checkbox for your management node
* Click Submit
+ 5. Install & Configure phpMyAdmin (Optional):
+ phpMyAdmin is a free and optional tool which allows MySQL to be
+ administered using a web browser. It makes administering the VCL
database
+ easier. This tool can be installed on the VCL web server. To install
+ phpMyAdmin, follow the instructions on:
+
+ phpMyAdmin Installation & Configuration
+ http://vcl.apache.org/docs/installphpmyadmin.html
+
Further steps if using only VMWare
If you are using standalone VMware servers (i.e. ones that VCL did not
@@ -308,7 +333,7 @@ II. Install & Configure the Web Componen
modify the VM Host Profile later if needed. See following page
for more information about VM Host Profiles:
- http://cwiki.apache.org/VCL/vmware-configuration.html
+ http://vcl.apache.org/docs/vmwareconfiguration
8. Click Add Computers
@@ -423,24 +448,6 @@ II. Install & Configure the Web Componen
node has started checking in, you should be able to make a
reservation
- Adding Local VCL Accounts
-
- Local VCL accounts are contained within the VCL database. The admin
- account is a local VCL account. Additional local accounts can be
added
- via the backend management node code. After you have finished the
- backend management node installation, run:
-
- vcld -setup
-
- 1. Select VCL Base Module
- 2. Select Add Local VCL User Account
- 3. Enter the requested information
-
- Adding LDAP Authentication
-
- The last section of this installation guide (IV. Adding LDAP
- authentication) explains how to set up LDAP authentication.
-
--------------------------------------------------------------------------------
III. Install & Configure the Management Node Components
@@ -449,8 +456,8 @@ III. Install & Configure the Management
The following management node installation instructions assume the
instructions on the following pages have previously been completed:
- * VCL 2.2.1 Database Installation
- * VCL 2.2.1 Web Code Installation
+ * VCL 2.2.2 Database Installation
+ * VCL 2.2.2 Web Code Installation
Supported Operating Systems:
@@ -501,7 +508,7 @@ III. Install & Configure the Management
Copy the managementnode directory to the location where you want it to
reside (typically /usr/local):
- cp -r apache-VCL-2.2.1-incubating/managementnode /usr/local/vcl
+ cp -r apache-VCL-2.2.2/managementnode /usr/local/vcl
2. Install the Required Linux Packages & Perl Modules
Run the install_perl_libs.pl script:
@@ -754,8 +761,27 @@ III. Install & Configure the Management
--------------------------------------------------------------------------------
-IV. Adding LDAP authentication
-
+IV. Configure Frontend Authentication
+
+
+
+ Adding Local VCL Accounts
+
+ Local VCL accounts are contained within the VCL database. The admin
+ account is a local VCL account. Additional local accounts can be added
+ via the backend management node code. After you have finished the
+ backend management node installation, run:
+
+ vcld -setup
+
+ 1. Select VCL Base Module
+ 2. Select Add Local VCL User Account
+ 3. Enter the requested information
+
+
+
+ Adding LDAP Authentication
+
1. Prerequisites for your LDAP server:
* enable SSL on your LDAP server
Modified: vcl/branches/vcl-2.2-bugfixes/NOTICE
URL:
http://svn.apache.org/viewvc/vcl/branches/vcl-2.2-bugfixes/NOTICE?rev=1458384&r1=1458383&r2=1458384&view=diff
==============================================================================
--- vcl/branches/vcl-2.2-bugfixes/NOTICE (original)
+++ vcl/branches/vcl-2.2-bugfixes/NOTICE Tue Mar 19 16:24:40 2013
@@ -1,5 +1,5 @@
Apache VCL
-Copyright 2009-2011 The Apache Software Foundation
+Copyright 2009-2013 The Apache Software Foundation
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
Modified: vcl/branches/vcl-2.2-bugfixes/RELEASE_NOTES
URL:
http://svn.apache.org/viewvc/vcl/branches/vcl-2.2-bugfixes/RELEASE_NOTES?rev=1458384&r1=1458383&r2=1458384&view=diff
==============================================================================
--- vcl/branches/vcl-2.2-bugfixes/RELEASE_NOTES (original)
+++ vcl/branches/vcl-2.2-bugfixes/RELEASE_NOTES Tue Mar 19 16:24:40 2013
@@ -1,4 +1,4 @@
-VCL 2.2
+VCL 2.2.2
I. Intro and Description
@@ -21,23 +21,32 @@ servers in a server farm or HPC cluster.
II. VCL Roadmap
-VCL 2.2.1 (this release)
- * removed frontend dependency on jpgraph
- * remove any access control that is hard coded in frontend
- * added support for VirtualBox hypervisor
- * many bug fixes and improvements to VMWare support
-
-VCL 2.3
- * Service deployments
- * power management
- * improve cluster reservations
+VCL 2.2.2 (this release)
+ * Bug fixes
+
+VCL 2.3.2 (latest 2.3 series release)
+ * Bug fixes
VCL 2.4
- * additional and improved hypervisor support
- * KVM and possibly others (virtual box and XEN)
- * Allow for additional access methods for environments (port, other
protocols, etc)
+ * Configuration management system
+ * Scripted installation
+ * VCL Broker
VCL 2.5
+ * Improve additional connect methods
+ * NAT support
+ * Remove requirement for 2 NICs
+ * Support for Spice remote display protocol
+ * Support for ESX OS for end users
+ * Initial support for EC2 API and OpenStack
+
+VCL 2.6
+ * Power management
+ * Improve cluster reservations
+ * Service deployment configuration management
+ * Initial support for Libcloud
+
+VCL 2.7
* develop tools for managing both system and user storage
With each release, we'll be working toward making VCL easier to install. As
@@ -51,24 +60,26 @@ III. Getting Involved in the ASF VCL Com
There are five ways to become involved in the ASF VCL community.
* Join the mailing lists and participate in discussion
- There are two mailing lists: [email protected] and
- [email protected]. To join vcl-user, send an empty message to
- [email protected]. To join vcl-dev, send an empty
- message to [email protected].
+ There are two mailing lists: [email protected] and [email protected].
+ To join user, send an empty message to [email protected].
+ To join dev, send an empty message to [email protected].
* Submit bug reports and feature requests to our JIRA bug tracking system.
See section IV below for more information on doing this.
-* Create documentation on our Confluence site. Create an account at
- http://cwiki.apache.org/confluence/display/VCL/Index and just start adding
- content. (Note to current community: We should create a page explaining
- the layout so new people will know where to add content better.)
+* Create documentation changes for our website. Our site is at
+
+ http://vcl.apache.org/
+
+ Anonymous contributions can be made by following these instructions:
+
+ http://www.apache.org/dev/cmsref#non-committer
-* Submit patches through the vcl-dev mailing list and via the JIRA bug
+* Submit patches through the dev mailing list and via the JIRA bug
tracking system. Once you have become familiar with VCL, you can begin
assisting with the development of it by picking a JIRA issue to fix or by
adding a feature needed at your site. Then, contribute a patch of your
- changes through the JIRA tracking system and send a message to the vcl-dev
+ changes through the JIRA tracking system and send a message to the dev
list explaining what you have done.
* Become an official committer to the project. Once you have shown that you
have
@@ -78,7 +89,7 @@ There are five ways to become involved i
project.
* If you are interested in contributing something to the project, please
discuss
- it on the vcl-dev list BEFORE starting work on it. This allows the community
+ it on the dev list BEFORE starting work on it. This allows the community
to be involved in decisions and allows current developers to provide some
guidance.
@@ -87,13 +98,13 @@ IV. How to Submit Bugs and Feature Reque
If you find a bug, please submit a bug report to our JIRA bug tracking system
at
http://issues.apache.org/jira/browse/VCL (you will need to set up an account
there if you haven't already done so - it's free to anyone). Also, we would
-appreciate it if you mentioned that you filed a bug on the vcl-dev list to make
+appreciate it if you mentioned that you filed a bug on the dev list to make
sure we don't miss it.
If you would like to requrest a new feature, you can also submit that in the
same way through JIRA (just select "New Feature" or "Improvement" as the Issue
Type). Again, it would be helpful if you mentioned that you filed a feature
-request on the vcl-dev list.
+request on the dev list.
After you have created a JIRA issue, you have the option to vote on it to help
us know how to prioritize issues. You can also "watch" the issue to see when
Modified: vcl/branches/vcl-2.2-bugfixes/UPGRADE
URL:
http://svn.apache.org/viewvc/vcl/branches/vcl-2.2-bugfixes/UPGRADE?rev=1458384&r1=1458383&r2=1458384&view=diff
==============================================================================
--- vcl/branches/vcl-2.2-bugfixes/UPGRADE (original)
+++ vcl/branches/vcl-2.2-bugfixes/UPGRADE Tue Mar 19 16:24:40 2013
@@ -1,6 +1,6 @@
-This file explains how to upgrade an existing install of Apache VCL 2.1 or 2.2
-to Apache VCL 2.2.1. It assumed that you extracted the release archive
-to /root/apache-VCL-2.2.1-incubating
+This file explains how to upgrade an existing install of Apache VCL 2.2 or
2.2.1
+to Apache VCL 2.2.2. It assumed that you extracted the release archive
+to /root/apache-VCL-2.2.2
The basic steps that will be performed:
@@ -17,23 +17,23 @@ The basic steps that will be performed:
1. Shutdown httpd and vcld services
service httpd stop
- service vcld stop
+ service vcld stop
2. Create a backup of vcl database
We will create a backup of the vcl database. This will provide a restore point
if necessary.
- mysqldump vcl > ~/vcl-pre2.2.1-upgrade.sql
+ mysqldump vcl > ~/vcl-pre2.2.2-upgrade.sql
-3. Update mysql schema
+3. Update mysql schema (2.2 -> 2.2.2 only)
This step updates the mysql schema.
- cd /root/apache-VCL-2.2.1-incubating
+ cd /root/apache-VCL-2.2.2
mysql vcl < mysql/update-vcl.sql
-4. Grant CREATE TEMPORARY TABLES to mysql user
+4. Grant CREATE TEMPORARY TABLES to mysql user (2.2 -> 2.2.2 only)
The web code now requires access to create temporary tables in mysql. You need
to grant the user your web code uses to access mysql the "CREATE TEMPORARY
@@ -54,7 +54,7 @@ exit
5. Update web code
-This step we will move the existing web directory out of the way, so we can
copy
+This step will move the existing 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 your
configuration changes. These instructions assume that you installed the vcl web
code at /var/www/html/vcl. If you installed it elsewhere, replace
@@ -63,70 +63,66 @@ code at /var/www/html/vcl. If you instal
a. copy your old code out of the way
cd /var/www/html
- mv vcl ~/vcl-pre2.2.1_web
+ mv vcl ~/vcl-pre2.2.2_web
+
+ b. copy the new code in place
+
+ cd /root/apache-VCL-2.2.2
+ cp -r web /var/www/html/vcl
+
+ c. copy your config files from the previous version:
- b. copy the new code in place
+ cd ~/vcl-pre2.2.2_web/.ht-inc
+ cp conf.php secrets.php pubkey.pem keys.pem /var/www/html/vcl/.ht-inc
- cd /root/apache-VCL-2.2.1-incubating
- cp -r web /var/www/html/vcl
+ d. make /var/www/html/vcl/.ht-inc/maintenance writable by the web server
+ user - normally this is the 'apache' user
- c. copy your config files from the previous version:
+ chown apache /var/www/html/vcl/.ht-inc/maintenance
- cd ~/vcl-pre2.2.1_web/.ht-inc
- cp conf.php secrets.php pubkey.pem keys.pem
/var/www/html/vcl/.ht-inc
+ e. make changes to conf.php: (2.2 -> 2.2.2 only)
- d. (2.1 -> 2.2.1 only) make /var/www/html/vcl/.ht-inc/maintenance
writable by
- the web server - if httpd on your server is running as the user
apache:
+ A new user group permission that controls who can manage block
allocations
+ globally or for a specific affiliation has been added. It can be granted
+ to any user group under Privileges->Additional User Permissions->Manage
+ Block Allocations. Users with this permission are notified of new block
+ allocation requests. Remove the following from conf.php.
- chown apache /var/www/html/vcl/.ht-inc/maintenance
+ $blockNotifyUsers
- e. (2.1 -> 2.2.1 only) add the following new entries to conf.php - You
can copy
- them in from .ht-inc/conf-default.php. Descriptions of each
item can also be
- found in conf-default.php
+ A new user group permission that controls who can look up users globally
+ or for a specific affiliation has been added. It can be granted to any
+ user group under Privileges->Additional User Permissions->User Lookup.
+ Users with this permission can look up information about other users.
+ Remove the following from conf.php.
+
+ $userlookupUsers
- * date_default_timezone_set('America/New_York');
- * $blockNotifyUsers = "[email protected]";
- * define("SCHEDULER_ALLOCATE_RANDOM_COMPUTER", 0);
- * define("DOCUMENTATIONURL",
"https://cwiki.apache.org/VCLDOCS/";);
- * define("USEFILTERINGSELECT", 1);
- * define("FILTERINGSELECTTHRESHOLD", 1000);
- * define("DEFAULTTHEME", 'default');
6. Restart httpd service
- service httpd start
+ service httpd start
7. Update management node code
-This step will move the existing vcl code base out of the way, so we can
cleanly
-copy in the new management node code.
+This step will make a backup copy of the existing code and then copy the new
+code over the existing code to preserve any drivers or other files you've
added.
+
+ a. Copy the existing management node code base to a backup location
+
+ cd <your vcl MN code root path>
+ ie. cd /usr/local/
+ cp -r vcl ~/vcl-pre2.2.2_managementnode
+
+ b. Copy in the 2.2.2 code base to /usr/local, copying in should preserve any
+ drivers or other files you've added.
+
+ /bin/cp -r /root/apache-VCL-2.2.2/managementnode/* /usr/local/vcl
- a. Copy the existing management node code base to a backup location
+ c. Run install_perl_libs.pl to add any new perl library requirements:
- cd <your vcl MN code root path>
- ie. cd /usr/local/
- cp -r vcl ~/vcl-pre2.2.1_managementnode
-
- b. Copy in the 2.2.1 code base to /usr/local, copying in should
preserve any
- drivers or other files you've added.
-
- /bin/cp -r /root/apache-VCL-2.2.1-incubating/managementnode/*
/usr/local/vcl
-
- c. (2.1 -> 2.2.1 only) Make changes related to vcld.conf settings
-
- * Open VCL web interface
- * 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
+ /usr/local/vcl/bin/install_perl_libs.pl
8. Restart vcld service
- service vcld start
+ service vcld start
