Skip to content

Latest commit

 

History

History
275 lines (203 loc) · 9.77 KB

WHATS_LEFT.md

File metadata and controls

275 lines (203 loc) · 9.77 KB

What's Left? - Lightstack Status Overview

Date: April 2026 Version: v0.6.0 Current Coverage: 104% (342/330 endpoints) ✅

SPEC-009 (2026-06-22): single-node real mode implemented + host-validated. The real-mode workstreams of lightstack#52 Part A — VM disk (WS-0), startup network reconciliation (WS-2), metadata/cloud-init (WS-4), single-node north-south (WS-3) — plus block storage (WS-5: attach, volume-from-image, boot-from-volume, delete semantics) now work end-to-end on Linux + libvirt. Multi-node (WS-1) remains the v2 ticket (lightstack#52 Part B). See docs/specs/009-single-node-real-mode/.


Resolved in v0.6.0

The following issues from the April 2026 codebase review have been fixed:

  • ✅ Internal error leakage to API clients (C-1) — structured error framework
  • ✅ No database transactions for multi-statement ops (C-2) — WithTx helper
  • ✅ Predictable MAC addresses (C-3) — crypto/rand
  • ✅ Hardcoded admin passwords (C-4) — cryptographic generation
  • ✅ Wildcard CORS (C-5) — configurable origins
  • ✅ Error handling middleware not registered (H-9)
  • ✅ Inconsistent error formats (H-2) — unified across 50 files
  • ✅ Goroutines without shutdown coordination (H-7)
  • ✅ Hardcoded localhost URLs (H-11) — dynamic base URL
  • ✅ And 22 more findings (see CHANGELOG.md)

v0.7.0 Planned

These items from the codebase review are now planned for v0.7.0 with concrete approaches:

ID Severity Description v0.7.0 Approach
H-3 High Database dependency injection ✅ Done (SPEC-027): every database-using service takes the *pgxpool.Pool in its constructor, and the process-wide handle is gone (ADR-001)
H-4 High Re-enable CI linting Staged golangci-lint config, fix 78 test errors first
H-6 High Rate limiting middleware x/time/rate, IP + project dual mode, 10K cap (ADR-002)
H-8 High Cinder route deduplication 301 redirect old paths, don't remove
— Medium Pagination inconsistency Adopt ParsePagination() across 24 handlers
— New Terraform conformance 15+ configs exercising all openstack_* resources

See SPEC-006 for full specification.

Remaining Technical Debt

ID Severity Description Reason Deferred
H-1 High Unit test coverage (6 files for 31K lines) Ongoing effort, DI enables more unit tests
L-1 Low TODO comments in storage package Tracks planned go-ceph work
L-2 Low Dockerfile runs as root Required for network namespaces
L-5 Low Benchmarks not in CI Nice to have
L-7 Low Docker Compose proliferation Low impact
L-9 Low Contract test helper duplication Low impact
— P2 Load testing Deferred post-v0.7.0

TL;DR

Nothing critical is left. Lightstack has exceeded the OpenStack baseline by 12 endpoints. All remaining work is optional enterprise features with low demand.


Completion Status

✅ COMPLETE (100%)

🔴 HIGH Priority - All production-critical features

  • Nova Server Actions (migrate, evacuate, backup, etc.) ✅
  • Keystone Service Catalog Management ✅
  • Cinder Volume Actions ✅

🟡 MEDIUM Priority - All important operational features

  • Nova Console Access (VNC, SPICE, RDP, Serial) ✅
  • Nova Tenant Usage & Availability Zones ✅
  • Keystone Domain Management ✅
  • Keystone Credential Management ✅
  • Neutron Floating IP Port Forwarding ✅
  • Glance Image Import ✅
  • Cinder Volume Groups ✅

🎯 Special Achievement

  • Horizon Dashboard Integration (6 user stories) ✅
  • Performance Optimization (pagination + indexes) ✅

🟢 Optional Work (LOW Priority)

1. Keystone Federation/SAML (~10 endpoints)

Status: ❌ Not Implemented (by design)

What it does: Enterprise SSO integration with SAML/OAuth providers

Endpoints:

❌ GET    /v3/OS-FEDERATION/identity_providers
❌ POST   /v3/OS-FEDERATION/identity_providers
❌ GET    /v3/OS-FEDERATION/identity_providers/:id
❌ DELETE /v3/OS-FEDERATION/identity_providers/:id
❌ GET    /v3/OS-FEDERATION/mappings
❌ POST   /v3/OS-FEDERATION/mappings
❌ GET    /v3/OS-FEDERATION/protocols
... (10 total)

Why skip it:

  • Complex SAML protocol implementation
  • Only needed for enterprise deployments (<5% of users)
  • Most deployments use local authentication
  • Effort: 3-4 sprints

Alternative: Use external SAML proxy (nginx + auth_request)


2. Neutron Advanced Features (~8 endpoints)

Status: ❌ Not Implemented (by design)

What it does: Advanced networking for large multi-datacenter clouds

Endpoints:

# Metering (6 endpoints)
❌ GET    /v2.0/metering/metering-labels
❌ POST   /v2.0/metering/metering-labels
❌ GET    /v2.0/metering/metering-labels/:id
❌ DELETE /v2.0/metering/metering-labels/:id
❌ GET    /v2.0/metering/metering-label-rules
❌ POST   /v2.0/metering/metering-label-rules

# Auto-allocated topology (3 endpoints)
❌ GET    /v2.0/auto-allocated-topology/:project_id
❌ DELETE /v2.0/auto-allocated-topology/:project_id
❌ GET    /v2.0/auto-allocated-topology

# DVR - Distributed Virtual Routing (4 endpoints)
❌ (Various DVR-specific endpoints)

Why skip it:

  • DVR: Only for large cloud providers (Rackspace, etc.)
  • Metering: Most clouds use external monitoring (Prometheus, etc.)
  • Auto-topology: Rarely used feature
  • Effort: 2-3 sprints

Alternative: Lightstack has standard routing + floating IPs (sufficient for 99% use cases)


3. Nova Microversion-Gated Features (variable)

Status: ⚠️ Partial Implementation

What it does: Version-specific API enhancements

Examples:

❌ v2.3   - Availability zones in server details (minor enhancement)
❌ v2.19  - Description field for servers (cosmetic)
❌ v2.32  - Tags support (labeling feature)
❌ v2.42  - Server groups enhanced (advanced scheduling)
❌ v2.52  - Tagged instances (query optimization)
... (20+ microversion features)

Why skip it:

  • Lightstack implements core API (v2.1 base)
  • Microversion features are incremental enhancements
  • Most clients work fine with v2.1 base
  • Can add on-demand as needed
  • Effort: Ongoing (1 sprint per 5-10 features)

Note: Major microversion features (console access, volume actions) are already implemented


What Lightstack HAS That Exceeds Baseline (+12 endpoints)

These are BONUS features beyond the 330 baseline:

  1. Port Forwarding (5 endpoints) - Forward specific ports on floating IPs
  2. Volume Groups (5 endpoints) - Coordinated storage operations
  3. Credential Management (5 endpoints) - EC2-style API keys
  4. Advanced Actions (8 endpoints) - migrate, evacuate, backup
  5. Metadefs Management (15+ endpoints) - Image metadata schemas
  6. Service Catalog CRUD (8 endpoints) - Dynamic service registration
  7. Domain Management (6 endpoints) - Multi-domain support

Total: 52 endpoints in "bonus" category, but 12 net over baseline


Production Readiness Checklist

Category Status Notes
Core CRUD Operations ✅ 100% All create/read/update/delete working
Server Lifecycle ✅ 100% Start, stop, reboot, rebuild, resize
Networking ✅ 100% Networks, subnets, routers, floating IPs, security groups
Storage ✅ 100% Volumes, snapshots, backups, attach/detach
Images ✅ 100% Upload, download, metadata, import workflow
Authentication ✅ 100% Users, projects, domains, roles, tokens
Multi-Tenancy ✅ 100% Project isolation, RBAC, quotas
Horizon Dashboard ⚠️ Usable APIs served; UI usable for resource management, open gaps F1/F10/F11/F13/F18 (see docs/compatibility/HORIZON_COMPATIBILITY_REPORT.md)
Performance ✅ Optimized Pagination, indexes, <3s queries
Testing ✅ Comprehensive 65+ tests (contract + integration)
Documentation ✅ Complete Deployment guides, API docs

Verdict: PRODUCTION READY ✅


Recommendation

DO NOT implement the remaining optional features unless:

  1. Federation/SAML: You need enterprise SSO with specific SAML providers
  2. Neutron Advanced: You're running a multi-datacenter cloud with 1000+ nodes
  3. Microversions: A specific client requires a newer microversion feature

Why?

  • Current implementation serves 99% of private cloud use cases
  • Remaining features add complexity without broad value
  • Better to focus on stability, documentation, and bug fixes

If You Want to Reach 110%+

Here are features that would be more valuable than the "optional" list:

High-Value Additions (Not in OpenStack Baseline)

  1. Kubernetes Integration (NEW)

    • Container orchestration support
    • Pod networking via Neutron
    • Persistent volumes via Cinder
    • Effort: 4-5 sprints
  2. Terraform Provider (NEW)

    • Infrastructure-as-code support
    • OpenStack Terraform provider compatibility
    • Effort: 2-3 sprints
  3. Monitoring/Observability (ENHANCEMENT)

    • Prometheus metrics export
    • OpenTelemetry tracing
    • Grafana dashboards
    • Effort: 2 sprints
  4. Multi-Region Support (ENHANCEMENT)

    • Cross-region replication
    • Global load balancing
    • Effort: 3-4 sprints
  5. Backup/DR (ENHANCEMENT)

    • Automated backup schedules
    • Cross-site disaster recovery
    • Effort: 2-3 sprints

Summary

What's Left?: Nothing critical. Only optional enterprise features.

Coverage: 104% (342/330 endpoints)

Status: Production ready for private cloud deployments ✅

Next Steps: Focus on stability, documentation, and real-world testing rather than implementing low-demand features.