Hey all, I've had a couple different conversations with week with organizations that want to ramp up their ceph development efforts, as a big piece of that, spin up their own teuthology environments. There has been a lot going on here, and I haven't been on the weekly calls, but I suspect things that will help them move forward include: - documenting a teuthology install-from-scratch. this would include setting up the databases, lock server, workers, etc., and will initially be long and ugly but will hopefully shrink over time. - adding support for euca2ools or some other cloud client that does openstack and ec2 for creating/destroying test machines. hopefully most of the integration points are mapped out from the downburst integration work. - ongoing work to collapse the locking and queuing and reporting into a unified and/or cohesive service. I'm probably missing things and/or vastly oversimplifying, but hopefully others can chime in an improve this list. I think the better roadmap we have here, the easier it will be for new people to come online and focus their efforts where they will make the most difference. Of course the upcomign CDS is a good place to discuss this, but something should be written down first to guide/frame that discussion. sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
