[Bug 347622] Re: in SYSTEM mode, VM ips are not automatically discovered by CC or NC on switched networks
This issue is now being tracked upstream at http://eucalyptus.atlassian.net/browse/EUCA-2638 Please watch that issue for further updates. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in Ubuntu. https://bugs.launchpad.net/bugs/347622 Title: in SYSTEM mode, VM ips are not automatically discovered by CC or NC on switched networks To manage notifications about this bug go to: https://bugs.launchpad.net/eucalyptus/+bug/347622/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 347622] Re: in SYSTEM mode, VM ips are not automatically discovered by CC or NC on switched networks
Targeting this bug for milestone 2.0.4: we probably need to document this, since we cannot bind to subnet we are not aware exists. ** Changed in: eucalyptus Milestone: None = 2.0.4 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in Ubuntu. https://bugs.launchpad.net/bugs/347622 Title: in SYSTEM mode, VM ips are not automatically discovered by CC or NC on switched networks To manage notifications about this bug go to: https://bugs.launchpad.net/eucalyptus/+bug/347622/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 347622] Re: in SYSTEM mode, VM ips are not automatically discovered by CC or NC on switched networks
Also dropping importance since the original issue was resolved: we just need to document the multi-subnet behavior. ** Changed in: eucalyptus Status: Fix Committed = In Progress ** Changed in: eucalyptus Importance: High = Low ** Changed in: eucalyptus Assignee: Daniel Nurmi (nurmi) = graziano obertelli (graziano.obertelli) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in Ubuntu. https://bugs.launchpad.net/bugs/347622 Title: in SYSTEM mode, VM ips are not automatically discovered by CC or NC on switched networks To manage notifications about this bug go to: https://bugs.launchpad.net/eucalyptus/+bug/347622/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 347622] Re: in SYSTEM mode, VM ips are not automatically discovered by CC or NC on switched networks
We've experienced a similar problem with neither the CC nor the NCs consistently discovering the public/private IP addresses of instances. Here is how to reproduce our particular scenario: It is in SYSTEM mode and a DHCP service is running on the CC. The DHCP can assign IP addresses from many possible subnets. If a NC (that happens to have its br0 bound somewhere in, say, subnet1) starts an instance that is told by DHCP to use an IP address in subnet2, this NC's ARP table will never populate with that particular instance IP and it will go undiscovered. If the instance happens to receive an IP address on its NC's subnet, the ARP entry is set and the instance IP is discovered. (Somewhat of a) Solution: One could have all NCs bound to all subnets, but that would be a waste of IP addresses and possibly introduce routing problems. The simplest solution is to have the CC bind to all subnets, for example: ifconfig eth0:1 subnet2_ip netmask ... And just create /etc/network/interface entries so that it will persist on restarts. Since the DHCP service is on the CC, its ARP table will populate across all subnets, and the CC will always discover and report IP addresses in euca-describe-instances. However, the NCs will still show 0.0.0.0 in its nc.log, but that is acceptable for now. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in Ubuntu. https://bugs.launchpad.net/bugs/347622 Title: in SYSTEM mode, VM ips are not automatically discovered by CC or NC on switched networks To manage notifications about this bug go to: https://bugs.launchpad.net/eucalyptus/+bug/347622/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 347622] Re: in SYSTEM mode, VM ips are not automatically discovered by CC or NC on switched networks
It seems that this still isn't resolved. We're running Ubuntu 10.04 Enterprise Cloud and our scenario fits this one perfectly. -- uecad...@cloudnc:~$ uname -a Linux cloudnc 2.6.32-21-generic-pae #32-Ubuntu SMP Fri Apr 16 09:39:35 UTC 2010 i686 GNU/Linux -- uecad...@cloudnc:~$ dpkg -l | grep iptables ii iptables1.4.4-2ubuntu2 administration tools for packet filtering an uecad...@cloudnc:~$ dpkg -l | grep eucalyptus ii eucalyptus-common 1.6.2-0ubuntu30.2 Elastic Utility Computing Architecture - Com ii eucalyptus-gl 1.6.2-0ubuntu30.2 Elastic Utility Computing Architecture - Log ii eucalyptus-nc 1.6.2-0ubuntu30.2 Elastic Utility Computing Architecture - Nod -- uecad...@cloudnc:~$ sudo iptables -L [sudo] password for uecadmin: Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT udp -- anywhere anywhereudp dpt:domain ACCEPT tcp -- anywhere anywheretcp dpt:domain ACCEPT udp -- anywhere anywhereudp dpt:bootps ACCEPT tcp -- anywhere anywheretcp dpt:bootps Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere 192.168.122.0/24state RELATED,ESTABLISHED ACCEPT all -- 192.168.122.0/24 anywhere ACCEPT all -- anywhere anywhere REJECT all -- anywhere anywherereject-with icmp-port-unreachable REJECT all -- anywhere anywherereject-with icmp-port-unreachable LOGudp -- anywhere anywhereudp spts:bootps:bootpc dpts:bootps:bootpc LOG level info Chain OUTPUT (policy ACCEPT) target prot opt source destination -- We checked the /usr/share/eucalyptus/populate_arp.pl file and indeed see the 'use Net::Ping;' in it. Any thoughts? -- in SYSTEM mode, VM ips are not automatically discovered by CC or NC on switched networks https://bugs.launchpad.net/bugs/347622 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 347622] Re: in SYSTEM mode, VM ips are not automatically discovered by CC or NC on switched networks
Still not working under jaunty :( r...@x-dom0-01:/etc/eucalyptus# dpkg -l|grep iptables ii iptables 1.4.1.1-4ubuntu3 administration tools for packet filtering an r...@x-dom0-01:/etc/eucalyptus# dpkg -l|grep eucalyptus ii eucalyptus-common 1.5.2-0euca424ga68 Elastic Utility Computing Architecture - Com ii eucalyptus-gl 1.5.2-0euca424ga68 Elastic Utility Computing Architecture - Log ii eucalyptus-nc 1.5.2-0euca424ga68 Elastic Utility Computing Architecture - Nod -- in SYSTEM mode, VM ips are not automatically discovered by CC or NC on switched networks https://bugs.launchpad.net/bugs/347622 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
