XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 2.5
    • lightspeed
    • False
    • Hide

      None

      Show
      None
    • False

       

      What is the nature and description of the request?

      Many of our FSI customers are still using Salt and are looking for an automated approach to move off it. There have been asks from:

      • Goldman Sachs
      • US Bank
      • Scotiabank
      • JPMC

      to provide a capability within Lightspeed that would analyze the existing Salt codebase and provide automated playbook migrations.

       

      Why does the customer need this? (List the business requirements here?

      Migrations are generally difficult and a very manual process. Right now we have a consulting offering that talks about Salt migrations but these are very abstract.

      An automated approach would help us to build credibility with customers, kick off POCs faster and demonstrate that we can actually migrate existing legacy automation tooling in Salt.

      How would you like to achieve this? (List the functional requirements here)

      A customer enters a Git repository, Lightspeed analyses the code and then provides either migrated playbooks or recommendations about how to do the migration.

      List any affected known dependencies: Doc, UI etc..

      This should be done via VSCode or some Chatbot window as part of Lightspeed.

              rh-ee-marturne Marty Turner
              florianmoss Florian Moss
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: