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/Group1-Docker-Commands/1-21-Docker-Volume-LS.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

1.9 KiB
Raw Blame History

Test 1-21 - Docker Volume LS

Purpose:

To verify that docker volume ls command is supported by VIC appliance

References:

1 - Docker Command Line Reference

Environment:

This test requires that a vSphere server is running and available

Test Steps:

  1. Deploy VIC appliance to vSphere server
  2. Issue docker volume create --name=testVol
  3. Issue docker volume ls
  4. Issue docker volume ls -q
  5. Issue docker volume ls -f bogusfilter=test
  6. Issue docker create --name=danglingVol
  7. Issue docker create -v testVol:/test busybox
  8. Issue docker volume ls -f dangling=true
  9. Issue docker volume ls -f dangling=false
  10. Issue docker volume ls -f name=dang
  11. Issue docker volume ls -f driver=vsphere
  12. Issue docker volume ls -f driver=vsph
  13. Issue docker volume create --name=labelVol --label=labeled
  14. Issue docker volume ls -f label=labeled
  15. Issue docker volume ls -f dangling=true -f name=dang
  16. Issue docker volume ls -f dangling=false -f name=dang

Expected Outcome:

  • Step 3 should result in each volume being listed with both driver and volume name
  • Step 4 should result in each volume being listed with only the volume name being listed
  • Step 5 should result in the following error:
Error response from daemon: Invalid filter 'bogusfilter'
  • Step 8 should result in only danglingVol being listed
  • Step 9 should result in only testVol being listed
  • Step 10 should result in only danglingVol being listed
  • Step 11 should result in danglingVol and testVol being listed
  • Step 12 should result in no volumes being listed
  • Step 14 should result in only labelVol being listed
  • Step 15 should result in only danglingVol being listed
  • Step 16 should result in no volumes being listed

Possible Problems:

  • VIC requires you to specify storage on creation of the VCH that volumes can be created from, so when installing the VCH make sure to specify this parameter: --volume-store=