Background

The reason for this change is that internal routers at the EUMETSAT cloud provider were being overloaded by the very high data flow rates from EUMETCAST, which could put network performance for other VMs at risk.  While the provider is improving these components, by changing to a public/floating IP, the burden is moved to a network path that is better able to scale up.  Existing VMs with internal IPs therefore need to be transitioned to public IPs.

Procedure

For existing Eumetcast terrestrial VMs you have to edit the security groups and attach a floating IP as shown below.

Edit security groups

Go to you Eumetcast terrestrial instance → Network → Security Groups → Edit Security groups

Select one of the security groups from the following according to your use case:

•        ssh-internal
•        http-ssh-internal
•        http-https-ssh-internal                    

Attach Floating IP

Go to the instance → Resources → setting icon → select Attach floating IP and select external or floating IP if available → Execute

Please note that the change may take some time to propagate and you will see the public IP assigned to your machine shortly thereafter.