Yea I meant you need the cluster mechanism to be extended to general group scheduling, basically you can pick and choose what you want to exclude and include in a group and run the scheduler against that. Currently (group scheduling) defines a group as two mutually exclusive clusters with different hosts and storage.<div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Dec 12, 2012 at 9:17 AM, Gary S. Cuozzo <span dir="ltr"><<a href="mailto:gary@isgsoftware.net" target="_blank">gary@isgsoftware.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div style="font-size:12pt;font-family:arial,helvetica,sans-serif">I could do it via a separate cluster, but it would leave my hosts very under utilized. I think I would also have to create and manage additional datastores and other resources for the new cluster. My preference would be to be able to configure the scheduler.<br>
<br><hr><div style="font-size:12pt;font-style:normal;font-family:Helvetica,Arial,sans-serif;text-decoration:none;font-weight:normal"><b>From: </b>"Shankhadeep Shome" <<a href="mailto:shank15217@gmail.com" target="_blank">shank15217@gmail.com</a>><div class="im">
<br><b>To: </b>"Gary S. Cuozzo" <<a href="mailto:gary@isgsoftware.net" target="_blank">gary@isgsoftware.net</a>><br></div><b>Sent: </b>Wednesday, December 12, 2012 8:46:55 AM<div><div class="h5"><br><b>Subject: </b>Re: [one-users] deployment of certain vm's to different hosts<br>
<br>I think what you want is the extension of the cluster mechanism that already exists in opennebula to be extended so that a cluster is a scheduling domain, not simply a set of {hosts, networks, storage}<div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, Dec 11, 2012 at 4:59 PM, Gary S. Cuozzo <span dir="ltr"><<a href="mailto:gary@isgsoftware.net" target="_blank">gary@isgsoftware.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div style="font-size:12pt;font-family:arial,helvetica,sans-serif">Oh nice. So will the "REQUIREMENTS" be able to be based on any attribute of the template? For example, could I have an attribute called "VM_GROUP" in the template and have a value such as "HTTP_1" in various templates. Then, each vm with VM_GROUP HTTP_1 would get deployed to different hosts?<br>
<br>Just trying to make sure I'm interpreting the description correctly. The example shows things based on vm id's, but I think it would be easier to just be able to make any sort of generic group(s) to base things on.<br>
gary<br><br><hr><div style="font-size:12pt;font-style:normal;font-family:Helvetica,Arial,sans-serif;text-decoration:none;font-weight:normal"><b>From: </b>"Jaime Melis" <<a href="mailto:jmelis@opennebula.org" target="_blank">jmelis@opennebula.org</a>><br>
<b>To: </b>"Gary S. Cuozzo" <<a href="mailto:gary@isgsoftware.net" target="_blank">gary@isgsoftware.net</a>><br><b>Cc: </b>"Users OpenNebula" <<a href="mailto:users@lists.opennebula.org" target="_blank">users@lists.opennebula.org</a>><br>
<b>Sent: </b>Tuesday, December 11, 2012 4:41:50 PM<div><div><br><b>Subject: </b>Re: [one-users] deployment of certain vm's to different hosts<br><br>Hi,<div><br></div><div>Yes, you guys really hit the spot! take a look at this:</div>
<div><a href="http://dev.opennebula.org/issues/1675" target="_blank">http://dev.opennebula.org/issues/1675</a><br></div><div><br></div><div>Basically, for the next OpenNebula release there will be a default probe with all the running vms, so you can create a REQUIREMENTS directive just like Mark described.</div>
<div><br></div><div>cheers,<br>Jaime</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Dec 11, 2012 at 10:36 PM, Gary S. Cuozzo <span dir="ltr"><<a href="mailto:gary@isgsoftware.net" target="_blank">gary@isgsoftware.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-size:12pt;font-family:arial,helvetica,sans-serif">Interesting. You can get a list of guests on a host using "virsh list", which would simplify your idea. Hopefully I'll have some time to mess around with ideas this week. I just wanted to make sure there was no feature already in ONE that I didn't know about.<br>
<br>Let me know if you go further with your ideas and I'll do the same.<br><br>Cheers,<br>gary<br><br><hr><div style="font-size:12pt;font-style:normal;font-family:Helvetica,Arial,sans-serif;text-decoration:none;font-weight:normal">
<b>From: </b>"Mark Wagner" <<a href="mailto:mwagner@intelius.com" target="_blank">mwagner@intelius.com</a>><br><b>To: </b><a href="mailto:users@lists.opennebula.org" target="_blank">users@lists.opennebula.org</a><br>
<b>Sent: </b>Tuesday, December 11, 2012 4:18:29 PM<br><b>Subject: </b>Re: [one-users] deployment of certain vm's to different hosts<div><div><br><br>
I'm interested in this idea as well. Without modifying the ONE code
here is how it could be accomplished by extending the IM MAD and
using the "REQUIREMENTS" section of a VM template to exclude a host
that is already running a guest of the same type.<br>
<br>
How to go about it is the somewhat kludgey part. The IM MAD scripts
are run on the host; as far as I can tell from the host it is
impossible to easily see the names of the guests running on it. The
best idea I could think of would be to ssh back to the FE and run
"onevm list | grep $HOST" and process that.<br>
<br>
Next, how do you group the guests? Assuming the guests have the
naming scheme of <type>NNN you could group them by removing
the NNN. Another way to do it would be to do a onevm show on each
guest but that may be too resource intensive.<br>
<br>
Putting this all together, here is the IM MAD script:<br>
<br>
#!/bin/sh<br>
<br>
VM_HOST=`hostname`<br>
FE=onefe<br>
<br>
GUEST_TYPES="`ssh $FE onevm list --list NAME,HOST | grep $VM_HOST |
awk '{ print $1 }' | sed 's/[0-9]*$//g' | sort -u`"<br>
GUEST_TYPES=":`echo $GUEST_TYPES | sed 's/ /:/g'`:"<br>
<br>
echo "GUEST_TYPES=\"$GUEST_TYPES\""<br>
<br>
For example type "ntp" you'd put in the template<br>
<br>
REQUIREMENTS = "GUEST_TYPES != \"*:ntp:*\""<br>
<br>
(I haven't tested this at all).<br>
<br>
On 12/11/2012 10:47 AM, Gary S. Cuozzo wrote:<br>
<blockquote>
<div style="font-size:12pt;font-family:arial,helvetica,sans-serif">Hello,<br>
We have certain vm's which are related and provide redundancy
and/or failover to each other. Ideally, we'd like to avoid the
situation where these vm's run on the same host machine. Is
there a way to configure the scheduler so it would know to rule
out a host if another related vm was already running there?<br>
<br>
If there is no feature in ONE already, what I'm thinking is
having an attribute that can be set in the vm template which
could be used to group vm's together. Then, the scheduler can
just check to see if a vm that is part of the same group(s) is
already running and rule that host out if there is. It could
also optionally override the attribute if it could not find a
'unique' host to deploy on (for example, multiple hosts are
unavailable and there are not enough resource to deploy to
unique hosts).<br>
<br>
Please let me know if a feature already exists or if my idea is
worth pursuing.<br>
<br>
Cheers,<br>
gary<br>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a>
</pre>
</blockquote>
<br>
<pre>--
Mark Wagner | <a href="mailto:mwagner@intelius.com" target="_blank">mwagner@intelius.com</a>
System Administrator | Intelius Inc.
</pre>
<br>_______________________________________________<br>Users mailing list<br><a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br><a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
</div></div></div><br></div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
<br></blockquote></div><br></div><br clear="all"><div><br></div>-- <br>Jaime Melis<br>Project Engineer<br>OpenNebula - The Open Source Toolkit for Cloud Computing<br><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:jmelis@opennebula.org" target="_blank">jmelis@opennebula.org</a><br>
</div></div></div><br></div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
<br></blockquote></div><br></div>
</div></div></div><br></div></div></blockquote></div><br></div>