Files

defiQUG 9daf1fd378 Apply Composer changes: comprehensive API updates, migrations, middleware, and infrastructure improvements

- Add comprehensive database migrations (001-024) for schema evolution
- Enhance API schema with expanded type definitions and resolvers
- Add new middleware: audit logging, rate limiting, MFA enforcement, security, tenant auth
- Implement new services: AI optimization, billing, blockchain, compliance, marketplace
- Add adapter layer for cloud integrations (Cloudflare, Kubernetes, Proxmox, storage)
- Update Crossplane provider with enhanced VM management capabilities
- Add comprehensive test suite for API endpoints and services
- Update frontend components with improved GraphQL subscriptions and real-time updates
- Enhance security configurations and headers (CSP, CORS, etc.)
- Update documentation and configuration files
- Add new CI/CD workflows and validation scripts
- Implement design system improvements and UI enhancements

2025-12-12 18:01:35 -08:00

3.0 KiB

Raw Blame History

Node Name Update Summary

Date: 2024-12-19
Status: ✅ Complete

Overview

All Proxmox node names have been updated from generic pve* names to actual hostnames based on physical hardware.

Node Name Mapping

IP Address	Old Node Name	New Node Name	Site(s)	FQDN
192.168.11.10	pve1	ML110-01	us-sfvalley	ml110-01.sankofa.nexus
192.168.11.11	pve4/pve7	R630-01	us-sfvalley-2	r630-01.sankofa.nexus

Changes Made

Configuration Files Updated

Provider Configuration
- crossplane-provider-proxmox/examples/provider-config.yaml
- Updated all 3 site node references
Cloudflare Tunnel Configs
- cloudflare/tunnel-configs/proxmox-site-1.yaml - httpHostHeader: ML110-01
- cloudflare/tunnel-configs/proxmox-site-2.yaml - httpHostHeader: R630-01
- cloudflare/tunnel-configs/proxmox-site-3.yaml - httpHostHeader: R630-01
VM Example Manifests
- crossplane-provider-proxmox/examples/test-vm-instance-1.yaml - node: ML110-01
- crossplane-provider-proxmox/examples/test-vm-instance-2.yaml - node: R630-01
- crossplane-provider-proxmox/examples/vm-example.yaml - node: ML110-01
- gitops/infrastructure/claims/vm-claim-example.yaml - node: ML110-01
- gitops/infrastructure/compositions/vm-ubuntu.yaml - node: ML110-01
Documentation
- docs/proxmox/SITE_MAPPING.md - Updated all site node references
- docs/proxmox/RESOURCE_INVENTORY.md - Updated cluster node tables
- docs/proxmox/TASK_LIST.md - Updated TASK-007 status
- docs/runbooks/PROXMOX_VM_PROVISIONING.md - Updated examples
- docs/runbooks/PROXMOX_TROUBLESHOOTING.md - Updated API examples
- docs/proxmox/DEPLOYMENT_GUIDE.md - Updated script examples
- crossplane-provider-proxmox/README.md - Updated documentation
Scripts
- scripts/discover-proxmox-resources.sh - Updated node discovery loop

Important Notes

DNS Hostnames Updated: The DNS hostnames have been updated to use sankofa.nexus domain:
- ml110-01.sankofa.nexus (Instance 1)
- r630-01.sankofa.nexus (Instance 2)
Instance 2 Sharing: Both eu-west-1 and apac-1 sites use the same physical instance (192.168.11.11) and node (R630-01). This is acceptable for development/testing.
Cloudflare Tunnels: The httpHostHeader in tunnel configs now uses the actual node names (ML110-01, R630-01) instead of DNS hostnames.

Verification

To verify node names are correct:

# Connect to Proxmox and list nodes
pvesh get /nodes

# Or via API
curl -k -H "Authorization: PVEAuthCookie=TOKEN" \
  https://192.168.11.10:8006/api2/json/nodes

✅ TASK-007: Map Proxmox instances to sites - COMPLETED
✅ TASK-028: Verify and update Proxmox resource names - COMPLETED

Next Steps

Verify actual node names match (ML110-01, R630-01) when connecting to Proxmox
Update any additional documentation that references old node names
Test VM provisioning with new node names

3.0 KiB Raw Blame History