On 20/07/18 16:54, Daniel Farrell wrote: > > I feel like blaming infrastructure being "slow" is too easy an > excuse for issues. If the software was run in a customer production > environment I suspect telling the customer that their hardware is > too slow and is not the same hardware as the developer's laptop it > would not be a solution the customer would be happy with. > > > +1000 > > Our code and tests need to be robust enough to handle diverse > infrastructure. Bugs like this might be highlighted by infra > variability, but they are still bugs in code/tests. > > Not picking on TomP or Controller here, this is a general ODL culture > problem of blaming the infra first and until Thanh/Jamo/et al prove > otherwise.
I am not taking sides here, but when we are talking distributed systems, timing *is* critical -- a system slow to respond is indiscernible from a failed system and it *will* get isolated. The trade-off here is tolerance of bumps vs. reaction to failures -- and this *is* something you tweak for a deployment and yes, this is where the vendor typically does get to dictate required performance characteristics and/or provides very stringent tuning parameters. And yes, as soon as you contact support, it will ask for those parameters (and bunch more) and will (very politely) ask you to fix your configuration if there is any deviation from recommended values. If there are stressors we experience during autorelease build we need to understand what they are so we can account for them: as Tom noted, the deadline is 'a tad too low' -- which works out to a trade-off question (I am exaggerating to make a point): Would you be okay with the test having a deadline on the order of 10 minutes before it declares the test failed? Which boils down to: how much of a hiccup are we supposed to tolerate? Regards, Robert
signature.asc
Description: OpenPGP digital signature
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
