Details
-
Task
-
Resolution: Won't Fix
-
Major
-
None
-
3.0
-
None
-
Security Level: Public
-
Linux (customer has IPv6 only network/servers; wants to know Couchbase position on IPv6 - deployment and support)
Description
Question raised by prospective customer require evaluation, assessment, statement of support. current focus will be latest 3.0 candidate, but may require re-assessment of latest 2.5.1. required target environment is: IPv6 client and IPv6 only network (i.e., no IPv4 messages allowed by routers/switches over external network). approach is to certify Couchbase and its components. current belief is that the couchbase server cluster will require dual stack implementation on each server node.
goal is to describe just what IPv6 based interconnect topology is possible; identify where coding practices in Couchbase may require change to be either IPv4/IPv6 insensitive/detect IPversion and adapt automatically; or use existing parameters at startup to determine IPversion and adjust.
tasks:
1) identify current usage. examine all open ports by running Couchbase system (memcached, couchbase server, couchbase replicate and XDCR)
2) identify any IPv4 only calls/parameters in above Couchbase components
3) attempt install of a full deployment of Couchbase server on IPv6 only configured cluster.
4) attempt various client stacks (Java, Python, cli) where no IPv4 connection between client and server platform is allowed
5) determine if IPv4 connections between server components required/allowed in dual stack IPv4/IPv6 cluster
6) document IPversion specific coding standards; identify any components not currently IPv6 capable - task list for future release
7) repeat for Couchbase 2.5.1