On 09/17/2014 11:33 AM, Jorick Astrego wrote:
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"?
> Users mailing list
Some "little things":
nfsv4 support (http://www.ovirt.org/Features/NFSv4
are there specific gaps here still?
did not make it iirc, though some progress was made.
allon - is that opt-in, or totally not in codebase?
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.
not in 3.6. if still relevant, please ask again in next poll.
//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./
vm affinity is supposed to cover some of the above?
* /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
/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
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/
/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
this could be an external utility, rather than core to ovirt?
Users mailing list