Mirror Mounts Test Plan

<2007/416>

SECTION 1 - Introduction

1.1 Authors

1.2 Test Sponsor

1.3 Open Source Project

• Is this an open source project? Yes

  http://opensolaris.org/os/project/nfs-namespace/

1.4 References

• PSARC http://opensolaris.org/os/community/arc/caselog/2007/416/

• Test Assertions http://opensolaris.org/os/project/nfs-namespace/files/mm-test-assertions.html

1.5 Glossary

SECTION 2 - Operational Factors

2.1 Project Dependencies

• There is no project dependency for this project.

2.2 Risks

Risk#1:

• Description:

This test plan is based on current schedule and design information from the I-team. Changes may occur during design and implementation phases. Test development schedule may shift with any changes.

• Likelihood of Occurrence: Medium

• Severity: Moderate

• Mitigation and Contingency Plan:

Will work very closely with the I-team to get informed of any changes and update testing schedule accordingly.

2.3 Assumptions

Assumption #1:
The mirror mounts of this project limit to NFSv4 clients and servers.

Assumption #2:
This test plan only covers the resource allocation for Nevada.

SECTION 3 - Test Program Operational Plan

3.1 Test Program Summary

This program qualifies the project requirements

• Triggering actions for automatic mirror-mounts and nested mirror-mounts

• Automatic and manual unmounting

• Interaction with the automounter

• Inheritance of mount properties and security

• No performance degradation compared to automount of the same mount directory tree

• No regression with existing NFS mount and automount support

Any issues found during the final testing cycle will be tracked in bugtraq under development/network/mars (product/category/subcategory). Re-testing of any bug fixes will depend on the scope/size of the changes. There should be no p1-p3 bugs for the project to integrate.

SECTION 4 - Test Development Information

4.1 Test Development

SECTION 5 - Areas of Testing

5.1 Functional Testing

• Verify new functionalities of mirror mounts/umounts

  • New developed tests listed at section 4.1

• Functional testing will start before the development complete, to work along with I-team for the preliminary testing and to verify the correctness of the tests.

5.2 Regression Testing

• Ensure existing functionalities continue to work, run the following suites

• cthon_automount

• fnfs

• sharemnt

• nfsv4-test

• cthon_stress

5.3 Stress Testing

• Looping multiple mirror mount with 10 level down server filesystems simultaneously

5.5 Performance Testing

• DTrace script to compare a mount of the same server using mirror mount and automount; expect same performance (within the noise).

5.6 Zones Testing

• Same set of functional and regression tests run in non-global zones

5.8 Interoperability Testing

• Testing against Linux NFSv4 server

5.9 Documentation Testing

• Review the System Administration Guide and the manpage updates related to the project.

SECTION 6 - Test Execution

6.1 Hardware Test Configurations

This project has no extraordinary hardware considerations. It will be tested on both SPARC and x86 systems.

6.2 Software Test Configurations

LOFI and ZFS shares will be used at servers to setup filesystem boundaries

6.3 Pre-Integration PIT Run

• Is a pre-integration PIT run is required? (REQUIRED, RECOMMENDED, NONE)?

None

6.4 Test Execution Matrix