Revision as of 12:30, 22 June 2015

Weekly Openstack Ansible Deployment team meeting

If you're interested in Ansible deploying OpenStack, we hold two public meetings weekly:

Community Meeting

- On IRC in #openstack-meeting-4, on Thursday at 16:00 UTC.

Bug Triage

- On IRC in #openstack-ansible, on Tuesday at 16:00 UTC.

Regular attendees

Add yourself to this list to be pinged prior to each meeting (Please use your irc_handle):

cloudnull, mattt, andymccr, d34dh0r53, hughsaunders, b3rnard0, palendae, Sam-I-Am, odyssey4me, serverascode, rromans, mancdaz, dolphm, _shaps_, BjoernT, claco, echiu, dstanek, jwagner

Agenda for next meeting

Please feel free to add items to the agenda below with your name or irc_handle and we'll cover them.

Agenda & rollcall
Review action items from last week
Blueprints
- https://blueprints.launchpad.net/openstack-ansible/+spec/build-facts-archive odyssey4me
  - What series should this target? When is work expected to start on this?
- https://blueprints.launchpad.net/openstack-ansible/+spec/modularize-config odyssey4me
  - What series should this target? When is work expected to start on this? Linked bugs?
Reviews
- Discuss https://review.openstack.org/189998 (Fernet token support for keystone) odyssey4me
  - How to best handle key rotation?
  - Should we enable this as a default?
Bugs
- bug/blueprint tracking. Should we always require a bug/blueprint be referenced in commits to allow easier tracking of what went into a milestone/release? mancdaz
Milestones
- Kilo 11.0.4: https://launchpad.net/openstack-ansible/+milestone/11.0.4
- Juno 10.1.10: https://launchpad.net/openstack-ansible/+milestone/10.1.10
- Icehouse 9.0.11: https://launchpad.net/openstack-ansible/+milestone/9.0.11
Open discussion
- Defining the project mission odyssey4me
  - Is our mission to OpenStack (just OpenStack services), or to deploy a whole OpenStack environment (OpenStack and all supporting infrastructure)?
  - How do we manage taking on too many things that end up not being well maintained? If we decide to use automated testing, then how do we decide what should or should not be tested?

Previous meetings & logs

Meeting #19 | Weekly Meeting | 18 June 2015 | logs | summary
Meeting #18 | Weekly Meeting | 11 June 2015 | logs | summary
Meeting #17 | Weekly Meeting | 4 June 2015 | logs | summary
Meeting #16 | Weekly Meeting | 28 May 2015 | logs | summary
Bug triage #16 | 12 May 2015 | notes
Meeting #15 | Weekly Meeting | 5 May 2015 | logs | summary
Bug triage #15 | 5 May 2015 | notes
Meeting #14 | Weekly Meeting | 30 April 2015 | logs | summary
Bug triage #14 | 28 April 2015 | notes
Meeting #13 | Weekly Meeting | 23 April 2015 | logs | summary
Bug triage #13 | 21 April 2015 | notes
Meeting #12 | Weekly Meeting | 16 April 2015 | logs | summary
Bug triage #12 | 14 April 2015 | notes
Meeting #11 | Weekly Meeting | 9 April 2015 | logs | summary
Bug triage #11 | 7 April 2015 | notes
Meeting #10 | Weekly Meeting | 2 April 2015 | logs | summary
Bug triage #10 | 31 March 2015 | notes
Meeting #9 | Weekly Meeting | 26 March 2015 | logs | summary
Bug triage #9 | 24 March 2015 | notes
Bug triage #8 | 17 March 2015 | notes
Meeting #8 | Weekly Meeting | 12 March 2015 | logs | summary
Bug triage #7 | 10 March 2015 | notes
Meeting #7 | Weekly Meeting | 5 March 2015 | logs | summary
Bug triage #6 | 3 March 2015 | notes
Meeting #6 | Weekly Meeting | 26 February 2015 | logs | summary
Bug triage #5 | 24 February 2015 | notes
Meeting #6 | Weekly Meeting | 19 February 2015 | logs | summary
Bug triage #4 | 17 February 2015 | notes
Meeting #6 | Weekly Meeting | 12 February 2015 | logs | summary
Bug triage #3 | 10 February 2015 | notes
Meeting #5 | Weekly Meeting | 5 February 2015 | logs | summary
Meeting #4 | Weekly Meeting | 29 January 2015 | logs | summary
Bug triage #1 | 27 January 2015 | notes
Meeting #3 | Weekly Meeting | 22 January 2015 | logs | summary
Meeting #2 | Weekly Meeting | 15 January 2015 | agenda | logs | summary
Meeting #1 | Weekly Meeting | 18 December 2014 | agenda

Agenda Archives

Previous agendas are archived here: agenda archives

Meetbot Commands

For those who are starting the weekly community meeting, use the following command:

#startmeeting OpenStack Ansible Meeting

Additional commands: Meetbot Manual

@@ Line 24: / Line 24: @@
 * Review action items from last week
 * Blueprints
+** https://blueprints.launchpad.net/openstack-ansible/+spec/build-facts-archive <code>odyssey4me</code>
+*** What series should this target? When is work expected to start on this?
+** https://blueprints.launchpad.net/openstack-ansible/+spec/modularize-config <code>odyssey4me</code>
+*** What series should this target? When is work expected to start on this? Linked bugs?
 * Reviews
 ** Discuss https://review.openstack.org/189998 (Fernet token support for keystone) <code>odyssey4me</code>
@@ Line 31: / Line 35: @@
 ** bug/blueprint tracking. Should we always require a bug/blueprint be referenced in commits to allow easier tracking of what went into a milestone/release? <code>mancdaz</code>
 * Milestones
+** Kilo 11.0.4: https://launchpad.net/openstack-ansible/+milestone/11.0.4
+** Juno 10.1.10: https://launchpad.net/openstack-ansible/+milestone/10.1.10
+** Icehouse 9.0.11: https://launchpad.net/openstack-ansible/+milestone/9.0.11
 * Open discussion
+** Defining the project mission <code>odyssey4me</code>
+*** Is our mission to OpenStack (just OpenStack services), or to deploy a whole OpenStack environment (OpenStack and all supporting infrastructure)?
+*** How do we manage taking on too many things that end up not being well maintained? If we decide to use automated testing, then how do we decide what should or should not be tested?
 -----

Difference between revisions of "Meetings/openstack-ansible"