From mboxrd@z Thu Jan 1 00:00:00 1970 From: Loic Dachary Subject: Re: teuthology-lock and choosing a kernel Date: Mon, 09 Mar 2015 15:01:05 +0100 Message-ID: <54FDA7A1.4020406@dachary.org> References: <54FC459D.2090703@dachary.org> <6E9B72C6-1FA0-46D3-873E-EA99A52BE669@redhat.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cSvRc574hqVlegqp5pCUrb0fUjHRtKI76" Return-path: Received: from mail2.dachary.org ([91.121.57.175]:55130 "EHLO smtp.dmail.dachary.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S932279AbbCIOBL (ORCPT ); Mon, 9 Mar 2015 10:01:11 -0400 In-Reply-To: <6E9B72C6-1FA0-46D3-873E-EA99A52BE669@redhat.com> Sender: ceph-devel-owner@vger.kernel.org List-ID: To: Andrew Schoen Cc: Ceph Development This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --cSvRc574hqVlegqp5pCUrb0fUjHRtKI76 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Of course ! Using teuthology tasks to configure the node makes perfect se= nse. Thanks ! On 09/03/2015 14:37, Andrew Schoen wrote: > Loic, >=20 > After locking the node like normal, you can use teuthology to install t= he kernel you need. Just include the kernel stanza in your yaml file. h= ttp://ceph.com/teuthology/docs/teuthology.task.html#teuthology.task.kerne= l.task >=20 > Something like this: >=20 > interactive-on-error: true = = =20 > roles: > - [mon.0, client.0] > kernel: > branch: testing > tasks: > - interactive:=20 >=20 > Use teuthology-lock =97list-targets to get the connection information f= or you newly locked node and add that to your yaml. >=20 > Best, > Andrew >=20 > On Mar 8, 2015, at 7:50 AM, Loic Dachary > wrote: >=20 >> Hi Andrew, >> >> After successfully locking a centos 6.5 VPS in the community lab with >> >> teuthology-lock --lock-many 1 --owner loic@dachary.org --machine-type vps --os-type centos --os-version 6.5 >> >> it turns out that it has a 2.6.32 kernel by default. A more recent ker= nel is required to run the ceph-disk tests because it relies on /dev/loop= handling partition tables as a regular disk would. After installing a 3.= 10 kernel from http://elrepo.org/tiki/kernel-lt and rebooting, it was no = longer possible to reach the machine. >> >> The teuthology-suite command has a -k option which suggest there is a = way to specify the kernel when provisioning a machine. The command >> >> ./virtualenv/bin/teuthology-suite --dry-run -k testing --priority 101 = --suite rgw --suite-branch firefly --machine-type plana,burnupi,mira --di= stro ubuntu --email loic@dachary.org --owner lo= ic@dachary.org --ceph firefly-backports >> >> shows lines like: >> >> 2015-03-08 13:43:26,432.432 INFO:teuthology.suite:dry-run: ./virtualen= v/bin/teuthology-schedule --name loic-2015-03-08_13:43:06-rgw-firefly-bac= kports-testing-basic-multi --num 1 --worker multi --priority 101 --owner = loic@dachary.org --description 'rgw/multifs/{cl= usters/fixed-2.yaml fs/btrfs.yaml rgw_pool_type/erasure-coded.yaml tasks/= rgw_multipart_upload.yaml}' -- /tmp/schedule_suite_AQ2b6w /home/loic/src/= ceph-qa-suite_firefly/suites/rgw/multifs/clusters/fixed-2.yaml /home/loic= /src/ceph-qa-suite_firefly/suites/rgw/multifs/fs/btrfs.yaml /home/loic/sr= c/ceph-qa-suite_firefly/suites/rgw/multifs/rgw_pool_type/erasure-coded.ya= ml /home/loic/src/ceph-qa-suite_firefly/suites/rgw/multifs/tasks/rgw_mult= ipart_upload.yaml >> >> which show the testing word as part of the job name. The https://githu= b.com/ceph/teuthology/ page shows some more information about kernel choi= ces but it's non trivial to figure out how to translate that into somethi= ng that could be used in the context of teuthology-lock. >> >> I'm not sure where to look and I would be grateful if you could give m= e a pointer to go in the right direction. >> >> Cheers >> >> --=20 >> Lo=EFc Dachary, Artisan Logiciel Libre >> >=20 --=20 Lo=EFc Dachary, Artisan Logiciel Libre --cSvRc574hqVlegqp5pCUrb0fUjHRtKI76 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlT9p6EACgkQ8dLMyEl6F21fMgCfTn2gKvPAEV9tWcdBzWX8lQdD TvgAn2rIogum7pMeJsJyz9vt5hZT13cd =a8WF -----END PGP SIGNATURE----- --cSvRc574hqVlegqp5pCUrb0fUjHRtKI76--