Hi Herman, I recently succeeded (thanks to Thierry's help ;-) to install paddles using ansible[1]. The playbook was developped recently by Zack. Even if you don't otherwise use ansible, it's a better option than more complex instructions. And easier to maintain as you can rely on Andrew, Dan and Zack (and maybe others) to maintain the playbook. One thing that I like (but is frowned upon by more seasoned ansible users) is to use ansible from the node where paddles is to be installed. For instance: ansible-playbook -i paddles, -c local paddles.yml I suppose the http://docs.ceph.com/teuthology/docs/LAB_SETUP.html document should be updated with this new recommended deployment method (the main document is at https://github.com/ceph/teuthology/blob/master/docs/LAB_SETUP.rst). Toward the end of your document, the "Submitting slave node" is where the I don't have any experience. But David Galloway and Dan Mick and maybe others do as they have deployed and configured all the hardware currently in the sepia lab. It's a significant undertaking but is fortunately well documented and all files you need are public. I chose an easier alternative which is to rely on an OpenStack cluster to provision the resources required to run teuthology jobs[2]. The last pitfall that comes to mind, and it's a significant one, is that a number of teuthology jobs are sensitive to the infrastructure. For instance, I recently worked around a paramiko bug that only showed on OpenStack although it is by no mean specific to OpenStack[3]. Fixing ceph-qa-suite so that it does not break because the infrastructure is slower or faster, has 1G network or 10G, has fast or slow internet connections etc. is sometime non trivial. But for the most part it's easy and a little tedious: you just have to do it on a regular basis :-) My 2cts [1] installing paddles via ansible http://www.spinics.net/lists/ceph-devel/msg28974.html [2] OpenStack backend https://github.com/dachary/teuthology/tree/openstack#openstack-backend [3] openstack: SSHException: Key-exchange timed out http://tracker.ceph.com/issues/15236 On 28/03/2016 12:14, Herman Narkaytis wrote: > We intended to publish this instruction as public document, so feedback from broader community would be valuable. > > HHN. > > On Mon, Mar 28, 2016 at 1:01 PM, Loic Dachary <loic@xxxxxxxxxxx <mailto:loic@xxxxxxxxxxx>> wrote: > > Hi, > > On 28/03/2016 10:55, Herman Narkaytis wrote: > > Loic, > > Below you will find a link on Teuthology deployment instructions. I would be appreciated to get your feedback on it. > > This is a precise and detailed documentation, very useful. Do you mind if I post my remarks about it with ceph-devel in cc ? Other developers will certainly have interesting contributions to make. > > > https://docs.google.com/document/d/18MW0NAwEZB45lGgsgjpb4fFdi8ope1YGr5OA-uvsIR8/edit > > > > We are still figuring out how to deploy GitBuilder, but it should not be as hard as it was with Teuthology. > > HHN. > > :-) > > Cheers > -- Loïc Dachary, Artisan Logiciel Libre -- 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
