513cebe7b7
* 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
750 B
750 B
Test 4-01 - Docker Integration
Purpose:
To verify that the VIC appliance passes the docker integration tests or at least any failure are characterized and well documented.
References:
Environment:
This test requires that a VIC appliance is available to execute the docker integration tests against
Test Steps:
- Deploy VIC appliance to a test server
- Execute the docker integration tests:
DOCKER_HOST=tcp://<VIP IP> go test
Expected Outcome:
VIC appliance needs to pass enough of the tests and for any failures, they need to be characterized, agreed that they are acceptable, and well documented.
Possible Problems:
None