d8dfun/virtual-kubelet
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity
Files
513cebe7b7cf590cd53c02ea8da1a20b58dd8f18
virtual-kubelet/vendor/github.com/vmware/vic/tests/test-cases/Group9-VIC-Admin/9-01-VICAdmin-ShowHTML.md
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

3.0 KiB
Raw Blame History

Test 9-01 - VIC Admin ShowHTML

Purpose:

To verify that the VIC Administration appliance can display HTML

Environment:

This test requires that a vSphere environment be running and available

Test Steps:

  1. Deploy VIC appliance to the vSphere server
  2. Pull the VICadmin web page and verify that it contains valid HTML
  3. Pull the Portlayer log file and verify that it contains valid data
  4. Pull the VCH-Init log and verify that it contains valid data
  5. Pull the Docker Personality log and verify that it contains valid data
  6. Create a container via the appliance
  7. Pull the container log bundle from the appliance and verify that it contains the new container's logs

Expected Outcomes:

  • VICadmin should display a web page that at a minimum includes
  • VICadmin responds with a log file indicating that the portlayer sever has started
  • VICadmin responds with a log file indicating VCH init has begun reaping processes
  • VICadmin responds with log file indicating docker personality service has started
  • VICadmin responds with a ZIP file containing at a minimum the vmware.log file from the new container

Unauthenticated Test Cases

Get Login Page

  1. Access the authentication web page

While Logged Out Fail To Display HTML

  1. Required authentication on restricted pages
  2. Page requests authentication

While Logged Out Fail To Get Portlayer Log

  1. Portlayer logs are restricted to authenticated users
  2. Page requests authentication

While Logged Out Fail To Get VCH-Init Log

  1. VCH_Init logs are restricted to authenticated users
  2. Page requests authentication

While Logged Out Fail To Get Docker Personality Log

  1. Personality logs are restricted to authenticated users
  2. Page requests authentication

While Logged Out Fail To Get Container Logs

  1. Container logs are restricted to authenticated users
  2. Page requests authentication

While Logged Out Fail To Get VICAdmin Log

  1. VICAdmin logs are restricted to authenticated users
  2. Page requests authentication

Authenticated Test Cases

Display HTML

  1. Log in
  2. Page displays vic-machine name in title

Get Portlayer Log

  1. Log in
  2. Portlayer Log access is allowed and logs are downloaded

Get VCH-Init Log

  1. Log in
  2. VCH-Init Log access is allowed and logs are downloaded

Get Docker Personality Log

  1. Log in
  2. Docker Personality Log access is allowed and logs are downloaded

Get Container Logs

  1. Log in
  2. Container Log access is allowed and logs are downloaded

Get VICAdmin Log

  1. Log in
  2. VICAdmin Log access is allowed and logs are downloaded

Check that VIC logs do not contain sensitive data

  1. Log in
  2. Fetch all logs in /logs/ path
  3. None of the downloaded logs contain the vch or vSphere password

Wan Routes Through Proxy

  1. Start a vch with a proxy defined at a localhost port. The proxy isn't actually running, so all requests will fail. IF the wan requests fail we know they were routed through the proxy.
  2. Log in to VICAdmin
  3. Verify wan health check is not successful.