You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2019/07/12 11:58:44 UTC

[GitHub] [cloudstack] rhtyd edited a comment on issue #3488: cloud0 subnet should not be hardcoded to 169.254.0.1/16

rhtyd edited a comment on issue #3488: cloud0 subnet should not be hardcoded to 169.254.0.1/16
URL: https://github.com/apache/cloudstack/issues/3488#issuecomment-510859501
 
 
   Aah okay it makes sense now @wido - what workaround do you propose? For example, one good solution could be to get rid of use of link-local based addresses/nics. VR/systemvm programming can be done via an IP on the mgmt/private network cidr.
   
   Our Vmware implementation does not use link-local as well, and all communications are done directly to the private IP in the private address range (typically in RFC1918). This change is do-able but may cause issues for users who don't have enough free address/ips in the pod/range for/in private/mgmt network. What do you think?

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services