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-16-Config.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

3.1 KiB
Raw Blame History

Test 6-16 - Verify vic-machine configure

Purpose:

Verify vic-machine configure

References:

  • vic-machine-linux create -h

Environment:

This test requires that a vSphere server is running and available

Test Steps

  1. Deploy VCH
  2. Configure VCH
  3. Check the debug state of the VCH
  4. Check the debug state of an existing containerVM
  5. Configure the VCH by setting the debug state to 0
  6. Check the debug state of the VCH
  7. Check the debug state of the existing containerVM
  8. Create a new container and check the debug state of it
  9. Configure the debug state of the VCH again and check whether there is only a single snapshot left
  10. check whether the output of vic-machine inspect contains the desired debug state
  11. Configure the VCH by adding a container network
  12. Run docker network ls
  13. Run vic-machine inspect config
  14. Run a container with the new container network
  15. Configure the VCH by adding a new container network without specifying the previous network
  16. Configure the VCH by adding a new container network while specifying the previous network
  17. Run docker network ls
  18. Run vic-machine inspect config
  19. Run a container with the new container network
  20. Configure the VCH by attempting to change an existing container network
  21. Configure VCH http proxy
  22. Verify http proxy is set correctly through govc
  23. Configure the VCH's operations user credentials
  24. Run vic-machine inspect config
  25. Reset VCH http proxy using VCH ID
  26. Verify http proxy is reset correctly through govc
  27. Run vic-machine inspect config
  28. Configure VCH dns server to 10.118.81.1 and 10.118.81.2
  29. Run vic-machine inspect config
  30. Reset VCH dns server to default
  31. Run vic-machine inspect config
  32. Configure VCH resources
  33. Verify VCH configuration through vic-machine inspect
  34. Configure VCH resources with too small values
  35. Verify VCH configuration is rollback to old value
  36. Configure the VCH by adding a new volume store
  37. Run vic-machine inspect config
  38. Run docker info
  39. Create a volume on the default volume store
  40. Create a volume on the new volume store
  41. Run docker volume ls
  42. Configure the volume stores without specifying an existing volume store
  43. Configure the volume stores by attempting to change an existing volume store
  44. Configure the VCH by adding a new volume store with a URL scheme
  45. Run vic-machine inspect config
  46. Verify configure is in vic-machine dialog

Expected Outcome

  • Step 15 should fail with an error message saying that the existing container network must be specified
  • Step 20 should fail with an error message saying that changes to existing container networks are not supported
  • Step 24's output should contain the operations user's name and the host thumbprint
  • Step 36 and 37's output should contain both volume stores
  • Step 40's output should contain both volumes
  • Step 41 should fail with an error message saying that existing volume stores must be specified
  • Step 42 should fail with an error message saying that changes to existing volume stores are not supported
  • Step 44's output should contain all three volume stores
  • All other steps should succeed