Re: [Xen-API] XCP and network interfaces

[Rob Hoes <Rob.Hoes@xxxxxxxxxx>]

Hi Christian,

> I posted this question already on xen-lists, but this seems to be the right 
> list.
> 
> I started using XCP (Debian wheezy packages) after I used XEN for several
> years. I have some questions regarding the creation of the networks (I am
> trying to use bridges not openvswitch).
> I have 4 physical network interfaces. They are renamed by udev (intern, dmz,
> san1 and san2) and already assigned to bridges (br0 to br3).
> 
> I want to use the same bridges in XCP, but XCP ignores these bridges and
> tries to create own bridges for every physical interface. This does not work,
> because the physical interface is already assigned to a bridge.
> 
> How can I use an already existing bridge (that is not named xenbr0, if this is
> relevant) in XCP?

Unfortunately, you can't at the moment. Xapi currently assumes that it always 
needs to create its own bridges. There are plans to make this more flexible, so 
that people can manage their own interfaces and bridges (if they would like 
to). 

Cheers,
Rob

> Who creates the pifs and networks in XCP (I assume xcp-networkd)?
> 
> What I want to do is:
> 
> xe network-create name-label=br0 name-description="internal network"
> bridge=br0 This does not work because the bridge param is RO and is
> ignored.
> 
> viki:~# xe pif-list
> uuid ( RO)                  : 070e32e7-da50-78f4-6cfd-0626f1fca089
>               device ( RO): dmz
>   currently-attached ( RO): false
>                 VLAN ( RO): -1
>         network-uuid ( RO): 799946d2-0402-abe9-5010-b4cc975cd26b
> 
> 
> uuid ( RO)                  : 4a123159-f10c-c887-c8a1-5fe17875ad7b
>               device ( RO): intern
>   currently-attached ( RO): false
>                 VLAN ( RO): -1
>         network-uuid ( RO): 73234b34-ae79-6ea0-45c7-2f5180dd2509
> 
> 
> uuid ( RO)                  : 39b6fd14-0077-ce36-d2c2-1157bfa391ea
>               device ( RO): san2
>   currently-attached ( RO): true
>                 VLAN ( RO): -1
>         network-uuid ( RO): 26ada0d6-dbee-87c3-c7c2-dd1e1d0aeedb
> 
> 
> uuid ( RO)                  : 0ec8bba3-ab45-715a-f7fe-e68e737b3fba
>               device ( RO): san1
>   currently-attached ( RO): false
>                 VLAN ( RO): -1
>         network-uuid ( RO): 111d1d5c-ce3f-1d70-960a-41feb3b7c478
> 
> 
> viki:~# xe network-list
> uuid ( RO)                : 111d1d5c-ce3f-1d70-960a-41feb3b7c478
>         name-label ( RW): Pool-wide network associated with san1
>   name-description ( RW):
>             bridge ( RO): brsan1
> 
> 
> uuid ( RO)                : 73234b34-ae79-6ea0-45c7-2f5180dd2509
>         name-label ( RW): Pool-wide network associated with intern
>   name-description ( RW):
>             bridge ( RO): brintern
> 
> 
> uuid ( RO)                : dbf3dcfd-9046-c6a0-ec5e-a39e2239cdcc
>         name-label ( RW): Host internal management network
>   name-description ( RW): Network on which guests will be assigned a
> private link-local IP address which can be used to talk XenAPI
>             bridge ( RO): xenapi
> 
> 
> uuid ( RO)                : 799946d2-0402-abe9-5010-b4cc975cd26b
>         name-label ( RW): Pool-wide network associated with dmz
>   name-description ( RW):
>             bridge ( RO): brdmz
> 
> 
> uuid ( RO)                : 26ada0d6-dbee-87c3-c7c2-dd1e1d0aeedb
>         name-label ( RW): Pool-wide network associated with san2
>   name-description ( RW):
>             bridge ( RO): brsan2
> 
> 
> _______________________________________________
> Xen-api mailing list
> Xen-api@xxxxxxxxxxxxx
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api