d8dfun/virtual-kubelet
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

VMware vSphere Integrated Containers provider (#206)

Browse Source 
* 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
This commit is contained in:
Loc Nguyen
2018-06-04 15:41:32 -07:00
committed by Ria Bhatia
parent 98a111e8b7
commit 513cebe7b7
6296 changed files with 1123685 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
vendor/github.com/vmware/vic/tests/test-cases/Group3-Docker-Compose/3-03-Docker-Compose-Basic.md generated vendored Normal file
View File

@@ -0,0 +1,40 @@
Test 3-03 - Docker Compose Basic
=======
# Purpose:
To verify that VIC appliance can work when deploying the most basic example from docker documentation
# References:
[1 - Docker Compose Getting Started](https://docs.docker.com/compose/gettingstarted/)
# Environment:
This test requires that a vSphere server is running and available
# Test Steps:
1. Create a compose file that includes a basic python server and redis server
2. Deploy VIC appliance to the vSphere server
3. Create a basic compose yml file
4. Issue DOCKER_HOST=<VCH IP> docker-compose create
5. Issue DOCKER_HOST=<VCH IP> docker-compose start
6. Issue DOCKER_HOST=<VCH IP> docker-compose logs
7. Issue DOCKER_HOST=<VCH IP> docker-compose stop
8. Issue DOCKER_HOST=<VCH IP> docker-compose up -d
9. Issue DOCKER_HOST=<VCH IP> docker-compose kill redis
10. Issue DOCKER_HOST=<VCH IP> docker-compose down
11. Issue DOCKER_HOST=<VCH IP> docker run -d busybox /bin/top
12. Issue DOCKER_HOST=<VCH IP> docker-compose up -d
13. Create compose file with link
14. Issue DOCKER_HOST=<VCH IP> docker-compose up -d
15. Issue DOCKER_HOST=<VCH IP> docker-compose bundle
16. Issue DOCKER_HOST=<VCH IP> docker-compose --file compose-rename.yml up -d
17. Issue DOCKER_HOST=<VCH IP> docker-compose --file compose-rename.yml up -d --force-recreate
18. Issue DOCKER_HOST=<VCH IP> docker-compose --file compose-rename.yml up -d
19. Issue DOCKER_HOST=<VCH IP> docker-compose up (without -d)
20. Issue DOCKER_HOST=<VCH IP> docker-compose stop on the above container
21. Issue DOCKER_HOST=<VCH IP> docker-compose up (without -d) again
# Expected Outcome:
* Step 4-21 should result in no errors
# Possible Problems:
None