Recommended
More Related Content
What's hot
What's hot (20)
Similar to Drupal GovCon 2015 - Managing Incremental Migrations
Similar to Drupal GovCon 2015 - Managing Incremental Migrations (20)
Recently uploaded
Recently uploaded (20)
Drupal GovCon 2015 - Managing Incremental Migrations
- 1. How to Eat an Elephant: Managing Incremental Migrations Presentation Slides: http://tiny.cc/govcon-elephant
- 2. What is this session about? ABOUT WHY HOW LESSONS QUESTIONS
- 3. This session is about… • Unique aspects of incremental migrations • Lessons learned from experience • Focus on project management aspects • Case study examples from Justice.gov
- 4. Justice.gov Case Study: the Challenge Migration Sources • 80% Hand curated HTML • Custom CMS • RedDot CMS • Wordpress • PHP + DB Migration Assets • 250k pages • 200k PDFs • Images • Videos Migration Stakeholders • Content owned by 120 offices across DOJ • Project managed by the OCIO
- 5. Justice.gov Case Study: the Results Justice.gov on Drupal! 200,000 nodes 120,000 file entities 5,476 git commits 750 content managers 188 code releases 163 migration classes 189 organic groups 18 months
- 6. Why would I consider incremental migration? ABOUT WHY HOW LESSONS QUESTIONS
- 7. Typical site migration project Discover Design Develop Migrate Training Cleanup Launch Reference: http://www.acquia.com/blog/taking-migrations-madness-gladness
- 8. Typical site migration project doesn’t always work • Feature re-engineering process potentially leads to endless discovery phase • Imbalance of training needs and resources • Expectation of significant migration cleanup • Benefits of agile approach: quick wins, stakeholder engagement, risk mitigation Discover Design Develop Migrate Training Cleanup Launch
- 9. Good candidates for incremental migration • Not planning a major visual redesign • Decentralized management of a large site • Many website content managers and few project team resources • Website can be divided into logical sections
- 10. How do I migrate incrementally? ABOUT WHY HOW LESSONS QUESTIONS
- 11. Determine the migration sequence Schedule Sequence Dependencies Big picture: discovery meetings, follow-up meetings Quick wins: visible change to energize stakeholders Related content: data flows, common migration sources Organizational needs: deadlines, high traffic periods
- 12. Establish a repeatable process for onboarding • ROT analysis (redundant, outdated, trivial) • Stakeholder communications • Flexibility
- 13. Establish a reverse proxy layer or CDN www.example.com/section1 legacy website IP address www.example.com/section2 new Drupal website IP address Create a reverse proxy layer with Apache or Varnish configs Content delivery network (CDN) enables this IP routing, plus performance and security benefits. Additional cost. Reference: https://www.acquia.com/blog/dont-wait-migrate-drupal-continuous-migration
- 14. Add new content without modifying existing content Deploy to Production Migrate to Production How it works Migrate to staging environment. Content cleanup in staging. Deploy from staging to prod. Go-live by changing proxy rules. Migrate to prod environment. Content cleanup in prod. Go-live by changing proxy rules. Pros Content cleanup “safer” in stage. Less complexity. Cons Must patch Deploy to integrate with some contributed modules. Justice.gov Experience Tried it and gave up. Did it 150 times.
- 15. What should I watch out for? ABOUT WHY HOW LESSONS QUESTIONS
- 16. Content review and cleanup can cause delays 1. Set accurate expectations for content cleanup 2. Define migration acceptance criteria in advance 3. Define the process for prioritizing bugs 4. Prepare project champions to unblock you when the time comes Reference: http://www.acquia.com/blog/10-tips-streamline-migration-review
- 17. Many artifacts can be slight variations of a template • Kickoff meeting handouts • Training materials and curriculum • Tickets in the PM tracking software • Base migration classes + extension classes for each site section and content type
- 18. Effects of the experience curve are real Reasons for the effect: labor efficiency, standardization, specialization, methods improvements, optimizing the resource mix, network effects, shared experience effects
- 19. Sync pace of development, content, and stakeholder work
- 20. Incremental migration allows for client enablement
- 21. Questions? joshua.smith@acquia.com, gail.d.solomon@usdoj.gov Presentation Slides: http://tiny.cc/govcon-elephant ABOUT WHY HOW LESSONS QUESTIONS
Editor's Notes
- Gail Introductions Slides are available at this link
- Gail About, Why, How, Lessons, Questions
- Gail Incremental migration, phased migration, continuous migration
- Gail Large amount of content to migrate Large number of people to coordinate with Decentralized management and lack of formal authority
- Gail It is done, but it was a lot of work. Only could have been done incrementally.
- Josh
- Josh
- Josh
- Josh
- Gail
- Gail Must understand enough detail to get the sequence right Several types of dependencies that will affect sequence
- Gail Structure a repeatable process for additional migrations Create template instructions and slightly customize for each migration Update an intranet project site as new information becomes available Ongoing tasks are ROT analysis and stakeholder communications like advisory group, email newsletter, etc. Easier to be flexible when starting with a structure
- Josh Get the right people involved in this early (infrastructure, network ops, security)
- Josh
- Gail
- Gail 1- Discuss tips for working with different personalities 5- Story about OARM wanting to take the new site down immediately because it wasn’t perfect. Vijay pushed back and mobilized the team to quickly solve the issues.
- Gail / Josh With templates it’s less work than it seems.
- Josh Specialization: team members naturally fell into roles (search, UAT, kickoff, etc) Methods improvement: Developers got bored of writing similar migration classes over and over. Built a script to write the classes for them. First release included 2 migrations. Eleventh release included 21 migrations.
- Josh Much of the schedule in a project like this is spent with stakeholders: clarifying requirements, training, content cleanup Increasing the pace of development won’t make the project go faster Focus on optimizing project staffing to synchronize the pace of dev and content work
- Josh Vendor / Client handoff is hard. One bad approach. Another bad approach. Incremental allows a good approach. Incremental migration allowed the project to stay steady through many staffing transitions. CIO transition, 2 ADs retired, Only 1 remaining from initial migration team.