This vagrant projec creates a VM with Red Hat Fuse development environment.
- projects: backup/copy your git folder
- scripts/binaries: backup/copy the redhat/bin folder
- Maven: backup/copy the redhat/bin .m2 folder. use the mvn-switch.sh script to recreate the symbolic link to the settings.xml. Make sure that the global and user settings in Eclipse/CodeReadyStudio are set correctly.
- SSH: backup/copy the .ssh folder. Don't share your keys! Make sure that in the new VM the fileattrubutes of the .ssh contents are 0600 (chmod 0600 *)
- root - vagrant
- vagrant - vagrant
- oracle - welcome1
The main VM settings are abstracted into the settings.yml file.
| Property | Default | Description |
|---|---|---|
| environment.vmMemory | 11264 | Allocated memory for the VM. At least 8GB is recommended. Depending on the available host memory. |
| environment.vmCpus | 4 | Number of CPU's allocated to the VM. Don't exceed the available cores of the host. |
| environment.vmGui | false | Toggle to denote if the Desktop is to be shown (true) or should run in head-less mode (false) |
| environment.vmsHome | C:/Data/VirtualMachines/VirtualBox | Location where VirtualBox will store the VM's. Change the VirtualBox preference to this value. Or vice versa. |
| environment.disks.vmsDisk2Size | 524288 | Size of the additional disk that will be created (1024 * 512 = 524288). |
| sharedFolders.stageHostFolder | c:/Data/git/makker/vagrant/Stage | Location of the Stage folder within the Vagrant project. Here the install scripts and install binaries are expected. |
| sharedFolders.stageGuestFolder | /media/sf_Stage | Local file mount refering to the STAGE_HOST_FOLDER. Don't change it |
| sharedFolders.projectHostFolder | c:/Data/projects | Location of the Projects folder, to use to store project files. For example to get to folder with local Git clones. |
| sharedFolders.projectGuestFolder | /media/sf_Projects | Local file mount refering to the STAGE_HOST_FOLDER. Don't change it |
The settings expect that you checked out the vagrant project in c:/Data/git/makker. If you checked out the Vagrant GitHub project in a different environment then prescribed, you would need to change the sharedFolders.stageHostFolder property accordingly. The sharedFolders.projectHostFolder points to the folder where I keep my company projects. You might want to change that accordingly as well. I assume you don't have that folder.
Which provisioners are executed can be set in the provisioners.yml file. Several of the available provisioners are:
- OpenJDK 11 in /etc/alternatives/java_sdk -> /usr/lib/jvm/java-11-openjdk-11.0.8.10-0.el7_8.x86_64
- Git Check out post-provisioning configuration.
- OracleJDK 8 in /app/oracle/product/jdk8 Download Installer.
- OracleJDK 11 in /app/oracle/product/jdk11 Download Installer.
- Eclipse 2022 Download Installer.
- Apache Maven 3.8.3 Maven home: /opt/maven
- SoapUI 5.7.0 in /app/opensource/SoapUI-5.7.0. Download Installer.
- Docker Including move of the Docker local storage folder to /app/docker/data
- Docker Compose (docker-compose)
- Postman Latest from https://dl.pstmn.io/download/latest/linux64 This list is not complete, as provisioners can be added from time to time.
The following provisioners are created.
| Name | run | Description |
|---|---|---|
| init | once | Initialize VM |
| installJava11 | once | Install OpenJDK 11 |
| installOJava8 | once | Install Oracle JDK 8 |
| installMaven | once | Install Apache Maven |
| installEclipse | once | Install Eclipse |
| installSoapUI | once | Install SoapUI |
| installDocker | once | Install Docker |
| installDockerCompose | once | Install docker-compose |
| installPostman | once | Install Postman (Latest) |
| installKubectl | never | Kubernetes Control CLI |
| installHelm | never | Helm commandline interface |
| installTektonCLI | never | Tekton CLI |
| installYq | never | yq yaml query |
The provisioners.yml file allows for toggling the run property, to be able to pick&choose which provisioners should be run. Additional Provisioners can be added when needed, and using this file enabled or disabled. The some provisioners the user for which the provisioner will be run can be changed. In most cases this is the redhat user and should not be changed.
To execute a specific provisioner, even after a VM is already provisioned execute:
vagrant provision --provision-with _provisioner-name_
Some of the scripts are based on CentOS setups and have co in the name. They might need to be replaced by an Oracle Linux variant. Especially the installDocker scripts, since they refer to a CentOS Repository.