d8dfun/virtual-kubelet
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity
Files
027b76651da0735fa84758d8d7928e336afaf791
virtual-kubelet/vendor/github.com/vmware/vic/tests/manual-test-cases/Group16-WindowsClient/16-1-Windows-VIC-Machine.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

806 B
Raw Blame History

Test 16-1 Windows VCH Install

Purpose:

To verify the VCH appliance can be installed and used from a windows based client

References:

  • vic-machine-windows.exe -h

Environment:

This test requires that a vSphere server is running and available and a windows client

Test Steps:

  1. From the windows client, download the latest VIC release
  2. From within the release package, run vic-machine-windows.exe to install the VCH into the vSphere server with TLS enabled
  3. Run a variety of docker commands on the new VCH
  4. Delete the VCH
  5. Install a new VCH server with TLS disabled
  6. Run a variety of docker commands on the new VCH
  7. Delete the VCH

Expected Outcome:

Each VCH should install properly and all docker commands executed should complete without error

Possible Problems:

None