Difference between revisions of "Training-manuals"
Line 1: | Line 1: | ||
Blueprint https://blueprints.launchpad.net/openstack-manuals/+spec/training-manuals | Blueprint https://blueprints.launchpad.net/openstack-manuals/+spec/training-manuals | ||
− | weekly | + | weekly meeting agenda https://wiki.openstack.org/wiki/Meetings/training-manuals |
== Project requirements == | == Project requirements == |
Revision as of 20:22, 16 July 2013
Blueprint https://blueprints.launchpad.net/openstack-manuals/+spec/training-manuals weekly meeting agenda https://wiki.openstack.org/wiki/Meetings/training-manuals
Contents
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
Project dependancies / issues
- openstack-docs refactoring: 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, gerrit review bugs and patches
- sub-core: work through sub-core sprints by checking out book chapters, fix bugs
- extended: walk through and use training-manuals, create bugs, provide content reviews
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
structure
- openstack associate engineer
- openstack operations engineer
- openstack development engineer
- openstack devOps architect
openstack associate
- reference http://docs.openstack.org/grizzly/openstack-compute/admin/content/
- 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
- 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
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.
- reference http://docs.openstack.org/trunk/openstack-ops/content/
- most of sections 1-17, workbook scenarios to diagnose
- 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?
openstack development engineer
- 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
- compute API http://docs.openstack.org/api/openstack-compute/programmer/content/
- http://docs.openstack.org/developer/nova/devref/index.html
- upstream university work is focusing on this
- deep understanding of APIs
- commit code through git
- karma greater than X
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. 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