d8dfun/virtual-kubelet
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity
Files
513cebe7b7cf590cd53c02ea8da1a20b58dd8f18
virtual-kubelet/vendor/github.com/vmware/vic/tests/test-cases/Group6-VIC-Machine/6-03-Delete.md
Loc Nguyen 513cebe7b7 VMware vSphere Integrated Containers provider (#206) 
* Add Virtual Kubelet provider for VIC

Initial virtual kubelet provider for VMware VIC.  This provider currently
handles creating and starting of a pod VM via the VIC portlayer and persona
server.  Image store handling via the VIC persona server.  This provider
currently requires the feature/wolfpack branch of VIC.

* Added pod stop and delete.  Also added node capacity.

Added the ability to stop and delete pod VMs via VIC.  Also retrieve
node capacity information from the VCH.

* Cleanup and readme file

Some file clean up and added a Readme.md markdown file for the VIC
provider.

* Cleaned up errors, added function comments, moved operation code

1. Cleaned up error handling.  Set standard for creating errors.
2. Added method prototype comments for all interface functions.
3. Moved PodCreator, PodStarter, PodStopper, and PodDeleter to a new folder.

* Add mocking code and unit tests for podcache, podcreator, and podstarter

Used the unit test framework used in VIC to handle assertions in the provider's
unit test.  Mocking code generated using OSS project mockery, which is compatible
with the testify assertion framework.

* Vendored packages for the VIC provider

Requires feature/wolfpack branch of VIC and a few specific commit sha of
projects used within VIC.

* Implementation of POD Stopper and Deleter unit tests (#4)

* Updated files for initial PR
2018-06-04 15:41:32 -07:00

2.1 KiB
Raw Blame History

Test 6-03 - Verify delete clean up all resources

Purpose:

Verify vic-machine delete can delete vch installed by vic-machine create

References:

  • vic-machine-linux delete -h

Environment:

This test requires that a vSphere server is running and available

Test Cases

Delete VCH and verify

  1. Create VCH through vic-machine create
  2. Create container
  3. Make sure container VM is powered on
  4. Delete VCH without --force, to get delete failure
  5. Delete VCH with --force, to get delete success
  6. Check vSphere through govc to make sure all resources are deleted correctly

Expected Outcome:

  • Step 4 should fail for VM is powered on
  • Step 5 should success
  • Step 6 should not find any resources created by vic-machine and VCH

Attach Disks and Delete VM

  1. Create VCH normally
  2. Pull a moderately sized image (ubuntu)
  3. Check to see that disk images exist via govc
  4. Use govc to attach disk images to appliance VM directly
  5. Delete the VCH
  6. Ensure that VCH folder is entirely gone after delete via govc

Expected Outcome:

  1. All steps should succeed
  2. govc should return 1 when not finding images in step 6

Delete VCH with non-cVM in same RP

  1. Create VCH though vic-machine create
  2. Create VM in the VCH's resource pool
  3. Delete VCH
  4. Check vSphere through govc to make sure the VM was not deleted
  5. Delete the VM and RP to cleanup

Expected Outcome:

  1. All steps should succeed

Delete VCH moved from its RP

  1. Create VCH though vic-machine create
  2. Create VM in the VCH's resource pool
  3. Create another RP
  4. Move VCH to the new RP
  5. Delete VCH
  6. Check vSphere through govc to make sure the VM and containerVM were not deleted
  7. Delete the VM, containerVM, and RP to cleanup

Expected Outcome:

  1. All steps should succeed

Delete VCH moved to root RP and original RP deleted

  1. Create VCH though vic-machine create
  2. Create VM in the root RP
  3. Move VCH to root RP
  4. Delete the VCH created RP
  5. Delete VCH
  6. Check vSphere through govc to make sure the VM in the root RP was not deleted
  7. Delete the VM to cleanup

Expected Outcome:

  1. All steps should succeed