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-13-Docker-Version.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.7 KiB
Raw Blame History

Test 1-13 - Docker Version

Purpose:

To verify that docker version 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 the vSphere server
  2. Issue a docker version command to the new VIC appliance
  3. Issue a docker version --format '{{.Client.Version}}' command to the new VIC appliance
  4. Issue a docker1.11 version --format '{{.Client.APIVersion}}' command to the new VIC appliance
  5. Issue a docker1.13 version --format '{{.Client.APIVersion}}' command to the new VIC appliance
  6. Issue a docker version --format '{{.Client.GoVersion}}' command to the new VIC appliance
  7. Issue a docker version --format '{{.Server.Version}}' command to the new VIC appliance
  8. Issue a docker1.11 version --format '{{.Server.APIVersion}}' command to the new VIC appliance
  9. Issue a docker1.13 version --format '{{.Server.APIVersion}}' command to the new VIC appliance
  10. Issue a docker1.13 version --format '{{.Server.MinAPIVersion}}' command to the new VIC appliance
  11. Issue a docker version --format '{{.Server.GoVersion}}' command to the new VIC appliance
  12. Issue a docker version --format '{{.fakeItem}}' command to the new VIC appliance

Expected Outcome:

  • VIC appliance should respond with a properly formatted version response, it should be capable of returning each individual field as well without error.
  • The server version field should indicate that it is VIC.
  • Step 6 should result in an error indicating: fakeItem is not a field of struct type types.VersionResponse

Possible Problems:

None