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

All it would be I'm imagining is it would be like a virtual private server.
In the long term. I think I TTF would still be quite expensive
On Mar 30, 2013 2:44 PM, "Florian Effenberger" <> wrote:


we have received a voucher for the Amazon Cloud, and after playing with it
for a while, I think it could be a good extension for our current

I would not use it for extending our general infrastructure, as
synchronizing data between two datacenters with different frameworks can be
tedious, but for booking compute power when needed, I think it's a good
thing - in other words, using it as on-demand compile cluster.

Anyone has already experience with using the Amazon Cloud for compiling?
From what I have heard, creating Windows builds would be not such a good
choice - not only is the Windows compute time more expensive than the Linux
one, but it seems that in addition, "real iron" seems to be better.

However, for other buildbot/tinderbox tasks, is there anyone who already
has experience? Otherwise, I'll investigate a bit on my own and see how we
can make best use of it.


Unsubscribe instructions: E-mail to 
Posting guidelines + more: http://wiki.****
Netiquette <>
List archive: 
All messages sent to this list will be publicly archived and cannot be

Unsubscribe instructions: 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.