Revision as of 17:38, 9 June 2014

Weekly Third Party meeting

The Third Party group holds public weekly meetings in #openstack-meeting, Mondays at 1800 UTC. Everyone interested in Third Party process surrounding automated testing is encouraged to attend.

• Leadership: Anita Kuno (anteaya), Kurt Taylor (krtaylor), Jay Pipes (jaypipes)
• Next meeting's chair is: Anita Kuno (anteaya)
• Please feel free to add agenda items (and your IRC nick in parenthesis).

Goals for Third Party meetings

• drive the collection/aggregation of documentation towards a single place
• get OpenStack leads talking to other OpenStack leads about issues and solutions in the third party space
• to work towards a common interface for third party folks who may have contact with multiple projects
  • document the process to get started in the third party testing space
  • document information in a common interface both for projects and for third party organizations
• to provide a forum for the curious and for OpenStack programs who are not yet in this space but may be in the future
• to encourage questions from third party folks and support the sourcing of answers
• work with infra to improve consumability of infra components, this can include refactoring code, offering documentation patches and reviewing current code

Agenda for next meeting

• Welcome & Reminder of OpenStack Mission
  • The OpenStack Open Source Cloud Mission: 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.
• Review of previous week's open action items
• Announcements
  • Documentation: http://ci.openstack.org/third_party.html
  • How To Ask Questions The Smart Way: http://www.catb.org/esr/faqs/smart-questions.html
  • anteaya continues to address the items brought forward during the Juno summit: https://etherpad.openstack.org/p/juno-infra-improving-3rd-party-testing one item is standardized naming of automated gerrit accounts: https://etherpad.openstack.org/p/automated-gerrit-account-naming-format
• OpenStack Program items
• Deadlines & Deprecations
• Highlighting a Program or Gerrit Account
• Open Discussion

Past Meetings

6/2/2014

• Welcome & Reminder of OpenStack Mission
  • The OpenStack Open Source Cloud Mission: 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.
• Review of previous week's open action items
  • Anita (anteaya) to polish the Purposes/Goals section from the etherpad
    • https://etherpad.openstack.org/p/polished-third-party-goals
• Announcements
  • http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg25513.html Mid-Cycle Meet-up Darmstadt
  • Documentation: http://ci.openstack.org/third_party.html
  • How To Ask Questions The Smart Way: http://www.catb.org/esr/faqs/smart-questions.html
• OpenStack Program items
  • What are the requirements for test environments for non-CI use? When patches are proposed that require 3rd party extension functionality to exercise, validating the patch on systems configured with the 3rd party software/hardware. This is a growing concern for Horizon. (david-lyle)
• Deadlines & Deprecations
• Highlighting a Program or Gerrit Account
  • thstack-ci and freescale-ci
• Open Discussion

5/26/2014

• Welcome & Reminder of OpenStack Mission
  • The OpenStack Open Source Cloud Mission: 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.
• Review of previous week's open action items (4-5 minutes)
  • Anita (anteaya) has to get better at using the #action tag
  • Anita (anteaya) to polish the Purposes/Goals section from the etherpad
    • https://etherpad.openstack.org/p/polished-third-party-goals
• Announcements
  • Documentation: http://ci.openstack.org/third_party.html
• OpenStack Program items
  • What are the requirements for test environments for non-CI use? When patches are proposed that require 3rd party extension functionality to exercise, validating the patch on systems configured with the 3rd party software/hardware. This is a growing concern for Horizon. (david-lyle)
• Deadlines & Deprecations
• Highlighting a Program or Gerrit Account
• Open Discussion

5/19/2014

• Welcome and discussion of format and goals (anteaya)
  • https://etherpad.openstack.org/p/third-party-meeting-format
• Recognition of OpenStack Programs affected by Third Party testing
  • Infra (anteaya)
  • Ironic (devananda)
  • other programs please identify and represent
• Recognition of what process we currently have for Third Party testing
  • documentation (anteaya)
    • http://ci.openstack.org/third_party.html
  • Ironic
    • https://wiki.openstack.org/wiki/Ironic/Testing#Third_party_CI
  • requirements from summit design session
    • https://etherpad.openstack.org/p/juno-infra-improving-3rd-party-testing
• Hearing from Third Party testing CI
  • VMware wiki status page: https://wiki.openstack.org/wiki/NovaVMware/Minesweeper/Status
• Open Discussion

Logs from past meetings

Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/third_party/ and http://eavesdrop.openstack.org/meetings/third_party_ci/