[ https://ovirt-jira.atlassian.net/browse/OVIRT-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37604#comment-37604 ] Eyal Edri commented on OVIRT-2367: ---------------------------------- The general guidelines for OST suite is total runtime from 30-45 min max, If this workflow is planning to take longer, you need to consider running it in QE and not CI. I suggest you'll schedule a meeting with [~gbenhaim@redhat.com] to share your needs and requirements so we'll see what is needed on OST side, but just to emphasis, most of the work will be done by you or the future maintainer of the suite, as other teams did ( see Networking/Ansible/Compat for e.g ).

Functional tests should support testing disaster recovery scenratios with two ovirt-engine setups to simulate failover and failback -----------------------------------------------------------------------------------------------------------------------------------

Key: OVIRT-2367 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2367 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt CI Reporter: Maor Lipchuk Assignee: infra Priority: High

RHV/oVirt should support functional tests for the disaster recovery feature which was introduced in oVirt/RHV 4.2 The functional tests should support testing disaster recovery scenratios with two ovirt-engine setups to simulate failover and failback between the different setups. Here are more resources explaining about the feature and the its usecases: github project: https://github.com/oVirt/ovirt-ansible-disaster-recovery/ Documentation: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/htm... Videos demostrating the usecases for oVirt DR: https://www.youtube.com/watch?v=_TVhU9Sf2uc https://www.youtube.com/watch?v=uRxsZME6fGs https://www.youtube.com/watch?v=7dStBp7Wpo0 https://www.youtube.com/watch?v=a44PdFbeIfE https://youtu.be/ayYrV5IBFUg https://www.youtube.com/watch?v=rt31-XJ45So&t=8s [~gbenhaim@redhat.com]

-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)