Ubuntu

ARM Server Storage Testing

Registered by Michael Casadevall

We need to setup testing to qualify and harden the ARM server storage options we want to support.

=Rationale=
The ARM server space is new and the kernel is constantly changing to support these new systems, so there is a need to have automated tests to watch for regressions. This blueprint specifically covers just storage as that is a large space all on its own where failures can be pretty catastrophic to users.

=Goal=
Create a series of scripts that each test the functionality of one of the listed storage technologies. Each of the scripts should be merged into the server-workload-testing repository.

Blueprint information

Status:
Not started
Approver:
Christopher Chaltain
Priority:
Medium
Drafter:
Ubuntu Server
Direction:
Approved
Assignee:
Craig Magina
Definition:
Approved
Series goal:
Accepted for quantal
Implementation:
Deferred
Milestone target:
milestone icon ubuntu-12.10-beta-1

Related branches

Sprints

Whiteboard

Carried forward from precise blueprint and extended:
= ACTIONS =
Write up tests for x86/ARM:
 - EXT4
 - BTRFS
 - CEPH
 - RADOS
 - DRBD (https://wiki.ubuntu.com/ClusterStack/LucidTesting#Pacemaker_with_DRBD)
 - GFS2 (https://wiki.ubuntu.com/ClusterStack/LucidTesting#Pacemaker.2C_drbd8_and_OCFS2_or_GFS2)
 - OCFS2 (https://wiki.ubuntu.com/ClusterStack/LucidTesting#Pacemaker.2C_drbd8_and_OCFS2_or_GFS2)
 - GlusterFS
 - NFS client/server
 - LVM
 - iSCSI initiator/target
Automate Tests

=User Stories=
 -Joe has a new ARM server and wants to combine each node's local storage into one large clustered pool.
 -Bob wants his new ARM server to use his iSCSI storage array.

=Assumptions=
 - All of the mentioned storage technologies are available and working on ARM.

=Test Plans=
 - Run each script on all available ARM server hardware and some x86 hardware.

=Release Note=
 - Automated testing of key storage technologies has been performed to ensure a more reliable experience on ARM hardware.
  *As work completes we can further refine this statment as to what filesystem was tested on what type of hardware [a.rosales].

[21-Sep-2012] Deferred blueprint as work items were postponed. -a.rosales

(?)

Work Items

Work items:
[server-workload-testing-team] write test script for ext4: POSTPONED
[server-workload-testing-team] write test script for btrfs: POSTPONED
[server-workload-testing-team] write test script for ceph: POSTPONED
[server-workload-testing-team] write test script for rados: POSTPONED
[server-workload-testing-team] write test script for drbd: POSTPONED
[server-workload-testing-team] write test script for gfs2: POSTPONED
[server-workload-testing-team] write test script for ocfs2: POSTPONED
[server-workload-testing-team] write test script for glusterfs: POSTPONED
[server-workload-testing-team] write test script for nfs client: POSTPONED
[server-workload-testing-team] write test script for nfs server: POSTPONED
[server-workload-testing-team] write test script for lvm: POSTPONED
[server-workload-testing-team] write test script for iSCSI initiator: POSTPONED
[server-workload-testing-team] write test script for iSCSI target: POSTPONED

Dependency tree

* Blueprints in grey have been implemented.

Nearby

This blueprint contains Public information 
Everyone can see this information.