Drupal Enterprise Environment Migrations


Quick View
Summary: 

This project is to identify current Drupal sites that require migration to the newly deployed Enterprise Environment. UTO Staff will work one on one with site administrators to ensure a smooth migration from the hosted environment to the enterprise.

 

Requirements for sites to move to enterprise environment:

  1. Website requires access to enterprise data
  2. Website is critical to ASU/UTO operations
  3. Other ASU services/websites are dependent on the website staying up (e.g. my.asu.edu)

The following websites will be transitioned over to the EnterpriseĀ  environment.

  1. Students.asu.edu (Nayeli Quiros -USI)
  2. BTS.asu.edu (Rudy Bellavia - Business Technology Services)
  3. researchadmin.asu.edu (Nancy Arbaugh- OVPREA)
  4. Graduate.asu.edu

 

Current Status (3/11/09 -- on hold)

  • Students.asu.edu has been moved to the enterprise-dev environment
  • Production migration process is not ready -- running into issues and project is on hold until we can figure it out.

RE-Baselined (4/13 - 4/30)

  • Production migration process kinks worked out -- process finalized before 4/30
  • Migrate students.asu.edu over.

Update (4/30)

  • Tasks complete. Students.asu.edu migrated over successfully in dev mode, awaiting USI dev's to complete final tasks before full migration to prod.

 

Start Date: 
November 3, 2008
Go Live: 
May 1, 2009
End Date: 
May 8, 2009
Current Milestone: 
05/08/2009 - Tasks complete. Awaiting OK to go full production from client websites.
Stage: 
Complete - In operation and supported by UTO.
People
Sponsor/Champion: 
Adrian Sannier, Vice President and University Technology Officer
Project Manager: 
Adrian Teo
Contact for more information: 
adrian.teo@asu.edu
Associate VP University Technology: 
Max Davis-Johnson
University Technology Director: 
Adrian Teo
More Info
Source: 
Internal
Priority: 
High
Scope: 

PHASE 1 - students.asu.edu

Students.asu.edu will be the first planned move; plan is as follows:

  1. Copy current students.asu.eduĀ  to enterprise-dev environment.
  2. Deploy the site in dev, confirm working
  3. Trial migration of dev site to enterprise-prod.
  4. Confirm the duplicate site runs on the production environment (i.e. dev to prod migration process test)
  5. Establish freeze on current site, do a final copy.
  6. Re-deploy and move to enterprise-dev
  7. Finally, switch DNS from current hosts to enterprise dev.
  8. Lift freeze.

ETA for steps 1-4 is 11/14

ETA for steps 5-8 is dependent on 1-4 and will need about additional 3 days of work

 

Phase 1 resourcesĀ 

  • Daniel Garcia-Mont (UTO Web Consulting)
  • Brent Dunlock (UTO Open Systems)
  • Nayeli Quiros & assigned staff (USI)

 

 

Syndicate content