WIP: ROBO test plans

tests/manual-test-cases/Group5-Functional-Tests/5-x-ROBO-Container-Limit.md

@@ -0,0 +1,43 @@
+Test 5-x - ROBO - total container VM limit feature
+=======
+
+# Purpose:
+To verify that the total container VM limit feature works as expected in a vSphere ROBO Advanced environment.
+
+# References:
+* [vSphere Remote Office and Branch Office](http://www.vmware.com/products/vsphere/remote-office-branch-office.html)
+* [Limit total allowed containerVMs per VCH](https://github.com/vmware/vic/issues/7273)
+* [vic-machine inspect to report configured containerVM limit](https://github.com/vmware/vic/issues/7284)
+
+# Environment:
+This test requires access to VMware Nimbus cluster for dynamic ESXi and vCenter creation.
+
+# Test Steps:
+1. Deploy a ROBO vCenter testbed with x ESXi hosts and vSAN enabled
+2. Install the VIC appliance on vCenter with a container VM limit of x
+3. Use vic-machine inspect to verify the set container VM limit
+4. Create and run x containers with the VCH
+5. Attempt to create/run more than x containers with the VCH
+6. Use vic-machine configure to increase the container VM limit (new limit = y)
+7. Use vic-machine inspect to verify the new container VM limit
+8. Create more containers and verify that upto a total of y containers can be created
+9. Use vic-machine configure to set the limit to lower than the current number of containers created/running
+10. Attempt to create/run more containers
+11. Delete/stop some containers so the current container VM count is lower than the set limit
+12. Attempt to create/run more containers until the set limit
+13. Delete the VCH
+
+# Expected Outcome:
+* Steps 1 and 2 should succeed
+* Step 3's output should indicate the limit set in Step 2
+* Step 4 should succeed
+* Step 5 should fail and should receive an error upon attempting to create/start "surplus" container VMs (exact create/start behavior TBD)
+* Step 6 should succeed
+* Step 7's output should indicate the limit set in Step 6
+* Step 8 should succeed
+* Step 9 should succeed - exact behavior of "surplus" container VMs is TBD
+* Step 10 should fail and should receive an error upon attempting to create/start "surplus" container VMs (exact create/start behavior TBD)
+* Steps 11-13 should succeed
+
+# Possible Problems:
+None

tests/manual-test-cases/Group5-Functional-Tests/5-y-ROBO-VM-Placement.md

@@ -0,0 +1,34 @@
+Test 5-y - ROBO - VM placement without DRS
+=======
+
+# Purpose:
+To verify that the VM placement feature specified works as expected in a vSphere ROBO Advanced environment without DRS.
+The current placement strategy is to avoid bad host selection, instead of selecting the "best" possible host.
+
+# References:
+* [vSphere Remote Office and Branch Office](http://www.vmware.com/products/vsphere/remote-office-branch-office.html)
+* [VM Placement without DRS](https://github.com/vmware/vic/issues/7282)
+
+# Environment:
+This test requires access to VMware Nimbus cluster for dynamic ESXi and vCenter creation.
+
+# Test Steps:
+1. Deploy a ROBO vCenter testbed with x ESXi hosts and vSAN enabled
+2. Install the VIC appliance on vCenter
+3. Create and run several containers in succession
+4. Gather host metrics and check container placements
+5. Delete the containers created in Step 3
+6. Create and run several containers in parallel
+7. Gather host metrics and check container placements
+8. Delete the containers created in Step 5
+9. Run the regression test suite
+10. Delete the VCH
+
+# Expected Outcome:
+* All steps should succeed.
+* In Step 2, the VCH should be placed on a host that satisfies the license and other feature requirements.
+* In Steps 3 and 6, containers shouldn't fail to be created/started unless the cluster resources/limits are exhausted.
+* In Steps 4 and 7, containers should be placed according to the criteria defined in [Purpose](#purpose). More details are TBD.
+
+# Possible Problems:
+None