You can set the IP address on any VM statically, even if DHCP is enabled on the network.
But as Weizhouapache mentioned, if you did this via template, all the VMs would have the same IP. If I needed to do this, I would create the VM, and change the network settings to static like you need, but the IP I would use would be invalid for that subnet. This allows you to spin this template up as much as you want and not interfere with “production VMs. Also, why do you need to specify a static IP explicitly? You can do this when spinning up a VM via a template by leaving it DHCP. During the creation of the VM, specify the IP you want it to have. This is a DHCP reservation and is effectively “static”. From: weizhouapache (via GitHub) <[email protected]> Date: Friday, July 5, 2024 at 1:46 PM To: [email protected] <[email protected]> Subject: Re: [D] Static IP in cloudstack instance [cloudstack] WARNING: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. GitHub user weizhouapache edited a comment on the discussion: Static IP in cloudstack instance You can make the changes you mentioned, then stop the vm and create a template from its volume. But all vms created from the template will have the same IP. What's your use case? GitHub link: https://github.com/apache/cloudstack/discussions/9342#discussioncomment-9970342 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
