To run tobiko on OSP18 and onward we need to have it in a container. As it's a standalone framework (not a tempest plugin), it makes sense to have it in a standalone container (not part of the tempest one).

The work required here should be analogical to tempest's one. Tempest container is built using tcib:

https://github.com/openstack-k8s-operators/tcib/tree/main/container-images/tcib/base/os/tempest

Question:

• Should be Tobiko packaged to an rpm?
  • if it isn't, it won't follow the same quality process as all the other containers (service components, tempest and tempest plugins) are/will be
  • If it is, we basically encourage customers to use it - we've had this discussion before and it was concluded that it's mainly meant to be executed by us - RH engineers.
    • in other words, should frameworks and tools which are meant only for downstream usage be packaged and thus shipped to customers?
      • note: if something is packaged, is it automatically shipped to customers?

DoD:

• we have a tobiko container defined in tcib (similarly to tempest)
• we are able to run tobiko container on OSP18
• any unexpected failures are reported

Reviews:

• https://github.com/openstack-k8s-operators/tcib/pull/77
• https://github.com/openstack-k8s-operators/tcib/pull/88