This bug was fixed in the package eucalyptus - 1.6~bzr808-0ubuntu1
---
eucalyptus (1.6~bzr808-0ubuntu1) karmic; urgency=low
[ Dustin Kirkland ]
* debian/eucalyptus-udeb.finish-install: eth0 should be set to
'manual', when configured with br0 on dhcp, LP: #430820
* tools/euca
Eucalyptus upstream said this is needed for VLAN tagging, which they use
to provide network isolation for VMs between clusters.
** Changed in: eucalyptus (Ubuntu)
Status: Triaged => Fix Committed
--
Eucalyptus CC package depends on 'vtund' process in multi-cluster mode
https://bugs.launch
** Branch linked: lp:~ubuntu-core-dev/eucalyptus/ubuntu
--
Eucalyptus CC package depends on 'vtund' process in multi-cluster mode
https://bugs.launchpad.net/bugs/425928
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
My testing on EC2 suggests that direct ethernet communication across
availability zone boundaries is not possible. For the record, I added an
extra IP address (192.168.10.1 and .2) to eth0 on each host, and added
an arp entry for the other host on each of them, and tried to ping. No
luck.
--
Euca
Just to get this on record:
Why is layer two tunneling needed? Does EC2 allow direct ethernet
communication between instances? Is that why we're doing it? Or is this
related to AoE?
--
Eucalyptus CC package depends on 'vtund' process in multi-cluster mode
https://bugs.launchpad.net/bugs/425928
Y
vtun has broken encryption support that makes it unsuitable for main
(and for a secure multi-cluster support), see MIR review in bug 412059.
The workaround proposal for karmic is to ship a working but unsupported
multi-cluster mode, by suggesting vtun usage in eucalyptus and leaving
it in universe
** Changed in: eucalyptus (Ubuntu)
Status: New => Triaged
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided => Medium
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) => Thierry Carrez (ttx)
** Tags added: eucalyptus
--
Eucalyptus CC package depends on 'vtund' pr