Your SlideShare is downloading. ×
0
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Understanding the Meaningful Use of Open Source Software
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Understanding the Meaningful Use of Open Source Software

948

Published on

My presentation from the Meaningful Use of Complex Medical Data Symposium.

My presentation from the Meaningful Use of Complex Medical Data Symposium.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
948
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Randall Wetzel, MD, MS Roby Khemani, MD, MS Dave Kale, MS Paul Vee, MBA Dan Crichton, MS Chris Mattmann, PhD Andrew Hart, MS Cameron Goodale, MBA Paul Zimdars MUCMD.ORG | SABAN RESEARCH CENTER | AUGUST 26-27 2011
  • 2. <ul><li>Areas for Open Source within the clinical context </li></ul><ul><li>Strategies and Decision Points </li></ul><ul><li>Discuss Open Source in the context of our current NLM grant between CHLA and JPL </li></ul><ul><li>This is a shorter version of a longer, half day breakout on NASA Open Source that I led at the 9 th NASA Earth Science Data System Working Group Meetings in October 2010 </li></ul><ul><li>http://s.apache.org/anM </li></ul><ul><li>Also check out NASA OSS slides that inspired this: http://s.apache.org/pw </li></ul>Does ‘open source’ provide clinical opportunities ? Can we devise a framework for understanding the concerns and challenges of using open source software in “big data” systems? MUCMD.ORG | SABAN RESEARCH CENTER | AUGUST 26-27 2011
  • 3. <ul><li>Apache Member involved in </li></ul><ul><ul><li>OODT (VP, PMC), Tika (VP,PMC), Nutch (PMC), Incubator (PMC), SIS (Mentor), Lucy (Mentor) and Gora (Champion), Hadoop MRUnit (Mentor) </li></ul></ul>MUCMD.ORG | SABAN RESEARCH CENTER | AUGUST 26-27 2011 <ul><li>Architect/Development Lead at NASA JPL in Pasadena, CA </li></ul><ul><li>Software Architecture/Engineering Prof at USC </li></ul>
  • 4. <ul><li>It ’s here </li></ul><ul><li>Chances are if you build software nowadays, are you are using some type of open source software </li></ul><ul><li>Let me give you some context… </li></ul>MUCMD.ORG | SABAN RESEARCH CENTER | AUGUST 26-27 2011
  • 5. Where is open source most useful? Which area should produce open source software?
  • 6. <ul><li>Licensing </li></ul><ul><ul><li>GPL(v2, v3?), LGPL(v?), BSD, MIT, ASLv2 </li></ul></ul><ul><ul><li>Your own custom license approved by OSS </li></ul></ul><ul><ul><ul><li>NLM OSS license? </li></ul></ul></ul><ul><ul><ul><li>CHLA license? </li></ul></ul></ul><ul><ul><li>Copy-left versus Copy-right </li></ul></ul><ul><li>Redistribution </li></ul><ul><ul><li>Can you take open source product X and use it in your commercially interested software Y? </li></ul></ul><ul><ul><ul><li>If so, do you have to pay for it? </li></ul></ul></ul><ul><li>Should others pay for your open source product if they use it in their commercial application? </li></ul><ul><li>Open Source “Help Desk” Syndrome versus Community </li></ul><ul><ul><li>Are you trying to simply make your open source software (releases) available for distribution (aka help desk)? </li></ul></ul><ul><ul><li>Are you trying to get others to “buy in” to your open source software? </li></ul></ul>
  • 7. <ul><li>Intellectual Property </li></ul><ul><ul><li>Who owns it? </li></ul></ul><ul><ul><li>How does the Open Source Software affect your IP? </li></ul></ul><ul><li>Open Source Ecosystems </li></ul><ul><ul><li>Where can you find the “killer app” you need? </li></ul></ul><ul><ul><li>Which communities are conducive for longevity? </li></ul></ul><ul><ul><li>How relevant are “generic” open source software communities to Clinical “Big Data” Data Systems? </li></ul></ul><ul><li>Contributing </li></ul><ul><ul><li>Are you even allowed to contribute to a OSS community? </li></ul></ul><ul><ul><li>Can you do it on “company” time? </li></ul></ul><ul><ul><li>What ’s required? </li></ul></ul><ul><ul><li>What ’s the governance? </li></ul></ul><ul><li>Responsiveness </li></ul><ul><ul><li>How response is the OSS community to your projects ’ needs? </li></ul></ul>
  • 8. <ul><li>Help/Guidance </li></ul><ul><ul><li>Is the OSS community/project alive? </li></ul></ul><ul><ul><li>How can you tell whether the project is alive? </li></ul></ul><ul><ul><li>How can you “follow the rainbow” to the OSS pot of gold? </li></ul></ul><ul><li>Interaction </li></ul><ul><ul><li>What are the best practices for interacting with OSS communities? </li></ul></ul><ul><li>Implementation strategies </li></ul><ul><ul><li>Insulation: how do you insulate your project from OSS change? </li></ul></ul><ul><ul><li>Configuration Management: what are the important CM issues when using Open Source Software in your organization? </li></ul></ul><ul><li>Architectural strategies </li></ul><ul><ul><li>How to design your system to take advantage of OSS? </li></ul></ul><ul><li>Legal strategies </li></ul><ul><ul><li>How to avoid getting sued by some huge tech company? </li></ul></ul>
  • 9. The aforementioned OSS concerns are cross cutting against the whole clinical enterprise!
  • 10. <ul><li>Relates to: redistribution, intellectual property, contributing, legal strategies </li></ul><ul><li>There are tons of OSS approved licenses </li></ul><ul><ul><li>What’s the difference between them? </li></ul></ul><ul><li>The difference mostly has to do with </li></ul><ul><ul><li>Commercialization </li></ul></ul><ul><ul><li>Redistribution </li></ul></ul><ul><ul><li>Attribution </li></ul></ul>
  • 11. <ul><li>So you’ve built some awesome piece of clinical software </li></ul><ul><ul><li>And you’re wondering </li></ul></ul><ul><ul><li>What are my options for distributing it to </li></ul></ul><ul><ul><ul><li>Other PICUs? </li></ul></ul></ul><ul><ul><ul><li>Other Grant-funded projects? </li></ul></ul></ul><ul><ul><li>Any other collaborators? </li></ul></ul><ul><li>Question: what license are you going to choose? </li></ul><ul><ul><li>Hopefully one that supports redistribution under your own terms! </li></ul></ul><ul><li>How to redistribute the software? </li></ul><ul><ul><li>Requires infrastructure </li></ul></ul><ul><ul><ul><li>Who’s going to set it up? </li></ul></ul></ul>
  • 12. <ul><li>Should you organization stand up its own? </li></ul><ul><li>Where should you go? </li></ul>
  • 13. <ul><li>Start out with Incubation </li></ul><ul><li>Grow community </li></ul><ul><li>Make releases </li></ul><ul><li>Gain interest </li></ul><ul><li>Diversify </li></ul><ul><li>When the project is ready, graduate into </li></ul><ul><ul><li>Top-Level Project (TLP) </li></ul></ul><ul><ul><li>Sub-project of TLP </li></ul></ul><ul><li>Increasingly, Sub-projects are discouraged compared to TLPs </li></ul>
  • 14. <ul><li>Apache is a meritocracy </li></ul><ul><ul><li>You earn your keep and your credentials </li></ul></ul><ul><li>Start out as Contributor </li></ul><ul><ul><li>Patches, mailing list comments, etc. </li></ul></ul><ul><ul><li>No commit access </li></ul></ul><ul><li>Move onto Committer </li></ul><ul><ul><li>Commit access, evolve the code </li></ul></ul><ul><li>PMC Members </li></ul><ul><ul><li>Have binding VOTEs on releases/personnel </li></ul></ul><ul><li>Officer (VP, Project) </li></ul><ul><ul><li>PMC Chair </li></ul></ul><ul><li>ASF Member </li></ul><ul><ul><li>Have binding VOTE in the state of the foundation </li></ul></ul><ul><ul><li>Elect Board of Directors </li></ul></ul><ul><li>Director </li></ul><ul><ul><li>Oversight of projects, foundation activities </li></ul></ul>
  • 15. <ul><li>Project Proposal </li></ul><ul><ul><li>Accepted? Get going! </li></ul></ul><ul><li>No foundation-wide oversight </li></ul><ul><li>Tons of dormant projects with no communities of interest </li></ul><ul><li>Goal is to host infrastructure and host technologies </li></ul><ul><li>Goal is not to build communities </li></ul><ul><li>No foundation-wide rules or guidelines for committership or for project management </li></ul><ul><ul><li>Dealt with locally by the progenitor of the project </li></ul></ul><ul><ul><li>Can lead to BDFL (benevolent dictator for life) syndrome </li></ul></ul><ul><li>No foundation-wide license requirements </li></ul><ul><ul><li>BSD, GPL(v2, v3), MIT, LGPL, etc all allowed </li></ul></ul>
  • 16. <ul><li>FTR, there are tons of concerns here </li></ul><ul><ul><li>Should the ecosystem impose license restrictions? </li></ul></ul><ul><ul><ul><li>Only support license X or Y? </li></ul></ul></ul><ul><ul><li>What are the redistribution policies? </li></ul></ul><ul><ul><li>What ’s the community? </li></ul></ul><ul><ul><li>What ’s the IP? </li></ul></ul><ul><ul><li>What ’s the infrastructure support? </li></ul></ul><ul><ul><li>Is it a foundation with rules, or just free for all? </li></ul></ul><ul><li>Elephant in the room: What is the exposure? How many people are going to community C and are going to see your software and perhaps want to use it, improve it, file bugs against it, file patches, etc.? </li></ul><ul><li>Where/how does this matter to you? </li></ul><ul><ul><li>Standing up our own OSS ecosystem may make sense for large, coarse-grained federations </li></ul></ul><ul><ul><li>A LOT more difficult to justify OTOH, for fine grained components, and module reuse </li></ul></ul>
  • 17. <ul><li>How do you want to have your open source software project run in the open? </li></ul><ul><ul><li>Do you expect folks to come to you and only file bugs? </li></ul></ul><ul><ul><ul><li>Then you and your team are the only ones who can fix them? </li></ul></ul></ul><ul><ul><ul><li>Then you and your team are the only ones who can release updates? </li></ul></ul></ul><ul><ul><ul><li> ” Help Desk” open source project </li></ul></ul></ul><ul><ul><ul><li>Examples: Sourceforge.net, Google Code, etc. </li></ul></ul></ul><ul><ul><li>Do you expect to grow a community of interest where volunteers actively engage in software development? </li></ul></ul><ul><ul><ul><li>Are volunteers empowered to pick up a shovel and help dig the hole? </li></ul></ul></ul><ul><ul><ul><li>Can volunteers (including your own paid employees) file issues? </li></ul></ul></ul><ul><ul><ul><li>Do you want to give the community a stake/vote in the overall process? </li></ul></ul></ul><ul><ul><ul><li> “ Community Building” open source project </li></ul></ul></ul><ul><ul><ul><li>Examples: Apache Software Foundation, Eclipse Foundation, etc. </li></ul></ul></ul>
  • 18. <ul><li>Working on common software </li></ul><ul><ul><li>Measured not in terms of what center contributor works for, but in terms of </li></ul></ul><ul><ul><ul><li>Number of patches contributed (high quality) </li></ul></ul></ul><ul><ul><ul><li>Mailing list questions answered </li></ul></ul></ul><ul><ul><ul><li># of releases made, or helped with </li></ul></ul></ul><ul><ul><ul><li>Tests written </li></ul></ul></ul><ul><ul><ul><li>Documentation added </li></ul></ul></ul><ul><ul><li>Take the politics out of it and just work on “core” common code of mutual interest </li></ul></ul><ul><li>Deciding on the right redistribution mechanism and license </li></ul><ul><ul><li>Apache Software Foundation and ALv2 provide openness and ability for center-local redistribution, commerciality and other decisions (for internal distributions and beyond) </li></ul></ul>
  • 19. <ul><li>Centers can similarly (if they so choose) have their own customizations/distributions of OSS </li></ul><ul><ul><li>CHLA VPICU’s FooBar powered by Apache Hadoop </li></ul></ul><ul><ul><li>Seattle Children’s Hospital’s Baz built on Apache Pivot powered by Linux </li></ul></ul><ul><li>Example: NASA protects its marks through the New Technology Report process </li></ul><ul><ul><li>Uncover marks </li></ul></ul><ul><ul><li>Uncover potential patents </li></ul></ul><ul><ul><li>License/etc., as appropriate </li></ul></ul><ul><ul><li>We see this less on the ground side than we do with the flight </li></ul></ul><ul><ul><li>Mostly NASA wide, but some center specifics (e.g., Caltech) </li></ul></ul><ul><li>Takeaway: the answer to “who owns it” is still “the Center” or “the project” who initiated the software development, with or without OSS. OSS may have its own restrictions/rules, so need to be wary of that (recall copyleft syndrome) </li></ul>
  • 20. <ul><li>OSS communities are built around “contributions” </li></ul><ul><ul><li>But what does it mean to contribute? </li></ul></ul><ul><li>Mailing list help/discussions </li></ul><ul><ul><li>Yes those are contributions </li></ul></ul><ul><li>Reporting/filing bugs and new feature improvements </li></ul><ul><ul><li>Yes those are contributions </li></ul></ul><ul><li>Writing documentation and user guides </li></ul><ul><ul><li>Yes those are contributions </li></ul></ul><ul><li>Volunteering to make releases </li></ul><ul><ul><li>Yes those are contributions </li></ul></ul><ul><li>Positively contributing towards the evolution of the project with your thoughts and ideas </li></ul><ul><ul><li>Yes those are contributions </li></ul></ul><ul><li>NOTE: What did I leave out? </li></ul>
  • 21. <ul><li>Yes yes, code is important (but not the only contribution) </li></ul><ul><li>How should you go about your code contributing process to open source? </li></ul><ul><li>Relates to: “Help Desk” versus Community </li></ul><ul><li>Do you want the members of your project to be the only folks who can actual touch the source code of your OSS project? </li></ul><ul><ul><li>Only bug reports? </li></ul></ul><ul><ul><li>How “open” are you? </li></ul></ul><ul><ul><li>How “open” do you want to be? </li></ul></ul><ul><li>Do you want to accept code contributions from the community? </li></ul><ul><ul><li>Patches? </li></ul></ul><ul><ul><li>Allow community members to become “committers” (assist in the development of the code?) </li></ul></ul><ul><ul><li>RTC versus CTR </li></ul></ul>
  • 22. <ul><li>Measure of a “healthy” community </li></ul><ul><li>Does your patch sit? </li></ul><ul><li>Do your mailing list questions go unanswered? </li></ul><ul><li>Is the project electing new “committers” (if it’s in community mode)? </li></ul><ul><li>How should your group decide whether or not an OSS project you want to use is responsive? </li></ul><ul><li>How should your group decide how responsive it will be ? </li></ul><ul><li>Heavily influenced by: </li></ul><ul><ul><li>Community mode: “Help desk” versus “Community” </li></ul></ul>
  • 23. <ul><li>Using Open Source Software is different than producing software intended for distribution in open source </li></ul><ul><ul><li>Either way: what’s your strategy for getting help? </li></ul></ul><ul><ul><li>It used to be: you can’t rely on OSS for any “real time” support </li></ul></ul><ul><ul><li>Not anymore: companies stood up “around” OSS technology, dedicated to providing support </li></ul></ul><ul><ul><ul><li>Apache Hadoop: Cloudera, Hortonworks, EMC, Netapp, MapR </li></ul></ul></ul><ul><ul><ul><li>Apache Solr/Lucene: Lucid Imagination </li></ul></ul></ul><ul><ul><ul><li>Apache Cassandra: Riptano </li></ul></ul></ul><ul><ul><ul><li>Apache Maven: Sonatype </li></ul></ul></ul><ul><ul><ul><li>… others? </li></ul></ul></ul><ul><li>How good is the documentation for the OSS Project? </li></ul><ul><ul><li>Healthy wiki? </li></ul></ul><ul><ul><li>Healthy “cook books”? </li></ul></ul><ul><ul><li>Is the documentation baked in or separate? </li></ul></ul><ul><ul><li>Javadocs (or equivalent) on all public methods? </li></ul></ul><ul><ul><li>Use cases? </li></ul></ul>
  • 24. <ul><li>Build expertise and intellectual capital in existing open source technology </li></ul><ul><ul><li>If you are pulling it in and using it </li></ul></ul><ul><ul><li>Involves: “Community” model, but also works in “Help Desk” </li></ul></ul><ul><ul><li>Involves: active participation </li></ul></ul><ul><ul><li>Involves: friendly license (especially if you want to redistribute) </li></ul></ul><ul><li>If you are building your own technology that you want to put into open source </li></ul><ul><ul><li>Others may “help” you </li></ul></ul><ul><ul><li>Solve challenges at ZERO cost to you (well not ZERO but minimal) </li></ul></ul><ul><ul><li>Free cycles of interest </li></ul></ul>
  • 25. <ul><li>Case Study: Mailing lists communications* </li></ul>* Taken from: http://wiki.apache.org/nutch/Becoming_A_Nutch_Developer
  • 26. <ul><li>Mailing list interaction very important </li></ul><ul><ul><li>Most immediate feedback you get when contributing to open source, and also when creating your own open source project </li></ul></ul><ul><ul><li>Is the biggest thing that turns people away to start out with </li></ul></ul><ul><ul><li>“ who are these nerds and why don’t they have any manners?” </li></ul></ul><ul><ul><li>It ’s all about “learning” their “language” </li></ul></ul><ul><ul><ul><li>Sure, the cost may be high in terms of ego and attitude, but the reward (free work!) is well worth it </li></ul></ul></ul><ul><li>Following and understanding the practices of the OSS project are hugely important </li></ul><ul><ul><li>Know the license for an OSS product </li></ul></ul><ul><ul><li>Know whether they are “community” versus “help desk” </li></ul></ul><ul><ul><li>Know its history </li></ul></ul><ul><ul><li>Read its documentation </li></ul></ul><ul><ul><li>Be informed! </li></ul></ul><ul><li>Danger: thinking the OSS community is your personal helpdesk (or vice versa, you are its) </li></ul>
  • 27. <ul><li>How to design for open source? </li></ul><ul><li>Extension points </li></ul><ul><ul><li>Places in your code for “plug ins” </li></ul></ul><ul><ul><li>Plugins should be well documented </li></ul></ul><ul><ul><ul><li>Public facing “ javadoc ” (or similar) </li></ul></ul></ul><ul><ul><ul><li>“ Cookbooks” for integrating </li></ul></ul></ul><ul><ul><ul><li>Wiki pages </li></ul></ul></ul><ul><ul><ul><li>Baked in documentation </li></ul></ul></ul><ul><li>Use of shared component marketplace </li></ul><ul><ul><li>Many times PL specific </li></ul></ul><ul><ul><li>PyPI – Python </li></ul></ul><ul><ul><li>Maven Central/Ibiblio – Java </li></ul></ul><ul><ul><li>CPAN – Perl </li></ul></ul><ul><ul><li>STL, GNU, Autoconf, Make, etc. – C/C++ </li></ul></ul><ul><ul><li>YMMV, some are </li></ul></ul><ul><ul><ul><li>Webified, have package metadata, searchable, etc. </li></ul></ul></ul>
  • 28. <ul><li>Don ’t expect to use Haskel and have a huge OSS community there to assist you </li></ul><ul><li>Some modern active OSS languages </li></ul><ul><ul><li>Python </li></ul></ul><ul><ul><li>Perl </li></ul></ul><ul><ul><li>Ruby </li></ul></ul><ul><ul><li>Java </li></ul></ul><ul><li>Don ’t just be a consumer, be a producer </li></ul><ul><ul><li>Pick up a shovel and help dig the hole </li></ul></ul><ul><ul><li>Instead of overlooking the OSS community and telling them how the hole should be dug to meet your needs </li></ul></ul><ul><ul><li>Will help you get needed OSS feedback for your technology </li></ul></ul>
  • 29. <ul><li>Understand patent law </li></ul><ul><ul><li>Or pay people to understand it for you </li></ul></ul><ul><li>Understand OSS licenses and what you sign up for when you use relevant technologies and their licenses </li></ul><ul><li>Look for open APIs and open specs </li></ul><ul><ul><li>Understand what “open” means </li></ul></ul><ul><li>Vendor lock in </li></ul><ul><ul><li>Try to avoid it through the use of all the techniques of OSS which we ’ve discussed </li></ul></ul><ul><li>Engage the community and understand what ’s “really” free an what isn’t </li></ul><ul><li>Get legal ’s buy-in </li></ul><ul><ul><li>Don ’t insulate them </li></ul></ul>
  • 30. <ul><li>Understand “marks” </li></ul><ul><ul><li>Trademarks </li></ul></ul><ul><ul><li>Their implication to patents </li></ul></ul><ul><li>What will your agency support in terms of licensing? </li></ul><ul><ul><li>Center specific </li></ul></ul><ul><ul><li>Depends on IP, export control, ITAR, compliance, commercialization </li></ul></ul><ul><ul><li>If you make it through all of the above and the software is cleared for release, you really are in the driver ’s seat </li></ul></ul><ul><ul><ul><li>No agency wide guidelines </li></ul></ul></ul><ul><ul><ul><li>Most or all communities allowed </li></ul></ul></ul><ul><ul><ul><li>Most or all OSS approved licenses allowed </li></ul></ul></ul><ul><li>Is there a Contributor License Agreement (CLA) or Corporate Contributor License Agreement (CCLA) to sign? </li></ul><ul><ul><li>What are its implications? </li></ul></ul>
  • 31. <ul><li>“ Something like the Apache foundation is the best place for released government software. A previous attempt at release and public distribution via a private company was a truly dismal failure. OpenPBS (portable batch system) is supposed to be available to anyone that asks. However when you do ask a sales rep strings you along for more than a month trying to sell you something that they can&apos;t actually assure you will fit your requirements (and is no longer under development) even when the free one is documented as doing so. It was a truly stupid waste of the salesperson&apos;s time and mine that would have exceeded the price of providing the file for download or sending by email by several orders of magnitude and generated a lot of ill will. I&apos;ll go as far as saying it was blatant false advertising using a government funded open source product to do a bait and switch to try to sell me an unmaintained product they picked up in a corporate take over. My experience appears to have been identical to that of many that attempted to obtain this government funded open source software that NASA had declared was available for anyone. Eventually due to this open source project becoming closed the project just had to fork and the compatible Torque batch system was developed by people that had actually get hold of the original OpenPBS .” – Slashdot user comment </li></ul>
  • 32. <ul><li>Originally funded by NASA to focus on </li></ul><ul><ul><li>distributed science data system environments </li></ul></ul><ul><ul><li>science data generation </li></ul></ul><ul><ul><li>data capture, end-to-end </li></ul></ul><ul><ul><li>Distributed access to science data repositories by the community </li></ul></ul><ul><li>Entered the Apache incubator program in January 2010 </li></ul><ul><ul><li>First Apache project we are aware of originating from a NASA Lab </li></ul></ul><ul><li>Graduated to Apache Top Level Project in November 2010 </li></ul><ul><li>Used for a number of science data system activities in planetary, earth, biomedicine, astrophysics and pediatric intensive care </li></ul><ul><ul><li>The basis of our joint CHLA-JPL NLM project data management system </li></ul></ul>http://oodt.apache.org
  • 33. <ul><li>Division of Labor Avoid making one component the workhorse, configurable </li></ul><ul><li>Technology Independence Guard against unexpected changes in the technology landscape </li></ul><ul><li>Metadata as a first-class citizen Descriptions of resources come in handy </li></ul><ul><li>Separation of software and data models Allow each to evolve independently </li></ul><ul><li>Modular, domain-agnostic Pick and choose from adaptable components with defined interfaces </li></ul>
  • 34. <ul><li>Software Components </li></ul><ul><ul><li>Catalog/Archive Services – data mgmt/workflow </li></ul></ul><ul><ul><li>Product Services – access/transformation of data </li></ul></ul><ul><ul><li>Profile Services – discovery of resources/data </li></ul></ul><ul><ul><li>Query Services – query federation </li></ul></ul><ul><ul><li>Web Grid – web-based messaging to connect services </li></ul></ul><ul><li>Core Models </li></ul><ul><ul><li>Common XML representations as an interface to all components </li></ul></ul><ul><ul><li>Representation of distributed resources </li></ul></ul><ul><li>Domain Models </li></ul><ul><ul><li>These are specializations that sit on top of OODT </li></ul></ul>
  • 35. Common Specific Unique Rqmts. More Capabilities <ul><li>OODT Core Framework </li></ul><ul><li>Core Components/Models </li></ul><ul><li>Process Control Framework </li></ul><ul><li>Science/Mission/Project-Specific </li></ul><ul><li>OODT Extension </li></ul><ul><li>Discipline Models </li></ul><ul><li>Mission-Specific Services </li></ul>New capabilities/ improvements
  • 36. <ul><li>Code Sharing/Tech Transfer </li></ul><ul><ul><li>Could rapidly start constructing services and extending the core OODT model </li></ul></ul><ul><ul><li>Development sharing between institutions without a lot of paperwork and hassle </li></ul></ul><ul><li>Contributions back into OODT from CHLA </li></ul><ul><ul><li>Customizations from CHLA can be leveraged by other OODT projects including NASA missions, and NIH/NCI Early Detection Research Network </li></ul></ul><ul><li>Allowed focus on the architecture, rather than the implementation </li></ul><ul><ul><li>See Andrew Hart’s talk on Saturday </li></ul></ul>
  • 37. <ul><li>Open source is critical to the strategy of the organization </li></ul><ul><li>A great method of sustainability and longevity of software and community beyond organizational boundaries </li></ul><ul><li>Different licenses, communities, development practices </li></ul><ul><ul><li>Know what the differences mean </li></ul></ul><ul><li>Open Source/OODT have allowed great progress in our collaboration between JPL and CHLA </li></ul>
  • 38. <ul><li>Any questions? </li></ul><ul><li>THANK YOU! </li></ul><ul><ul><li>[email_address] </li></ul></ul><ul><ul><li>@chrismattmann on Twitter </li></ul></ul>
  • 39. MUCMD.ORG | SABAN RESEARCH CENTER | AUGUST 26-27 2011 Phone: 323.361.2557 Email: [email_address] Address: 4650 Sunset Blvd. MS#12 Los Angeles, CA 90027 Web: www.vpicu.org www.mucmd.org We will create a common information space for the international community of care givers providing critical care for children. Every critically ill child will have access to the Virtual PICU which will provide the essential information required to optimize their outcome.

×