in SYSTEM mode, VM ips are not automatically discovered by CC or NC on switched networks
Bug #347622 reported by
Daniel Nurmi
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Eucalyptus |
In Progress
|
Low
|
graziano obertelli | ||
eucalyptus (Ubuntu) |
Fix Released
|
Critical
|
Soren Hansen | ||
Jaunty |
Fix Released
|
Critical
|
Soren Hansen |
Bug Description
When a CC is configured in SYSTEM mode, VMs are attached to a ethernet bridge and depend on an external DHCP server (not controlled by eucalyptus) to get an IP address. On a switched network, the NC and CC cannot automatically discover the IP of a VM unless the VM uses the network and the NC/CC arp tables are populated (allowing the NC or CC to resolve the known MAC address with the allocated IP).
Possible solution - add an iptable rule to the NC that logs DHCP traffic to syslog, periodically inspect syslog to discover IP addresses, send single ICMP packet to discovered IPs to populate NC arp table, parse arp table to discover MAC/IP mapping for VMs
Related branches
Changed in eucalyptus: | |
assignee: | nobody → nurmi |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in eucalyptus (Ubuntu Jaunty): | |
importance: | Undecided → Critical |
status: | New → Confirmed |
To post a comment you must log in.
fix is as described above - NC now adds a (benign) iptables rule that logs incoming DHCP responses. If an instance has '0.0.0.0' address, it will call an external helper script (/usr/share/ eucalyptus/ populate_ arp.pl) to send single ICMP packets to DHCP REPLY IPs until the arp cache is populated with the VM's mac/ip mapping. Then, then NC will pick up the IP and will not run the pinger any longer.
fix is in r249