Eucalyptus, avahi-publish component discovery, and eucalyptus configuration not functional if front-end machine has more than one interface

Bug #425933 reported by Daniel Nurmi on 2009-09-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Medium
Colin Watson
Karmic
Medium
Colin Watson

Bug Description

The UEC installer configures only one interface (one can choose manually which to configure), but eucalyptus needs more configuration if a front-end is using more than one interface. For example, if 'eth0' is connected to a public (user) facing network, and 'eth1' is connected to a node facing network, then VNET_PUBINTERFACE should be set to 'eth0' and VNET_PRIVINTERFACE should be set to 'eth1' in eucalyptus.conf in the eucalyptus-cc package. In addition, if a user chooses 'eth0' when installing, the avahi-publish process that gets started by eucalyptus-cc will not be broadcasting on eth1 when the user tries to install a node. The workaround is to install the front-end, stop eucalyptus services, configure the networking manually, bring up eucalyptus services, install UEC node. This process could be better integrated/partially automated if the user could inform the system as to the roles of each network device at front-end installation time.

Matt Zimmerman (mdz) on 2009-09-07
Changed in eucalyptus (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Soren Hansen (soren)
Matt Zimmerman (mdz) on 2009-09-07
tags: added: eucalyptus
Soren Hansen (soren) on 2009-09-08
Changed in eucalyptus (Ubuntu Karmic):
assignee: Soren Hansen (soren) → Colin Watson (cjwatson)
Colin Watson (cjwatson) on 2009-09-15
Changed in eucalyptus (Ubuntu Karmic):
milestone: none → ubuntu-9.10-beta
Colin Watson (cjwatson) wrote :

I think we can assume that by definition the network interface configured in netcfg is public-facing; it's used to do things like 'apt-get update', after all. If there are multiple network interfaces, we can ask later on which one should be used to communicate with nodes.

We don't tell avahi-publish to broadcast on any particular interface, so we probably just need to make sure that the interface is up.

Can we assume DHCP on the private interface for now, if it is distinct from the public one?

Colin Watson (cjwatson) on 2009-09-21
Changed in eucalyptus (Ubuntu Karmic):
status: Triaged → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package eucalyptus - 1.6~bzr840-0ubuntu1

---------------
eucalyptus (1.6~bzr840-0ubuntu1) karmic; urgency=low

  [ Colin Watson ]
  * Configure VNET_PUBINTERFACE and VNET_PRIVINTERFACE, asking for the
    private interface if multiple interfaces are available (LP: #425933). If
    the private interface is not the same as the public interface configured
    in netcfg, then give it basic DHCP configuration in
    /etc/network/interfaces.

  [ Soren Hansen ]
  * New upstream snapshot.

 -- Soren Hansen <email address hidden> Tue, 22 Sep 2009 12:44:42 +0200

Changed in eucalyptus (Ubuntu Karmic):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers