1 / 17

Lessons From the Java Migration

Learn about the Java.net migration and how the community managed the challenges of upgrading infrastructure and moving to a new platform. Discover why the move was necessary, the goals of the migration, and the unexpected issues faced along the way. Gain insights into the new architecture and features of Java.net, and the lessons learned from this major change.

twood
Télécharger la présentation

Lessons From the Java Migration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lessons From the Java.net Migration Managing an Open Source Community Through Major Change

  2. What is Java.net? • 600,000+ registered users • Free hosting for 2000+ Java, JVM, or Education related open source projects • Technology communities within the larger Community, with their own leads • Editorial content • Blogs • Forums

  3. Volunteer Community Leaders (25) Oracle Management (1) Community Activities Infrastructure Management Team (5)

  4. Java.net Architecture - Old Four separate “front end” applications: Custom Content Management System Twiki Wiki Moveable Type Blogs Jive Forums Cookie-based Shared Authentication Old Project Platform Project Workspaces Project administration SVN Issue Tracking Forums Mailing Lists Project and Role-based Permissions

  5. Why did we need to move? • Outdated infrastructure and tools • No path to upgrade • Backup failures • Too expensive

  6. How did it get so bad? • Sun cutting back on staffing/budget • Painted ourselves into a corner with upgrade failures over the years • Infrastructure built for a much smaller community and never expanded As of February 2010, Sun management planned to pull the plug entirely on project hosting, if not the whole site.

  7. Oracle saves the day? Really? Yes. They recognized the value in Java.net and our community, but our expenses were unsustainable, especially given the state of our infrastructure. Deadline to move: December 2010. (We didn’t make it.)

  8. Java.net Architecture - New Drupal Content Management System Content Management Blogs, Articles, spotlights, Announcements, Twitter Syndication, RSS Aggregation Communication Drupal API Discussion Forums, Polls/Surveys, User Groups, Calendaring Administration Content Workflow, Customized Roles, Customized Content Types Project Metadata SSO Kenai Project Workspaces Project administration Kenai Web Services Repository Issue Tracking Project Wiki Mailing Lists Project and Role-based Permissions

  9. Planning – what was our goal? • Better concentration of quality projects • Code, bugs, mailing lists moved and usable • Leave paths open for more community features in the future

  10. What were the biggest issues? • Significant downtime for working projects • Data had to be moved AND converted (cvs to svn, IssueTracker to JIRA, mailing lists to SYMPA) • Users had to be moved and roles mapped • Passwords would not be exported

  11. Options • Turn off the site. Wait for data delivery. Turn on the new site. 2. Move projects in small batches, having two completely separate Java.net sites at the same time. Pick a fixed date to move the front door (editorial, blogs, forums) of the site. We chose option 2.

  12. Phased Migration! • First projects move in November 2010 • Moved Drupal presence to the new site • Turned off old site in March 2011 • Final wave of imports completed in June 2011 In retrospect, this was absolutely the right choice. Data delivery was so slow we would have been down for months.

  13. Sacrifices had to be made. • No time to move (minimally used) project based forums • Project owners would be required to fix up project home pages

  14. Unexpected Issues • Communication – there is a fine line between not enough information and too much, and many users interpret that line differently • Abandoned projects – several major projects had been quietly closed over the months or years prior

  15. How did we do? Unscientific poll, June 2010: 65% say the site is significantly better. What do people think failed? • Abandoned projects • Forums

  16. What would I do differently? • Invent a time machine • Streamline communications • Spend more time on the opt-in form and process

  17. Q&A Thanks for coming!

More Related