c39465c2bd
Some checks failed
Test / test (push) Has been cancelled
Co-authored-by: Cursor <cursoragent@cursor.com>
111 lines
3.1 KiB
Markdown
111 lines
3.1 KiB
Markdown
# Final Deployment Status
|
|
|
|
## ✅ R630 (pve2) - 192.168.1.55 - DEPLOYMENT COMPLETE
|
|
|
|
**Network Status:**
|
|
- ✅ vmbr0 (nic3): **192.168.1.55/24** (LAN) - Working
|
|
- ✅ vmbr1 (nic2): **45.49.66.13/19** (WAN - Public IP) - Working
|
|
- ✅ Network configuration applied and active
|
|
- ✅ Both bridges have IP addresses
|
|
|
|
**Configuration:**
|
|
- ✅ /etc/network/interfaces configured
|
|
- ✅ /etc/hosts updated with pve entry (192.168.1.207)
|
|
- ⚠️ corosync.conf still has old IPs (192.168.1.206, 192.168.1.49) - needs manual update
|
|
|
|
## ⚠️ ML110 (pve) - 192.168.1.207 - CONFIGURED (Needs Verification)
|
|
|
|
**Network Configuration:**
|
|
- ✅ Network configuration file written (nic0→vmbr0, nic1→vmbr1)
|
|
- ✅ /etc/hosts updated with pve2 entry (192.168.1.55)
|
|
- ⚠️ Network apply may have been interrupted
|
|
- ⚠️ Currently not accessible via SSH (likely due to network restart)
|
|
|
|
**Actions Needed:**
|
|
- Use console access to verify network configuration
|
|
- Check if network was applied: `ip addr show`
|
|
- If needed, apply network: `ifreload -a` or `systemctl restart networking`
|
|
- Update corosync.conf with new IPs if cluster is configured
|
|
|
|
## Network Configuration Summary
|
|
|
|
### R630 (pve2)
|
|
```
|
|
Physical: nic3 (LAN) → vmbr0 → 192.168.1.55/24 ✅
|
|
Physical: nic2 (WAN) → vmbr1 → 45.49.66.13/19 ✅
|
|
```
|
|
|
|
### ML110 (pve)
|
|
```
|
|
Physical: nic0 (LAN) → vmbr0 → Should get 192.168.1.207/24
|
|
Physical: nic1 (WAN) → vmbr1 → Should get public IP
|
|
```
|
|
|
|
## Cluster Configuration Status
|
|
|
|
### Current Cluster State
|
|
- R630 can see cluster but only 1 node (quorum not met)
|
|
- ML110 cluster status unknown (not accessible)
|
|
|
|
### To Complete Cluster Configuration
|
|
|
|
**Once ML110 is accessible again:**
|
|
|
|
1. **Update corosync.conf on ML110:**
|
|
```bash
|
|
# Update ring0_addr entries
|
|
sed -i 's/ring0_addr:.*pve$/ring0_addr: 192.168.1.207/' /etc/pve/corosync.conf
|
|
sed -i 's/ring0_addr:.*pve2$/ring0_addr: 192.168.1.55/' /etc/pve/corosync.conf
|
|
```
|
|
|
|
2. **Restart cluster services (one node at a time):**
|
|
```bash
|
|
# On ML110 first
|
|
systemctl restart corosync
|
|
systemctl restart pve-cluster
|
|
|
|
# Then on R630
|
|
systemctl restart corosync
|
|
systemctl restart pve-cluster
|
|
```
|
|
|
|
3. **Update cluster certificates:**
|
|
```bash
|
|
# On both nodes
|
|
pvecm updatecerts -f
|
|
pvecm expected 2
|
|
```
|
|
|
|
4. **Verify cluster:**
|
|
```bash
|
|
pvecm status
|
|
pvecm nodes
|
|
```
|
|
|
|
## Next Steps
|
|
|
|
1. **Access ML110 via console** (if SSH not working)
|
|
2. **Verify network on ML110:**
|
|
- Check `ip addr show` to see if bridges have IPs
|
|
- Apply network config if needed
|
|
3. **Complete cluster configuration** once both nodes are accessible
|
|
4. **Verify connectivity** between nodes
|
|
|
|
## Deployment Summary
|
|
|
|
✅ **R630 (pve2)**: Fully deployed and working
|
|
⚠️ **ML110 (pve)**: Configuration written, needs verification via console
|
|
|
|
## Files Deployed
|
|
|
|
All configuration files have been written:
|
|
- ✅ `/etc/network/interfaces` on both servers
|
|
- ✅ `/etc/hosts` on both servers
|
|
- ⚠️ `/etc/pve/corosync.conf` on R630 (needs manual update - has old IPs)
|
|
- ⚠️ `/etc/pve/corosync.conf` on ML110 (needs verification and update)
|
|
|
|
---
|
|
|
|
**Status:** R630 deployment complete. ML110 needs console access to verify.
|
|
|