Files
smom-dbis-138/docs/guides/README_VM_DEPLOYMENT.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

60 lines
1.3 KiB
Markdown

# VM Deployment Quick Reference
## Overview
The Besu network can be deployed on Azure Virtual Machines (VMs) or Virtual Machine Scale Sets (VMSS) with Docker Engine, as an alternative to AKS deployment.
## Quick Start
### 1. Enable VM Deployment
```bash
# Set VM deployment enabled in terraform.tfvars
vm_deployment_enabled = true
```
### 2. Configure Variables
```bash
# Copy example file
cp terraform/terraform.tfvars.vm.example terraform/terraform.tfvars.vm
# Edit with your values
nano terraform/terraform.tfvars.vm
```
### 3. Deploy
```bash
cd terraform
terraform init
terraform plan -var-file=terraform.tfvars.vm
terraform apply -var-file=terraform.tfvars.vm
```
## Features
- ✅ Individual VMs or VM Scale Sets
- ✅ Multi-region deployment
- ✅ Automatic Docker installation
- ✅ Automatic Besu configuration
- ✅ Cloud-init setup
- ✅ Managed Identity for Key Vault
- ✅ Boot diagnostics
- ✅ Network security groups
## Node Types
- **Validators**: Private subnets, no public IPs
- **Sentries**: Public IPs, P2P enabled
- **RPC Nodes**: Public IPs, RPC enabled
## Documentation
See [VM Deployment Guide](docs/VM_DEPLOYMENT.md) for detailed instructions.
## Comparison
See [Deployment Comparison](docs/DEPLOYMENT_COMPARISON.md) for AKS vs VM deployment comparison.