So I'll just give an update regarding this:
Finally I was able to add my vswitch (xenbr0) to my open flow controller (floodlight:IP 192.168.1.250, URL:
http://192.168.1.250:8080/ui/index.html) by doing this:
Xe network-list
ovs-vsctl set-controller xenbr0
tcp:192.168.1.250:6633
My problem now is that I can't see any private vswitch and I try to do the same :
ovs-vsctl set-controller xapi0 tcp:192.168.1.250:6633
I get this error message: "ovs-vsctl: no bridge named xapi"
So my question is: are the vswitch declared as private (not bridged or external) not managed by openflow controllers, I mean does XCP support having openflow controllers on private/internal vswitches?
Thanks
Date: Sun, 21 Apr 2013 21:14:32 -0400
Subject: Re: [Xen-API] Setup vswitches in XCP 1.6
From: seriuomnis@xxxxxxxxx
To: benkhellat_samir@xxxxxxxxxxx
CC: xen-api@xxxxxxxxxxxxx
AFAIK, the xe-network commands are frontends for switches created via openvswitch. So to answer your first question, it seems to be just create networks.
From some Citrix documentation (that I have since misplaced, if memory serves it was their xenserver administration guide, though not the 6.1 one), it showed the physical NIC being connected up to a 'network' object which was a switch created via openvswitch, from there, all the guest virtual NICs connected up to that switch.
For your second question, I'm afraid I'm not an expert at networking, but I hope the first answer can help