Jump to: navigation, search

Difference between revisions of "Meetings/ThirdParty"

 
(180 intermediate revisions by 15 users not shown)
Line 1: Line 1:
= Weekly Third Party meeting =
+
= Weekly Third Party meetings =
  
The Third Party group holds public weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code>, Mondays at 1800 UTC. Everyone interested in Third Party process surrounding automated testing is encouraged to attend.
+
*Third Party meeting for all aspects of Third Party needs:
* Leadership: Anita Kuno (anteaya), Kurt Taylor (krtaylor), Jay Pipes (jaypipes)
+
** First Monday of the month at 1500 UTC in <code><nowiki>#openstack-meeting</nowiki></code>. Everyone interested in any aspect Third Party process is encouraged to attend.
* Next meeting's chair is: Anita Kuno (anteaya)
+
** Constant irc channel in <code><nowiki>#openstack-third-party-ci</nowiki></code>
* Please feel free to add agenda items (and your IRC nick in parenthesis).
+
** Chair: Anita Kuno (anteaya), Lenny Verkhovsky (lennyb)  
 +
** Please feel free to add agenda items (and your IRC nick in parenthesis).
 +
* <del>Working Group: Third party CI operators interested in working to improving the consumability of infra CI components and sharing best practices are encouraged to attend. Details on the Third Party CI Working Group: https://wiki.openstack.org/wiki/ThirdPartyCIWorkingGroup
 +
** <code><nowiki>#openstack-meeting</nowiki></code>, Monthly at first Monday of the month at 1500 UTC
 +
** Sub-wiki: https://wiki.openstack.org/wiki/ThirdPartyCIWorkingGroup
 +
** Chairs: Ramy Asselin (asselin)
 +
** Please feel free to add agenda items (and your IRC nick in parenthesis).</del>
  
 
== Goals for Third Party meetings ==
 
== Goals for Third Party meetings ==
Line 16: Line 22:
 
* work with infra to improve consumability of infra components, this can include refactoring code, offering documentation patches and reviewing current code
 
* 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 ==
+
== Reference links ==
* Welcome & Reminder of OpenStack Mission
+
* Common-ci - Solution for in-tree 3rd party CI system
** 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.
+
** Documentation: http://docs.openstack.org/infra/openstackci/
* Review of previous week's open action items
+
** Notes for users who have set it up. These should be added back into the documentation and/or bug fixes: https://etherpad.openstack.org/p/thirdpartyci
** Anita (anteaya) to polish the Purposes/Goals section from the etherpad
+
* Spec to have infra host ci-watch
*** https://etherpad.openstack.org/p/polished-third-party-goals
+
** http://specs.openstack.org/openstack-infra/infra-specs/specs/deploy-ci-dashboard.html
* Announcements
+
* CI Watch - Third-party CI monitoring project (skylerberg)
** http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg25513.html Mid-Cycle Meet-up Darmstadt
+
** Running instance of CI Watch: http://ci-watch.tintri.com
** Documentation: http://ci.openstack.org/third_party.html
+
** Bugs: https://bugs.launchpad.net/ciwatch
** How To Ask Questions The Smart Way: http://www.catb.org/esr/faqs/smart-questions.html
+
** Blueprints: https://blueprints.launchpad.net/ciwatch/
* OpenStack Program items
+
* Patches for review
** 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)
+
** 3rd Party CI Tools: https://review.openstack.org/#/q/project:stackforge/third-party-ci-tools+status:open,n,z
* Deadlines & Deprecations
+
** Downstream-puppet: https://review.openstack.org/#/q/topic:downstream-puppet+status:open,n,z
* Highlighting a Program or Gerrit Account
+
** CI Watch dashboard: https://review.openstack.org/#/q/topic:ci-dashboard+status:open,n,z
** thstack-ci and freescale-ci
+
** Enable Zuul to work behind a proxy: https://review.openstack.org/#/c/240131/
* Open Discussion
 
 
 
== Past Meetings ==
 
=== 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 ==
 
== 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/
+
Previous meetings, with their notes and logs, can be found at  
 +
* 11/30/2015 (meetbot not working): http://paste.openstack.org/show/480387/
 +
* Starting May 2014: http://eavesdrop.openstack.org/meetings/third_party/  
 +
* Before May 2014: http://eavesdrop.openstack.org/meetings/third_party_ci/
 +
[[category: meetings]]

Latest revision as of 07:02, 17 April 2018

Weekly Third Party meetings

  • Third Party meeting for all aspects of Third Party needs:
    • First Monday of the month at 1500 UTC in #openstack-meeting. Everyone interested in any aspect Third Party process is encouraged to attend.
    • Constant irc channel in #openstack-third-party-ci
    • Chair: Anita Kuno (anteaya), Lenny Verkhovsky (lennyb)
    • Please feel free to add agenda items (and your IRC nick in parenthesis).
  • Working Group: Third party CI operators interested in working to improving the consumability of infra CI components and sharing best practices are encouraged to attend. Details on the Third Party CI Working Group: https://wiki.openstack.org/wiki/ThirdPartyCIWorkingGroup

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

Reference links

Logs from past meetings

Previous meetings, with their notes and logs, can be found at