Am 21.08.2018 um 10:35 schrieb José Manuel Giner:
What I ask is that Proxmox offer us a native DHCP server integration,
so that we can configure VMs as easily as in cloud-init based VMs or
containers.
I do not have a solution but I see the point of José.
The thing is about having untrusted
What I ask is that Proxmox offer us a native DHCP server integration, so
that we can configure VMs as easily as in cloud-init based VMs or
containers.
What we want is to avoid fighting with alternative solutions:
https://forum.proxmox.com/threads/dhcp-server-proxmox-and-ovh.43420/
What sort of OS are you using for VM's, that does not default to having
DHCP enabled? I personally can't think of one that isn't DHCP out of the
box.
As for using specific IP's based on MAC address, this would be easily set
in the dhcp server config?
On 21 August 2018 at 08:48, José Manuel Giner
I mentioned at the beginning of the conversation that this is about
installing ISO images.
On 21/08/2018 9:54, Mark Schouten wrote:
On Tue, 2018-08-21 at 09:48 +0200, José Manuel Giner wrote:
We are talking about auto-configuring the network on the VM, and
therefore you cannot install the
On Tue, 2018-08-21 at 09:48 +0200, José Manuel Giner wrote:
> We are talking about auto-configuring the network on the VM, and
> therefore you cannot install the qemu-guest-agent on the VM if you
> do
> not have a network yet.
I deploy using templates, with packages required already installed
We are talking about auto-configuring the network on the VM, and
therefore you cannot install the qemu-guest-agent on the VM if you do
not have a network yet.
On 21/08/2018 9:40, Mark Schouten wrote:
On Tue, 2018-08-21 at 08:51 +0200, José Manuel Giner wrote:
I know that already :) and it
On Tue, 2018-08-21 at 08:51 +0200, José Manuel Giner wrote:
> I know that already :) and it doesn't change anything because the
> management difficulty still exists.
>
> Everything would be simpler with native integration.
I disagree. As would many people. But, nothing stops you from writing
I know that already :) and it doesn't change anything because the
management difficulty still exists.
Everything would be simpler with native integration.
On 21/08/2018 8:27, Michael Rasmussen wrote:
On Tue, 21 Aug 2018 08:18:14 +0200
José Manuel Giner wrote:
It's not that simple when
On Tue, 21 Aug 2018 08:18:14 +0200
José Manuel Giner wrote:
> It's not that simple when IP allocation depends on the VM MAC addres, if you
> have a few VMs it may not be a problem, but hosting companies that handle
> thousands of VMs do not want to assign any random IP to a VPS and would be
>
It's not that simple when IP allocation depends on the VM MAC addres, if
you have a few VMs it may not be a problem, but hosting companies that
handle thousands of VMs do not want to assign any random IP to a VPS and
would be better to have a native integration, at least at the API level.
Maybe lost in translation? He said "determine" not "configure".
That means installing qemu agent in the guest will allow the proxmox
interface to show you what IP it is using.
On 20 August 2018 at 23:16, Vinicius Barreto
wrote:
> Hello please could you tell which command what qemu agent do you
Just install your own DHCP server on proxmox if you want. I don't see this
as a feature many people would want, as in any "normal" network you always
have a dhcp server already?
On 20 August 2018 at 15:35, José Manuel Giner wrote:
> I thought cloud-init was connecting against a DHCP server.
>
>
Hello please could you tell which command what qemu agent do you use to
configure the IP settings of the VM?
Thank you!
Em seg, 20 de ago de 2018 às 10:22, Ian Coetzee
escreveu:
> Hi José,
>
> Using the Qemu Agent you are able to determine the IP of the VM.
>
> Kind regards
>
> On Mon, 20 Aug
I thought cloud-init was connecting against a DHCP server.
Does Proxmox have any plan to provide a DHCP service so that VMs can
receive IP auto-configuration, whether they use cloud-init or not?
On 20/08/2018 16:28, Dominik Csapak wrote:
but that cannot happen without an agent/cloud init
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
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.
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 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
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!
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
Hello,
there any plan to implement DHCP for non cloudinit VMs?
Thanks!
--
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
20 matches
Mail list logo
