Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Cloud beta exit gate: acceptance walkthrough and TPC-DS sales demo on AWS and Scaleway

Open
  • Is something wrong?
#339 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
aws, python
Domain
cloud, data-engineering

Research direction

Start with the #182 walkthrough, then inspect the olf e2e and olf bench entry points referenced in the issue. Run the TPC-DS sf100 workload on fresh AWS and Scaleway deployments and record the results and costs. Done means the walkthrough and full demo script pass on both clouds without manual repair, with evidence retained; OVHcloud is best-effort.

Written by the indexing model from the issue text.

Description

priority: P0 roadmap track: cloud

Milestone: v0.9-beta — Cloud Beta (AWS, Scaleway, OVH)
Roadmap sequence: #183 (revised 2026-10-05)

Context

v0.9-beta exit gate. Each earlier milestone added a scene to one demo script; here the whole script runs on clouds and becomes the sales demo for data teams.

Demo scenes

  1. Login at https://<base_domain>, landing page, an analyst reaches Superset and is refused Dagster (v0.5).
  2. olf bench run --workload tpcds --scale sf100 on a medium profile; TPC-DS flows Bronze → Floe Silver → dbt Gold → Superset dashboard; elapsed time shown (v0.6).
  3. Grafana follows the run; an injected Floe rejection fires an alert (v0.7).
  4. olf users grant/revoke changes access live; upgrade and restore with no data loss (v0.5, v0.8).
  5. The same on AWS and Scaleway, with the monthly cost of each size (v0.9).

The large public-database ingestion of #110 can be shown as an optional scene proving realistic extraction.

Scope

  • The #182 walkthrough on fresh AWS and Scaleway deployments.
  • The demo as a repeatable written script plus automated checks reusing olf e2e and olf bench.
  • OVHcloud runs it best-effort as preview.

Acceptance criteria

  • #182 passes on fresh AWS and Scaleway deployments.
  • The demo script runs start to finish on both with no manual repair.
  • Results and costs are retained as release evidence.
Dominant language
Python
Stars
26
Forks
6
Avg merge
12h 14m
Merged PRs (30d)
133

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenLakeForge/openlakeforge

All issues in OpenLakeForge/openlakeforge

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.