Jump to: navigation, search

Difference between revisions of "Meetings/InfraTeamMeeting"

(Agenda for next meeting)
m (Agenda for next meeting: jenkins module split)
Line 16: Line 16:
 
*** https://etherpad.openstack.org/p/swift_logs_next_steps
 
*** https://etherpad.openstack.org/p/swift_logs_next_steps
 
** Puppet module split
 
** Puppet module split
*** asselin (available first 20 mins of meeting) is working on Jenkins module split, working with 'shepherd' fungi. Spec was updated to better reflect actual process. Let's get these merged:
+
*** asselin (available first 20 mins of meeting) completed Jenkins module split
**** https://review.openstack.org/#/c/129768/
+
**** module metadata patch needs reviews: https://review.openstack.org/134373
**** https://review.openstack.org/#/c/132129/
+
**** spec was updated following prior meetings to better reflect actual process, with one still pending: https://review.openstack.org/134393
*** Need to clarify 'last step' of spec for new Jenkins puppet module repo:
 
**** Spec: https://review.openstack.org/#/c/134393/1
 
**** 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
 
 
*** nibz has two module splits ready to go, github and pip
 
*** 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
 
**** pip is a bit weird because we landed the create repo but not the split out

Revision as of 18:43, 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/