Administration
NCP-AIO · 46 questions
- Library branch cameras run Metropolis-style apps at the edge. How should city ops administer them?
- Transit wants remote updates of depot occupancy models on edge boxes. What Fleet Command step comes first?
- A bad model push hits public-health clinic kiosks. What should civic ops use in Fleet Command?
- Parks CV gateways stop answering. What should civic ops check in Fleet Command before rolling trucks?
- County wants court lobby edges and library edges to limit shared blast radius. What should Fleet Command structure reflect?
- Emergency-management trailers need overnight model health checks without a tech on site. What should ops use?
- School-district AI lab edges must not share the same Fleet Command org as PHI clinic edges. Why?
- City is about to ship 311 lobby kiosks to a new site. What Fleet Command work should precede shipping?
- Public-health PHI training must not share Slurm QoS with open research. What should civic admins configure?
- After a transit node swap, Slurm schedules CPUs but no GPUs. What should civic admins correct?
- Housing fine-tune jobs need whole nodes without noisy neighbors. What Slurm administration action fits?
- County assessor array jobs flood the Slurm controller. What should civic admins do?
- Clerk OCR needs Slurm maintenance, but 311 Kubernetes inference must keep running on other nodes. What should admins do?
- School-district thesis jobs starve while weekend scrapers run. What Slurm admin change favors thesis work?
- Water-utility multi-node GPU jobs land on poorly connected hosts. What should Slurm admins configure?
- Emergency AI must jump ahead of batch library jobs during a surge. What Slurm administration fits?
- City wants Slurm jobs to mount civic datasets safely at start and clean up at end. What practice fits?
- Library consortium sites want shared weekend catalog-vision training. What Slurm arrangement should admins use?
- City plans dense health-model training with heavy all-reduce. What data center architecture choice fits?
- 311 inference wants many smaller nodes; overnight training wants dense NVLink domains. What should architecture reflect?
- Transit ETA training checkpoints crawl across the network. What architecture change helps?
- County power and cooling cannot add another full GPU rack. What architecture move should come first?
- Public-health PHI models must not share the same zone as open-data 311 models. What architecture fits?
- Emergency management wants on-prem primary AI plus cloud burst. What should architecture define?
- Library branches need light CV inference; heavy training stays downtown. What architecture split fits?
- Water SCADA analytics GPUs share a ToR with guest Wi-Fi. What architecture change is required?
- Courts OCR GPU row lost power in a prior UPS event. What architecture improvement fits?
- School-district teaching labs keep crashing production district models. What architecture control helps?
- City departments 311, public health, and transit share one Run:ai cluster. What admin setup fits?
- Housing researchers need Run:ai notebooks but leave GPUs idle for hours. What should admins configure?
- Transit inference cannot wait in a general training queue. What Run:ai administration fits?
- County wants training favored on weekends and inference on weekdays in Run:ai. What should admins tune?
- Public-health PHI projects are about to go live on Run:ai. What identity step should admins complete first?
- Parks CV needs a weekend festival quota bump without permanent entitlement creep. What should Run:ai admins do?
- School-district staff keep creating cluster-wide Run:ai roles. What should admins restrict?
- Emergency-management drills must preempt low-priority library jobs in Run:ai. What should admins configure?
- After maintenance, Run:ai still schedules to a cordoned civic GPU node. What should admins do?
- City platform admins run weekly Kubernetes GPU health checks. What should those checks include?
- City 311 inference runs as a Kubernetes Deployment. What availability control should admins apply before draining nodes?
- County Kubernetes hosts both public-health and open 311 namespaces. What should admins use to keep PHI traffic isolated?
- Transit ops, planning, and safety each run GPU jobs on one Kubernetes cluster. How should admins separate their capacity?
- Library GPU nodes need a controlled Kubernetes upgrade. What node-lifecycle practice should admins follow?
- City wants several 311 microservices to share A100 GPUs without starving each other. What should admins configure?
- Public-health overnight fine-tuning needs full GPUs. How should admins handle MIG on that BCM node category?
- A school-district GPU lab wants about twenty students to run homework models at once. What MIG approach fits?
- Transit finds mixed MIG and non-MIG GPU nodes confuse the scheduler. What should admins do?