Good suggestion, but same result:

lxc network attach QA-Server-03:vxlan.1101 QA-Server-03:centos-vm4
error: not found


On the remote server (QA-Server-03):
----------------------------------
root@QA-Server-03:~# ip link |grep 1101
4: vxlan.1101: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state 
UNKNOWN mode DEFAULT group default qlen 1000

The network interface is definitely there.



> On Apr 26, 2017, at 4:02 PM, Stéphane Graber <[email protected]> wrote:
> 
> On Wed, Apr 26, 2017 at 03:55:58PM -0400, Ron Kelley wrote:
>> Thanks.  It seems the command works for the local server only.  When I try 
>> to do this from a remote server ("lxc network attach vxlan.1101 
>> QA-Server-04:centos-vm4), I get “error: not found”.  Is that expected?
> 
> Did you try?
> 
>   lxc network attach QA-Server-04:vxlan.1101 QA-Server-04:centos-vm4
> 
> 
>> Also, it seems the command, "lxc network show <remote_server>:” has a bug as 
>> the command returns with “error: json: cannot unmarshal array into Go value 
>> of type api.Network".  I have just filed a bug (#3230) to track this issue.
>> 
>> 
>> 
>> 
>> 
>> 
>>> On Apr 26, 2017, at 3:49 PM, Stéphane Graber <[email protected]> wrote:
>>> 
>>> On Wed, Apr 26, 2017 at 03:37:25PM -0400, Ron Kelley wrote:
>>>> Trying to create a macvlan network type using LXD 2.12 but can’t figure 
>>>> out the syntax.  I have a number of vxlan interfaces created via the “ip 
>>>> link” command and would like to create the corresponding LXD networks 
>>>> without having to create separate profiles.  I tried the commands "lxc 
>>>> network create vxlan1101 type=physical” and "lxc network create vxlan1101 
>>>> nictype=macvlan”.  Each time, I get "error: Invalid network configuration 
>>>> key:”
>>>> 
>>>> I looked at the network configuration document 
>>>> (https://github.com/lxc/lxd/blob/master/doc/networks.md) but don’t see 
>>>> anywhere to specify a nic type.
>>>> 
>>>> For what it’s worth, creating a new profile using the “nictype:macvlan" 
>>>> and "parent: vxlan.1101” key values works just fine.
>>>> 
>>>> 
>>>> Any pointers?
>>> 
>>> LXD only manages bridges. You can make a bridge that's connected to your
>>> macvlan device with:
>>> 
>>> lxc network create br-vxlan1101 ipv4.address=none ipv6.address=none 
>>> bridge.external_interfaces=vxlan.1101
>>> 
>>> Which you can then attach containers to.
>>> 
>>> 
>>> But it sounds like just attaching the container directly using macvlan 
>>> would be easiest:
>>> 
>>> lxc network attach vxlan.1101 <container name>
>>> 
>>> -- 
>>> Stéphane Graber
>>> Ubuntu developer
>>> http://www.ubuntu.com
>>> _______________________________________________
>>> lxc-users mailing list
>>> [email protected]
>>> http://lists.linuxcontainers.org/listinfo/lxc-users
>> 
>> _______________________________________________
>> lxc-users mailing list
>> [email protected]
>> http://lists.linuxcontainers.org/listinfo/lxc-users
> 
> -- 
> Stéphane Graber
> Ubuntu developer
> http://www.ubuntu.com
> _______________________________________________
> lxc-users mailing list
> [email protected]
> http://lists.linuxcontainers.org/listinfo/lxc-users

_______________________________________________
lxc-users mailing list
[email protected]
http://lists.linuxcontainers.org/listinfo/lxc-users

Reply via email to