incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Sorensen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-548) Static DHCP leases - MAC address pool
Date Wed, 28 Nov 2012 16:54:58 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505647#comment-13505647
] 

Marcus Sorensen commented on CLOUDSTACK-548:
--------------------------------------------

Maybe what you want is the ability to pass a mac address to deployVm? You can already select
which IP address a VM will get when you create the VM, but it doesn't sound like you're using
cloudstack-provided DHCP (your reference to centeral DHCP servers). If you have your own DHCP
servers, then you could create a network offering without DHCP/DNS services, create a network
based on that offering, and then specify a mac when you run deployVM in order to select the
IP it gets from the central DHCP server (if the feature were added).

I sort of get the issue you have, but I'm struggling to understand how you want to fix it,
since the MAC addresses are dynamically generated upon VM creation, and you can already specify
IP on vm deployment and specify an IP pool for the network when you create it( and only if
you are using CloudStack provided DHCP). Do you just want a MAC pool associated with a network,
or do you want to specify an exact MAC for a VM upon deploying it?
                
> Static DHCP leases - MAC address pool
> -------------------------------------
>
>                 Key: CLOUDSTACK-548
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-548
>             Project: CloudStack
>          Issue Type: New Feature
>            Reporter: Ioannis Charalampidis
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message