Services > Network

OpenStack Neutron


Neutron is the software defined networking solution of the OpenStack project. Komponentes provides “network as a service” between interface devices (e.g. vNICs) managed by other OpenStack services (e.g. nova). Neutron is an important and central part of the OpenStack platform.


Why Neutron?

  • Give cloud users an API to create network topologies and configure advanced network policies in the cloud
    Example: Creating a multi-level web application topology
  • Basis for advanced network services available to users
    Examples: LBaaS, VPNaaS, Cloud Interconnect
  • Horizon GUI support for:
    • Neutron L2 and L3 network and subnet creation/deletion
    • Booting VMs on specific Neutron Networks

Our Highlights

We offer the highest availability of all our services. The Neutron components are highly available.

Extended network capabilities through extensions (DHCP, VPNaaS, etc.)

The user can build advanced network services himself

Our service supports the Horizon GUI


OpenStack Networking (Neutron) is the component of the OpenStack project, which implements the network connectivity of the various services available. The user is offered the possibility to configure the underlying SDN of the noris cloud via Neutron API ( The noris cloud uses a distributed implementation of the Neutron service to enable best scalability. The service provides Layer 3 connectivity to the Internet.

The following Neutron options are available to the user:

  • Layer 2 Network
    The user has the possibility to configure 2 networks per tenant layer which are routed via VxLAN between the individual hypervisors.
  • Layer 3 Network
    The user has the possibility to configure per tenant layer 3 networks (subnets) into existing layer 2 networks.
  • Routers
    You can route between configured networks by creating routers according to traffic.
  • Floating IPs
    By default, configured Layer 3 networks cannot be accessed from the Internet. To make services available on the Internet, at least one IP must be assigned to a port on the compute resource from a pool of public floating IPs. Neutron takes care of the configuration of the corresponding NAT rules.
  • Security Groups
    By default, all incoming traffic to compute resources is blocked in the noris cloud. Outgoing traffic is allowed by default. To open incoming ports to the Internet, a rule must be created here in a security group that allows corresponding networks to access a specific port. Security groups realize this possibility of firewalling via IPtables on the hypervisors. Security Groups can be assigned to one or more compute resources.
  • DHCP
    For configured Layer 3 networks, DHCP pools are available to the user, which can be mapped either statically or dynamically to compute resources.