You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sudha Ponnaganti (JIRA)" <ji...@apache.org> on 2013/04/20 06:27:15 UTC

[jira] [Commented] (CLOUDSTACK-794) QA - Testing For Nicira NVP

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637119#comment-13637119 ] 

Sudha Ponnaganti commented on CLOUDSTACK-794:
---------------------------------------------

Test activity completed

From: Daan Hoogland [mailto:DHoogland@schubergphilis.com] 
Sent: Thursday, April 18, 2013 12:38 PM
To: dev@cloudstack.apache.org
Subject: qa tests for nicira code in 4.1

LS,

At Schuberg Philis we did some tests on the 4.1 code for the tests in the following table
Test Case ID  Test Description         Results
           Infrastructure
NVP-001         Create NVP Element pass
NVP-002         Disable NVP Element            pass
NVP-003         Enable NVP Element pass
NVP-004         Delete NVP Element  pass
NVP-005         Create NVP Device   pass
NVP-006         Delete NVP Device    pass
           L2 Functions
NVP-101         Create Logical Switch            pass
NVP-102         Create Logical Port    pass
NVP-103         Check Connection     Pass
NVP-104         Check Connection     Pass
NVP-105         Delete Logical Switch            Pass
NVP-106         Delete Logical Port     Pass
           L3 Functions
NVP-201         Create Logical Router            Pass
NVP-202         Create Source Nat rule          Pass
NVP-203         Create Static Nat rule            Pass
NVP-204         Create Port FW rule   Pass
NVP-205         Check Source Nat rule          Pass
NVP-206         Check Static Nat rule Pass
NVP-207         Check Port FW rule   Pass
NVP-208         Delete Source Nat rule          Pass
NVP-209         Delete Static Nat rule Fail
NVP-210         Delete Port FW rule   Pass
NVP-211         Delete Logical Router            Pass

The tests where partly done aith scripts but these are not yet complete and the remainder of functionality was done by hand.
For the failed test, NVP-209 a ticket was created, 'CLOUDSTACK-2092'. The problem in this case was that deleting the static rule did not result in the deletion of the ip adres from the logical router.

Kind regards,
Daan Hoogland

                
> QA - Testing For Nicira NVP
> ---------------------------
>
>                 Key: CLOUDSTACK-794
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-794
>             Project: CloudStack
>          Issue Type: Sub-task
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Devices, Test
>    Affects Versions: 4.1.0
>         Environment: Nicira Integration
>            Reporter: Sudha Ponnaganti
>            Assignee: Hugo Trippaers
>              Labels: Nicira
>             Fix For: 4.1.0
>
>
> Following testing has been done by Hugo while checking the code. 
> Check in Details : http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201206.mbox/%3C20120626165622.10353.36046@reviews.apache.org%3E
> Testing
> -------
> Simple build check
>   clean-all build-all
> Testing of all api calls
>  * addNiciraNvpDevice
>  * deleteNiciraNvpDevice		
>  * listNiciraNvpDevices
>  * listNiciraNvpDeviceNetwork
> Functional testing using the following procedure
> * start from clean db and create zone (with guest traffic on a physical network with stt isolation
> type)
> * add NiciraNvp network service provider and enable
> * add NiciraNcpDevice to physical network and configure using api
> * create guestnetwork
> * create instance linked to guest network
> * check existence of logical switch and logical ports for routervm and instance
> * check connectivity between routervm and instance
> * destroy host
> * after shutdown of routervm and network check logical switch and ports on nicira (should
> be gone)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira