Add Windows PowerShell Installer (scripts/install.ps1) for Llama Stack

[natedemoss]

Add Windows PowerShell Installer (scripts/install.ps1) for Llama Stack

Context

The repository currently offers a one-line Bash installer (scripts/install.sh) for macOS/Linux users. Windows users must manually set up Docker containers and environment variables, creating onboarding friction and increasing chances of misconfiguration.

Problem / Gap

There is no native automated Windows setup:

• Slower evaluation for new Windows users.
• Inconsistent cross-platform install experience.
• More manual steps (network, telemetry stack, model pull, container launch).

Proposal

Introduce and maintain a PowerShell installer: scripts/install.ps1

Goals

• Parity with scripts/install.sh: network creation, optional telemetry (Jaeger, OTEL Collector, Prometheus, Grafana), Ollama model pull, Llama Stack container start.
• Parameters: -Port, -OllamaPort, -ModelAlias, -Image, -Timeout, -NoTelemetry, -TelemetryServiceName, -TelemetrySinks, -OtelEndpoint.
• Clean, emoji-free console output for Windows PowerShell 5.1 compatibility.
• Documentation updates in README.md and CONTRIBUTING.md.

Non-Goals (initial)

• Installing Docker automatically.
• GPU passthrough setup.
• Advanced model selection logic.
• Persistence of telemetry configs.

Behavior Summary

• Creates llama-net Docker network if absent.
• Optionally starts telemetry containers unless -NoTelemetry is supplied.
• Starts Ollama container and pulls selected model alias.
• Launches Llama Stack distribution container with required environment variables.
• Health checks http://localhost:<Port>/v1/health before success message.
• Cleans up temp telemetry config directory.

Benefits

• Faster onboarding for Windows developers.
• Cross-platform parity increases adoption and testing breadth.
• Reduces misconfiguration risks.
• Encourages contributions from a larger developer base.

Usage Examples

From cloned repo

PowerShell -ExecutionPolicy Bypass -File [install.ps1](http://_vscodecontentref_/0)

Open Questions

• Add -SkipModelPull flag?
• Preserve telemetry configs (-RetainTelemetryConfigs)?
• Target both Windows PowerShell 5.1 and PowerShell 7+ (pwsh) officially?
• Include Windows CI job (PSScriptAnalyzer + smoke run)?
• Add winget preflight guidance for Docker Desktop installation?

Requested Feedback

• Parameter naming and defaults.
• CI coverage expectations.
• Additional environment variables needed?
• Any provider-specific flags to include early?