Files
virtual-kubelet/vendor/github.com/vmware/vic/tests/test-cases/Group6-VIC-Machine/6-18-Container-Name-Convention.robot
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

60 lines
2.6 KiB
Plaintext

# Copyright 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 6-18 - Container Name Convention
Resource ../../resources/Util.robot
Test Teardown Cleanup VIC Appliance On Test Server
Test Timeout 20 minutes
*** Test Cases ***
Container name convention with id
Set Test Environment Variables
Install VIC Appliance To Test Server With Current Environment Variables additional-args=--container-name-convention %{VCH-NAME}-{id}
Run docker %{VCH-PARAMS} pull ${busybox}
${containerID}= Run docker %{VCH-PARAMS} run -d ${busybox}
${shortId}= Get container shortID ${containerID}
${output}= Run govc ls vm
Should Contain ${output} %{VCH-NAME}-${shortID}
Run docker %{VCH-PARAMS} rename ${containerID} renamed-container
${output}= Run govc ls vm
# confirm that the cnc is still in force
Should Contain ${output} %{VCH-NAME}-${shortID}
Run docker %{VCH-PARAMS} rm -f ${containerID}
Run Regression Tests
Container name convention with name
Set Test Environment Variables
Install VIC Appliance To Test Server With Current Environment Variables additional-args=--container-name-convention %{VCH-NAME}-{name}
Run docker %{VCH-PARAMS} pull ${busybox}
${containerID}= Run docker %{VCH-PARAMS} run -d ${busybox}
${name}= Get container name ${containerID}
${output}= Run govc ls vm
Should Contain ${output} %{VCH-NAME}-${name}
Run docker %{VCH-PARAMS} rename ${containerID} renamed-container
${output}= Run govc ls vm
# confirm that the cnc is still in force but updated for new container name
Should Contain ${output} %{VCH-NAME}-renamed-container
Run docker %{VCH-PARAMS} rm -f ${containerID}
Run Regression Tests
Container name convention with invalid argument
${rc} ${output}= Run Keyword And Ignore Error Install VIC Appliance To Test Server additional-args=--container-name-convention 192.168.1.1-mycontainer
Should Contain ${output} Container name convention must include {id} or {name} token
[Teardown] Log To Console Test passed no need to run cleanup