Files
smom-dbis-138/docs/azure/QUOTA_SURGE_ISSUE.md
defiQUG 1fb7266469 Add Oracle Aggregator and CCIP Integration
- 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.
2025-12-12 14:57:48 -08:00

56 lines
1.7 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Quota Surge Issue Resolution
## Issue
**Error**: Insufficient vCPU quota (0 available, need 2)
- **Root Cause**: AKS surge nodes consume quota during node pool creation
- **Standard_B2s**: Needs 2 vCPUs for node + 1 vCPU for surge = 3 vCPUs total during creation
- **Available**: 4 vCPUs (should be enough, but surge consumes extra)
## Solution Applied
### Use maxUnavailable Instead of maxSurge
```hcl
upgrade_settings {
max_surge = "0" # No surge nodes, prevents quota consumption
}
```
### Benefits
- **No surge nodes**: Eliminates extra quota consumption
- **Deployment uses existing nodes**: No additional quota needed during creation
- **Fits quota**: 2 vCPUs needed (within 4 available)
## Configuration
### Validator Node Pool
- **Count**: 1 node
- **VM Size**: Standard_B2s (2 vCPUs, 4GB RAM)
- **Surge**: 0 (max_surge = 0)
- **Total vCPUs**: 2 (no surge overhead)
### Resource Allocation
- **System**: 3 × Standard_D2s_v3 = 6 vCPUs
- **Validators**: 1 × Standard_B2s = 2 vCPUs
- **Total**: 8 vCPUs (within 10 limit) ✅
## Alternative Solutions
### Option 1: Wait for Quota to Clear
- If temporary quota hold, wait and retry
- Check for ongoing deployments consuming quota
### Option 2: Request Quota Increase
- Request 2 more vCPUs (total 12)
- Allows surge nodes and more flexibility
### Option 3: Deploy as Pods (No New Nodes)
- Deploy Besu validators as pods on existing system nodes
- No additional quota needed
- Use node selectors to prefer system nodes
## References
- [AKS maxSurge and maxUnavailable](https://aka.ms/aks/maxUnavailable)
- [AKS Node Pool Upgrade Settings](https://docs.microsoft.com/azure/aks/use-multiple-node-pools#upgrade-settings)