search

indigo-dc / im

Infrastructure Manager (TOSCA support)
http://www.grycap.upv.es/im
GNU General Public License v3.0
9 stars 0 forks source link

Public and private IPs #221

Closed alahiff closed 6 years ago

alahiff commented 6 years ago

In the documentation (http://www.grycap.upv.es/im/documentation.php) is this description of the keyword "outbound":

Indicate whether the IP that will have the virtual machines in this network will be public (accessible from any external network) or private. If yes, IPs will be public, and if no, they will be private. The default value is no.

My understanding of this is that with outbound = 'no' (the default) a machine will only have a private IP address (not accessible on the internet) and with outbound = 'yes' a machine will have a public IP address. Is this correct?

However, when deploying VMs on EGI FedCloud sites using IM all IPs seem to be public and accessible on the internet. The SLURM example (https://github.com/indigo-dc/im/blob/master/examples/slurm.radl), gives the impression that the worker nodes will have only private IPs and the front-end node with have both private and public IPs. But this is not the case - the front-end and worker nodes only have public IPs. And, for example, port 22 on the front-end and the worker nodes is accessible on the internet.

micafer commented 6 years ago

Hi @alahiff ,

My understanding of this is that with outbound = 'no' (the default) a machine will only have a private IP address (not accessible on the internet) and with outbound = 'yes' a machine will have a public IP address. Is this correct?

Yes. The IM will try to create the VMs in this way. But there are some EGI sites (almost all OpenNebula ones) that gives a public IP to all VMs in all the cases. You have no posibility to get a VM with a private IP.

alahiff commented 6 years ago

Hi @micafer,

Thanks for the quick reply! I'll close this issue now.

alahiff commented 6 years ago

FYI I noticed that on Google Cloud Platform all VMs get public IPs as well. Is this also a known issue?

micafer commented 6 years ago

Hi @alahiff, I have checked the code and you are right. It seems that by default a public IP is assigned. I will try to fix it.