We don't have devcloud or devcloud-kvm for vmware. To use marvin tests, we need to set up dedicated vCenter setup, not sure if we have that.
Thanks -min On 2/27/13 8:14 AM, "Chip Childers" <chip.child...@sungard.com> wrote: >On Tue, Feb 26, 2013 at 06:02:02PM -0800, Min Chen wrote: >> Changed to subject to submit a Merge request. >> >> This is to request merging my feature branch vim51_win8 to master. The >> context of this feature branch is already discussed in this email >>thread, >> basically we are upgrading Vmware SDK from 4.x to 5.1 to support more >> guest OS, like Windows 8, Windows 2012, or potentially OSX. Since this >> feature is directly communicating to Vmware hypervisor, we need to have >>a >> Vcenter and esx host setup to test this code change. Unit tests are not >>of >> much value here. Based on our earlier discussion, I am sharing the >>manual >> integration tests I have done so far with this branch (synced with >>master >> up to commit cf06861c9bf883f2ca1ec818fe7bd4ad26b84318 today): >> >> 1. Back-compatibility test to make sure that new SDK will work with >>older >> version of VCenter (I used VCenter 5.0 to test) >> - Deploy CentOs VM. >> - Apply the following operations on VM: start/stop/volume snapshot >> >> 2. Test with 5.1 VCenter >> - Deploy CentOS VM. >> - Register Template: Windows 2012 template >> - Deploy Windows 2012 VM. >> - Start/Stop VM >> - Take Volume snapshot of VM >> >> All these tests are done with Basic Zone setup. >> >> Thanks >> -min > >Why are you not using marvin tests for this? I'd rather know that >testing is automated, then rely on manual regression testing results. > >-chip
