Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Date: Wed, 27 Feb 2013 20:07:13 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-dev@incubator.apache.org
Message-ID: <JIRA.12615145.1352287664319.352542.1361995633650@arcas>
In-Reply-To: <JIRA.12615145.1352287664319@arcas>
References: <JIRA.12615145.1352287664319@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-452) IPv6 support
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588700#comment-13588700 ] 

ASF subversion and git services commented on CLOUDSTACK-452:
------------------------------------------------------------

Commit 476687d931596bee0f50a08bdf107d6c505e0072 in branch refs/heads/4.1 from Jessica Wang <jessicawang@apache.org>
[ https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;h=476687d ]

Revert "CLOUDSTACK-452: cloudstack UI - network menu - guest network section - network detail - add IPv6 CIDR field, IPv6 Gateway field."

This reverts commit a565d0b699478849d88730faf8a9c9bf7892aef3.

                
> IPv6 support
> ------------
>
>                 Key: CLOUDSTACK-452
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-452
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Wido den Hollander
>            Assignee: Sheng Yang
>             Fix For: Future
>
>
> This is quite a large feature, but we are lacking complete IPv6 support at this moment.
>  
> We should support IPv6 for: 
> - The Management server itself 
> - Communication with the Hypervisors 
> - Communication with the System VMs 
> Those three are probably the easiest work, we also need to support IPv6 for instances.
>  
> In both the Advanced and Basic zone Instances should be able to get a non-NAT true and native IPv6 address.
>  
> We should also not limit them to having one IP, they should be able to get multiple IPv6 addresses.
>  
> In the basic zone it can be done pretty easily by having the Virtual Router also hand out IPv6 over DHCPv6 and have your router in the network handle the gateway work.
>  
> In the advanced zone it becomes more difficult. 
> One way could be that the network admin creates a static route for a /48 towards a Virtual Router and then the VR can hand out /64s to Instances.
>  
> But static routing can become a problem, so you might want to use OSPF, LISP or even iBGP for getting those prefixes to the VR.
>  
> This is a big feature, but I think the Basic zone is the easiest for now. 
> In the Advanced Zone you COULD keep everything behind the VR IPv4 and have the VR do IPv6 loadbalancing, but that would still not be true IPv6 connectivity.
>  
> NAT in the VR seems like a firewall, but a true statefull firewall in the VR could do the same while the Instances still have publicly routeable IPv6 addresses.
>  
> There is no functional spec on this yet, but we have to keep this in mind that we need IPv6 support. People are running out of IPv4 space. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira