update ansible hosts

[DaMandal0rian]

Add Subspace Network Infrastructure to Ansible Inventory

Overview

This PR expands our Ansible inventory to include all Subspace network infrastructure nodes, organizing them by network type and service function for better management and deployment automation.

Changes Made

🌐 Added Mainnet Network Nodes

• Bootstrap nodes: 5 nodes across different providers (Hetzner, Alibaba Cloud, AWS)
• Timekeeper nodes: 3 nodes for network time synchronization
• RPC nodes: 3 nodes for blockchain API access
• Domain nodes: 2 Auto-EVM nodes for domain-specific operations
• Specialized nodes: Integration operator and farmer-genesis nodes

🚀 Added Taurus Network Nodes

• Bootstrap nodes: 5 nodes including Azure deployment
• Timekeeper node: 1 dedicated timekeeper
• RPC nodes: 2 nodes for API services
• Domain nodes: 2 Auto-EVM nodes

📊 Added SubQL Infrastructure

• Blue/Green deployment structure for zero-downtime updates
• Mainnet SubQL: 2 nodes (1 blue, 1 green environments)
• Taurus SubQL: 2 nodes (1 blue, 1 green environments)
• Organized for easy blue/green deployment management

🚗 Added Auto Drive Services

• Mainnet Auto Drive: Private, public, and staging environments
• Taurus Auto Drive: Private, public, and staging environments
• Multi-network gateway: Cross-network coordination node

📁 Added Files Gateway Services

• Staging environments: Both Taurus and Mainnet
• Production environments: Both Taurus and Mainnet
• Organized by environment for controlled deployments

Inventory Structure

New Group Hierarchies

subspace_networks/
├── mainnet/
│   ├── mainnet_bootstrap
│   ├── mainnet_timekeeper
│   ├── mainnet_rpc
│   ├── mainnet_domain
│   ├── mainnet_other
│   ├── mainnet_subql_blue
│   ├── mainnet_subql_green
│   └── mainnet_auto_drive
├── taurus/
│   ├── taurus_timekeeper
│   ├── taurus_bootstrap
│   ├── taurus_rpc
│   ├── taurus_domain
│   └── taurus_auto_drive
└── services/
    ├── all_subql (blue/green deployments)
    ├── all_auto_drive (cross-network)
    ├── files_gateway (staging/production)
    └── all_gateways

Node Metadata Added

Each node now includes structured metadata:

• node_name: Semantic node identifier
• node_type: Service type (bootstrap, rpc, subql, auto_drive, etc.)
• environment: Deployment environment (private, public, staging, production)
• network: Network association (mainnet, taurus, multinetwork)
• subspace_path: Installation directory path
• deployment_color: Blue/green deployment tracking (SubQL nodes)

Usage Examples

Network-specific deployments:

# Deploy to all mainnet nodes
ansible-playbook -i hosts.yml deploy.yml --limit mainnet

# Deploy to taurus network only
ansible-playbook -i hosts.yml deploy.yml --limit taurus

Service-specific deployments:

# Update all RPC nodes
ansible-playbook -i hosts.yml update-rpc.yml --limit mainnet_rpc,taurus_rpc

# Blue/green SubQL deployment
ansible-playbook -i hosts.yml deploy-subql.yml --limit subql_blue
ansible-playbook -i hosts.yml deploy-subql.yml --limit subql_green

Environment-specific deployments:

# Deploy to staging environments only
ansible-playbook -i hosts.yml deploy.yml --limit auto_drive_staging,files_gateway_staging

# Production files gateway update
ansible-playbook -i hosts.yml update.yml --limit files_gateway_production

Infrastructure Overview

• Total new nodes: ~35 servers across multiple cloud providers
• Networks supported: Mainnet, Taurus, Multi-network gateway
• Service types: Bootstrap, Timekeeper, RPC, Domain, SubQL, Auto Drive, Files Gateway
• Deployment patterns: Blue/green for SubQL, environment-based for services
• Cloud providers: AWS, Hetzner, Alibaba Cloud, Azure

[github-actions]

Failed to generate code suggestions for PR