Ticket #48 (closed task: fixed)

Opened 4 years ago

Last modified 4 years ago

NFSv4 Test Day

Reported by: jlaska Owned by: jlaska
Priority: major Milestone: Fedora 13
Component: Test Day Version:
Keywords: Cc: caiqian@…, steved@…, rhe
Blocked By: Blocking:

Description

On Mon, 2010-01-18 at 11:06 -0500, caiqian@… wrote:

I'd recommend next Tuesday (1/26), next Thursday (1/28), or any

Tuesday/Thursday? after. This will be influenced by the amount of prep work needed (see next step).

Next Tuesday will be working for me. Steve, are you able to be online at that date to provide helps if necessary?

Step#3 - Create the Wiki page

This should help you think about what needs testing, and perhaps designing the tests in such a way that might be helpful for a distributed testers to attack. I'm not thinking of any good distributed test scenarios for NFS, but I'm also not aware of the testing involved.If you can start with a outline of what testing you'd like to see covered, we might be able to get a better sense for how to make it a good fit for a Fedora test event.

I will be create a wiki page for it. I have not looked them in details yet. Overall, we will be running some automated NFS tests like,

Does it sound like a good fit for a test day?

It's not something I'd envision a strong level of community participation on. Mainly, since Fedora QA doesn't have a lot of experience/skill in this technical area. That said ... I'm sure there are communities that might be interested in participating? So, some questions to help explore our options ...

  1. What external customers/communities should we solicit for attendance?
  2. What is required to participate?
    1. What distro? F12, Rawhide, other?
    2. Installed system or Live image?
    3. System requirements (single system or multiple)?
    4. Can a virtual lab be used?
  3. What test feedback is needed?
    1. Is there a hardware-specific component where community contributor feedback would be helpful (i.e. like xorg-x11-drv-* test days where testers all have different hardware?)
    2. Is there software-specific components where community feedback is needed? (for example, running tests against different versions of nfs (client+server), or across F-12, F-11 and rawhide)?

Change History

comment:1 in reply to: ↑ description Changed 4 years ago by caiqian

It's not something I'd envision a strong level of community participation on. Mainly, since Fedora QA doesn't have a lot of experience/skill in this technical area. That said ... I'm sure there are communities that might be interested in participating? So, some questions to help explore our options ...

  1. What external customers/communities should we solicit for attendance?

Customers who need to involve with NFS server or/and client, system administrators. NFS, network, kernel, Fedora communities.

  1. What is required to participate?
    1. What distro? F12, Rawhide, other?

Rawhide. 2.6.32-2 F-13 (or later) kernel and nfs-utils-1.2.1-5 (or later) rpm.

  1. Installed system or Live image?

Both.

  1. System requirements (single system or multiple)?

Single will do if use virtual machines.

  1. Can a virtual lab be used?

Yes

  1. What test feedback is needed?
    1. Is there a hardware-specific component where community contributor feedback would be helpful (i.e. like xorg-x11-drv-* test days where testers all have different hardware?)

Not I am aware at the moment except architectures.

  1. Is there software-specific components where community feedback is needed? (for example, running tests against different versions of nfs (client+server), or across F-12, F-11 and rawhide)?

Maybe, some of the fixed.

v3 server + v4 client v4 client + v3 server v4 server + v4 client

comment:2 follow-up: ↓ 3 Changed 4 years ago by jlaska

Had a good discussion with Cai on IRC this morning. In order to schedule the NFS test day, we agreed that the following tasks need to be completed first.

  1. Get people on board - Identify and reach out to additional NFS experts who can provide test guidance (see https://fedoraproject.org/wiki/QA/SOP_Test_Day_management#Get_people_on_board).
  2. How to test - outline some details on what, and how, to test NFSv4 in the form of wiki test cases (basically, need to flesh out https://fedoraproject.org/wiki/QA/SOP_Test_Day_management#Create_the_Wiki_page).

comment:3 in reply to: ↑ 2 Changed 4 years ago by caiqian

Sorry for the delay.

  1. Get people on board - Identify and reach out to additional NFS experts who can provide test guidance.

After discussed with Steve, looks like there some NFS community we can get them involved like,

Linux NFS mailing list <linux-nfs@…> Linux NFSv4 mailing list <nfsv4@…> Linux pNFS mailing list <pnfs@…> Connectathon event <http://www.connectathon.org/>

  1. How to test - outline some details on what, and how, to test NFSv4 in the form of wiki test cases

We can test NFS v4 as well as Secure NFS with the above NFS test suites, and general filesystem testsuites like fsx2, bonnie etc. I'll be working on a sample test wiki page for review shortly. Does it make sense?

comment:5 Changed 4 years ago by jlaska

  • Owner set to jlaska
  • Status changed from new to assigned

The page looks good. I see you have made a few corrections already. Thanks for pushing forward with the content.

As we get closer, we should provide more test prep/setup information. For example, how can testers test the latest NFS v4 code. Whether they need to download a nightly live image, or install Fedora 13 Alpha, or install Fedora 12 (and apply test packages). Also, I assume the test case instructions will provide the details, but guidance on downloading the connectathon test.

I moved the page into the anonymous "Test_Day" namespace so you can have anonymous feedback from testers (QA/Test_Day:2010-03-02_NFS -> Test_Day:2010-03-02_NFS).

I've updated the test day schedule to include NFSv4 testing on 2010-03-02.

The next steps I believe are:

  1. Complete the test cases - If you, or someone else, are able to gather the content for the test cases, I (and likely others on test@…) can assist cleaning up the cases for proper formatting etc...
  2. ~ 1 week prior, promote the test day to the lists you mentioned in comment#3.

comment:6 Changed 4 years ago by jlaska

  • Status changed from assigned to closed
  • Resolution set to fixed

NFSv4 test day completed, thanks Qai and Steved. I couldn't find a test day summary for the event. Feel free to add that link in case I missed it.

Note: See TracTickets for help on using tickets.