cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcus <shadow...@gmail.com>
Subject Re: Use
Date Wed, 06 May 2015 15:14:23 GMT
Yeah, so cloudstack will take those labels to the KVM hypervisor and try to
resolve them to bridges, and then to the physical devices that host those
bridges, so it knows where to create new bridges. I was just wondering if
your labels were matching your bridge names. By 'default', I was asking if
your labels matched your OVS bridge (usually I only create one).

On Wed, May 6, 2015 at 4:57 AM, Aleksandr <admin@rnet.ru> wrote:

> Marcus <shadowsor@...> writes:
>
> >
> > What is your default OVS bridge name? Are your traffic labels matching
> the
> > OVS bridge cloudbr0?
> >
> > On Tue, May 5, 2015 at 1:24 PM, Aleksandr Ivanov <admin@...> wrote:
> >
> > > Sure
> > > [root <at> node2 /]# cat /etc/cloudstack/agent/agent.properties
> > > #Storage
> > > #Mon May 04 23:29:33 MSK 2015
> > > guest.network.device=cloudbr1
> > > workers=5
> > > private.network.device=mgmt0
> > > network.bridge.type=openvswitch
> > > port=8250
> > > resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
> > > pod=1
> > > libvirt.vif.driver=com.cloud.hypervisor.kvm.resource.OvsVifDriver
> > > zone=1
> > > guid=f31d8de3-4d74-3f99-827c-72e67e5ced03
> > > hypervisor.type=kvm
> > > cluster=1
> > > public.network.device=cloudbr0
> > > local.storage.uuid=68db7328-e15c-4b88-ba26-7a1183598a1e
> > > domr.scripts.dir=scripts/network/domr/kvm
> > > host=94.242.***.***
> > > LibvirtComputingResource.id=1
> > >
> > >
> > > Aaaand : Cannot get interface MTU on 'OVSTunnel1725': No such device
> > > But on mgmt host i see :
> > > 2015-05-04 23:50:22,568 DEBUG [c.c.n.o.OvsTunnelManagerImpl]
> > > (Work-Job-Executor-14:ctx-cc29fc27 job-379/job-383 ctx-faec5ad1)
> Creating
> > > tunnels with OVS tunnel manager
> > > 2015-05-04 23:50:23,604 INFO  [c.c.v.VirtualMachineManagerImpl]
> > > (Work-Job-Executor-14:ctx-cc29fc27 job-379/job-383 ctx-faec5ad1)
> Unable to
> > > start VM on Host[-1-Routing] due to Cannot get interface MTU on
> > > 'OVSTunnel1725': No such device
> > >
> > >
> > >
> > >
> >
>
> What do you mean by "default" ?
> In Cloudstack zone config you make a labels for traffic types ( mgmt +
> storage = mgmt0, public - cloudbr0, guest - cloudbr1 ) and a main bridge
> cloudbr ( all other OVS bridges are fake )
>
> [root@node2 ~]# ovs-vsctl show
> f73b7c50-61f6-433e-9eb1-7f5d20d27b01
>     Bridge cloudbr
>         Port "cloudbr1"
>             tag: 1725
>             Interface "cloudbr1"
>                 type: internal
>         Port "eth0"
>             Interface "eth0"
>         Port cloudbr
>             trunks: [1700, 1725, 1750]
>             Interface cloudbr
>                 type: internal
>         Port "cloudbr0"
>             tag: 1700
>             Interface "cloudbr0"
>                 type: internal
>         Port "mgmt0"
>             tag: 1750
>             Interface "mgmt0"
>                 type: internal
>     Bridge "cloud0"
>         Port "cloud0"
>             Interface "cloud0"
>                 type: internal
>
>     ovs_version: "2.3.1"
> Cloud0 i think is for   Control traffic ( 169.254.* )
>
>
>

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