You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Engelmann Florian <fl...@everyware.ch> on 2017/02/17 12:26:27 UTC

Ubuntu 16.04, Openvswitch, cloudstack-agent and secondary storage IP

Hi,

we are currently building a new test setup: ACS + Ubuntu 16.04 KVM + OVS

I am stuck with the getting the wrong secondary IP from the KVM host:


[...]
"publicIpAddress":"10.1.0.233","publicNetmask":"255.255.255.240","publicMacAddress":"24:8a:07:6c:75:30","privateIpAddress":"10.1.0.233","privateMacAddress":"24:8a:07:6c:75:30","privateNetmask":"255.255.255.240","storageIpAddress":"10.1.0.233","storageNetmask":"255.255.255.240","storageMacAddress":"24:8a:07:6c:75:30","resourceName":"LibvirtComputingResource","gatewayIpAddress":"10.1.0.225","wait":0}},
[...]

The secondary storage IP should be 10.1.2.233

I did add the secondary storage label like:

KVM traffic label	"secstore0"

and the OVS configuration looks like:

# ovs-vsctl show
c736c85f-badb-4fec-9fd9-fdc94ceed776
    Bridge "cloudbr0"
        Port "bond0"
            Interface "enp136s0"
            Interface "enp136s0d1"
        Port "cloudbr0"
            Interface "cloudbr0"
                type: internal
        Port secstore0
            tag: 2007
            Interface secstore0
                type: internal
    Bridge "cloud0"
        Port "cloud0"
            Interface "cloud0"
                type: internal
    ovs_version: "2.5.0"

And the IP configuration looks like:

8: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1
    link/ether 76:50:ad:b6:37:90 brd ff:ff:ff:ff:ff:ff
18: cloud0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1
    link/ether ae:bf:4c:94:c6:42 brd ff:ff:ff:ff:ff:ff
    inet 169.254.0.1/16 scope global cloud0
       valid_lft forever preferred_lft forever
    inet6 fe80::acbf:4cff:fe94:c642/64 scope link 
       valid_lft forever preferred_lft forever
19: cloudbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1
    link/ether 24:8a:07:6c:75:30 brd ff:ff:ff:ff:ff:ff
    inet 10.1.0.233/28 brd 10.1.0.239 scope global cloudbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::268a:7ff:fe6c:7530/64 scope link 
       valid_lft forever preferred_lft forever
20: bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1
    link/ether ce:13:53:5a:d8:e1 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::cc13:53ff:fe5a:d8e1/64 scope link 
       valid_lft forever preferred_lft forever
21: secstore0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1
    link/ether 8a:eb:53:70:69:40 brd ff:ff:ff:ff:ff:ff
    inet 10.1.2.233/28 brd 10.1.2.239 scope global secstore0
       valid_lft forever preferred_lft forever
    inet6 fe80::88eb:53ff:fe70:6940/64 scope link 
       valid_lft forever preferred_lft forever


Any idea why ACS is not able to fetch the correct IP used to access secondary storage?

All the best,
Flo




EveryWare AG
Florian Engelmann
Systems Engineer
Zurlindenstrasse 52a
CH-8003 Zürich

T  +41 44 466 60 00
F  +41 44 466 60 10

florian.engelmann@everyware.ch
www.everyware.ch

Re: Ubuntu 16.04, Openvswitch, cloudstack-agent and secondary storage IP

Posted by Engelmann Florian <fl...@everyware.ch>.
Hi there,

it looks like the IP mismatch is irrelevant in this case:

10.1.2.238:/exports/zh-ep-z00/template/tmpl/2/296 53685002240 362133504 53322868736   1% /mnt/4276a235-9ab3-3f5f-b6e3-a19142e7f524
root@ewcstack-vh023-test:~# ip r g 10.1.2.238
10.1.2.238 dev secstore0  src 10.1.2.233 
    cache 

Secondary storage is woking fine anyway.

All the best,
Flo


________________________________________
From: Engelmann Florian <fl...@everyware.ch>
Sent: Friday, February 17, 2017 1:26 PM
To: users@cloudstack.apache.org
Subject: Ubuntu 16.04, Openvswitch, cloudstack-agent and secondary storage IP

Hi,

we are currently building a new test setup: ACS + Ubuntu 16.04 KVM + OVS

I am stuck with the getting the wrong secondary IP from the KVM host:


[...]
"publicIpAddress":"10.1.0.233","publicNetmask":"255.255.255.240","publicMacAddress":"24:8a:07:6c:75:30","privateIpAddress":"10.1.0.233","privateMacAddress":"24:8a:07:6c:75:30","privateNetmask":"255.255.255.240","storageIpAddress":"10.1.0.233","storageNetmask":"255.255.255.240","storageMacAddress":"24:8a:07:6c:75:30","resourceName":"LibvirtComputingResource","gatewayIpAddress":"10.1.0.225","wait":0}},
[...]

The secondary storage IP should be 10.1.2.233

I did add the secondary storage label like:

KVM traffic label       "secstore0"

and the OVS configuration looks like:

# ovs-vsctl show
c736c85f-badb-4fec-9fd9-fdc94ceed776
    Bridge "cloudbr0"
        Port "bond0"
            Interface "enp136s0"
            Interface "enp136s0d1"
        Port "cloudbr0"
            Interface "cloudbr0"
                type: internal
        Port secstore0
            tag: 2007
            Interface secstore0
                type: internal
    Bridge "cloud0"
        Port "cloud0"
            Interface "cloud0"
                type: internal
    ovs_version: "2.5.0"

And the IP configuration looks like:

8: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1
    link/ether 76:50:ad:b6:37:90 brd ff:ff:ff:ff:ff:ff
18: cloud0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1
    link/ether ae:bf:4c:94:c6:42 brd ff:ff:ff:ff:ff:ff
    inet 169.254.0.1/16 scope global cloud0
       valid_lft forever preferred_lft forever
    inet6 fe80::acbf:4cff:fe94:c642/64 scope link
       valid_lft forever preferred_lft forever
19: cloudbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1
    link/ether 24:8a:07:6c:75:30 brd ff:ff:ff:ff:ff:ff
    inet 10.1.0.233/28 brd 10.1.0.239 scope global cloudbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::268a:7ff:fe6c:7530/64 scope link
       valid_lft forever preferred_lft forever
20: bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1
    link/ether ce:13:53:5a:d8:e1 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::cc13:53ff:fe5a:d8e1/64 scope link
       valid_lft forever preferred_lft forever
21: secstore0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1
    link/ether 8a:eb:53:70:69:40 brd ff:ff:ff:ff:ff:ff
    inet 10.1.2.233/28 brd 10.1.2.239 scope global secstore0
       valid_lft forever preferred_lft forever
    inet6 fe80::88eb:53ff:fe70:6940/64 scope link
       valid_lft forever preferred_lft forever


Any idea why ACS is not able to fetch the correct IP used to access secondary storage?

All the best,
Flo




EveryWare AG
Florian Engelmann
Systems Engineer
Zurlindenstrasse 52a
CH-8003 Zürich

T  +41 44 466 60 00
F  +41 44 466 60 10

florian.engelmann@everyware.ch
www.everyware.ch

Re: Ubuntu 16.04, Openvswitch networking issue

Posted by Abhinandan Prateek <ab...@shapeblue.com>.
Ignore these errors, cloudstack goes thru all the plugins and they emit this message saying that they cannot design this network, till a good one is found.



On 17/02/17, 8:32 PM, "Engelmann Florian" <fl...@everyware.ch> wrote:

>Hi,
>
>sorry I ment "I am NOT able to solve"....
>
>________________________________________
>From: Engelmann Florian <fl...@everyware.ch>
>Sent: Friday, February 17, 2017 3:36 PM
>To: users@cloudstack.apache.org
>Subject: Ubuntu 16.04, Openvswitch networking issue
>
>Hi,
>
>another error I am able to solve:
>
>2017-02-17 15:24:36,097 DEBUG [c.c.a.ApiServlet] (catalina-exec-26:ctx-30020483) (logid:d303f8ef) ===START===  192.168.252.76 -- GET  command=createNetwork&response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&name=net-kvm008&displayText=net-kvm008&networkOf
>2017-02-17 15:24:36,135 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network, the physical isolation type is not BCF_SEGMENT
>2017-02-17 15:24:36,136 DEBUG [o.a.c.n.c.m.ContrailGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network
>2017-02-17 15:24:36,137 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-144:ctx-b2cdad73) (logid:eb129204) Seq 179-6955246674520311671: Response Received:
>2017-02-17 15:24:36,137 DEBUG [c.c.a.t.Request] (StatsCollector-5:ctx-4298a591) (logid:eb129204) Seq 179-6955246674520311671: Received:  { Ans: , MgmtId: 345049101620, via: 179(ewcstack-vh003-test), Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
>2017-02-17 15:24:36,137 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) design called
>2017-02-17 15:24:36,138 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru] (StatsCollector-5:ctx-4298a591) (logid:eb129204) getCommandHostDelegation: class com.cloud.agent.api.GetStorageStatsCommand
>2017-02-17 15:24:36,138 DEBUG [c.c.h.XenServerGuru] (StatsCollector-5:ctx-4298a591) (logid:eb129204) getCommandHostDelegation: class com.cloud.agent.api.GetStorageStatsCommand
>2017-02-17 15:24:36,139 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network, the physical isolation type is not MIDO
>2017-02-17 15:24:36,139 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-72:ctx-656a03ae) (logid:dd7ada9e) Seq 217-8596245788743434945: Executing request
>2017-02-17 15:24:36,141 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network
>2017-02-17 15:24:36,142 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network
>2017-02-17 15:24:36,144 DEBUG [c.c.n.g.OvsGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network
>2017-02-17 15:24:36,163 DEBUG [o.a.c.n.g.SspGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) SSP not configured to be active
>2017-02-17 15:24:36,164 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network
>2017-02-17 15:24:36,165 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design network using network offering 54 on physical network 200
>2017-02-17 15:24:36,166 DEBUG [o.a.c.e.o.NetworkOrchestrator] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Releasing lock for Acct[3426fb73-70ad-47d9-9c5d-355f34891438-fen]
>2017-02-17 15:24:36,188 DEBUG [c.c.a.ApiServlet] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) ===END===  192.168.252.76 -- GET  command=createNetwork&response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&name=net-kvm008&displayText=net-kvm00
>
>
>We do not use BigSwitch or anything like this, just plain Openvswitch with Ubuntu 16.04. Any idea whats going on?
>
>All the best,
>Florian
>
>EveryWare AG
>Florian Engelmann
>Systems Engineer
>Zurlindenstrasse 52a
>CH-8003 Zürich
>
>T  +41 44 466 60 00
>F  +41 44 466 60 10
>
>florian.engelmann@everyware.ch
>www.everyware.ch

abhinandan.prateek@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


Re: Ubuntu 16.04, Openvswitch networking issue

Posted by Tim Mackey <tm...@gmail.com>.
Importantly, if you're in a multi-hypervisor setup, you need to account for
what'll happen when all clusters of a hypervisor type go down. In your
case, if the KVM cluster goes down and you've pinned the systems VMs to the
KVM cluster, then CloudStack won't be able to restart them on either
XenServer cluster. The net result of this will be an outage which may be
difficult to recover from.

Trust me, that was one of the first outages I needed to attend to when I
started with CloudStack a few years ago. At the time I was running clusters
of vSphere, XenServer and KVM managed by the same management server, and
there was a bug where the system VMs could get stuck on a hypervisor. That
bug is long since fixed, but highlighted that in multi-hypervisor you need
to plan for the outages of a given hypervisor type in addition to planning
for the "normal" outages.

-ti

On Mon, Feb 20, 2017 at 11:48 AM, Rafael Weingärtner <
rafaelweingartner@gmail.com> wrote:

> [UPDATE]
>
> According to this method
> "com.cloud.resource.ResourceManagerImpl.getAvailableHypervisor(long)", if
> you do not configure the “system.vm.default.hypervisor” parameter, the
> hypervisor selected for system VMs is random (among the ones available).
>
> On Mon, Feb 20, 2017 at 11:37 AM, Rafael Weingärtner <
> rafaelweingartner@gmail.com> wrote:
>
> > Hi Engelmann,
> > I still quite not understand your problem yet. I see that you have three
> > different clusters; one KVM, One XenServer 6.5 and one 7.0. You want to
> use
> > the KVM as the hypervisor to host your system VMs, right?
> >
> > Have you configured the parameter “system.vm.default.hypervisor”?
> >
> > On Mon, Feb 20, 2017 at 11:25 AM, Engelmann Florian <
> > florian.engelmann@everyware.ch> wrote:
> >
> >> Hi Rafael,
> >>
> >> We do use the following setup (Test environment currently):
> >>
> >> ACS 4.9.2
> >> 1x Xenserver 6.5 Cluster (3 nodes)
> >> 1x Xenserver 7.0 Cluster (1 node)
> >> 1x Ubuntu 16.04 KVM Cluster (3 nodes)
> >>
> >> Networking = Advanced Zone VPC and Virtual Router
> >>
> >> I noticed the error Message was just informational an not the real
> >> problem. The problem we got is:
> >>
> >> [...]
> >> Allocating the VR with id=4185 in datacenter
> >> com.cloud.dc.DataCenterVO$$EnhancerByCGLIB$$caa6c375@2 with the
> >> hypervisor type XenServer
> >> [...]
> >> Cluster: 6 has HyperVisorType that does not match the VM, skipping this
> >> cluster
> >> [...]
> >>
> >> We tried to force ACS to use the KVM systemVM template but for some
> >> reason ACS refuses to use that System offering.
> >>
> >> Hosts:
> >> Name        ewcstack-vh023-test
> >> Host Tags="kvm"
> >>
> >> Primary storage:
> >> Name: ewcstack-vh023-test,Local Storage: Storage Tags="vol-local-kvm"
> >>
> >> System offering:
> >> Name  custom-local-sm-kvm
> >> Storage Tags="vol-local-kvm"
> >> Host Tags="kvm"
> >>
> >> Network offering:
> >> Name        custom local kvm
> >> System offering="custom-local-sm-kvm"
> >>
> >> Disk offering:
> >> Name        custom local kvm
> >> Storage Tags="vol-local-kvm"
> >>
> >>
> >> Creating a Instance with a network offering "custom-local-sm-kvm"
> doesn't
> >> stop ACS from using a XenServer systemVM template. Why?
> >>
> >> All the best,
> >> Florian
> >>
> >>
> >> ________________________________________
> >> From: Rafael Weingärtner <ra...@gmail.com>
> >> Sent: Friday, February 17, 2017 4:08 PM
> >> To: users@cloudstack.apache.org
> >> Subject: Re: Ubuntu 16.04, Openvswitch networking issue
> >>
> >> I think we may need more information. ACS version, network deployment
> >> type,
> >> and hypervisors?
> >>
> >> On Fri, Feb 17, 2017 at 10:02 AM, Engelmann Florian <
> >> florian.engelmann@everyware.ch> wrote:
> >>
> >> > Hi,
> >> >
> >> > sorry I ment "I am NOT able to solve"....
> >> >
> >> > ________________________________________
> >> > From: Engelmann Florian <fl...@everyware.ch>
> >> > Sent: Friday, February 17, 2017 3:36 PM
> >> > To: users@cloudstack.apache.org
> >> > Subject: Ubuntu 16.04, Openvswitch networking issue
> >> >
> >> > Hi,
> >> >
> >> > another error I am able to solve:
> >> >
> >> > 2017-02-17 15:24:36,097 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-26:ctx-
> >> > 30020483) (logid:d303f8ef) ===START===  192.168.252.76 -- GET
> >> > command=createNetwork&response=json&zoneId=e683eeaa-
> >> > 92c9-4651-91b9-165939f9000c&name=net-kvm008&displayText=
> >> > net-kvm008&networkOf
> >> > 2017-02-17 15:24:36,135 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru]
> >> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
> >> (logid:d303f8ef) Refusing to
> >> > design this network, the physical isolation type is not BCF_SEGMENT
> >> > 2017-02-17 15:24:36,136 DEBUG [o.a.c.n.c.m.ContrailGuru]
> >> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
> >> (logid:d303f8ef) Refusing to
> >> > design this network
> >> > 2017-02-17 15:24:36,137 DEBUG [c.c.a.m.DirectAgentAttache]
> >> > (DirectAgent-144:ctx-b2cdad73) (logid:eb129204) Seq
> >> > 179-6955246674520311671: Response Received:
> >> > 2017-02-17 15:24:36,137 DEBUG [c.c.a.t.Request]
> >> (StatsCollector-5:ctx-4298a591)
> >> > (logid:eb129204) Seq 179-6955246674520311671: Received:  { Ans: ,
> >> MgmtId:
> >> > 345049101620, via: 179(ewcstack-vh003-test), Ver: v1, Flags: 10, {
> >> > GetStorageStatsAnswer } }
> >> > 2017-02-17 15:24:36,137 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> >> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
> >> (logid:d303f8ef) design called
> >> > 2017-02-17 15:24:36,138 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru]
> >> > (StatsCollector-5:ctx-4298a591) (logid:eb129204)
> >> > getCommandHostDelegation: class com.cloud.agent.api.GetStorage
> >> StatsCommand
> >> > 2017-02-17 15:24:36,138 DEBUG [c.c.h.XenServerGuru]
> >> (StatsCollector-5:ctx-4298a591)
> >> > (logid:eb129204) getCommandHostDelegation: class com.cloud.agent.api.
> >> > GetStorageStatsCommand
> >> > 2017-02-17 15:24:36,139 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> >> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
> >> (logid:d303f8ef) Refusing to
> >> > design this network, the physical isolation type is not MIDO
> >> > 2017-02-17 15:24:36,139 DEBUG [c.c.a.m.DirectAgentAttache]
> >> > (DirectAgent-72:ctx-656a03ae) (logid:dd7ada9e) Seq
> >> 217-8596245788743434945:
> >> > Executing request
> >> > 2017-02-17 15:24:36,141 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru]
> >> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
> >> (logid:d303f8ef) Refusing to
> >> > design this network
> >> > 2017-02-17 15:24:36,142 DEBUG [o.a.c.n.o.
> OpendaylightGuestNetworkGuru]
> >> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
> >> (logid:d303f8ef) Refusing to
> >> > design this network
> >> > 2017-02-17 15:24:36,144 DEBUG [c.c.n.g.OvsGuestNetworkGuru]
> >> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
> >> (logid:d303f8ef) Refusing to
> >> > design this network
> >> > 2017-02-17 15:24:36,163 DEBUG [o.a.c.n.g.SspGuestNetworkGuru]
> >> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
> >> (logid:d303f8ef) SSP not
> >> > configured to be active
> >> > 2017-02-17 15:24:36,164 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru]
> >> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
> >> (logid:d303f8ef) Refusing to
> >> > design this network
> >> > 2017-02-17 15:24:36,165 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru]
> >> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
> >> (logid:d303f8ef) Refusing to
> >> > design network using network offering 54 on physical network 200
> >> > 2017-02-17 15:24:36,166 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> >> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
> >> (logid:d303f8ef) Releasing
> >> > lock for Acct[3426fb73-70ad-47d9-9c5d-355f34891438-fen]
> >> > 2017-02-17 15:24:36,188 DEBUG [c.c.a.ApiServlet]
> >> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
> >> (logid:d303f8ef) ===END===
> >> > 192.168.252.76 -- GET  command=createNetwork&
> >> > response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&
> >> > name=net-kvm008&displayText=net-kvm00
> >> >
> >> >
> >> > We do not use BigSwitch or anything like this, just plain Openvswitch
> >> with
> >> > Ubuntu 16.04. Any idea whats going on?
> >> >
> >> > All the best,
> >> > Florian
> >> >
> >> > EveryWare AG
> >> > Florian Engelmann
> >> > Systems Engineer
> >> > Zurlindenstrasse 52a
> >> > CH-8003 Zürich
> >> >
> >> > T  +41 44 466 60 00 <+41%2044%20466%2060%2000>
> >> > F  +41 44 466 60 10 <+41%2044%20466%2060%2010>
> >> >
> >> > florian.engelmann@everyware.ch
> >> > www.everyware.ch
> >> >
> >>
> >>
> >>
> >> --
> >> Rafael Weingärtner
> >>
> >
> >
> >
> > --
> > Rafael Weingärtner
> >
>
>
>
> --
> Rafael Weingärtner
>

Re: Ubuntu 16.04, Openvswitch networking issue

Posted by Rafael Weingärtner <ra...@gmail.com>.
[UPDATE]

According to this method
"com.cloud.resource.ResourceManagerImpl.getAvailableHypervisor(long)", if
you do not configure the “system.vm.default.hypervisor” parameter, the
hypervisor selected for system VMs is random (among the ones available).

On Mon, Feb 20, 2017 at 11:37 AM, Rafael Weingärtner <
rafaelweingartner@gmail.com> wrote:

> Hi Engelmann,
> I still quite not understand your problem yet. I see that you have three
> different clusters; one KVM, One XenServer 6.5 and one 7.0. You want to use
> the KVM as the hypervisor to host your system VMs, right?
>
> Have you configured the parameter “system.vm.default.hypervisor”?
>
> On Mon, Feb 20, 2017 at 11:25 AM, Engelmann Florian <
> florian.engelmann@everyware.ch> wrote:
>
>> Hi Rafael,
>>
>> We do use the following setup (Test environment currently):
>>
>> ACS 4.9.2
>> 1x Xenserver 6.5 Cluster (3 nodes)
>> 1x Xenserver 7.0 Cluster (1 node)
>> 1x Ubuntu 16.04 KVM Cluster (3 nodes)
>>
>> Networking = Advanced Zone VPC and Virtual Router
>>
>> I noticed the error Message was just informational an not the real
>> problem. The problem we got is:
>>
>> [...]
>> Allocating the VR with id=4185 in datacenter
>> com.cloud.dc.DataCenterVO$$EnhancerByCGLIB$$caa6c375@2 with the
>> hypervisor type XenServer
>> [...]
>> Cluster: 6 has HyperVisorType that does not match the VM, skipping this
>> cluster
>> [...]
>>
>> We tried to force ACS to use the KVM systemVM template but for some
>> reason ACS refuses to use that System offering.
>>
>> Hosts:
>> Name        ewcstack-vh023-test
>> Host Tags="kvm"
>>
>> Primary storage:
>> Name: ewcstack-vh023-test,Local Storage: Storage Tags="vol-local-kvm"
>>
>> System offering:
>> Name  custom-local-sm-kvm
>> Storage Tags="vol-local-kvm"
>> Host Tags="kvm"
>>
>> Network offering:
>> Name        custom local kvm
>> System offering="custom-local-sm-kvm"
>>
>> Disk offering:
>> Name        custom local kvm
>> Storage Tags="vol-local-kvm"
>>
>>
>> Creating a Instance with a network offering "custom-local-sm-kvm" doesn't
>> stop ACS from using a XenServer systemVM template. Why?
>>
>> All the best,
>> Florian
>>
>>
>> ________________________________________
>> From: Rafael Weingärtner <ra...@gmail.com>
>> Sent: Friday, February 17, 2017 4:08 PM
>> To: users@cloudstack.apache.org
>> Subject: Re: Ubuntu 16.04, Openvswitch networking issue
>>
>> I think we may need more information. ACS version, network deployment
>> type,
>> and hypervisors?
>>
>> On Fri, Feb 17, 2017 at 10:02 AM, Engelmann Florian <
>> florian.engelmann@everyware.ch> wrote:
>>
>> > Hi,
>> >
>> > sorry I ment "I am NOT able to solve"....
>> >
>> > ________________________________________
>> > From: Engelmann Florian <fl...@everyware.ch>
>> > Sent: Friday, February 17, 2017 3:36 PM
>> > To: users@cloudstack.apache.org
>> > Subject: Ubuntu 16.04, Openvswitch networking issue
>> >
>> > Hi,
>> >
>> > another error I am able to solve:
>> >
>> > 2017-02-17 15:24:36,097 DEBUG [c.c.a.ApiServlet] (catalina-exec-26:ctx-
>> > 30020483) (logid:d303f8ef) ===START===  192.168.252.76 -- GET
>> > command=createNetwork&response=json&zoneId=e683eeaa-
>> > 92c9-4651-91b9-165939f9000c&name=net-kvm008&displayText=
>> > net-kvm008&networkOf
>> > 2017-02-17 15:24:36,135 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru]
>> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
>> (logid:d303f8ef) Refusing to
>> > design this network, the physical isolation type is not BCF_SEGMENT
>> > 2017-02-17 15:24:36,136 DEBUG [o.a.c.n.c.m.ContrailGuru]
>> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
>> (logid:d303f8ef) Refusing to
>> > design this network
>> > 2017-02-17 15:24:36,137 DEBUG [c.c.a.m.DirectAgentAttache]
>> > (DirectAgent-144:ctx-b2cdad73) (logid:eb129204) Seq
>> > 179-6955246674520311671: Response Received:
>> > 2017-02-17 15:24:36,137 DEBUG [c.c.a.t.Request]
>> (StatsCollector-5:ctx-4298a591)
>> > (logid:eb129204) Seq 179-6955246674520311671: Received:  { Ans: ,
>> MgmtId:
>> > 345049101620, via: 179(ewcstack-vh003-test), Ver: v1, Flags: 10, {
>> > GetStorageStatsAnswer } }
>> > 2017-02-17 15:24:36,137 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
>> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
>> (logid:d303f8ef) design called
>> > 2017-02-17 15:24:36,138 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru]
>> > (StatsCollector-5:ctx-4298a591) (logid:eb129204)
>> > getCommandHostDelegation: class com.cloud.agent.api.GetStorage
>> StatsCommand
>> > 2017-02-17 15:24:36,138 DEBUG [c.c.h.XenServerGuru]
>> (StatsCollector-5:ctx-4298a591)
>> > (logid:eb129204) getCommandHostDelegation: class com.cloud.agent.api.
>> > GetStorageStatsCommand
>> > 2017-02-17 15:24:36,139 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
>> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
>> (logid:d303f8ef) Refusing to
>> > design this network, the physical isolation type is not MIDO
>> > 2017-02-17 15:24:36,139 DEBUG [c.c.a.m.DirectAgentAttache]
>> > (DirectAgent-72:ctx-656a03ae) (logid:dd7ada9e) Seq
>> 217-8596245788743434945:
>> > Executing request
>> > 2017-02-17 15:24:36,141 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru]
>> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
>> (logid:d303f8ef) Refusing to
>> > design this network
>> > 2017-02-17 15:24:36,142 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru]
>> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
>> (logid:d303f8ef) Refusing to
>> > design this network
>> > 2017-02-17 15:24:36,144 DEBUG [c.c.n.g.OvsGuestNetworkGuru]
>> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
>> (logid:d303f8ef) Refusing to
>> > design this network
>> > 2017-02-17 15:24:36,163 DEBUG [o.a.c.n.g.SspGuestNetworkGuru]
>> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
>> (logid:d303f8ef) SSP not
>> > configured to be active
>> > 2017-02-17 15:24:36,164 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru]
>> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
>> (logid:d303f8ef) Refusing to
>> > design this network
>> > 2017-02-17 15:24:36,165 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru]
>> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
>> (logid:d303f8ef) Refusing to
>> > design network using network offering 54 on physical network 200
>> > 2017-02-17 15:24:36,166 DEBUG [o.a.c.e.o.NetworkOrchestrator]
>> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
>> (logid:d303f8ef) Releasing
>> > lock for Acct[3426fb73-70ad-47d9-9c5d-355f34891438-fen]
>> > 2017-02-17 15:24:36,188 DEBUG [c.c.a.ApiServlet]
>> > (catalina-exec-26:ctx-30020483 <3002-0483> ctx-430b6ae1)
>> (logid:d303f8ef) ===END===
>> > 192.168.252.76 -- GET  command=createNetwork&
>> > response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&
>> > name=net-kvm008&displayText=net-kvm00
>> >
>> >
>> > We do not use BigSwitch or anything like this, just plain Openvswitch
>> with
>> > Ubuntu 16.04. Any idea whats going on?
>> >
>> > All the best,
>> > Florian
>> >
>> > EveryWare AG
>> > Florian Engelmann
>> > Systems Engineer
>> > Zurlindenstrasse 52a
>> > CH-8003 Zürich
>> >
>> > T  +41 44 466 60 00 <+41%2044%20466%2060%2000>
>> > F  +41 44 466 60 10 <+41%2044%20466%2060%2010>
>> >
>> > florian.engelmann@everyware.ch
>> > www.everyware.ch
>> >
>>
>>
>>
>> --
>> Rafael Weingärtner
>>
>
>
>
> --
> Rafael Weingärtner
>



-- 
Rafael Weingärtner

Re: Ubuntu 16.04, Openvswitch networking issue

Posted by Rafael Weingärtner <ra...@gmail.com>.
Hi Engelmann,
I still quite not understand your problem yet. I see that you have three
different clusters; one KVM, One XenServer 6.5 and one 7.0. You want to use
the KVM as the hypervisor to host your system VMs, right?

Have you configured the parameter “system.vm.default.hypervisor”?

On Mon, Feb 20, 2017 at 11:25 AM, Engelmann Florian <
florian.engelmann@everyware.ch> wrote:

> Hi Rafael,
>
> We do use the following setup (Test environment currently):
>
> ACS 4.9.2
> 1x Xenserver 6.5 Cluster (3 nodes)
> 1x Xenserver 7.0 Cluster (1 node)
> 1x Ubuntu 16.04 KVM Cluster (3 nodes)
>
> Networking = Advanced Zone VPC and Virtual Router
>
> I noticed the error Message was just informational an not the real
> problem. The problem we got is:
>
> [...]
> Allocating the VR with id=4185 in datacenter com.cloud.dc.DataCenterVO$$
> EnhancerByCGLIB$$caa6c375@2 with the hypervisor type XenServer
> [...]
> Cluster: 6 has HyperVisorType that does not match the VM, skipping this
> cluster
> [...]
>
> We tried to force ACS to use the KVM systemVM template but for some reason
> ACS refuses to use that System offering.
>
> Hosts:
> Name        ewcstack-vh023-test
> Host Tags="kvm"
>
> Primary storage:
> Name: ewcstack-vh023-test,Local Storage: Storage Tags="vol-local-kvm"
>
> System offering:
> Name  custom-local-sm-kvm
> Storage Tags="vol-local-kvm"
> Host Tags="kvm"
>
> Network offering:
> Name        custom local kvm
> System offering="custom-local-sm-kvm"
>
> Disk offering:
> Name        custom local kvm
> Storage Tags="vol-local-kvm"
>
>
> Creating a Instance with a network offering "custom-local-sm-kvm" doesn't
> stop ACS from using a XenServer systemVM template. Why?
>
> All the best,
> Florian
>
>
> ________________________________________
> From: Rafael Weingärtner <ra...@gmail.com>
> Sent: Friday, February 17, 2017 4:08 PM
> To: users@cloudstack.apache.org
> Subject: Re: Ubuntu 16.04, Openvswitch networking issue
>
> I think we may need more information. ACS version, network deployment type,
> and hypervisors?
>
> On Fri, Feb 17, 2017 at 10:02 AM, Engelmann Florian <
> florian.engelmann@everyware.ch> wrote:
>
> > Hi,
> >
> > sorry I ment "I am NOT able to solve"....
> >
> > ________________________________________
> > From: Engelmann Florian <fl...@everyware.ch>
> > Sent: Friday, February 17, 2017 3:36 PM
> > To: users@cloudstack.apache.org
> > Subject: Ubuntu 16.04, Openvswitch networking issue
> >
> > Hi,
> >
> > another error I am able to solve:
> >
> > 2017-02-17 15:24:36,097 DEBUG [c.c.a.ApiServlet] (catalina-exec-26:ctx-
> > 30020483) (logid:d303f8ef) ===START===  192.168.252.76 -- GET
> > command=createNetwork&response=json&zoneId=e683eeaa-
> > 92c9-4651-91b9-165939f9000c&name=net-kvm008&displayText=
> > net-kvm008&networkOf
> > 2017-02-17 15:24:36,135 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network, the physical isolation type is not BCF_SEGMENT
> > 2017-02-17 15:24:36,136 DEBUG [o.a.c.n.c.m.ContrailGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network
> > 2017-02-17 15:24:36,137 DEBUG [c.c.a.m.DirectAgentAttache]
> > (DirectAgent-144:ctx-b2cdad73) (logid:eb129204) Seq
> > 179-6955246674520311671: Response Received:
> > 2017-02-17 15:24:36,137 DEBUG [c.c.a.t.Request] (StatsCollector-5:ctx-
> 4298a591)
> > (logid:eb129204) Seq 179-6955246674520311671: Received:  { Ans: , MgmtId:
> > 345049101620, via: 179(ewcstack-vh003-test), Ver: v1, Flags: 10, {
> > GetStorageStatsAnswer } }
> > 2017-02-17 15:24:36,137 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) design
> called
> > 2017-02-17 15:24:36,138 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru]
> > (StatsCollector-5:ctx-4298a591) (logid:eb129204)
> > getCommandHostDelegation: class com.cloud.agent.api.
> GetStorageStatsCommand
> > 2017-02-17 15:24:36,138 DEBUG [c.c.h.XenServerGuru]
> (StatsCollector-5:ctx-4298a591)
> > (logid:eb129204) getCommandHostDelegation: class com.cloud.agent.api.
> > GetStorageStatsCommand
> > 2017-02-17 15:24:36,139 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network, the physical isolation type is not MIDO
> > 2017-02-17 15:24:36,139 DEBUG [c.c.a.m.DirectAgentAttache]
> > (DirectAgent-72:ctx-656a03ae) (logid:dd7ada9e) Seq
> 217-8596245788743434945:
> > Executing request
> > 2017-02-17 15:24:36,141 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network
> > 2017-02-17 15:24:36,142 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network
> > 2017-02-17 15:24:36,144 DEBUG [c.c.n.g.OvsGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network
> > 2017-02-17 15:24:36,163 DEBUG [o.a.c.n.g.SspGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) SSP not
> > configured to be active
> > 2017-02-17 15:24:36,164 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network
> > 2017-02-17 15:24:36,165 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design network using network offering 54 on physical network 200
> > 2017-02-17 15:24:36,166 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Releasing
> > lock for Acct[3426fb73-70ad-47d9-9c5d-355f34891438-fen]
> > 2017-02-17 15:24:36,188 DEBUG [c.c.a.ApiServlet]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) ===END===
> > 192.168.252.76 -- GET  command=createNetwork&
> > response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&
> > name=net-kvm008&displayText=net-kvm00
> >
> >
> > We do not use BigSwitch or anything like this, just plain Openvswitch
> with
> > Ubuntu 16.04. Any idea whats going on?
> >
> > All the best,
> > Florian
> >
> > EveryWare AG
> > Florian Engelmann
> > Systems Engineer
> > Zurlindenstrasse 52a
> > CH-8003 Zürich
> >
> > T  +41 44 466 60 00
> > F  +41 44 466 60 10
> >
> > florian.engelmann@everyware.ch
> > www.everyware.ch
> >
>
>
>
> --
> Rafael Weingärtner
>



-- 
Rafael Weingärtner

Re: Ubuntu 16.04, Openvswitch networking issue

Posted by Engelmann Florian <fl...@everyware.ch>.
Hi,

looks like I was wrong. The typo did not fix our issue. We are still not sure whats going on but we are not able to deploy virtual router on xenserver if 

 system.vm.default.hyper

is empty.

All the best,
Florian

________________________________________
From: Engelmann Florian <fl...@everyware.ch>
Sent: Wednesday, March 1, 2017 9:53 AM
To: users@cloudstack.apache.org
Subject: Re: Ubuntu 16.04, Openvswitch networking issue

Dear Rafael,

my apologies! We had a typo in "router.template.xenserver".

All the best,
Florian


________________________________________
From: Rafael Weingärtner <ra...@gmail.com>
Sent: Tuesday, February 28, 2017 4:08 PM
To: users@cloudstack.apache.org
Subject: Re: Ubuntu 16.04, Openvswitch networking issue

Did you configure the parameter “system.vm.default.hypervisor”? If so, ACS
will try to deploy only on hosts of the hypervisor type configured there.

If the parameter is not configured, ACS will get the first it finds. After
it deployed the VR (let’s say on KVM host of cluster "x"), if a redeploy is
needed, it will retry to do so on the same cluster "x". This is a guess now
(have to check the code to make sure), if there are no more available hosts
on the cluster "x" it first deployed the VR, it will try other available
clusters.

On Tue, Feb 28, 2017 at 6:44 AM, Engelmann Florian <
florian.engelmann@everyware.ch> wrote:

> Dear Rafael,
>
> thank you very much. I am wondering why just KVM is tried in our case? The
> Zone got 3 clusters, one 3 node Xenserver 6.5, one 1 node Xenserver 7.0 and
> one 3 node KVM cluster.
>
> Is there some Setting we have to edit?
>
> All the best,
> Florian
>
>
>
> ________________________________________
> From: Rafael Weingärtner <ra...@gmail.com>
> Sent: Wednesday, February 22, 2017 5:00 PM
> To: users@cloudstack.apache.org
> Subject: Re: Ubuntu 16.04, Openvswitch networking issue
>
> Yes, I am able to explain. I am still not getting the whole picture here.
> VR = virtual router
>
> First condition:
>
> > if (dest.getCluster() != null) {
> >
>
>
>    - If we are forcing a VR to a specific cluster, normally this happens
>    when we are starting a router that was already deployed. If it is a new
> VR
>    “dest.getCluster()” will return null( I think this is your case).
>    - Then, we go for the “else” part of the code. In this block, we check
>    if there is a default hypervisor configured,
>    “_resourceMgr.getDefaultHypervisor”.
>    - If there is not a default hypervisor, we load
>    “_resourceMgr.getSupportedHypervisorTypes” all supported hypervisor in
> the
>    given zone. And this will be the value of “hypervisors”.
>    - After all that, at the method
>    “com.cloud.network.router.NetworkHelperImpl.deployRouter(
> RouterDeploymentDefinition,
>    boolean)”, we get the first hypervisor available and try to deploy a
> router
>    in on of the available hosts for this hypervisor type.
>
>
> Was that clear for you?
>
>
> On Wed, Feb 22, 2017 at 9:14 AM, Engelmann Florian <
> florian.engelmann@everyware.ch> wrote:
>
> > Hi,
> >
> > after digging into the source code I wonder if
> >
> > https://github.com/apache/cloudstack/blob/master/server/
> > src/com/cloud/network/router/NetworkHelperImpl.java
> >
> > line 453
> > final List<HypervisorType> hypervisors = getHypervisors(
> > routerDeploymentDefinition);
> >
> > line 458
> >  for (final Iterator<HypervisorType> iter = hypervisors.iterator();
> > iter.hasNext();) {
> >
> > ever gets more than one item in the list? In our case it looks like there
> > is only one item in this list (KVM) even if we got three clusters - one
> > with KVM and two with Xenserver and the VM gets deployed on Xenserver.
> >
> > Are you able to explain the following function to me?
> >
> >     protected List<HypervisorType> getHypervisors(final
> > RouterDeploymentDefinition routerDeploymentDefinition) throws
> > InsufficientServerCapacityException {
> >         final DeployDestination dest = routerDeploymentDefinition.
> > getDest();
> >         List<HypervisorType> hypervisors = new
> ArrayList<HypervisorType>();
> >         if (dest.getCluster() != null) {
> >             if (dest.getCluster().getHypervisorType() ==
> > HypervisorType.Ovm) {
> >                 hypervisors.add(getClusterToStartDomainRouterF
> > orOvm(dest.getCluster().getPodId()));
> >             } else {
> >                 hypervisors.add(dest.getCluster().getHypervisorType());
> >             }
> >         } else {
> >             final HypervisorType defaults = _resourceMgr.
> > getDefaultHypervisor(dest.getDataCenter().getId());
> >             if (defaults != HypervisorType.None) {
> >                 hypervisors.add(defaults);
> >             } else {
> >                 // if there is no default hypervisor, get it from the
> > cluster
> >                 hypervisors = _resourceMgr.getSupportedHypervisorTypes(
> dest.getDataCenter().getId(),
> > true, routerDeploymentDefinition.getPlan().getPodId());
> >             }
> >         }
> >
> > How will that function return a list?
> >
> > All the best,
> > Florian
> >
> > ________________________________________
> > From: Engelmann Florian <fl...@everyware.ch>
> > Sent: Wednesday, February 22, 2017 12:24 PM
> > To: users@cloudstack.apache.org
> > Subject: Re: Ubuntu 16.04, Openvswitch networking issue
> >
> > Hi,
> >
> > this behavior was caused by the following setting:
> >
> > system.vm.default.hypervisor = Xenserver
> >
> > After setting this global parameter to NULL we are able to deploy
> > SystemVMs (virtual router) on KVM.
> >
> > Sad to say, we are no more able to deploy SystemVMs on Xenserver since we
> > changed the parameter?!?!
> >
> > Allocating the VR with id=4213 in datacenter com.cloud.dc.DataCenterVO$$
> > EnhancerByCGLIB$$6fda4e4f@2 with the hypervisor type KVM
> > [...]
> > VM state transitted from :Starting to Stopped with event:
> > OperationFailedvm's original host id: null new host id: null host id
> before
> > state transition: null
> >
> >
> > Is anybody able to point me in the direction where to find the logic (on
> > Github) behind how ACS decides which Hypervisor should be used to deploy
> a
> > VirtualRouter SystemVM? Why is KVM chosen?
> >
> > All the best,
> > Florian
> >
> >
> >
> > ________________________________________
> > From: Engelmann Florian
> > Sent: Monday, February 20, 2017 5:25 PM
> > To: users@cloudstack.apache.org
> > Subject: Re: Ubuntu 16.04, Openvswitch networking issue
> >
> > Hi Rafael,
> >
> > We do use the following setup (Test environment currently):
> >
> > ACS 4.9.2
> > 1x Xenserver 6.5 Cluster (3 nodes)
> > 1x Xenserver 7.0 Cluster (1 node)
> > 1x Ubuntu 16.04 KVM Cluster (3 nodes)
> >
> > Networking = Advanced Zone VPC and Virtual Router
> >
> > I noticed the error Message was just informational an not the real
> > problem. The problem we got is:
> >
> > [...]
> > Allocating the VR with id=4185 in datacenter com.cloud.dc.DataCenterVO$$
> > EnhancerByCGLIB$$caa6c375@2 with the hypervisor type XenServer
> > [...]
> > Cluster: 6 has HyperVisorType that does not match the VM, skipping this
> > cluster
> > [...]
> >
> > We tried to force ACS to use the KVM systemVM template but for some
> reason
> > ACS refuses to use that System offering.
> >
> > Hosts:
> > Name        ewcstack-vh023-test
> > Host Tags="kvm"
> >
> > Primary storage:
> > Name: ewcstack-vh023-test,Local Storage: Storage Tags="vol-local-kvm"
> >
> > System offering:
> > Name  custom-local-sm-kvm
> > Storage Tags="vol-local-kvm"
> > Host Tags="kvm"
> >
> > Network offering:
> > Name        custom local kvm
> > System offering="custom-local-sm-kvm"
> >
> > Disk offering:
> > Name        custom local kvm
> > Storage Tags="vol-local-kvm"
> >
> >
> > Creating a Instance with a network offering "custom-local-sm-kvm" doesn't
> > stop ACS from using a XenServer systemVM template. Why?
> >
> > All the best,
> > Florian
> >
> >
> > ________________________________________
> > From: Rafael Weingärtner <ra...@gmail.com>
> > Sent: Friday, February 17, 2017 4:08 PM
> > To: users@cloudstack.apache.org
> > Subject: Re: Ubuntu 16.04, Openvswitch networking issue
> >
> > I think we may need more information. ACS version, network deployment
> type,
> > and hypervisors?
> >
> > On Fri, Feb 17, 2017 at 10:02 AM, Engelmann Florian <
> > florian.engelmann@everyware.ch> wrote:
> >
> > > Hi,
> > >
> > > sorry I ment "I am NOT able to solve"....
> > >
> > > ________________________________________
> > > From: Engelmann Florian <fl...@everyware.ch>
> > > Sent: Friday, February 17, 2017 3:36 PM
> > > To: users@cloudstack.apache.org
> > > Subject: Ubuntu 16.04, Openvswitch networking issue
> > >
> > > Hi,
> > >
> > > another error I am able to solve:
> > >
> > > 2017-02-17 15:24:36,097 DEBUG [c.c.a.ApiServlet] (catalina-exec-26:ctx-
> > > 30020483) (logid:d303f8ef) ===START===  192.168.252.76 -- GET
> > > command=createNetwork&response=json&zoneId=e683eeaa-
> > > 92c9-4651-91b9-165939f9000c&name=net-kvm008&displayText=
> > > net-kvm008&networkOf
> > > 2017-02-17 15:24:36,135 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network, the physical isolation type is not BCF_SEGMENT
> > > 2017-02-17 15:24:36,136 DEBUG [o.a.c.n.c.m.ContrailGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network
> > > 2017-02-17 15:24:36,137 DEBUG [c.c.a.m.DirectAgentAttache]
> > > (DirectAgent-144:ctx-b2cdad73) (logid:eb129204) Seq
> > > 179-6955246674520311671: Response Received:
> > > 2017-02-17 15:24:36,137 DEBUG [c.c.a.t.Request] (StatsCollector-5:ctx-
> > 4298a591)
> > > (logid:eb129204) Seq 179-6955246674520311671: Received:  { Ans: ,
> MgmtId:
> > > 345049101620, via: 179(ewcstack-vh003-test), Ver: v1, Flags: 10, {
> > > GetStorageStatsAnswer } }
> > > 2017-02-17 15:24:36,137 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) design
> > called
> > > 2017-02-17 15:24:36,138 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru]
> > > (StatsCollector-5:ctx-4298a591) (logid:eb129204)
> > > getCommandHostDelegation: class com.cloud.agent.api.
> > GetStorageStatsCommand
> > > 2017-02-17 15:24:36,138 DEBUG [c.c.h.XenServerGuru]
> > (StatsCollector-5:ctx-4298a591)
> > > (logid:eb129204) getCommandHostDelegation: class com.cloud.agent.api.
> > > GetStorageStatsCommand
> > > 2017-02-17 15:24:36,139 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network, the physical isolation type is not MIDO
> > > 2017-02-17 15:24:36,139 DEBUG [c.c.a.m.DirectAgentAttache]
> > > (DirectAgent-72:ctx-656a03ae) (logid:dd7ada9e) Seq
> > 217-8596245788743434945:
> > > Executing request
> > > 2017-02-17 15:24:36,141 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network
> > > 2017-02-17 15:24:36,142 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network
> > > 2017-02-17 15:24:36,144 DEBUG [c.c.n.g.OvsGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network
> > > 2017-02-17 15:24:36,163 DEBUG [o.a.c.n.g.SspGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) SSP not
> > > configured to be active
> > > 2017-02-17 15:24:36,164 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network
> > > 2017-02-17 15:24:36,165 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design network using network offering 54 on physical network 200
> > > 2017-02-17 15:24:36,166 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Releasing
> > > lock for Acct[3426fb73-70ad-47d9-9c5d-355f34891438-fen]
> > > 2017-02-17 15:24:36,188 DEBUG [c.c.a.ApiServlet]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) ===END===
> > > 192.168.252.76 -- GET  command=createNetwork&
> > > response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&
> > > name=net-kvm008&displayText=net-kvm00
> > >
> > >
> > > We do not use BigSwitch or anything like this, just plain Openvswitch
> > with
> > > Ubuntu 16.04. Any idea whats going on?
> > >
> > > All the best,
> > > Florian
> > >
> > > EveryWare AG
> > > Florian Engelmann
> > > Systems Engineer
> > > Zurlindenstrasse 52a
> > > CH-8003 Zürich
> > >
> > > T  +41 44 466 60 00
> > > F  +41 44 466 60 10
> > >
> > > florian.engelmann@everyware.ch
> > > www.everyware.ch
> > >
> >
> >
> >
> > --
> > Rafael Weingärtner
> >
>
>
>
> --
> Rafael Weingärtner
>



--
Rafael Weingärtner

Re: Ubuntu 16.04, Openvswitch networking issue

Posted by Engelmann Florian <fl...@everyware.ch>.
Dear Rafael,

my apologies! We had a typo in "router.template.xenserver".

All the best,
Florian


________________________________________
From: Rafael Weingärtner <ra...@gmail.com>
Sent: Tuesday, February 28, 2017 4:08 PM
To: users@cloudstack.apache.org
Subject: Re: Ubuntu 16.04, Openvswitch networking issue

Did you configure the parameter “system.vm.default.hypervisor”? If so, ACS
will try to deploy only on hosts of the hypervisor type configured there.

If the parameter is not configured, ACS will get the first it finds. After
it deployed the VR (let’s say on KVM host of cluster "x"), if a redeploy is
needed, it will retry to do so on the same cluster "x". This is a guess now
(have to check the code to make sure), if there are no more available hosts
on the cluster "x" it first deployed the VR, it will try other available
clusters.

On Tue, Feb 28, 2017 at 6:44 AM, Engelmann Florian <
florian.engelmann@everyware.ch> wrote:

> Dear Rafael,
>
> thank you very much. I am wondering why just KVM is tried in our case? The
> Zone got 3 clusters, one 3 node Xenserver 6.5, one 1 node Xenserver 7.0 and
> one 3 node KVM cluster.
>
> Is there some Setting we have to edit?
>
> All the best,
> Florian
>
>
>
> ________________________________________
> From: Rafael Weingärtner <ra...@gmail.com>
> Sent: Wednesday, February 22, 2017 5:00 PM
> To: users@cloudstack.apache.org
> Subject: Re: Ubuntu 16.04, Openvswitch networking issue
>
> Yes, I am able to explain. I am still not getting the whole picture here.
> VR = virtual router
>
> First condition:
>
> > if (dest.getCluster() != null) {
> >
>
>
>    - If we are forcing a VR to a specific cluster, normally this happens
>    when we are starting a router that was already deployed. If it is a new
> VR
>    “dest.getCluster()” will return null( I think this is your case).
>    - Then, we go for the “else” part of the code. In this block, we check
>    if there is a default hypervisor configured,
>    “_resourceMgr.getDefaultHypervisor”.
>    - If there is not a default hypervisor, we load
>    “_resourceMgr.getSupportedHypervisorTypes” all supported hypervisor in
> the
>    given zone. And this will be the value of “hypervisors”.
>    - After all that, at the method
>    “com.cloud.network.router.NetworkHelperImpl.deployRouter(
> RouterDeploymentDefinition,
>    boolean)”, we get the first hypervisor available and try to deploy a
> router
>    in on of the available hosts for this hypervisor type.
>
>
> Was that clear for you?
>
>
> On Wed, Feb 22, 2017 at 9:14 AM, Engelmann Florian <
> florian.engelmann@everyware.ch> wrote:
>
> > Hi,
> >
> > after digging into the source code I wonder if
> >
> > https://github.com/apache/cloudstack/blob/master/server/
> > src/com/cloud/network/router/NetworkHelperImpl.java
> >
> > line 453
> > final List<HypervisorType> hypervisors = getHypervisors(
> > routerDeploymentDefinition);
> >
> > line 458
> >  for (final Iterator<HypervisorType> iter = hypervisors.iterator();
> > iter.hasNext();) {
> >
> > ever gets more than one item in the list? In our case it looks like there
> > is only one item in this list (KVM) even if we got three clusters - one
> > with KVM and two with Xenserver and the VM gets deployed on Xenserver.
> >
> > Are you able to explain the following function to me?
> >
> >     protected List<HypervisorType> getHypervisors(final
> > RouterDeploymentDefinition routerDeploymentDefinition) throws
> > InsufficientServerCapacityException {
> >         final DeployDestination dest = routerDeploymentDefinition.
> > getDest();
> >         List<HypervisorType> hypervisors = new
> ArrayList<HypervisorType>();
> >         if (dest.getCluster() != null) {
> >             if (dest.getCluster().getHypervisorType() ==
> > HypervisorType.Ovm) {
> >                 hypervisors.add(getClusterToStartDomainRouterF
> > orOvm(dest.getCluster().getPodId()));
> >             } else {
> >                 hypervisors.add(dest.getCluster().getHypervisorType());
> >             }
> >         } else {
> >             final HypervisorType defaults = _resourceMgr.
> > getDefaultHypervisor(dest.getDataCenter().getId());
> >             if (defaults != HypervisorType.None) {
> >                 hypervisors.add(defaults);
> >             } else {
> >                 // if there is no default hypervisor, get it from the
> > cluster
> >                 hypervisors = _resourceMgr.getSupportedHypervisorTypes(
> dest.getDataCenter().getId(),
> > true, routerDeploymentDefinition.getPlan().getPodId());
> >             }
> >         }
> >
> > How will that function return a list?
> >
> > All the best,
> > Florian
> >
> > ________________________________________
> > From: Engelmann Florian <fl...@everyware.ch>
> > Sent: Wednesday, February 22, 2017 12:24 PM
> > To: users@cloudstack.apache.org
> > Subject: Re: Ubuntu 16.04, Openvswitch networking issue
> >
> > Hi,
> >
> > this behavior was caused by the following setting:
> >
> > system.vm.default.hypervisor = Xenserver
> >
> > After setting this global parameter to NULL we are able to deploy
> > SystemVMs (virtual router) on KVM.
> >
> > Sad to say, we are no more able to deploy SystemVMs on Xenserver since we
> > changed the parameter?!?!
> >
> > Allocating the VR with id=4213 in datacenter com.cloud.dc.DataCenterVO$$
> > EnhancerByCGLIB$$6fda4e4f@2 with the hypervisor type KVM
> > [...]
> > VM state transitted from :Starting to Stopped with event:
> > OperationFailedvm's original host id: null new host id: null host id
> before
> > state transition: null
> >
> >
> > Is anybody able to point me in the direction where to find the logic (on
> > Github) behind how ACS decides which Hypervisor should be used to deploy
> a
> > VirtualRouter SystemVM? Why is KVM chosen?
> >
> > All the best,
> > Florian
> >
> >
> >
> > ________________________________________
> > From: Engelmann Florian
> > Sent: Monday, February 20, 2017 5:25 PM
> > To: users@cloudstack.apache.org
> > Subject: Re: Ubuntu 16.04, Openvswitch networking issue
> >
> > Hi Rafael,
> >
> > We do use the following setup (Test environment currently):
> >
> > ACS 4.9.2
> > 1x Xenserver 6.5 Cluster (3 nodes)
> > 1x Xenserver 7.0 Cluster (1 node)
> > 1x Ubuntu 16.04 KVM Cluster (3 nodes)
> >
> > Networking = Advanced Zone VPC and Virtual Router
> >
> > I noticed the error Message was just informational an not the real
> > problem. The problem we got is:
> >
> > [...]
> > Allocating the VR with id=4185 in datacenter com.cloud.dc.DataCenterVO$$
> > EnhancerByCGLIB$$caa6c375@2 with the hypervisor type XenServer
> > [...]
> > Cluster: 6 has HyperVisorType that does not match the VM, skipping this
> > cluster
> > [...]
> >
> > We tried to force ACS to use the KVM systemVM template but for some
> reason
> > ACS refuses to use that System offering.
> >
> > Hosts:
> > Name        ewcstack-vh023-test
> > Host Tags="kvm"
> >
> > Primary storage:
> > Name: ewcstack-vh023-test,Local Storage: Storage Tags="vol-local-kvm"
> >
> > System offering:
> > Name  custom-local-sm-kvm
> > Storage Tags="vol-local-kvm"
> > Host Tags="kvm"
> >
> > Network offering:
> > Name        custom local kvm
> > System offering="custom-local-sm-kvm"
> >
> > Disk offering:
> > Name        custom local kvm
> > Storage Tags="vol-local-kvm"
> >
> >
> > Creating a Instance with a network offering "custom-local-sm-kvm" doesn't
> > stop ACS from using a XenServer systemVM template. Why?
> >
> > All the best,
> > Florian
> >
> >
> > ________________________________________
> > From: Rafael Weingärtner <ra...@gmail.com>
> > Sent: Friday, February 17, 2017 4:08 PM
> > To: users@cloudstack.apache.org
> > Subject: Re: Ubuntu 16.04, Openvswitch networking issue
> >
> > I think we may need more information. ACS version, network deployment
> type,
> > and hypervisors?
> >
> > On Fri, Feb 17, 2017 at 10:02 AM, Engelmann Florian <
> > florian.engelmann@everyware.ch> wrote:
> >
> > > Hi,
> > >
> > > sorry I ment "I am NOT able to solve"....
> > >
> > > ________________________________________
> > > From: Engelmann Florian <fl...@everyware.ch>
> > > Sent: Friday, February 17, 2017 3:36 PM
> > > To: users@cloudstack.apache.org
> > > Subject: Ubuntu 16.04, Openvswitch networking issue
> > >
> > > Hi,
> > >
> > > another error I am able to solve:
> > >
> > > 2017-02-17 15:24:36,097 DEBUG [c.c.a.ApiServlet] (catalina-exec-26:ctx-
> > > 30020483) (logid:d303f8ef) ===START===  192.168.252.76 -- GET
> > > command=createNetwork&response=json&zoneId=e683eeaa-
> > > 92c9-4651-91b9-165939f9000c&name=net-kvm008&displayText=
> > > net-kvm008&networkOf
> > > 2017-02-17 15:24:36,135 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network, the physical isolation type is not BCF_SEGMENT
> > > 2017-02-17 15:24:36,136 DEBUG [o.a.c.n.c.m.ContrailGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network
> > > 2017-02-17 15:24:36,137 DEBUG [c.c.a.m.DirectAgentAttache]
> > > (DirectAgent-144:ctx-b2cdad73) (logid:eb129204) Seq
> > > 179-6955246674520311671: Response Received:
> > > 2017-02-17 15:24:36,137 DEBUG [c.c.a.t.Request] (StatsCollector-5:ctx-
> > 4298a591)
> > > (logid:eb129204) Seq 179-6955246674520311671: Received:  { Ans: ,
> MgmtId:
> > > 345049101620, via: 179(ewcstack-vh003-test), Ver: v1, Flags: 10, {
> > > GetStorageStatsAnswer } }
> > > 2017-02-17 15:24:36,137 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) design
> > called
> > > 2017-02-17 15:24:36,138 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru]
> > > (StatsCollector-5:ctx-4298a591) (logid:eb129204)
> > > getCommandHostDelegation: class com.cloud.agent.api.
> > GetStorageStatsCommand
> > > 2017-02-17 15:24:36,138 DEBUG [c.c.h.XenServerGuru]
> > (StatsCollector-5:ctx-4298a591)
> > > (logid:eb129204) getCommandHostDelegation: class com.cloud.agent.api.
> > > GetStorageStatsCommand
> > > 2017-02-17 15:24:36,139 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network, the physical isolation type is not MIDO
> > > 2017-02-17 15:24:36,139 DEBUG [c.c.a.m.DirectAgentAttache]
> > > (DirectAgent-72:ctx-656a03ae) (logid:dd7ada9e) Seq
> > 217-8596245788743434945:
> > > Executing request
> > > 2017-02-17 15:24:36,141 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network
> > > 2017-02-17 15:24:36,142 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network
> > > 2017-02-17 15:24:36,144 DEBUG [c.c.n.g.OvsGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network
> > > 2017-02-17 15:24:36,163 DEBUG [o.a.c.n.g.SspGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) SSP not
> > > configured to be active
> > > 2017-02-17 15:24:36,164 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network
> > > 2017-02-17 15:24:36,165 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design network using network offering 54 on physical network 200
> > > 2017-02-17 15:24:36,166 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Releasing
> > > lock for Acct[3426fb73-70ad-47d9-9c5d-355f34891438-fen]
> > > 2017-02-17 15:24:36,188 DEBUG [c.c.a.ApiServlet]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) ===END===
> > > 192.168.252.76 -- GET  command=createNetwork&
> > > response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&
> > > name=net-kvm008&displayText=net-kvm00
> > >
> > >
> > > We do not use BigSwitch or anything like this, just plain Openvswitch
> > with
> > > Ubuntu 16.04. Any idea whats going on?
> > >
> > > All the best,
> > > Florian
> > >
> > > EveryWare AG
> > > Florian Engelmann
> > > Systems Engineer
> > > Zurlindenstrasse 52a
> > > CH-8003 Zürich
> > >
> > > T  +41 44 466 60 00
> > > F  +41 44 466 60 10
> > >
> > > florian.engelmann@everyware.ch
> > > www.everyware.ch
> > >
> >
> >
> >
> > --
> > Rafael Weingärtner
> >
>
>
>
> --
> Rafael Weingärtner
>



--
Rafael Weingärtner

Re: Ubuntu 16.04, Openvswitch networking issue

Posted by Rafael Weingärtner <ra...@gmail.com>.
Did you configure the parameter “system.vm.default.hypervisor”? If so, ACS
will try to deploy only on hosts of the hypervisor type configured there.

If the parameter is not configured, ACS will get the first it finds. After
it deployed the VR (let’s say on KVM host of cluster "x"), if a redeploy is
needed, it will retry to do so on the same cluster "x". This is a guess now
(have to check the code to make sure), if there are no more available hosts
on the cluster "x" it first deployed the VR, it will try other available
clusters.

On Tue, Feb 28, 2017 at 6:44 AM, Engelmann Florian <
florian.engelmann@everyware.ch> wrote:

> Dear Rafael,
>
> thank you very much. I am wondering why just KVM is tried in our case? The
> Zone got 3 clusters, one 3 node Xenserver 6.5, one 1 node Xenserver 7.0 and
> one 3 node KVM cluster.
>
> Is there some Setting we have to edit?
>
> All the best,
> Florian
>
>
>
> ________________________________________
> From: Rafael Weingärtner <ra...@gmail.com>
> Sent: Wednesday, February 22, 2017 5:00 PM
> To: users@cloudstack.apache.org
> Subject: Re: Ubuntu 16.04, Openvswitch networking issue
>
> Yes, I am able to explain. I am still not getting the whole picture here.
> VR = virtual router
>
> First condition:
>
> > if (dest.getCluster() != null) {
> >
>
>
>    - If we are forcing a VR to a specific cluster, normally this happens
>    when we are starting a router that was already deployed. If it is a new
> VR
>    “dest.getCluster()” will return null( I think this is your case).
>    - Then, we go for the “else” part of the code. In this block, we check
>    if there is a default hypervisor configured,
>    “_resourceMgr.getDefaultHypervisor”.
>    - If there is not a default hypervisor, we load
>    “_resourceMgr.getSupportedHypervisorTypes” all supported hypervisor in
> the
>    given zone. And this will be the value of “hypervisors”.
>    - After all that, at the method
>    “com.cloud.network.router.NetworkHelperImpl.deployRouter(
> RouterDeploymentDefinition,
>    boolean)”, we get the first hypervisor available and try to deploy a
> router
>    in on of the available hosts for this hypervisor type.
>
>
> Was that clear for you?
>
>
> On Wed, Feb 22, 2017 at 9:14 AM, Engelmann Florian <
> florian.engelmann@everyware.ch> wrote:
>
> > Hi,
> >
> > after digging into the source code I wonder if
> >
> > https://github.com/apache/cloudstack/blob/master/server/
> > src/com/cloud/network/router/NetworkHelperImpl.java
> >
> > line 453
> > final List<HypervisorType> hypervisors = getHypervisors(
> > routerDeploymentDefinition);
> >
> > line 458
> >  for (final Iterator<HypervisorType> iter = hypervisors.iterator();
> > iter.hasNext();) {
> >
> > ever gets more than one item in the list? In our case it looks like there
> > is only one item in this list (KVM) even if we got three clusters - one
> > with KVM and two with Xenserver and the VM gets deployed on Xenserver.
> >
> > Are you able to explain the following function to me?
> >
> >     protected List<HypervisorType> getHypervisors(final
> > RouterDeploymentDefinition routerDeploymentDefinition) throws
> > InsufficientServerCapacityException {
> >         final DeployDestination dest = routerDeploymentDefinition.
> > getDest();
> >         List<HypervisorType> hypervisors = new
> ArrayList<HypervisorType>();
> >         if (dest.getCluster() != null) {
> >             if (dest.getCluster().getHypervisorType() ==
> > HypervisorType.Ovm) {
> >                 hypervisors.add(getClusterToStartDomainRouterF
> > orOvm(dest.getCluster().getPodId()));
> >             } else {
> >                 hypervisors.add(dest.getCluster().getHypervisorType());
> >             }
> >         } else {
> >             final HypervisorType defaults = _resourceMgr.
> > getDefaultHypervisor(dest.getDataCenter().getId());
> >             if (defaults != HypervisorType.None) {
> >                 hypervisors.add(defaults);
> >             } else {
> >                 // if there is no default hypervisor, get it from the
> > cluster
> >                 hypervisors = _resourceMgr.getSupportedHypervisorTypes(
> dest.getDataCenter().getId(),
> > true, routerDeploymentDefinition.getPlan().getPodId());
> >             }
> >         }
> >
> > How will that function return a list?
> >
> > All the best,
> > Florian
> >
> > ________________________________________
> > From: Engelmann Florian <fl...@everyware.ch>
> > Sent: Wednesday, February 22, 2017 12:24 PM
> > To: users@cloudstack.apache.org
> > Subject: Re: Ubuntu 16.04, Openvswitch networking issue
> >
> > Hi,
> >
> > this behavior was caused by the following setting:
> >
> > system.vm.default.hypervisor = Xenserver
> >
> > After setting this global parameter to NULL we are able to deploy
> > SystemVMs (virtual router) on KVM.
> >
> > Sad to say, we are no more able to deploy SystemVMs on Xenserver since we
> > changed the parameter?!?!
> >
> > Allocating the VR with id=4213 in datacenter com.cloud.dc.DataCenterVO$$
> > EnhancerByCGLIB$$6fda4e4f@2 with the hypervisor type KVM
> > [...]
> > VM state transitted from :Starting to Stopped with event:
> > OperationFailedvm's original host id: null new host id: null host id
> before
> > state transition: null
> >
> >
> > Is anybody able to point me in the direction where to find the logic (on
> > Github) behind how ACS decides which Hypervisor should be used to deploy
> a
> > VirtualRouter SystemVM? Why is KVM chosen?
> >
> > All the best,
> > Florian
> >
> >
> >
> > ________________________________________
> > From: Engelmann Florian
> > Sent: Monday, February 20, 2017 5:25 PM
> > To: users@cloudstack.apache.org
> > Subject: Re: Ubuntu 16.04, Openvswitch networking issue
> >
> > Hi Rafael,
> >
> > We do use the following setup (Test environment currently):
> >
> > ACS 4.9.2
> > 1x Xenserver 6.5 Cluster (3 nodes)
> > 1x Xenserver 7.0 Cluster (1 node)
> > 1x Ubuntu 16.04 KVM Cluster (3 nodes)
> >
> > Networking = Advanced Zone VPC and Virtual Router
> >
> > I noticed the error Message was just informational an not the real
> > problem. The problem we got is:
> >
> > [...]
> > Allocating the VR with id=4185 in datacenter com.cloud.dc.DataCenterVO$$
> > EnhancerByCGLIB$$caa6c375@2 with the hypervisor type XenServer
> > [...]
> > Cluster: 6 has HyperVisorType that does not match the VM, skipping this
> > cluster
> > [...]
> >
> > We tried to force ACS to use the KVM systemVM template but for some
> reason
> > ACS refuses to use that System offering.
> >
> > Hosts:
> > Name        ewcstack-vh023-test
> > Host Tags="kvm"
> >
> > Primary storage:
> > Name: ewcstack-vh023-test,Local Storage: Storage Tags="vol-local-kvm"
> >
> > System offering:
> > Name  custom-local-sm-kvm
> > Storage Tags="vol-local-kvm"
> > Host Tags="kvm"
> >
> > Network offering:
> > Name        custom local kvm
> > System offering="custom-local-sm-kvm"
> >
> > Disk offering:
> > Name        custom local kvm
> > Storage Tags="vol-local-kvm"
> >
> >
> > Creating a Instance with a network offering "custom-local-sm-kvm" doesn't
> > stop ACS from using a XenServer systemVM template. Why?
> >
> > All the best,
> > Florian
> >
> >
> > ________________________________________
> > From: Rafael Weingärtner <ra...@gmail.com>
> > Sent: Friday, February 17, 2017 4:08 PM
> > To: users@cloudstack.apache.org
> > Subject: Re: Ubuntu 16.04, Openvswitch networking issue
> >
> > I think we may need more information. ACS version, network deployment
> type,
> > and hypervisors?
> >
> > On Fri, Feb 17, 2017 at 10:02 AM, Engelmann Florian <
> > florian.engelmann@everyware.ch> wrote:
> >
> > > Hi,
> > >
> > > sorry I ment "I am NOT able to solve"....
> > >
> > > ________________________________________
> > > From: Engelmann Florian <fl...@everyware.ch>
> > > Sent: Friday, February 17, 2017 3:36 PM
> > > To: users@cloudstack.apache.org
> > > Subject: Ubuntu 16.04, Openvswitch networking issue
> > >
> > > Hi,
> > >
> > > another error I am able to solve:
> > >
> > > 2017-02-17 15:24:36,097 DEBUG [c.c.a.ApiServlet] (catalina-exec-26:ctx-
> > > 30020483) (logid:d303f8ef) ===START===  192.168.252.76 -- GET
> > > command=createNetwork&response=json&zoneId=e683eeaa-
> > > 92c9-4651-91b9-165939f9000c&name=net-kvm008&displayText=
> > > net-kvm008&networkOf
> > > 2017-02-17 15:24:36,135 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network, the physical isolation type is not BCF_SEGMENT
> > > 2017-02-17 15:24:36,136 DEBUG [o.a.c.n.c.m.ContrailGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network
> > > 2017-02-17 15:24:36,137 DEBUG [c.c.a.m.DirectAgentAttache]
> > > (DirectAgent-144:ctx-b2cdad73) (logid:eb129204) Seq
> > > 179-6955246674520311671: Response Received:
> > > 2017-02-17 15:24:36,137 DEBUG [c.c.a.t.Request] (StatsCollector-5:ctx-
> > 4298a591)
> > > (logid:eb129204) Seq 179-6955246674520311671: Received:  { Ans: ,
> MgmtId:
> > > 345049101620, via: 179(ewcstack-vh003-test), Ver: v1, Flags: 10, {
> > > GetStorageStatsAnswer } }
> > > 2017-02-17 15:24:36,137 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) design
> > called
> > > 2017-02-17 15:24:36,138 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru]
> > > (StatsCollector-5:ctx-4298a591) (logid:eb129204)
> > > getCommandHostDelegation: class com.cloud.agent.api.
> > GetStorageStatsCommand
> > > 2017-02-17 15:24:36,138 DEBUG [c.c.h.XenServerGuru]
> > (StatsCollector-5:ctx-4298a591)
> > > (logid:eb129204) getCommandHostDelegation: class com.cloud.agent.api.
> > > GetStorageStatsCommand
> > > 2017-02-17 15:24:36,139 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network, the physical isolation type is not MIDO
> > > 2017-02-17 15:24:36,139 DEBUG [c.c.a.m.DirectAgentAttache]
> > > (DirectAgent-72:ctx-656a03ae) (logid:dd7ada9e) Seq
> > 217-8596245788743434945:
> > > Executing request
> > > 2017-02-17 15:24:36,141 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network
> > > 2017-02-17 15:24:36,142 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network
> > > 2017-02-17 15:24:36,144 DEBUG [c.c.n.g.OvsGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network
> > > 2017-02-17 15:24:36,163 DEBUG [o.a.c.n.g.SspGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) SSP not
> > > configured to be active
> > > 2017-02-17 15:24:36,164 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design this network
> > > 2017-02-17 15:24:36,165 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing
> to
> > > design network using network offering 54 on physical network 200
> > > 2017-02-17 15:24:36,166 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Releasing
> > > lock for Acct[3426fb73-70ad-47d9-9c5d-355f34891438-fen]
> > > 2017-02-17 15:24:36,188 DEBUG [c.c.a.ApiServlet]
> > > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) ===END===
> > > 192.168.252.76 -- GET  command=createNetwork&
> > > response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&
> > > name=net-kvm008&displayText=net-kvm00
> > >
> > >
> > > We do not use BigSwitch or anything like this, just plain Openvswitch
> > with
> > > Ubuntu 16.04. Any idea whats going on?
> > >
> > > All the best,
> > > Florian
> > >
> > > EveryWare AG
> > > Florian Engelmann
> > > Systems Engineer
> > > Zurlindenstrasse 52a
> > > CH-8003 Zürich
> > >
> > > T  +41 44 466 60 00
> > > F  +41 44 466 60 10
> > >
> > > florian.engelmann@everyware.ch
> > > www.everyware.ch
> > >
> >
> >
> >
> > --
> > Rafael Weingärtner
> >
>
>
>
> --
> Rafael Weingärtner
>



-- 
Rafael Weingärtner

Re: Ubuntu 16.04, Openvswitch networking issue

Posted by Engelmann Florian <fl...@everyware.ch>.
Dear Rafael,

thank you very much. I am wondering why just KVM is tried in our case? The Zone got 3 clusters, one 3 node Xenserver 6.5, one 1 node Xenserver 7.0 and one 3 node KVM cluster.

Is there some Setting we have to edit?

All the best,
Florian



________________________________________
From: Rafael Weingärtner <ra...@gmail.com>
Sent: Wednesday, February 22, 2017 5:00 PM
To: users@cloudstack.apache.org
Subject: Re: Ubuntu 16.04, Openvswitch networking issue

Yes, I am able to explain. I am still not getting the whole picture here.
VR = virtual router

First condition:

> if (dest.getCluster() != null) {
>


   - If we are forcing a VR to a specific cluster, normally this happens
   when we are starting a router that was already deployed. If it is a new VR
   “dest.getCluster()” will return null( I think this is your case).
   - Then, we go for the “else” part of the code. In this block, we check
   if there is a default hypervisor configured,
   “_resourceMgr.getDefaultHypervisor”.
   - If there is not a default hypervisor, we load
   “_resourceMgr.getSupportedHypervisorTypes” all supported hypervisor in the
   given zone. And this will be the value of “hypervisors”.
   - After all that, at the method
   “com.cloud.network.router.NetworkHelperImpl.deployRouter(RouterDeploymentDefinition,
   boolean)”, we get the first hypervisor available and try to deploy a router
   in on of the available hosts for this hypervisor type.


Was that clear for you?


On Wed, Feb 22, 2017 at 9:14 AM, Engelmann Florian <
florian.engelmann@everyware.ch> wrote:

> Hi,
>
> after digging into the source code I wonder if
>
> https://github.com/apache/cloudstack/blob/master/server/
> src/com/cloud/network/router/NetworkHelperImpl.java
>
> line 453
> final List<HypervisorType> hypervisors = getHypervisors(
> routerDeploymentDefinition);
>
> line 458
>  for (final Iterator<HypervisorType> iter = hypervisors.iterator();
> iter.hasNext();) {
>
> ever gets more than one item in the list? In our case it looks like there
> is only one item in this list (KVM) even if we got three clusters - one
> with KVM and two with Xenserver and the VM gets deployed on Xenserver.
>
> Are you able to explain the following function to me?
>
>     protected List<HypervisorType> getHypervisors(final
> RouterDeploymentDefinition routerDeploymentDefinition) throws
> InsufficientServerCapacityException {
>         final DeployDestination dest = routerDeploymentDefinition.
> getDest();
>         List<HypervisorType> hypervisors = new ArrayList<HypervisorType>();
>         if (dest.getCluster() != null) {
>             if (dest.getCluster().getHypervisorType() ==
> HypervisorType.Ovm) {
>                 hypervisors.add(getClusterToStartDomainRouterF
> orOvm(dest.getCluster().getPodId()));
>             } else {
>                 hypervisors.add(dest.getCluster().getHypervisorType());
>             }
>         } else {
>             final HypervisorType defaults = _resourceMgr.
> getDefaultHypervisor(dest.getDataCenter().getId());
>             if (defaults != HypervisorType.None) {
>                 hypervisors.add(defaults);
>             } else {
>                 // if there is no default hypervisor, get it from the
> cluster
>                 hypervisors = _resourceMgr.getSupportedHypervisorTypes(dest.getDataCenter().getId(),
> true, routerDeploymentDefinition.getPlan().getPodId());
>             }
>         }
>
> How will that function return a list?
>
> All the best,
> Florian
>
> ________________________________________
> From: Engelmann Florian <fl...@everyware.ch>
> Sent: Wednesday, February 22, 2017 12:24 PM
> To: users@cloudstack.apache.org
> Subject: Re: Ubuntu 16.04, Openvswitch networking issue
>
> Hi,
>
> this behavior was caused by the following setting:
>
> system.vm.default.hypervisor = Xenserver
>
> After setting this global parameter to NULL we are able to deploy
> SystemVMs (virtual router) on KVM.
>
> Sad to say, we are no more able to deploy SystemVMs on Xenserver since we
> changed the parameter?!?!
>
> Allocating the VR with id=4213 in datacenter com.cloud.dc.DataCenterVO$$
> EnhancerByCGLIB$$6fda4e4f@2 with the hypervisor type KVM
> [...]
> VM state transitted from :Starting to Stopped with event:
> OperationFailedvm's original host id: null new host id: null host id before
> state transition: null
>
>
> Is anybody able to point me in the direction where to find the logic (on
> Github) behind how ACS decides which Hypervisor should be used to deploy a
> VirtualRouter SystemVM? Why is KVM chosen?
>
> All the best,
> Florian
>
>
>
> ________________________________________
> From: Engelmann Florian
> Sent: Monday, February 20, 2017 5:25 PM
> To: users@cloudstack.apache.org
> Subject: Re: Ubuntu 16.04, Openvswitch networking issue
>
> Hi Rafael,
>
> We do use the following setup (Test environment currently):
>
> ACS 4.9.2
> 1x Xenserver 6.5 Cluster (3 nodes)
> 1x Xenserver 7.0 Cluster (1 node)
> 1x Ubuntu 16.04 KVM Cluster (3 nodes)
>
> Networking = Advanced Zone VPC and Virtual Router
>
> I noticed the error Message was just informational an not the real
> problem. The problem we got is:
>
> [...]
> Allocating the VR with id=4185 in datacenter com.cloud.dc.DataCenterVO$$
> EnhancerByCGLIB$$caa6c375@2 with the hypervisor type XenServer
> [...]
> Cluster: 6 has HyperVisorType that does not match the VM, skipping this
> cluster
> [...]
>
> We tried to force ACS to use the KVM systemVM template but for some reason
> ACS refuses to use that System offering.
>
> Hosts:
> Name        ewcstack-vh023-test
> Host Tags="kvm"
>
> Primary storage:
> Name: ewcstack-vh023-test,Local Storage: Storage Tags="vol-local-kvm"
>
> System offering:
> Name  custom-local-sm-kvm
> Storage Tags="vol-local-kvm"
> Host Tags="kvm"
>
> Network offering:
> Name        custom local kvm
> System offering="custom-local-sm-kvm"
>
> Disk offering:
> Name        custom local kvm
> Storage Tags="vol-local-kvm"
>
>
> Creating a Instance with a network offering "custom-local-sm-kvm" doesn't
> stop ACS from using a XenServer systemVM template. Why?
>
> All the best,
> Florian
>
>
> ________________________________________
> From: Rafael Weingärtner <ra...@gmail.com>
> Sent: Friday, February 17, 2017 4:08 PM
> To: users@cloudstack.apache.org
> Subject: Re: Ubuntu 16.04, Openvswitch networking issue
>
> I think we may need more information. ACS version, network deployment type,
> and hypervisors?
>
> On Fri, Feb 17, 2017 at 10:02 AM, Engelmann Florian <
> florian.engelmann@everyware.ch> wrote:
>
> > Hi,
> >
> > sorry I ment "I am NOT able to solve"....
> >
> > ________________________________________
> > From: Engelmann Florian <fl...@everyware.ch>
> > Sent: Friday, February 17, 2017 3:36 PM
> > To: users@cloudstack.apache.org
> > Subject: Ubuntu 16.04, Openvswitch networking issue
> >
> > Hi,
> >
> > another error I am able to solve:
> >
> > 2017-02-17 15:24:36,097 DEBUG [c.c.a.ApiServlet] (catalina-exec-26:ctx-
> > 30020483) (logid:d303f8ef) ===START===  192.168.252.76 -- GET
> > command=createNetwork&response=json&zoneId=e683eeaa-
> > 92c9-4651-91b9-165939f9000c&name=net-kvm008&displayText=
> > net-kvm008&networkOf
> > 2017-02-17 15:24:36,135 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network, the physical isolation type is not BCF_SEGMENT
> > 2017-02-17 15:24:36,136 DEBUG [o.a.c.n.c.m.ContrailGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network
> > 2017-02-17 15:24:36,137 DEBUG [c.c.a.m.DirectAgentAttache]
> > (DirectAgent-144:ctx-b2cdad73) (logid:eb129204) Seq
> > 179-6955246674520311671: Response Received:
> > 2017-02-17 15:24:36,137 DEBUG [c.c.a.t.Request] (StatsCollector-5:ctx-
> 4298a591)
> > (logid:eb129204) Seq 179-6955246674520311671: Received:  { Ans: , MgmtId:
> > 345049101620, via: 179(ewcstack-vh003-test), Ver: v1, Flags: 10, {
> > GetStorageStatsAnswer } }
> > 2017-02-17 15:24:36,137 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) design
> called
> > 2017-02-17 15:24:36,138 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru]
> > (StatsCollector-5:ctx-4298a591) (logid:eb129204)
> > getCommandHostDelegation: class com.cloud.agent.api.
> GetStorageStatsCommand
> > 2017-02-17 15:24:36,138 DEBUG [c.c.h.XenServerGuru]
> (StatsCollector-5:ctx-4298a591)
> > (logid:eb129204) getCommandHostDelegation: class com.cloud.agent.api.
> > GetStorageStatsCommand
> > 2017-02-17 15:24:36,139 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network, the physical isolation type is not MIDO
> > 2017-02-17 15:24:36,139 DEBUG [c.c.a.m.DirectAgentAttache]
> > (DirectAgent-72:ctx-656a03ae) (logid:dd7ada9e) Seq
> 217-8596245788743434945:
> > Executing request
> > 2017-02-17 15:24:36,141 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network
> > 2017-02-17 15:24:36,142 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network
> > 2017-02-17 15:24:36,144 DEBUG [c.c.n.g.OvsGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network
> > 2017-02-17 15:24:36,163 DEBUG [o.a.c.n.g.SspGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) SSP not
> > configured to be active
> > 2017-02-17 15:24:36,164 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network
> > 2017-02-17 15:24:36,165 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design network using network offering 54 on physical network 200
> > 2017-02-17 15:24:36,166 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Releasing
> > lock for Acct[3426fb73-70ad-47d9-9c5d-355f34891438-fen]
> > 2017-02-17 15:24:36,188 DEBUG [c.c.a.ApiServlet]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) ===END===
> > 192.168.252.76 -- GET  command=createNetwork&
> > response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&
> > name=net-kvm008&displayText=net-kvm00
> >
> >
> > We do not use BigSwitch or anything like this, just plain Openvswitch
> with
> > Ubuntu 16.04. Any idea whats going on?
> >
> > All the best,
> > Florian
> >
> > EveryWare AG
> > Florian Engelmann
> > Systems Engineer
> > Zurlindenstrasse 52a
> > CH-8003 Zürich
> >
> > T  +41 44 466 60 00
> > F  +41 44 466 60 10
> >
> > florian.engelmann@everyware.ch
> > www.everyware.ch
> >
>
>
>
> --
> Rafael Weingärtner
>



--
Rafael Weingärtner

Re: Ubuntu 16.04, Openvswitch networking issue

Posted by Rafael Weingärtner <ra...@gmail.com>.
Yes, I am able to explain. I am still not getting the whole picture here.
VR = virtual router

First condition:

> if (dest.getCluster() != null) {
>


   - If we are forcing a VR to a specific cluster, normally this happens
   when we are starting a router that was already deployed. If it is a new VR
   “dest.getCluster()” will return null( I think this is your case).
   - Then, we go for the “else” part of the code. In this block, we check
   if there is a default hypervisor configured,
   “_resourceMgr.getDefaultHypervisor”.
   - If there is not a default hypervisor, we load
   “_resourceMgr.getSupportedHypervisorTypes” all supported hypervisor in the
   given zone. And this will be the value of “hypervisors”.
   - After all that, at the method
   “com.cloud.network.router.NetworkHelperImpl.deployRouter(RouterDeploymentDefinition,
   boolean)”, we get the first hypervisor available and try to deploy a router
   in on of the available hosts for this hypervisor type.


Was that clear for you?


On Wed, Feb 22, 2017 at 9:14 AM, Engelmann Florian <
florian.engelmann@everyware.ch> wrote:

> Hi,
>
> after digging into the source code I wonder if
>
> https://github.com/apache/cloudstack/blob/master/server/
> src/com/cloud/network/router/NetworkHelperImpl.java
>
> line 453
> final List<HypervisorType> hypervisors = getHypervisors(
> routerDeploymentDefinition);
>
> line 458
>  for (final Iterator<HypervisorType> iter = hypervisors.iterator();
> iter.hasNext();) {
>
> ever gets more than one item in the list? In our case it looks like there
> is only one item in this list (KVM) even if we got three clusters - one
> with KVM and two with Xenserver and the VM gets deployed on Xenserver.
>
> Are you able to explain the following function to me?
>
>     protected List<HypervisorType> getHypervisors(final
> RouterDeploymentDefinition routerDeploymentDefinition) throws
> InsufficientServerCapacityException {
>         final DeployDestination dest = routerDeploymentDefinition.
> getDest();
>         List<HypervisorType> hypervisors = new ArrayList<HypervisorType>();
>         if (dest.getCluster() != null) {
>             if (dest.getCluster().getHypervisorType() ==
> HypervisorType.Ovm) {
>                 hypervisors.add(getClusterToStartDomainRouterF
> orOvm(dest.getCluster().getPodId()));
>             } else {
>                 hypervisors.add(dest.getCluster().getHypervisorType());
>             }
>         } else {
>             final HypervisorType defaults = _resourceMgr.
> getDefaultHypervisor(dest.getDataCenter().getId());
>             if (defaults != HypervisorType.None) {
>                 hypervisors.add(defaults);
>             } else {
>                 // if there is no default hypervisor, get it from the
> cluster
>                 hypervisors = _resourceMgr.getSupportedHypervisorTypes(dest.getDataCenter().getId(),
> true, routerDeploymentDefinition.getPlan().getPodId());
>             }
>         }
>
> How will that function return a list?
>
> All the best,
> Florian
>
> ________________________________________
> From: Engelmann Florian <fl...@everyware.ch>
> Sent: Wednesday, February 22, 2017 12:24 PM
> To: users@cloudstack.apache.org
> Subject: Re: Ubuntu 16.04, Openvswitch networking issue
>
> Hi,
>
> this behavior was caused by the following setting:
>
> system.vm.default.hypervisor = Xenserver
>
> After setting this global parameter to NULL we are able to deploy
> SystemVMs (virtual router) on KVM.
>
> Sad to say, we are no more able to deploy SystemVMs on Xenserver since we
> changed the parameter?!?!
>
> Allocating the VR with id=4213 in datacenter com.cloud.dc.DataCenterVO$$
> EnhancerByCGLIB$$6fda4e4f@2 with the hypervisor type KVM
> [...]
> VM state transitted from :Starting to Stopped with event:
> OperationFailedvm's original host id: null new host id: null host id before
> state transition: null
>
>
> Is anybody able to point me in the direction where to find the logic (on
> Github) behind how ACS decides which Hypervisor should be used to deploy a
> VirtualRouter SystemVM? Why is KVM chosen?
>
> All the best,
> Florian
>
>
>
> ________________________________________
> From: Engelmann Florian
> Sent: Monday, February 20, 2017 5:25 PM
> To: users@cloudstack.apache.org
> Subject: Re: Ubuntu 16.04, Openvswitch networking issue
>
> Hi Rafael,
>
> We do use the following setup (Test environment currently):
>
> ACS 4.9.2
> 1x Xenserver 6.5 Cluster (3 nodes)
> 1x Xenserver 7.0 Cluster (1 node)
> 1x Ubuntu 16.04 KVM Cluster (3 nodes)
>
> Networking = Advanced Zone VPC and Virtual Router
>
> I noticed the error Message was just informational an not the real
> problem. The problem we got is:
>
> [...]
> Allocating the VR with id=4185 in datacenter com.cloud.dc.DataCenterVO$$
> EnhancerByCGLIB$$caa6c375@2 with the hypervisor type XenServer
> [...]
> Cluster: 6 has HyperVisorType that does not match the VM, skipping this
> cluster
> [...]
>
> We tried to force ACS to use the KVM systemVM template but for some reason
> ACS refuses to use that System offering.
>
> Hosts:
> Name        ewcstack-vh023-test
> Host Tags="kvm"
>
> Primary storage:
> Name: ewcstack-vh023-test,Local Storage: Storage Tags="vol-local-kvm"
>
> System offering:
> Name  custom-local-sm-kvm
> Storage Tags="vol-local-kvm"
> Host Tags="kvm"
>
> Network offering:
> Name        custom local kvm
> System offering="custom-local-sm-kvm"
>
> Disk offering:
> Name        custom local kvm
> Storage Tags="vol-local-kvm"
>
>
> Creating a Instance with a network offering "custom-local-sm-kvm" doesn't
> stop ACS from using a XenServer systemVM template. Why?
>
> All the best,
> Florian
>
>
> ________________________________________
> From: Rafael Weingärtner <ra...@gmail.com>
> Sent: Friday, February 17, 2017 4:08 PM
> To: users@cloudstack.apache.org
> Subject: Re: Ubuntu 16.04, Openvswitch networking issue
>
> I think we may need more information. ACS version, network deployment type,
> and hypervisors?
>
> On Fri, Feb 17, 2017 at 10:02 AM, Engelmann Florian <
> florian.engelmann@everyware.ch> wrote:
>
> > Hi,
> >
> > sorry I ment "I am NOT able to solve"....
> >
> > ________________________________________
> > From: Engelmann Florian <fl...@everyware.ch>
> > Sent: Friday, February 17, 2017 3:36 PM
> > To: users@cloudstack.apache.org
> > Subject: Ubuntu 16.04, Openvswitch networking issue
> >
> > Hi,
> >
> > another error I am able to solve:
> >
> > 2017-02-17 15:24:36,097 DEBUG [c.c.a.ApiServlet] (catalina-exec-26:ctx-
> > 30020483) (logid:d303f8ef) ===START===  192.168.252.76 -- GET
> > command=createNetwork&response=json&zoneId=e683eeaa-
> > 92c9-4651-91b9-165939f9000c&name=net-kvm008&displayText=
> > net-kvm008&networkOf
> > 2017-02-17 15:24:36,135 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network, the physical isolation type is not BCF_SEGMENT
> > 2017-02-17 15:24:36,136 DEBUG [o.a.c.n.c.m.ContrailGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network
> > 2017-02-17 15:24:36,137 DEBUG [c.c.a.m.DirectAgentAttache]
> > (DirectAgent-144:ctx-b2cdad73) (logid:eb129204) Seq
> > 179-6955246674520311671: Response Received:
> > 2017-02-17 15:24:36,137 DEBUG [c.c.a.t.Request] (StatsCollector-5:ctx-
> 4298a591)
> > (logid:eb129204) Seq 179-6955246674520311671: Received:  { Ans: , MgmtId:
> > 345049101620, via: 179(ewcstack-vh003-test), Ver: v1, Flags: 10, {
> > GetStorageStatsAnswer } }
> > 2017-02-17 15:24:36,137 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) design
> called
> > 2017-02-17 15:24:36,138 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru]
> > (StatsCollector-5:ctx-4298a591) (logid:eb129204)
> > getCommandHostDelegation: class com.cloud.agent.api.
> GetStorageStatsCommand
> > 2017-02-17 15:24:36,138 DEBUG [c.c.h.XenServerGuru]
> (StatsCollector-5:ctx-4298a591)
> > (logid:eb129204) getCommandHostDelegation: class com.cloud.agent.api.
> > GetStorageStatsCommand
> > 2017-02-17 15:24:36,139 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network, the physical isolation type is not MIDO
> > 2017-02-17 15:24:36,139 DEBUG [c.c.a.m.DirectAgentAttache]
> > (DirectAgent-72:ctx-656a03ae) (logid:dd7ada9e) Seq
> 217-8596245788743434945:
> > Executing request
> > 2017-02-17 15:24:36,141 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network
> > 2017-02-17 15:24:36,142 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network
> > 2017-02-17 15:24:36,144 DEBUG [c.c.n.g.OvsGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network
> > 2017-02-17 15:24:36,163 DEBUG [o.a.c.n.g.SspGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) SSP not
> > configured to be active
> > 2017-02-17 15:24:36,164 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design this network
> > 2017-02-17 15:24:36,165 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> > design network using network offering 54 on physical network 200
> > 2017-02-17 15:24:36,166 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Releasing
> > lock for Acct[3426fb73-70ad-47d9-9c5d-355f34891438-fen]
> > 2017-02-17 15:24:36,188 DEBUG [c.c.a.ApiServlet]
> > (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) ===END===
> > 192.168.252.76 -- GET  command=createNetwork&
> > response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&
> > name=net-kvm008&displayText=net-kvm00
> >
> >
> > We do not use BigSwitch or anything like this, just plain Openvswitch
> with
> > Ubuntu 16.04. Any idea whats going on?
> >
> > All the best,
> > Florian
> >
> > EveryWare AG
> > Florian Engelmann
> > Systems Engineer
> > Zurlindenstrasse 52a
> > CH-8003 Zürich
> >
> > T  +41 44 466 60 00
> > F  +41 44 466 60 10
> >
> > florian.engelmann@everyware.ch
> > www.everyware.ch
> >
>
>
>
> --
> Rafael Weingärtner
>



-- 
Rafael Weingärtner

Re: Ubuntu 16.04, Openvswitch networking issue

Posted by Engelmann Florian <fl...@everyware.ch>.
Hi,

after digging into the source code I wonder if 

https://github.com/apache/cloudstack/blob/master/server/src/com/cloud/network/router/NetworkHelperImpl.java

line 453
final List<HypervisorType> hypervisors = getHypervisors(routerDeploymentDefinition);

line 458
 for (final Iterator<HypervisorType> iter = hypervisors.iterator(); iter.hasNext();) {

ever gets more than one item in the list? In our case it looks like there is only one item in this list (KVM) even if we got three clusters - one with KVM and two with Xenserver and the VM gets deployed on Xenserver.

Are you able to explain the following function to me?

    protected List<HypervisorType> getHypervisors(final RouterDeploymentDefinition routerDeploymentDefinition) throws InsufficientServerCapacityException {
        final DeployDestination dest = routerDeploymentDefinition.getDest();
        List<HypervisorType> hypervisors = new ArrayList<HypervisorType>();
        if (dest.getCluster() != null) {
            if (dest.getCluster().getHypervisorType() == HypervisorType.Ovm) {
                hypervisors.add(getClusterToStartDomainRouterForOvm(dest.getCluster().getPodId()));
            } else {
                hypervisors.add(dest.getCluster().getHypervisorType());
            }
        } else {
            final HypervisorType defaults = _resourceMgr.getDefaultHypervisor(dest.getDataCenter().getId());
            if (defaults != HypervisorType.None) {
                hypervisors.add(defaults);
            } else {
                // if there is no default hypervisor, get it from the cluster
                hypervisors = _resourceMgr.getSupportedHypervisorTypes(dest.getDataCenter().getId(), true, routerDeploymentDefinition.getPlan().getPodId());
            }
        }

How will that function return a list?

All the best,
Florian

________________________________________
From: Engelmann Florian <fl...@everyware.ch>
Sent: Wednesday, February 22, 2017 12:24 PM
To: users@cloudstack.apache.org
Subject: Re: Ubuntu 16.04, Openvswitch networking issue

Hi,

this behavior was caused by the following setting:

system.vm.default.hypervisor = Xenserver

After setting this global parameter to NULL we are able to deploy SystemVMs (virtual router) on KVM.

Sad to say, we are no more able to deploy SystemVMs on Xenserver since we changed the parameter?!?!

Allocating the VR with id=4213 in datacenter com.cloud.dc.DataCenterVO$$EnhancerByCGLIB$$6fda4e4f@2 with the hypervisor type KVM
[...]
VM state transitted from :Starting to Stopped with event: OperationFailedvm's original host id: null new host id: null host id before state transition: null


Is anybody able to point me in the direction where to find the logic (on Github) behind how ACS decides which Hypervisor should be used to deploy a VirtualRouter SystemVM? Why is KVM chosen?

All the best,
Florian



________________________________________
From: Engelmann Florian
Sent: Monday, February 20, 2017 5:25 PM
To: users@cloudstack.apache.org
Subject: Re: Ubuntu 16.04, Openvswitch networking issue

Hi Rafael,

We do use the following setup (Test environment currently):

ACS 4.9.2
1x Xenserver 6.5 Cluster (3 nodes)
1x Xenserver 7.0 Cluster (1 node)
1x Ubuntu 16.04 KVM Cluster (3 nodes)

Networking = Advanced Zone VPC and Virtual Router

I noticed the error Message was just informational an not the real problem. The problem we got is:

[...]
Allocating the VR with id=4185 in datacenter com.cloud.dc.DataCenterVO$$EnhancerByCGLIB$$caa6c375@2 with the hypervisor type XenServer
[...]
Cluster: 6 has HyperVisorType that does not match the VM, skipping this cluster
[...]

We tried to force ACS to use the KVM systemVM template but for some reason ACS refuses to use that System offering.

Hosts:
Name        ewcstack-vh023-test
Host Tags="kvm"

Primary storage:
Name: ewcstack-vh023-test,Local Storage: Storage Tags="vol-local-kvm"

System offering:
Name  custom-local-sm-kvm
Storage Tags="vol-local-kvm"
Host Tags="kvm"

Network offering:
Name        custom local kvm
System offering="custom-local-sm-kvm"

Disk offering:
Name        custom local kvm
Storage Tags="vol-local-kvm"


Creating a Instance with a network offering "custom-local-sm-kvm" doesn't stop ACS from using a XenServer systemVM template. Why?

All the best,
Florian


________________________________________
From: Rafael Weingärtner <ra...@gmail.com>
Sent: Friday, February 17, 2017 4:08 PM
To: users@cloudstack.apache.org
Subject: Re: Ubuntu 16.04, Openvswitch networking issue

I think we may need more information. ACS version, network deployment type,
and hypervisors?

On Fri, Feb 17, 2017 at 10:02 AM, Engelmann Florian <
florian.engelmann@everyware.ch> wrote:

> Hi,
>
> sorry I ment "I am NOT able to solve"....
>
> ________________________________________
> From: Engelmann Florian <fl...@everyware.ch>
> Sent: Friday, February 17, 2017 3:36 PM
> To: users@cloudstack.apache.org
> Subject: Ubuntu 16.04, Openvswitch networking issue
>
> Hi,
>
> another error I am able to solve:
>
> 2017-02-17 15:24:36,097 DEBUG [c.c.a.ApiServlet] (catalina-exec-26:ctx-
> 30020483) (logid:d303f8ef) ===START===  192.168.252.76 -- GET
> command=createNetwork&response=json&zoneId=e683eeaa-
> 92c9-4651-91b9-165939f9000c&name=net-kvm008&displayText=
> net-kvm008&networkOf
> 2017-02-17 15:24:36,135 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network, the physical isolation type is not BCF_SEGMENT
> 2017-02-17 15:24:36,136 DEBUG [o.a.c.n.c.m.ContrailGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,137 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-144:ctx-b2cdad73) (logid:eb129204) Seq
> 179-6955246674520311671: Response Received:
> 2017-02-17 15:24:36,137 DEBUG [c.c.a.t.Request] (StatsCollector-5:ctx-4298a591)
> (logid:eb129204) Seq 179-6955246674520311671: Received:  { Ans: , MgmtId:
> 345049101620, via: 179(ewcstack-vh003-test), Ver: v1, Flags: 10, {
> GetStorageStatsAnswer } }
> 2017-02-17 15:24:36,137 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) design called
> 2017-02-17 15:24:36,138 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru]
> (StatsCollector-5:ctx-4298a591) (logid:eb129204)
> getCommandHostDelegation: class com.cloud.agent.api.GetStorageStatsCommand
> 2017-02-17 15:24:36,138 DEBUG [c.c.h.XenServerGuru] (StatsCollector-5:ctx-4298a591)
> (logid:eb129204) getCommandHostDelegation: class com.cloud.agent.api.
> GetStorageStatsCommand
> 2017-02-17 15:24:36,139 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network, the physical isolation type is not MIDO
> 2017-02-17 15:24:36,139 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-72:ctx-656a03ae) (logid:dd7ada9e) Seq 217-8596245788743434945:
> Executing request
> 2017-02-17 15:24:36,141 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,142 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,144 DEBUG [c.c.n.g.OvsGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,163 DEBUG [o.a.c.n.g.SspGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) SSP not
> configured to be active
> 2017-02-17 15:24:36,164 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,165 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design network using network offering 54 on physical network 200
> 2017-02-17 15:24:36,166 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Releasing
> lock for Acct[3426fb73-70ad-47d9-9c5d-355f34891438-fen]
> 2017-02-17 15:24:36,188 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) ===END===
> 192.168.252.76 -- GET  command=createNetwork&
> response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&
> name=net-kvm008&displayText=net-kvm00
>
>
> We do not use BigSwitch or anything like this, just plain Openvswitch with
> Ubuntu 16.04. Any idea whats going on?
>
> All the best,
> Florian
>
> EveryWare AG
> Florian Engelmann
> Systems Engineer
> Zurlindenstrasse 52a
> CH-8003 Zürich
>
> T  +41 44 466 60 00
> F  +41 44 466 60 10
>
> florian.engelmann@everyware.ch
> www.everyware.ch
>



--
Rafael Weingärtner

Re: Ubuntu 16.04, Openvswitch networking issue

Posted by Engelmann Florian <fl...@everyware.ch>.
Hi,

this behavior was caused by the following setting:

system.vm.default.hypervisor = Xenserver

After setting this global parameter to NULL we are able to deploy SystemVMs (virtual router) on KVM.

Sad to say, we are no more able to deploy SystemVMs on Xenserver since we changed the parameter?!?!

Allocating the VR with id=4213 in datacenter com.cloud.dc.DataCenterVO$$EnhancerByCGLIB$$6fda4e4f@2 with the hypervisor type KVM
[...]
VM state transitted from :Starting to Stopped with event: OperationFailedvm's original host id: null new host id: null host id before state transition: null


Is anybody able to point me in the direction where to find the logic (on Github) behind how ACS decides which Hypervisor should be used to deploy a VirtualRouter SystemVM? Why is KVM chosen?

All the best,
Florian



________________________________________
From: Engelmann Florian
Sent: Monday, February 20, 2017 5:25 PM
To: users@cloudstack.apache.org
Subject: Re: Ubuntu 16.04, Openvswitch networking issue

Hi Rafael,

We do use the following setup (Test environment currently):

ACS 4.9.2
1x Xenserver 6.5 Cluster (3 nodes)
1x Xenserver 7.0 Cluster (1 node)
1x Ubuntu 16.04 KVM Cluster (3 nodes)

Networking = Advanced Zone VPC and Virtual Router

I noticed the error Message was just informational an not the real problem. The problem we got is:

[...]
Allocating the VR with id=4185 in datacenter com.cloud.dc.DataCenterVO$$EnhancerByCGLIB$$caa6c375@2 with the hypervisor type XenServer
[...]
Cluster: 6 has HyperVisorType that does not match the VM, skipping this cluster
[...]

We tried to force ACS to use the KVM systemVM template but for some reason ACS refuses to use that System offering.

Hosts:
Name        ewcstack-vh023-test
Host Tags="kvm"

Primary storage:
Name: ewcstack-vh023-test,Local Storage: Storage Tags="vol-local-kvm"

System offering:
Name  custom-local-sm-kvm
Storage Tags="vol-local-kvm"
Host Tags="kvm"

Network offering:
Name        custom local kvm
System offering="custom-local-sm-kvm"

Disk offering:
Name        custom local kvm
Storage Tags="vol-local-kvm"


Creating a Instance with a network offering "custom-local-sm-kvm" doesn't stop ACS from using a XenServer systemVM template. Why?

All the best,
Florian


________________________________________
From: Rafael Weingärtner <ra...@gmail.com>
Sent: Friday, February 17, 2017 4:08 PM
To: users@cloudstack.apache.org
Subject: Re: Ubuntu 16.04, Openvswitch networking issue

I think we may need more information. ACS version, network deployment type,
and hypervisors?

On Fri, Feb 17, 2017 at 10:02 AM, Engelmann Florian <
florian.engelmann@everyware.ch> wrote:

> Hi,
>
> sorry I ment "I am NOT able to solve"....
>
> ________________________________________
> From: Engelmann Florian <fl...@everyware.ch>
> Sent: Friday, February 17, 2017 3:36 PM
> To: users@cloudstack.apache.org
> Subject: Ubuntu 16.04, Openvswitch networking issue
>
> Hi,
>
> another error I am able to solve:
>
> 2017-02-17 15:24:36,097 DEBUG [c.c.a.ApiServlet] (catalina-exec-26:ctx-
> 30020483) (logid:d303f8ef) ===START===  192.168.252.76 -- GET
> command=createNetwork&response=json&zoneId=e683eeaa-
> 92c9-4651-91b9-165939f9000c&name=net-kvm008&displayText=
> net-kvm008&networkOf
> 2017-02-17 15:24:36,135 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network, the physical isolation type is not BCF_SEGMENT
> 2017-02-17 15:24:36,136 DEBUG [o.a.c.n.c.m.ContrailGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,137 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-144:ctx-b2cdad73) (logid:eb129204) Seq
> 179-6955246674520311671: Response Received:
> 2017-02-17 15:24:36,137 DEBUG [c.c.a.t.Request] (StatsCollector-5:ctx-4298a591)
> (logid:eb129204) Seq 179-6955246674520311671: Received:  { Ans: , MgmtId:
> 345049101620, via: 179(ewcstack-vh003-test), Ver: v1, Flags: 10, {
> GetStorageStatsAnswer } }
> 2017-02-17 15:24:36,137 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) design called
> 2017-02-17 15:24:36,138 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru]
> (StatsCollector-5:ctx-4298a591) (logid:eb129204)
> getCommandHostDelegation: class com.cloud.agent.api.GetStorageStatsCommand
> 2017-02-17 15:24:36,138 DEBUG [c.c.h.XenServerGuru] (StatsCollector-5:ctx-4298a591)
> (logid:eb129204) getCommandHostDelegation: class com.cloud.agent.api.
> GetStorageStatsCommand
> 2017-02-17 15:24:36,139 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network, the physical isolation type is not MIDO
> 2017-02-17 15:24:36,139 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-72:ctx-656a03ae) (logid:dd7ada9e) Seq 217-8596245788743434945:
> Executing request
> 2017-02-17 15:24:36,141 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,142 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,144 DEBUG [c.c.n.g.OvsGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,163 DEBUG [o.a.c.n.g.SspGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) SSP not
> configured to be active
> 2017-02-17 15:24:36,164 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,165 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design network using network offering 54 on physical network 200
> 2017-02-17 15:24:36,166 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Releasing
> lock for Acct[3426fb73-70ad-47d9-9c5d-355f34891438-fen]
> 2017-02-17 15:24:36,188 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) ===END===
> 192.168.252.76 -- GET  command=createNetwork&
> response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&
> name=net-kvm008&displayText=net-kvm00
>
>
> We do not use BigSwitch or anything like this, just plain Openvswitch with
> Ubuntu 16.04. Any idea whats going on?
>
> All the best,
> Florian
>
> EveryWare AG
> Florian Engelmann
> Systems Engineer
> Zurlindenstrasse 52a
> CH-8003 Zürich
>
> T  +41 44 466 60 00
> F  +41 44 466 60 10
>
> florian.engelmann@everyware.ch
> www.everyware.ch
>



--
Rafael Weingärtner

Re: Ubuntu 16.04, Openvswitch networking issue

Posted by Engelmann Florian <fl...@everyware.ch>.
Hi Rafael,

We do use the following setup (Test environment currently):

ACS 4.9.2
1x Xenserver 6.5 Cluster (3 nodes)
1x Xenserver 7.0 Cluster (1 node)
1x Ubuntu 16.04 KVM Cluster (3 nodes)

Networking = Advanced Zone VPC and Virtual Router

I noticed the error Message was just informational an not the real problem. The problem we got is:

[...]
Allocating the VR with id=4185 in datacenter com.cloud.dc.DataCenterVO$$EnhancerByCGLIB$$caa6c375@2 with the hypervisor type XenServer
[...]
Cluster: 6 has HyperVisorType that does not match the VM, skipping this cluster
[...]

We tried to force ACS to use the KVM systemVM template but for some reason ACS refuses to use that System offering.

Hosts:
Name        ewcstack-vh023-test
Host Tags="kvm"

Primary storage:
Name: ewcstack-vh023-test,Local Storage: Storage Tags="vol-local-kvm"

System offering:
Name  custom-local-sm-kvm
Storage Tags="vol-local-kvm"
Host Tags="kvm"

Network offering:
Name        custom local kvm
System offering="custom-local-sm-kvm"

Disk offering:
Name        custom local kvm
Storage Tags="vol-local-kvm"


Creating a Instance with a network offering "custom-local-sm-kvm" doesn't stop ACS from using a XenServer systemVM template. Why?

All the best,
Florian


________________________________________
From: Rafael Weingärtner <ra...@gmail.com>
Sent: Friday, February 17, 2017 4:08 PM
To: users@cloudstack.apache.org
Subject: Re: Ubuntu 16.04, Openvswitch networking issue

I think we may need more information. ACS version, network deployment type,
and hypervisors?

On Fri, Feb 17, 2017 at 10:02 AM, Engelmann Florian <
florian.engelmann@everyware.ch> wrote:

> Hi,
>
> sorry I ment "I am NOT able to solve"....
>
> ________________________________________
> From: Engelmann Florian <fl...@everyware.ch>
> Sent: Friday, February 17, 2017 3:36 PM
> To: users@cloudstack.apache.org
> Subject: Ubuntu 16.04, Openvswitch networking issue
>
> Hi,
>
> another error I am able to solve:
>
> 2017-02-17 15:24:36,097 DEBUG [c.c.a.ApiServlet] (catalina-exec-26:ctx-
> 30020483) (logid:d303f8ef) ===START===  192.168.252.76 -- GET
> command=createNetwork&response=json&zoneId=e683eeaa-
> 92c9-4651-91b9-165939f9000c&name=net-kvm008&displayText=
> net-kvm008&networkOf
> 2017-02-17 15:24:36,135 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network, the physical isolation type is not BCF_SEGMENT
> 2017-02-17 15:24:36,136 DEBUG [o.a.c.n.c.m.ContrailGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,137 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-144:ctx-b2cdad73) (logid:eb129204) Seq
> 179-6955246674520311671: Response Received:
> 2017-02-17 15:24:36,137 DEBUG [c.c.a.t.Request] (StatsCollector-5:ctx-4298a591)
> (logid:eb129204) Seq 179-6955246674520311671: Received:  { Ans: , MgmtId:
> 345049101620, via: 179(ewcstack-vh003-test), Ver: v1, Flags: 10, {
> GetStorageStatsAnswer } }
> 2017-02-17 15:24:36,137 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) design called
> 2017-02-17 15:24:36,138 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru]
> (StatsCollector-5:ctx-4298a591) (logid:eb129204)
> getCommandHostDelegation: class com.cloud.agent.api.GetStorageStatsCommand
> 2017-02-17 15:24:36,138 DEBUG [c.c.h.XenServerGuru] (StatsCollector-5:ctx-4298a591)
> (logid:eb129204) getCommandHostDelegation: class com.cloud.agent.api.
> GetStorageStatsCommand
> 2017-02-17 15:24:36,139 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network, the physical isolation type is not MIDO
> 2017-02-17 15:24:36,139 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-72:ctx-656a03ae) (logid:dd7ada9e) Seq 217-8596245788743434945:
> Executing request
> 2017-02-17 15:24:36,141 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,142 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,144 DEBUG [c.c.n.g.OvsGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,163 DEBUG [o.a.c.n.g.SspGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) SSP not
> configured to be active
> 2017-02-17 15:24:36,164 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,165 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design network using network offering 54 on physical network 200
> 2017-02-17 15:24:36,166 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Releasing
> lock for Acct[3426fb73-70ad-47d9-9c5d-355f34891438-fen]
> 2017-02-17 15:24:36,188 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) ===END===
> 192.168.252.76 -- GET  command=createNetwork&
> response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&
> name=net-kvm008&displayText=net-kvm00
>
>
> We do not use BigSwitch or anything like this, just plain Openvswitch with
> Ubuntu 16.04. Any idea whats going on?
>
> All the best,
> Florian
>
> EveryWare AG
> Florian Engelmann
> Systems Engineer
> Zurlindenstrasse 52a
> CH-8003 Zürich
>
> T  +41 44 466 60 00
> F  +41 44 466 60 10
>
> florian.engelmann@everyware.ch
> www.everyware.ch
>



--
Rafael Weingärtner

Re: Ubuntu 16.04, Openvswitch networking issue

Posted by Rafael Weingärtner <ra...@gmail.com>.
I think we may need more information. ACS version, network deployment type,
and hypervisors?

On Fri, Feb 17, 2017 at 10:02 AM, Engelmann Florian <
florian.engelmann@everyware.ch> wrote:

> Hi,
>
> sorry I ment "I am NOT able to solve"....
>
> ________________________________________
> From: Engelmann Florian <fl...@everyware.ch>
> Sent: Friday, February 17, 2017 3:36 PM
> To: users@cloudstack.apache.org
> Subject: Ubuntu 16.04, Openvswitch networking issue
>
> Hi,
>
> another error I am able to solve:
>
> 2017-02-17 15:24:36,097 DEBUG [c.c.a.ApiServlet] (catalina-exec-26:ctx-
> 30020483) (logid:d303f8ef) ===START===  192.168.252.76 -- GET
> command=createNetwork&response=json&zoneId=e683eeaa-
> 92c9-4651-91b9-165939f9000c&name=net-kvm008&displayText=
> net-kvm008&networkOf
> 2017-02-17 15:24:36,135 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network, the physical isolation type is not BCF_SEGMENT
> 2017-02-17 15:24:36,136 DEBUG [o.a.c.n.c.m.ContrailGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,137 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-144:ctx-b2cdad73) (logid:eb129204) Seq
> 179-6955246674520311671: Response Received:
> 2017-02-17 15:24:36,137 DEBUG [c.c.a.t.Request] (StatsCollector-5:ctx-4298a591)
> (logid:eb129204) Seq 179-6955246674520311671: Received:  { Ans: , MgmtId:
> 345049101620, via: 179(ewcstack-vh003-test), Ver: v1, Flags: 10, {
> GetStorageStatsAnswer } }
> 2017-02-17 15:24:36,137 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) design called
> 2017-02-17 15:24:36,138 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru]
> (StatsCollector-5:ctx-4298a591) (logid:eb129204)
> getCommandHostDelegation: class com.cloud.agent.api.GetStorageStatsCommand
> 2017-02-17 15:24:36,138 DEBUG [c.c.h.XenServerGuru] (StatsCollector-5:ctx-4298a591)
> (logid:eb129204) getCommandHostDelegation: class com.cloud.agent.api.
> GetStorageStatsCommand
> 2017-02-17 15:24:36,139 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network, the physical isolation type is not MIDO
> 2017-02-17 15:24:36,139 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-72:ctx-656a03ae) (logid:dd7ada9e) Seq 217-8596245788743434945:
> Executing request
> 2017-02-17 15:24:36,141 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,142 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,144 DEBUG [c.c.n.g.OvsGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,163 DEBUG [o.a.c.n.g.SspGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) SSP not
> configured to be active
> 2017-02-17 15:24:36,164 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,165 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design network using network offering 54 on physical network 200
> 2017-02-17 15:24:36,166 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Releasing
> lock for Acct[3426fb73-70ad-47d9-9c5d-355f34891438-fen]
> 2017-02-17 15:24:36,188 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) ===END===
> 192.168.252.76 -- GET  command=createNetwork&
> response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&
> name=net-kvm008&displayText=net-kvm00
>
>
> We do not use BigSwitch or anything like this, just plain Openvswitch with
> Ubuntu 16.04. Any idea whats going on?
>
> All the best,
> Florian
>
> EveryWare AG
> Florian Engelmann
> Systems Engineer
> Zurlindenstrasse 52a
> CH-8003 Zürich
>
> T  +41 44 466 60 00
> F  +41 44 466 60 10
>
> florian.engelmann@everyware.ch
> www.everyware.ch
>



-- 
Rafael Weingärtner

Re: Ubuntu 16.04, Openvswitch networking issue

Posted by Engelmann Florian <fl...@everyware.ch>.
Hi,

sorry I ment "I am NOT able to solve"....

________________________________________
From: Engelmann Florian <fl...@everyware.ch>
Sent: Friday, February 17, 2017 3:36 PM
To: users@cloudstack.apache.org
Subject: Ubuntu 16.04, Openvswitch networking issue

Hi,

another error I am able to solve:

2017-02-17 15:24:36,097 DEBUG [c.c.a.ApiServlet] (catalina-exec-26:ctx-30020483) (logid:d303f8ef) ===START===  192.168.252.76 -- GET  command=createNetwork&response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&name=net-kvm008&displayText=net-kvm008&networkOf
2017-02-17 15:24:36,135 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network, the physical isolation type is not BCF_SEGMENT
2017-02-17 15:24:36,136 DEBUG [o.a.c.n.c.m.ContrailGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network
2017-02-17 15:24:36,137 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-144:ctx-b2cdad73) (logid:eb129204) Seq 179-6955246674520311671: Response Received:
2017-02-17 15:24:36,137 DEBUG [c.c.a.t.Request] (StatsCollector-5:ctx-4298a591) (logid:eb129204) Seq 179-6955246674520311671: Received:  { Ans: , MgmtId: 345049101620, via: 179(ewcstack-vh003-test), Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
2017-02-17 15:24:36,137 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) design called
2017-02-17 15:24:36,138 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru] (StatsCollector-5:ctx-4298a591) (logid:eb129204) getCommandHostDelegation: class com.cloud.agent.api.GetStorageStatsCommand
2017-02-17 15:24:36,138 DEBUG [c.c.h.XenServerGuru] (StatsCollector-5:ctx-4298a591) (logid:eb129204) getCommandHostDelegation: class com.cloud.agent.api.GetStorageStatsCommand
2017-02-17 15:24:36,139 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network, the physical isolation type is not MIDO
2017-02-17 15:24:36,139 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-72:ctx-656a03ae) (logid:dd7ada9e) Seq 217-8596245788743434945: Executing request
2017-02-17 15:24:36,141 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network
2017-02-17 15:24:36,142 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network
2017-02-17 15:24:36,144 DEBUG [c.c.n.g.OvsGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network
2017-02-17 15:24:36,163 DEBUG [o.a.c.n.g.SspGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) SSP not configured to be active
2017-02-17 15:24:36,164 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network
2017-02-17 15:24:36,165 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design network using network offering 54 on physical network 200
2017-02-17 15:24:36,166 DEBUG [o.a.c.e.o.NetworkOrchestrator] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Releasing lock for Acct[3426fb73-70ad-47d9-9c5d-355f34891438-fen]
2017-02-17 15:24:36,188 DEBUG [c.c.a.ApiServlet] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) ===END===  192.168.252.76 -- GET  command=createNetwork&response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&name=net-kvm008&displayText=net-kvm00


We do not use BigSwitch or anything like this, just plain Openvswitch with Ubuntu 16.04. Any idea whats going on?

All the best,
Florian

EveryWare AG
Florian Engelmann
Systems Engineer
Zurlindenstrasse 52a
CH-8003 Zürich

T  +41 44 466 60 00
F  +41 44 466 60 10

florian.engelmann@everyware.ch
www.everyware.ch

Re: Ubuntu 16.04, Openvswitch networking issue

Posted by Tim Mackey <tm...@gmail.com>.
In order to use OVS, you need both the virtual switch and the control
plane. Those messages largely boil down to "We can't find an appropriate
control plane for your chosen network topology and hypervisor." This then
raises the questions of which control plane are you attempting to use, and
which hypervisor. Here's a deck[1] I prepared for CloudStack 4.5 which
outlines the impact of hypervisor choices. Slide 15 is most relevant to
your problem. If you have a supported control plane, then its likely
misconfigured and CloudStack doesn't know how to talk to it. Newer
CloudStack versions will vary of course, but the principles are the same,
plus you didn't mention your version ;).

[1]
https://www.slideshare.net/TimMackey/selecting-the-correct-hypervisor-for-cloudstack-45

-tim

On Fri, Feb 17, 2017 at 9:36 AM, Engelmann Florian <
florian.engelmann@everyware.ch> wrote:

> Hi,
>
> another error I am able to solve:
>
> 2017-02-17 15:24:36,097 DEBUG [c.c.a.ApiServlet] (catalina-exec-26:ctx-30020483)
> (logid:d303f8ef) ===START===  192.168.252.76 -- GET  command=createNetwork&
> response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&
> name=net-kvm008&displayText=net-kvm008&networkOf
> 2017-02-17 15:24:36,135 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network, the physical isolation type is not BCF_SEGMENT
> 2017-02-17 15:24:36,136 DEBUG [o.a.c.n.c.m.ContrailGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,137 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-144:ctx-b2cdad73) (logid:eb129204) Seq
> 179-6955246674520311671: Response Received:
> 2017-02-17 15:24:36,137 DEBUG [c.c.a.t.Request] (StatsCollector-5:ctx-4298a591)
> (logid:eb129204) Seq 179-6955246674520311671: Received:  { Ans: , MgmtId:
> 345049101620, via: 179(ewcstack-vh003-test), Ver: v1, Flags: 10, {
> GetStorageStatsAnswer } }
> 2017-02-17 15:24:36,137 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) design called
> 2017-02-17 15:24:36,138 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru]
> (StatsCollector-5:ctx-4298a591) (logid:eb129204)
> getCommandHostDelegation: class com.cloud.agent.api.GetStorageStatsCommand
> 2017-02-17 15:24:36,138 DEBUG [c.c.h.XenServerGuru] (StatsCollector-5:ctx-4298a591)
> (logid:eb129204) getCommandHostDelegation: class com.cloud.agent.api.
> GetStorageStatsCommand
> 2017-02-17 15:24:36,139 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network, the physical isolation type is not MIDO
> 2017-02-17 15:24:36,139 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-72:ctx-656a03ae) (logid:dd7ada9e) Seq 217-8596245788743434945:
> Executing request
> 2017-02-17 15:24:36,141 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,142 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,144 DEBUG [c.c.n.g.OvsGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,163 DEBUG [o.a.c.n.g.SspGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) SSP not
> configured to be active
> 2017-02-17 15:24:36,164 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design this network
> 2017-02-17 15:24:36,165 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to
> design network using network offering 54 on physical network 200
> 2017-02-17 15:24:36,166 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Releasing
> lock for Acct[3426fb73-70ad-47d9-9c5d-355f34891438-fen]
> 2017-02-17 15:24:36,188 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) ===END===
> 192.168.252.76 -- GET  command=createNetwork&
> response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&
> name=net-kvm008&displayText=net-kvm00
>
>
> We do not use BigSwitch or anything like this, just plain Openvswitch with
> Ubuntu 16.04. Any idea whats going on?
>
> All the best,
> Florian
>
> EveryWare AG
> Florian Engelmann
> Systems Engineer
> Zurlindenstrasse 52a
> CH-8003 Zürich
>
> T  +41 44 466 60 00
> F  +41 44 466 60 10
>
> florian.engelmann@everyware.ch
> www.everyware.ch

Ubuntu 16.04, Openvswitch networking issue

Posted by Engelmann Florian <fl...@everyware.ch>.
Hi,

another error I am able to solve:

2017-02-17 15:24:36,097 DEBUG [c.c.a.ApiServlet] (catalina-exec-26:ctx-30020483) (logid:d303f8ef) ===START===  192.168.252.76 -- GET  command=createNetwork&response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&name=net-kvm008&displayText=net-kvm008&networkOf
2017-02-17 15:24:36,135 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network, the physical isolation type is not BCF_SEGMENT
2017-02-17 15:24:36,136 DEBUG [o.a.c.n.c.m.ContrailGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network
2017-02-17 15:24:36,137 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-144:ctx-b2cdad73) (logid:eb129204) Seq 179-6955246674520311671: Response Received: 
2017-02-17 15:24:36,137 DEBUG [c.c.a.t.Request] (StatsCollector-5:ctx-4298a591) (logid:eb129204) Seq 179-6955246674520311671: Received:  { Ans: , MgmtId: 345049101620, via: 179(ewcstack-vh003-test), Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
2017-02-17 15:24:36,137 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) design called
2017-02-17 15:24:36,138 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru] (StatsCollector-5:ctx-4298a591) (logid:eb129204) getCommandHostDelegation: class com.cloud.agent.api.GetStorageStatsCommand
2017-02-17 15:24:36,138 DEBUG [c.c.h.XenServerGuru] (StatsCollector-5:ctx-4298a591) (logid:eb129204) getCommandHostDelegation: class com.cloud.agent.api.GetStorageStatsCommand
2017-02-17 15:24:36,139 DEBUG [c.c.n.g.MidoNetGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network, the physical isolation type is not MIDO
2017-02-17 15:24:36,139 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-72:ctx-656a03ae) (logid:dd7ada9e) Seq 217-8596245788743434945: Executing request
2017-02-17 15:24:36,141 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network
2017-02-17 15:24:36,142 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network
2017-02-17 15:24:36,144 DEBUG [c.c.n.g.OvsGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network
2017-02-17 15:24:36,163 DEBUG [o.a.c.n.g.SspGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) SSP not configured to be active
2017-02-17 15:24:36,164 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design this network
2017-02-17 15:24:36,165 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Refusing to design network using network offering 54 on physical network 200
2017-02-17 15:24:36,166 DEBUG [o.a.c.e.o.NetworkOrchestrator] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) Releasing lock for Acct[3426fb73-70ad-47d9-9c5d-355f34891438-fen]
2017-02-17 15:24:36,188 DEBUG [c.c.a.ApiServlet] (catalina-exec-26:ctx-30020483 ctx-430b6ae1) (logid:d303f8ef) ===END===  192.168.252.76 -- GET  command=createNetwork&response=json&zoneId=e683eeaa-92c9-4651-91b9-165939f9000c&name=net-kvm008&displayText=net-kvm00


We do not use BigSwitch or anything like this, just plain Openvswitch with Ubuntu 16.04. Any idea whats going on?

All the best,
Florian

EveryWare AG
Florian Engelmann
Systems Engineer
Zurlindenstrasse 52a
CH-8003 Zürich

T  +41 44 466 60 00
F  +41 44 466 60 10

florian.engelmann@everyware.ch
www.everyware.ch