Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. follow instructions on VCL 2.3 Release page to download and verify apache-VCL-2.3-incubating.tar.bz2 and put in in /root
  2. extract VCL 2.3 code
    Tip

    tar xjf apache-VCL-2.3-incubating.tar.bz2

Shutdown services

...

Tip

cd /root/apache-VCL-2.3-incubating
mysql vcl < mysql/update-vcl.sql

...

  1. move your old code out of the way
    Tip

    cd /var/www/html
    mv vcl ~/vcl_2.2.1_web

  2. copy the new code in place
    Tip

    cd /root/apache-VCL-2.3-incubating
    cp -r web /var/www/html/vcl

  3. copy your 2.2.1 config files
    Tip

    cd ~/vcl_2.2.1_web/.ht-inc
    cp conf.php secrets.php pubkey.pem keys.pem /var/www/html/vcl/.ht-inc

  4. Make the maintenance directory writable by the web server user. You will need to know what user httpd runs as on your server. This can be found with
    Tip

    ps aux | grep httpd

    Look at the first column. One process will be owned by root. The remaining processes will be owned by the web server user. Now, own /var/www/html/vcl/.ht-inc/maintenance to that user (replacing 'apache' with your web server user if different):
    Tip

    chown apache /var/www/html/vcl/.ht-inc/maintenance

  5. make some changes to conf.php:
    1. 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
      Warning

      $blockNotifyUsers

      from conf.php.
    2. 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
      Warning

      $userlookupUsers

      from conf.php.
    3. Multilingualization has been added VCL. So, DEFAULTLOCALE has been added to conf.php to set the default locale. Add
      Tip

      define("DEFAULTLOCALE", "en_US");

      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.
    4. Users authenticated using Shibboleth without also having an LDAP server can now be added before they log in. Add
      Tip

      define("ALLOWADDSHIBUSERS", 0);

      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.
    5. Some LDAP related items have been simplified in the code using some additional options in $authMechs. For any LDAP entries, you need to 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'). Add
      Tip

      "lookupuserbeforeauth" => 0,
      "lookupuserfield" => '',

      to each LDAP array you have in the $authMech array in conf.php.
    6. If you are using any Local accounts for authentication, you need to modify the entries for $addUserFunc and $updateUserFunc. Change
      Warning

      Wiki Markup
      $addUserFunc\[$item['affiliationid']\] = create_function('', 'return 0;');
      $updateUserFunc\[$item['affiliationid']\] = create_function('', 'return 0;');

      to
      Tip

      Wiki Markup
      $addUserFunc\[$item['affiliationid']\] = create_function('', 'return NULL;');
      $updateUserFunc\[$item['affiliationid']\] = create_function('', 'return NULL;');

...

  1. Copy 2.2.1 code base to a backup location
    Tip

    cd <your vcl MN code root path>
    ie. cd /usr/local/
    cp -r vcl ~/vcl_2.2.1_managementnode

  2. Copy in the 2.3 code base to /usr/local, copying in should preserve any drivers or other files you've added.
    Tip

    /bin/cp -r /root/apache-VCL-2.3-incubating/managementnode/* /usr/local/vcl

  3. Run install_perl_libs.pl to add any new perl library requirements:
    Tip

    /usr/local/vcl/bin/install_perl_libs.pl

...