Fix broken master repo
Because of the new gating system (gate-training-guides-tox-slides), we need to
cleanup all existing RST files.
There is a small rendering problem with Landslide in the Upstream training
and all the Title slides (empty slides with only a Title). The check doesn't
like "empty" slides ("Document or section may not begin with a transition."),
Landslide deals with this by ignoring errors
(https://github.com/adamzap/landslide/issues/94), but our gating check does
not. I temporary changed all such slides to normal ones.
I also had to change training-guides/landslide.sh a bit (a quick hack so that
it works as expected).
Change-Id: I6c3ae06235e69c4a53741e74a5642d27083f4df0
This commit is contained in:
Matjaz Pancur
parent
b0226a11d7
commit
747227bb04
doc
training-guides
upstream-training
@ -4,7 +4,7 @@ Associate training guide
|
||||
Compute node quiz questions
|
||||
---------------------------
|
||||
|
||||
.. include:: ./associate-guide/notes/06-compute-node.rst
|
||||
.. include:: ./notes/06-compute-node.rst
|
||||
:start-after: begin-compute-nova-scheduler
|
||||
:end-before: end-compute-nova-scheduler
|
||||
|
||||
@ -16,7 +16,7 @@ Associate training guide
|
||||
Compute node quiz questions
|
||||
---------------------------
|
||||
|
||||
.. include:: ./associate-guide/notes/06-compute-node.rst
|
||||
.. include:: ./notes/06-compute-node.rst
|
||||
:start-after: begin-compute-queue
|
||||
:end-before: end-compute-queue
|
||||
|
||||
@ -28,7 +28,7 @@ Associate training guide
|
||||
Compute node quiz questions
|
||||
---------------------------
|
||||
|
||||
.. include:: ./associate-guide/notes/06-compute-node.rst
|
||||
.. include:: ./notes/06-compute-node.rst
|
||||
:start-after: begin-compute-default-scheduler
|
||||
:end-before: end-compute-default-scheduler
|
||||
|
||||
@ -40,7 +40,7 @@ Associate training guide
|
||||
Compute node quiz questions
|
||||
---------------------------
|
||||
|
||||
.. include:: ./associate-guide/notes/06-compute-node.rst
|
||||
.. include:: ./notes/06-compute-node.rst
|
||||
:start-after: begin-compute-filter-scheduler
|
||||
:end-before: end-compute-filter-scheduler
|
||||
|
||||
@ -52,7 +52,7 @@ Associate training guide
|
||||
Compute node quiz questions
|
||||
---------------------------
|
||||
|
||||
.. include:: ./associate-guide/notes/06-compute-node.rst
|
||||
.. include:: ./notes/06-compute-node.rst
|
||||
:start-after: begin-compute-scheduler-returns
|
||||
:end-before: end-compute-scheduler-returns
|
||||
|
||||
@ -64,7 +64,7 @@ Associate training guide
|
||||
Compute node quiz questions
|
||||
---------------------------
|
||||
|
||||
.. include:: ./associate-guide/notes/06-compute-node.rst
|
||||
.. include:: ./notes/06-compute-node.rst
|
||||
:start-after: begin-compute-classes-block-storage
|
||||
:end-before: end-compute-classes-block-storage
|
||||
|
||||
@ -76,7 +76,7 @@ Associate training guide
|
||||
Compute node quiz questions
|
||||
---------------------------
|
||||
|
||||
.. include:: ./associate-guide/notes/06-compute-node.rst
|
||||
.. include:: ./notes/06-compute-node.rst
|
||||
:start-after: begin-compute-persistent-volumes
|
||||
:end-before: end-compute-persistent-volumes
|
||||
|
||||
@ -88,30 +88,30 @@ Associate training guide
|
||||
Compute node quiz answers
|
||||
-------------------------
|
||||
|
||||
.. include:: ./associate-guide/notes/06-compute-node.rst
|
||||
.. include:: ./notes/06-compute-node.rst
|
||||
:start-after: begin-compute-answer-nova-scheduler
|
||||
:end-before: end-compute-answer-nova-scheduler
|
||||
|
||||
.. include:: ./associate-guide/notes/06-compute-node.rst
|
||||
.. include:: ./notes/06-compute-node.rst
|
||||
:start-after: begin-compute-answer-queue
|
||||
:end-before: end-compute-answer-queue
|
||||
|
||||
.. include:: ./associate-guide/notes/06-compute-node.rst
|
||||
.. include:: ./notes/06-compute-node.rst
|
||||
:start-after: begin-compute-answer-default-scheduler
|
||||
:end-before: end-compute-answer-default-scheduler
|
||||
|
||||
.. include:: ./associate-guide/notes/06-compute-node.rst
|
||||
.. include:: ./notes/06-compute-node.rst
|
||||
:start-after: begin-compute-answer-filter-scheduler
|
||||
:end-before: end-compute-answer-filter-scheduler
|
||||
|
||||
.. include:: ./associate-guide/notes/06-compute-node.rst
|
||||
.. include:: ./notes/06-compute-node.rst
|
||||
:start-after: begin-compute-answer-scheduler-returns
|
||||
:end-before: end-compute-answer-scheduler-returns
|
||||
|
||||
.. include:: ./associate-guide/notes/06-compute-node.rst
|
||||
.. include:: ./notes/06-compute-node.rst
|
||||
:start-after: begin-compute-answer-classes-block-storage
|
||||
:end-before: end-compute-answer-classes-block-storage
|
||||
|
||||
.. include:: ./associate-guide/notes/06-compute-node.rst
|
||||
.. include:: ./notes/06-compute-node.rst
|
||||
:start-after: begin-compute-answer-persistent-volumes
|
||||
:end-before: end-compute-answer-persistent-volumes
|
||||
|
||||
@ -8,22 +8,24 @@ Compute node quiz questions
|
||||
|
||||
1. **Which component determines which host a VM should launch on?**
|
||||
|
||||
#. nova-network
|
||||
#. queue
|
||||
#. nova-compute
|
||||
#. nova-console
|
||||
#. nova-scheduler
|
||||
#. nova-api
|
||||
#. nova-network
|
||||
#. queue
|
||||
#. nova-compute
|
||||
#. nova-console
|
||||
#. nova-scheduler
|
||||
#. nova-api
|
||||
|
||||
.. end-compute-nova-scheduler
|
||||
|
||||
.. begin-compute-queue
|
||||
|
||||
2. **All compute nodes (also known as hosts in terms of OpenStack) periodically publish their status, resources available and hardware capabilities: (choose all that apply)**
|
||||
2. **All compute nodes (also known as hosts in terms of OpenStack) periodically
|
||||
publish their status, resources available and hardware capabilities:
|
||||
(choose all that apply)**
|
||||
|
||||
#. through the queue
|
||||
#. with SQL calls to the database
|
||||
#. with direct interprocess communication
|
||||
#. through the queue
|
||||
#. with SQL calls to the database
|
||||
#. with direct interprocess communication
|
||||
|
||||
.. end-compute-queue
|
||||
|
||||
@ -31,11 +33,11 @@ Compute node quiz questions
|
||||
|
||||
3. **By default, the compute node's scheduler is configured as:**
|
||||
|
||||
#. the RAM scheduler
|
||||
#. the base scheduler
|
||||
#. the chance scheduler
|
||||
#. the filter scheduler
|
||||
#. the weight scheduler
|
||||
#. the RAM scheduler
|
||||
#. the base scheduler
|
||||
#. the chance scheduler
|
||||
#. the filter scheduler
|
||||
#. the weight scheduler
|
||||
|
||||
.. end-compute-default-scheduler
|
||||
|
||||
@ -43,43 +45,48 @@ Compute node quiz questions
|
||||
|
||||
4. **If the compute node is using the filter scheduler, it works by:**
|
||||
|
||||
#. filtering hosts by using predefined properties
|
||||
#. weighting hosts by applying predefined weights
|
||||
#. sorting hosts by using weights to determine host preference list first, then applying filters
|
||||
#. filtering hosts first, then using weights to determine host preference
|
||||
#. filtering hosts first, then choosing a random host from the filtered list
|
||||
#. filtering hosts by using predefined properties
|
||||
#. weighting hosts by applying predefined weights
|
||||
#. sorting hosts by using weights to determine host preference list first,
|
||||
then applying filters
|
||||
#. filtering hosts first, then using weights to determine host preference
|
||||
#. filtering hosts first, then choosing a random host from the filtered
|
||||
list
|
||||
|
||||
.. end-compute-filter-scheduler
|
||||
|
||||
.. begin-compute-scheduler-returns
|
||||
|
||||
5. **Scheduler always returns a host on which nova can start the requested VM.**
|
||||
5. **Scheduler always returns a host on which nova can start the requested
|
||||
VM.**
|
||||
|
||||
#. True
|
||||
#. False
|
||||
#. True
|
||||
#. False
|
||||
|
||||
.. end-compute-scheduler-returns
|
||||
|
||||
.. begin-compute-classes-block-storage
|
||||
|
||||
6. **OpenStack provides which classes of block storage? (choose all that apply).**
|
||||
6. **OpenStack provides which classes of block storage?
|
||||
(choose all that apply).**
|
||||
|
||||
#. RAM storage
|
||||
#. object storage
|
||||
#. persistent storage
|
||||
#. file storage
|
||||
#. SSD storage
|
||||
#. ephemeral storage
|
||||
#. disk storage
|
||||
#. RAM storage
|
||||
#. object storage
|
||||
#. persistent storage
|
||||
#. file storage
|
||||
#. SSD storage
|
||||
#. ephemeral storage
|
||||
#. disk storage
|
||||
|
||||
.. end-compute-classes-block-storage
|
||||
|
||||
.. begin-compute-persistent-volumes
|
||||
|
||||
7. **Persistent volumes can be used by more than one instance at the same time:**
|
||||
7. **Persistent volumes can be used by more than one instance at the same
|
||||
time:**
|
||||
|
||||
#. True
|
||||
#. False
|
||||
#. True
|
||||
#. False
|
||||
|
||||
.. end-compute-persistent-volumes
|
||||
|
||||
@ -87,24 +94,49 @@ Compute node quiz questions
|
||||
|
||||
8. **Specify in which order these steps must be completed to provision VMs:**
|
||||
|
||||
| **a.** nova-scheduler picks up the request from the queue.
|
||||
| **b.** nova-compute generates data for the hypervisor driver and executes the request on the hypervisor (via libvirt or API).
|
||||
| **c.** nova-scheduler interacts with nova DB to find an appropriate host via filtering and weighting, returns the updated instance entry with the appropriate host ID and sends the rpc.cast request to nova-compute for launching an instance on the appropriate host.
|
||||
| **d.** nova-conductor interacts with nova DB and returns the instance information. nova-compute picks up the instance information from the queue.
|
||||
| **e.** nova-api receives the request and sends a request to the Identity Service for validation of the auth-token and access permission. The Identity Service validates the token.
|
||||
| **f.** nova-compute picks up the request for launching an instance on the appropriate host from the queue.
|
||||
| **g.** neutron-server validates the auth-token with Identity Service. nova-compute retrieves the network info.
|
||||
| **h.** nova-compute performs the REST-call by passing the auth-token to Network API to allocate and configure the network so that the instance gets the IP address.
|
||||
| **i.** The dashboard or CLI converts the new instance request to a REST API request and sends it to nova-api.
|
||||
| **j.** nova-compute performs the REST call by passing the auth-token to glance-api. Then, nova-compute uses the Image ID to retrieve the Image URI from the Image Service, and loads the image from the image storage.
|
||||
| **k.** nova-compute sends the rpc.call request to nova-conductor to fetch the instance information such as host ID and flavor (RAM, CPU, disk).
|
||||
| **l.** cinder-api validates the auth-token with Identity Service. nova-compute retrieves the block storage info.
|
||||
| **m.** The dashboard or CLI gets the user credentials and authenticates with the Identity Service via REST API. The Identity Service authenticates the user and sends back an auth-token.
|
||||
| **n.** glance-api validates the auth-token with Identity Service. nova-compute gets the image metadata.
|
||||
| **o.** nova-compute performs the REST call by passing the auth-token to Volume API to attach volumes to the instance.
|
||||
| **p.** nova-api checks for conflicts with nova DB and creates the initial database entry for a new instance.
|
||||
| **q.** nova-api sends the rpc.call request to nova-scheduler expecting to get an updated instance entry with the host ID specified.
|
||||
| **r.** nova-conductor picks up the request from the queue.
|
||||
| **a.** nova-scheduler picks up the request from the queue.
|
||||
| **b.** nova-compute generates data for the hypervisor driver and executes
|
||||
the request on the hypervisor (via libvirt or API).
|
||||
| **c.** nova-scheduler interacts with nova DB to find an appropriate host
|
||||
via filtering and weighting, returns the updated instance entry
|
||||
with the appropriate host ID and sends the rpc.cast request to
|
||||
nova-compute for launching an instance on the appropriate host.
|
||||
| **d.** nova-conductor interacts with nova DB and returns the instance
|
||||
information. nova-compute picks up the instance information from
|
||||
the queue.
|
||||
| **e.** nova-api receives the request and sends a request to the Identity
|
||||
Service for validation of the auth-token and access permission. The
|
||||
Identity Service validates the token.
|
||||
| **f.** nova-compute picks up the request for launching an instance on the
|
||||
appropriate host from the queue.
|
||||
| **g.** neutron-server validates the auth-token with Identity Service.
|
||||
nova-compute retrieves the network info.
|
||||
| **h.** nova-compute performs the REST-call by passing the auth-token to
|
||||
Network API to allocate and configure the network so that the
|
||||
instance gets the IP address.
|
||||
| **i.** The dashboard or CLI converts the new instance request to a REST
|
||||
API request and sends it to nova-api.
|
||||
| **j.** nova-compute performs the REST call by passing the auth-token to
|
||||
glance-api. Then, nova-compute uses the Image ID to retrieve the
|
||||
Image URI from the Image Service, and loads the image from the
|
||||
image storage.
|
||||
| **k.** nova-compute sends the rpc.call request to nova-conductor to fetch
|
||||
the instance information such as host ID and flavor (RAM, CPU,
|
||||
disk).
|
||||
| **l.** cinder-api validates the auth-token with Identity Service.
|
||||
nova-compute retrieves the block storage info.
|
||||
| **m.** The dashboard or CLI gets the user credentials and authenticates
|
||||
with the Identity Service via REST API. The Identity Service
|
||||
authenticates the user and sends back an auth-token.
|
||||
| **n.** glance-api validates the auth-token with Identity Service.
|
||||
nova-compute gets the image metadata.
|
||||
| **o.** nova-compute performs the REST call by passing the auth-token to
|
||||
Volume API to attach volumes to the instance.
|
||||
| **p.** nova-api checks for conflicts with nova DB and creates the initial
|
||||
database entry for a new instance.
|
||||
| **q.** nova-api sends the rpc.call request to nova-scheduler expecting to
|
||||
get an updated instance entry with the host ID specified.
|
||||
| **r.** nova-conductor picks up the request from the queue.
|
||||
|
||||
.. end-compute-provisioning-steps
|
||||
|
||||
@ -142,13 +174,15 @@ Compute node quiz answers
|
||||
|
||||
.. begin-compute-answer-scheduler-returns
|
||||
|
||||
5. 2 (False) - Scheduler can also return an error (no suitable host for the requested VM).
|
||||
5. 2 (False) - Scheduler can also return an error (no suitable host for the
|
||||
requested VM).
|
||||
|
||||
.. end-compute-answer-scheduler-returns
|
||||
|
||||
.. begin-compute-answer-classes-block-storage
|
||||
|
||||
6. 3 (persistent storage), f (ephemeral storage) - The question is about OpenStack's block storage classes.
|
||||
6. 3 (persistent storage), f (ephemeral storage) - The question is about
|
||||
OpenStack's block storage classes.
|
||||
|
||||
.. end-compute-answer-classes-block-storage
|
||||
|
||||
@ -160,6 +194,7 @@ Compute node quiz answers
|
||||
|
||||
.. begin-compute-answer-provisioning-steps
|
||||
|
||||
8. a (6), b (18), c (7), d (11), e (3), f (8), g (15), h (14), i (2), j (12), k (9), l (17), m (1), n (13), o (16), p (4), q (5), r (10)
|
||||
8. a (6), b (18), c (7), d (11), e (3), f (8), g (15), h (14), i (2), j (12),
|
||||
k (9), l (17), m (1), n (13), o (16), p (4), q (5), r (10)
|
||||
|
||||
.. end-compute-answer-provisioning-steps
|
||||
.. end-compute-answer-provisioning-steps
|
||||
|
||||
@ -8,7 +8,9 @@ if [[ ${LANDSLIDE_MISSING} -ne 0 ]]; then
|
||||
exit 1
|
||||
fi
|
||||
|
||||
for presentation in ./associate-guide/*.rst; do
|
||||
cd ./associate-guide
|
||||
|
||||
for presentation in *.rst; do
|
||||
presentation_name=$(basename "${presentation}" .rst)
|
||||
landslide -i -d "./associate-guide/${presentation_name}.html" "${presentation}"
|
||||
landslide -i -d "${presentation_name}.html" "${presentation}"
|
||||
done
|
||||
|
||||
@ -13,6 +13,7 @@ Planning : Design
|
||||
=================
|
||||
|
||||
.. class:: colleft
|
||||
|
||||
- Planning stage is at the start of a cycle
|
||||
- take a step back
|
||||
- focus on what we want to do for the next one
|
||||
@ -26,6 +27,7 @@ Planning : Discuss
|
||||
==================
|
||||
|
||||
.. class:: colleft
|
||||
|
||||
- With our peers
|
||||
- feedback and comments
|
||||
- create the corresponding blueprint
|
||||
@ -40,6 +42,7 @@ Planning : Target
|
||||
=================
|
||||
|
||||
.. class:: colleft
|
||||
|
||||
- file new blueprints and/or specs
|
||||
- set a target milestone
|
||||
- when in the cycle they intend to complete it
|
||||
@ -54,6 +57,7 @@ Implementation : Milestone
|
||||
==========================
|
||||
|
||||
.. class:: colleft
|
||||
|
||||
- pushed to our Gerrit review
|
||||
- weeks before the milestone publication date
|
||||
- milestone-proposed branch
|
||||
@ -68,6 +72,7 @@ Implementation : freezes
|
||||
========================
|
||||
|
||||
.. class:: colleft
|
||||
|
||||
- Feature freeze
|
||||
|
||||
- new features will not be accepted, only fixes
|
||||
@ -92,6 +97,7 @@ Release Candidates
|
||||
==================
|
||||
|
||||
.. class:: colleft
|
||||
|
||||
- After the last milestone
|
||||
- file bugs about everything you find
|
||||
- prioritize bugs / bug triage
|
||||
@ -107,9 +113,11 @@ Release candidate 1
|
||||
===================
|
||||
|
||||
.. class:: colleft
|
||||
|
||||
- Between the last milestone and the RC1
|
||||
- stop adding features and concentrate on bug fixes
|
||||
- Once all the release-critical bugs are fixed, we produce the first - - - release candidate for that project (RC1)
|
||||
- Once all the release-critical bugs are fixed, we produce the first release
|
||||
candidate for that project (RC1)
|
||||
- used as-is as the final release
|
||||
|
||||
.. class:: colright
|
||||
@ -121,6 +129,7 @@ Other release candidates
|
||||
========================
|
||||
|
||||
.. class:: colleft
|
||||
|
||||
- regressions and integration issues
|
||||
- new release-critical bugs
|
||||
- (RC2), with bugs targeted to it
|
||||
@ -136,6 +145,7 @@ Release day
|
||||
===========
|
||||
|
||||
.. class:: colleft
|
||||
|
||||
- last published release candidate
|
||||
- published collectively as the OpenStack release
|
||||
|
||||
@ -148,4 +158,5 @@ Exercise
|
||||
========
|
||||
|
||||
|
||||
Based on the Icehouse release schedule, find the URL of a document or a patch that belongs to each of the steps.
|
||||
Based on the Icehouse release schedule, find the URL of a document or a patch
|
||||
that belongs to each of the steps.
|
||||
|
||||
@ -58,5 +58,5 @@ Your management
|
||||
Exercise
|
||||
========
|
||||
|
||||
List three companies and individuals that have been the most influential in the making of the module you plan to contribute to, for each metric value.
|
||||
|
||||
List three companies and individuals that have been the most influential in
|
||||
the making of the module you plan to contribute to, for each metric value.
|
||||
|
||||
@ -1,6 +1,8 @@
|
||||
OpenStack Technical Committee
|
||||
=============================
|
||||
|
||||
|
|
||||
|
||||
-----
|
||||
|
||||
Technical Committee
|
||||
@ -8,7 +10,11 @@ Technical Committee
|
||||
|
||||
The role of the Technical Committee
|
||||
|
||||
The Technical Committee ("TC") is tasked with providing technical leadership over all the OpenStack projects. It enforces OpenStack ideals (Openness, Transparency, Commonality, Integration, Quality), decides on issues affecting multiple programs, forms an ultimate appeals board for technical decisions, and generally has oversight over the OpenStack project entirely.
|
||||
The Technical Committee ("TC") is tasked with providing technical leadership
|
||||
over all the OpenStack projects. It enforces OpenStack ideals (Openness,
|
||||
Transparency, Commonality, Integration, Quality), decides on issues affecting
|
||||
multiple programs, forms an ultimate appeals board for technical decisions,
|
||||
and generally has oversight over the OpenStack project entirely.
|
||||
|
||||
.. image:: ./_assets/03-01-TC.png
|
||||
|
||||
@ -17,7 +23,12 @@ The Technical Committee ("TC") is tasked with providing technical leadership ove
|
||||
OpenStack Programs
|
||||
==================
|
||||
|
||||
OpenStack "Programs" are efforts which are essential to the completion of the OpenStack project mission. This mission is to produce the ubiquitous Open Source cloud computing platform that will meet the needs of public and private clouds regardless of size, by being simple to implement and massively scalable. Programs can create any code repository and produce any deliverable they deem necessary to achieve their goals.
|
||||
OpenStack "Programs" are efforts which are essential to the completion of the
|
||||
OpenStack project mission. This mission is to produce the ubiquitous Open
|
||||
Source cloud computing platform that will meet the needs of public and private
|
||||
clouds regardless of size, by being simple to implement and massively
|
||||
scalable. Programs can create any code repository and produce any deliverable
|
||||
they deem necessary to achieve their goals.
|
||||
|
||||
- The official list of programs is in the `governance` repository
|
||||
- http://git.openstack.org/cgit/openstack/governance/tree/reference/programs.yaml
|
||||
@ -70,8 +81,9 @@ Meetings
|
||||
Exercise
|
||||
========
|
||||
|
||||
- Exercise
|
||||
- read tc.2014-04-01-20.03.log.html and briefly comment on keystone document
|
||||
- Exercise
|
||||
|
||||
- read tc.2014-04-01-20.03.log.html and briefly comment on keystone document
|
||||
|
||||
----
|
||||
|
||||
@ -98,11 +110,16 @@ Active Technical Contributor (ATC)
|
||||
======================================
|
||||
|
||||
|
||||
The TC seats are elected by the Active Technical Contributors ("ATC"), which are a subset of the Foundation Individual Members. Individual Members who committed a change to a repository under any of the official OpenStack programs (as defined above) over the last two 6-month release cycles are automatically considered an ATC.
|
||||
The TC seats are elected by the Active Technical Contributors ("ATC"), which
|
||||
are a subset of the Foundation Individual Members. Individual Members who
|
||||
committed a change to a repository under any of the official OpenStack
|
||||
programs (as defined above) over the last two 6-month release cycles are
|
||||
automatically considered an ATC.
|
||||
|
||||
- TC seats are elected by ATC
|
||||
- Same as APC
|
||||
- Bug triagers, technical documentation writers, etc can exceptionally apply for ATC
|
||||
- Bug triagers, technical documentation writers, etc can exceptionally apply
|
||||
for ATC
|
||||
|
||||
----
|
||||
|
||||
|
||||
@ -1,6 +1,8 @@
|
||||
OpenStack Program Ecosystem
|
||||
===========================
|
||||
|
||||
|
|
||||
|
||||
----
|
||||
|
||||
Lifecycle of a new Program
|
||||
@ -17,7 +19,7 @@ External
|
||||
.. image:: ./_assets/04-02-lifecycle.png
|
||||
|
||||
- Idea
|
||||
- Gather a community
|
||||
- Gather a community
|
||||
- Alternate implementations
|
||||
- Stackforge
|
||||
- File an OpenStack incubation request
|
||||
@ -30,7 +32,7 @@ Incubated
|
||||
.. image:: ./_assets/04-03-lifecycle.png
|
||||
|
||||
- Fill the gap with graduation requirements
|
||||
- Align with the OpenStack way
|
||||
- Align with the OpenStack way
|
||||
- Two development milestones
|
||||
- Migrate to the openstack/* namespace
|
||||
- Graduation review
|
||||
|
||||
@ -1,12 +1,15 @@
|
||||
OpenStack Design Summit
|
||||
=======================
|
||||
|
||||
|
|
||||
|
||||
----
|
||||
|
||||
Design Summit
|
||||
=============
|
||||
|
||||
Where developers meet face to face to finalize planning for the next release cycle.
|
||||
Where developers meet face to face to finalize planning for the next release
|
||||
cycle.
|
||||
|
||||
.. image:: ./_assets/05-01-design-summit.png
|
||||
|
||||
|
||||
@ -36,21 +36,25 @@ Join irc.freenode.net#upstream-university
|
||||
#info
|
||||
=====
|
||||
|
||||
Add an info item to the minutes. People should liberally use this for important things they say, so that they can be logged in the minutes.
|
||||
Add an info item to the minutes. People should liberally use this for
|
||||
important things they say, so that they can be logged in the minutes.
|
||||
|
||||
----
|
||||
|
||||
#action
|
||||
=======
|
||||
|
||||
Document an action item in the minutes. Include any nicknames in the line, and the item will be assigned to them. (nicknames are case-sensitive)
|
||||
Document an action item in the minutes. Include any nicknames in the line, and
|
||||
the item will be assigned to them. (nicknames are case-sensitive)
|
||||
|
||||
----
|
||||
|
||||
#help
|
||||
=====
|
||||
|
||||
Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot)
|
||||
Add a "Call for Help" to the minutes. Use this command when you need to
|
||||
recruit someone to do a task. (Counter-intuitively, this doesn't provide help
|
||||
on the bot)
|
||||
|
||||
----
|
||||
|
||||
|
||||
@ -45,7 +45,8 @@ Sign the Individual agreement
|
||||
Do you work at a company?
|
||||
=========================
|
||||
|
||||
- If your contribution is on behalf of a company, have your managers sign the Corporate Contributor License Agreement
|
||||
- If your contribution is on behalf of a company, have your managers sign the
|
||||
Corporate Contributor License Agreement
|
||||
- http://docs.openstack.org/infra/manual/developers.html#account-setup
|
||||
|
||||
----
|
||||
|
||||
@ -26,10 +26,12 @@ Bug status
|
||||
- New: The bug was just created
|
||||
- Incomplete: The bug is waiting on input from the reporter
|
||||
- Confirmed: The bug was reproduced or confirmed as a genuine bug
|
||||
- Triaged: The bug comments contain a full analysis on how to properly fix the issue
|
||||
- Triaged: The bug comments contain a full analysis on how to properly fix the
|
||||
issue
|
||||
- In Progress: Work on the fix is in progress, bug has an assignee
|
||||
- Fix Committed: The branch containing the fix was merged into master
|
||||
- Fix Released: The fix is included in the milestone-proposed branch, a past milestone or a past release
|
||||
- Fix Released: The fix is included in the milestone-proposed branch, a past
|
||||
milestone or a past release
|
||||
- Invalid: This is not a bug
|
||||
- Opinion: This is a valid issue, but it is the way it should be
|
||||
- Won't Fix: This is a valid issue, but we don't intend to fix that
|
||||
@ -55,8 +57,10 @@ Bug status
|
||||
Bug importance
|
||||
==============
|
||||
|
||||
- Critical: Data corruption / complete failure affecting most users, no workaround
|
||||
- High: Data corruption / complete failure affecting most users, with workaround
|
||||
- Critical: Data corruption / complete failure affecting most users, no
|
||||
workaround
|
||||
- High: Data corruption / complete failure affecting most users, with
|
||||
workaround
|
||||
- Failure of a significant feature, no workaround
|
||||
- Medium: Failure of a significant feature, with workaround
|
||||
- Failure of a fringe feature, no workaround
|
||||
@ -83,13 +87,18 @@ Bug importance
|
||||
Bug tags
|
||||
========
|
||||
|
||||
- low-hanging-fruit: Bugs that are easy to fix, ideal for beginners to get familiar with the workflow and to have their first contact with the code in OpenStack development.
|
||||
- low-hanging-fruit: Bugs that are easy to fix, ideal for beginners to get
|
||||
familiar with the workflow and to have their first contact with the code in
|
||||
OpenStack development.
|
||||
- documentation: Bug is about documentation or has an impact on documentation.
|
||||
- i18n: Translations / i18n issues.
|
||||
- security: Fix for the bug would make OpenStack more resilient to future security issues.
|
||||
- security: Fix for the bug would make OpenStack more resilient to future
|
||||
security issues.
|
||||
- ops: Fix for the bug would significantly ease OpenStack operation.
|
||||
- SERIES-rc-potential: During the SERIES pre-release period, mark the bug as a potential release-critical blocker
|
||||
- SERIES-backport-potential: Mark the bug as a potential backport target to a specific SERIES (grizzly, havana...)
|
||||
- SERIES-rc-potential: During the SERIES pre-release period, mark the bug as a
|
||||
potential release-critical blocker
|
||||
- SERIES-backport-potential: Mark the bug as a potential backport target to a
|
||||
specific SERIES (grizzly, havana...)
|
||||
- Per project tags: https://wiki.openstack.org/wiki/BugTags
|
||||
|
||||
----
|
||||
@ -97,8 +106,10 @@ Bug tags
|
||||
Bug
|
||||
===
|
||||
|
||||
- Assigned To: The person currently working to fix this bug. Must be set by In progress stage.
|
||||
- Milestone: The milestone we need to fix the bug for, or the milestone/version it was fixed in.
|
||||
- Assigned To: The person currently working to fix this bug. Must be set by
|
||||
In progress stage.
|
||||
- Milestone: The milestone we need to fix the bug for, or the
|
||||
milestone/version it was fixed in.
|
||||
|
||||
----
|
||||
|
||||
@ -117,7 +128,8 @@ Confirming & prioritizing
|
||||
|
||||
- lacking information => Status: Incomplete
|
||||
- reproduced the issue => Status: Confirmed
|
||||
- core developer or a member of the project bug supervision team => Importance: <Bug impact>
|
||||
- core developer or a member of the project bug supervision team =>
|
||||
Importance: <Bug impact>
|
||||
|
||||
----
|
||||
|
||||
|
||||
@ -154,7 +154,7 @@ Local and upstream
|
||||
Good workflow
|
||||
=============
|
||||
|
||||
.. image:: ./_assets/19-01-goodworkflow.png
|
||||
.. image:: ./_assets/19-01-goodworkflow.png
|
||||
|
||||
----
|
||||
|
||||
|
||||
@ -1,6 +1,7 @@
|
||||
Lego applied to Free Software contributions
|
||||
===========================================
|
||||
|
||||
|
|
||||
|
||||
----
|
||||
|
||||
@ -37,7 +38,8 @@ Lego town
|
||||
|
||||
- Upstream project : a lego town
|
||||
- Company deadline : lego exhibition
|
||||
- Epic: become a major contributor and demonstrate the company skills during the exhibition
|
||||
- Epic: become a major contributor and demonstrate the company skills during
|
||||
the exhibition
|
||||
|
||||
----
|
||||
|
||||
@ -93,11 +95,15 @@ Sprint
|
||||
Communication
|
||||
=============
|
||||
|
||||
|
|
||||
|
||||
----
|
||||
|
||||
Diplomacy
|
||||
=========
|
||||
|
||||
|
|
||||
|
||||
----
|
||||
|
||||
Time to play with Legos
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user