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

855 B

Raw Blame History

Test 5-2 - Cluster

Purpose:

To verify the VIC appliance works when the vCenter appliance is using a cluster

References:

1 - VMware vCenter Server Availability Guide

Environment:

This test requires access to VMWare Nimbus cluster for dynamic ESXi and vCenter creation

Test Steps:

Deploy a new vCenter with 3 ESXi hosts in a cluster:
govc cluster.create cls
Install the VIC appliance into the cluster using the cluster path as the compute resource:

--compute-resource /ha-datacenter/host/cls

Run a variety of docker commands on the VCH appliance

Expected Outcome:

The VCH appliance should deploy without error and each of the docker commands executed against it should return without error

Possible Problems:

None

855 B Raw Blame History