apologies for the delay in sending my reply. It is not the best reply either. and I'm top-posting (so shameful)
For both the OVSDB and Netvirt project, the clustering suites we have (which are not based on any official (that I know of) written testplan) are the HA/Failover type wrapped around the existing functional system tests. essentially: do normal project system tests kill some controller(s) do normal project system tests bring back some controller(s) do normal project system tests for ovsdb boron/carbon, the 3node jobs are fine. There are some hiccups that need to be investigated. No bugs that I know of. for netvirt, I have no clue. yet. We have been working really hard to make 1node jobs get to 100% pass. we are almost there and just now talking about looking at the 3node failures. they do have failures. Thanks for all the hard work the controller/cluster team does, btw. JamO On 02/06/2017 05:31 AM, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) wrote: > Hello Test Contacts. > > > > In Controller project, our highest priority > > for Carbon release is to make sure ODL clustering > > is usable and stable. > > > > We are in the phase of formulating explicit acceptance criteria, > > so we can create execution plan for turning them into Robot suites. > > > > Of course, clustering is not very useful just by itself, > > it is used as a tool applications can use to reach their goals. > > So real acceptance criteria for clustering should also > > take into account whether ODL applications can work in cluster. > > > > Many projects are already running their 3node CSIT tests, > > but on one hand, some important scenarios might be not covered yet, > > and some suites might be too unstable to serve as acceptance tests. > > > > Controller team is small and busy, so we are asking for help. > > Here is a set of quick questions for test contacts: > > * Does your project have a test plan mentioning specific cluster scenarios? > > * Do you have any of such scenarios implemented as Robot suites? > > * Do the robot suites have failures, suspected to be caused by clustering > > (as opposed to application logic, or mistakes in Robot code)? > * Are there open Bugs corresponding to the clustering failures? > > * Are you planning to implement more Robot 3node suites until Carbon release? > > * Are there scenarios you would like Controller team to cover using mock apps? > > > > Vratko (as a Controller test contact). > > > > _______________________________________________ > controller-dev mailing list > controller-dev@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/controller-dev > _______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
