- Confirm maintenance mode
- We need to allow access from dedicated IPs for possible pre-upgrade work
- Adjust iptables on production nodes to allow JMX access to port 9000 for specified IPs
- PORT 8443:
# 169.237.11.246 (thomas)
# 69.12.224.247 (thomas)
# 169.237.97.91 (zoidberg: vpn, terminal server)
# 169.237.97.133 (kirk)
# 169.237.11.220 (james)
# 169.237.11.130 (sandra)
# 169.237.11.6 (jon)
# 169.237.11.242 (mike)
# 169.237.11.37 (Pete Peterson)
# 169.237.205.242 (Nancy Wilkison)
# OTHERS
- PORT 9000:
# 169.237.11.246
Steps
Work Aheads
...
- (Jan 30, 2009) Kirk, Create the template for guest type with an altered workspace to prevent membership, resources, worksite set up and ???
- (Jan 30, 2009) Kirk, Create the Guest Access site
- Select the following tools: Home, Site Info
- Add Guest Registration Tool via Admin Site tool
- Add .anon role to site enabling site.visit function in the site's realm
During
...
designated maintenance window
- (05:30 Thomas) Put smartsite into maintenance mode and shutdown sakai Sakai on all 7 app application servers.
- (05:35 Joncarlo) Deploy SAK-2586 switch
- (0405: Mike35 Thomas) Deploy Prod Tag 010. This deploys the following Jiras on sakProd1:
- sak-2599
- sak-2589
- sak-2584
- sak-2583
- sak-2582
- sak-2577
- sak-2575
- sak-2573
- sak-2568
- sak-2555
- sak-2548
- sak-2539
- sak-2538
- sak-2536
- sak-2535
- sak-2534
- sak-2533
- sak-2520
- sak-2472
- sak-2075
- sak-1638.
- (05:30 Mike) Start sakaiprod1
- (05:40 Mike) Test simple functions
- (05:45 Mike) If simple test is OK, then start deploying sakaiprod2-6 and sakaiprodmail1
- (06:00 Mike) Start all other app servers(sakaiprod2-6 and sakaiprodmail1)
- (06:10 Mike) Remove maintenance mode for sakaiprod1-6 and sakaiprodmail1
- (06:15 Mike) Validate all app servers are not in maintenance modesakai_2-5-x-prod-010 tag on all 7 application servers via setup-sakai-node.sh
- (05:50 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
No Format 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=
- (06:00 Thomas) Run setup-sakai-node.sh on all 7 application servers
- (06:10 Thomas) Start Sakai on all 7 application nodes
- (06:15 TEAM) Verify Guest Access installation
- Create a project site
- Enable site.add.guests function for that site's maintain role
- Add guest to project site
- Register and activate guest
- (06:30 TEAM) Evaluate test results
- (06:50 Thomas) Take 7 application servers out of maintenance
Fall-back Procedure (If needed)
- (06:00 Prabhu) Run the restore
- (06:00 Michael) roll back the executable for all upgrade changes
- (06:40 Michael) bring up prod1
- (06:43 Sandra and Kirk) QA SmartSite to make sure it's back in its correct state. Check for database markers
- (In case the Guest Access test fails for some reason, we just won't enable the site.add.guests function on any sites