Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

Architecture and Design description

tbd

HTML Comment
hiddentrue
  • 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
    • branding parameters or files introduced/changed
    • highlight parameters for performance tweaking
    • highlight how installation/upgrade scenarios change
  • deployment requirements (fresh install vs. upgrade) if any
  • system requirements: memory, CPU, desk space, etc
  • interoperability and compatibility requirements:
    • OS
    • xenserver, hypervisors
    • storage, networks, other
  • list localization and internationalization specifications 
  • 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)
Wiki Markup
{htmlcomment:hidden} * *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 ** branding parameters or files introduced/changed ** highlight parameters for performance tweaking ** highlight how installation/upgrade scenarios change * *deployment requirements (fresh install vs. upgrade) if any* * *system requirements: memory, CPU, desk space, etc* * *interoperability and compatibility requirements:* ** OS ** xenserver, hypervisors ** storage, networks, other * *list localization and internationalization specifications * * *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)* {htmlcomment}

Web Services APIs

As the gateway creates a network and the network offering for a nicira based network has a different 'Connectivity' provider then the default, a network offering must be passed as an optional argument to the createVpcGateway api call. This will be added by uuid.

...