Jump to: navigation, search

Training-manuals

openstack-training docs http://docs.openstack.org/training-guides
Blueprint https://blueprints.launchpad.net/openstack-manuals/+spec/training-manuals
weekly meeting agenda https://wiki.openstack.org/wiki/Meetings/training-manuals
trello storyboard https://trello.com/board/openstack-training/51d6e5fee37248fd5b003de9
sfbay-openstack hackathon https://etherpad.openstack.org/sfbay-openstack

Project Goals

  • Provide a structured training program to enable skill development for maintaining, consuming, and contributing to OpenStack
  • Align to the OpenStack Foundation certification program
  • Increase accuracy and usability of documentation and training by engaging user groups and community members across the world
  • Increase the amount of skilled engineers and developers in the hiring pool for OpenStack operators and developers
  • Enable underrepresented / economically disadvantaged users groups and communities (Africa, Vietnam, Etc) to develop valuable and marketable skills.
  • We will be targeting the user group and university audiences first while partnering with commercial interests like Aptira. Commercial interests are encouraged to use and contribute to the project.
  • We aim to have as many commercial training programs use this project for the 'core' of their training. It will only improve the quality of the content while limiting the quantity to just the very most important bits.

Project Status

  • Currently an incubated project under OpenStack Manuals (PTL = Anne Gentle)
  • Currently focused - OpenStack Developer Course Launch

Project requirements

  • Reuse the openstack foundation manuals with some additional training specific pages
  • Target 80% doc reuse
  • Same process as existing manuals
  • Leave in space and time for distro specific training
  • Training material and lab work would all be based on refstack https://etherpad.openstack.org/RefStackBlueprint, but this work is still evolving

Project dependancies / issues

  • majority of the material will be stitched together from remote github repositories and the local openstack-manuals repository through xi:include statements through the gerrit build process
  • breakdown of task management
  • in launchpad, the blueprint will hold status and links back to bugs,
  • in launchpad bugs on the published documentation will be posted,
  • on this wiki page the project status and overview will be posted
  • in trello the story boards and sprints will be published and developed
  • breakdown of responsibilities
  • core: attend weekly IRC meets, attend core sprints when called, through gerrit review bugs and patches
  • community: work on submitting bugs, fixing bugs, and suggest new material. All are welcome to participate.

RST-XML Conversion automation

Blueprint here https://blueprints.launchpad.net/openstack-manuals/+spec/rst-xml-conversion

This code is used to convert devref project rst documentation into xml that the openstack manuals project can use. The Training-manuals sub-project will use xi:include statements so the converted xml becomes part of the training guides during build. The conversion script will live in the ./training-guide/sources sub directory of the training-manuals sub-project. The converted xml gets placed within ./training-guide/sources/<project> directories. The conversion script will be run at the same time as when the openstack-manuals repo updates are pulled. All 8 repositories will then be in the same state. This will allow the training manuals team to find xml content and include it with the training guides. If the source RST has a bug, then the RST source will be patched, and the XML will get the bug fix through the next run of the conversion script.

Code details (also in the comments of the script): The code must executed within ./openstack-manuals/doc/training-manuals/sources/. Requirement that pandoc-1.12.0.2 is installed on the local system and that the path to pandoc is part of the user profile. Find pandoc here http://johnmacfarlane.net/pandoc/installing.html. The code will automagically create the 7 'core' openstack repositories and convert the rst docs to xml. The script has four parts: create_repo, pull_repo_updates, convert_rst, and rst_xml_cleanup.

  • create_repo: clones the nova, glance, cinder, neutron, swift, keystone, oslo, and horizon repositories into the directory above openstack-manuals repository. It is assumed this is where repositories belong on the local system.
  • pull_repo_updates: Intended that all the local repositories are to be pulled for updates before starting a new branch.
  • convert_rst: use pandoc to convert the rst to docbook 4.5 xml. Copy over images as well.
  • rst_xml_cleanup: convert docbook 4.5 xml to docbook 5.0 along with some cleanup of poorly formatted tags.

Before the rst xml conversion results are accepted in their entirety, a first patch to openstack-manuals will only include the rst files from the cinder project.

  • the repo array contains only 'cinder'
  • maybe use xslt plus regex to go from 4.5 to 5.0

That patch is here ....

Book structure

  • each book needs an outline published inline below
  • each book needs goals that slightly overlap with the previous and next
  • 10 question quiz and 1 scenario at the end of each chapter
  • 40+ assessment broken down by each section/question representing a different chapter
  • hierarchy: set -> book -> chapter -> section
  • book topics
  • openstack associate engineer
  • openstack operator engineer
  • openstack developer engineer
  • openstack devOps architect
  • publish to docs.openstack.org/training-guides

Overview of training structure (Self Paced and user group paced)

time - name

  • 1 month - associate
  • 2.5 months - operator
  • 2.5 months - developer
  • 6 months - devOps

Book openstack associate

  • training would take 1 month self paced, (2) 2 week periods with a user group meeting, or 16 hours instructor led. Some time set aside for distro specific training.
  • basic knowledge of core OpenStack components (Compute, Block, Network, Dashboard)
  • for the rest see the associate guide online

Book openstack operations engineer

  • training would take 2.5 months self paced, (5) 2 week periods with a user group meeting, or 40 hours instructor led with 40 hours of self paced lab time. Some time set aside for distro specific training.
  • for the rest see the operator guide online

Book openstack development engineer

  • build on concepts from Operator training
  • combine how to contribute and working with CI guides into a developers guide
  • training would take 2.5 months self paced, (5) 2 week periods with a user group meeting, or 40 hours instructor led with 40 hours of self paced lab time. Some time set aside for distro specific training.
  • outline is here
  • sprint storyboard til 20 march 2014 is here

Book openstack devOps architect

  • Combination of Operator and Developer training
  • training would take 6 months or (12) 2 week periods with a user group meeting. 240 hours of self paced lab time.
  • Meant to be very hard to complete. Public contribution must be a considerable part of the work completed.
  • code contribution
  • CI infrastructure time in
  • implementation builds
  • contributions to answer
  • speaking at user groups
  • summit session submissions should all count towards karma/contribution
  • use TripleO for build/ops environment. include https://github.com/tripleo/incubator/blob/master/devtest.md
  • karma greater than Y
  • Passing DevOps training would make the person desirable as an employee.
  • Passing DevOps training would make the person desirable as a core contributor to any project

Last edit 46937 by Sarob on 20140328235647 (year+month+day+UTC hour+seconds)

training manuals core leaders sarob and colinmcnamara