Hi Alex,
On Wed, 2015-01-07 at 12:23 +0100, Alexander Werner wrote:
the crashtest VM host has arrived.
Great news.
At the moment the setup is delayed as we ran into a problem with glusterfs:
...
This shows up during manual gluster setup as well as automatic setup by oVirt.
I will try to handle this by the end of next week, if that is not
successful I will fallback to local storage which has some
disadvantages as the host is then not able to increase the HA of the
overall platform.
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 ;-)
Thanks !
Michael.
--
michael.meeks@collabora.com <><, Pseudo Engineer, itinerant idiot
--
To unsubscribe e-mail to: website+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted
Context
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.