Bug #3815
possible to give lease that is not in network
| Status: | Closed | Start date: | 05/23/2015 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - | |||
| Resolution: | worksforme | Pull request: | ||
| Affected Versions: | OpenNebula 4.10 |
Description
As we managed the hosts, we recognized that chosing a wrong lease was possible.
The view should only show possible leases for the chosen host
History
#1
Updated by Ruben S. Montero about 6 years ago
- Status changed from Pending to Closed
- Resolution set to worksforme
Access is checked as cluster level: networks and hosts in the same cluster are supposed to work together. You can impose network-host checks if they are in the same cluster
#2
Updated by Nico Schottelius about 6 years ago
I think there is a slight misunderstanding here:
We have used a network definition like this:
NAME = "cluster2"
DESCRIPTION = "cluster2"
BRIDGE = "br0"
NETWORK_ADDRESS = "136.243.209.112"
NETWORK_MASK = "255.255.255.240"
DNS = "213.133.99.99 213.133.100.100 213.133.98.98"
GATEWAY = "136.243.209.113"
AR=[
TYPE = "IP4",
IP = "136.243.209.114",
SIZE = "13"
]
But where the actual address range has been out of the network. Opennebula accepts this, however it does not make any sense - does it?
#3
Updated by Ruben S. Montero about 6 years ago
Address ranges are in control of AR's. There is no check for CONTEXT variables. Multiple AR's with different address ranges, network masks or gateways can be combined in a network. You can define the Context variables per AR in this case.