Running Services
OpenFactory Enterprise deployments should be operated with your organization’s standard service manager, container platform, or orchestration layer.
Day-Two Operations
| Task | Guidance |
|---|---|
| Start and stop services | Use the deployment runbook provided for your environment |
| Scale capacity | Add build or VM capacity based on queue depth and concurrency targets |
| Rotate secrets | Update secrets through your secrets manager and restart affected services |
| Apply updates | Use signed release packages and follow change-control procedures |
| Review audit logs | Export audit events to your approved logging destination |
Health Checks
Monitor:
- Console availability
- API availability
- Build queue depth
- VM target health
- Artifact storage availability
- Identity provider connectivity
- Integration delivery failures
Troubleshooting
Start with the user-facing symptom, then check the related subsystem:
| Symptom | Check |
|---|---|
| Users cannot sign in | Identity provider, callback URL, clock skew, and role mapping |
| Builds stay queued | Build worker capacity, package mirror access, and artifact storage |
| VM tests fail to start | VM target registration, available capacity, and network policy |
| Downloads fail | Artifact storage permissions, retention policy, and signed URL configuration |
| MCP cannot connect | API key, MCP URL, client transport support, and organization permissions |
Last updated on