Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-10023

Implement the lightspeed integration within the integrations CLI

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • 1.9.0
    • None
    • lightspeed
    • None

      Story (Required)

      As a customer trying to try the RHDH Lightspeed integration I want an easy way to setup this integration using an automated tool.

      Implements the lightspeed integration commands under the integrations CLI in order to provide users a quick, simple, and painless way to setup the integration with RHDH. This is also essential to have for supporting the lightspeed integration install using a RHDH helm chart install as the upcoming helm charts will use this tool to perform the integration setup operations.

      Background (Required)

      We currently have the integrations tool which at the time of writing will be implemented with just the model catalog integration commands (RHDHPAI-1146).

      Out of scope

      • QE work
      • Documentation to be done and revisions by the docs team
      • Container build implementation
      • Release engineering (i.e. publish workflows, release process, release automation)

      Approach (Required)

      We'll need to provide the same commands from RHDHPAI-1146 for the lightspeed integration setup:

      • lightspeed check - This command would provide an indication of readiness for the lightspeed RHDH integration to be installed to a target RHDH instance
      • lightspeed install - This command will setup and install the lightspeed RHDH integration to a target RHDH instance
      • lightspeed uninstall - This command will undo the setup and install the lightspeed RHDH integration to a target RHDH instance

      Dependencies

      1. An investigation into more details will need to be done (RHDHPAI-1069)
      2. RHDHPAI-1146 will need to be completed.

      Acceptance Criteria (Required)

      library functions implemented
      commands implemented
      documentation updates (design docs, release notes etc)

      Done Checklist

      Code is completed, reviewed, documented and checked in
      Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      Continuous Delivery pipeline(s) is able to proceed with new code included
      Customer facing documentation, API docs, design docs etc. are produced/updated, reviewed and published
      Acceptance criteria are met
      If the Grafana dashboard is updated, ensure the corresponding SOP is updated as well

              Unassigned Unassigned
              mvaldron Michael Valdron
              RHIDP - AI
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: