Revision as of 07:55, 25 June 2014

Weekly TripleO team meeting

MEETING TIME: Tuesdays at 19:00 UTC or Wednesday at 0700UTC (alternating weeks) in #openstack-meeting-alt.

See the iCal feed to check the time this week.

Agenda for next meeting

We have a standing agenda + one-off items: please add your one-off thing below.

Scheduled for July 2, 2014, 1900 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140702T19)

bugs
reviews
Projects needing releases
CD Cloud status
CI
Tuskar
Specs
Insert one-off agenda items here
open discussion

bugs

Copy/Paste for IRC:

#link https://bugs.launchpad.net/tripleo/
#link https://bugs.launchpad.net/diskimage-builder/
#link https://bugs.launchpad.net/os-refresh-config
#link https://bugs.launchpad.net/os-apply-config
#link https://bugs.launchpad.net/os-collect-config
#link https://bugs.launchpad.net/os-cloud-config
#link https://bugs.launchpad.net/tuskar
#link https://bugs.launchpad.net/python-tuskarclient

reviews

Here we check the review SLA and discuss any thorny blocked reviews.

Copy/paste for IRC:

#info There's a new dashboard linked from https://wiki.openstack.org/wiki/TripleO#Review_team - look for "TripleO Inbox Dashboard"
#link http://russellbryant.net/openstack-stats/tripleo-openreviews.html
#link http://russellbryant.net/openstack-stats/tripleo-reviewers-30.txt
#link http://russellbryant.net/openstack-stats/tripleo-reviewers-90.txt

CI

Derek has a high level summary - http://goodsquishy.com/downloads/s_tripleo-jobs.html

Previous meetings

[1]

@@ Line 9: / Line 9: @@
 We have a standing agenda + one-off items: please add your one-off thing below.
-Scheduled for June 25, 2014, 0700 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140625T07)
+Scheduled for July 2, 2014, 1900 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140702T19)
 * bugs
@@ Line 17: / Line 17: @@
 * CI
 * Tuskar
+* Specs
 * Insert one-off agenda items here
-** https://review.openstack.org/#/c/97657/ / https://review.openstack.org/#/c/93981/ - reading passwords only from $TRIPLEO_ROOT
-*** Is it too soon? Commenters suggest to make the path configurable, defaulting to $TRIPLEO_ROOT - will still break people who have passwords elsewhere and always run the scripts from that directory - but they can simply set a variable to point at the password files.
-*** Too soon for this, or should we go ahead?
-** For those attending the TripleO mid-cycle sprint in Raleigh, the hotel details have been posted to the etherpad
-** #link https://etherpad.openstack.org/p/juno-midcycle-meetup
 * open discussion
 <br/>

Difference between revisions of "Meetings/TripleO"