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. clou
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 par
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
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.
If we setup our own brid
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
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.
The reason being we're usi
