Jump to: navigation, search

Difference between revisions of "Meetings/ThirdParty"

(Created page with "= Weekly Third Party meeting = The Third Party group holds public weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code>, Mondays at 1800 UTC. Everyone intereste...")
 
 
(200 intermediate revisions by 18 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:
 +
** 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.
 +
** Constant irc channel in <code><nowiki>#openstack-third-party-ci</nowiki></code>
 +
** 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>
  
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 ==
+
== Reference links ==
* Welcome and discussion of format and goals (anteaya)
+
* Common-ci - Solution for in-tree 3rd party CI system
* Recognition of OpenStack Programs affected by Third Party testing
+
** Documentation: http://docs.openstack.org/infra/openstackci/
** Infra (anteaya)
+
** 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
** other programs please identify and represent
+
* Spec to have infra host ci-watch
* Recognition of what process we currently have for Third Party testing
+
** http://specs.openstack.org/openstack-infra/infra-specs/specs/deploy-ci-dashboard.html
** documentation
+
* CI Watch - Third-party CI monitoring project (skylerberg)
** requirements from summit design session
+
** Running instance of CI Watch: http://ci-watch.tintri.com
* Hearing from Third Party testing CI
+
** Bugs: https://bugs.launchpad.net/ciwatch
** Walking through VMware Third Party testing interface with OpenStack
+
** Blueprints: https://blueprints.launchpad.net/ciwatch/
* Open Discussion
+
* Patches for review
 +
** 3rd Party CI Tools: https://review.openstack.org/#/q/project:stackforge/third-party-ci-tools+status:open,n,z
 +
** Downstream-puppet: https://review.openstack.org/#/q/topic:downstream-puppet+status:open,n,z
 +
** CI Watch dashboard: https://review.openstack.org/#/q/topic:ci-dashboard+status:open,n,z
 +
** Enable Zuul to work behind a proxy: https://review.openstack.org/#/c/240131/
 +
 
 +
== Logs from past meetings ==
 +
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