Skip to content

Instantly share code, notes, and snippets.

View castrojo's full-sized avatar
🦖
Shipping raptors ...

Jorge O. Castro castrojo

🦖
Shipping raptors ...
View GitHub Profile
@castrojo
castrojo / fsdk-containers-size-analysis.md
Last active July 25, 2026 22:53
fsdk-containers Size Analysis: Before vs. After FSDK 26.08 Refactoring

fsdk-containers OCI Image Size Analysis (Chainguard vs Ubuntu)

Real, verified OCI image layer size measurements from ghcr.io/projectbluefin/ using skopeo inspect. All fsdk-containers images are squashed into a single ultra-slim OCI layer.

Image / Category Registry Link fsdk-containers (x86_64) Chainguard Equivalent Ubuntu Equivalent Net Reduction vs Ubuntu
base ghcr.io/projectbluefin/base 15.84 MB 4.54 MB (glibc-dynamic) 39.65 MB (ubuntu:latest) -60.1%
static ghcr.io/projectbluefin/static 15.86 MB 0.60 MB (static) 39.65 MB (ubuntu:latest) -60.0%
python ghcr.io/projectbluefin/python 37.22 MB 24.85 MB (python) 78.39 MB (ubuntu + python3) **-52.5
@castrojo
castrojo / dakota-bst-performance-analysis.md
Created July 24, 2026 20:54
Dakota BuildStream (BST) Remote Execution & Cluster Performance Analysis

Dakota BuildStream (BST) Remote Execution & Cluster Performance Analysis

Executive Summary & Cluster Topology

This document details the performance optimization, scaling extrapolation, and factory build comparison for the dakota:testing and dakota-nvidia:testing BuildStream (BST) remote execution pipeline across the lab cluster infrastructure.

Cluster Infrastructure Overview

  • Nodes: 2 physical machines (ghost and exo-0).
  • Compute Capacity: 32 CPU threads & 64 GiB RAM per node (64 total CPU threads, 128 GiB total RAM).
  • Storage: High-speed local NVMe XFS mounts (/var/lib/dakota/buildstream-cache and BuildBarn CAS/AC block devices).
@castrojo
castrojo / gist:7d459175411a9e16dcde7cef68d63a6a
Created July 19, 2026 04:44
Corrected Wolves companion artwork positioning implementation plan
Wolves companion artwork positioning implementation plan
# Wolves Companion Artwork Positioning Recovery Implementation Plan
> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
**Goal:** Pin Bob Torosaurus, Karl, and Kaslin Torosaurus artwork to the lower-right of their existing guardian-bond cards, with Karl aligned to the guardian nameplate baseline.
**Architecture:** Keep the documented guardian-bond data and shared companion-card layout unchanged. Add a small component-local mapping from documented species IDs to CSS position classes, then target the three affected images with scoped styles that preserve every other bonded dinosaur and the existing responsive card sizing.
@castrojo
castrojo / gist:1d095ce5f33d9657168f18853c1c5351
Created July 19, 2026 04:43
Wolves companion artwork positioning implementation plan
# Wolves Companion Artwork Positioning Recovery Implementation Plan
> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
**Goal:** Pin Bob Torosaurus, Karl, and Kaslin Torosaurus artwork to the lower-right of their existing guardian-bond cards, with Karl aligned to the guardian nameplate baseline.
**Architecture:** Keep the documented guardian-bond data and shared companion-card layout unchanged. Add a small component-local mapping from documented species IDs to CSS position classes, then target the three affected images with scoped styles that preserve every other bonded dinosaur and the existing responsive card sizing.
**Tech Stack:** Vue 3 `<script setup>`, TypeScript, scoped SCSS, Vitest, Vue Test Utils.
@castrojo
castrojo / gist:93d5ccb984629a846ab539f81b6244e3
Created July 19, 2026 04:43
Wolves companion art positioning recovery
# Wolves companion art positioning recovery
## Scope
Pin only Bob Torosaurus, Karl, and Kaslin Torosaurus companion artwork to the lower-right of their existing guardian-bond plate. Karl aligns to the guardian nameplate baseline.
## Implementation
- Add existing-ID-specific classes to the three relevant companion plate instances.
- Add scoped CSS rules in `WolvesIntroOverlay.vue`; leave the shared companion layout and all other artwork unchanged.
- Retain the current responsive width rules and verify the three assets on desktop and mobile.
@castrojo
castrojo / 2026-07-18-nested-systemd-qa-implementation-plan.md
Created July 19, 2026 00:16
Nested systemd container QA implementation plan

Nested Systemd Container QA Implementation Plan

Goal: Run all existing desktop Behave suites against a booted systemd/GDM instance of the requested bootc OCI image, without KubeVirt or containerDisk artifacts.

Architecture: run-container-tests will be a privileged outer Podman host using the requested target image, then run a second instance of that target as a named nested container with podman run --systemd=always. The outer runner clones the test suite and collects results; qecore and Behave execute inside

@castrojo
castrojo / 2026-07-18-container-only-bootc-qa-implementation-plan.md
Last active July 18, 2026 22:06
Container-only Bootc QA implementation plan

Container-Only Bootc QA Implementation Plan

For agentic workers: REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (- [ ]) syntax for tracking.

Goal: Replace image-poll-driven KubeVirt/containerDisk QA with the existing Kubernetes container test runner for every requested Bootc suite, then remove the reproducible disk-build artifacts.

Architecture: image-poller, PR polling, and scheduled QA call container-only pipelines. bluefin-qa-pipeline, dakota-qa-pipeline, and cosmic-qa-pipeline fan out requested suites directly to run-container-tests; they no longer assert or create a local containerDisk, provision a VMI, use SSH, or clean up VMs. After a successful full-matrix container run, GitOps removes the disk/VM producer graph and operational cleanup deletes only its reproducible workflows, PVCs, and Zot manifests.

Tech Stack: Argo Workflows 3.7, Kubernetes, Bootc

@castrojo
castrojo / plan.md
Created July 18, 2026 21:59
Container-only Bootc QA migration design

Container-Only Bootc QA Migration Design

Goal

Replace all image-poll driven KubeVirt/containerDisk QA with Kubernetes container-only tests. Preserve the existing smoke, common, developer, software, and system suite contract. Treat the disk images, staging PVCs, active build-cd-sync-* workflows, and KubeVirt artifacts as reproducible and delete them after the replacement has passed.

@castrojo
castrojo / plan.md
Last active July 18, 2026 17:43
ISO publisher repair implementation plan

ISO Publisher Repair Implementation Plan

For agentic workers: REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (- [ ]) syntax for tracking.

Goal: Restore customized Fedora Stable and LTS-HWE ISO builds so successful matrix outputs can flow through the existing testing-bucket prerelease pipeline.

@castrojo
castrojo / destiny-qr-dinosaur-plan.md
Last active July 18, 2026 08:39
Destiny QR dinosaur deck stability implementation plan

Destiny QR Dinosaur Deck Stability Implementation Plan

For agentic workers: REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (- [ ]) syntax for tracking.

Goal: Present a fresh no-repeat dinosaur order on each Destiny intro run while keeping artwork geometry fixed so the QR screen does not reflow.

Architecture: Keep registry data in wolves-comic-hero-shots.ts. Add a pure Fisher-Yates copy helper with injected randomness for unit tests. WolvesIntroOverlay.vue creates one deck for its lifetime and resolves timestamp slots from that deck; CSS reserves the existing artwork space using explicit responsive dimensions and object-fit: contain.

Tech Stack: Vue 3 Composition API, TypeScript, Vitest, scoped CSS.