On 08/24/2012 01:36 AM, Gautam Sampathkumar wrote:
No, we are not running cloud-setup-agent manually. I believe when we set up
things on the management UI, it kicks of cloud-setup-agent
programmatically. We'd like to identify the piece of code that takes over
eth0 and disable it if possible. cloud_utils.py has some code that did this
(there's a part that sets up a bridge and makes the default interface a
member), but removing that code seems to have had no effect.
The piece of code is in agent/bindir/cloud-setup-agent and in
python/lib/cloudutils/serviceConfig.py
However, you can also manually populate a /etc/cloud/agent.properties
like this:
guest.network.device=vlanbr672
workers=5
private.network.device=vlanbr670
port=8250
resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
pod=1
vm.migrate.speed=0
zone=1
guid=<GENERATE UUID>
cluster=1
public.network.device=vlanbr672
local.storage.uuid=<GENERATE UUID>
domr.scripts.dir=scripts/network/domr/kvm
host=192.168.0.1
That should be enough and the Agent will now register with the
management server and show up there.
Wido
--Gautam
On Thu, Aug 23, 2012 at 3:54 PM, Wido den Hollander <w...@widodh.nl> wrote:
On 08/23/2012 09:16 PM, Gautam Sampathkumar wrote:
Hi Wido,
Thanks for your response. Not sure what you mean w.r.t setting
up the KVM agent. We're not doing anything with the KVM agent, except when
we initially installed the qemu-kvm packages. Also, we're working through
the command line and not using the WebUI.
Ah, so you are running cloud-setup-agent manually? With which arguments?
You can manually provide a different public, private and guest bridge/NIC.
If we setup our own bridges and keep them separate from eth0, the
cloud-setup-agent tool will figure out which ones to use correctly?
cloud-setup-agent has some issues and makes a couple of assumptions, so it
could sometimes do weird things.
I'm working on improving cloud-setup-agent, but this will probably hit 4.0.
Wido
thanks,
Gautam
On Thu, Aug 23, 2012 at 12:50 AM, Wido den Hollander <w...@widodh.nl>
wrote:
On 08/23/2012 02:53 AM, Gautam Sampathkumar wrote:
Hi everyone,
I'm trying to get cloudstack running and I see that
cloudstack
configures a bridge interface cloudbr0 and modifies the eth0 interface
to
use the bridge. Is this a requirement or is there a way we can keep eth0
separate from the cloudstack setup.
How are you setting up the KVM agent? I assume you add it through the
WebUI?
Make sure you set your traffic labels correctly and have the bridges
running already before adding the host.
The reason being we're using some custom software for bridge networking
and
everytime we restart or play around with the bridge interface we lose
connectivity to the machine since eth0 is the external interface as
well.
Is there some part of cloudstack configuration that tells it to use
eth0?
Any thoughts or ideas would be appreciated.
No, but it is the cloud-setup-agent tool which is executed when adding
the
Agent to the cluster.
Wido
thanks,
Gautam
