default eucalyptus.conf in 'eucalyptus-common' does not lead to working system 'out of the box'

[Daniel Nurmi]

attaching a eucalyptus.conf that will work for both NC and CC in most cases (primary interface is 'eth0', network is 'vlan clean', hypervisor is 'kvm', scheduling policy is 'round robin'). Note that START_CC, START_NC, START_CLOUD are all set to "N", the eucalyptus-cloud/cc/nc packages will have to set them upon installation. Also note that the network params are currently set, and will have to be set on CC package post install.

[Soren Hansen (soren)]

I'm not sure I'm reading this configuration file correctly. It looks to me like you are grabbing 192.168.0.0/16 ? Is that accurate? If so, that needs to change. While libvirt manages to get away with grabbing 192.168.122.0/24, I'm confident that the vast majority of people who use the 192.168.x.y style subnets are using 192.168.0.y and/or 192.168.1.y, which I'm presuming are the very first ranges Eucalyptus will use if told to go nuts on 192.168.0.0/16, so this will most definitely cause conflicts in many, many situations.

[Daniel Nurmi (nurmi)]

in the original bug report, this sentence:

Also note that the network params are currently set, and will have to be set on CC package post install.

is meant to express that there should not be a pre-defined subnet in the default configuration file, but that those parameters should be filled in by the administrator through a series of post-install questions when installing the 'eucalyptus-cc' package. Specifically, the thinking was that:

VNET_SUBNET
VNET_NETMASK
VNET_DNS
VNET_PUBLICIPS

parameters should be filled in with the response to post-install questions.

[Soren Hansen (soren)]

These all need to have default answers, though. We need to answer the question: What if the user doesn't want to answer these questions? Eucalyptus still works, it's just limited in functionality, so refusing to install if the user doesn't want to answer these questions would be wrong, IMO.

[Dustin Kirkland  (kirkland)]

I'm marking fix-released, as we should be there in Karmic. If not, please open new bugs for particular issues where default conf doesn't work out of the box.

:-Dustin