<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 10pt; color: #000000"><div>Hi Serge </div><div><br></div><div>Thanks for the explantation, really appreciated.</div><div>Multi-tenant support is what I'm looking for here but the way I designed it without thinking in an LXD point of view but more into an LXC point of view . <br>I think many people talking about LXD in fact never did use the daemon if they did not "launch" any containers that way. <br>I came through when I start asked myself questions about the API and live migration . Witch should become really easy in the future using LXD . </div><div><br data-mce-bogus="1"></div><div>Looks like I have a lot of work ahead . </div><div data-marker="__SIG_PRE__"><div><span style="color: rgb(51, 51, 51); font-family: times new roman,new york,times,serif;" data-mce-style="color: #333333; font-family: times new roman,new york,times,serif;"><br data-mce-bogus="1"></span></div><div><span style="color: rgb(51, 51, 51); font-family: times new roman,new york,times,serif;" data-mce-style="color: #333333; font-family: times new roman,new york,times,serif;">Cordialement,</span><span style="color: rgb(51, 51, 51); font-family: times new roman,new york,times,serif; font-weight: bold;" data-mce-style="color: #333333; font-family: times new roman,new york,times,serif; font-weight: bold;"><span style="color: rgb(51, 51, 51); font-family: times new roman,new york,times,serif; font-weight: bold;" data-mce-style="color: #333333; font-family: times new roman,new york,times,serif; font-weight: bold;"><br></span></span></div><div><br></div><div><span style="color: rgb(51, 51, 51); font-family: times new roman,new york,times,serif; font-weight: bold;" data-mce-style="color: #333333; font-family: times new roman,new york,times,serif; font-weight: bold;">Benoît </span><span style="color: rgb(51, 51, 51); font-family: times new roman,new york,times,serif; font-weight: bold;" data-mce-style="color: #333333; font-family: times new roman,new york,times,serif; font-weight: bold;"><br></span></div></div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>De: </b>"Serge Hallyn" <serge.hallyn@ubuntu.com><br><b>À: </b>"lxc-users" <lxc-users@lists.linuxcontainers.org><br><b>Envoyé: </b>Mardi 1 Mars 2016 13:55:20<br><b>Objet: </b>Re: [lxc-users] lxc / lxd I'm lost somewhere<br></div><div><br></div><div data-marker="__QUOTED_TEXT__">Quoting Benoit GEORGELIN - Association Web4all (benoit.georgelin@web4all.fr):<br>> Hi Serge, <br>> <br>> Thanks for your input. <br>> I still don't understand how I can manage the equivalent to create a container using LXD instant of lxc-create. <br>> <br>> My goal is just to create a container with a permanent existence . <br>> To me, lxc launch is only for volatile containers, a bit more like a docker container <br><br>Why is that?<br><br>lxc launch is just lxc init && lxc start. The container sticks around<br>until you lxc delete it.<br><br>> I'll try to understand more how I should work with LXD instant of only LXC . I understand all the capabilities of LXD but I misunderstand how I can just do what i am doing right now : <br>> <br>> - Create a dedicated système user (unpriv container) <br><br>lxc init imagelias containername<br><br>> - Apply a specific lxc.config file <br><br>lxc config edit containername<br><br>> - Create a new rootfs with LVM or BTRFS <br><br>You do need to choose whether you're using lvm, btrfs, zfs, or<br>just a regular rootfs as backing store, although you could<br>run 4 different lxd instances each with different backing<br>store, all on the same host, if you wanted.<br><br>> - Create a new container like this <br>> lxc-create -n test -t ubuntu -B lvm --lvname test --vgname vg_node1 --fstype ext4 --fssize 1GB <br>> <br>> So the specific user will have his own container . <br>> <br>> User A will have his own space for containers <br>> User B will have his own space for containers <br><br>The real support for segratated lxc users (multi-tenant support) is not<br>yet there. And at the moment, giving user A the ability to use the lxd<br>remote on host X (meaning, full ability to configure the containers and<br>devices there) means that user A is effectively root on host X.<br><br>> They should do "lxc-ls -f" or "lxc list" and see only their own containers <br>> <br>> Maybe this is not a typical use case ? <br><br>I'm hoping we can focus on multi-tenant support as a design goal after<br>the 2.0 release. But with lxd being remote based, the idea really is<br>that A and B can both have accounts on host H1, with lxd remotes running<br>on host H2 for user A and H3 for user B, and their lxc client configured<br>to use the appropriate remotes. (where H2 and H3 can of course just be<br>VMs on H1, or truly remote). So whereas lxc was host-based, i.e. I<br>create and use containers on the host I'm logged in on, lxd is<br>remote-based and it doesn't really matter where things are.<br><br>For instance I have my local laptop and a (very) remote server. I<br>can 'lxc launch xenial h:x1; lxc file push my.tar.gz h:x1/; lxc<br>shell h:x1' and the fact that x1 is running on 'h' on a different<br>continent really doesn't matter a lick. it's the same thing I'd<br>do locally - 'lxc launch xenial x1; lxc file push my.tar.gz x1;<br>lxc shell x1'.<br><br>-serge<br>_______________________________________________<br>lxc-users mailing list<br>lxc-users@lists.linuxcontainers.org<br>http://lists.linuxcontainers.org/listinfo/lxc-users<br></div></div></body></html>