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-14-Update-Firewall.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.3 KiB
Raw Blame History

Test 6-14 - Verify vic-machine update firewall function

Purpose:

Verify vic-machine update firewall

References:

  • vic-machine-linux update firewall -h

Environment:

This test requires that a vSphere server is running and available

Update

Enable and disable VIC firewall rule

  1. Get state of host firewall
  2. Enable host firewall
  3. Verify host firewall enabled
  4. Enable VIC firewall rule by issuing the following command:
bin/vic-machine-linux update firewall --target %{TEST_URL} \
    --user=%{TEST_USERNAME} --password=%{TEST_PASSWORD} \
    --compute-resource=%{TEST_RESOURCE} --timeout %{TEST_TIMEOUT} \
    --allow
  1. Verify state of rule by issuing the following command:
govc host.esxcli network firewall ruleset list --ruleset-id=vSPC
  1. Create VCH
  2. Run regression tests
  3. Disable VIC firewall rule by issuing the following command:
bin/vic-machine-linux update firewall --target %{TEST_URL} \
    --user=%{TEST_USERNAME} --password=%{TEST_PASSWORD} \
    --compute-resource=%{TEST_RESOURCE} --timeout %{TEST_TIMEOUT} \
    --deny
  1. Verify state of rule by issuing the following command:
govc host.esxcli network firewall ruleset list --ruleset-id=vSPC
  1. Revert state of host firewall

Expected Outcome

  • Firewall rule state changes as expected
  • Regression tests pass