1fb7266469
- Introduced Aggregator.sol for Chainlink-compatible oracle functionality, including round-based updates and access control. - Added OracleWithCCIP.sol to extend Aggregator with CCIP cross-chain messaging capabilities. - Created .gitmodules to include OpenZeppelin contracts as a submodule. - Developed a comprehensive deployment guide in NEXT_STEPS_COMPLETE_GUIDE.md for Phase 2 and smart contract deployment. - Implemented Vite configuration for the orchestration portal, supporting both Vue and React frameworks. - Added server-side logic for the Multi-Cloud Orchestration Portal, including API endpoints for environment management and monitoring. - Created scripts for resource import and usage validation across non-US regions. - Added tests for CCIP error handling and integration to ensure robust functionality. - Included various new files and directories for the orchestration portal and deployment scripts.
2.3 KiB
2.3 KiB
Deployment Strategy Clarification
Current Configuration
West Europe (Primary Region)
- AKS Cluster: 1 cluster (az-p-we-aks-main)
- System Nodes: 3 × Standard_D2s_v3 (6 vCPUs)
- Validators: 1 × Standard_B2s (2 vCPUs) - Planned
- Total: 8 vCPUs (within 10 limit)
Cloud for Sovereignty (37 Regions)
- Foundation: ✅ Deployed (resource groups, VNets, Key Vaults)
- AKS Clusters: ❌ Not deployed (deploy_aks_clusters = false)
- Validators: ❌ Not configured
Deployment Options
Option 1: 5 Validators in West Europe
Configuration:
- 5 × Standard_B2s = 10 vCPUs
- Issue: Exceeds 10 vCPU limit (need quota increase)
- Cost: ~$75/month
- Location: Single region (West Europe)
Option 2: 1 Validator per Region (5 Regions)
Configuration:
- 5 regions × 1 validator = 5 × Standard_B2s = 10 vCPUs total
- Requirements:
- Deploy AKS clusters in 5 regions
- Each region needs quota for 2 vCPUs
- Cost: ~$75/month (5 × $15/month)
- Regions: Could use West Europe, North Europe, UK South, France Central, Germany West Central
Option 3: Validators as Pods (No Quota Needed)
Configuration:
- Deploy Besu validators as pods on existing system nodes
- Advantages:
- No additional quota needed
- Can deploy immediately
- Can deploy in multiple regions (if AKS clusters exist)
- Cost: $0 additional (uses existing nodes)
Recommended Strategy
Phase 1: Immediate (No Quota Needed)
- Deploy Besu validators as pods in West Europe
- Uses existing 6 vCPUs from system nodes
- Can deploy multiple validators as pods
Phase 2: Regional Expansion (After Quota/Infrastructure)
- Deploy AKS clusters in priority regions
- Deploy 1 validator per region (or as pods)
- Scale based on requirements
Phase 3: Production (Full Deployment)
- Deploy dedicated validator node pools
- Use Standard_B2s or Standard_B2ms
- Deploy across multiple regions for redundancy
Questions to Clarify
-
How many validators?
- 5 validators total?
- Or 1 validator per region across 5 regions?
-
Which regions?
- All in West Europe?
- Or distributed across multiple regions?
-
Deployment method?
- Dedicated node pools (need quota)?
- Or as pods on existing nodes (no quota)?
-
Timeline?
- Immediate (pods)?
- Or after quota increase (node pools)?