This is a multi-part message in MIME format. --------------080507040808090903050208 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit On 09/12/2014 02:22 PM, Itamar Heim wrote:
With oVirt 3.5 nearing GA, time to ask for "what do you want to see in oVirt 3.6"?
Thanks, Itamar _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Some "little things": nfsv4 support (http://www.ovirt.org/Features/NFSv4) libgfapi drbd support (http://www.ovirt.org/Features/DRBD) Some concepts from IBM PowerHA look interesting: I don't know if the term is correct but we'd like to be able to group vm's together and create dependency's between them. Something like, first start the database vm then the authentication vm and last the webserver vm. /resource groups (http://www-01.ibm.com/support/knowledgecenter/SSPHQG_7.1.0/com.ibm.powerha.c... //Resource groups/allow you to combine related resources into a single logical entity for easier configuration and management. The//PowerHA SystemMirror//software handles the resource group as a unit, thus keeping the interdependent resources together on one node and keeping them highly available./ // * /Identifying the set of cluster resources that are essential to the operation of an application, and combining those resources into a resource group./ * /Defining the resource group policies and attributes that dictate how////PowerHA SystemMirror////manages resources to keep them highly available at different stages of cluster operation (startup, fallover and fallback)./ /By identifying resources and defining resource group policies, the////PowerHA SystemMirror////software makes numerous cluster configurations possible, providing tremendous flexibility in defining a cluster environment tailored to individual requirements. / We would also like to be able to split a cluster between two racks or DC's /linked clusters/ /http://www-01.ibm.com/support/knowledgecenter/api/content/SSPHQG_7.1.0/com.i... /A linked cluster is ideal for situations where each site is located at a different geographical location. Typically, the sites are far enough apart so that they cannot conveniently share a common storage area network (SAN). Each site must have its own active repository disk, and any backup repositories. Linked clusters always use unicast to communicate between sites. Linked clusters are a useful part of high availability disaster recovery (HADR)./ We are currently developing a benchmarking system for ovirt and test failover stuff by hand. Something like this would save people a lot of time /Cluster test tool/ /http://www-01.ibm.com/support/knowledgecenter/SSPHQG_7.1.0/com.ibm.powerha.c... /The Cluster Test Tool is a utility that lets you test a////PowerHA® SystemMirror®////cluster configuration to evaluate how a cluster behaves under a set of specified circumstances, such as when a node becomes inaccessible, a network becomes inaccessible, a resource group moves from one node to another, and so forth./ /You can start the test, let it run unattended, and return later to evaluate the results of your testing./ /If you want to run an automated suite of basic cluster tests for topology and resource group management, you can run the automated test suite from SMIT. If you are an experienced////PowerHA SystemMirror//administrator and want to tailor cluster testing to your environment, you can also create custom tests that can be run from SMIT./ /It is recommended to run the tool after you initially configure////PowerHA SystemMirror////and before you put your cluster into a production environment; after you make cluster configuration changes while the cluster is out of service; or at regular intervals even though the cluster appears to be functioning well./ --------------080507040808090903050208 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit <html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <br> <div class="moz-cite-prefix">On 09/12/2014 02:22 PM, Itamar Heim wrote:<br> </div> <blockquote cite="mid:5412E591.6060900@redhat.com" type="cite">With oVirt 3.5 nearing GA, time to ask for "what do you want to see in oVirt 3.6"? <br> <br> Thanks, <br> Itamar <br> _______________________________________________ <br> Users mailing list <br> <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <br> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> <br> </blockquote> <br> Some "little things":<br> <br> <blockquote>nfsv4 support (<a class="moz-txt-link-freetext" href="http://www.ovirt.org/Features/NFSv4">http://www.ovirt.org/Features/NFSv4</a>)<br> <br> libgfapi <br> <br> drbd support (<a class="moz-txt-link-freetext" href="http://www.ovirt.org/Features/DRBD">http://www.ovirt.org/Features/DRBD</a>)<br> <br> <br> Some concepts from IBM PowerHA look interesting:<br> <br> <blockquote>I don't know if the term is correct but we'd like to be able to group vm's together and create dependency's between them. Something like, first start the database vm then the authentication vm and last the webserver vm.<br> <br> <i>resource groups (<a class="moz-txt-link-freetext" href="http://www-01.ibm.com/support/knowledgecenter/SSPHQG_7.1.0/com.ibm.powerha.concepts/ha_concepts_cluster_resources.htm">http://www-01.ibm.com/support/knowledgecenter/SSPHQG_7.1.0/com.ibm.powerha.concepts/ha_concepts_cluster_resources.htm</a>)</i><br> <i> </i><dfn class="term" style="color: rgb(0, 0, 0); font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 13px; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 16.66666603088379px; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);">Resource groups</dfn><i><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 16.66666603088379px; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline !important; float: none; background-color: rgb(255, 255, 255);"><span class="Apple-converted-space"> </span>allow you to combine related resources into a single logical entity for easier configuration and management. The</span></i><i><span class="ph" style="color: rgb(0, 0, 0); font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 16.66666603088379px; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);">PowerHA SystemMirror</span></i><i><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 16.66666603088379px; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline !important; float: none; background-color: rgb(255, 255, 255);"><span class="Apple-converted-space"> </span>software handles the resource group as a unit, thus keeping the interdependent resources together on one node and keeping them highly available.</span></i><br> <i><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 16.66666603088379px; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline !important; float: none; background-color: rgb(255, 255, 255);"></span></i> <ul class="ul" style="padding: 0px; margin: 0.75em 0px 0.75em 2em; list-style-type: disc; color: rgb(0, 0, 0); font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);"> <li class="li" style="padding: 0px; margin: 0.75em 0px; line-height: 16.66666603088379px;"><i>Identifying the set of cluster resources that are essential to the operation of an application, and combining those resources into a resource group.</i></li> <li class="li" style="padding: 0px; margin: 0.75em 0px; line-height: 16.66666603088379px;"><i>Defining the resource group policies and attributes that dictate how</i><i><span class="Apple-converted-space"> </span></i><i><span class="ph">PowerHA SystemMirror</span></i><i><span class="Apple-converted-space"> </span></i><i>manages resources to keep them highly available at different stages of cluster operation (startup, fallover and fallback).</i></li> </ul> <p class="p" style="padding: 0px; margin: 1em 0px 0.75em; line-height: 16.66666603088379px; color: rgb(0, 0, 0); font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);"><i>By identifying resources and defining resource group policies, the</i><i><span class="Apple-converted-space"> </span></i><i><span class="ph">PowerHA SystemMirror</span></i><i><span class="Apple-converted-space"> </span></i><i>software makes numerous cluster configurations possible, providing tremendous flexibility in defining a cluster environment tailored to individual requirements.<br> </i></p> <big><big><small>We would also like to be able to split a cluster between two racks or DC's</small></big></big><br> <i>linked clusters</i><br> <i><a class="moz-txt-link-freetext" href="http://www-01.ibm.com/support/knowledgecenter/api/content/SSPHQG_7.1.0/com.ibm.powerha.concepts/ha_concepts_multi_linked.htm">http://www-01.ibm.com/support/knowledgecenter/api/content/SSPHQG_7.1.0/com.ibm.powerha.concepts/ha_concepts_multi_linked.htm</a></i><br> <i><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 16.66666603088379px; orphans: auto; text-align: left; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline !important; float: none; background-color: rgb(255, 255, 255);">A linked cluster is ideal for situations where each site is located at a different geographical location. Typically, the sites are far enough apart so that they cannot conveniently share a common storage area network (SAN). Each site must have its own active repository disk, and any backup repositories. Linked clusters always use unicast to communicate between sites. Linked clusters are a useful part of high availability disaster recovery (HADR).</span></i><br> <br> We are currently developing a benchmarking system for ovirt and test failover stuff by hand. Something like this would save people a lot of time<br> <i>Cluster test tool</i><br> <i><a class="moz-txt-link-freetext" href="http://www-01.ibm.com/support/knowledgecenter/SSPHQG_7.1.0/com.ibm.powerha.concepts/ha_concepts_test_tool.htm">http://www-01.ibm.com/support/knowledgecenter/SSPHQG_7.1.0/com.ibm.powerha.concepts/ha_concepts_test_tool.htm</a></i><br> <br> <div class="body conbody" style="color: rgb(0, 0, 0); font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"> <p class="shortdesc" style="padding: 0px; margin: 0.75em 0px; line-height: 16.66666603088379px;"><i>The Cluster Test Tool is a utility that lets you test a</i><i><span class="Apple-converted-space"> </span></i><i><span class="ph">PowerHA® SystemMirror®</span></i><i><span class="Apple-converted-space"> </span></i><i>cluster configuration to evaluate how a cluster behaves under a set of specified circumstances, such as when a node becomes inaccessible, a network becomes inaccessible, a resource group moves from one node to another, and so forth.</i></p> <p class="p" style="padding: 0px; margin: 1em 0px 0.75em; line-height: 16.66666603088379px;"><i>You can start the test, let it run unattended, and return later to evaluate the results of your testing.</i></p> <p class="p" style="padding: 0px; margin: 1em 0px 0.75em; line-height: 16.66666603088379px;"><i>If you want to run an automated suite of basic cluster tests for topology and resource group management, you can run the automated test suite from SMIT. If you are an experienced</i><i><span class="Apple-converted-space"> </span></i><i><span class="ph">PowerHA SystemMirror</span></i><i>administrator and want to tailor cluster testing to your environment, you can also create custom tests that can be run from SMIT.</i></p> <p class="p" style="padding: 0px; margin: 1em 0px 0.75em; line-height: 16.66666603088379px;"><i>It is recommended to run the tool after you initially configure</i><i><span class="Apple-converted-space"> </span></i><i><span class="ph">PowerHA SystemMirror</span></i><i><span class="Apple-converted-space"> </span></i><i>and before you put your cluster into a production environment; after you make cluster configuration changes while the cluster is out of service; or at regular intervals even though the cluster appears to be functioning well.</i></p> </div> </blockquote> <meta http-equiv="content-type" content="text/html; charset=windows-1252"> <meta http-equiv="content-type" content="text/html; charset=windows-1252"> <meta http-equiv="content-type" content="text/html; charset=windows-1252"> <br> </blockquote> <meta http-equiv="content-type" content="text/html; charset=windows-1252"> </body> </html> --------------080507040808090903050208--