Made grub execution conditional and not done when ARM.
Use ctx parameter to change machine type to tala.
Fix kernel assignments when running ARM systems.
Fixes: #5000
Signed-off-by: Warren Usui <warren.usui@inktank.com>
Adding tests for ticket #5604 to test
user propagation via the radosgw-agent.
Signed-off-by: Joe Buck <jbbuck@gmail.com>
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
Enable multi-region calls and tests only if
the configuration has specified a
radosgw-agent tastk.
Signed-off-by: Joe Buck <jbbuck@gmail.com>
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
When doing a lock-many, do not lock any of the vpms when downburst errors
occur. Do not display message on unlock with downburst error, because
slot is still freed (and can be locked by someone else).
Fix: 5957
Signed-off-by: Warren Usui <warren.usui@inktank.com>
Because it relies on the lock server which is presumably not available
since check-locks was set to False. It matters when using teuthology
on a minimal installation.
http://tracker.ceph.com/issues/5946fixes#5946
Signed-off-by: Loic Dachary <loic@dachary.org>
Refactored the radosgw-agent.py code so that it
is structured more like existing teuthology
tasks.
Additionally, added code to enable:
using the override field in YAML files,
specifying which radosgw-agent github branch
to use checkout and for the YAML file to
specify one of the following: a full sync,
an incremental sync and the starting of the
test radosgw-agent server (previously the
server was always started by this task).
Signed-off-by: Joe Buck <jbbuck@gmail.com>
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
In the example config, the region root and
zone root where pointing to the same pool,
which is not a best practice. Updated the
example to show them pointing to different pools.
Signed-off-by: Joe Buck <jbbuck@gmail.com>
When pulling region info from the config
structure, if the region info isn't there,
log a more helpful message.
Signed-off-by: Joe Buck <jbbuck@gmail.com>
Extend the s3readwrite.py task to enable the
creation and deletion of users for the s3readwrite
tests to be independently specified with the default
assumption to both being true.
This is needed for tests that will create a user and
data in one execution and read it in another.
Signed-off-by: Joe Buck <jbbuck@gmail.com>
Extend the rados pool configuration options to
specify all pools (if desired).
Also, reordered zone and region configuration
so that they're configure (per client) in
this order: zone, region, set default region
Signed-off-by: Joe Buck <jbbuck@gmail.com>
The log_data and log_metadata are made configurable
via the YAML file and default to false
(meaning neither data nor metadata operations are
logged).
Signed-off-by: Joe Buck <jbbuck@gmail.com>
Go to the master zone in the master region for radosgw-admin
operations. Trigger metadata sync. Other fixes.
Signed-off-by: Yehuda Sadeh <yehuda@inktank.com>
