but that cannot happen without an agent/cloud init like program in the
vm, so what and why (if we have cloud-init) should we implement there?
On 08/20/2018 03:25 PM, José Manuel Giner wrote:
I mean, when you install the ISO of an operating system on a VM, when
configuring the network, that the user can choose the DHCP option
instead of defining the values by hand.
On 20/08/2018 15:21, Ian Coetzee wrote:
Hi José,
Using the Qemu Agent you are able to determine the IP of the VM.
Kind regards
On Mon, 20 Aug 2018 at 13:43, José Manuel Giner <j...@ginernet.com> wrote:
The possibility of being able to define IPs directly from the
Proxmox/API interface. Just like with Cloud-init or containers.
On 20/08/2018 11:14, Dominik Csapak wrote:
On 08/20/2018 09:36 AM, José Manuel Giner wrote:
Hello,
there any plan to implement DHCP for non cloudinit VMs?
Thanks!
the question does not really make sense as we did not implement dhcp
for
cloudinit, the config there only tells the vm how to configure its
network (same as with containers, were we also don't implement a dhcp
server)
but where is the problem in having a host/vm in your network serving
dhcp?
_______________________________________________
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
--
José Manuel Giner
http://ginernet.com
_______________________________________________
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
_______________________________________________
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
_______________________________________________
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
