Learn by doing

1,141 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,141
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Learn by doing

  1. 1. Learn By Doing AIC->CCAC Project Proposal Overview George Thomas, December 2009
  2. 2. This Presentation <ul><li>LBD = Acquisition 2.0 Example </li></ul><ul><li>Means to Ends, Assets – Legend </li></ul><ul><li>LBD Proposal Overview Model </li></ul><ul><li>LBD Design, Runtime, and Challenge Views (1 slide each) </li></ul><ul><li>Cloud Computing ‘Ends’ Model </li></ul><ul><li>Cloud Challenges </li></ul><ul><li>HHS + LBD 'Innovation Sandbox' </li></ul><ul><li>LBD High Level Project Plan </li></ul><ul><li>Project Plan Highlights </li></ul><ul><li>Conclusion </li></ul><ul><li>Backup Slides </li></ul>
  3. 3. LBD = Acquisition2.0 Example <ul><li>Start with the end in hand: </li></ul><ul><ul><li>← reverse the procurement process ← </li></ul></ul><ul><ul><ul><li>Instead of imagining (guessing) requirements for a solution you don't understand or have any experience with; </li></ul></ul></ul><ul><ul><li>Stand up a working system to 'discover the design' </li></ul></ul><ul><ul><ul><li>start with a clone of an Industry benchmark (EC2) and Gov best practice foundation (Nebula), consider this a 'Cloud Type' </li></ul></ul></ul><ul><ul><ul><li>determine if it meets all your (known :) requirements </li></ul></ul></ul><ul><ul><li>Develop requirements representing that system (!) </li></ul></ul><ul><ul><ul><li>use SNS to create (social media) SOW, SLA, Auth Pkg, etc. </li></ul></ul></ul><ul><ul><li>Exercise the procurement process, find the best contract vehicle </li></ul></ul><ul><ul><ul><li>creating a faux example for the learning organization (all of us ;) </li></ul></ul></ul><ul><li>Primary enablers: </li></ul><ul><ul><li>Open Source software and commodity hardware </li></ul></ul>
  4. 4. Means to Ends, Assets - Legend
  5. 5. LBD Proposal Overview Model
  6. 6. LBD Design View <ul><li>Demonstrate Acquisition 2.0 Goals </li></ul><ul><ul><li>Using OpenID enabled Social Media tools provided to create a Platform Specific Model based on Amazon as Reference Architecture and Eucalyptus as Reference Implementation </li></ul></ul><ul><ul><ul><li>Semantic Media Wiki for collaborative artifact development </li></ul></ul></ul><ul><ul><ul><li>Drupal for Social Network community management </li></ul></ul></ul><ul><ul><li>Use that Platform Specific Model to define the Cloud Type and as input to the Authorization Package and any other Acquisition related contract artifacts, including (but not necessarily limited to) a Statement of Work/Objectives, SLA, etc. </li></ul></ul><ul><li>The resulting Case Study provides; </li></ul><ul><ul><li>The Learning Organization an example (of a specific Cloud Type Procurement, Acquisition 2.0 style) to use as we proceed to define/authorize/procure other Cloud Types </li></ul></ul>
  7. 7. LBD Runtime View <ul><li>Stand up a 'Homogenous' Hybrid Cloud with minimal hardware </li></ul><ul><ul><li>Eucalyptus is; </li></ul></ul><ul><ul><ul><li>the foundation of the NASA Nebula Gov Best Practice Cloud and a clone of the Amazon EC2 Industry Benchmark Cloud </li></ul></ul></ul><ul><ul><ul><li>Commercial Open Source Software (COSS), and bundled in the Ubuntu's Enterprise Cloud (UEC) Linux distribution </li></ul></ul></ul><ul><ul><li>Hybrid because it enables both a Public and Private environment </li></ul></ul><ul><ul><ul><li>Homogeneous because the same software provides identical management capabilities across both environments </li></ul></ul></ul><ul><li>Use this Proof of Concept to; </li></ul><ul><ul><li>Provide IaaS and PaaS services initially, creating an Innovation Sandbox as a foundation to explore Agency Mission Specific and Shared Services </li></ul></ul>
  8. 8. LBD Challenge View <ul><li>Progressively Elaborating; </li></ul><ul><ul><li>Our understanding of the gap between concrete Platform Specific services (that are all we currently have) and abstract Platform Independent services (that we'd like to standardize to enhance portability and mitigate lock-in) </li></ul></ul><ul><ul><li>Ability to qualify and quantify business capabilities and technical features in the context of cost and risk </li></ul></ul><ul><li>Successively Refining; </li></ul><ul><ul><li>Our understanding of the elastic nature or 'burstability' of this specific cloud type, horizontally and vertically, within and across public and private environments </li></ul></ul><ul><ul><li>Capabilities offered in the Innovation Sandbox demonstrating service reuse network effects across multi-tenant agencies </li></ul></ul><ul><li>Help demand meet supply </li></ul><ul><ul><li>as an example for Gov/Ind scrutiny </li></ul></ul>
  9. 9. Cloud Computing ‘Ends’ Model
  10. 10. Cloud Challenges <ul><li>Each (public) Cloud Platform API amounts to a PSM with no (common) Open Standard PIM </li></ul><ul><ul><li>Typically interoperability is achieved, but portability isn't </li></ul></ul><ul><ul><ul><li>Interoperability may be manual or automated ($$-$$$$) </li></ul></ul></ul><ul><ul><ul><li>Often we choose not to re-engineer (migrate from one stack to another) unless we really have to have to ($$$-$$$$$$) </li></ul></ul></ul><ul><ul><li>Proprietary interoperable systems are 'heterogeneous' </li></ul></ul><ul><li>An Open Standard PIM is half of the Cloud Portability puzzle </li></ul><ul><ul><li>A goal expressed by the CCAC Standards WG </li></ul></ul><ul><li>This puzzle picture completes when all Cloud Platform API/PSM are derived from this Open Standard PIM </li></ul><ul><ul><li>This is extraordinarily difficult and perhaps unrealistic </li></ul></ul><ul><li>So we're back to focusing on interoperability (??) </li></ul>
  11. 11. HHS + LBD ‘Innovation Sandbox’
  12. 12. LBD High Level Project Plan
  13. 13. LBD Project Plan Highlights <ul><li>Resources </li></ul><ul><ul><li>6 machines and 6 people </li></ul></ul><ul><ul><ul><li>From GSA and HHS (3 people and machines each) </li></ul></ul></ul><ul><ul><ul><ul><li>~ 3 months, but not FTE </li></ul></ul></ul></ul><ul><ul><ul><li>KSA’s: LAMP/JEE, UML, Technical Writing, Contracting (SOW, TEB) and Project Management experience </li></ul></ul></ul><ul><li>Milestones </li></ul><ul><ul><li>CCAC ESC ‘greenlight’ </li></ul></ul><ul><ul><li>HHS and GSA (hardware/software/human) resources </li></ul></ul><ul><ul><li>Acquisition Package </li></ul></ul><ul><ul><ul><li>HoHy Cloud Type environment specs </li></ul></ul></ul><ul><ul><li>Assessment Package </li></ul></ul><ul><ul><ul><li>Mission App deploy/test findings </li></ul></ul></ul>
  14. 14. Conclusion <ul><li>Win/Win/Win/Win/Win/Win/… </li></ul><ul><ul><li>OMB </li></ul></ul><ul><ul><ul><li>Helps Cloud Provider supply meet Agency Mission demand </li></ul></ul></ul><ul><ul><li>CCAC WG’s </li></ul></ul><ul><ul><ul><li>Refines mission and enhances linkages </li></ul></ul></ul><ul><ul><li>GSA </li></ul></ul><ul><ul><ul><li>Acquisition2.0 example, exercises existing vehicles </li></ul></ul></ul><ul><ul><li>HHS </li></ul></ul><ul><ul><ul><li>Standard Segment Solution/Technology Architecture </li></ul></ul></ul><ul><ul><li>NASA </li></ul></ul><ul><ul><ul><li>Elaboration and differentiation of existing offerings </li></ul></ul></ul><ul><ul><li>AIC </li></ul></ul><ul><ul><ul><li>Adds value to OMB, CCAC, GSA, HHS, NASA… </li></ul></ul></ul>
  15. 15. Thanks For Your Consideration! <ul><li>http://xri.net/=george.thomas </li></ul><ul><ul><li>HHS Technical Architect </li></ul></ul><ul><ul><ul><li>CTO Council member </li></ul></ul></ul><ul><ul><ul><li>Innovation Council member </li></ul></ul></ul><ul><ul><li>Federal CIO Council </li></ul></ul><ul><ul><ul><li>AIC Services Subcommittee co-chair </li></ul></ul></ul><ul><ul><ul><li>CCAC member </li></ul></ul></ul><ul><ul><li>Graduate School SOA Faculty Instructor </li></ul></ul><ul><ul><li>W3C eGov IG Invited Expert </li></ul></ul><ul><ul><li>OMG GovDTF Steering Committee member </li></ul></ul>
  16. 16. Backup Slides (14 total) <ul><li>Kinds of Ends – Legend, 1 slide </li></ul><ul><li>Cloud Computing Ends Overview Model, 1 slide (graphic) </li></ul><ul><li>What the Cloud Computing Ends Model says, 3 slides </li></ul><ul><li>Ends Concepts Elaboration, 2 slides </li></ul><ul><li>Means to Ends, Assets – Icon Legend, 1 slide </li></ul><ul><li>Means to Ends, Assets – Prose Legend, 1 slide </li></ul><ul><li>LBD Project Overview Model, 1 slide (graphic) </li></ul><ul><li>What the Learn By Doing Project Proposal Model says, 3 slides </li></ul><ul><li>References, 1 slide </li></ul>
  17. 17. Kinds of Ends - Legend <ul><li>Vision:: the possibly unattainable but ultimate desired outcome, the best end we can imagine, regardless of how it can/can't be achieved </li></ul><ul><li>Goal :: a more narrowly focused desired outcome that we'd like to achieve that amplifies the Vision </li></ul><ul><ul><li>Goal 1 amplifies Vision and includes Goal 2 </li></ul></ul><ul><ul><li>Goal 2 indirectly amplifies the Vision, since Goal 1 includes it </li></ul></ul><ul><li>Objective :: a desired output that quantifies a Goal with some measurement or deliverable </li></ul><ul><ul><li>Objective 1 quantifies Goal 2 and includes Objective 2 </li></ul></ul><ul><ul><li>Objective 2 also quantifies Goal 2, since Objective 1 includes it </li></ul></ul>
  18. 18. Cloud Computing Ends Overview Model
  19. 19. Ends Overview Model Prose, 1 of 3 <ul><li>Vision::GovCloud </li></ul><ul><ul><li>A heterogeneous hybrid enabling Agencies to easily procure and compose (infrastructure, platform and software) secure services from multiple (public and private) providers </li></ul></ul><ul><li>Goal::Cross Agency </li></ul><ul><ul><li>Demand will meet supply when all these common agency goals are met </li></ul></ul><ul><ul><li>includes other Goals:: </li></ul></ul><ul><ul><ul><li>Efficient, Effective, Agency Specific </li></ul></ul></ul><ul><li>Goal::Agency Specific </li></ul><ul><ul><li>A narrower set of mission specific agency goals </li></ul></ul><ul><li>Both Goals amplify Vision::GovCloud </li></ul>
  20. 20. Ends Overview Model Prose, 2 of 3 <ul><li>Objective::Data Centers (we can count) </li></ul><ul><ul><li>quantifies Goal::Efficient and Goal::Effective </li></ul></ul><ul><ul><li>includes other Objectives:: </li></ul></ul><ul><ul><ul><li>Infr (Infrastructure) Services (IaaS), which includes Platform Services (PaaS), which includes Shared Services </li></ul></ul></ul><ul><ul><ul><ul><li>Shared Services includes Infr Services </li></ul></ul></ul></ul><ul><ul><ul><li>(we can count/access/reuse/qualify all the service capabilities offered) </li></ul></ul></ul><ul><li>Goal::Efficient includes Goal::Green </li></ul><ul><li>Objective::SWAP (Space, Watts & Performance) quantifies Goal:: Green and includes Objective::RAS (Reliability, Accessiblity, Serviceability) </li></ul><ul><li>Objective::Mission Services quantifies Goal::Agency Specific and Goal::Agile and includes Objective::Shared Services </li></ul>
  21. 21. Ends Overview Model Prose, 3 of 3 <ul><li>Goal::Effective includes Goal:: </li></ul><ul><ul><li>Secure, Scalable, Portable, Interoperable </li></ul></ul><ul><ul><li>Objective::Incidents quantifies Goal::Secure and includes Objective:: Multi-tenant </li></ul></ul><ul><ul><li>Objective::Elastic quantifies Goal::Scalable and includes Objective::Commodity </li></ul></ul><ul><ul><li>Objective::PIM (Platform Independent Model) quantifies Goal::Portable and includes Objective::PSM (Platform Specific Model) </li></ul></ul><ul><ul><li>Objective::RA (Reference Architecture) quantifies Goal::Interoperable and includes Objective::Open Standards </li></ul></ul><ul><ul><li>Objective::RI (Reference Implementation) quantifies Goal::Agile and includes Objective::Open Source </li></ul></ul><ul><li>Objective::PSM includes Objective::RA which includes Objective::RI </li></ul>
  22. 22. Ends Concepts Elaboration, 1 of 2 <ul><li>A Platform Independent Model (PIM) is an abstract specification of a system structure and behavior that is (technology) language and platform independent </li></ul><ul><ul><li>An Application Programming Interface (API) is a subset of a PIM that defines software functionality </li></ul></ul><ul><ul><li>An 'Open API' is a specification of proprietary functionality that is published and accessible on the Web </li></ul></ul><ul><ul><li>An '(Open) Standards based API' is a specification of proprietary functionality expressed using design and/or implemented using runtime standards that are defined by any (A-123 defined) Voluntary Consensus Standards Organization (VCSO) </li></ul></ul><ul><ul><li>An 'Open Standard API' is where the functionality is standardized and managed by any VCS </li></ul></ul>
  23. 23. Ends Concepts Elaboration, 2 of 2 <ul><li>A Platform Specific Model (PSM) is a concrete API that uses specific technology languages and platforms bound to specific network and application protocols and data representations </li></ul><ul><li>A Reference Architecture (RA) combines functional specifications with physical network and server topologies, incorporating all abstract and concrete representations </li></ul><ul><li>A Reference Implementation (RI) implements a PSM and can used to deploy a configured Platform Specific Instance (PSI) that be invoked (or used) on a particular network and server topology </li></ul><ul><ul><li>An Open Source RI is a shareable community 'gardened' component in source form that can recompiled/reconfigured and reused (PSI) in any new environment - a tremendous impact on software procurement for pilot or production systems </li></ul></ul>
  24. 24. Means to Ends, Assets – Icon Legend
  25. 25. Means to Ends, Assets – Prose Legend <ul><li>An Org establishes these courses of action ; </li></ul><ul><ul><li>The daily operational Mission to make operative the Vision </li></ul></ul><ul><ul><li>Long term Strategies to channels effort towards Goals </li></ul></ul><ul><ul><li>Short term Tactics to channel effort towards Objectives </li></ul></ul><ul><li>Strategies define Offerings , but Tactics deploy Offerings and therefore Tactics implement Strategies </li></ul><ul><li>Offering1 requires a Software Resource and uses Offering2 , that provides a different Software Resource </li></ul><ul><ul><li>( Hardware Resource(s) used or provided are not shown, but can be simplistically aligned with Offerings ) </li></ul></ul><ul><li>Offering2 uses a bundled Content Resource and provides yet another Document Resource </li></ul>
  26. 26. LBD Project Overview Model
  27. 27. LBD Project Model Prose, 1 of 3 <ul><li>Strategy::Learning Organization enables Strategy::Acquisition 2.0 and are both a component of the plan for Mission::LBD (Learn By Doing) </li></ul><ul><ul><li>Tactic::Commercial Open Source Software (COSS); </li></ul></ul><ul><ul><ul><li>implements Strategy::Acquisition 2.0 </li></ul></ul></ul><ul><ul><ul><li>includes Tactic::Social Networking Software and Tactic::Industry Benchmark </li></ul></ul></ul><ul><ul><ul><li>enables Tactic::Gov Best Practice </li></ul></ul></ul><ul><ul><ul><li>and deploys Offering::Homogeneous Hybrid Proof of Concept (HoHy PoC) </li></ul></ul></ul><ul><ul><li>Tactic::Industry Benchmark and Tactic::Gov Best Practice both implement Strategy::Learning Organization </li></ul></ul>
  28. 28. LBD Project Model Prose, 2 of 3 <ul><li>Strategy::Acquisition 2.0 channels effort towards Goal::Better Buy </li></ul><ul><li>Strategy::Learning Organization channels effort towards Goal::Try Before You Buy (Try B4U Buy) </li></ul><ul><li>Tactic::Social Networking Software channels effort towards Objective::Cloud Type Reference Architecture, which; </li></ul><ul><ul><li>quantifies Goal::Better Buy and Goal::Case Study and </li></ul></ul><ul><ul><li>includes Objective ::Platform Specific - Independent Model Gap (PSM->PIM Gap), which; </li></ul></ul><ul><ul><ul><li>quantifies Goal::Case Study </li></ul></ul></ul><ul><li>Tactic::Gov Best Practice channels effort towards Objective::Cloud Type Reference Implementation, which; </li></ul><ul><ul><li>quantifies Goal::Innovation Sandbox and </li></ul></ul><ul><ul><li>includes Objective::Burstability </li></ul></ul>
  29. 29. LBD Project Model Prose, 3 of 3 <ul><li>Strategy::Learning Organization defines Offering::Homogenous Hybrid Proof of Concept that requires Resource::Ubuntu Enterprise Cloud, and uses ; </li></ul><ul><ul><li>Offering::Private Java Enterprise Edition Virtual Appliance and Offering::Public Java Enterprise Virtual Appliance, that provides ; </li></ul></ul><ul><ul><ul><li>Resource::Glassfish Application Server and Resource::MySQL RDBMS </li></ul></ul></ul><ul><ul><li>Offering::Public Linux Apache MySQL PHP/Python (LAMP) Virtual Appliance, that provides ; </li></ul></ul><ul><ul><ul><li>Resource::Drupal Content Management system, Resource::Semantic MediaWiki (SMW), and Resource::MySQL RDBMS </li></ul></ul></ul><ul><ul><ul><li>and uses a Resource::Acquisition Package, that provides Resource::Authorization Package and Resource::Cloud Type Statement of Work / Statement of Objectives </li></ul></ul></ul>
  30. 30. References <ul><li>Business Motivation Model (Open Standard) </li></ul><ul><li>Better Buy Project (Acquisition 2.0 effort) </li></ul><ul><li>Eucalyptus (Amazon EC2 clone, Commercial Open Source) </li></ul><ul><li>Ubuntu Enterprise Cloud (Commercial Open Source) </li></ul><ul><li>NASA Nebula (Government Best Practice) </li></ul><ul><li>Amazon EC2 (Industry Benchmark) </li></ul><ul><li>Semantic MediaWiki (Commercial Open Source Social Media) </li></ul><ul><li>Drupal (Commercial Open Source Content Mgmt and Social Media) </li></ul><ul><li>Glassfish (Java Enterprise Edition Reference Implementation) </li></ul><ul><li>MySQL (Commercial Open Source RDBMS) </li></ul>

×