Denis, Unfortunately, we had some issues with this recording (low slides recording resolution, missed slides and random slides switch delay), which makes it slightly unwatchable :( Anyway, if you brave enough, you may open the slides [1] and the recording [2] simultaneously to solve this :)
[1] https://go.gridgain.com/rs/491-TWR-806/images/11_IgniteSummit2021-Deep-dive-into-testing.pdf [2] https://www.youtube.com/watch?v=uRRlGrSA3NY On Wed, Jun 23, 2021 at 5:40 PM Denis Magda <dma...@apache.org> wrote: > Congrats, Anton, that's a valuable contribution! I attended your session at > the Ignite Summit and wonder if you should share that recording with an > English-speaking part of the community? > > - > Denis > > On Wed, Jun 23, 2021 at 7:37 AM Anton Vinogradov <a...@apache.org> wrote: > > > Folks, > > > > Here's the video [1] that explains the proposal in detail. > > Feel free to ask questions here. > > > > [1] https://www.youtube.com/watch?v=f-i9COU5uAQ (in Russian) > > > > On Tue, Jun 8, 2021 at 2:51 PM Anton Vinogradov <a...@apache.org> wrote: > > > > > Igniters, > > > Let me present a framework, we developed, that allows automating Apache > > > Ignite testing on a real cluster. > > > The framework was initially presented at Ignite Summit. > > > > > > In brief, > > > The framework allows automating operations with any applications on a > > real > > > cluster using ssh in a form of a python test. > > > > > > Features: > > > - Ignite nodes can be started/stopped on a Docker or a real cluster > with > > > any custom configuration > > > - Any AI version is supported (released or compiled from sources) > > > - Ignite forks are also supported «out of the box» > > > - Any other application execution is also possible, eg. we implemented > > > starters for Spark and Zookeeper > > > - Cluster can be managed using the control.sh, we made this a part of > the > > > test API > > > - Custom Java applications can be executed remotely with/without a > > > built-in Ignite node or a Thin client > > > - Any ssh command can be executed remotely, and the result will be > > > available locally (at the python test) > > > - Network can be broken by iptables change to check communication > issues > > > - Tests can be executed in parallel when cluster size bigger than tests > > > requirements > > > > > > As a result, seems, we may automate any testing scenario we can even > > > imagine. > > > > > > Framework based on Ducktape [1] library from Kafka team, that's why we > > > called it Ducktests. > > > > > > The Ducktests were developed during work on IEP-56 [2] and already were > > > used during the work on IEP-45 [3]. > > > IEP-45 measurement results examples [4.1] [4.2] were demonstrated at > the > > > HighLoad conference last month. > > > > > > Code available at PR-9117 [5] and ready to be reviewed/merged. > > > Feel free to ask questions or make proposals. > > > > > > [1] https://ducktape-docs.readthedocs.io/en/latest/index.html > > > [2] > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-56%3A+Distributed+environment+tests > > > [3] > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-45%3A+Crash+Recovery+Speed-Up > > > [4.1] https://youtu.be/UZsvCNjbkww?t=1065 (in Russian) > > > [4.2] https://youtu.be/UZsvCNjbkww?t=1609 (in Russian) > > > [5] https://github.com/apache/ignite/pull/9117 > > > > > >
