OpenStack Training & Certifications


Published on

Presented by Foundation staff for discussion during the May 30, 2013 board meeting regarding OpenStack training and certifications.

  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

OpenStack Training & Certifications

  1. 1. Training & Certification Discussion
  2. 2. 2Background: The Foundation & Training‣  OpenStack Foundation Mission: Protecting, Empowering, and Promoting theOpenStack software and the community around it, including users, developers, andthe entire ecosystem‣  Education is a top Foundation priority for 2013, to lower barriers to adoption, createmore OpenStack experts, and grow the community‣  Jobs: There are 1000+ OpenStack related job openings worldwide‣  We believe training is one of the best paths to:§  Grow the community§  Close the jobs gap§  Drive adoption§  Build a common knowledge set that unifies the community’s efforts acrossdeployments§  Create new fans all over the world that share our values
  3. 3. 3Background: Training Ecosystem‣  The OpenStack ecosystem is already delivering dozens of training classes all over theworld today: San Francisco, London, San Antonio, Slovenia, Silicon Valley, France, NewZealand, Hungary, Hong Kong‣  The ecosystem has licensed marks under “Built for OpenStack” historically‣  To explore a more targeted program, we formed a working group of companies currentlyadministering training and community members to discuss how a new licensing programmight look
  4. 4. 4Background: Certification/Credentials‣  We also see growing interest in a credentialing program, as Stackers look togrow their careers‣  Credentialing programs have traditionally helped technology brands gaincredibility in the enterprise space and create long-term fans amongst engineersand admins (CCIE, RHCE, MCSE, LPI)‣  Think “OpenStack Certified Engineer”‣  The ecosystem is interested in offering credentials
  5. 5. 5Complications & Opportunities‣  The lack of training-specific requirements in the “Built for OpenStack” license means everytraining approach is potentially different‣  No common baseline will create detrimental knowledge and talent fragmentation‣  Different OpenStack-powered solutions (distributions, appliances, etc.) also create a needfor solution-specific training‣  There is value in a common baseline:§  Improves OpenStack brand meaning, value, growth, and protection§  A global pool of trained individuals who see the value of an open, interoperableplatform §  More value in “OpenStack skills” for those that bet careers on itThe Foundation has an opportunity to improve consistency and ensure the meaning of“OpenStack” and any credentials associated with it have long term value & meaning
  6. 6. 6The Proposed Approach1.  Create a new “OpenStack Training” logo licensing program for training businesses,with published guidelines & quality assurance measures2.  Develop set of baseline credentials covering universal “OpenStack Fundamentals.”Implement standard tests in partnership with ecosystem and manage database ofcertified professionals ‣  E.g. “OpenStack Certified Engineer”, “OpenStack Certified Administrator”3.  Encourage ecosystem to offer add-on, solution-specific courses and certifications,above the baseline credentials
  7. 7. 7Proposed Training Licensing ApproachProgram Goals & Approach‣  Generate awareness of the many OpenStack Training options in the ecosystemby creating a targeted co-marketing/licensing program ‣  Empower 3rd parties to promote OpenStack and spread OpenStack knowledgeglobally by licensing the marks for their use, and by making the program asfrictionless as possible. Training represents the bulk of the resourcerequirements and revenue opportunity.‣  Protect the OpenStack Brand by implementing quality control measuresApproach to Quality Control1.  Outline key topics/content courses should cover. Working group has started abasic outline2.  Foundation administered post-training student surveys and optional auditing3.  Measure % of students who go on to earn credentials (see next slide)
  8. 8. 8Proposed Credentialing Program ApproachProgram Goals & Approach‣  Help Stackers prove their expertise through the use of specific credentials‣  Close the knowledge gap and help fill jobs by accelerating training toward aspecific achievement‣  Protect the OpenStack Brand by implementing quality control measuresApproach to Quality Control1.  Develop a common set of baseline credentials to be used across the ecosystem2.  Develop a common set of tests to determine who qualifies for those credentialswith existing training partners and training working group3.  Over time, get feedback from employers to find out if credentialed candidatescome in with necessary skills for the job
  9. 9. 9Next Steps1.  Training logo/marketing program: Implement by Q3 20132.  Credential program: ‣  Continue to solicit feedback from students, employers, ecosystem‣  Develop list of credentials (e.g. “OpenStack Certified Engineer” and beyond)‣  Develop standardized tests in cooperation with ecosystem and establishedtesting centers‣  Target dates: Announce program Q3 2013, rollout Q1 2014