Jump to: navigation, search

Difference between revisions of "Training-manuals"

Line 146: Line 146:
 
* karma greater than Y
 
* karma greater than Y
  
−
Last edit {{REVISIONID}} by {{REVISIONUSER}} on date/time {{REVISIONTIMESTAMP}}
+
== Last edit {{REVISIONID}} by {{REVISIONUSER}} on date/time {{REVISIONTIMESTAMP}} ==
−
Core author [[User:Sarob|seanrob]]  23:11, 17 July 2013 (UTC)
+
== Core author [[User:Sarob|seanrob]]  ==

Revision as of 23:16, 17 July 2013

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 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
  • openstack-docs refactoring https://wiki.openstack.org/wiki/Blueprint-restructure-documentation: as of 15jul2013, the impact will be minimal. colin and sean will continue monitor
  • 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 of the three teams:
  • core: attend weekly IRC meets, attend core sprints when called, through gerrit review bugs and patches
  • sarob, colinmcnamara, plus up to eight others
  • sub-core: work through sub-core sprints by checking out book chapters, fix bugs
  • sfbay hackathon team, and other user groups we can get to sign up
  • extended: walk through and use training-manuals, create bugs, provide content reviews
  • user groups, university, others?

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 structure xml details
  • bkXXX-ch000-preface
  • bkXXX-ch001-what-does-this-book-intend-to-teach
  • bkXXX-ch002-getting-started
  • bkXXX-ch050-YYY-assessment
  • book topics
  • openstack associate engineer
  • openstack operations engineer
  • openstack development engineer
  • openstack devOps architect

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

time - name - topics covered

  • 1 month - associate - general
  • 2.5 months - ops general - general, nova, glance
  •                          - ops specialization - swift, quantum, oslo, or cinder
  • 2.5 months - dev general - general, nova, glance
  •                          - dev specialization - nova, glance, swift, quantum, oslo, cinder
  • 6 months - devOps general - general, nova, glance
  •                          - devOps specializaton - nova, glance, swift, quantum, oslo, cinder
OpenStack Training Outline

Book openstack associate

  • source content
  • basic install-guide openstack-manual/doc/src/docbkx/basic-install/src
  • most of sections 1-12, 14-15
  • tag admin manual subsections to be included in the training manual
  • 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.
  • requirements for test
  • basic knowledge of core OpenStack components (Compute, Block, Network, Dashboard)
  • create an instance
  • understand conf and log files
  • understand basics of APIs and framework architecture
  • understand shared components
  • work off a single node openstack implementation
  • get on IRC, mailing lists
  • able to deploy applications to OpenStack clouds
  • able to leverage basic functions including pools IPs and multiple disks
  • able to deploy multi-tier applications to OpenStack clouds
  • advanced knowledge of OpenStack components including new and incubated projects
  • able to create complicated network topologies
  • able to leverage advanced application topologies

Book openstack operations engineer

  • source content
  • 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.
  • additional source material
  • deep understanding of nova and glance
  • deep understanding of one other core project;; swift, quantum, olso, or cinder
  • trace workflow
  • work off a three node openstack implementation, create a vagant/chef configuration
  • based on http://workstuff.tumblr.com/post/50911984233/some-tips-on-getting-started-with-vagrant-and-chef
  • understanding of core components interaction through APIs
  • deep understanding of core conf and log files
  • puppet/chef understanding
  • 5-10 scenarios to diagnose, hands on?

Book openstack development engineer

  • source content
  • 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.
  • include ideas from
  • upstream university work is focusing on this
  • deep understanding of APIs
  • commit code through git
  • karma greater than X

Book openstack devOps architect

  • source content
  • 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. This will make the person who passes very desirable as an employee.
  • code contribution, CI infrastructure time in, operations 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

Last edit 26338 by Sarob on date/time 20130717231619

Core author seanrob

Retrieved from "https://wiki.openstack.org/w/index.php?title=Training-manuals&oldid=26338"