Transcript What Is New - MN.Next RC IOVP

1
What’s new in MN.Next – IOVP
Program
Confidential
© 2009 VMware Inc. All rights reserved
What is new in MN.next IOVP
 New test cases
 Enhancements
 Fixes
 Questionnaire pages
 Result submission page
 Submission Verifier page
2
Confidential
What is new in MN.next IOVP - New test cases
IOVP Certification
NIC
Test Name
Netdump
-Test verifies ESXi server can coredump to netdump server
Memory Usage
-Calculates heap usage of driver.
iPXE
-Checks ESXi image can be iPXE booted using DUT.
Receive Side Scaling
-Enables multiq RX to acieve high performanace.
16G Support
-16G support for FCHBA's.
FCHBA
IODM
-Queries storage device information using esxcfg and esxcli commands.
Dependent iSCSI
Jumbo Frame
-Enabling Jumbo frame on iscsi adapters.
New session
- Creates new iscsi session
Max Chars in IQN, CHAP Name
- Enforcing Maximun charects in IQN and CHAP name
Independent iSCSI
Jumbo Frame
-Enabling Jumbo frame on iscsi adapters.
New session
- Creates new iscsi session
Max Chars in IQN, CHAP Name
- Enforcing Maximun charects in IQN and CHAP name
3
Confidential
What is new in MN.next IOVP - Enhancements
Enhancements
Partner needs to run Failover tests on Active-Active array and other tests on Active passive array
Partner can browse all source files in submission page and upload with Result submission.
Partners can run FCoE , iSCSI and NIC Certs independently (VIO)
Partners can enter details of Host Profile certification if their driver supports Stateless.
4
Confidential
What is new in MN.next IOVP –Fixes
fixes
: vmkstress test should be run only on Beta Buid.
 JF_VST test fails on inbox driver.
 ConvergedIO::ConvergedIscsiNet test fails with XML merge error
I nstall::Config:driver Update test
I nstall:driver::Custom-ISO test
Core dump test fails on FCHBA
5
Confidential
What is new in MN.next IOVP - Result Submission page
6
Confidential
What is new in MN.next IOVP - Result Submission page
- Enter Partner name, email address, Contact name, Address, City,
State, ZIP code, Country.
- Also Enter Device Information on which certification is run.
 Driver name and Version : mn_op.o 2.2.2.4
 Driver License (GPL/Proprietry): GPL
 Device Used for certification(Model name) : My_device 1122 CNA
 Device ID (VID:DID:SVID:SSID): 1058:1058:1058:1058
 Device Firmware Version : 2.2.2.0
Click on ‘Finish’ , when asked ‘Are you sure you want to submit’, click on ‘OK’ for going to submission verifier page.
- Above information will be captured in report pdf file.
7
Confidential
What is new in MN.next IOVP - Certification Verifier page
8
Confidential
What is new in MN.next IOVP - Certification Verifier page
- This page needs to be filled if this is new async driver. In case of Inbox or already
certified async driver, need not to fill this.
• driver vib : Browse driver vib file
• Source code : Browse source code file (in tar/zip)
• Source verification : Browse .sva file
• Driver license : Browse driver license.txt file
• Copyright notice : Browse copyright notice.txt file
• Bulletin : Browse bulletin.xml file
• Release Notes : Browse Release Notes .txt file
• Download description
• Manual test logs directory : Browse for manual logs if at all your certification has any manual logs.
• Other comments- Any other comment.
These values will be saved under test_session.d/ CertVerificationData.prop file in submitted result.
- Click on Finish to submit result to VMware.
9
Confidential