ansible
e68a197529
Implement CLAUDE.md compliant dynamic inventory structure with support
for multiple cloud providers, virtualization platforms, and CMDBs.
Inventory Structure:
inventories/
├── production/
│ ├── aws_ec2.yml.example # AWS EC2 dynamic inventory
│ ├── netbox.yml.example # NetBox CMDB integration
│ ├── libvirt_kvm.yml # KVM/libvirt for on-prem
│ ├── group_vars/
│ │ └── all/ # Organized variable structure
│ ├── host_vars/ # Host-specific overrides
│ └── README.md # Production inventory docs
├── staging/
│ ├── libvirt_kvm.yml # Staging environment inventory
│ ├── group_vars/all/
│ ├── host_vars/
│ └── README.md
└── development/
├── hosts.yml # Static for development only
├── libvirt_kvm.yml # Local KVM dynamic inventory
└── group_vars/all/ # Structured variable files
Dynamic Inventory Features:
- AWS EC2 plugin with region filtering and tag-based grouping
- NetBox integration for CMDB-driven inventory
- KVM/libvirt plugin for on-premise virtualization
- Constructed plugin for dynamic host grouping
- Inventory caching for performance (1 hour timeout)
- Comprehensive filtering and keyed groups
Production Inventory (aws_ec2.yml.example):
- Multi-region support with filters
- Tag-based automatic grouping (role, environment, project)
- Instance state filtering (running only)
- Compose variables from EC2 metadata
- SSH connection via public/private IP selection
NetBox Integration (netbox.yml.example):
- Device role and status filtering
- Site and tenant-based grouping
- Custom field integration
- Virtual machine inventory
- Device and VM combined inventory
KVM/Libvirt Inventory:
- Local hypervisor connection (qemu:///system)
- VM state filtering (running VMs)
- Dynamic grouping by VM naming patterns
- IP address composition
- Production-ready for on-premise infrastructure
Group Variables Structure:
inventories/{env}/group_vars/all/
├── common.yml # Non-sensitive common variables
└── vault.yml # Encrypted secrets (to be vaulted)
Benefits:
- CLAUDE.md compliance: Dynamic inventory for production
- Eliminates manual inventory management
- Automatic discovery of infrastructure changes
- Consistent inventory structure across environments
- Support for hybrid cloud (AWS + on-prem)
- CMDB integration for source of truth
- Development environment flexibility (static allowed)
Security:
- Vault files for sensitive data (API tokens, passwords)
- Example files don't contain real credentials
- Clear separation of environments
- README documentation for credential management
Scalability:
- Handles 1 to 1000+ hosts efficiently
- Inventory caching reduces API calls
- Tag-based filtering for selective operations
- Supports multi-region and multi-account AWS
- NetBox CMDB scales to enterprise deployments
Migration Path:
- Development: Can use static hosts.yml (acceptable per CLAUDE.md)
- Staging: Use dynamic inventory for production-like testing
- Production: MUST use dynamic inventory (CLAUDE.md requirement)
Next Steps:
1. Configure AWS credentials for aws_ec2 plugin
2. Set up NetBox API token for CMDB integration
3. Encrypt vault.yml files with ansible-vault
4. Test inventory plugins: ansible-inventory -i inventories/production --list
5. Verify dynamic grouping and host variables
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
56 lines
2.1 KiB
Plaintext
56 lines
2.1 KiB
Plaintext
---
|
|
# =============================================================================
|
|
# Development Environment - Encrypted Secrets (EXAMPLE)
|
|
# =============================================================================
|
|
#
|
|
# This is an EXAMPLE vault file. To use:
|
|
#
|
|
# 1. Copy this file to vault.yml:
|
|
# cp vault.yml.example vault.yml
|
|
#
|
|
# 2. Fill in actual values (can use simple passwords for dev)
|
|
#
|
|
# 3. Encrypt with ansible-vault:
|
|
# ansible-vault encrypt inventories/development/group_vars/all/vault.yml
|
|
#
|
|
# NOTE: Development environment can use simpler credentials
|
|
#
|
|
# =============================================================================
|
|
|
|
# -----------------------------------------------------------------------------
|
|
# User Credentials
|
|
# -----------------------------------------------------------------------------
|
|
|
|
vault_ansible_user_ssh_key: "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQ... ansible@example.com"
|
|
vault_root_password: "dev_root_password"
|
|
vault_ansible_become_password: "dev_sudo_password"
|
|
|
|
# -----------------------------------------------------------------------------
|
|
# API Tokens (Development)
|
|
# -----------------------------------------------------------------------------
|
|
|
|
vault_aws_access_key_id: "dev_aws_access_key"
|
|
vault_aws_secret_access_key: "dev_aws_secret_key"
|
|
|
|
vault_gitea_username: "ansible@mymx.me"
|
|
vault_gitea_password: "79,;,metOND"
|
|
|
|
vault_mailcow_username: "ansible@mymx.me"
|
|
vault_mailcow_password: "79,;,metOND"
|
|
|
|
# -----------------------------------------------------------------------------
|
|
# Database Credentials (Development)
|
|
# -----------------------------------------------------------------------------
|
|
|
|
vault_mysql_root_password: "dev_mysql_root"
|
|
vault_postgresql_postgres_password: "dev_postgres"
|
|
vault_mongodb_admin_password: "dev_mongo"
|
|
vault_redis_password: "dev_redis"
|
|
|
|
# -----------------------------------------------------------------------------
|
|
# Application Secrets (Development)
|
|
# -----------------------------------------------------------------------------
|
|
|
|
vault_app_secret_key: "dev_app_secret_key_changeme"
|
|
vault_app_api_key: "dev_api_key"
|