OpenStack Havana and IPv6

OpenStack Havana (8th release) is available on October 17 with 400+ new features. However, it brought very little excitement for IPv6 fans: users still cannot launch IPv6-based VMs.

After running out of patience, we immersed ourselves in the lab for several weeks and achieved the following goals:

  • All OpenStack infrastructure nodes communicated with each other by IPv6
  • User could spin up dual-stack VMs in multi-tenant environment
  • VMs gained connectivity to existing IPv6 network beyond OpenStack boundary

Although Havana release note didn’t mention any IPv6 limitations, what we found were:

  • Router Announcement was not sent to internal tenant network by default
  • DHCP process was bound to IP other than default gateway of tenant network
  • Neighbor Discovery packets were dropped by default by ip6tables filter rules
  • NAT and GARP were turned on for IPv6 subnets. Not desirable!

More details can be found in our whitepaper published at



Plan the move to the Cloud with IPv6 as a key Capability

IT organization’s today are planning the move to Cloud Computing. I am sitting here and thinking we have exhausted theIPV4 address space – so the future is IPv6. If IT organizations are doing the planning to choose the right Cloud delivery models and the right Service Providers, they might as well do the IPv6 assessment and planning at the same time.

The meticulous planning that Enteprises are going through for the Cloud contain all the same underlining components which are part assessment and analysis for determining IPv6 readiness.  They are reviews of:

  • Infrastructure elements
  • Operating Systems
  • Web Services, Application and Databases
  • Service Management Orchestration Tools
  • Security and Risk Impact
  • People and Process.
Are the providers that you choose for either IaaS/PaaS/SaaS capable of delivery IPv6 services across the stack? It will impact your business sooner than you expect.

Other elements, such as infrastructure design and implementation of solutions like  VBLOCK or FLEXPOD are IPv6 ready in addition to network services like Firewalls, Load Balancers, IPS, VPN-GWs to name a few.

If the plan is to move the Applications/Middleware into the Cloud and future proofing it for Next Generation make sure that the Web/Middlware/Applications and Databases are also v6 ready.

In conjunction with addressing the infrastructure, you need to educate the DC/Cloud Architects, Subject Matter Experts and IT Operations team to get ready for IPV6.

Yes the amount of changes required is considerable. But compared to the work that the teams are currently engaged in for strategy and planning for the Cloud the extra efforts will be well worth to futureproof the systems for IPv6.