nemo/deploy_vm
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
14 commits 1 branch 0 tags 364 KiB
Shell 100%
Go to file
nemo 9e4c3b2644 Test set static bridge for SSH connection
2019-09-09 11:07:35 +02:00
creds Initial commit, based on old erispoe VM deploy script 2019-05-05 19:23:45 +02:00
deploy_vm.conf Initial commit, based on old erispoe VM deploy script 2019-05-05 19:23:45 +02:00
deploy_vm.sh Test set static bridge for SSH connection 2019-09-09 11:07:35 +02:00
LICENSE Initial commit, based on old erispoe VM deploy script 2019-05-05 19:23:45 +02:00
README.md Correct README 2019-09-08 15:40:52 +02:00
vm-template.conf Set incorrect SSH pub key for example 2019-09-08 15:43:53 +02:00

README.md

deploy_vm

Script to deploy a VM based on debian template (in our case). The script add IPAM entry for an IPv4 address and an IPv6 range, and deploy/configure a VM based on the VM conf file (see vm-template.conf).

How to use

  • Define your IPAM credentials in file "cred" and adjust parameters in "deploy_vm.conf" file
  • Copy the VM conf file template : cp vm-template.conf vm-user123.conf
  • Adjust all parameters in new file vm-user123.conf
  • WARNING : if the SSH public key isn't correct, nobody would be able to log in the VM after deploy.
  • Run the script : ./deploy_vm.sh vm-user123.conf

If problems

  • If the script fail and already do updates in IPAM or on the VM, you can manually finish the deploy OR delete IPAM entries (1 IPv4 and 1 IPv6 range), delete the VM, rectify to avoid the problem and retry deploy

To do

  • Variabilize some parameters like adminsys e-mail address, disk's name, ...
  • Verify if VM conf file parameters are numbers before test the interval (actually in the same line)
  • Verify deploy_vm.conf parameters