Releases: aerospike/aerolab
AeroLab - v7.6.3
Upgrading
If using AWS or GCP backends, extra steps are required to migrate the firewalls from AeroLab version 6.0 or below to a new system. Follow this manual for upgrade instructions
Documentation and changelog
See the documentation for full installation and usage instructions.
Download aerolab from Assets below
Download one of the installers from the releases page, depending on where you are intending to execute aerolab command itself. Aerolab will still be able to deploy Aerospike on both arm and x64 architectures, regardless of which aerolab binary you are using.
AeroLab is currently compiled and packaged for amd64 and arm64 as below:
- MacOS as a multiarch installer and compressed binaries
- Linux as zip, deb and rpm
- Windows as zipped executables
Install - MacOS and Linux
It is advisable to use the provided installer files for your distro. Upon download, run the installation and aerolab command will become available.
Alternatively, manual installation can be performed by downloading the relevant zip file, unpacking it, and then moving the unpacked aerolab binary to /usr/local/bin/ or /usr/bin/. Remember to chmod +x the binary.
Install - Windows users
Download the zip file, unpack it and run it from Explorer by double-clicking on it. AeroLab will install itself and become available in PowerShell as the aerolab command. You may need to close and reopen PowerShell for the changes to take effect.
Alternatively, the binary itself may be called straight from PowerShell without first installing.
AeroLab - v7.6.2
Upgrading
If using AWS or GCP backends, extra steps are required to migrate the firewalls from AeroLab version 6.0 or below to a new system. Follow this manual for upgrade instructions
Documentation and changelog
See the documentation for full installation and usage instructions.
Download aerolab from Assets below
Download one of the installers from the releases page, depending on where you are intending to execute aerolab command itself. Aerolab will still be able to deploy Aerospike on both arm and x64 architectures, regardless of which aerolab binary you are using.
AeroLab is currently compiled and packaged for amd64 and arm64 as below:
- MacOS as a multiarch installer and compressed binaries
- Linux as zip, deb and rpm
- Windows as zipped executables
Install - MacOS and Linux
It is advisable to use the provided installer files for your distro. Upon download, run the installation and aerolab command will become available.
Alternatively, manual installation can be performed by downloading the relevant zip file, unpacking it, and then moving the unpacked aerolab binary to /usr/local/bin/ or /usr/bin/. Remember to chmod +x the binary.
Install - Windows users
Download the zip file, unpack it and run it from Explorer by double-clicking on it. AeroLab will install itself and become available in PowerShell as the aerolab command. You may need to close and reopen PowerShell for the changes to take effect.
Alternatively, the binary itself may be called straight from PowerShell without first installing.
AeroLab - v7.6.1
Upgrading
If using AWS or GCP backends, extra steps are required to migrate the firewalls from AeroLab version 6.0 or below to a new system. Follow this manual for upgrade instructions
Documentation and changelog
See the documentation for full installation and usage instructions.
Download aerolab from Assets below
Download one of the installers from the releases page, depending on where you are intending to execute aerolab command itself. Aerolab will still be able to deploy Aerospike on both arm and x64 architectures, regardless of which aerolab binary you are using.
AeroLab is currently compiled and packaged for amd64 and arm64 as below:
- MacOS as a multiarch installer and compressed binaries
- Linux as zip, deb and rpm
- Windows as zipped executables
Install - MacOS and Linux
It is advisable to use the provided installer files for your distro. Upon download, run the installation and aerolab command will become available.
Alternatively, manual installation can be performed by downloading the relevant zip file, unpacking it, and then moving the unpacked aerolab binary to /usr/local/bin/ or /usr/bin/. Remember to chmod +x the binary.
Install - Windows users
Download the zip file, unpack it and run it from Explorer by double-clicking on it. AeroLab will install itself and become available in PowerShell as the aerolab command. You may need to close and reopen PowerShell for the changes to take effect.
Alternatively, the binary itself may be called straight from PowerShell without first installing.
AeroLab - v7.6.0
Upgrading
If using AWS or GCP backends, extra steps are required to migrate the firewalls from AeroLab version 6.0 or below to a new system. Follow this manual for upgrade instructions
Documentation and changelog
See the documentation for full installation and usage instructions.
Download aerolab from Assets below
Download one of the installers from the releases page, depending on where you are intending to execute aerolab command itself. Aerolab will still be able to deploy Aerospike on both arm and x64 architectures, regardless of which aerolab binary you are using.
AeroLab is currently compiled and packaged for amd64 and arm64 as below:
- MacOS as a multiarch installer and compressed binaries
- Linux as zip, deb and rpm
- Windows as zipped executables
Install - MacOS and Linux
It is advisable to use the provided installer files for your distro. Upon download, run the installation and aerolab command will become available.
Alternatively, manual installation can be performed by downloading the relevant zip file, unpacking it, and then moving the unpacked aerolab binary to /usr/local/bin/ or /usr/bin/. Remember to chmod +x the binary.
Install - Windows users
Download the zip file, unpack it and run it from Explorer by double-clicking on it. AeroLab will install itself and become available in PowerShell as the aerolab command. You may need to close and reopen PowerShell for the changes to take effect.
Alternatively, the binary itself may be called straight from PowerShell without first installing.
AeroLab - v7.5.2
Upgrading
If using AWS or GCP backends, extra steps are required to migrate the firewalls from AeroLab version 6.0 or below to a new system.
Follow this manual for upgrade instructions
NOTES:
- AeroLab 7.0.0 implements an instance expiry system. By default your instances will terminate after 30 hours. To modify this behaviour, create clusters with
--aws-expires TIMEor--gcp-expires. For example--aws-expires 50h. To disable expiry, set to0. - AeroLab 7.2.0 adds AWS EFS Volume expiries. If using the expiry system in AWS, reinstall using
aerolab config aws expiry-remove && aerolab config aws expiry-install.
Documentation and changelog
See the documentation for full installation and usage instructions.
Download aerolab from Assets below
Head to the releases page and download one of the installers, depending on where you are intending to execute aerolab command itself.
Note that aerolab will still be able to deploy Aerospike on both arm and x64 architectures, regardless of which aerolab binary you are using.
AeroLab is currently compiled and packaged for amd64 and arm64 as below:
- MacOS as an installer and compressed binaries
- Linux as zip, deb and rpm
- Windows as zip executables
Install - MacOS and Linux
It is advisable to use the provided installer files for your distro. Upon download, run the installation and aerolab command will become available.
Alternatively, manual installation can be performed by downloading the relevant zip file, unpacking it, and then moving the unpacked aerolab binary to /usr/local/bin/ or /usr/bin/. Remember to chmod +x the binary too.
Install - Windows users
Download the zip file, unpack it and run it from Explorer by double-clicking on it. AeroLab will install itself and become available in PowerShell as the aerolab command. You may need to close and reopen PowerShell for the changes to take effect.
Alternative, the binary itself may be called straight from PowerShell without first installing.
AeroLab - v7.5.1
Upgrading
If using AWS or GCP backends, extra steps are required to migrate the firewalls from AeroLab version 6.0 or below to a new system.
Follow this manual for upgrade instructions
NOTES:
- AeroLab 7.0.0 implements an instance expiry system. By default your instances will terminate after 30 hours. To modify this behaviour, create clusters with
--aws-expires TIMEor--gcp-expires. For example--aws-expires 50h. To disable expiry, set to0. - AeroLab 7.2.0 adds AWS EFS Volume expiries. If using the expiry system in AWS, reinstall using
aerolab config aws expiry-remove && aerolab config aws expiry-install.
Documentation and changelog
See the documentation for full installation and usage instructions.
Download aerolab from Assets below
Head to the releases page and download one of the installers, depending on where you are intending to execute aerolab command itself.
Note that aerolab will still be able to deploy Aerospike on both arm and x64 architectures, regardless of which aerolab binary you are using.
AeroLab is currently compiled and packaged for amd64 and arm64 as below:
- MacOS as an installer and compressed binaries
- Linux as zip, deb and rpm
- Windows as zip executables
Install - MacOS and Linux
It is advisable to use the provided installer files for your distro. Upon download, run the installation and aerolab command will become available.
Alternatively, manual installation can be performed by downloading the relevant zip file, unpacking it, and then moving the unpacked aerolab binary to /usr/local/bin/ or /usr/bin/. Remember to chmod +x the binary too.
Install - Windows users
Download the zip file, unpack it and run it from Explorer by double-clicking on it. AeroLab will install itself and become available in PowerShell as the aerolab command. You may need to close and reopen PowerShell for the changes to take effect.
Alternative, the binary itself may be called straight from PowerShell without first installing.
AeroLab - v7.5.0
Upgrading
If using AWS or GCP backends, extra steps are required to migrate the firewalls from AeroLab version 6.0 or below to a new system.
Follow this manual for upgrade instructions
NOTES:
- AeroLab 7.0.0 implements an instance expiry system. By default your instances will terminate after 30 hours. To modify this behaviour, create clusters with
--aws-expires TIMEor--gcp-expires. For example--aws-expires 50h. To disable expiry, set to0. - AeroLab 7.2.0 adds AWS EFS Volume expiries. If using the expiry system in AWS, reinstall using
aerolab config aws expiry-remove && aerolab config aws expiry-install.
Documentation and changelog
See the documentation for full installation and usage instructions.
Download aerolab from Assets below
Head to the releases page and download one of the installers, depending on where you are intending to execute aerolab command itself.
Note that aerolab will still be able to deploy Aerospike on both arm and x64 architectures, regardless of which aerolab binary you are using.
AeroLab is currently compiled and packaged for amd64 and arm64 as below:
- MacOS as an installer and compressed binaries
- Linux as zip, deb and rpm
- Windows as zip executables
Install - MacOS and Linux
It is advisable to use the provided installer files for your distro. Upon download, run the installation and aerolab command will become available.
Alternatively, manual installation can be performed by downloading the relevant zip file, unpacking it, and then moving the unpacked aerolab binary to /usr/local/bin/ or /usr/bin/. Remember to chmod +x the binary too.
Install - Windows users
Download the zip file, unpack it and run it from Explorer by double-clicking on it. AeroLab will install itself and become available in PowerShell as the aerolab command. You may need to close and reopen PowerShell for the changes to take effect.
Alternative, the binary itself may be called straight from PowerShell without first installing.
AeroLab - v7.4.0
Upgrading
If using AWS or GCP backends, extra steps are required to migrate the firewalls from AeroLab version 6.0 or below to a new system.
Follow this manual for upgrade instructions
NOTES:
- AeroLab 7.0.0 implements an instance expiry system. By default your instances will terminate after 30 hours. To modify this behaviour, create clusters with
--aws-expires TIMEor--gcp-expires. For example--aws-expires 50h. To disable expiry, set to0. - AeroLab 7.2.0 adds AWS EFS Volume expiries. If using the expiry system in AWS, reinstall using
aerolab config aws expiry-remove && aerolab config aws expiry-install.
Documentation and changelog
See the documentation for full installation and usage instructions.
Download aerolab from Assets below
Head to the releases page and download one of the installers, depending on where you are intending to execute aerolab command itself.
Note that aerolab will still be able to deploy Aerospike on both arm and x64 architectures, regardless of which aerolab binary you are using.
AeroLab is currently compiled and packaged for amd64 and arm64 as below:
- MacOS as an installer and compressed binaries
- Linux as zip, deb and rpm
- Windows as zip executables
Install - MacOS and Linux
It is advisable to use the provided installer files for your distro. Upon download, run the installation and aerolab command will become available.
Alternatively, manual installation can be performed by downloading the relevant zip file, unpacking it, and then moving the unpacked aerolab binary to /usr/local/bin/ or /usr/bin/. Remember to chmod +x the binary too.
Install - Windows users
Download the zip file, unpack it and run it from Explorer by double-clicking on it. AeroLab will install itself and become available in PowerShell as the aerolab command. You may need to close and reopen PowerShell for the changes to take effect.
Alternative, the binary itself may be called straight from PowerShell without first installing.
AeroLab - v7.3.0
Upgrading
If using AWS or GCP backends, extra steps are required to migrate the firewalls from AeroLab version 6.0 or below to a new system.
Follow this manual for upgrade instructions
NOTES:
- AeroLab 7.0.0 implements an instance expiry system. By default your instances will terminate after 30 hours. To modify this behaviour, create clusters with
--aws-expires TIMEor--gcp-expires. For example--aws-expires 50h. To disable expiry, set to0. - AeroLab 7.2.0 adds AWS EFS Volume expiries. If using the expiry system in AWS, reinstall using
aerolab config aws expiry-remove && aerolab config aws expiry-install.
Documentation and changelog
See the documentation for full installation and usage instructions.
Download aerolab from Assets below
Head to the releases page and download one of the installers, depending on where you are intending to execute aerolab command itself.
Note that aerolab will still be able to deploy Aerospike on both arm and x64 architectures, regardless of which aerolab binary you are using.
AeroLab is currently compiled and packaged for amd64 and arm64 as below:
- MacOS as an installer and compressed binaries
- Linux as zip, deb and rpm
- Windows as zip executables
Install - MacOS and Linux
It is advisable to use the provided installer files for your distro. Upon download, run the installation and aerolab command will become available.
Alternatively, manual installation can be performed by downloading the relevant zip file, unpacking it, and then moving the unpacked aerolab binary to /usr/local/bin/ or /usr/bin/. Remember to chmod +x the binary too.
Install - Windows users
Download the zip file, unpack it and run it from Explorer by double-clicking on it. AeroLab will install itself and become available in PowerShell as the aerolab command. You may need to close and reopen PowerShell for the changes to take effect.
Alternative, the binary itself may be called straight from PowerShell without first installing.
AeroLab - v7.2.2
Upgrading
If using AWS or GCP backends, extra steps are required to migrate the firewalls from AeroLab version 6.0 or below to a new system.
Follow this manual for upgrade instructions
NOTES:
- AeroLab 7.0.0 implements an instance expiry system. By default your instances will terminate after 30 hours. To modify this behaviour, create clusters with
--aws-expires TIMEor--gcp-expires. For example--aws-expires 50h. To disable expiry, set to0. - AeroLab 7.2.0 adds AWS EFS Volume expiries. If using the expiry system in AWS, reinstall using
aerolab config aws expiry-remove && aerolab config aws expiry-install.
Documentation and changelog
See the documentation for full installation and usage instructions.
Download aerolab from Assets below
Head to the releases page and download one of the installers, depending on where you are intending to execute aerolab command itself.
Note that aerolab will still be able to deploy Aerospike on both arm and x64 architectures, regardless of which aerolab binary you are using.
AeroLab is currently compiled and packaged for amd64 and arm64 as below:
- MacOS as an installer and compressed binaries
- Linux as zip, deb and rpm
- Windows as zip executables
Install - MacOS and Linux
It is advisable to use the provided installer files for your distro. Upon download, run the installation and aerolab command will become available.
Alternatively, manual installation can be performed by downloading the relevant zip file, unpacking it, and then moving the unpacked aerolab binary to /usr/local/bin/ or /usr/bin/. Remember to chmod +x the binary too.
Install - Windows users
Download the zip file, unpack it and run it from Explorer by double-clicking on it. AeroLab will install itself and become available in PowerShell as the aerolab command. You may need to close and reopen PowerShell for the changes to take effect.
Alternative, the binary itself may be called straight from PowerShell without first installing.