<div dir="ltr">Hi Stefan,<div><br></div><div>On Wed, Feb 5, 2014 at 3:26 PM, Stefan Kooman <span dir="ltr"><<a href="mailto:stefan@bit.nl" target="_blank">stefan@bit.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div>Quoting Carlos Martín Sánchez (<a href="mailto:cmartin@opennebula.org" target="_blank">cmartin@opennebula.org</a>):<br></div></blockquote><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div></div><div>> In future versions, we may change this and allow to select more than one<br>> cluster for each host/vnet/ds...<br><br></div>I thought this was already possible but I must be mistaken with sharing<br>
resources between VDC / oZones. Did Ruben create #2591 for this [1]?<br></blockquote></div><div><br></div><div>Yes, that ticket is for this functionality.</div><div><br></div><div>In 4.4, different oZones VDCs can use the same resources. But don't get too attached to the VDCs, they will be merged with the existing groups in the core. See this section of the dev docs for more info [1].</div>
<div><br></div><div>Regards</div><div><br></div><div>[1] <a href="https://github.com/OpenNebula/docs/blob/master/source/administration/users_and_groups/manage_users.rst#managing-resource-provider-within-groups" target="_blank">https://github.com/OpenNebula/docs/blob/master/source/administration/users_and_groups/manage_users.rst#managing-resource-provider-within-groups</a><br>
</div><div class="gmail_extra"><br clear="all"><div><div dir="ltr">--<br><div>Carlos Martín, MSc<br>Project Engineer</div><div>OpenNebula - Flexible Enterprise Cloud Made Simple<br><div><span style="border-collapse:collapse;color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:cmartin@opennebula.org" target="_blank">cmartin@opennebula.org</a> | <a href="http://twitter.com/opennebula" target="_blank">@OpenNebula</a></span><span style="border-collapse:collapse;color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"><a href="mailto:cmartin@opennebula.org" style="color:rgb(42,93,176)" target="_blank"></a></span></div>
</div></div></div>
<br><br><div class="gmail_quote">On Wed, Feb 5, 2014 at 3:26 PM, Stefan Kooman <span dir="ltr"><<a href="mailto:stefan@bit.nl" target="_blank">stefan@bit.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div>Quoting Carlos Martín Sánchez (<a href="mailto:cmartin@opennebula.org" target="_blank">cmartin@opennebula.org</a>):<br>
><br>
> You can create vnets directly in a cluster, using the --cluster option [1],<br>
> but not with the CLUSTER attribute [2].<br>
> I agree that since the new vnet is defined with a template, it is more<br>
> intuitive to set the cluster also there, so I've opened a ticket for this<br>
> [3].<br>
<br>
</div>Thanks.<br>
<div><br>
><br>
> This is a bit hard to explain easily in the docs, but the key is this<br>
> paragraph [4]:<br>
><br>
> Virtual Machines using resources from Datastores or Virtual Networks in the<br>
> Cluster 'none' can be deployed in any Host, which must be properly<br>
> configured.<br>
><br>
> That is, your vnet is not in any cluster (or cluster 'none'), which means<br>
> that all hosts (either in cluster none or any other cluster) will be able<br>
> to deploy the VM.<br>
> The core sees that you are requesting something specific to cluster<br>
> kvm_cluster and a vnet that is configured to be used by any Host, including<br>
> those in kvm_cluster.<br>
><br>
> If you try to create a VM using resources from two different clusters, the<br>
> core will complain on creation, it won't wait for the scheduler to notice.<br>
><br>
><br>
> This may be a bit convoluted, but the other option we had was to force you<br>
> to put everything in a cluster. That would mean that you can't configure a<br>
> network to be used by both xen and kvm hosts.<br>
<br>
</div>It makes perfect sense.<br>
<div><br>
> In future versions, we may change this and allow to select more than one<br>
> cluster for each host/vnet/ds...<br>
<br>
</div>I thought this was already possible but I must be mistaken with sharing<br>
resources between VDC / oZones. Did Ruben create #2591 for this [1]?<br>
<br>
Thanks for your explanation.<br>
<br>
Gr. Stefan<br>
<br>
[1]: <a href="http://dev.opennebula.org/issues/2591" target="_blank">http://dev.opennebula.org/issues/2591</a><br>
<div><div><br>
--<br>
| BIT BV <a href="http://www.bit.nl/" target="_blank">http://www.bit.nl/</a> Kamer van Koophandel 09090351<br>
| GPG: 0xD14839C6 <a href="tel:%2B31%20318%20648%20688" value="+31318648688" target="_blank">+31 318 648 688</a> / <a href="mailto:info@bit.nl" target="_blank">info@bit.nl</a><br>
</div></div></blockquote></div><br></div></div>