<div dir="ltr"><div class="gmail_extra">On Wed, Nov 25, 2015 at 3:50 PM, Serge Hallyn <span dir="ltr"><<a href="mailto:serge.hallyn@ubuntu.com" target="_blank">serge.hallyn@ubuntu.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Quoting Dilvan Moreira (<a href="mailto:dilvan@gmail.com">dilvan@gmail.com</a>):<br></span>> 1.<br><span class="">> Is there a way to pass a block volume (Ceph/rbd) or folder to a LXD VM,<br>
<br>
</span>You can just have your scripts mount the volume/folder to<br>
/var/lib/lxd/containers/container/rootfs. You can set<br>
lxc.rootfs= in the raw.lxc.</blockquote><div><br></div><div> Where this raw.lxc file is located (Can I have one for each VM)? In any case, that doesn’t solve my problem. I cannot just start a VM from another machine (as I can do now), I will have to copy the metadata.yam file and templates folder. Don’t they change over time? Is it safe to copy them just after the container is created?</div><div> </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Or you can wait for<br>
<br>
<a href="https://github.com/lxc/lxc/pull/670" rel="noreferrer" target="_blank">https://github.com/lxc/lxc/pull/670</a><br>
<br>
Once that gets into lxc, I've not thought through whether you'll need<br>
any specific support from lxd.<br>
<br>
I think what you're doing now makes a lot of sense - the only shortcoming<br>
is that live migration may be complicated because of the shared rootfs.<br>
<br>
Note that Guido (cc:d) is also doing a similar setup (using NFS).<br>
<span class=""><br>
> so LXD itself would mount the root folder (/)? It would be nice to have<br>
> a block volume for each VM (and not all VMs using the same folder).<br>
</span>> 2.<br>
<span class="">><br>
> Is there a simpler solution than OpenStack for my use case (or a simpler<br>
> installation procedure for OpenStack)?<br>
<br>
</span>imho juju is the simplest way to install openstack.<br></blockquote><div><br></div><div> In all examples I found of juju installing OpenStack (I don’t know much about juju), it was using a set of VMs or MaaS (Metal as a Service). VMs would be pointless in my case and MaaS is very complicated to implement (and not very useful in my case). Can I use juju in real bare metal? If so, can you point me to some example/documentation?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> 3.<br>
<span class="">><br>
> Ultimately, I would like my cluster to have the ability to schedule VMs<br>
> to nodes, move VMs from failed nodes, etc. Any suggestions on how to get<br>
> that?<br>
<br>
</span>The biggest complication I see is that when you ask lxd to move a container,<br>
lxd will want to migrate the rootfs. I'm waiting for clarification from<br>
Tycho on whether lxd will be smart enough to DTRT.<br></blockquote><div><br></div><div> Using Ceph/rbd, there is no need to migrate anything. I am not aiming to have live migration, so the plan is to shutdown the container and start it agin in another node.</div><div><br></div><div>Cheers,</div><div><br></div><div>Dilvan.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
lxc-users mailing list<br>
<a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
<a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a></div></div></blockquote></div><br></div></div>