Ubuntu
eucalyptus package

[FFe] CC and NC networking mode is set to 'SYSTEM' by default

Bug #425914 reported by Daniel Nurmi
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Fix Released
Medium
Soren Hansen
Ubuntu karmic-alpha-6

Bug Description

This report applies to Eucalyptus in Karmic

The default configuration file (/etc/eucalyptus/eucalyptus.conf) that is installed by the UEC installer/eucalyptus-cc/eucalyptus-nc packages has the networking mode (VNET_MODE) set to SYSTEM. In order to enable security groups, elastic IPs, and meta-data service, the mode should be set to MANAGED-NOVLAN along with the extra parameters that are required for MANAGED-NOVLAN to operate properly. On the CC, these are:

VNET_MODE
VNET_SUBNET
VNET_NETMASK
VNET_DNS
VNET_ADDRSPERNET
VNET_PUBLICIPS

on the node, this is:

VNET_MODE

Tags: eucalyptus
Matt Zimmerman (mdz)
Changed in eucalyptus (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Soren Hansen (soren)
Matt Zimmerman (mdz)
tags: added: eucalyptus
Soren Hansen (soren)
Changed in eucalyptus (Ubuntu):
milestone: none → karmic-alpha-6
Soren Hansen (soren)
summary: - CC and NC networking mode is set to 'SYSTEM' by default
+ [FFe] CC and NC networking mode is set to 'SYSTEM' by default
Soren Hansen (soren)
Changed in eucalyptus (Ubuntu):
status: Triaged → New
Revision history for this message
Steve Langasek (vorlon) wrote :

To evaluate this for a freeze exception, we need to understand what the risks are of this change - what is it about this change thta makes it more than a simple bugfix?

Revision history for this message
Soren Hansen (soren) wrote :

In SYSTEM mode, Eucalypus connects instances to the existing LAN by way of a bridge, and relies on existing networking infrastructure (DHCP servers, DNS, etc.) to run them. This is a very basic mode of operation, and is somewhat limited. In MANAGED(-NOVLAN) you get all the bells and whistles Eucalyptus has to offer: EBS, Elastic IP's, the user-data and meta-data service, etc. So much for the rationale.

In order to get into MANAGED(-NOVLAN) mode, Eucalyptus needs to have a dedicated subnet for its instances. I've added debconf questions to get networking information from the admin and changed a bit of logic along the way to make Eucalyptus use these settings. In this mode, Eucalyptus will run a few extra services, which will only be exposed to Eucalyptus' internal subnet.

Revision history for this message
Steve Langasek (vorlon) wrote :

<slangasek> soren: so what can go wrong here? Eucalyptus packages failing to configure in cases where it configured before (e.g., if the admin provides no input on the new debconf questions)? Things breaking on upgrade?
<soren> slangasek: This only applies for fresh installs.
<soren> slangasek: The primary risk is the default values for the network we provide, really. If they match a subnet the admin already uses, things are going to be odd.
<soren> Not horrible, just odd :)

FFe granted.

Changed in eucalyptus (Ubuntu):
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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

  * New upstream, bugfix snapshot.
  * Add more full-featured default network configuration (LP: #425914).

 -- Soren Hansen <email address hidden> Tue, 15 Sep 2009 13:50:40 +0200

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

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.