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
• list all open items or unresolved issues the developer is unable to decide about without further discussion
• quality risks (test guidelines)
  • functional
  • non functional: performance, scalability, stability, overload scenarios, etc
  • corner cases and boundary conditions
  • negative usage scenarios
• specify supportability characteristics:
  • what new logging (or at least the important one) is introduced
  • how to debug and troubleshoot
  • what are the audit events 
  • list JMX interfaces
  • graceful failure and recovery scenarios
  • possible fallback or work around route if feature does not work as expected, if those workarounds do exist ofcourse.
  • if feature depends other run-time environment related requirements, provide sanity check list for support people to run
• 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
  • 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.
  • system requirements: memory, CPU, desk space, etc
  • interoperability and compatibility requirements:
    • Hypervisors - VMware vSphere 4.1 or later
  • list localization and internationalization specifications 
    • UI changes in "Add Cluster" wizard. See the section "UI Flow".
  • explain the impact and possible upgrade/migration solution introduced by the feature 
  • explain performance & scalability implications when feature is used from small scale to large scale
  • explain security specifications
    • list your evaluation of possible security attacks against the feature and the answers in your design* *
  • explain marketing specifications
  • explain levels or types of users communities of this feature (e.g. admin, user, etc)
    admin
    Administrators would be target audience for this feature as this is at infrastructure level.

  ...

  • Add cluster wizard
    If hypervisor is VMware and global configuration parameter "vmware.use.dvswitch" is set to true, then display a list box that
    has 3 options with following labels.
  1. "VMware vNetwork Standard Virtual Switch"
     Action to perform if this option is selected:-
     Add a parameter to parameter list of AddClusterCmd API call.
     Parameter name: "vswitchtype"
     Parameter value: "vmwaresvs"
  1. "VMware vNetwork Distributed Virtual Switch"
     Action to perform if this option is selected:-
     Add a parameter to parameter list of AddClusterCmd API call.
     Parameter name: "vswitchtype"
     Parameter value: "vmwaredvs"
  1. "Cisco Nexus 1000v Distributed Virtual Switch"
     Action to perform if this option is selected:-
     Add a parameter to parameter list of AddClusterCmd API call.
     Parameter name: "vswitchtype"
     Parameter value: "nexusdvs"

  ...

  • • List Box label - "Virtual Switch Type"

  ...

  • • Default option - "VMware vNetwork Standard Virtual Switch"

  Appendix

  Appendix A:

  Appendix B: