Right now when we do tlp-cluster use 3.11.4, it downloads the deb package, unpacks it, and puts it in the provisioning/cassandra directory. It takes up the majority of the upload time and on a slow connection it's somewhat pointless.
Instead of uploading to every server, we can push the deb package once to an S3 bucket. I'm thinking that bucket can be set once per profile. That way if the user does a lot of builds of 3.11.4, for example, they won't have to push it up every time.
The alternative is to download it from the official site every time, but that doesn't solve the problem of custom builds, which the tool needs to support.
Right now when we do
tlp-cluster use 3.11.4, it downloads the deb package, unpacks it, and puts it in the provisioning/cassandra directory. It takes up the majority of the upload time and on a slow connection it's somewhat pointless.Instead of uploading to every server, we can push the deb package once to an S3 bucket. I'm thinking that bucket can be set once per profile. That way if the user does a lot of builds of 3.11.4, for example, they won't have to push it up every time.
The alternative is to download it from the official site every time, but that doesn't solve the problem of custom builds, which the tool needs to support.