Hi Boris,
Thanks for comment.
Sorry for the misleading context in the etherpad. It sounds like Eris
will do everything, but it is not.
I think I need to add more details to etherpad (I will do that)
Short answer is we are not into "reinventing wheels" and we will use
all possible existing
Sam,
Etherpad: https://etherpad.openstack.org/p/SYD-extreme-testing
I really don't want to sound like a person that say use Rally my best ever
project blablbab and other BS.
I think that "reinventing wheels" approach is how humanity evolves and
that's why I like this effort in any case.
But
Hi All,
Sending out a gentle reminder of Sydney Summit Forum Session
regarding this topic.
Extreme/Destructive Testing
Tuesday, November 7, 1:50pm-2:30pm
Sydney Convention and Exhibition Centre - Level 4 - C4.11
+1 for Boris’ suggestion. Many of us use Rally to probe our clouds and have
significant tooling behind it to integrate with local availability reporting
and trouble ticketing systems. It would be much easier to deploy new
functionality such as you propose if it was integrated into an existing
2017-08-14 13:41 GMT+02:00 Ghanshyam Mann :
> On Mon, Aug 14, 2017 at 7:56 PM, Boris Pavlovic wrote:
> > Sam,
> >
> > Seems like a good plan and huge topic ;)
> >
> > I would as well suggest to take a look at the similar efforts in
> OpenStack:
> > -
Sam,
Seems like a good plan and huge topic ;)
I would as well suggest to take a look at the similar efforts in OpenStack:
- Failure injection: https://github.com/openstack/os-faults
- Rally Hooks Mechanism (to inject in rally scenarios failures):