The Networking service allows you to create and manage network resources, such as networks, subnets, and ports, to use with other services. You can create a private network to manage network resources without requiring administrative priviledges. These self-service networks are entirely virtual and require virtual routers to interact with provider and external networks and provide DHCP and metadata services to instances. See Networking Overview for more information about the Metacloud Networking service, including provider and project networks.
|Subnet||A block of IP addresses used to allocate to ports created on the network.|
|Port||A connection point for attaching a single device, such as the NIC of a virtual server, to a virtual network. Port attributes include the resource MAC address and the assigned fixed IP address on the subnet.|
|Router||A virtual device that provides routing between self-service networks and provider networks or other self-service networks belonging to the project. The Networking service uses a layer-3 agent to manage routers.|
|Security group||A set of virtual firewall rules that control ingress (inbound to instances) and egress (outbound from instances) network traffic at the port level.|
|DHCP||An agent that manages IP addresses for instances on provider and self-service networks. The Networking service implements the DHCP service using an agent that manages qdhcp namespaces and the dnsmasq service.|
|Metadata||An optional service to pass data to an instance during initialization, such as property key and value pairs. Requires default egress rules for access to TCP port 80 to allow instances to retrieve metadata.|