c39465c2bd
Some checks failed
Test / test (push) Has been cancelled
Co-authored-by: Cursor <cursoragent@cursor.com>
176 lines
4.4 KiB
Markdown
176 lines
4.4 KiB
Markdown
# Todo Completion Guide
|
|
|
|
**Generated:** 2025-11-27
|
|
**Status:** Many tasks require SSH access or manual intervention
|
|
|
|
## Task Categories
|
|
|
|
### ✅ Can Be Automated (Via API/Scripts)
|
|
These tasks can be completed programmatically:
|
|
|
|
1. **VM Deployment** - Can be done via Proxmox API
|
|
2. **VM Configuration** - Can be done via Proxmox API
|
|
3. **Template Verification** - Can be checked via API
|
|
4. **Cloudflare Credentials** - Can be added to .env file
|
|
|
|
### ⚠️ Requires SSH Access
|
|
These tasks require SSH access to Proxmox servers:
|
|
|
|
1. **Cluster Configuration** - Must run `pvecm` commands on servers
|
|
2. **NFS Storage Configuration** - Must run `pvesm` commands on servers
|
|
3. **VLAN Configuration** - Must modify network interfaces on servers
|
|
4. **Service Configuration** - Must SSH to VMs
|
|
|
|
### 🔧 Requires Manual Intervention
|
|
These tasks require console access or manual steps:
|
|
|
|
1. **OS Installation** - Requires Proxmox console access
|
|
2. **Initial Service Setup** - May require interactive configuration
|
|
|
|
---
|
|
|
|
## Automated Completion Status
|
|
|
|
### Completed via API/Scripts
|
|
|
|
#### ✅ Cloudflare Credentials (if configured)
|
|
- Status: Can be added to `.env` file
|
|
- Action: Add `CLOUDFLARE_API_TOKEN` and `CLOUDFLARE_ACCOUNT_EMAIL` to `.env`
|
|
|
|
#### ✅ Template Verification
|
|
- Status: Can check via API
|
|
- Action: Query VM 9000 status via Proxmox API
|
|
|
|
### Pending - Requires SSH Access
|
|
|
|
#### ⏳ Cluster Configuration
|
|
**ML110:**
|
|
```bash
|
|
ssh root@192.168.1.206
|
|
export CLUSTER_NAME=hc-cluster NODE_ROLE=create
|
|
./infrastructure/proxmox/cluster-setup.sh
|
|
```
|
|
|
|
**R630:**
|
|
```bash
|
|
ssh root@192.168.1.49
|
|
export CLUSTER_NAME=hc-cluster NODE_ROLE=join CLUSTER_NODE_IP=192.168.1.206
|
|
./infrastructure/proxmox/cluster-setup.sh
|
|
```
|
|
|
|
#### ⏳ NFS Storage Configuration
|
|
**Both servers:**
|
|
```bash
|
|
export NFS_SERVER=10.10.10.1 NFS_PATH=/mnt/storage STORAGE_NAME=router-storage
|
|
./infrastructure/proxmox/nfs-storage.sh
|
|
```
|
|
|
|
#### ⏳ VLAN Configuration
|
|
**Both servers:**
|
|
```bash
|
|
./infrastructure/network/configure-proxmox-vlans.sh
|
|
```
|
|
|
|
### Pending - Can Be Automated via API
|
|
|
|
#### ⏳ VM Deployment
|
|
Can be automated using Proxmox API or Terraform:
|
|
- Cloudflare Tunnel VM (100)
|
|
- K3s Master VM (101)
|
|
- Git Server VM (102)
|
|
- Observability VM (103)
|
|
|
|
#### ⏳ Template Verification
|
|
Can check VM 9000 status via API
|
|
|
|
---
|
|
|
|
## Execution Instructions
|
|
|
|
### Option 1: Manual SSH Execution
|
|
|
|
1. **Enable SSH access** to both Proxmox servers
|
|
2. **Copy project files** to servers (or clone repo)
|
|
3. **Run scripts** directly on servers
|
|
|
|
### Option 2: Automated via Scripts (When SSH Available)
|
|
|
|
Run the automation script:
|
|
```bash
|
|
./scripts/deploy/execute-all-todos.sh
|
|
```
|
|
|
|
### Option 3: Hybrid Approach
|
|
|
|
1. **Automate VM deployment** via API (can be done now)
|
|
2. **Manual cluster/storage/network** setup via SSH
|
|
3. **Automate service configuration** after OS installation
|
|
|
|
---
|
|
|
|
## Current Blockers
|
|
|
|
1. **SSH Access** - Required for cluster, storage, and network configuration
|
|
2. **Console Access** - Required for OS installation on VMs
|
|
3. **NFS Server** - May not be available (can skip if not needed)
|
|
|
|
---
|
|
|
|
## Recommended Approach
|
|
|
|
### Phase 1: What Can Be Done Now (No SSH Required)
|
|
1. ✅ Verify template via API
|
|
2. ✅ Deploy VMs via API (if template exists)
|
|
3. ✅ Configure Cloudflare credentials in `.env`
|
|
|
|
### Phase 2: Requires SSH Access
|
|
1. Configure cluster
|
|
2. Configure storage
|
|
3. Configure network/VLANs
|
|
|
|
### Phase 3: Requires Console Access
|
|
1. Install OS on VMs
|
|
2. Initial service configuration
|
|
|
|
### Phase 4: Can Be Automated After Phase 3
|
|
1. Service configuration via SSH
|
|
2. Monitoring setup
|
|
3. Security hardening
|
|
|
|
---
|
|
|
|
## Quick Commands
|
|
|
|
### Test SSH Access
|
|
```bash
|
|
ssh root@192.168.1.206 "echo 'ML110 accessible'"
|
|
ssh root@192.168.1.49 "echo 'R630 accessible'"
|
|
```
|
|
|
|
### Deploy VMs via API (if template exists)
|
|
```bash
|
|
# Use existing VM creation scripts
|
|
./scripts/vm-management/create/create-vms-from-template.sh
|
|
```
|
|
|
|
### Check Current Status
|
|
```bash
|
|
./scripts/health/query-proxmox-status.sh
|
|
```
|
|
|
|
---
|
|
|
|
## Next Steps
|
|
|
|
1. **If SSH access is available:** Run `./scripts/deploy/execute-all-todos.sh`
|
|
2. **If SSH access is not available:**
|
|
- Set up SSH keys for passwordless access
|
|
- Or manually execute scripts on each server
|
|
3. **For VM deployment:** Use Proxmox API scripts (no SSH needed)
|
|
4. **For OS installation:** Use Proxmox web console
|
|
|
|
---
|
|
|
|
**Note:** Many tasks in the todo list require infrastructure access that may not be available from this environment. The scripts and documentation are ready - they just need to be executed in the appropriate environment.
|
|
|