Guest Access Implementation Plan, February 3, 2009

Steps

Preparation work

• (Jan 30, 2009) Kirk : Create the template for guest type with an altered workspace to prevent membership, resources, worksite set up and Account PW editing. (Done)

• (Jan 30, 2009) Kirk : Create the Guest Access site (Done)

  • Select the following tools: Home, Site Info

  • Site cannot be joined by anybody

  • Add .anon role to site enabling site.visit function in the site's realm

  • Site Info Tool is hidden using Page Order tool on Site Info

• (Feb 02, 2009) Thomas: Prepare sakai_2-5-x-prod-010 on sakaiprod1

During maintenance window : February 3, 2009 : 05:00 - 07:00

• (05:00 Thomas) Put smartsite into maintenance mode and shutdown Sakai on all 7 application servers

• (05:05 Thomas) Deploy sakai_2-5-x-prod-010 tag on all 7 application servers via setup-sakai-node.sh

• (05:10 Thomas) Startup sakaiprod1

  • Add Guest Registration tool via Admin's Site tool to the Guest Access site

  • Record the url of the just added Guest Registration tool

  • Stop Sakai on sakaiprod1

  • Edit sakai.properties file: property guest.registration.tool.url

    • The property is of the following format: guest.registration.tool.url=http://smartsite.ucdavis.edu:8443/portal/site/<siteId>/page/<pageId>?toolstate-<toolId>= e.g. guest.registration.tool.url=https://smartsite.ucdavis.edu:8443/portal/site/fcb8657c-f611-4314-9f51-d4a3d90bf220/page/b9137edd-a08a-4606-9ebe-1f64caccab73?toolstate-4a2dc079-5254-4122-8978-2bae859edfb0=

      • We forgot the following step during deployment

      • Commit sakai.properties changes to:

        • https://mware.ucdavis.edu/svn/ucd-sakai/sakai-properties/branches/sakai_2-5-x/smartsite-prod/

        • https://mware.ucdavis.edu/svn/ucd-sakai/sakai-properties/tags/sakai-properties-2-5-x-prod-010/

• (05:20 Thomas) Run setup-sakai-node.sh on all 7 application servers

• (05:30 Thomas) Start Sakai on all 7 application nodes

• (05:35 TEAM) Verify Guest Access installation

  • Create a project site ("Guest Access Verification") [Thomas]

  • Enable site.add.guests function for that site's maintain role [Thomas, verified by Kirk]

  • Add guest to project site [Thomas to add: kdalexander@sbcglobal.net, swavocet@gmail.com, vikingvikingson@yahoo.com]

  • Register and activate guest [Kirk, Sandra and Pete to register their own external accounts, Thomas to Activate, then Kirk/Sandra/Pete attempt to login]

• (06:00 TEAM) Evaluate test results [If all 3 users can login then good to go, else discuss fallback.]

• (06:20 Thomas) Take 7 application servers out of maintenance

Fall-back Procedure (If needed)

• ( 5 min ) In case the Guest Access test fails for some reason, we just won't enable the site.add.guests function on any sites and remove from "Guest Access Verification" site

  • ( 10 min ) We may want to remove the Guest Login button from the portal site by editing the sakai.properties and restarting Sakai all 7 application servers. Comment out the following properties:

    • #SAK-2503: guest access - enable alternate login xlogin.enabled=true xlogin.text=Registered Guest Login

      
      
      
      
      
      

• ( 30 min ) If code fails during test - roll back to previous sakai_2-5-x-009

  • Stop Sakai on all application servers

  • Redeploy sakai_2-5-x-009

  • Redeploy sakai.properties 009 prod tag

  • Running setup-sakai-node.sh on all application servers

  • Startup Sakai on all application servers