wido commented on issue #12210: URL: https://github.com/apache/cloudstack/issues/12210#issuecomment-3629420135
> This fashion of IP assignment can simplify network management for large public clouds. However, in some datacenters, IP ranges are delivered to servers through VLANs which would not be compatible with this setup. That is correct, but this feature would not be aimed at those use-cases. This feature requires you to have full control over the networking fabric and being able to use dynamic routing protocols (BGP) everywhere. I believe that when you want to use this feature because your use-case requires it that you have already designed such a network or are able to deploy it. This is aimed at large scale. > Also, user data is nowadays crucial for cloud application deployment. I believe, this should be implemented as a separate networking option to keep everything working smoothly as before. > As I wrote, we could and should use ConfigDrive for this. Using CD we can provide the VM with the required networking configuration. > One benefit for this setup would be that there would be no need to allocate a full IP subnet which sometimes costs 2 IPs to be reserved for the subneting. So individual IPs can be used for IP assignment. Yes, exactly! You can allocate all 255 addresses of an IPv4 /24 subnet for example. With IPv6 this is no problem as there are more than enough addresses in a subnet, but with IPv4 it can be a problem. And if you run out, you can just allocate an additional /26 (example) to CloudStack and use all addresses. -- 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]
