Latest revision as of 10:53, 9 July 2016

What is the Training Guides Project

The Training Guides project creates open source OpenStack training materials for use by OpenStack User Groups, Universities, and the OpenStack Upstream Training teams.

Quick Links

OpenStack Trainers Team https://wiki.openstack.org/wiki/Meetings/trainers
OpenStack Training Docs
  * Draft http://docs.openstack.org/draft/training-guides/
  * Icehouse (EOL) http://docs.openstack.org/icehouse/training-guides/
OpenStack Upstream Training http://docs.openstack.org/upstream-training
Training Guides Launchpad project page https://launchpad.net/openstack-training-guides
Training Guides source code https://git.openstack.org/cgit/openstack/training-guides/
OpenStack Training Labs https://wiki.openstack.org/wiki/Documentation/training-labs

Meeting Information

• The team meets weekly, here are the details
  • Meeting agenda
• weekly meeting history (weekly meeting history up to 8/2014)

Project Goals

• Aim/Goal (What does training guides provides):
  • Training Content mostly by HTML slides
  • Example scenarios and use cases
  • Quizzes
• Target Audience
  • OpenStack User Groups
  • Upstream Training/OpenStack Summit training
  • Universities
  • Self-paced training
• Support the OpenStack Documentation Program projects by cross posting content

Project Lead

• Matjaz Pancur/matjazp

Core Reviewer Responsibilities

• attend weekly IRC meets,
• attend core sprints when called,
• work through gerrit reviews of bugs and patches (Code Review Guidelines)
• Consistent reviews to training-guides project.
• Preference given to quality of reviews over quantity of reviews.
• Creating or maintaining a sub-project/section in the project (ex. Labs, Docs, Slides etc.)
• If it is required to give the core reviewership to the candidate (blockers ex. no one else can do the job better)
• Current Core Reviewers

Project Status

• Training Guides Heartbeat
• OpenStack docs mailing list history
• Some discussion on this etherpad with the results being moved to this wiki https://etherpad.openstack.org/p/training-guides-developing-topics

How To

Create a Bug

• Either by clicking the red bug in the upper right hand corner of the training-guides documentation http://docs.openstack.org/training-guides/content/associate-getting-started.html OR
• By creating the bug directly in launchpad https://bugs.launchpad.net/openstack-training-guides/+filebug

Training slides - Modules

• OpenStack getting started
  • what is, it's mission, other general info
  • conceptual architecture, basic concepts
  • logical architecture diagram with "core" projects
• Start a new VM with Horizon
• Start a new VM with CLI
• Dashboard (Horizon)
• What happens when you start a VM
• Compute service (Nova)
• Networking (Neutron)
• Image service (Glance)
• Identity service (Keystone)
• Block storage (Cinder)
• Object storage (Swift)

Old proposal: Structure of Materials

Book OpenStack Associate Guide

• 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)

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. May set aside some time for distro specific training.

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. May set aside some time for distro specific training.

Book openstack devOps architect

• 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.
• The Architect focuses on a specific OpenStack project as a specialization and becomes a working member of that project. The Architect training will be all about becoming a functioning member of the OpenStack open source community.
• speaking at user groups
• summit session submissions should all count towards karma/contribution
• Passing DevOps training would make the person desirable as an employee and a core contributor to any project

Last edit 127859 by Ian Y. Choi on 20160709105307 (year+month+day+UTC hour+seconds)