cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Weber (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8303) infinite lease times for a Dynamic Host Configuration Protocol should be avoided (like the plague)
Date Wed, 11 Mar 2015 20:31:39 GMT

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

Erik Weber commented on CLOUDSTACK-8303:
----------------------------------------

I agree that it shouldn't be infinite.

> infinite lease times for a Dynamic Host Configuration Protocol should be avoided (like
the plague)
> --------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8303
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8303
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Virtual Router
>            Reporter: Ronald van Zantvoort
>
> The edithosts script in the SystemVM's currently doles out DHCP leases with infinite
validity.
> Considering the D in DHCP is for 'Dynamic', and considering it might be useful to change
the information in the lease every once in a while (such as resolvers, gateways & searches
etc.), it's very bad practice to do this.
> Currently, aside from one very exotic RFC, it's impossible to inform VM's of changing
network conditions because they simply won't fetch new leases.
> Please consider changing it to at max 1 week or something, or better: a configurable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message