On 11/16/2015 04:24 PM, John Wong wrote:
Obviously you will get a better answer from someone directly with
datastax... but IMO, I would look to either
The ASF handles the Apache Cassandra download infrastructure, not
DataStax. (I work for DataStax, fyi)
I believe the OP is asking about links to the mirror redirects from
http://cassandra.apache.org/download/
* keep the package locally in your own infrastructure. I have had mirror
issue or content unavailable error in the past with other OSS before.
If you can get hold of an NFS server, or a S3 bucket, you will probably
be okay doing bulk roll out more quickly and reliability.
This is good advice and might make things a little faster, if the
internal mirror is local to the installing clients.
On Mon, Nov 16, 2015 at 3:40 PM, Bryan Cheng <br...@blockcypher.com
<mailto:br...@blockcypher.com>> wrote:
Is there a URL available for downloading Cassandra that abstracts
away the mirror selection (eg. just 302's to a mirror URL?) We've
got a few self-configuring Cassandras (for example, the Docker
container our devs use), and using the same mirror for the
containers or for any bulk provisioning operation seems like bad
table manners.
As suggested, your own mirror might be the best route to go, since you
control the availability and content. The full list of mirrors and
creating your own mirror docs might be helpful if you want a
geographically closer mirror, or want to set up your own mirror of a
subset of software.
http://www.apache.org/mirrors/
http://www.apache.org/info/how-to-mirror.html
I don't know if they or one of the mirrors might provide the ability to
rsync mirror *only* cassandra to your internal mirror, but even that may
be too much unnecessary data. Personally, I'd download and throw the
exact versions of packages you want in dirs on your own web server, and
just upload new versions for your devs after you've had a quick test or two.
--
Kind regards,
Michael
