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/test-cases/Group6-VIC-Machine/6-08-Create-Compute.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

2.1 KiB
Raw Blame History

Test 6-08 - Verify vic-machine create compute-resource verification

Purpose:

Verify vic-machine create compute resource parsing

References:

  • vic-machine-linux create -h

Environment:

This test requires that a vSphere server is running and available

Wrong absolute path

Test Steps

  1. Create with compute resource set wrongDC:malformat
  2. Create with compute resource set to /WrongDC/cluster/
  3. Create with compute resource set to /DC/cluster/host/rp
  4. Verify creation failed correctly

Correct absolute path

Test Steps

  1. Create with compute resource set to /DC/host/cluster/Resources/rp
  2. Verify creation passed successfully
  3. Verify VCH is created in the correct place though govc

Wrong relative path

Test Steps

  1. Prepare env with multiple VC clusters and multiple available resource pools
  2. Create with compute resource set to wrongRP1 (wrongRP1 does not exist)
  3. Create with compute resource set to wrongCluster (wrongCluster does not exist)
  4. Create with compute resource set to RP1 (RP1 exists in one cluster)
  5. Create with compute resource set to Cluster1 (Cluster1 exists)
  6. Verify creation failed correctly

Correct relative path with single VC cluster

Test Steps

  1. Prepare env single VC cluster
  2. Create with compute resource set to (real cluster name here)
  3. Create with compute resource set to RP1 (RP1 exists in cluster)
  4. Create with compute resource not set
  5. Verify deployed successfully
  6. Verify VCH is created in the correct place though govc

Correct relative path with ESXi

Test Steps

  1. Test in ESXi
  2. Create with compute resource set to RP1 (RP1 exists in cluster)
  3. Create with compute resource not set
  4. Verify deployed successfully
  5. Verify VCH is created in the correct place though govc

Correct relative path in multiple VC cluster

Test Steps

  1. Prepare env with multiple VC clusters and multiple available resource pools
  2. Create with compute resource set to Cluster (Cluster exists)
  3. Create with compute resource set to Cluster/RP1 (Cluster/RP1 exists in cluster)
  4. Verify deployed successfully
  5. Verify VCH is created in the correct place though govc