Finish current uPortal upgrade project (Chris O'Brien - PM)
Project targeted to complete by 5/31/11
Includes (as noted in Approved Change Order 001):
1. Scalability/Linear testing https://jira.cornell.edu/browse/UPORTALUPG-188
2. Fully Transition production support from the E-Team to the A-Team (ISIS); which includes the following tasks:
a. Internal Procedures[1]
i. Updating/maintaining groups https://jira.cornell.edu/browse/UPORTALUPG-263
ii. Adding group definitions to Announcements https://jira.cornell.edu/browse/UPORTALUPG-247
b. Production Support Transition from Engineering team to A-Team (A-Team Hand-Off Docs) https://jira.cornell.edu/browse/UPORTALUPG-44 ; including:
i. CAS provisioning under puppet https://jira.cornell.edu/browse/UPORTALUPG-284
ii. “hardening” of uPortal production environment https://jira.cornell.edu/browse/UPORTALUPG-283
c. Standard Operating Procedures (SOPs):
i. Operating Procedures for Infrastructure https://jira.cornell.edu/browse/UPORTALUPG-56
ii. Engineering/Architecture Docs https://jira.cornell.edu/browse/UPORTALUPG-41
iii. ISIS Disaster Recovery (DR) Docs https://jira.cornell.edu/browse/UPORTALUPG-42
iv. Configuration Management (CM) Docs https://jira.cornell.edu/browse/UPORTALUPG-43
v. Hosting Disaster Recovery (DR) Docs https://jira.cornell.edu/browse/UPORTALUPG-52
vi. Hosting Release Management (new channels) Docs https://jira.cornell.edu/browse/UPORTALUPG-55
3. Support of LaunchPad performance testing (if needed) https://jira.cornell.edu/browse/UPORTALUPG-270
4. Stabilization period (includes problem resolution)
Production Support for the myCornell framework will be handled as follows for the interim period (until transition from the E-Team to the A-Team is complete as noted above):
Ø Tier 1 calls à Help Desk à Portal Administrator
Ø Tier 2 calls à Portal Administrator à A-Team à E-Team
A Service Support Team has been formed and includes members from the Help Desk.
Any issues/fixes will be batched up and prioritized with the Portal Administrator, Service Owner, Service Manager and the A-Team.
As additional Reference Groups are defined, the Portal Administrator will coordinate with the A-Team to have these applied to the PAG groups and/or Announcements as needed per Standard Maintenance requests.
LaunchPad “loose-ends”:
1. Performance testing and resolution (if needed) https://jira.cornell.edu/browse/LAUNCHPADENHANCEMENTS-92
2. Stabilization period (includes problem resolution)
3. User preferences needs fixing https://jira.cornell.edu/browse/UPORTALUPG-328
Administrative “loose-ends”:
1. Prepare support FAQs, Help URLs, etc.:
a. FAQ and Feedback pages https://jira.cornell.edu/browse/UPORTALUPG-220
2. New & Revised CIT Services documentation https://jira.cornell.edu/browse/UPORTALUPG-127
3. Final uPortal/LaunchPad environment sign-off https://jira.cornell.edu/browse/UPORTALUPG-272
On-going operational support and enhancements
Retire uPortal.cornell.edu - June 1, 2011
Cornell engaged with Unicon - purpose is to augment technical staff to provide myCornell upgrades without impacting the Engineering team.
- Unicon would install uPortal code into Cornell Subversion
- Apply the following:
- update 3.2.4
- Pulled DLM Fragments
- provide instruction to Cornell on how to build and install
Cornell (currently not scheduled)
- take the new 3.??? uPortal code and build new version (can this process be turned over the the Release Management team) They are currently doing the build and release for KFS. Maybe this could be used as a model.
- deploy into infrastructure, dev, test, and production