Skip to content

Cloud deployment of all frink components. #34

@YaphetKG

Description

@YaphetKG

Issue to track cloud progress: (Here's the draft of the roll out plan (https://docs.google.com/document/d/16zrv0m_KMqG4DOUdpdJzprnLNSMT-8FaHspUXPwKltw/edit?tab=t.0) )

  • Sync Lakefs (1D)
    • Copy data to s3 lakefs bucket
    • Migrate postgres (repository and user data)
    • Start with the old version to keep Credential compatibility. (No longer needed we have an ACL server working with latest lakefs)
  • Migrate KACE (pipelines) (.5D)
    • Do helm deploy of kace.
    • Deployments of Fuski / LDF servers (.5D)
  • Deployment of Qlever (3D):
    • Ensure all lakefs data is clean for QLever loading and reach out if any issues / apply localized fixes.
    • Use the Indexing job in KACE to create qlever index.
    • Add Qlever deployment step in pipeline.
  • Migrate Embedding UI (.25D)
  • Migrate FRINK UI (.25D)
  • Identify DNS strategy

Spider: (timeline TBD)

  • Identify components and dependencies
  • Work with the Spider team to create containers and helm charts.
  • Deploy

Theme 1 UI (if any)(timeline TBD):

  • Identify components and dependencies
  • Create Helm charts
  • Deploy

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

In progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions