Sandon Van Ness [Thu, 21 Nov 2013 00:37:31 +0000 (16:37 -0800)]
Use shortened version in order to avoid revision/arch mishaps.
Sometimes -X is added to package names which does not exist in the
/version file. Simply using the version string does not work on
RHEL (it does on centos). Until version and the packages match
identically we instead will just split the version at the - and
no longer specify the dist for better reliability but slightly
lower accuracy.
Signed-off-by: Sandon Van Ness <sandon@inktank.com>
Sandon Van Ness [Sat, 9 Nov 2013 01:00:27 +0000 (17:00 -0800)]
For saya (arm) use arm gitbuilder for ceph sha1.
Since the arm gitbuilder (even using a ton of nodes for distcc) is
much slower than x86 lets grab the sha1 from its own gitbuilder
when machine_type is saya rather than the x86 one.
Signed-off-by: Sandon Van Ness <sandon@inktank.com>
Warren Usui [Tue, 15 Oct 2013 21:43:39 +0000 (14:43 -0700)]
Added two new tasks. tgt starts up the tgt service. iscsi starts
up the iscsi service and logins to an rbd image using the tgt service
(either locally or remotely). The iscsi service runs some
simple tests, and then sets up the isci-image to be useable by
rbd test scripts. Later workunits can perform further testing
on the isci-image interface.
In order to add the new tasks, common_fs_utils.py was formed
from code extracted out of rbd.py. Rbd.py and iscsi.py both
call the functions in this module.
Sage Weil [Fri, 1 Nov 2013 17:56:42 +0000 (10:56 -0700)]
install.upgrade: fix overrides of sha1|tag|branch
If the upgrade task config has a branch: (or tag or sha1), do
not apply the sha1|branch|tag overrides keys. This fixes the
breakage from 280f783c2e8dda0df6afb4de0b115aad1614fbdc which
made
...use the sha1 from the overrides instead of the explicitly
specified branch. The intention was to only use the overrides
when the version was not specified (whether it was sha1 or
branch or tag).
At some point we should probably make the same change for
install function in install.py, but let's fix this first to
get the upgrade tests working.
Sandon Van Ness [Mon, 28 Oct 2013 18:04:28 +0000 (11:04 -0700)]
Fixed errors. Tests pass.
Since the default OS version is different for each distro the
argument default is None instead of explicity set to a value
like with get_distro. Fixed some logic around that and the tests
making the arugment always take precidence.
Signed-off-by: Sandon Van Ness <sandon@inktank.com>
Sandon Van Ness [Sat, 26 Oct 2013 00:48:50 +0000 (17:48 -0700)]
Support --os-version as argument.
You can use --os-type as an argument when not running teuthology
tests but instead just using teuthology-lock. This adds the ability
to also use --os-version so you can specify the version of the
distro without having to run an actual test with a yaml like you
normally would have had to do setting os_version in the yaml.
Signed-off-by: Sandon Van Ness <sandon@inktank.com>
Sandon Van Ness [Fri, 25 Oct 2013 20:14:21 +0000 (13:14 -0700)]
Use worker httpd instead of prefork (like ubuntu) on rpm distros.
Ubuntu's default apache uses worker instead of prefork like rpm
based distro's. If rpm use httpd.worker instead of httpd so that
the -X behavior will not be blocked by a single request.
Signed-off-by: Sandon Van Ness <sandon@inktank.com>
Sandon Van Ness [Fri, 25 Oct 2013 20:14:21 +0000 (13:14 -0700)]
Use worker httpd instead of prefork (like ubuntu) on rpm distros.
Ubuntu's default apache uses worker instead of prefork like rpm
based distro's. If rpm use httpd.worker instead of httpd so that
the -X behavior will not be blocked by a single request.
Signed-off-by: Sandon Van Ness <sandon@inktank.com>
Sage Weil [Thu, 24 Oct 2013 02:24:06 +0000 (19:24 -0700)]
rbd_fsx: do not exceed 250GB for fsx image
This breaks on 32-bit architectures because fsx can't allocate the
in-memory buffer or hit some other limit. 500MG also seems to run out of
memory (tho it at least does not segfault).
Fixes: #6576 Signed-off-by: Sage Weil <sage@inktank.com>
Samuel Just [Wed, 23 Oct 2013 17:52:55 +0000 (10:52 -0700)]
ceph_manager: workaround for 6116
This is an annoying race, we really should delay going
clean until the backfill peer has acknoledged the clean
info, but we currently don't. In order to prevent this
bug from messing up the nightlies, we'll delay killing
the peer for 20s to make it likely that the backfill
peer has gotten the clean info.
Workaround: #6116 Signed-off-by: Samuel Just <sam.just@inktank.com>
Zack Cerza [Fri, 11 Oct 2013 22:41:22 +0000 (17:41 -0500)]
Put machine_type in config.yaml
Reason being, if --worker is passed to teuthology-schedule, we are
already placing the job in the tube for that machine type. If the job
config doesn't specify a machine_type, it will later be assigned to
'plana' by teuthology-run without actually modifying the config. This
can result in jobs running on hardware other than what was requested.
projects / ceph.git / log