Defining network pools

 

Network pools are used to provide addressation pools in your cloud. Until the fully virtualized, isolated networks could use any addresses defined by user, the routed and public networks should be limited by cloud administrator. This is especially important to not collide with internal cloud and infrastructure addressation.

Required network pools

Each cloud requires at least three network pools. All of them should have public access.

First one is the isolated network. This pool allows to create isolated, fully virtualized networks in your cluster. Isolated networks allow users to select any addressation. This network is fully isolated, it means that there will be no address collisions across your physical networks and virtual networks.

The second pool is routed. It allows to create small subnets used to transfer high volumes of data across cluster's network, also with using Infiniband technology. This type of network is also the most tolerant for fails, in redundant connections. It is default medium for all virtual machines to access the Internet. When assigning IPv4 address pool, be carreful to not collide addressation with your existing network. Routed networks use OSPF protocol to advertise network presence on particular Computing Nodes.

The last one pool is used for public redirections. You can define it as not-public ip set, but it should be present in your final setup. Public networks allow to redirect public IPs from this pools to routed addresses.

Go to the Admin site

Log into the Administrator's panel and find Network pools at the main screen: Click + Add next to the Network pools to create new template.

Create new isolated network pool

Set the access to public, address to 0.0.0.0, mask to 0 and mode to isolated: All other parameters might be default.

At the bottom of page click Save button.

Try to define new isolated network in CoreUI

Your network pool should be ready to use. Log in to the CoreUI interface and try to create one isolated network. This should cause creation new network namespace in a few seconds. Check if there is present network namespace related to your network's ID:

sudo ip netns show

Create new routed network pool

Set the access to public, address and mask to arbitrary IPv4 pool, not colliding with your existing networks. Set mode to routed: All other parameters might be default. In above example network uses addressation 10.128.0.0-10.255.255.255. This leaves whole bottom half of 10.0.0.0/8 network for your purposes, i.e. for addressing physical nodes in your cloud.

At the bottom of page click Save button.

Try to define new routed network in CoreUI

Your network pool should be ready to use. Log in to the CoreUI interface and try to create one routed network. Then create new virtual machine with lease attached to this network. This step could be done when your storage is ready. After launching your VM you should be able to see new route path in Management Node:

route -n

Create new public network pool

Set the access to public, address and mask should be arbitrary IPv4 pool, not colliding with your existing networks. Set mode to public: All other parameters might be default. In above example network address is 192.168.0.0/16. It might be used only when you are not using any of 192.168.x.x networks or subnetworks. The public IP pool might be also any public IPv4 addressation pool if you have one.

At the bottom of page click Save button.

< Go back     Author: Maciej Nabozny Published: Sept. 29, 2016, 2:11 p.m.