"wrong" ip address shown for vms running in an EC2 host (hybrid cloud)
|Assignee:||Tino Vázquez||% Done:|
|Category:||Drivers - VM|
|Target version:||Release 4.14|
I manage an Opennebula Cluster using the hybrid cloud model with Amazon EC2 as public cloud backend. If I create a new vm on an "Amazon" host, then the vm gets an ip address assigned from the local virtual network. This ip address is shown in the Sunstone overview as main ip address too. Unfortunately this is not the ip address the vm is really using. The vm is using the ip address assigned from Amazon. I mean the ip address in the VPC in which the vm was started.
You can only see the real IP address from the attribute AWS_PRIVATE_IP_ADDRESS.
So I suggest two changes:
- use the IP address in the attribute AWS_PRIVATE_IP_ADDRESS as main address for the vm if this vm is running on an Amazon host
- don't assign a local ip address to this vm -> this IP address is just blocked and can't be used from other vm's
Opennebula Version: 4.12.1
#4 Updated by Carlos Martín over 5 years ago
- Status changed from Closed to Assigned
- Resolution deleted (
Reopening because of a possible bug.
The IPs column in sunstone shows '--' for a local VM with 1 NIC. This IP is shown correctly in the VM Network tab, and the CLI.
NIC=[ AR_ID="0", BRIDGE="virbr0", IP="192.168.122.2", MAC="02:00:c0:a8:7a:02", MODEL="virtio", NETWORK="private-net", NETWORK_ID="0", NETWORK_UNAME="oneadmin", NIC_ID="0", SECURITY_GROUPS="0", VLAN="NO" ] NIC_DEFAULT=[ MODEL="virtio" ]