Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.9.0-b1
-
Component/s: None
-
Labels:None
Description
Feature request @ https://requests.blesta.com/topic/add-the-ability-to-assign-an-ipv6-subnet-and-ips-in-vultr-module
We should consider adding support for IPv6 with Vultr.
Activity
I'm not familiar with the module to understand exactly what part of it he thinks should support ipv6 subnets and IPs, but there are API calls to enable IPv6 subnets. Perhaps that is what he is referring to?
Tyson Phillips (Inactive)
added a comment - I'm not familiar with the module to understand exactly what part of it he thinks should support ipv6 subnets and IPs, but there are API calls to enable IPv6 subnets. Perhaps that is what he is referring to? There is an argument included with server creation requests:
enable_ipv6 string (optional) 'yes' or 'no'. If yes, an IPv6 subnet will be assigned to the machine (where available).
This argument is already supported through the service fields
Hmmm, looks like the method you reference has a different function than the argument I mentioned. It should provide the solution.
It seems like you would need to have a subnet ID already defined in Vultr, or create one via the API, then call that method I linked to to use it. Or maybe the 'enable_ipv6' option you mentioned would choose one and assign it automatically?
Tyson Phillips (Inactive)
added a comment - It seems like you would need to have a subnet ID already defined in Vultr, or create one via the API, then call that method I linked to to use it. Or maybe the 'enable_ipv6' option you mentioned would choose one and assign it automatically? The subnet is assigned automatically, the parameter just enables the possibility I believe
Task was private, made it public.
Paul Phillips
added a comment - Task was private, made it public. 
Maybe I'm misunderstanding this, but I'm pretty sure we do support it.