Who’s paying for the s3 storage (sorry if I missed something there)? How long do you keep old images?
Vaguely related - I was pondering seeding ACS and/or VM image torrents - wonder if folks would be interested in that? I realize bittorrent isn’t always welcome in corp environments... On Feb 24, 2014, at 1:51 AM, Hugo Trippaers <h...@trippaers.nl<mailto:h...@trippaers.nl>> wrote: Hey all, I’ve finally fixed the configuration to automagically upload the systemvm templates to an s3 bucket. The jobs build-systemvm-master and build-systemvm64-master will rebuild the systemvm template on a daily basis and send the resulting files to that S3 bucket. I would like to update the URLs in the docs and in the database to make master point to these new locations. The locations will look like : https://s3.amazonaws.com/systemvm-templates.cloudstack.org/master/64/systemvm64template-master-hyperv.vhd Why? Anyone using master will automagically use the latest and greatest images. Transparent process from build script to distribution. Accessible logging for folks willing to track number of downloads etc. Any thoughts? Cheers, Hugo Stratosec<http://stratosec.co/> - Compliance as a Service o: 415.315.9385 @johnlkinsella<http://twitter.com/johnlkinsella>
