Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


Am 09.01.2015 um 18:46 schrieb Markus Mohrhard <>:

        JFYI - all of the work we do inside the main VM is throw-away work - we
only are interested in the output of it. Worse - there are tens of GB of
it generated all the time - so mirroring that across a cluster sounds
like it would bring only pain & aggravation =)

        Is there some way we can have the basic VM / OS image on a HA /
mirrored image - but ensure that the scratch data we build, and throw
away repeatedly in really huge bulk doesn't end up just screwing up the
cluster performance ;-) ie. for now local storage sounds just fine to
me ;-)

for the crashtesting itself nothing else than local storage was ever considered. But i want to add 
the host to the same cluster to have 3 hosts in the cluster, so that we can enable server-quorum 
with gluster to avoid split-brain situations. So: Store Crashtest VMs in local storage, but also 
increase the stability of the whole platform. Even VMs with multiple HDDs with some with HA and 
some without can be built. 


Alexander Werner <>
Admin Team of The Document Foundation
The Document Foundation, Kurfürstendamm 188, 10707 Berlin
Rechtsfähige Stiftung des bürgerlichen Rechts
Legal details:

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.