Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In order to plan for the proper Platform Maturity requirements and levels for CasblancaCasablanca, we would like to gather feedback from the community.  We welcome feedback from all, but especially:

...

Please leave your feedback as comments to this wiki page.

THANK YOU!


Security Subcommittee Feedback


Architecture Subcommittee Feedback (from Vancouver Session)

  • Stability: 72 hours platform level soak with random transaction. (not just component-level, such as we did for Beijing). TSC has to approve this. We have to understand the resources needed for this, as it may require more lab resources.
  • Resiliency: level 3 for run-time projects (proposal). N/C for design-time projects
  • Security: see above from Security Subcommittee
  • Scalability: stay level for 1 run-time. Horizontal scaling up and down.
  • Manageability: level 2 for upgrade a single cpt (1 cpt at a time) with no loss of data.
  • Usability: more discussion with wider group needed

Presentation for the discussion session held 20June2018 in Beijing.  

View file
namePlatform Maturity S3P Discussion 20June2018.pdf
height250


Presentation as presented to TSC on 21June2018:

View file
namePlatform Maturity S3P Casablanca Proposal 21June2018v2.pdf
pageTSC 2018-06-21 (Beijing)
spaceMeetings
height250


Updates to presentation based on feedback from the TSC:

View file
namePlatform Maturity S3P Casablanca Proposal 21June2018v3.pdf
height250