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/Group6-VIC-Machine/6-15-Syslog.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

1.2 KiB
Raw Blame History

Test 6-15 - Verify vic-machine syslog-address

Purpose:

Verify remote syslog for VCH

References:

  • vic-machine-linux create -h

Environment:

This test requires that a vSphere server is running and available This test requires that a syslog server is running and available

Test Steps

  1. Deploy VIC appliance with debug logs enabled, and syslog server specified
  2. Enable SSH on VIC appliance
  3. Open SSH connection to VIC appliance
  4. Get PIDs of running VIC daemons on VIC appliance
  5. Open SSH connection to syslog server
  6. Get contents of syslog file from syslog server
  7. Verify syslog messages from all daemons exist on the syslog server
  8. Run docker ps -a
  9. Get contents of syslog file from syslog server
  10. Verify messages generated by docker ps -a are on the syslog server
  11. Run a variety of docker commands
  12. Get contents of syslog file from syslog server

Expected Outcome

  • Step 6 output should have messages of the form [] for docker-engine-server, port-layer-server, vic-init, and vicadmin
  • Step 9 output should contain output of the form docker-engine-server[]: Calling GET /v1.25/containers/json?all=1
  • Step 12 output should contain the output of the variety of docker commands