Files

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

812 B

Raw Blame History

Test 11-9 - Container Disk Stress

Purpose:

To verify the VIC appliance works when stressing the appliance with a lot of disk operations

References:

None

Environment:

This test requires that a vSphere server is running and available

Test Steps:

Install a new VCH appliance into the vSphere server
Create a container with a 10GB volume attached
Within the container, execute bonnie++ disk stress test
Run a variety of docker commands on the VCH appliance

Expected Outcome:

The bonnie++ command should return without error and at the end, the variety of docker commands run should work without error

Possible Problems:

If you exhaust the resources of the vSphere server, it is not necessarily a failure as long as the VCH appliance continues to function and behave as expected

812 B Raw Blame History