+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 project framework (such as Rally).
Tim From: Boris Pavlovic <bo...@pavlovic.me> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-...@lists.openstack.org> Date: Monday, 14 August 2017 at 12:57 To: "OpenStack Development Mailing List (not for usage questions)" <openstack-...@lists.openstack.org> Cc: openstack-operators <openstack-operators@lists.openstack.org> Subject: Re: [openstack-dev] [QA][LCOO] MEX-ops-meetup: OpenStack Extreme Testing 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): https://rally.readthedocs.io/en/latest/plugins/implementation/hook_and_trigger_plugins.html Best regards, Boris Pavlovic On Mon, Aug 14, 2017 at 2:35 AM, Sam P <sam47pr...@gmail.com<mailto:sam47pr...@gmail.com>> wrote: Hi All, This is a follow up for OpenStack Extreme Testing session[1] we did in MEX-ops-meetup. Quick intro for those who were not there: In this work, we proposed to add new testing framework for openstack. This framework will provides tool for create tests with destructive scenarios which will check for High Availability, failover and recovery of OpenStack cloud. Please refer the link on top of the [1] for further details. Follow up: We are planning periodic irc meeting and have an irc channel for discussion. I will get back to you with those details soon. At that session, we did not have time to discuss last 3 items, Reference architectures We are discussing about the reference architecture in [2]. What sort of failures do you see today in your environment? Currently we are considering, service failures, backend services (mq, DB, etc.) failures, Network sw failures..etc. To begin with the implementation, we are considering to start with service failures. Please let us know what failures are more frequent in your environment. Emulation/Simulation mechanisms, etc. Rather than doing actual scale, load, or performance tests, we are thinking to build a emulation/simulation mechanism to get the predictions or result of how will openstack behave on such situations. This interesting idea was proposed by the Gautam and need more discussion on this. Please let us know you questions or comments. Request to Mike Perez: We discussed about synergies with openstack assertion tags and other efforts to do similar testing in openstack. Could you please give some info or pointer of previous discussions. [1] https://etherpad.openstack.org/p/MEX-ops-extreme-testing [2] https://openstack-lcoo.atlassian.net/wiki/spaces/LCOO/pages/15477787/Extreme+Testing-Vision+Arch --- Regards, Sampath __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
