[
https://issues.apache.org/jira/browse/AIRAVATA-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14383943#comment-14383943
]
Suresh Marru commented on AIRAVATA-1650:
----------------------------------------
Hi Chathuri, thank you for jumping on this topic, this should be incredibly
useful to authoritatively declare Airavata is ready for production. I have
following suggestion:
* I see that the goal is in general to come up with a test framework for
Airavata agnostic to a particular feature (like multi tenancy). For each
release this goal might change based on the targeted features for that release.
* If a particular feature is tested with this framework, we could mark it as a
supported.
* The requirement list of good for the current target of multi-tenancy.
The steps specified in the document look good. I have a meta comment:
We probably should clearly have three category of tests: Acceptance Tests,
Scalability Tests and Reliability Tests
* Acceptance Tests - These test through the targeted advertised feature with
both positive and negative scenarios. This could include automatic or manual
fault injection.
* Scalability Tests - While Acceptance tests ensures few instances of tests
pass successfully, scalability tests can focus on running the same tests
multiple times. These should bring out sporadic resource usages (memory, i/o,
cpu, threads, sockets, file handles), race conditions and concurrency limits of
a single instance. This information should be very helpful for load balancing
and replication of services.
Reliability Tests - The focus can be to ensure there are no resource leaks, and
as much as possible the system is auto-recovering. A service goes down, load is
reshuffled or restarted after a component is back up.
> Come up with a document to gather requirements and define the architecture
> --------------------------------------------------------------------------
>
> Key: AIRAVATA-1650
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1650
> Project: Airavata
> Issue Type: Sub-task
> Reporter: Chathuri Wimalasena
> Assignee: Chathuri Wimalasena
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
