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

1.7 KiB

Raw Blame History

Test 13-1 vMotion VCH Appliance

Purpose:

To verify the VCH appliance continues to function properly after being vMotioned to a new host

References:

1- vMotion A Powered On Virtual Machine

Environment:

This test requires that a vCenter server is running and available

Test Steps:

Install a new VCH appliance onto one of the hosts within the vCenter server
Power down the VCH appliance
vMotion the VCH appliance to a new host
Power on the VCH appliance and run a variety of docker commands
Delete the VCH appliance
Install a new VCH appliance onto one of the hosts within the vCenter server
While the VCH appliance is powered on, vMotion the VCH appliance to a new host
Run a variety of docker commands on the VCH appliance after it has moved
Delete the VCH appliance
Install a new VCH appliance onto on the hosts within the vCenter server
Create several containers on the new VCH appliance that are in the following states: created but not started, started and running, started and stopped, stopped after running and being attached to, running after being attached to but currently not attached to, running and currently attached to
vMotion the VCH appliance to a new host
Complete the life cycle of the containers created in Step 11, including getting docker logs and re-attaching to containers that are running

Expected Outcome:

In each scenario, the VCH appliance should continue to work as expected after being vMotioned and all docker commands should return without error

Possible Problems:

None

1.7 KiB Raw Blame History