Network concepts
Overview
Network concepts
Background and rationale for the building blocks that make up the Network service. Read these to understand what each primitive is, how it relates to the others, and why the platform models networking the way it does. For step-by-step instructions, see the how-to guides.
Concepts
- Floating IPs: The Network service (OpenStack Neutron) implements floating IPs as public addresses you attach to an instance on a private network when you need reachability from the internet or another external...
- IP Address Management: Instances on Quake AI receive at least one private IP address from the subnet they connect to. How that address is allocated, how it reaches the guest OS, and what happens when you need multiple...
- Networks: Networks are isolated Layer 2 segments that give your instances connectivity. Instances attach to at least one network; most production deployments use private networks with routers and floating IPs...
- Ports: The Network service (OpenStack Neutron) implements ports as the logical attachment between a network and a device, most often a VM’s virtual NIC, but also router interfaces and other integrations...
- Routers: The Network service (OpenStack Neutron) implements routers as virtual layer-3 gateways inside your project. They connect private subnets to each other and, when you set an external gateway, to...
- Security Groups: The Network service (OpenStack Neutron) implements security groups as stateful packet filters attached to instance ports. Each rule describes allowed traffic by direction (ingress or egress), IP...
Also known as
- Cloud Firewalls on Quake AI: Provider firewalls, security lists, and cloud firewalls filter traffic to VMs. On Quake AI port-level rules are security groups in the Network service (OpenStack Neutron).
- Elastic IPs and Static Public Addresses: Elastic IP (AWS), reserved IP (DigitalOcean), static external IP (GCP), and public IP (Azure) names all describe a stable public address you attach to a workload. On Quake AI that role is a floating...
- VPC on Quake AI: Quake AI does not expose a single object named VPC or virtual private cloud. The same job is done with networks (including subnets as IP ranges inside a network), routers (routing and NAT between...
Common Network tasks
See Also
Was this page helpful?