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
This commit is contained in:
26
vendor/github.com/vmware/vic/tests/manual-test-cases/Group16-WindowsClient/16-1-Windows-VIC-Machine.md
generated
vendored
Normal file
26
vendor/github.com/vmware/vic/tests/manual-test-cases/Group16-WindowsClient/16-1-Windows-VIC-Machine.md
generated
vendored
Normal file
@@ -0,0 +1,26 @@
|
||||
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
|
||||
53
vendor/github.com/vmware/vic/tests/manual-test-cases/Group16-WindowsClient/16-1-Windows-VIC-Machine.robot
generated
vendored
Normal file
53
vendor/github.com/vmware/vic/tests/manual-test-cases/Group16-WindowsClient/16-1-Windows-VIC-Machine.robot
generated
vendored
Normal file
@@ -0,0 +1,53 @@
|
||||
# Copyright 2016-2017 VMware, Inc. All Rights Reserved.
|
||||
#
|
||||
# Licensed under the Apache License, Version 2.0 (the "License");
|
||||
# you may not use this file except in compliance with the License.
|
||||
# You may obtain a copy of the License at
|
||||
#
|
||||
# http://www.apache.org/licenses/LICENSE-2.0
|
||||
#
|
||||
# Unless required by applicable law or agreed to in writing, software
|
||||
# distributed under the License is distributed on an "AS IS" BASIS,
|
||||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
||||
# See the License for the specific language governing permissions and
|
||||
# limitations under the License
|
||||
|
||||
*** Settings ***
|
||||
Documentation Test 16-1 - Windows VIC Machine
|
||||
Resource ../../resources/Util.robot
|
||||
Test Setup Set Test Environment Variables
|
||||
|
||||
*** Variables ***
|
||||
${ver} 8351
|
||||
|
||||
*** Keywords ***
|
||||
Cleanup Folders
|
||||
${output}= Execute Command rm -Recurse -Force vic*
|
||||
${output}= Execute Command rm *.pem
|
||||
|
||||
*** Test Cases ***
|
||||
Install VCH With TLS
|
||||
Open Connection %{WINDOWS_URL} prompt=>
|
||||
Login %{WINDOWS_USERNAME} %{WINDOWS_PASSWORD}
|
||||
Cleanup Folders
|
||||
${output}= Execute Command wget https://storage.googleapis.com/vic-engine-builds/vic_${ver}.tar.gz -OutFile vic.tar.gz
|
||||
${output}= Execute Command 7z x vic.tar.gz
|
||||
${output}= Execute Command 7z x vic.tar
|
||||
${output}= Execute Command ./vic/vic-machine-windows.exe create --target %{TEST_URL} --user %{TEST_USERNAME} --password %{TEST_PASSWORD}
|
||||
Get Docker Params ${output} ${true}
|
||||
Run Regression Tests
|
||||
${output}= Execute Command ./vic/vic-machine-windows.exe delete --target %{TEST_URL} --user %{TEST_USERNAME} --password %{TEST_PASSWORD}
|
||||
Cleanup Folders
|
||||
|
||||
Install VCH Without TLS
|
||||
Open Connection %{WINDOWS_URL} prompt=>
|
||||
Login %{WINDOWS_USERNAME} %{WINDOWS_PASSWORD}
|
||||
Cleanup Folders
|
||||
${output}= Execute Command wget https://storage.googleapis.com/vic-engine-builds/vic_${ver}.tar.gz -OutFile vic.tar.gz
|
||||
${output}= Execute Command 7z x vic.tar.gz
|
||||
${output}= Execute Command 7z x vic.tar
|
||||
${output}= Execute Command ./vic/vic-machine-windows.exe create --target %{TEST_URL} --user %{TEST_USERNAME} --password %{TEST_PASSWORD} --no-tls
|
||||
Get Docker Params ${output} ${false}
|
||||
Run Regression Tests
|
||||
${output}= Execute Command ./vic/vic-machine-windows.exe delete --target %{TEST_URL} --user %{TEST_USERNAME} --password %{TEST_PASSWORD}
|
||||
Cleanup Folders
|
||||
6
vendor/github.com/vmware/vic/tests/manual-test-cases/Group16-WindowsClient/TestCases.md
generated
vendored
Normal file
6
vendor/github.com/vmware/vic/tests/manual-test-cases/Group16-WindowsClient/TestCases.md
generated
vendored
Normal file
@@ -0,0 +1,6 @@
|
||||
Group 16 - Windows Client
|
||||
=======
|
||||
|
||||
|
||||
[Test 16-1 - Windows VIC Machine](16-1-Windows-VIC-Machine.md)
|
||||
-
|
||||
Reference in New Issue
Block a user