How to use this box with Vagrant:
Vagrant.configure("2") do |config|
config.vm.box = "ralloway/centos-8"
endvagrant init ralloway/centos-8
vagrant up
This version was created over 2 years ago.
For more information, including per-provider configuration info, support instructions, etc, please read our deployment guide
This version was created over 2 years ago.
All boxes use the latest OpenLogic cloud image for the CentOS version as of the date encoded in the release version.
i.e. 8.2.20201021 will launch the latest OpenLogic CentOS 8.2 images on each cloud provider as of Oct 21, 2020.
For this release, the AWS, Google and VirtualBox images are identical, but the Azure image is slightly different. This is because the AWS, Google and VirtualBox images are entirely OpenLogic images whereas the Azure images are built and maintained by OpenLogic for Microsoft specifically for Azure.
The AWS and Google images include 9x5 support (email-only) from our team of Tier 4 architects and engineers. Upon login, support details are presented on the terminal. The Azure and VirtualBox images are not supported in this manner, but support contracts are available directly from OpenLogic.
The AWS Vagrantfile takes advantage of the vagrant-aws plugin and requires at least this minimum configuration:
config.vm.provider :aws do |aws, override|
aws.access_key_id = "YOUR KEY"
aws.secret_access_key = "YOUR SECRET KEY"
aws.session_token = "SESSION TOKEN"
aws.keypair_name = "KEYPAIR NAME"
aws.keypair_name = "KEYPAIR NAME"
override.ssh.private_key_path = "/path/to/your/private_key"
end
The Azure Vagrantfile takes advantage of the vagrant-azure plugin and requires at least this minimum configuration:
config.ssh.private_key_path = "/path/to/your/private_key"
config.vm.provider :azure do |azure|
azure.tenant_id = "AZURE_TENANT_ID"
azure.client_id = "AZURE_CLIENT_ID"
azure.client_secret = "AZURE_CLIENT_SECRET"
azure.subscription_id = "AZURE_SUBSCRIPTION_ID"
azure.vm_password = "PASSWORD"
end
The Google Vagrantfile takes advantage of the vagrant-google plugin and requires at least this minimum configuration:
config.vm.provider :google do |google, override|
google.google_project_id = "YOUR_GOOGLE_CLOUD_PROJECT_ID"
google.google_json_key_location = "/path/to/your/google-key.json"
override.ssh.username = "USERNAME"
override.ssh.private_key_path = "/path/to/your/private_key"
end
The VirtualBox Vagrantfile requires no additional plugins or configuration.
This version was created over 2 years ago.
All boxes use the latest OpenLogic cloud image for the CentOS version as of the date encoded in the release version.
i.e. 8.2.20201019 will launch the latest OpenLogic CentOS 8.2 images on each cloud provider as of Oct 19, 2020.
For this release, the AWS, Google and VirtualBox images are identical, but the Azure image is slightly different. This is because the AWS, Google and VirtualBox images are entirely OpenLogic images whereas the Azure images are built and maintained by OpenLogic for Microsoft specifically for Azure.
The AWS and Google images include 9x5 support (email-only) from our team of Tier 4 architects and engineers. Upon login, support details are presented on the terminal. The Azure and VirtualBox images are not supported in this manner, but support contracts are available directly from OpenLogic.
The AWS Vagrantfile takes advantage of the vagrant-aws plugin and requires at least this minimum configuration:
config.vm.provider :aws do |aws, override|
aws.access_key_id = "YOUR KEY"
aws.secret_access_key = "YOUR SECRET KEY"
aws.session_token = "SESSION TOKEN"
aws.keypair_name = "KEYPAIR NAME"
aws.keypair_name = "KEYPAIR NAME"
override.ssh.private_key_path = "/path/to/your/private_key"
end
The Azure Vagrantfile takes advantage of the vagrant-azure plugin and requires at least this minimum configuration:
config.ssh.private_key_path = "/path/to/your/private_key"
config.vm.provider :azure do |azure|
azure.tenant_id = "AZURE_TENANT_ID"
azure.client_id = "AZURE_CLIENT_ID"
azure.client_secret = "AZURE_CLIENT_SECRET"
azure.subscription_id = "AZURE_SUBSCRIPTION_ID"
azure.vm_password = "PASSWORD"
end
The Google Vagrantfile takes advantage of the vagrant-google plugin and requires at least this minimum configuration:
config.vm.provider :google do |google, override|
google.google_project_id = "YOUR_GOOGLE_CLOUD_PROJECT_ID"
google.google_json_key_location = "/path/to/your/google-key.json"
override.ssh.username = "USERNAME"
override.ssh.private_key_path = "/path/to/your/private_key"
end
The VirtualBox Vagrantfile requires no additional plugins and requires at least this minimum configuration:
config.ssh.username = "centos"
This version was created over 2 years ago.
All boxes use the latest OpenLogic cloud image for the CentOS version as of the date encoded in the release version.
i.e. 8.2.20201016 will launch the latest OpenLogic CentOS 8.2 images on each cloud provider as of Oct 16, 2020.
For this release, the AWS, Google and VirtualBox images are identical, but the Azure image is slightly different. This is because the AWS, Google and VirtualBox images are entirely OpenLogic images whereas the Azure images are built and maintained by OpenLogic in for Microsoft specifically for Azure.
The AWS and Google images include 9x5 support (email-only) from our team of Tier 4 architects and engineers. Upon login, support details are presented on the terminal. The Azure and VirtualBox images are not supported in this manner, but support contracts are available directly from OpenLogic.
The AWS Vagrantfile takes advantage of the vagrant-aws plugin and requires at least this minimum configuration:
config.vm.provider :aws do |aws, override|
aws.access_key_id = "YOUR KEY"
aws.secret_access_key = "YOUR SECRET KEY"
aws.session_token = "SESSION TOKEN"
aws.keypair_name = "KEYPAIR NAME"
aws.keypair_name = "KEYPAIR NAME"
override.ssh.private_key_path = "/path/to/your/private_key"
end
The Azure Vagrantfile takes advantage of the vagrant-azure plugin and requires at least this minimum configuration:
config.ssh.private_key_path = "/path/to/your/private_key"
config.vm.provider :azure do |azure|
azure.tenant_id = "AZURE_TENANT_ID"
azure.client_id = "AZURE_CLIENT_ID"
azure.client_secret = "AZURE_CLIENT_SECRET"
azure.subscription_id = "AZURE_SUBSCRIPTION_ID"
azure.vm_password = "PASSWORD"
end
The Google Vagrantfile takes advantage of the vagrant-google plugin and requires at least this minimum configuration:
config.vm.provider :google do |google, override|
google.google_project_id = "YOUR_GOOGLE_CLOUD_PROJECT_ID"
google.google_json_key_location = "/path/to/your/google-key.json"
override.ssh.username = "USERNAME"
override.ssh.private_key_path = "/path/to/your/private_key"
end
The VirtualBox Vagrantfile requires no additional plugins and requires at least this minimum configuration:
config.ssh.username = "centos"