OSOpenStack Learning Academy
INTERVIEW PREPARATION

OpenStack Question & Answer Bank

All 50 questions from the supplied senior interview guide, grouped by module.

MODULE D · Q26–Q32

Networking (Neutron)

Q26. What is Neutron?
Neutron is OpenStack's Networking service. It provides APIs for networks, subnets, ports, routers, security groups and floating IPs. It connects instances to tenant or provider networks and can provide routing, DHCP, address allocation and security through configured backends and agents. Neutron supports legacy agent-based deployments and OVN. It abstracts network provisioning while translating requests into underlying network configuration.
Q27. What are the common network virtualization types available to tenants in Neutron?
Common types include VXLAN, GRE and Geneve overlays, which encapsulate tenant traffic across an IP underlay. VLAN uses 802.1Q tags and requires the physical network to carry the VLANs. Flat provides untagged connectivity on a configured physical network. Availability depends on ML2 type/mechanism drivers, physical mappings and operator configuration. Tenants can create only types exposed by administrators.
Q28. What is the structural difference between a Provider Network and a Tenant Network?
A provider network is created by or controlled by the administrator and maps to a physical network or segment, such as VLAN or flat. It often connects instances to a data-center network. A tenant network is created by a project user within permitted options and is often an isolated overlay such as VXLAN or Geneve. Provider networks depend on physical configuration; tenant overlays provide logical isolation over shared infrastructure.
Q29. What is the purpose of a Security Group in Neutron and how does it operate?
A security group is a virtual firewall policy applied to Neutron ports. It contains ingress and egress rules for protocol, port range and remote IP prefix or security-group reference. Common configurations are stateful, allowing return traffic for permitted connections. Enforcement depends on backend such as Open vSwitch or OVN. Security groups operate at virtual ports and complement physical firewalls.
Q30. Explain the role and function of the Neutron L3 Agent.
In legacy agent-based Neutron, the L3 agent manages virtual routers and implements routing and NAT, often using Linux network namespaces and virtual interfaces. It routes between tenant and external networks and can handle floating-IP NAT. OVN deployments commonly implement logical routing and NAT through OVN components instead. Identify whether the deployment uses legacy L3 agents or OVN.
Q31. What are Floating IPs in OpenStack and how do they function under the hood?
A floating IP is an externally reachable address associated with an instance's Neutron port, usually through a router connected to an external network. In a typical legacy deployment, the router performs NAT between floating and fixed IPs. This enables external access without changing the guest's internal address. The address must come from an external pool, and routing, security rules and upstream reachability must be correct. OVN implementation differs.
Q32. What is Open Virtual Network (OVN) and why is it used in place of legacy Neutron agents?
OVN is a network virtualization system providing logical switching, routing, ACLs and NAT. Neutron's ML2/OVN driver translates Neutron resources into OVN logical configuration. OVN uses northbound and southbound databases and local Open vSwitch integration to distribute configuration. It can replace several legacy agent functions in supported designs. It is a distributed control- and data-plane architecture, not one agent.