Updated YAML filenames and removed duplicates
Removed duplicate ironic team meeting file. Renamed YAML files to remove spaces. Change-Id: I991fb27b73c11a5557f825ab13321fe65df72ade
This commit is contained in:
parent
e7235a7301
commit
00f5cc7acb
|
@ -0,0 +1,10 @@
|
|||
project: Gantt (Scheduler) team meeting
|
||||
schedule:
|
||||
- time: '1500'
|
||||
day: Tuesday
|
||||
irc: openstack-meeting
|
||||
frequency: weekly
|
||||
chair: Don Dugger
|
||||
description: >
|
||||
agenda: |
|
||||
*How will the current API work lead to actual scheduling
|
|
@ -0,0 +1,38 @@
|
|||
project: Ironic team Meeting
|
||||
schedule:
|
||||
- time: '1900'
|
||||
day: Mondays
|
||||
irc: openstack-meeting
|
||||
frequency: weekly
|
||||
chair: Devananda van der Veen
|
||||
description: >
|
||||
If you're interested in bare metal deployments ith OpenStack, please join
|
||||
us. This meeting is here we'll talk about the Ironic project, an evolution
|
||||
of the Nova Baremetal driver.
|
||||
agenda: |
|
||||
*Greeting, roll-call and anouncements
|
||||
*Regular Topics
|
||||
**blueprint status check: https://blueprints.launchpad.net/ironic
|
||||
**bug status check: https://wiki.openstack.org/wiki/BugTriage
|
||||
*Call outs
|
||||
**Nova Driver
|
||||
***Nova volume driver
|
||||
***Nova hostmanager
|
||||
***Refactor get_iscsi_initiator
|
||||
**Functional testing with devstack
|
||||
**Inteeration with TripleO
|
||||
*I-3 planning
|
||||
**Graduation requirements
|
||||
***nova driver needs to land
|
||||
***we need ful CI (https://review.openstack.org/#/c/70348/)
|
||||
**feature freeze
|
||||
***what work / revies need to be prioritized
|
||||
***what can we realistically land
|
||||
**code cleanup
|
||||
***with mock vs. @mock
|
||||
***node[property] vs node.property
|
||||
*Open Discussion
|
||||
*Adds max retry limit to sync_poer_state task(should e rely on driver | health or not when preventing infinite syncs?) https://revie.openstack.org/#/c/77420/2/ironic/conductor/manager.py
|
||||
**Functional/Integration testing of vendor drivers (Tempest?)
|
||||
**Driver architecture for Chassis object (Allo vendors to define behavior | for the Chassis object like Auto node discovery etc)
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
project: Nova Bug Scrub Meeting
|
||||
schedule:
|
||||
- time: '1630'
|
||||
day: Wednesday
|
||||
irc: openstack-meeting-3
|
||||
frequency: weekly
|
||||
chair: Tracy Jones
|
||||
description: >
|
||||
This is a weekly meeting review Nova Bugs. The initial focus will be on
|
||||
triaging bugs in the New state and ensuring that critical bugs are making
|
||||
progress. Once the New queue is under control we will switch our focus to
|
||||
reviewing incomplete bugs, removing assignees from stale bugs so others can
|
||||
pick them up (especially low hanging fruit)
|
||||
agenda:
|
||||
- triage new
|
||||
- review critical
|
||||
- open discussion
|
|
@ -0,0 +1,19 @@
|
|||
project: Nova Bug Scrub Meeting
|
||||
schedule:
|
||||
- time: '1630'
|
||||
day: Wednesday
|
||||
irc: openstack-meeting-3
|
||||
frequency: weekly
|
||||
chair: Tracy Jones
|
||||
description: >
|
||||
This is a weekly meeting review Nova Bugs. The initial focus will be on
|
||||
triaging bugs in the New state and ensuring that critical bugs are making
|
||||
progress. Once the new queue is under control we will switch our focus to
|
||||
reviewing incomplete bugs, removing assignees from stale bugs so others
|
||||
can pick them up (especially low hanging fruit). In general we will follow
|
||||
the policies documented here https://wiki.openstack.org/wiki/BugTriage
|
||||
agenda: |
|
||||
*Tag untagged
|
||||
*Triage New
|
||||
*Revie Critical
|
||||
*Open Discussion
|
|
@ -0,0 +1,9 @@
|
|||
project: Nova Hyper-V team meeting
|
||||
schedule:
|
||||
- time: '1600'
|
||||
day: Tuesday
|
||||
irc: openstack-meeting
|
||||
frequency: weekly
|
||||
chair: Peter Pouliot
|
||||
description:
|
||||
agenda:
|
|
@ -1,22 +0,0 @@
|
|||
project: Nova Team Meeting
|
||||
schedule:
|
||||
- time: '1400'
|
||||
day: Thursday
|
||||
irc: openstack-meeting-alt
|
||||
frequency: weekly
|
||||
|
||||
- time: '2100'
|
||||
day: Thursday
|
||||
irc: openstack-meeting
|
||||
frequency: weekly
|
||||
chair: Russell Bryant
|
||||
description: >
|
||||
This meeting is a weekly gathering of developers working on OpenStack Compute
|
||||
(Nova). We cover topics such as release planning and status, bugs, reviews,
|
||||
and other current topics worthy of real-time discussion.
|
||||
agenda:
|
||||
- general annoucement
|
||||
- sub-teams
|
||||
- bugs
|
||||
- blueprints
|
||||
- open discussion
|
|
@ -0,0 +1,20 @@
|
|||
project: Nova Team meeting
|
||||
schedule:
|
||||
- time: '1400'
|
||||
day: Thursday
|
||||
irc: openstack-meeting-alt
|
||||
frequency: biweekly
|
||||
- time: '2100'
|
||||
day: Thursday
|
||||
irc: openstack-meeting
|
||||
frequency: biweekly
|
||||
chair: Russell Bryant
|
||||
description: >
|
||||
This meeting is a weekly gathering of developers working on OpenStack Compute
|
||||
(NOVA). We cover topics such as release and planning and status, bugs,
|
||||
reviews, and other current topics worthy of real-time discussion
|
||||
agenda: |
|
||||
*Icehouse-rc
|
||||
*other bugs
|
||||
*blueprints
|
||||
*Open Discussion
|
|
@ -1,15 +0,0 @@
|
|||
project: OpenStack Project and Release Status Meeting
|
||||
schedule:
|
||||
- time: '2100'
|
||||
day: Tuesday
|
||||
irc: openstack-meeting
|
||||
frequency: weekly
|
||||
chair: Thierry Carrez
|
||||
description: >
|
||||
The whole OpenStack Team holds a public weekly Project and Release Status
|
||||
meeting. Everyome is encouraged to attend.
|
||||
agenda:
|
||||
- icehouse-3 progress
|
||||
- red flag district (or blocked blueprints)
|
||||
- incubated projects
|
||||
- open discussion
|
|
@ -0,0 +1,16 @@
|
|||
project: OpenStack Project & Release Status meeting
|
||||
schedule:
|
||||
- time: '2100'
|
||||
day: Tuesday
|
||||
irc: openstack-meeting
|
||||
frequency: weekly
|
||||
chair: Thierry Carrez
|
||||
description: >
|
||||
The whole OpenStack Team holds a public weekly Project & Release Status
|
||||
meeting in #openstack-meetings, Tuesdays at 2100 UTC. Everyone is encouraged
|
||||
to attend.
|
||||
agenda: |
|
||||
*Current RC status
|
||||
*(add topics here)
|
||||
*Incubated Projects
|
||||
*Open Discussion
|
|
@ -1,22 +0,0 @@
|
|||
project: Technical Committee Meeting
|
||||
schedule:
|
||||
- time: '2000'
|
||||
day: Tuesday
|
||||
irc: openstack-meeting
|
||||
frequency: weekly
|
||||
chair: Thierry Carrez
|
||||
description: >
|
||||
The OpenStack Technical Committee is one of the governing bodies of the
|
||||
OpenStack project. It is an elected group that represents the contributors
|
||||
to the project, and has oversight on all technical matters.
|
||||
agenda:
|
||||
- progress on DefCore feedback
|
||||
- creating key distribution service (KDS) under identity program
|
||||
- 'integrated projects and new requirements: Neutron'
|
||||
-
|
||||
- minor govermance changes
|
||||
-
|
||||
- add oslo.test to the Oslo program
|
||||
- add Infrastructure Program mission
|
||||
- Oslo program changes (oslo.vmware addition)
|
||||
- open discussion
|
|
@ -0,0 +1,18 @@
|
|||
project: Technical Committee Meeting
|
||||
schedule:
|
||||
- time: '2000'
|
||||
day: Tuesday
|
||||
irc: openstack-meeting
|
||||
frequency: weekly
|
||||
chair: Thierry Carrez
|
||||
description: >
|
||||
The OpenStack Technical Committee is one of the governing bodies of the
|
||||
OpenStack project. It is an elected group that represents the
|
||||
contributors to the project, and has oversight on all technical matters.
|
||||
The Technical Committee is formally defined in the OpenStack Foundation
|
||||
bylas and further refined in the Technical Committee charter.
|
||||
agenda: |
|
||||
*Integrated projects and new requirements, Gap analysis for Ceilometer
|
||||
*Bylas subcommitte report, proposed changes to the OpenStack Bylas
|
||||
*Minor governance changes
|
||||
*Open Discussion
|
|
@ -0,0 +1,18 @@
|
|||
project: VMware API team meeting
|
||||
schedule:
|
||||
- time: '1500'
|
||||
day: Wednesday
|
||||
irc: openstack-meeting
|
||||
frequency: weekly
|
||||
chair: Shan Hartsock
|
||||
description: >
|
||||
This is a weekly meeting to discuss blueprints and bugs related to VMwareAPI
|
||||
integrations ith OpenStack. At present, this one meeting will cover all
|
||||
these out into separate sub-teams. We maintain a channel for general
|
||||
discussion of VMwareAPI on freenode IRC at openstack-vmware but formal meetings
|
||||
are held in the official IRC meeting rooms for OpenStack.
|
||||
agenda: |
|
||||
*Refactorings priority order & assignments and schedule
|
||||
*blueprint priority order after refactorings
|
||||
**any exceptional blueprints which should be exempt from this rule
|
||||
*Open Discussion
|
|
@ -1,22 +0,0 @@
|
|||
project: XenAPI Team Meeting
|
||||
schedule:
|
||||
- time: '1500'
|
||||
day: Wednesday
|
||||
irc: openstack-meeting
|
||||
frequency: weekly
|
||||
chair: John Garbutt
|
||||
description: >
|
||||
Meeting to discuss the status of Blueprints and bugs relating to the XenAPI
|
||||
layer.
|
||||
agenda:
|
||||
- actions from last meeting
|
||||
-
|
||||
- blueprints
|
||||
-
|
||||
- discuss Icehouse-2 progress
|
||||
-
|
||||
- bugs and QA
|
||||
-
|
||||
- 'https://bugs.launchpad.net/nova/+bugs?field.tag=xenserver'
|
||||
- gating progress
|
||||
- open discussion
|
|
@ -0,0 +1,21 @@
|
|||
project: Xen Api team meeting
|
||||
schedule:
|
||||
- time: '1500'
|
||||
day: Wednesday
|
||||
irc: openstack-meeting
|
||||
frequency: weekly
|
||||
chair: John Garbutt
|
||||
description: >
|
||||
Meeting to discuss the status of Blueprints and bugs relating to the XenAPI
|
||||
layer in #openstack-meeting, every Wednesday at 1500 UTC. (It used to be
|
||||
every Wednesday at 1700 UTC, but this proved to late for the UK folks at
|
||||
Citrix after daylight savings kicked in)
|
||||
agenda: |
|
||||
*Actions from last meeting
|
||||
*Blueprints
|
||||
**Discuss Icehouse-2 progress
|
||||
*Docs
|
||||
*Bugs & QA
|
||||
**https://bugs.launchpad.net/nova/+bugs?field.tag=xenserver
|
||||
**gating progress
|
||||
*Open Discussion
|
Loading…
Reference in New Issue