Jump to: navigation, search

Difference between revisions of "Meetings/InfraTeamMeeting"

(Agenda for next meeting: Zuul pending patches could use a review, list some of them)
(Agenda for next meeting)
Line 23: Line 23:
 
**** New Jenkins repo changes depend on ^^: https://review.openstack.org/#/c/134373/
 
**** New Jenkins repo changes depend on ^^: https://review.openstack.org/#/c/134373/
 
*** Afterwards, we should be good to do more puppet-module splits in parallel
 
*** Afterwards, we should be good to do more puppet-module splits in parallel
 +
*** nibz has two module splits ready to go, github and pip
 +
**** pip is a bit weird because we landed the create repo but not the split out
 +
**** https://review.openstack.org/#/c/134723/ would change it so we don't need to keep track of modules in two places
 
** Nodepool DIB
 
** Nodepool DIB
 
** Docs publishing
 
** Docs publishing
Line 30: Line 33:
 
* puppet-httpd (ianw 11/18)
 
* puppet-httpd (ianw 11/18)
 
** import or new?
 
** import or new?
 +
** Well this ship kindof sailed. Now must do a full new one(nibalizer happy to do it)
 
* ianw outstanding reviews (ianw 11/18)
 
* ianw outstanding reviews (ianw 11/18)
 
** https://review.openstack.org/131921 (set useful path)
 
** https://review.openstack.org/131921 (set useful path)
Line 42: Line 46:
 
** https://review.openstack.org/128921 "Update merge status after merge:merge is submitted"
 
** https://review.openstack.org/128921 "Update merge status after merge:merge is submitted"
 
** https://review.openstack.org/131559 "Support stracktracing on Geard embedded server"
 
** https://review.openstack.org/131559 "Support stracktracing on Geard embedded server"
 +
* Puppet module maturity(nibz)
 +
** A few things are comming to the infra modules
 +
** auto upload to forge on signed tags (upload as openstackci or as openstackinfra or openstack-infra ?)
 +
** generated html documenation and upload(upload to where)
 +
** section of infra manual for infra-modules
 +
** unit (puppet-rspec) and integration (beaker-rspec) tests
 
* Open discussion
 
* Open discussion
  

Revision as of 17:13, 18 November 2014

Header

Weekly Project Infrastructure team meeting

The OpenStack Project Infrastructure Team holds public weekly meetings in #openstack-meeting, Tuesdays at 1900 UTC. Everyone interested in infrastructure and process surrounding automated testing and deployment is encouraged to attend.

Please feel free to add agenda items (and your IRC nick in parenthesis).

Agenda for next meeting

Upcoming Project Renames

Items for Future Meetings

  • for November 25, 2014 meeting
    • stackforge ci account naming: proposal from fungi => when a third-party ci is operated by and exclusively testing changes for a single project, it's allowable for their project name to appear as the subsystem being tested within the account display name

Previous meetings

Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/infra/ and earlier at http://eavesdrop.openstack.org/meetings/ci/