weizhouapache commented on pull request #5786: URL: https://github.com/apache/cloudstack/pull/5786#issuecomment-1067057928
> @weizhouapache is it good idea to: > > * allow updating internet protocol for an exisiting VPC offering (probably simplest) > * allow updating offering for an existing VPC > * or a different approach altogether @shwstppr it will introduce a new feature: update vpc to another offering,might it be complicated ? it looks easier to (1) succeed to create a vpc tier, if there is an ipv6 address range available in same vlan as ipv4 (2) fail to create a vpc tier, if there is not an ipv6 address range available in same vlan as ipv4 as far as I remember, in the prototype, it worked if create a vpc tier with ipv6 in VPC without public ipv6 address ( an ipv6 address will be allocated and associated to eth0 in VPC VR when create the vpc tier). public ipv6 address do not need to be pre-allocated in VPC. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
