How can we improve our smoke testing pipeline so that we catch issues in merge proposal *before* they land? A brief overview of SmokeStack. What it is good at... and how the system might be improved. Discussion Questions: -Gating vs. Pre-gating (commenting on merge proposals)? -How to deal with false negatives? -Speed improvements? Get more resources? Better utilize resources? Does speed matter? -What configurations are the most important? (Libvirt, XenServer, MySQL, PostgreSQL, LDAP, etc) -Multi-node vs. Single node. -Using/building real packages? (Fedora/Ubuntu) -How does config management fit in? (Chef/Puppet) (Session lead is Dan Prince)
Tuesday April 17, 2012 11:00am - 11:55am PDT
Seacliff C
