Tweak k8s deployment footprint

Further reduce sizes of Rancher and orchestration VMs,
and use the savings to add another k8s compute VM.

Change-Id: Ie4976765d4ad3e2954886c746160f650ff9312ea
Issue-ID: INT-586
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
diff --git a/deployment/heat/onap-oom/env/windriver/onap-oom.env b/deployment/heat/onap-oom/env/windriver/onap-oom.env
index 2d28fd7..c611184 100644
--- a/deployment/heat/onap-oom/env/windriver/onap-oom.env
+++ b/deployment/heat/onap-oom/env/windriver/onap-oom.env
@@ -5,15 +5,17 @@
   apt_proxy: 10.12.5.2:8000
   docker_proxy: 10.12.5.2:5000
 
-  rancher_vm_flavor: m1.xlarge
+  rancher_vm_flavor: m1.large
   k8s_vm_flavor: m1.xlarge
   etcd_vm_flavor: m1.large
-  orch_vm_flavor: m1.xlarge
+  orch_vm_flavor: m1.large
 
   public_net_id: 971040b2-7059-49dc-b220-4fab50cb2ad4
 
   oam_network_cidr: 10.0.0.0/16
 
+  helm_deploy_delay: 2.5m
+
   integration_override_yaml: >
     global:
       repository: __docker_proxy__