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

["Sudha Ponnaganti (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sudha Ponnaganti resolved CLOUDSTACK-794.
-----------------------------------------

    Resolution: Fixed
    
> 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