Files
smom-dbis-138/docs/azure/QUOTA_ANALYSIS_SUMMARY.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

2.2 KiB
Raw Blame History

Quota Analysis Summary

Current Quota Status

vCPU Quota

  • Total Limit: 10 vCPUs
  • Currently Used: 6 vCPUs (3 nodes × Standard_D2s_v3 @ 2 vCPUs each)
  • Available: 4 vCPUs

Other Quotas (All Available)

  • Virtual Machines: 3 / 25,000
  • Virtual Machine Scale Sets: 1 / 2,500
  • Availability Sets: 0 / 2,500
  • standardBSFamily: 0 / 10 (B-series available)
  • standardDSv3Family: 6 / 10 (D-series, 4 more available)

Optimized Configuration

Selected VM Sizes

  • System Pool: Standard_D2s_v3 (2 vCPUs, 8GB RAM) - Keep existing
  • Validators: Standard_B1ms (1 vCPU, 2GB RAM) - New, burstable
  • Sentries: Standard_B1ms (1 vCPU, 2GB RAM) - For future
  • RPC: Standard_B1ms (1 vCPU, 2GB RAM) - For future

Deployment Plan

Phase 1 (Current - Fits Quota):

  • System: 3 × Standard_D2s_v3 = 6 vCPUs (existing)
  • Validators: 2 × Standard_B1ms = 2 vCPUs (new)
  • Total: 8 vCPUs (within 10 limit)

Phase 2 (After Quota Increase):

  • Sentries: 1-3 × Standard_B1ms = 1-3 vCPUs
  • RPC: 1-3 × Standard_B1ms = 1-3 vCPUs

Why Standard_B1ms?

Advantages

  1. Fits Quota: 1 vCPU per node, allows 2 validators with 4 available vCPUs
  2. Cost Effective: ~$0.01/hour vs $0.096/hour (90% savings)
  3. Burstable: CPU credits for variable workloads
  4. Sufficient for Besu: 1 vCPU, 2GB RAM meets minimum requirements
  5. Available: standardBSFamily quota is 0/10 (plenty available)

Considerations

  • CPU Credits: B-series uses burst credits, monitor usage
  • Performance: May need upgrade for production workloads
  • Scaling: Can upgrade to Standard_B2s or Standard_D2s_v3 later

Cost Analysis

Current Monthly Cost

  • 3 × Standard_D2s_v3: ~$210/month
  • 2 × Standard_B1ms: ~$15/month
  • Total: ~$225/month

If Replaced All with B1ms

  • 5 × Standard_B1ms: ~$38/month
  • Savings: ~$172/month (76% reduction)

Next Steps

  1. Review quotas - Complete
  2. Select VM sizes - Standard_B1ms selected
  3. Update configuration - terraform.tfvars updated
  4. Deploy validators - Ready to apply
  5. Monitor performance - After deployment
  6. Scale up - After quota increase or validation