Author: jfthomps
Date: Tue Dec 11 16:38:16 2012
New Revision: 1420266
URL: http://svn.apache.org/viewvc?rev=1420266&view=rev
Log:
initial add of 2.3 to 2.3.1 upgrade page
Added:
vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.3to2.3.1.mdtext
- copied, changed from r1420246,
vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.1to2.3.1.mdtext
Copied:
vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.3to2.3.1.mdtext
(from r1420246,
vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.1to2.3.1.mdtext)
URL:
http://svn.apache.org/viewvc/vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.3to2.3.1.mdtext?p2=vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.3to2.3.1.mdtext&p1=vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.1to2.3.1.mdtext&r1=1420246&r2=1420266&rev=1420266&view=diff
==============================================================================
---
vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.1to2.3.1.mdtext
(original)
+++
vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.3to2.3.1.mdtext
Tue Dec 11 16:38:16 2012
@@ -1,4 +1,4 @@
-Title: Upgrade From 2.2.1 to 2.3.1
+Title: Upgrade From 2.3 to 2.3.1
Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -16,8 +16,8 @@ Notice: Licensed to the Apache Softwa
specific language governing permissions and limitations
under the License.
-This page provides information on how to upgrade from VCL 2.2.1 to VCL 2.3.1.
Please note it only applies for the upgrade
-from 2.2.1 to 2.3.1, this may or may not work for other versions.
+This page provides information on how to upgrade from VCL 2.3 to VCL 2.3.1.
Please note it only applies for the upgrade
+from 2.3 to 2.3.1, this may or may not work for other versions.
**The basic steps that will be performed**
@@ -29,7 +29,7 @@ from 2.2.1 to 2.3.1, this may or may not
- Update Management node vcl code, create a backup, copy in new, make
changes
- Restart vcld service
-# Detailed steps for upgrade from 2.2.1 to 2.3.1 #
+# Detailed steps for upgrade from 2.3 to 2.3.1
1. follow instructions on VCL 2.3.1 Release page to download and verify
apache-VCL-2.3.1.tar.bz2 and put in in /root
2. **extract VCL 2.3.1 code**
@@ -48,23 +48,19 @@ from 2.2.1 to 2.3.1, this may or may not
:::BashLexer
mysqldump vcl > ~/vcl-pre2.3.1-upgrade.sql
-5. This step **updates the mysql schema**. *Note*: A new resource group is
added in update-vcl.sql - **all profiles**.
-Access to manage the group is added to the VCL->admin node in the privilege
tree if that node exists. If not, you will
-need to add it manually after starting httpd again. To add it manually, pick a
node in the privilege tree, scroll to
-Resources, click Add Resource Group, select serverprofile/all profiles from
the drop-down box, check available,
-administer, manageGroup, and manageMapping, and click Submit New Resource
Group.
+5. This step **updates the mysql schema**.
:::BashLexer
cd /root/apache-VCL-2.3.1
mysql vcl < mysql/update-vcl.sql
-6. **Update the web code**. This step we will move the 2.2.1 web directory out
of the way, so we can copy in the new
+6. **Update the web code**. This step we will move the 2.3 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 /var/www/html/vcl with your vcl web root.
:::BashLexer
cd /var/www/html
- mv vcl ~/vcl_2.2.1_web
+ mv vcl ~/vcl_2.3_web
7. **Copy the new code** in place
@@ -72,10 +68,10 @@ that you installed the vcl web code at /
cd /root/apache-VCL-2.3.1
cp -r web /var/www/html/vcl
-8. **Copy your 2.2.1 config files**
+8. **Copy your 2.3 config files**
:::BashLexer
- cd ~/vcl_2.2.1_web/.ht-inc
+ cd ~/vcl_2.3_web/.ht-inc
cp conf.php secrets.php pubkey.pem keys.pem /var/www/html/vcl/.ht-inc
9. **Make the maintenance directory writable by the web server user**.
Normally this is the apache user, if using
@@ -84,78 +80,18 @@ a different user change below cmd accord
:::BashLexer
chown apache /var/www/html/vcl/.ht-inc/maintenance
-10. **Make changes to conf.php**:
-
- <ol type="a">
- <li>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**.
-
- :::PhpLexer
- $blockNotifyUsers
-
- <li>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**
-
- :::PhpLexer
- $userlookupUsers
-
- <li>**Multilingualization** has been added VCL. So, **DEFAULTLOCALE** has
been added to conf.php to set
-the default locale. **Add the following to conf.php**, changing en_US if
needed to match your locale. You can
-look in /var/www/html/vcl/locale to see which ones are available.
-
- :::PhpLexer
- define("DEFAULTLOCALE", "en_US");
-
- <li>Users authenticated using Shibboleth without also having an LDAP
server can now be added before they
-log in. **Add the following to conf.php** If you are using Shibboleth and
would like to be able to add users
-to groups before the user has ever logged in to VCL, you can set this to 1.
However, please note that if you
-typo the userid, there is no way to verify it, and the user will be added with
the typoed userid.
-
- :::PhpLexer
- define("ALLOWADDSHIBUSERS", 0);
-
- <li>LDAP related items have been simplified in the code using additional
options in $authMechs. For any
-LDAP entries, add two options. "lookupuserbeforeauth" is used if you need VCL
to look up the full DN of a
-user and use that when doing the bind that authenticates the user (if you
don't know what this means, leave
-it set to 0). If you need to set it to 1, then you will need to set
"lookupuserfield" to what LDAP attribute
-to use when looking up the user's DN (typically either 'cn', 'uid', or
'samaccountname'). In conf.php, **Add
-the following to each LDAP** array you have in the $authMech array.
-
- :::PhpLexer
- "lookupuserbeforeauth" => 0,
- "lookupuserfield" => '',
-
- <li>If you are using any Local accounts for authentication, you need to
modify the entries for $addUserFunc and $updateUserFunc. Change
-
- * OLD
-
- :::PhpLexer
- $addUserFunc[$item['affiliationid']] = create_function('', 'return
0;');
- $updateUserFunc[$item['affiliationid']] = create_function('',
'return 0;');
-
- * NEW
-
- :::PhpLexer
- $addUserFunc[$item['affiliationid']] = create_function('', 'return
NULL;');
- $updateUserFunc[$item['affiliationid']] = create_function('',
'return NULL;');
-
- </ol>
-
11. **Restart httpd service**
:::BashLexer
service httpd start or /etc/init.d/httpd start
-12. **Update management node code** This step will make a backup copy of the
2.2.1 vcl code base and then copy
+12. **Update management node code** This step will make a backup copy of the
2.3 vcl code base and then copy
the new code over the existing code to preserve any drivers or other files
you've added.
:::BashLexer
cd <your vcl MN code root path>
ie. cd /usr/local/
- cp -r vcl ~/vcl_2.2.1_managementnode
+ cp -r vcl ~/vcl_2.3_managementnode
13. **Copy in the 2.3.1 code base to /usr/local**, copying in should preserve
any drivers or other files you've added.
