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
2.7 KiB
2.7 KiB
Test 1-23 - Docker Inspect
Purpose:
To verify that docker inspect command is supported by VIC appliance
References:
1 - Docker Command Line Reference
Environment:
This test requires that a vSphere server is running and available
Test Steps:
- Deploy VIC appliance to vSphere server
- Issue docker pull busybox to the VIC appliance
- Issue docker inspect busybox to the VIC appliance
- Issue docker inspect --type=image busybox to the VIC appliance
- Issue docker inspect --type=container busybox to the VIC appliance
- Issue docker create busybox to the VIC appliance
- Issue docker inspect to the VIC appliance
- Issue docker inspect --type=container to the VIC appliance
- Issue docker inspect to the VIC appliance and verify the Cmd and Image fields
- Issue docker inspect --type=image to the VIC appliance
- Issue docker network create net-one
- Issue docker network create net-two
- Issue docker create --network net-one --name two-net-test busybox
- Issue docker network connect net-two two-net-test
- Issue docker start two-net-test
- Issue docker inspect -f '{{range $key, $value := .NetworkSettings.Networks}}{{$key}}{{end}}' two-net-test
- Issue docker inspect fake to the VIC appliance
- Issue docker create -v /var/lib/test busybox
- Issue docker inspect -f {{.Config.Volumes}}
- Issue docker inspect test-with-volume | jq '.[]|.["Config"]|.["Volumes"]|keys[0]' and docker volume ls
- Issue docker inspect busybox -f '{{.RepoDigest}}'
- Issue docker inspect on container with both an anonymous and named volume bound to mount points
- Issue docker inspect container status across container lifecycle (created, running, exited)
Expected Outcome:
- Step 3,4,7,8 should result in success and a properly formatted JSON response
- Step 5 should result in an error with the following message:
Error: No such container: busybox
- Step 9 should result in success with the correct values in the Cmd and Image fields
- Step 10 should result in an error with the following message:
Error: No such image: <containerID>
- Step 16 should result in two networks listed in the inspect data
- Step 17 should result in an error with the following message:
Error: No such image or container: fake
- Step 19 should result in the map returned containing /var/lib/test
- Step 20 should find matching volume ID matching in docker inspect in volume ls
- Step 21 should result in a valid digest, previously cached
- Step 22 should result in valid Mounts data
- Step 23 should result in correct container status values (created, running, exited)
Possible Problems:
None