[
https://issues.apache.org/jira/browse/CLOUDSTACK-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daan Hoogland closed CLOUDSTACK-548.
------------------------------------
Resolution: Won't Fix
makes sense if clear but no discussion for a long time and a new issue is cheap
;)
> Static DHCP leases - MAC address pool
> -------------------------------------
>
> Key: CLOUDSTACK-548
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-548
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.0.0, 4.1.0
> Reporter: Ioannis Charalampidis
> Fix For: Future
>
>
> It would be very useful if there was a way to specify a MAC addresses / IP
> address pool for a particular network offering. This way, when a VM starts it
> gets a static, predefined lease from a DHCP server in the infrastructure's
> network.
> For example, we are using CloudStack in a test cluster at CERN, but due to
> our network restrictions, each machine on the network must be pre-registered.
> With this pool feature, it will make possible to register all the possible
> VMs in advance and get an IP from our central DHCP servers.
> In order to avoid expensive IP address lookups it should possible to
> pre-define an IP address for each MAC address. This is more or less the same
> parameters that someone would put in a dhcpd configuration for static leases.
> This should also be possible for the system VMs... this does not cancel-out
> the use of Virtual Router / Security Groups. On the contrary, they will need
> the static lease in order to be granted access to the infrastructure network.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
