Bug Reference

CLOUDSTACK-9853 - Getting issue details... STATUS

Introduction

Since version 4.10 there is support for IPv6 in Basic Networking, but this is limited to a single address (/128) per Instance.

The feature is that using DHCPv6 Prefix Delegation the Instances can get a subnet, for example a /60 routed to them.

A routed IPv6 subnet allows for multiple features inside Instances, not limited to, but for example:

• (Docker) containers with native IPv6 inside a Instance
• VPN tunnels with native IPv6

Goals

The goals for IPv6 Prefix Delegation are in Basic Networking are:

• Management server understanding address pools and handing out subnets
• Virtual Router supporting handing out IPv6 Prefixes to Instances

Since the Virtual Router in Basic Networking does not function as a gateway it is up to the network administrator to configure (static) routes for the subnets towards the Instances.

For example: 2001:db8:200:1:/60 -> 2001:db8:100:0:9804:6f0a:990a:a798

Scope

This document only covers IPv6 Prefix Delegation where Instances are able to obtain a subnet using DHCPv6 PD.

Feature Specification

In addition to having a single IPv6 address Instances will be able to have a IPv6 subnet routed to them.

The management server will need to understand a IPv6 Address Pool from where it can assign subnets to Instances when requested.

Per POD a subnet (for example /48) can be configured from which a pre-defined size of subnets (for example /60) can be assigned to Instances.

When a Instance is deployed and a subnet is requested the management server will assign a new subnet and record it in the database.

During deployment it will add this information to dnsmasq on the VR so that the Instance obtains a proper DHCPv6+PD response from dnsmasq when it requests a subnet.