How ipspace/pubcloud works
Project type and purpose
• This repository is an *infrastructure-as-code* sample library for demonstrating public-cloud networking. It is not a traditional full-stack app but a set of Terraform modules, Ansible playbooks, CLI/PowerShell/Bash scripts and CloudFormation/ARM templates targeting AWS and Azure networks.
File structure
• Top-level components:
• AWS/ – advanced AWS networking scenarios (IP multicast, VPC peering, WAF, NLB, Transit Gateway)
• Azure/ – Azure networking scenarios (route server, virtual WAN with multiple test-beds)
• Deployment/ – “consumers” of those modules: step-by-step AWS & Azure deployments via Terraform, Ansible, CLI, CloudFormation/ARM
• install/ & Vagrantfile – scripts and Vagrant to spin up a local Ubuntu dev VM
• Under each cloud directory you see a typical Terraform module layout (modules/* with compute/network/… tf files), scenario definitions, and in Deployment you see playbooks (Ansible tasks/steps), CLI scripts, and IaC templates.
README for additional insights
• The README confirms these are *provisioning & automation examples* for public-cloud networking courses and demos.
• No pre-drawn architecture; we must illustrate how pieces fit.
1. Developer Environment
• Vagrant VM
• install/ scripts
2. Code Repository
• AWS examples (IP-multicast, VPC-peering, WAF, NLB, TGW)
• Azure examples (route-server, virtual-wan)
• Deployment orchestrators (Terraform, Ansible, CLI, CloudFormation/ARM)
3. Provisioning Engines
• Terraform CLI
• Ansible Engine
• AWS CLI & Azure CLI scripts
• CloudFormation & Azure Resource Manager
4. Target Clouds
• AWS account(s)
• Azure subscription(s)
• From Developer Environment → Code Repository (git pull / edit)
• Developer runs Provisioning Engines locally (Terraform, Ansible, CLI) against code in repo
• Provisioning Engines call Cloud Provider APIs
• Cloud Provider APIs create/modify Networking resources in AWS/Azure
c. Architectural patterns & design principles:
• *Modular IaC*: reusable modules for compute, network, peering, WAF, transit
• *Separation of concerns*: cloud-agnostic orchestration (Deployment/) separated from cloud-specific modules (AWS/, Azure/)
• *Layered approach*: root configurations delegate to nested modules, testbed scenarios invoke common modules
d. Key technologies/frameworks:
• Terraform (HCL modules, variables, outputs)
• Ansible playbooks & inventory
• AWS CloudFormation / Azure Resource Manager templates
• Bash/PowerShell + AWS CLI / Azure CLI