Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
42a7d2dc9d
commit
15cb03a7c3
1 changed files with 2 additions and 2 deletions
|
|
@ -30,7 +30,7 @@ Getting the lab clusters to a state where we can actually build on them.
|
||||||
| # | Idea | Done when… | Status | Owner |
|
| # | Idea | Done when… | Status | Owner |
|
||||||
|---|---|---|---|---|
|
|---|---|---|---|---|
|
||||||
| 1 | **Ansible control node on lab cluster 1** | A working control node exists from which the lab cluster can be configured declaratively. | 💡 Idea | |
|
| 1 | **Ansible control node on lab cluster 1** | A working control node exists from which the lab cluster can be configured declaratively. | 💡 Idea | |
|
||||||
| 2 | **User management for lab cluster 1** | We have decided on and set up an approach to accounts and access on the lab cluster. | 💡 Idea | |
|
| 2 | **User management for lab cluster 1** | We have decided on and set up an approach to accounts and access on the lab cluster. | 🔨 In progress | Holger |
|
||||||
| 3 | **Remote power on/off of rack equipment** | Rack hardware can be power-cycled without being physically in the room. | 💡 Idea | |
|
| 3 | **Remote power on/off of rack equipment** | Rack hardware can be power-cycled without being physically in the room. | 💡 Idea | |
|
||||||
| 4 | **UPS strategy** | We have a decision: do we need a UPS, can we cover it with gear we already own, and should the clusters run networked NUT so hosts shut down cleanly? | 💡 Idea | |
|
| 4 | **UPS strategy** | We have a decision: do we need a UPS, can we cover it with gear we already own, and should the clusters run networked NUT so hosts shut down cleanly? | 💡 Idea | |
|
||||||
| 5 | **Lab monitoring / dashboard** | One place to see what is up and what is down across the [hardware](hardware/index.md) we have. | 💡 Idea | |
|
| 5 | **Lab monitoring / dashboard** | One place to see what is up and what is down across the [hardware](hardware/index.md) we have. | 💡 Idea | |
|
||||||
|
|
@ -53,7 +53,7 @@ MakerFLOSS is not the Orange Makerspace IT setup — but we help out where we ca
|
||||||
|
|
||||||
| # | Idea | Done when… | Status | Owner |
|
| # | Idea | Done when… | Status | Owner |
|
||||||
|---|---|---|---|---|
|
|---|---|---|---|---|
|
||||||
| 10 | **Event management system** | OM events are organised in a system we host. Prior-art sweep first: is there a FLOSS tool we can adopt rather than build? | 💡 Idea | |
|
| 10 | **Event management system** | OM events are organised in a system we host. Prior-art sweep first: is there a FLOSS tool we can adopt rather than build? | 🔨 In progress | Marcus |
|
||||||
| 11 | **Todo-gizmo for OM** | A shared task system with both an online part and a physical part in the makerspace (status board / display). | 💡 Idea | |
|
| 11 | **Todo-gizmo for OM** | A shared task system with both an online part and a physical part in the makerspace (status board / display). | 💡 Idea | |
|
||||||
|
|
||||||
## Documentation & housekeeping
|
## Documentation & housekeeping
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue