Difference between revisions of "Training-manuals"
(→Core authors sarob and colinmcnamara) |
(→Book openstack associate) |
||
Line 71: | Line 71: | ||
== Book openstack associate == | == 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. | * 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. | ||
− | * source content | + | * source content: basic install-guide repo openstack-manual/doc/src/docbkx/basic-install/src |
− | : | + | :* basic-install_intro.xml |
+ | :* basic-install_controller.xml:section:basic-install_controller | ||
+ | ::* section:basic-install_controller-intro | ||
+ | ::* section:basic-install_controller-common | ||
+ | :::* section:controller-os | ||
+ | :::* section:controller-mysql | ||
+ | :::* section:controller-rabbitmq | ||
+ | ::* section:basic-install_controller-glance | ||
+ | ::* section:basic-install_controller-nova | ||
+ | ::* section:basic-install_controller-cinder | ||
+ | ::* section:basic-install_controller-quantum | ||
+ | ::* section:basic-install_controller-dashboard | ||
+ | :* basic-install_network.xml:section:basic-install_network | ||
+ | ::* section:basic-install_network-intro | ||
+ | ::* section:basic-network-common | ||
+ | ::* section:basic-install_network-services | ||
+ | ::* section:basic-install_network-operating | ||
+ | :* basic-install_compute.xml:section:basic-install_compute | ||
+ | ::* section:basis-install_compute-intro | ||
+ | ::* section:basis-install_compute-common | ||
+ | ::* section:basis-install_compute-nova | ||
+ | ::* section:basis-install_compute-quanum | ||
+ | :* basic-install_operate.xml | ||
+ | :* basic-install_conclusion.xml | ||
+ | |||
* requirements for test | * requirements for test | ||
:* basic knowledge of core OpenStack components (Compute, Block, Network, Dashboard) | :* basic knowledge of core OpenStack components (Compute, Block, Network, Dashboard) |
Revision as of 21:16, 25 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
Contents
- 1 Project requirements
- 2 Project dependancies / issues
- 3 Book structure
- 4 Overview of training structure (Self Paced and user group paced)
- 5 Book openstack associate
- 6 Book openstack operations engineer
- 7 Book openstack development engineer
- 8 Book openstack devOps architect
- 9 Last edit 27020 by Sarob on 20130725211633 (year+month+day+UTC hour+seconds)
- 10 training manuals core leaders sarob and colinmcnamara
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
- publishing location
- gerrit/jenkins files
- modules/openstack_project/files/jenkins_job_builder/config/manuals.yaml
- modules/openstack_project/files/zuul/layout.yaml
- web index file ...
- 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
- bk002-ch000-associate-preface
- bk002-ch001-associate-what-does-this-book-intend-to-teach
- bk002-ch002-associate-getting-started
- bk002-ch003-associate-general (three main core sections: general, nova, glance)
- bk002-ch004-associate-nova (specialization)
- bk002-ch005-associate-neutron (specialization)
- bk002-ch006-associate-swift (specialization)
- bk002-ch007-associate-glance (specialization)
- bk002-ch008-associate-cinder (specialization)
- bk002-ch009-associate-oslo (specialization)
- bk002-ch010-associate-assessment
- book topics
- openstack associate engineer
- openstack operations engineer
- openstack development engineer
- openstack devOps architect
- publish to
- docs.openstack.org/training as annegentle suggests OR
- by each release like docs.openstack.org/trunk/training, docs.openstack.org/grizzly/training
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
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.
- source content: basic install-guide repo openstack-manual/doc/src/docbkx/basic-install/src
- basic-install_intro.xml
- basic-install_controller.xml:section:basic-install_controller
- section:basic-install_controller-intro
- section:basic-install_controller-common
- section:controller-os
- section:controller-mysql
- section:controller-rabbitmq
- section:basic-install_controller-glance
- section:basic-install_controller-nova
- section:basic-install_controller-cinder
- section:basic-install_controller-quantum
- section:basic-install_controller-dashboard
- basic-install_network.xml:section:basic-install_network
- section:basic-install_network-intro
- section:basic-network-common
- section:basic-install_network-services
- section:basic-install_network-operating
- basic-install_compute.xml:section:basic-install_compute
- section:basis-install_compute-intro
- section:basis-install_compute-common
- section:basis-install_compute-nova
- section:basis-install_compute-quanum
- basic-install_operate.xml
- basic-install_conclusion.xml
- 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
- install-guide repo openstack-manual/doc/src/docbkx/openstack-install
- user-guide repo openstack-manual/doc/src/docbkx/openstack-user/src
- operations-guide https://github.com/openstack/operations-guide/tree/master/doc/src/docbkx/openstack-ops/src
- api programming https://github.com/openstack/api-site/tree/master/openstack-api-programming
- api quick start https://github.com/openstack/api-site/tree/master/api-quick-start/src/docbkx
- api reference https://github.com/openstack/api-site/tree/master/api-ref/src/docbkx
- 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
- most of operations guide sections 1-17, workbook scenarios to diagnose
- git basics, create scenarios from http://git-scm.com/book/en/Git-Basics
- reference Nova API reference http://docs.openstack.org/api/openstack-compute/2/content/
- referenece Glance API reference
- http://docs.openstack.org/api/openstack-image-service/1.0/content/
- requirements for test
- 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
- repo openstack-manuals/doc/src/docbkx/training-manuals
- operations-guide https://github.com/openstack/operations-guide/tree/master/doc/src/docbkx/openstack-ops/src
- https://github.com/openstack/nova/tree/master/doc/source/devref
- https://github.com/openstack/neutron/tree/master/doc/source/devref
- https://github.com/openstack/keystone/tree/master/doc/source
- https://github.com/openstack/cinder/tree/master/doc/source/devref
- https://github.com/openstack/glance/tree/master/doc/source
- https://github.com/openstack/swift/tree/master/doc/source
- https://github.com/openstack/horizon/tree/master/doc/source
- http://github.com/openstack/api-site - API Quick Start, API Reference page, and Programmers Guide for Compute API with Shell and Python
- http://github.com/openstack/compute-api - Compute Administration Guide
- http://github.com/openstack/database-api - Database Administration Guide
- http://github.com/openstack/identity-api - Identity Administration Guide
- http://github.com/openstack/image-api - Image Service Administration Guide
- http://github.com/openstack/object-api - Object Storage Administration Guide
- http://github.com/openstack/netconn-api - Networking Administration Guide
- http://github.com/openstack/volume-api - Block Storage Service Administration Guide
- https://github.com/openstack/operations-guide - Operations Guide
- 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
- http://redmine.upstream-university .org/projects/slides/repository/revisions/master/show/training
- http://www.slideshare.net/eyepv6/open-stack-summitsurvivingyourfirstcheckin
- http://www.slideshare.net/delapsley1/opensack-quantum-devstack-tutorial,
- http://www.slideshare.net/khinnu4u/developing-withdevstack
- upstream university work is focusing on this
- deep understanding of APIs
- commit code through git
- karma greater than X
- requirements for test
Book openstack devOps architect
- source content
- repo openstack-manuals/doc/src/docbkx/training-manuals
- 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