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-07-Docker-Stop.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.6 KiB
Raw Blame History

Test 1-07 - Docker Stop

Purpose:

To verify that docker stop 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 create busybox sleep 30 to the VIC appliance
  3. Issue docker stop to the VIC appliance
  4. Issue docker start to the VIC appliance
  5. Issue docker stop to the VIC appliance
  6. Issue docker start to the VIC appliance
  7. Issue docker stop -t 2 to the VIC appliance
  8. Issue docker stop fakeContainer to the VIC appliance
  9. Create a new container, start the container using govc/UI, attempt to stop the container using docker stop
  10. Start a new container, stop it, then attempt to restart it again
  11. Start a new container, stop it with Docker 1.13 CLI

Expected Outcome:

  • Steps 2-8 should each complete without error, and the response should be the containerID
  • Step 5 should take 10 seconds to complete
  • Step 7 should take 2 seconds to complete
  • Step 8 should respond with the following error message:
Failed to stop container (fakeContainer): Error response from daemon: No such container: fakeContainer
  • Step 9 should result in the container stopping successfully
  • Step 10 should result in the container starting without error the second time
  • Step 11 should result in the container stopping successfully

Possible Problems:

None