Page History

...

• put a summary or a brief description of the feature in question 
• list what is deliberately not supported or what the feature will not offer - to clear any prospective ambiguities
• quality risks (test guidelines)
  • functional
  • non functional: performance, scalability, stability, overload scenarios, etc
  • negative usage scenarios
  • what are the audit events 
    ***All virtul network orchestration events
    ***VM migration events
  • graceful failure and recovery scenarios
  • possible fallback or work around route if feature does not work as expected, if those workarounds do exist ofcourse.
• explain configuration characteristics:
  • configuration parameters or files introduced/changed
    New configuration parameter - "vmware.use.dvswitch" of type Boolean. Possible values are "true" or "false". Default value is "false".
  • branding parameters or files introduced/changed - NA
  • highlight parameters for performance tweaking - NA
  • highlight how installation/upgrade scenarios change
• deployment requirements (fresh install vs. upgrade) if any
  • VMware dvSwitch must be already created/configured in the vCenter datacenter deployment.
  • All the host/clusterresources should be added to dvSwitch before adding the cluster to CloudStack's pod cluster.

...