<div dir="ltr">Hi Stefan,<div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 30, 2014 at 9:18 AM, 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">Hi,<br>
<br>
I created a new vnet based on the following template:<br>
<br>
--- template start ---<br>
NAME = "v-test01"<br>
TYPE = "ranged"<br>
BRIDGE = "uplink"<br>
CLUSTER = "kvm_cluster"<br>
<br>
NETWORK_ADDRESS = 172.17.226.0<br>
NETWORK_MASK = 255.255.255.224<br>
IP_START = 172.17.226.4<br>
IP_END = 172.17.226.30<br>
<br>
GATEWAY = 172.17.226.1<br>
<br>
VLAN = "YES"<br>
VLAN_ID = 226<br>
--- template end ---<br>
<br>
After creation the vnet is not a member of the kvm_cluster but instead<br>
of the default cluster "-". Is this a bug or is it me doing it wrong?<br>
After reading [1] again it explicitly states a "vnet or datastore"<br>
should be added with the onecluster add command, so I was doing it<br>
wrong. It still would be nice to have it automatically added to a<br>
cluster if "CLUSTER" attribute is there.<br></blockquote><div><br></div><div>You can create vnets directly in a cluster, using the --cluster option [1], but not with the CLUSTER attribute [2].</div><div>I agree that since the new vnet is defined with a template, it is more intuitive to set the cluster also there, so I've opened a ticket for this [3].</div>
<div> <br></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">
After that I instantiated a vm based on a template with a mix of<br>
resources from "kvm_cluster" and "-" (v-test01). This vm succesfully<br>
managed to get into running state. According to [1] section "The Default<br>
Cluster 'None'" hosts in the Cluster 'none' will only run VMs using<br>
resources without a cluster. I assume this is equally true for hosts<br>
that are a member of a non-default cluster (kvm_cluster in our case) but<br>
instead it did run the vm. Indeed, according to "The "Scheduling and<br>
Cluster" section of [1] the deployment should have failed. What info do<br>
we need to make sure it's a bug and not PEBKAC?<br>
<br>
Gr. Stefan<br>
<br>
[1]:<br>
<a href="http://docs.opennebula.org/4.4/administration/hosts_and_clusters/cluster_guide.html" target="_blank">http://docs.opennebula.org/4.4/administration/hosts_and_clusters/cluster_guide.html</a></blockquote><div><br></div>
<div>This is a bit hard to explain easily in the docs, but the key is this paragraph [4]:</div><div><br></div><div><div>Virtual Machines using resources from Datastores or Virtual Networks in the Cluster ‘none’ can be deployed in any Host, which must be properly configured.</div>
<div><br></div></div><div>That is, your vnet is not in any cluster (or cluster 'none'), which means that all hosts (either in cluster none or any other cluster) will be able to deploy the VM.</div><div>The core sees that you are requesting something specific to cluster kvm_cluster and a vnet that is configured to be used by any Host, including those in kvm_cluster.</div>
<div><br></div><div>If you try to create a VM using resources from two different clusters, the core will complain on creation, it won't wait for the scheduler to notice.</div><div><br></div><div><br></div><div>This may be a bit convoluted, but the other option we had was to force you to put everything in a cluster. That would mean that you can't configure a network to be used by both xen and kvm hosts.</div>
<div>In future versions, we may change this and allow to select more than one cluster for each host/vnet/ds... </div><div><br></div><div>Regards</div><div class="gmail_quote"><br></div><div class="gmail_quote">[1] <a href="http://docs.opennebula.org/doc/4.4/cli/onevnet.1.html">http://docs.opennebula.org/doc/4.4/cli/onevnet.1.html</a><br>
</div>[2] <a href="http://docs.opennebula.org/4.4/user/references/vnet_template.html">http://docs.opennebula.org/4.4/user/references/vnet_template.html</a></div><div class="gmail_quote">[3] <a href="http://dev.opennebula.org/issues/2698">http://dev.opennebula.org/issues/2698</a></div>
<div class="gmail_quote">[4] <a href="http://docs.opennebula.org/4.4/administration/hosts_and_clusters/cluster_guide.html#the-default-cluster-none">http://docs.opennebula.org/4.4/administration/hosts_and_clusters/cluster_guide.html#the-default-cluster-none</a><br class="">
--<br><div>Carlos Martín, MSc<br>Project Engineer</div><div>OpenNebula - Flexible Enterprise Cloud Made Simple<br></div><div><a href="http://www.opennebula.org/" target="_blank" style="font-family:arial,sans-serif;font-size:13px">www.OpenNebula.org</a><span style="color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"> </span><span style="color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px">|</span><span style="color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"> </span><a href="mailto:cmartin@opennebula.org" target="_blank" style="font-family:arial,sans-serif;font-size:13px">cmartin@opennebula.org</a><span style="color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"> </span><span style="color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px">|</span><span style="color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"> </span><a href="http://twitter.com/opennebula" target="_blank" style="font-family:arial,sans-serif;font-size:13px">@OpenNebula</a> </div>
</div><br></div></div>