Closed dorogarcia closed 8 years ago
I was under the impression that all instances must have a VLAN ID, but it seems you can also create them without one. Will see if it's easy to add.
In the mean time, the exception you're getting (value must have minimum value of 2) should be fixed in PVE 4.2-6+.
Yes, because it uses ID "1" by default and this ID in use, if i type 2, everything works but after script creates vm i have to change vlan ID from 2 to empty.
Thanks :)
No, that message is actually part of this bug: https://bugzilla.proxmox.com/show_bug.cgi?id=952 .
Proxmox changed the minimum VLAN ID to 2, and enforced this suddenly during 4.1 and 4.2. It should now only generate a warning.
I created an pull request (#6) for this issue, but I can't test it at the moment. If you'd like, you can download the PR and test it for me.
It works!
# proxmox-deploy --proxmox-host XXXXXX --proxmox-user XXXX --cloud-images-dir /mnt/nfs/images/
proxmox-deploy version 0.3 (build 7b45fa9) starting...
▽
Asking user for configuration input
Storage to create disk on (Enter ? for a list of options) [test1]:
Amount of CPUs: 1
Emulate which CPU family (Enter ? for a list of options) [host]:
Amount of Memory (MB): 512
Size of disk (GB): 10
Virtual Machine id [100]: 31337
Hostname (a FQDN is recommended): 31337
What Cloud image to upload (Enter ? for a list of options) [/mnt/nfs/images/trusty-server-cloudimg-amd64-disk1.img]:
Locale (Enter ? for a list of options) [en_US.UTF-8]:
Timezone (Enter ? for a list of options) [Europe/Amsterdam]:
Keyboard layout (Enter ? for a list of options) [us]:
SSH Public key for root user [2 entries]:
Run apt-get update after rollout [Yes]:
Run apt-get upgrade after rollout [No]:
Bootstrap with Chef [No]:
Configure networking [Yes]:
VLAN ID [1 or 'empty']: empty
Network device to configure [eth0]:
Network type (Enter ? for a list of options) [dhcp]:
Resize root filesystem [Yes]:
Install extra packages (space separated)) []:
Run commands after cloud init (space separated) []:
Reboot after cloud-init [No]: Yes
Start VM after provisioning [No]: Yes
Starting provisioning process
Creating Virtual Machine
Generating cloud-init seed files at /tmp/cloudinit-seed-isoDc3o5o
Generating cloud-init seed ISO at /tmp/cloudinit-seed-iso-zSn4yj.iso
Removing cloud-init temp files
Uploading cloud-init seed ISO to Proxmox
Uploading to flat storage
Transferring image to Proxmox
Setting disk size to 366K
Allocating virtual disk
Copying image into virtual disk
Removing temporary disk file
Uploading cloud image to Proxmox
Uploading to flat storage
Transferring image to Proxmox
Allocating virtual disk
Copying image into virtual disk
Removing temporary disk file
Resizing virtual disk
Adding serial console to VM
Starting VM
Virtual Machine provisioning completed
#
Thanks.
Hello,
Should be good idea if script allows to use untagged networks.
Regards.