Managing IP Pools

You can monitor and manage a set of available IP addresses on Platform using the Cluster > IP Pool section of JCA. Herewith, the three pools of addresses are separated and are managed through the separate subsections:

  • Internal IPv4
  • Public IPv4
  • Public IPv6

Within these sections you can monitor a set of available free and busy IP addresses, displayed with the appropriate environment domains (if any) and regions, where these IPs are available.

In the shown table you can find the following information:
  • IP address - lists all of the IPs in a pool
  • Status - indicates whether the IP is in use (the red busy label) or is available for users (the green free label)
  • Environment - displays name of the environment, which includes a container with the corresponding address bound. Clicking on a particular domain will redirect you to the Cluster > Environments section, where the detailed information on the chosen environment will be shown
  • Region - shows a physical location of the hardware a particular IP belongs to

Using the upper tool panel, you can filter this list in order to show only those IP addresses, that Starts / Ends with the stated IP (specified within the blank input field next to the filtering drop-down list) or have Any match with it. In addition, you can select a particular Status (i.e. all, busy and free) and/or a Region for the addresses to be separated out.

Once all of the required parameters are stated, just click on Search to apply filtering. Subsequently, you can select Clear to remove the conditions and show the whole list of IPs.

Tip: Also, you can click on a particular domain name (with an assigned address) for viewing information on the corresponding Environment within the same-named section to the right.

Here, you can find the following environment data, divided into columns:
  • Name - name of the chosen environment with the expandable list of all instances it includes and deployed contexts
  • ID - unique ID value for each instance
  • IP address - all bound IP’s, both internal and external (if are any) ones
  • Hardware node - name and IP address of the hardware node, where a particular instance is located
  • Node Mission - type of the used software stack

Select a separate container within this area if you want to migrate it to another hardware node.
In addition, you are able to perform the following operations with the Public IP pools:

Migrate a Container

You can migrate any node with busy IP (regardless of whether it’s internal or external address). For that, choose the required IP address from the list and navigate to the opened Environment section at the right. Then select the necessary container and click the Migrate button above.

In the opened dialog box, specify the destination hardware Node using the drop-down list and and Migration Mode (either offline or online).

Click Migrate to proceed.

Add Public IPs

If you run out of external IP addresses for your cluster nodes, you can add a new IPs in the following way:

IPv4 Range

1. Navigate to the IP Pool > Public IPv4 and select the Add IP range button at the toolbar.

2. In the opened Add IP range dialog frame, type the Start and End IPs, tick at least one region within the list below (for these addresses to be available at) and click Add.

Tip: You are also able to add a new range of Public IPs from a new subnet.

As a result, IPs from the specified range will appear in the list.


IPv6 Network

1. Navigate to the IP Pool > Public IPv6 > Networks and select the Add button at the toolbar.

2. In the opened Add IPv6 Network frame, type your Network with the appropriate prefix being specified after the “/” character (e.g. 0000:0000:0000:0000:0000:0000:0000:0000/80). Next, tick the required Regions from the list below (for these addresses to be available at) and click Add to attach the specified network.

Note: The specified IPv6 address sets should be preliminarily routed to the appropriate hardware node(s) within the ticked regions.

This can be done through adjusting the appropriate configuration files:
  • /etc/sysconfig/network

    NETWORKING_IPV6=yes
    IPV6FORWARDING=yes
    IPV6_DEFAULTDEV=eth0
    IPV6_DEFAULTGW=aaaa:bbbb:a01a::1

    IPV6_AUTOCONF=no

  • /etc/sysconfig/network-scripts/ifcfg-ethX (where X is your interface number)

    IPV6INIT=yes

    IPV6ADDR=aaaa:bbbb:cccc:0000:0100::1/ddd

  • /etc/sysctl.conf

    net.ipv6.conf.default.forwarding = 1
    net.ipv6.conf.all.forwarding = 1
    net.ipv6.conf.all.proxy_ndp = 1

Remove Public IP Address

In case a particular IPv4 address is no longer needed, select it with the left-hand check-box and press the Remove button at the toolbar above. Herewith, you cannot delete an IP address, which is in use (i.e. has the busy status).

After the deletion, this address will disappear from the list and all of the information about it will be removed from Jelastic DB.

Note: In order to delete the IPv6 addresses the appropriate network should be removed.

IPv6 Subnets

When user attach IPv6 to an environment, it receives not a single address, but a Subnet of 1024 IPs by default, which is automatically allocated from the network.

If needed, the exact number of addresses per subnet can be manually tuned with the help of the jelastic.ip.v6.subnet.prefix setting. It receives the prefix length for IPv6 addresses, that will be used to slice the whole network into subnets for environments.

For example, the prefix of 118 means the last 10 bits of the IPv6 address (i.e. total of 128 bits minus the specified 118) will be used as subnet, which is equal to 210 = 1024 addresses.