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-05-Docker-Start.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-05 - Docker Start

Purpose:

To verify that docker start 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 -it busybox /bin/top to VIC appliance
  3. Issue docker start
  4. Issue docker create vmware/photon
  5. Issue docker start vmware/photon
  6. Issue docker start fakeContainer
  7. Create a container, remove it's ethernet adapter, then start the container
  8. Create and start 5 busybox containers running /bin/top serially
  9. Create and start 5 ubuntu containers running /bin/top serially
  10. Create and start 5 busybox containers running /bin/top all at once
  11. Run a container with a test-network, stop the container, remove the test-network, then start the container again
  12. Issue docker start -a to a busybox ls container

Expected Outcome:

  • Commands 1-5 should all return without error and respond with the container ID
  • After commands 3 and 5 verify that the containers are running
  • Step 6 should result in the VIC appliance returning the following error:
Error response from daemon: No such container: fakeContainer
Error: failed to start containers: fakeContainer
  • Step 7 should result in an error message stating unable to wait for process launch status
  • Steps 8-11 should all result in all containers succeeding and not throwing any errors
  • Step 11 should result in the VIC appliance returning the following error:
Error response from daemon: Server error from portlayer: network test-network not found
Error: failed to start containers: containerID
  • Step 12 should succeed and provide the output from the ls command to the screen

Possible Problems:

None