Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-38963

[SPIKE] Figure out what will break in robottelo when we containerize

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Installation
    • None
    • sat-rocket
    • 5
    • False
    • Satellite Rocket Sprint 7
    • None

      With SAT-23140 the whole delivery of Satellite will change which has a large impact on how we test the software. Currently robottelo often call satellite-installer or verifies certain RPMs are installed. This will all fail, but there may be many other issues hiding out there.

      A good use case to look at is the external DB scenario. Then Rocket also owns various workflows within satlab, often centered around provisioning that may change and require investigation.

      The goal of this spike is to get a grasp on what needs to change and perhaps come up with some ideas how to change that in the future.

      Upgrades should be considered out of scope now because we don't know yet how it's going to look like. Once we get closer to picking up SAT-38671 there will be another spike.

              gtalreja@redhat.com Gaurav Talreja
              ekohlvan@redhat.com Ewoud Kohl van Wijngaarden
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: