Feature #1062: The automatic loading of next ip when a subnet is selected should be made a manual operation - Foreman

Custom queries

3.11.5 release DONE
3.11.5 release TODO
3.12.2 release DONE
3.12.2 release TODO
3.13.0 release DONE
3.13.0 release TODO
All bugs by votes
All issues closed in the last 3 weeks
Easy and Trivial Issues
Easy Issues (only)
Foreman - new open issues in last 10 days
Good first issues - Foreman core
high prio open bugs
Host registration [open]
Mine
My issues closed in the last 3 weeks
old bugs
Open with target version set (aka blockers)
registration
taken-none
Team Atlas untriaged bugs
templates
Trivial Issues
Untriaged and opened in the past two weeks

Actions

Copy link

Feature #1062

closed

The automatic loading of next ip when a subnet is selected should be made a manual operation

Added by Paul Kelly over 13 years ago. Updated almost 9 years ago.

Status:

Rejected

Priority:

Normal

Assignee:

Paul Kelly

Category:

Web Interface

Target version:

Difficulty:

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

I have been working on this project for a long time and I have never used this feature. I suspect that many others do not and find the wait annoying. If the user has selected a hypervisor then the selection should be automated, otherwise click on a link

Related issues 1 (0 open — 1 closed)

Related to Foreman - Bug #727: next_ip function always overwrites the ip address even if it has already been entered

Duplicate

Paul Kelly

03/12/2011

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Paul Kelly over 13 years ago

Status changed from New to Ready For Testing

Actions

Copy link

Updated by Ohad Levy over 13 years ago

Status changed from Ready For Testing to Feedback

I'm in mixed feelings about that, what is the relationship to hypvervisors?

Actions

Copy link

Updated by Paul Kelly over 13 years ago

Assignee changed from Paul Kelly to Ohad Levy

In the cold light of day I cannot really say why hypervisors should be treated any differently. In my case they were always attached to a local internal subnet so automatic IP assignment was useful to me but this was entirely site dependent. I guess that I made a stupid assumption.
However I do believe that the get_ip icon is useful. It is annoying when creating hosts that you have to wait 5, 10, 30 seconds before you can enter the mac and click continue. I think that one extra click to get the IP is a small price to pay for the flexibility of not having to wait for the ip suggestion. Do you wish for me to convert this so that you always click to get_ip?

Actions

Copy link

Updated by Ohad Levy over 13 years ago

Paul Kelly wrote:

However I do believe that the get_ip icon is useful. It is annoying when creating hosts that you have to wait 5, 10, 30 seconds before you can enter the mac and click continue. I think that one extra click to get the IP is a small price to pay for the flexibility of not having to wait for the ip suggestion. Do you wish for me to convert this so that you always click to get_ip?

can we make it a subnet setting?
why does it take 30 seconds?! I guess this is related to windows dhcp server, at least in my env it takes about 3-4 seconds..

What i dont understand is why you dont use this feature, is it because you have your own rules for ip allocations? or does it simply suggest bogus ip's ?

if we can support a better logic to assign ip's, imho that would be better, as not having to think ip address is a great plus.

Actions

Copy link