{"action":"closed","issue":{"url":"https://api.github.com/repos/vmware/kubernetes/issues/288","repository_url":"https://api.github.com/repos/vmware/kubernetes","labels_url":"https://api.github.com/repos/vmware/kubernetes/issues/288/labels{/name}","comments_url":"https://api.github.com/repos/vmware/kubernetes/issues/288/comments","events_url":"https://api.github.com/repos/vmware/kubernetes/issues/288/events","html_url":"https://github.com/vmware/kubernetes/issues/288","id":259243359,"number":288,"title":"Functional Tests","user":{"login":"divyenpatel","id":22985595,"avatar_url":"https://avatars3.githubusercontent.com/u/22985595?v=4","gravatar_id":"","url":"https://api.github.com/users/divyenpatel","html_url":"https://github.com/divyenpatel","followers_url":"https://api.github.com/users/divyenpatel/followers","following_url":"https://api.github.com/users/divyenpatel/following{/other_user}","gists_url":"https://api.github.com/users/divyenpatel/gists{/gist_id}","starred_url":"https://api.github.com/users/divyenpatel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/divyenpatel/subscriptions","organizations_url":"https://api.github.com/users/divyenpatel/orgs","repos_url":"https://api.github.com/users/divyenpatel/repos","events_url":"https://api.github.com/users/divyenpatel/events{/privacy}","received_events_url":"https://api.github.com/users/divyenpatel/received_events","type":"User","site_admin":false},"labels":[{"id":660564787,"url":"https://api.github.com/repos/vmware/kubernetes/labels/Epic","name":"Epic","color":"3E4B9E","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2017-09-20T17:33:42Z","updated_at":"2017-11-20T17:10:02Z","closed_at":"2017-11-20T17:10:02Z","author_association":"NONE","body":"vSphere Cloud Provider on Kubernetes is tested with following Function tests.\r\n**This EPIC will be used to attach the new proposed functional test for vSphere Cloud Provider.**\r\n\r\n### PV/PVC, StorageClass and Basic Volume Plugin functional tests\r\n\r\n- Create and delete pod with the same volume source on the same worker node\r\n- Create and delete pod with the same volume source attach/detach to different worker nodes\r\n- Create and delete pod with multiple volumes from same datastore\r\n- Create and delete pod with multiple volumes from different datastore\r\n- Back to back pod creation and deletion with different volume sources on the same worker node\r\n- Verify persistent volume should be deleted when reclaimPolicy on the PV is set to delete and associated claim is deleted\r\n- Verify persistent volume should be retained when reclaimPolicy on the PV is set to retain and associated claim is deleted\r\n- Verify volume with the matching label is bounded with the PVC. This is function test for Selector-Label Volume Binding Feature.\r\n- Node Label Selector - Test Back-to-back pod creation/deletion with the same volume source on the same worker node\r\n- Node Label Selector - Test Back-to-back pod creation/deletion with the same volume source attach/detach to different worker nodes\r\n- Diskformat Verification - Verify diskformat specified in storage-class is being honored while volume creation.\r\n- Filesystem type test - Verify volume attached to the POD is mounted on the container with correct file system.\r\n\r\n### Ops storm\r\nTest creating POD with many volumes (30 Volumes) and verify no attach call fails.\r\n\r\n\r\n### SPBM Policy\r\n\r\n- Verify VSAN storage capability with valid hostFailuresToTolerate and cacheReservation values is honored for dynamically provisioned pvc using storageclass\r\n- Verify VSAN storage capability with valid diskStripes and objectSpaceReservation values is honored for dynamically provisioned pvc using storageclass\r\n- Verify VSAN storage capability with valid diskStripes and objectSpaceReservation values and a VSAN datastore is honored for dynamically provisioned pvc using storageclass\r\n- Verify VSAN storage capability with valid objectSpaceReservation and iopsLimit values is honored for dynamically provisioned pvc using storageclass\r\n- Verify VSAN storage capability with invalid capability name objectSpaceReserve is not honored for dynamically provisioned pvc using storageclass\r\n- Verify VSAN storage capability with invalid diskStripes value is not honored for dynamically provisioned pvc using storageclass\r\n- Verify VSAN storage capability with invalid hostFailuresToTolerate value is not honored for dynamically provisioned pvc using storageclass\r\n- Verify VSAN storage capability with non-vsan datastore is not honored for dynamically provisioned pvc using storageclass\r\n- Verify an existing and compatible SPBM policy is honored for dynamically provisioned pvc using storageclass\r\n- Verify if a SPBM policy is not honored on a non-compatible datastore for dynamically provisioned pvc using storageclass\r\n- Verify if a non-existing SPBM policy is not honored for dynamically provisioned pvc using storageclass\r\n- Verify an if a SPBM policy and VSAN capabilities cannot be honored for dynamically provisioned pvc using storageclass\r\n\r\n\r\n### Negative Tests - Kubelet Restart, Namespace Deletion, Delete PVC when PV is attached to the POD.\r\n- Test to verifiy that a volume mounted to a pod that is deleted while the kubelet is down, unmounts volume when the kubelet returns.\r\n- Test to verify that deleting the Namespace of a PVC and Pod causes the successful detach of Persistent Disk.\r\n- Test to verify that a volume mounted to a pod remains mounted after a kubelet restarts.\r\n- Test to delete the PVC and then the pod.  Expect the pod to succeed in unmounting and detaching PD on delete\r\n\r\n\r\n"}}
{"actor":{"display_login":"divyenpatel"}}