cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrija Panic <andrija.pa...@gmail.com>
Subject Re: Agent deleting/stoping main bridge on Linux ???
Date Wed, 04 Mar 2015 16:46:34 GMT
No Marcus, I was not proficient with CS long time ago, and configured
things in wrong way obviously (did not know that, but I do now), so I will
fix it in other way, and slapp my self in the face a few times.

I will make a serious script as cron job "ifup breth1-500; ifup eth1" that
is more consistent across upgrades of ACS, and we are already wokring on
new ACS installations, where I will be more carefull/knowledgable I guess...


Thanks for you help, as always!

On 4 March 2015 at 17:24, Marcus <shadowsor@gmail.com> wrote:

> Yeah, sorry. You could request an enhancement for an agent tunable
> that keeps the bridge from being removed, but it will not help you
> now.
>
> If you want to get hacky, you can edit the
>    /usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh
> script on your agent, commenting out deleteVlan(). That *might* do
> what you want.
>
> On Wed, Mar 4, 2015 at 8:19 AM, Andrija Panic <andrija.panic@gmail.com>
> wrote:
> > Thanks Markus - yes don't ask me why I did name bridge like this... so
> this
> > is obviously unsuported scenario, that I did... crap...
> >
> > Thx again.
> >
> > On 4 March 2015 at 17:16, Marcus <shadowsor@gmail.com> wrote:
> >
> >> I don't think anyone has ever tested what would happen if the admin
> >> has manually defined the same guest bridges that CloudStack wants to
> >> use. CloudStack creates them on the fly and deletes them when the last
> >> VM has been removed. I assume you're using these bridges on the host
> >> for something out of band that CloudStack isn't aware of?
> >>
> >> On Wed, Mar 4, 2015 at 8:09 AM, Andrija Panic <andrija.panic@gmail.com>
> >> wrote:
> >> > I forgot to add - this is ACS 4.3.0 and CentOS 6.x... breth1-500 is
> the
> >> > main bridge used for Shared Network (yes, I know, somewhat confusing
> name
> >> > for the bridge...)
> >> >
> >> > On 4 March 2015 at 17:07, Andrija Panic <andrija.panic@gmail.com>
> wrote:
> >> >
> >> >> Hi people.
> >> >>
> >> >> on physical host, I was having breth1-500(bridge) with eth1(joined
to
> >> this
> >> >> bridge) - all defined manually in Centos network config files.
> >> >> (when you boot physical host - this bridge is active of course)
> >> >>
> >> >> When I deploy new VM with Shared Network with vlan 500, new device
is
> >> >> created eth1.500 and joined to this bridge - which is fine, and then
> >> vnet0
> >> >> device from VM is also joined to the bridge...
> >> >>
> >> >>
> >> >>
> >> >> When I stop the last VM that is using this Shared Network, CloudStack
> >> >> (agent?) removes eth1.500 from bridge (fine with me), and ***then
> >> removed
> >> >> eth1 from bridge (which I manually configured !!!) and later
> >> stoped/removed
> >> >> the whole bridge***
> >> >>
> >> >> If you try to start new VM again (joined to Shared Network with vlan
> >> 500)
> >> >> - then no bridge is available, VM is started, but no vnet device, no
> >> >> breth1-500 bridge up, and no eth1.500 up.
> >> >> No bridge was available - but also bridge was not created on the
> fly...
> >> >>
> >> >>
> >> >> Is there any explanation - why the heck would my manually configured
> >> >> bridge get deleted?
> >> >>
> >> >> --
> >> >>
> >> >> Andrija Panić
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> >
> >> > Andrija Panić
> >>
> >
> >
> >
> > --
> >
> > Andrija Panić
>



-- 

Andrija Panić

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message